$TXT Created by at CLN2G2.AAC.DOMAIN.EXT (KIDS) on Monday, 01/20/20 at 08:31 ============================================================================= Run Date: SEP 21, 2020 Designation: MD*1*78 Package : MD - CLINICAL PROCEDURES Priority: Mandatory Version : 1 SEQ #62 Status: Released Compliance Date: OCT 22, 2020 ============================================================================= Associated patches: (v)MD*1*60 <<= must be installed BEFORE `MD*1*78' Subject: AUTO CHECK-IN ORDER NUMBER ISSUE Category: - Routine Description: ============ This patch addresses the following issue: Auto check-in issues with Muse procedures: The auto check-ins that occur within a certain time frame after midnight are only creating 7-digit order numbers. Muse requires a 9-digit order number. Defect Tracking System Ticket(s) & Overview: 1. INC7749918 - Auto check-in issues with Muse procedures; 7-digit order number created instead of 9-digit order number. Problem: -------- Muse version 9 requires a 9-digit order number sent to the Muse server from VistA via HL7. Auto check-in occurs each night when the Study Check-in [MD STUDY CHECK-IN] job runs slightly after midnight. At the Memphis VA Medical Center, a problem was discovered with Muse studies being attached to a 7-digit order number. They do not file correctly in VistA Imaging leading to breakdown and delays in care for patients. The current workaround is to use Clinical Procedures (CP) User to check in the patients manually. Manual check-in generates a 9-digit order number resulting in the Muse studies filing correctly in VistA Imaging. The problem is that the logic to build the 9-digit number being sent from VistA creates a number less than 9 digits when it executes between midnight and 2:46 AM. Resolution: ----------- The creation of an order number less than 9 digits is due to how routine MDRPCOT1 creates it using the $H special variable, which provides a date (number of days since 1/1/1841) and a time (number of seconds since midnight) value. The time portion of $H date/time value will be less than 5 digits until 02:46:40 AM. The order number is created from digits 2-5 of the date (which will always be 4 digits) concatenated with the time portion which is from 1-5 digits depending on the time of day. MDRPCOT1 is modified with this patch to pad the time returned in $H with zeros to a length of 5 before using it to create the order number. Before the patch: $H = 65317,560 (10/31/19 12:09:20 AM) Order Number = 5317560 (invalid in Muse) After the patch: $H = 65317,560 (10/31/19 12:09:20 AM) Order Number = 531700560 (valid in Muse) The order number sent to Muse after 02:46:39 AM is not affected: $H = 65317,10000 (10/31/19 02:46:40 AM) Order Number = 531710000 Test Sites: ----------- Captain James A. Lovell Federal Health Care Center (North Chicago, IL) Louis A. Johnson VAMC (Clarksburg, WV) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: ------------------- Pre-Installation Instructions: This patch may be loaded with users on the system. You may wish to install it during non-peak hours. Installation will take less than 1 minute. NOTE: Kernel patches must be current on the target system to avoid problems loading and/or installing this patch. 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. or XXXXX BUILD X.X) NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. 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. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Back-Out/Roll Back Plan: ------------------------ In the event of a catastrophic failure, the Facility CIO may make the decision to back-out the patch. It is imperative that you have performed a backup of the routine included in this patch prior to installation. The back-out plan is to restore the routine from the backup created. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;CLINICAL PROCEDURES;**[Patch List]**;Apr 01, 2004;Build 7 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MDRPCOT1 Before: B62839525 After: B66247005 **5,11,21,41,60,78** Routine list of preceding patches: 60 ============================================================================= User Information: Entered By : Date Entered : OCT 29, 2019 Completed By: Date Completed: SEP 18, 2020 Released By : Date Released : SEP 21, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT