WI-OC-051 - Reporting Annotation Considerations
Key Information for how Annotations Interact with Reports, and Reporting Copy Down Workflow Information
Purpose
- Reference document for how copy downs affect the integration with Florence
- Details on how Annotation Updates affect reporting and Florence
Responsibilities
- Notifying Reporting team of Annotation Updates
- Application Adminsitrator
- Maintaining Reports Using Annotations
- Reporting Team
- Granting Permissions following a Copy Down to the Train environment for Florence
- Reporting Team
Instructions
- Each time a new version of annotation form is released it creates a new view for that version. Example: sv_an_pcl_oncologyv# (Where # is the version number).
- This view can be identified on the Info tab in the Forms module.
- The view takes roughly 15 minutes to generate.
- Permissions need to be granted to report writers and any other integration that use annotations.
- Through AMI, grants are generated every 15 minutes for read-only users (i.e. report writers).
- Read-restricted users must be granted view access manually. Via the UTILS schema login (wisc_oncore_rw_utils), the following code should be run: grant read on wisc_oncore_prod.VIEW_NAME to wisc_oncore_prod_rr# (where # is user-specific).
- Currently, there are two read-restricted users: wisc_oncore_prod_rr1 and wisc_oncore_prod_rr2. These users are needed to maintain the eBinders integration.
- These are the current reports using protocol annotations:
- Oncology:
- UWCC17 - SAS: Correlative Billing Report
- UWCC18 - SAS: Legacy Banking Billing Report
- WISC:
- WISC43 - SMPH Review Requirements REport
- SMPH03 - WebCAMP Data Export
- Non-oncology:
- Study Finder Requirements
- Study Finder Conditions**
- These must be sent to UMN to update the Study Finder code.
Disease Groups - query:
select disease_group1
from sv_an_pcl_non_oncologyv1
where protocol_id = #{connection.quote(protocol_id)}
and disease_group1 is not nullAdditional Conditions - query:
select additional_condition
from (
select add2_condition_pop as additional_condition
from sv_an_pcl_non_oncologyv1
where protocol_id = #{connection.quote(protocol_id)}
union
select add3_condition_pop as additional_condition
from sv_an_pcl_non_oncologyv1
where protocol_id = #{connection.quote(protocol_id)}
)
where additional_condition is not null
- These must be sent to UMN to update the Study Finder code.
- Oncology:
Document History
Reviewed Date | Change Reason | Approver |
---|---|---|
03/13/2023 | New | Brian Davidson |
5/1/2024 | Added restart of Florence application after permissions regranted | Sheri Alexander |
11/18/2024 | Removed annotation consideration for reporting team for Florence | Brian Davidson |
Related Documents
- Managing OnCore Protocol Annotations