$TXT Created by at MDEVC.FO-BIRM.DOMAIN.EXT (KIDS) on Friday, 06/26/20 at 14:53 ============================================================================= Run Date: JUL 14, 2020 Designation: DG*5.3*1005 Package : DG - REGISTRATION Priority: EMERGENCY Version : 5.3 SEQ #881 Status: Released Compliance Date: JUL 15, 2020 ============================================================================= Associated patches: (v)DG*5.3*951 <<= must be installed BEFORE `DG*5.3*1005' (v)XU*8*720 <<= must be installed BEFORE `DG*5.3*1005' Subject: HL7 ROUTING UPDATE FOR PRF/CERNER Category: - Routine - Other Description: ============ This patch does the following: 1. Modify routing of Patient Record Flag (PRF) messages so that if the recipient is a Cerner site then ORU messages will also be sent to a site specific HealthConnect regional router, and QRY messages will be sent to the national HealthConnect router. 2. Modify DGPFHLU3 to allow for the case where message control IDs may be alphanumeric. 3. Fix a problem where assignment histories cannot be stored if there are no comments. 4. Add a new PARAMETER DEFINITION that identifies the name of the logical link for the VDIF regional router appropriate to the facility. 5. Adds HL LOGICAL LINKs for each of the six VDIF regional routers and adds VACRNR (national router) if it is not present. 6. Fix a problem where inactivating a Category II PRF could leave assignments using the inactivated flag in an active state. 7. Adds a protocol Virtual Patient Record needs to update Health Share. 8. Filters out facilities of type OTHER when building treating facility list. 9. Adds a new mail group DGPF APPLICATION ERRORS and sends messages to this group when HL7 application errors are sent to VDIF. This mail group should be populated with support personnel who will be responsible for monitoring PRF errors. The Outlook group OEHRM Tier II Support will be automatically added to this group as an external recipient. (Note: the error messages generated do not contain PII/PHI). There are several message triggers (types of errors), a typical example is Subj: PRF Application Error (station #984) [T] [#617149] 05/29/20@15:48 2 lines From: PRF ERROR PROCESSOR In 'IN' basket. Page 1 -------------------------------------------------------------------------- One or more parse errors occurred in message #63337562. Error #261111 occurred in OBR-4. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- DGPF APPLICATION ERRORS New Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- DGPF PRF EVENT New Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definition New/Modified/Deleted -------------------- -------------------- DG PRF REGIONAL ROUTER New Logical Links New/Modified/Deleted ------------- -------------------- DGVDFRR11 New DGVDFRR12 New DGVDFRR2 New DGVDFRR3 New DGVDFRR41 New DGVDFRR42 New Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Test Sites: ----------- Altoona, PA Charleston, SC Software Documentation and Retrieval Instructions: ------------------------------------------------- This software is distributed as a PackMan patch only. Documentation Title File Name FTP Mode --------------------------------------------------------------------- N/A Host File Name FTP Mode --------------------------------------------------------------------- N/A Patch Installation: ------------------- Pre/Post Installation Overview: Pre-Installation Instructions: This patch takes less than a minute to install. This patch may be installed with users on the system, but it is recommended that installation occurs during off hours. If the coordinator of the DGPF APPLICATION ERRORS mail group is to be anyone but the installer, enter that person's name (from the NEW PERSON file) at the mail group Coordinator prompt. The HL7 incoming filers should be stopped. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch or build name. (ex. DG*5.3*1005) B. Select the Backup a Transport Global option to create a backup message of any routines exported with this patch. It will not backup any other changes such as DDs or templates. C. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. 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 of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. When prompted for a mail group coordinator, enter the name of the person who should be mail group coordinator or accept the default to select yourself. ii. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer NO. iii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iv. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. a. When prompted 'Delay Install (Minutes): (0 - 60):0//', answer 0. Post-Installation Instructions: ------------------------------- The links VACRNR and DGVDFRR* should NOT be modified or configured at the present time. A future informational patch will contain information on configuring these links. After patch installation has completed, restart the HL7 incoming filers. Use the Monitor, Start, Stop Filers [HL FILER MONITOR] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. Review the patch installation via the menu (INSTALL FILE PRINT) or the install file in FileMan to determine if any attempted local record flag inactivations were not filed successfully during the installation. If notice(s) are displayed in the install file regarding "Local record flag ... inactivation was not filed successfully" please use the Record Flag Management [DGPF RECORD FLAG MANAGEMENT] option to inactivate the flag(s) noted during the install. You will have to Change Category [CC] upon entering the screen to get to local flags, then Edit Record Flag [EF] to inactivate the flag(s). Please contact Health Product Support if there are issues with this manual process. Back-Out/Roll Back Plan: ------------------------ Restore the DG* routines from the backup created as part of the installation process. The PARAMETER DEFINITION "DG PRF REGIONAL ROUTER" should be deleted as should the following HL LOGICAL LINKs: DGVDFRR11 DGVDFRR12 DGVDFRR2 DGVDFRR3 DGVDFRR41 DGVDFRR42 To delete the parameter, first delete the parameter instance using DEL^XPAR then delete the entry in the PARAMETER INSTANCE file using FileMan: MDEVB>D DEL^XPAR("SYS","DG PRF REGIONAL ROUTER",1,.ERR) ZW ERR ERR=0 MDEVB>D Q^DI VA FileMan 22.2 Select OPTION: ENTER OR EDIT FILE ENTRIES Input to what File: HL LOGICAL LINK// PARAMETER DEFINITION (939 entries) EDIT WHICH FIELD: ALL// .01 NAME THEN EDIT FIELD: Select PARAMETER DEFINITION NAME: DG PRF REGIONAL ROUTER Regional Router NAME: DG PRF REGIONAL ROUTER Replace @ SURE YOU WANT TO DELETE THE ENTIRE 'DG PRF REGIONAL ROUTER' PARAMETER DEFINIT ION? Y (Yes) SINCE THE DELETED ENTRY MAY HAVE BEEN 'POINTED TO' BY ENTRIES IN THE 'XHD PARAMETER CATEGORY' FILE, ETC., DO YOU WANT THOSE POINTERS UPDATED (WHICH COULD TAKE QUITE A WHILE)? No// Y (Yes) WHICH DO YOU WANT TO DO? -- 1) DELETE ALL SUCH POINTERS 2) CHANGE ALL SUCH POINTERS TO POINT TO A DIFFERENT 'PARAMETER DEFINITION' E NTRY CHOOSE 1) OR 2): 1 DELETE ALL POINTERS? Yes// (Yes) (DELETION WILL OCCUR WHEN YOU LEAVE 'ENTER/EDIT' OPTION) Select PARAMETER DEFINITION NAME: ...EXCUSE ME, I'M WORKING AS FAST AS I CAN... DEVICE: HOME// Linux Telnet /SSh For the logical links, be sure each link is Shutdown (or has no entry for its STATE field) as follows: Select OPTION: PRINT FILE ENTRIES Output from what File: HL LOGICAL LINK// (275 entries) Sort by: NODE// Start with NODE: FIRST// DGVDF Go to NODE: LAST// DGVDFZZ Within NODE, Sort by: First Print FIELD: NODE Then Print FIELD: STATE Then Print FIELD: Heading (S/C): HL LOGICAL LINK List Replace START at PAGE: 1// DEVICE: Linux Telnet /SSh HL LOGICAL LINK List JUL 10, 2020@11:40 PAGE 1 NODE STATE -------------------------------------------------------------------------- DGVDFRR11 Shutdown DGVDFRR12 DGVDFRR2 DGVDFRR3 DGVDFRR41 DGVDFRR42 If any of them are running, shut them down by selecting SL on the Filer and Link Management menu [HL MENU FILER LINK MGT], enter the name of the link and answer YES when asked if you want to shut down the link. You may then delete the links from the HL LOGICAL LINK (#870) file using FileMan. If assistance is still required to back-out the patch please contact the National Service Desk (NSD) to log a help desk ticket so the development team can assist in the process. Note: This process should only be done with the concurrence and participation of the development team and the appropriate VA Site/Region personnel. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Registration;**[Patch List]**;Aug 13, 1993;Build 57 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: DGPFAA Before: B81848262 After: B84231125 **425,921,951,1005** Routine Name: DGPFAAH Before: B57134079 After: B58738836 **425,554,951,1005** Routine Name: DGPFHLR Before:B124847191 After:B154472676 **425,650,951,1005** Routine Name: DGPFHLS Before: B55420041 After: B90778990 **425,650,1005** Routine Name: DGPFHLU3 Before: B31602328 After: B32016606 **425,650,951,1005** Routine Name: DGPFHLU6 Before: B6742118 After: B15319134 **425,554,1005** Routine Name: DGPFHLUT Before: B64018223 After: B64018223 **425,650,951,1005** Routine Name: DGPFPOST Before: n/a After: B21448491 **1005** Routine Name: DGPFUT2 Before: B44485554 After: B46919303 **425,554,650,1005** Routine Name: DGPFXCRN Before: n/a After: B10108323 **1005** Routine Name: DGY994PO Before: n/a After: B33994265 **1005** Routine list of preceding patches: 951 ============================================================================= User Information: Entered By : Date Entered : DEC 05, 2019 Completed By: Date Completed: JUL 14, 2020 Released By : Date Released : JUL 14, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT