$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 04/01/26 at 15:16 ============================================================================= Run Date: MAY 12, 2026 Designation: PSX*2*102 Package : PSX - CMOP Priority: Mandatory Version : 2 SEQ #84 Status: Released Compliance Date: JUN 12, 2026 ============================================================================= Associated patches: (v)PSX*2*98 <<= must be installed BEFORE `PSX*2*102' Subject: CMOP ERRORS DUE TO MISSING SIG Category: - Routine Description: ============ This patch addresses one issue: If a Consolidated Mail Outpatient Pharmacy (CMOP) prescription does not have information populated in the "SIG" field, the CMOP transmission process will error and cause transmission to halt for all prescriptions in the CMOP queue. EHRM Impact Statement: ---------------------- This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. 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 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: =========================================== INC42036723: CMOP Errors Due to Missing "SIG" Problem: -------- If a CMOP prescription does not have information populated in the "SIG" field, the CMOP transmission process will error and cause transmission to halt for all prescriptions in the CMOP queue. It is unknown how a prescription can be filed without this information. "Dosage ordered" and "Schedule" are required fields which are copied into the "SIG" field. Theoretically a prescription should not be filed without specifying a dosage and schedule. However, since the scenario can occur, the CMOP logic should not error because of the missing information. Resolution: ---------- Routine PSXMISC1 has been modified to initialize variable SIG before an evaluation is performed on the entry in the "SIG" field. The evaluation checks for embedded control characters and strips them out if found. Logic was already in place to check for an empty (null) SIG value after completion of the evaluation. However, because variable SIG was not initialized before the evaluation, an undefined error occurred at NG1+28^PSXMISC1 if the prescription did not contain any information. The logic already in place before PSX*2.0*102 intended to send a MailMan message if the "SIG" field was empty (null). Example: Subj: 442 CMOP Error Encountered [#568551] 04/01/26@18:34 18 lines From: POSTMASTER In 'IN' basket. Page 1 *New* -------------------------------------------------------------------------- An error has been encountered while processing prescription data for the Consolidated Mail Outpatient Pharmacy system. Date/Time : APR 1,2026@18:34 Process : Data Validation Error Type : Invalid or missing data Description : RX # Fill Data Field SSN NAME 3060652 Original SIG nnn-nn-nnnn XXXX,XXXX 3060652 Original SIG nnn-nn-nnnn XXXX,XXXX Action Taken: Rx's not sent to CMOP but still suspended for transmission. Recommended action: Correct invalid data. Enter message action (in IN basket): Ignore// Note: The prescription number might display twice depending on the MUMPS PSX routine code flow for a given prescription. Two routines (PSXBPSUT and PSXRPPL) call CHKDATA^PSXMISC1. Test Sites: ----------- Biloxi VAMC, Biloxi, MS Wilmington VAMC, Wilmington, DE SNOW Change Order Number: ------------------------- Biloxi VAMC: #CHG0721264 Wilmington VAMC: #CHG0722308 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 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. It is not necessary to disable any options. 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 name. (ex. PSX*2.0*102). 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 PSX*2.0*102. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. 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: ------------------------ 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. The back-out plan is to restore the routine from the backup created. No data was modified by this patch. Routine Information: ==================== The second line of each of these routines now looks like: ;;2.0;CMOP;**[Patch List]**;11 Apr 97;Build 1 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSXMISC1 Before: B48508352 After: B49075581 **3,18,23,28,30,42,41,52,54, 58,64,76,78,98,102** Routine list of preceding patches: 98 ============================================================================= User Information: Entered By : Date Entered : APR 01, 2026 Completed By: Date Completed: MAY 11, 2026 Released By : Date Released : MAY 12, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT