$TXT Created by at CLN1G1.AAC.DOMAIN.EXT (KIDS) on Tuesday, 03/17/20 at 09:52 ============================================================================= Run Date: JUL 20, 2020 Designation: PSJ*5*395 Package : PSJ - INPATIENT MEDICATIONS Priority: Mandatory Version : 5 SEQ #343 Status: Released Compliance Date: AUG 20, 2020 ============================================================================= Associated patches: (v)PSJ*5*279 <<= must be installed BEFORE `PSJ*5*395' (v)PSJ*5*337 <<= must be installed BEFORE `PSJ*5*395' Subject: PADE HL7 MESS w/SPEC CHAR / IV DOSE LIMIT ISSUE Category: - Routine Description: ============ This patch will address the following issues: 1. INC7737535 - The PADE software uses the character '&' as a subcomponent separator, preventing certain schedules from transmitting across the interface 2. INC8062634 - IV order processing with single line solution dismisses the ord.item dose limit Patient Safety Issues (HITPS): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC7737535 - The PADE software uses the character & as a subcomponent separator, preventing certain schedules from transmitting across the interface Problem: ------- When schedules have '&' as a part of their name, the schedule is truncated when it displays on Omnicell and nothing displays after the '&' (QID PC&HS displays on Omnicell as QID PC). This also affects drugs in the NDF that have '&' as part of their name. The '&' character is used as a subcomponent separator in HL7. The sending system (VistA) needs to encode the '&' when sending it and then Omnicell can change it back to an '&', which is the standard coding practice for HL7. Schedules and drugs that have an '&' as part of their name will have it replaced by \T\ in the outgoing PADE HL7 message. Resolution: ---------- A modification was made to routine PSJPDCLU to replace the '&' with the standard encoding escape character of \T\ for both the schedule name and the drug name for the outbound HL7 messages. 2. INC8062634 - IV order processing with single line solution dismisses the ord.item dose limit. Problem: ------- Routine PSIVCAL is called to compute the Stop Date of an Inpatient order for IV medications. The routine was incorrectly ignoring the Dose Limit set at the PHARMACY ORDERABLE ITEM file [#50.7] for this drug and computing the wrong Stop date. This issue is for a specific scenario involving a Pending order from CPRS that is Finished as an IV with no Additives and only a Solution for a medication. Resolution: ---------- A modification was made to routine PSIVCAL in the tag DDLIM to check the value of the reference in the Additive 0 node for true and not just that the node exists, else then default to the Solution's node value to find the correct Dispense Drug. Test Sites: ---------- Tampa VAMC, Tampa FL Charleston VAMC, Charleston SC Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Installation: Pre-Installation Instructions: -------------------------- If installed during the normal workday, it is recommended that the Outpatient Pharmacy users be off the system. Other VISTA users will not be affected. Install Time - less than 2 minutes (unless otherwise indicated) 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. 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//', NO. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', press the Enter key. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Back-out/Rollback Strategy: =========================== Post Installation Instructions: ------------------------------- None. Installation Verification: -------------------------- Successful installation can be verified by reviewing the first 2 lines of the routines contained in the patch. The second line will contain the patch number (395) in the [PATCH LIST] section. ;;5.0;INPATIENT MEDICATIONS;**[PATCH LIST]**;16 DEC 97;[BUILD #] The option Calculate and Show Checksum Values [XTSUMBLD-CHECK] can be run to compare the routine checksums to what is documented in the patch description. Back-out/Rollback Strategy: --------------------------- Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. Prior to installing an updated KIDS package, the site/region should have saved a backup of the routines in a mail message using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The message containing the backed-up routines can be loaded with the "Xtract PackMan" function at the Message Action prompt. The Packman function "INSTALL/CHECK MESSAGE" is then used to install the backed-up routines onto the VistA System. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure --------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the PSJ Routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routines contained in the PSJ*5.0*395 patch have been rolled back, the first two lines of the Routines will no longer contain the designation of patch PSJ*5.0*395 in the patch list section on line 2 Routine Information: ==================== The second line of each of these routines now looks like: ;;5.0;INPATIENT MEDICATIONS;**[Patch List]**;16 DEC 97;Build 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSIVCAL Before: B76248321 After: B76670260 **4,26,41,47,63,67,69,58,94, 80,110,111,177,120,134,229,279, 395** Routine Name: PSJPDCLU Before:B195649926 After:B198653553 **317,337,395** Routine list of preceding patches: 279, 337 ============================================================================= User Information: Entered By : Date Entered : NOV 13, 2019 Completed By: Date Completed: JUL 16, 2020 Released By : Date Released : JUL 20, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT