Original message: "ROR*1.5*30 T2 5/19/17" [#156560] ============================================================================= Run Date: AUG 29, 2017 Designation: ROR*1.5*30 Package : ROR - CLINICAL CASE REGISTRIES Priority: Mandatory Version : 1.5 SEQ #30 Status: Released Compliance Date: SEP 29, 2017 ============================================================================= Associated patches: (v)ROR*1.5*8 <<= must be installed BEFORE `ROR*1.5*30' (v)ROR*1.5*19 <<= must be installed BEFORE `ROR*1.5*30' (v)ROR*1.5*21 <<= must be installed BEFORE `ROR*1.5*30' (v)ROR*1.5*26 <<= must be installed BEFORE `ROR*1.5*30' (v)ROR*1.5*29 <<= must be installed BEFORE `ROR*1.5*30' (v)PSN*4*507 <<= must be installed BEFORE `ROR*1.5*30' Subject: CLINICAL CASE REGISTRY SUSTAINMENT Category: - Routine - Data Dictionary - Other Description: ============ This patch includes several enhancements and corrections to the Clinical Case Registries (CCR) package. These changes include: 1. Two new local registries added: (Idiopathic Pulmonary Fibrosis (IPF) Registry - VA IPF, Hypoparathyroidism - VA HYPOPARA) including the following functionality: a. The set up and initial build of the new registries. b. Adding the new registries to the nightly job that searches for and adds patients to them, based on registry-specific International Classification of Disease, 9th edition (ICD-9), International Classification of Disease, 10th edition (ICD-10) procedure codes and Current Procedural Technology (CPT) procedure codes. c. The standard local reports currently available in CCR will be available for the new registries. 2. It was discovered that the Hepatitis A and Hepatitis B reports were not finding all patients who have laboratory documented immunity. HCV and HIV labs have always used upper case searches for positive LOINC results so results entered in mixed case were missed. The code has been modified to change all positive LOINC results to upper case. 3. The caption on the Sex panel has been modified from Sex to Birth Sex. The output for the report headers and report columns were modified appropriately. 4. One new medication had been added to the ROR GENERIC DRUG file (#799.51) to be used as inclusion criteria for patients in the respective registry(s). a. HEP C registry: SOFOSBUVIR/VELPATASVIR 5. The warning on the Potential DAA Candidates report will be updated to remove the reference to genotype 1, as the report no longer requires genotype 1. 6. Additional CCR GUI updates were made to work towards becoming fully compliant with the Section 508Section_508 standards. 7. The version of the CCR software has been updated to 1.5.30. Patch Components: ----------------- File Data Included: File Name (Number) Entry Name New/Modified/Deleted ------------------ ------------------ -------------------- ROR REGISTRY PARAMETERS VA IPF New (#798.1) VA HYPOPARA New ROR SELECTION RULE VA IPF PTF New (#798.2) VA IPF PTF (ICD10) New VA IPF PROBLEM New VA IPF PROBLEM New (ICD10) VA IPF VPOV New VA IPF VPOV (ICD10) New ROR SELECTION RULE VA HYPOPARA PTF New (#798.2) VA HYPOPARA PTF (ICD10) New VA HYPOPARA PROBLEM New VA HYPOPARA PROBLEM New (ICD10) VA HYPOPARA VPOV New VA HYPOPARA VPOV (ICD10) New ROR ICD SEARCH (#798.5) VA IPF New VA HYPOPARA New ROR XML ITEM (#799.31) BIRTHSEX New BIRTHSEX_SUMMARY New ROR GENERIC DRUG SOFOSBUVIR/VELPATASVIR New (#799.51) ROR LIST ITEM (#799.1) eGFR by CKD-EPI New Registry: VA IPF eGFR by MDRD New Registry: VA IPF Creatinine clearance New by Cockroft-Gault Registry: VA IPF FIB-4 New Registry: VA IPF APRI New Registry: VA IPF MELD-Na New Registry: VA IPF MELD New Registry: VA IPF BMI New Registry: VA IPF eGFR by CKD-EPI New Registry: VA HYPOPARA eGFR by MDRD New Registry: VA HYPOPARA Creatinine clearance New by Cockcroft-Gault Registry: VA HYPOPARA FIB-4 New Registry: VA HYPOPARA APRI New Registry: VA HYPOPARA MELD-Na New Registry: VA HYPOPARA MELD New Registry: VA HYPOPARA BMI New Registry: VA HYPOPARA New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Remedy Ticket(s) & Overview: ---------------------------- N/A Test Sites: ---------- San Antonio, Tx Palo Alto HCS, Ca Coatesville, Pa Installation Files ================== GUI Update ---------- IMPORTANT NOTE: This patch includes a revised Graphical User Interface (GUI) application which must be distributed to the appropriate workstations. After the patch is installed correctly, and the GUI is updated, the version of the GUI will be 1.5.30. File Name Contents Transfer Mode --------- ----------- ------------- ROR1_5P30GUI.ZIP Zipped GUI BINARY The file listed above may be obtained via Secure File Transfer PROTOCOL (SFTP). The preferred method is to SFTP the file from: Download.vista.domain.ext. This transmits the file from the first available FTP server. Sites may also elect to retrieve software directly from a specific server as follows: OIFO SFTP Address Directory ---------------- ------------------------- -------------------- Albany domain.ext [] Hines domain.ext [] Salt Lake City domain.ext [] M Code ------ Included as a standard PackMan message. Documentation Files =================== The documentation has been updated and is distributed in the following two zipped files. Each zip file contains both the .DOC and .PDF formats. File Name Description Protocol ----------------------------------------------------------------- ROR1_5P30DOC1.ZIP ROR User Manual BINARY ROR1_5P30DOC2.ZIP Release Notes, BINARY Technical Manual/Security Guide, Installation/Implementation Guide The revised CCR documentation is available on the ANONYMOUS.SOFTWARE directory at one of the following OIFO FTP Address Directory -------------- ------------------------ ------------------ Albany domain.ext Hines domain.ext Salt Lake City domain.ext Sites may retrieve documentation in one of the following ways: 1. The preferred method is to use SFTP to download the files from download.vista.domain.ext, which will transmit the files from the first available server. 2. Sites may also elect to retrieve documentation directly from a specific server listed above. Documentation may also be retrieved from the VistA Documentation Library (VDL) on the Intranet at the following address: http://www4.domain.ext/vdl Patch Installation Overview: ============================ This patch includes an M patch and a revised Graphical User Interface (GUI) executable. Below is a summary of the installation steps required for this patch. 1. Install M components. 2. Update GUI. Patch Installation: ------------------ M INSTALLATION INSTRUCTIONS: ---------------------------- Installation of the patch will not take more than 5 minutes. This patch can be installed with VistA users online, but Registry users should be logged out of the CCR Registry Application, as a new GUI is to be installed. There are no options that need to be disabled prior to patch install. NOTE: The nightly task (Registry Update & Data Extraction [ROR TASK] option) must not be running during the installation. Pre/Post Installation Overview: ------------------------------- The pre-installation routine for this patch checks to be sure the task Initialize new registries (one time) [ROR INITIALIZE] is not running. If it is, the user is informed of the task number found and that the job must finish or be terminated before the patch can be installed. The patch installation then exits, incomplete. Routine name is PRE^RORP030. The post-installation routine for this patch is POST^RORP030 and performs the following functions: - Schedules the Initialize new registries (one time) [ROR INITIALIZE] option to run. If the new registries included in the patch have already been initialized, the user can opt not to re-do the initialize for each registry. - Adds eight entries to the ROR LIST ITEM file (#799.1) for each of the new registries added with this patch. - Adding CPT and ICD-9 procedures to ROR ICD SEARCH file for new registries") Installation Instructions: -------------------------- The post-initialization routine for this patch schedules the Initialize new registries (one time) [ROR INITIALIZE] task to run. During the installation process, you will be presented with a series of questions that must be answered that will be used to schedule this task. The following questions provide the parameters needed to schedule this task: Maximum number of registry update subtasks: [valid response is a number 0-10] Suspend the post-install during the peak hours: [valid response is Yes/No] If the answer to this question is Yes, then the following 2 questions must be answered: Suspension start time: [valid response is any valid time input] Suspension end time: [valid response is any valid time input occurring after the start time] Date/Time to run the new registry initialize task: [valid response is a date/time that is at least 15 minutes in the future.] If this patch needs to be re-installed after the new registries have been initialized, the following will be prompted to allow this step to be skipped for each of the new registries: >> New registry has already completed initialization Do you want to rerun its initialization?: NO// Once initialized, do not respond YES to this prompt unless you are requested to do so by the CCR team. Installation steps: ------------------ 1. Unschedule or delete the Registry Update & Data Extraction [ROR TASK] job (CCR nightly job) from the Schedule/Unschedule Options [XUTM SCHEDULE] in Taskman. 2. Choose the PackMan message containing this patch. 3. Choose the INSTALL/CHECK MESSAGE PackMan option. 4. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, you may elect to use the following options. When prompted for the INSTALL NAME enter the patch designation 'ROR*1.5*30': a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DDs or templates. It is recommended this step be done as it will be needed if a rollback is required for this patch in the future. b. **Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all components of this patch (routines, DDs, templates, etc.). ** Note that for this patch, this option will produce a system error due to the known problem with Fileman not correctly handling the lookup to a file with no B cross reference. There is currently no workaround for this problem. The error expected to be produced is: I C["P",$D(@("^"_$P(^(0),U,3)_"0)")) S C=$P(^(0),U,2) Q:'$D(^(+Y,0)) S Y=$P(^(0),U) I $D(^DD(+C,.01,0)) S C=$P(^(0),U,2) G S S+1^DIQ This issue does not affect the installation of the CCR patch. The patch will install without issue.^ c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 5. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', respond NO 8. The post-initialization routine for this performs the following functions: a. Updates data in the following files: ROR REGISTRY PARAMETERS (#798.1) b. Adds eight entries to the ROR LIST ITEM file (#799.1) for each of the new registries added with this patch. c. Schedules the Initialize new registries (one time) [ROR INITIALIZE] option to run. This task sets up and populates the 5 new registries added with this patch. d. You must periodically (at least once per day) check the status of the Initialize new registries (one time) [ROR INITIALIZE] job. When it has successfully completed, you must restart the Registry Update & Data Extraction [ROR TASK] job. INSTALLATION EXAMPLE: ==================== elect Installation Option: INstall Package(s) Select INSTALL NAME: ROR*1.5*30 2/28/17@13:23:44 => ROR*1.5*30 This Distribution was loaded on Feb 28, 2017@13:23:44 with header of ROR*1.5*30 It consisted of the following Install(s): ROR*1.5*30 Checking Install for Package ROR*1.5*30 Install Questions for ROR*1.5*30 Incoming Files: 798.1 ROR REGISTRY PARAMETERS (including data) Note: You already have the 'ROR REGISTRY PARAMETERS' File. I will OVERWRITE your data with mine. 798.2 ROR SELECTION RULE (including data) Note: You already have the 'ROR SELECTION RULE' File. I will OVERWRITE your data with mine. 798.5 ROR ICD SEARCH (including data) Note: You already have the 'ROR ICD SEARCH' File. I will OVERWRITE your data with mine. 799.31 ROR XML ITEM (including data) Note: You already have the 'ROR XML ITEM' File. I will OVERWRITE your data with mine. 799.51 ROR GENERIC DRUG (including data) Note: You already have the 'ROR GENERIC DRUG' File. I will OVERWRITE your data with mine. Maximum number of registry update subtasks: (0-10): 5// Suspend the post-install during the peak hours ? NO// Suspension start time: 7:00AM// Suspension end time: 6:00PM// 7PM Date/Time to run the new registry initialize task: 8AM Want KIDS to INHIBIT LOGONs during the install? NO// Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// Enter the Device you want to print the Install messages. You can queue the install by enter a 'Q' at the device prompt. Enter a '^' to abort the install. DEVICE: HOME// WORKSTATION ROR*1.5*30 The scheduled task number is 8919396 >> Step complete POST INSTALL COMPLETE Updating Routine file... Updating KIDS files... ROR*1.5*30 Installed. Feb 28, 2017@13:26:49 Not a production UCI NO Install Message sent Install Completed Routine Information: ==================== The second line of each of these routines now looks like: ;;1.5;CLINICAL CASE REGISTRIES;**[Patch List]**;Feb 17, 2006;Build 37 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RORP030 Before: n/a After: B84964316 **30** Routine Name: RORRP016 Before: B89480677 After: B90558646 **1,10,23,19,30** Routine Name: RORRP020 Before: B29770622 After: B30397748 **1,8,30** Routine Name: RORUPD52 Before: B12529395 After: B12757919 **30** Routine Name: RORUTL11 Before: B4575612 After: B4666039 **13,14,15,17,18,20,19,21,22, 24,27,25,26,28,29,30** Routine Name: RORX000 Before: B4541569 After: B4748275 **30** Routine Name: RORX003 Before: B39028501 After: B39739839 **1,8,13,19,21,30** Routine Name: RORX003A Before: B48786633 After: B49665251 **1,21,30** Routine Name: RORX024A Before: B72187457 After: B73730046 **29,30** Routine Name: RORXU002 Before:B146259436 After:B148272435 **1,10,13,15,17,19,21,22,26,29,30** Routine Name: RORXU005 Before: B44286894 After: B45030841 **1,15,21,22,26,30** Routine list of preceding patches: 29 ============================================================================= User Information: Entered By : Date Entered : MAR 29, 2017 Completed By: Date Completed: AUG 28, 2017 Released By : Date Released : AUG 29, 2017 ============================================================================= Packman Mail Message: ===================== $END TXT