Purpose

1. Reference document for how copy downs affect the integration with Florence
2. Details on how Annotation Updates affect reporting and Florence 

Responsibilities

1. Notifying Reporting team of Annotation Updates
   1. Application Adminsitrator 
2. Maintaining Reports Using Annotations
   1. Reporting Team
3. Granting Permissions following a Copy Down to the Train environment for Florence
   1. Reporting Team 

Instructions

1. 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).
   1. This view can be identified on the Info tab in the Forms module.
   2. The view takes roughly 15 minutes to generate.
2. Permissions need to be granted to report writers and any other integration that use annotations.
   1. Through AMI, grants are generated every 15 minutes for read-only users (i.e. report writers).
   2. 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.
3. These are the current reports using protocol annotations:
   1. Oncology:
      1. UWCC17 - SAS: Correlative Billing Report
      2. UWCC18 - SAS: Legacy Banking Billing Report 
   2. WISC:
      1. WISC43 - SMPH Review Requirements REport
      2. SMPH03 - WebCAMP Data Export
   3.  Non-oncology:
      1. Study Finder Requirements
      2. Study Finder Conditions**
         1. 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 null

             

            Additional 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

Document History

Related Documents

• Managing OnCore Protocol Annotations
  
  • https://kb.wisc.edu/smph/informatics/internal/page.php?id=115620