$TXT Created by NNE at MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 06/01/23 at 15:00 ============================================================================= Run Date: AUG 29, 2023 Designation: PSO*7*724 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #602 Status: Released Compliance Date: SEP 29, 2023 ============================================================================= Associated patches: (v)PSO*7*696 <<= must be installed BEFORE `PSO*7*724' Subject: SPMP ZERO REPORT FIXES Category: - Data Dictionary - Routine Description: ============ This patch will resolve the following issues: 1) Zero Report email verbiage: A Zero Report batch is transmitted when there are no controlled substances to report. When that happens an email for the Zero Report batch is generated announcing a Zero Report was transmitted to the state. When the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] job fails to transmit a Zero Report batch when it should have, another email is generated announcing that the transmission failed. When the job fails, both emails will be sent for the Zero Report batch with contradicting wording. The first email says the transmission failed; the second email says that the Zero Report was transmitted. To reduce confusion at the sites, the wording in the Zero Report email should be corrected to not indicate the transmission status, thereby avoiding confusion when the job fails and the "transmission failed" email is also sent. 2) PSO*7*696 follow-up issues: Four issues were identified regarding the field, ZERO REPORT DEFAULT DIVISON (#22), in the SPMP STATE PARAMETERS (#58.41) file that was added with the release of patch PSO*7.0*696. All of the items deal with the View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option. 1. When the SEND EXPORT STATE PARAMETER="2" but the ZERO REPORT DEFAULT DIVISION State Parameter is not set, then no Zero Report is generated. However, currently the ZERO REPORT DEFAULT DIVISION (#22) field is not a required field when using the View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option. It should be a required field within the View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option when SEND EXPORT STATE PARAMETER is set to "2" to ensure that Zero reports will be sent. 2. The Help Text for the ZERO REPORT DEFAULT DIVISION State Parameter does not clearly indicate it is required when the SEND EXPORT STATE PARAMETER="2". 3. When using the SEND EXPORT STATE PARAMETER, the State Parameter ZERO REPORT DEFAULT DIVISION prompt shows "//" even when it's blank. This is not normal behavior since empty fields should not have "//". This is only cosmetic and does not affect functionality of the Zero Report, but it should be fixed. 4. The wording of the Technical Description of the ZERO REPORT DEFAULT DIVISION (#22) field in the SPMP STATE PARAMETERS (#58.41) file is a little confusing by saying it is used for "MbM states that do not dispense controlled substances". It should be clarified to say this is used when a state has the State Parameter SEND EXPORT STATE PARAMETER set to "2". Associated ticket(s): --------------------- INC26586596 - Zero Report verbiage INC27015594 - PSO*7*696 IOC follow-up issues Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- SPMP STATE PARAMETERS (#58.41) Modified ZERO REPORT DEFAULT DIVISION (#22) 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 List Templates Associated: Template Name Type 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 New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1) INC26586596 - Zero Report verbiage Problem: -------- A Zero Report batch is transmitted when there are no controlled substances to report. When that happens an email for the Zero Report batch is generated announcing a Zero Report was transmitted to the state. When the Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] job fails to transmit a Zero Report batch when it should have, another email is generated announcing that the transmission failed. When the job fails, both emails will be sent for the Zero Report batch with contradicting wording. The first email says the transmission failed; the second email says that the Zero Report was transmitted. To reduce confusion at the sites, the wording in the Zero Report email should be corrected to not indicate the transmission status, thereby avoiding confusion when the job fails and the "transmission failed" email is also sent. Resolution: ----------- The current verbiage for the second email for the Zero Report is the following: "A Zero Report has been transmitted to the state." The verbiage has been changed to the following: "A Zero Report has been created for transmission to the state." Technical Resolution: --------------------- The SENDMAIL^PSOSPML0 API was updated with the new verbiage for the Zero Report email. 2) INC27015594 - PSO*7*696 SPMP Zero report follow-up issues Problem: -------- Four issues were identified regarding the field, ZERO REPORT DEFAULT DIVISON (#22), in the SPMP STATE PARAMETERS (#58.41) file that was added with the release of patch PSO*7.0*696. All of the items deal with the View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option. 1. When the SEND EXPORT STATE PARAMETER="2" but the ZERO REPORT DEFAULT DIVISION State Parameter is not set, then no Zero Report is generated. However, currently the ZERO REPORT DEFAULT DIVISION (#22) field is not a required field when using the View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option. It should be a required field within the View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option when SEND EXPORT STATE PARAMETER is set to "2" to ensure that Zero reports will be sent. 2. The Help Text for the ZERO REPORT DEFAULT DIVISION State Parameter does not clearly indicate it is required when the SEND EXPORT STATE PARAMETER="2". 3. When using the SEND EXPORT STATE PARAMETER, the State Parameter ZERO REPORT DEFAULT DIVISION prompt shows "//" even when it's blank. This is not normal behavior since empty fields should not have "//". This is only cosmetic and does not affect functionality of the Zero Report, but it should be fixed. 4. The wording of the Technical Description of the ZERO REPORT DEFAULT DIVISION (#22) field in the SPMP STATE PARAMETERS (#58.41) file is a little confusing by saying it is used for "MbM states that do not dispense controlled substances". It should be clarified to say this is used when a state has the State Parameter SEND EXPORT STATE PARAMETER set to "2". Resolution: ----------- 1. The ZERO REPORT DEFAULT DIVISION State Parameter is now required when the SEND EXPORT STATE PARAMETER="2". 2. The Help Text for the ZERO REPORT DEFAULT DIVISION State Parameter has been updated for clarity. It now displays the following: "Enter the Default Division that is used for the Zero Report when the SEND EXPORT STATE PARAMETER field is set to 2 (SEND TO STATE OF PATIENT DELIVERY) for the state." 3. The two forward slashes "//" have been removed when the ZERO REPORT DEFAULT DIVISION State Parameter is empty. 4. The Technical Description of the ZERO REPORT DEFAULT DIVISION State Parameter has been updated for clarity to the users. It now displays the following: "This field is used to specify the Default Division from file 59 OUTPATIENT SITE that provides the Pharmacy DEA # that will be populated into the Zero Report. When the SEND EXPORT STATE PARAMETER field is set to 2 (SEND TO STATE OF PATIENT DELIVERY) for the state, this field must be populated in addition to parameter ZERO REPORT ASAP VERSION in order to generate a Zero Report. Zero Reports are created when there are no controlled substances to report to the state for the reporting period. Technical Resolution: --------------------- 1. The ZERO REPORT DEFAULT DIVISION (#22) field in the SPMP STATE PARAMETERS (#58.41) file has been updated to be required. 2. The Help Text was updated for the State Parameter field, ZERO REPORT DEFAULT DIVISION (#22), in the SPMP STATE PARAMETERS file (#58.41). 3. The ZERODIV^PSOSPMSP API was updated to check if the PSOZRDIV variable is null before setting DIR("B"). This will remove the two forward slashes (i.e. "//") if the parameter is null. 4. The Technical Description was updated for the State Parameter field, ZERO REPORT DEFAULT DIVISION (#22), in the SPMP STATE PARAMETERS file (#58.41). Test Sites: ----------- Meds by Mail Central Arkansas HCS (Little Rock, AR) SNOW Change Order #: -------------------- Meds by Mail - CHG0395561 Little Rock - CHG0393942 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 2 minutes to install. For this installation there are no options that are required to be disabled. 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 PSO*7.0*724. 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 PSO*7.0*724. 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. 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 routine in a mail message using the Backup a Transport Global [XPD BACKUP] menu option from the Kernel Installation and Distribution System Menu and selecting the Installation Menu. The back-out plan is to restore the routine from the backup created. The message containing the backed-up routine 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 routine onto the VistA System. If the patch was backed up for the build, from the Kernel Installation and Distribution System Menu, select the Installation Menu. Select the Install Package(s) option and choose the patch (PSO*7.0*724b) to install. 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 confirming the checksums have been returned to the pre-patch value using CHECK1^XTSUMBLD. It can also be verified by printing the first 2 lines of the PSO routine(s) contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the routine(s) contained in this patch have been backed out, the Second line of each routine will no longer contain the designation of patch PSO*7.0*724. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOSPML0 Before:B129300399 After:B129636646 **408,451,625,630,696,724** Routine Name: PSOSPMSP Before:B156853075 After:B157161476 **408,451,625,630,696,724** Routine list of preceding patches: 696 ============================================================================= User Information: Entered By : Date Entered : MAY 03, 2023 Completed By: Date Completed: AUG 28, 2023 Released By : Date Released : AUG 29, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT