============================================================================= Run Date: FEB 27, 2023 Designation: OR*3*597 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #503 Status: Released Compliance Date: MAR 30, 2023 ============================================================================= Associated patches: (c)PX*1*233 install with patch `OR*3*597' (c)PXRM*2*84 install with patch `OR*3*597' (v)OR*3*405 <<= must be installed BEFORE `OR*3*597' Subject: POST CPRS V32B - VIMM FIXES Category: - Routine Description: ============ This patch is part of a multi-package build. The other patches are PX*1*233, and PXRM*2*84. This patch corrects issues identified after the installation of CPRS v32b related to the Veterans Health Information Systems and Technology Architecture (VistA) Immunizations Enhancements (VIMM). See below, "Defect Tracking System Ticket(s) & Overview", for a full list of defects fixed by this patch. 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 --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A 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 Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. VISTAOR-33137 - Immunization Times Incorrect for Guam/Saipan Problem: -------- Guam/Saipan is on Honolulu VistA time, so they see patients the "day before" the appointment date. This creates an incorrect entry in the system when documenting Vaccines or Skin Tests. They need the ability to allow for future entry of the vaccine or skin test in the VIMM form. Resolution: ----------- Changes were made to check the ORPARAM OVER DATELINE parameter. If the parameter is set to YES, a future date/time before tomorrow at 23:59 is now allowed when documenting an immunization or skin test. 2. VISTAOR-31517 - Lot Numbers Should be Sorted Alphanumerically Problem: -------- On the CPRS Immunization form, when documenting an administered immunization, the lot numbers are sorted by internal entry number (IEN). Resolution: ----------- This patch will change it to sort lot numbers alphanumerically. 3. VISTAOR-33056 - Skin Test Reading Unit of Measure Problem: -------- When entering a skin test reading, the Measurements field does not display the unit of measurement, both in the form and in the note text that is outputted. Resolution: ----------- In this patch the label on the form will be changed to "Reading in millimeters (mm)", and similarly the note text will be updated to show "mm", example: "Reading: 2 mm." 4. VISTAOR-33361 - VIMM Form Lets User Document Immunization for Inpatient Without Selecting a Lot Problem: -------- An issue can occur where the VIMM form loads with the Lot Number field greyed out, and it lets the user document the immunization without selecting a lot number. It only happens for inpatients when there is at least one active lot for that immunization at TODAY@00:00, but as of now, all the lots for that immunization are inactive or expired. Resolution: ----------- When loading lots for an inpatient, the system will check if the lot is active based off NOW, instead of TODAY@00:00. Also, validation was added to prevent a user from saving a VA-administered immunization without a Lot Number. Test Sites: ----------- New Orleans VAMC (New Orleans, LA) Pacific Islands HCS (Honolulu, HI) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/CPRS_V32B_VIMM_FOLLOW_UP.KID Patch Installation: ------------------- Pre/Post Installation Overview: There are no pre/post installation steps associated with this patch. Pre-Installation Instructions: This patch may be installed with users on the system although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Installation Instructions: 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:" enter /srv/vista/patches/SOFTWARE/CPRS_V32B_VIMM_FOLLOW_UP.KID 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 CPRS V32B VIMM FOLLOW-UP PATCHES 1.0. 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. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter your build, CPRS V32B VIMM FOLLOW-UP PATCHES 1.0. iii. At the Subject prompt, after the subject name, press Enter to accept the default. iv. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// Press Enter to select Build v. When prompted for "Enter a Host File:", enter the path and name for the host file backup file. If you don't specify a directory, the default directory of HFS Primary Directory will be used. 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. Post-Installation Instructions: N/A Back-Out/Roll Back Plan: ------------------------ 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 build to a Host file using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The Host file containing the back-up can be installed using the Installation Menu on the Kernel Installation and Distribution System Menu. The back-out plan is to restore the routines from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;ORDER ENTRY/RESULTS REPORTING;**[Patch List]**;Dec 17, 1997;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORFIMM Before:B184651996 After:B195782958 **405,597** Routine Name: ORFIMM1 Before:B127100033 After:B137891844 **405,597** Routine Name: ORFIMM2 Before: B24997789 After: B25909619 **405,597** Routine Name: ORFSKT Before:B175502675 After:B176446239 **405,597** Routine list of preceding patches: 405 ============================================================================= User Information: Entered By : Date Entered : DEC 07, 2022 Completed By: Date Completed: FEB 22, 2023 Released By : Date Released : FEB 27, 2023 ============================================================================= Packman Mail Message: ===================== No routines included