$TXT Created by ALVIN JR at CMLCACHE.FO-BIRM.DOMAIN.EXT (KIDS) on Monday, 06/23/25 at 14:48 ============================================================================= Run Date: AUG 01, 2025 Designation: PSO*7*772 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #655 Status: Released Compliance Date: AUG 22, 2025 ============================================================================= Associated patches: (v)PSO*7*451 <<= must be installed BEFORE `PSO*7*772' (v)PSO*7*625 <<= must be installed BEFORE `PSO*7*772' (v)PSO*7*705 <<= must be installed BEFORE `PSO*7*772' Subject: SPMP-ADD ASAP DATASETS 4.2A, 4.2B, AND 5.0 Category: - Data Dictionary - Routine - Enhancement (Mandatory) Description: ============ ************************* WARNING ************************************ An environment check runs during the loading of this patch (prior to installation) and during installation to verify there are no custom versions of ASAP definitions 4.2A, 4.2B, 5.0, 4.2AZ, 4.2BZ, or 5.0Z in the STANDARD sub-file (#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4). If custom versions of any of these ASAP definitions are found, the installation is halted. Please submit a Service Now (SNOW) ticket and assign to the SPM.Health.PCS.Sub_1 team, requesting they coordinate with a holder of the PSO SPMP ADMIN Security Key to remove or rename the custom ASAP definition from the SPMP ASAP RECORD DEFINITION file (#58.4). *********************************************************************** To comply with the implementation of the American Society for Automation in Pharmacy (ASAP) Standard this patch will add the ASAP Standard datasets 4.2A, 4.2B, 5.0, 4.2AZ, 4.2BZ, and 5.0Z within the Outpatient Pharmacy v7.0 State Prescription Monitoring Program (SPMP) menu. The patch will also implement any other needed changes to the existing SPMP functionality that will be affected by the addition of the new ASAP datasets. ------------------------------------------------------------------------- Add 4.2A Standard dataset to the SPMP ASAP RECORD DEFINITION FILE (#58.4) ------------------------------------------------------------------------- The 4.2A ASAP definition was added as a STANDARD ASAP DEFINITION to the SPMP ASAP RECORD DEFINITION file (#58.4). The 4.2A ASAP definition has built upon previous ASAP datasets (e.g., 4.1 and 4.2), meaning the VistA ASAP definition will consist of pre-existing data elements, revised data elements, and new data elements. -------------------------------------------------------------------- Add 4.2A Zero Report to the SPMP ASAP RECORD DEFINITION FILE (#58.4) -------------------------------------------------------------------- The ASAP 4.2A Zero Report was added as a STANDARD ASAP DEFINITION to the SPMP ASAP RECORD DEFINITION file (#58.4). The 4.2A Zero Report uses the 4.2A standard as a template when building and processing zero report batches. Add 4.2B Standard dataset to the SPMP ASAP RECORD DEFINITION FILE (#58.4) ------------------------------------------------------------------------- The 4.2B ASAP definition was added as a STANDARD ASAP DEFINITION to the SPMP ASAP RECORD DEFINITION file (#58.4). The 4.2B ASAP definition has built upon previous ASAP datasets (e.g., 4.2 and 4.2A), meaning the VistA ASAP definition will consist of pre-existing data elements, revised data elements, and new data elements. -------------------------------------------------------------------- Add 4.2B Zero Report to the SPMP ASAP RECORD DEFINITION FILE (#58.4) -------------------------------------------------------------------- The ASAP 4.2B Zero Report was added as a STANDARD ASAP DEFINITION to the SPMP ASAP RECORD DEFINITION file (#58.4). The 4.2B Zero Report uses the 4.2B standard as a template when building and processing zero report batches. ------------------------------------------------------------------------ Add 5.0 Standard dataset to the SPMP ASAP RECORD DEFINITION FILE (#58.4) ------------------------------------------------------------------------ The 5.0 ASAP definition was added as a STANDARD ASAP DEFINITION to the SPMP ASAP RECORD DEFINITION file (#58.4). The 5.0 ASAP definition has built upon previous ASAP datasets (e.g., 4.2, 4.2A, and 4.2B), meaning the VistA ASAP definition will consist of pre-existing data elements, revised data elements, and new data elements. ------------------------------------------------------------------- Add 5.0 Zero Report to the SPMP ASAP RECORD DEFINITION FILE (#58.4) ------------------------------------------------------------------- The 5.0 ASAP Zero Report was added as a STANDARD ASAP DEFINITION to the SPMP ASAP RECORD DEFINITION file (#58.4). The 5.0 Zero Report uses the 5.0 standard as a template when building and processing zero report batches. ------------------------------------------------ Remove ability to edit Standard ASAP Definition ------------------------------------------------ A field was added, LOCKED? (58.4001,.07), to the VERSION subfile of the SPMP ASAP RECORD DEFINITION file (#58.4) and will be set to 'YES' so that the ASAP definition is locked from editing when using the View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS] option. The 4.2A, 4.2B, and 5.0 standard datasets and the 4.2AZ, 4.2BZ, and 5.0Z Zero Reports will all be locked upon installation of the patch. The SCREEN field (#101,24) of the PSO SPMP3 MENU protocol has been populated with the following M statement, "I $$ACTIONS^PSOSPML3" which will disable editing actions to a LOCKED ASAP definition when using the View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS] option. ------------------------------------------------------------------------- Export Batch Processing for 4.2A, 4.2B and 5.0 Standard Datasets ------------------------------------------------------------------------- The 4.2A, 4.2B, and 5.0 datasets have new, revised, and existing data elements that will get exported to the state's Prescription Drug Monitoring Program (PDMP) when the following options are executed: Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] View/Export Void Prescriptions [PSO SPMP VOID RX VIEW/EXPORT] View/Export Batch [PSO SPMP BATCH VIEW/EXPORT] Export Batch Processing [PSO SPMP BATCH PROCESSING] Manual Export/Prescription Correction [PSO SPMP MANUAL EXPORT/RX FIX] --------------------------------------------------------------- Export Batch Processing for 4.2AZ, 4.2BZ, and 5.0Z Zero Reports --------------------------------------------------------------- When the SPMP State Parameter ZERO REPORT ASAP VERSION is set to "4.2AZ", "4.2BZ", or "5.0Z", and there are no controlled substance prescriptions to report, one of these new zero report versions will get exported to the state's PDMP when the following options are executed: Scheduled SPMP Data Export [PSO SPMP SCHEDULED EXPORT] View/Export Batch [PSO SPMP BATCH VIEW/EXPORT] Export Batch Processing [PSO SPMP BATCH PROCESSING] --------------------------------- Modify ASAP Customization Feature --------------------------------- The behavior of various customization actions in the View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS] option has been modified as described below: CV Copy Version ---------------- When a custom ASAP definition is created via the CV Copy Version action, a new COPIED FROM ASAP VERSION (#.06) field in the VERSION subfile of the SPMP ASAP RECORD DEFINITION (#58.4) file is set to the ASAP definition from which the new version was copied. This new field is used to identify an ASAP version as a custom ASAP version. When the details of the custom ASAP definitions containing a value in this new field are displayed, segments and elements that have not been customized are displayed without asterisks. Elements and segments that have been customized via the CE Customize Element or CS Customize Segment, respectively, are displayed with asterisks. DC Delete Customization ------------------------ When the DC Delete Customization action is performed on a Custom ASAP Definition containing a value in the new COPIED FROM ASAP VERSION (#.06) field in the VERSION subfile of the SPMP ASAP RECORD DEFINITION (#58.4) file, the action has been modified as described below: Deleting Data Element: When deleting a data element that was a standard element in the source ASAP definition from which the custom ASAP version was copied, the customizations are deleted and the original standard element definition is restored. When deleting a data element that was a standard element in the source ASAP definition from which the custom ASAP version was copied, but was instead added as a new custom data element, the entire data element is deleted and is no longer displayed in the ASAP definition. Deleting Segment: When deleting a segment that was a standard segment in the source ASAP definition from which the custom ASAP version was copied, the customizations are deleted and the original standard segment definition is restored. New custom elements added to the segment are deleted from the segment. When deleting a segment that was a standard segment in the source ASAP definition from which the custom ASAP version was copied, but was instead added as a new custom segment, the entire segment is deleted and is no longer displayed in the ASAP definition. Deleting Version: When deleting a custom ASAP definition, the ASAP definition is deleted and is no longer displayed for selection. Change "Version" to "Ver" in PSO SPMP ASAP DEFINITIONS Screen Title ------------------------------------------------------------------- The Screen Title in the View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS] option has been changed to display the word "Ver" instead of "Version" to accommodate long ASAP definition names, and to avoid truncating the ASAP definition name or the asterisk indicating the definition is a custom copied version. Send/Display Standard ASAP Version Name in TH01 for Custom ASAP Versions ------------------------------------------------------------------------- During SPMP batch transmission and when displayed in the View/Export Description screen, if the value of the "TH01 - Version / Release Number" data element contains an underscore ("_") character, and if the portion of the TH01 value that appears before the underscore character matches a standard, locked ASAP version in the SPMP ASAP RECORD DEFINITION file (#58.4), then only the portion of the TH01 value before the underscore character will be sent and/or displayed Environment Check ------------------ An environment check runs during the loading of this patch (prior to installation) to verify there are no custom versions of ASAP definitions 4.2A, 4.2B, 5.0, 4.2AZ, 4.2BZ, or 5.0Z in the STANDARD sub-file (#58.4001) of the SPMP ASAP RECORD DEFINITION file (#58.4). If custom versions of any of these ASAP definitions are found, the installation is halted and the installer is instructed to contact a holder of the PSO SPMP ADMIN Security Key to have the custom ASAP definitions removed or renamed prior to installing the patch. 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 ------------------ ------------------- -------------------- VERSION subfile COPIED FROM ASAP VERSION (.06) New (#58.4001) of the LOCKED? (.07) New SPMP ASAP RECORD DEFINITION (#58.4) 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 ------------- -------------------- PSO SPMP3 MENU Modified Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- PSO SPMP VIEW LIST LIST TEMPLATE (409.61) Modified ASAP DEFINITION Remote Procedure Calls: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- Blood Bank Team Coordination: ---------------------------- N/A New Service Requests (NSRs): ----------------------------- NSR 20230218 - SPMP - Support for ASAP Versions 4.2a, 4.2b, 5.0. Patient Safety Issues (PSIs): ----------------------------- N/A Test Sites: ---------- Jesse Brown VAMC, Chicago, IL Cleveland VAMC, Cleveland, OH Manchester VAMC, Manchester, NH Omaha VAMC, Ohama, NE Portland VAMC, Portland, OR Test Sites - SNOW Change Orders: ----------------------------------- Chicago - CHG0619154 Cleveland - CHG0619070 Manchester - CHG0618448 Omaha - CHG0619160 Portland - CHG0618466 Documentation Retrieval Instructions: ------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Title File Name ------------------------------------------------------------------ Manager's User Manual PSO_7_0_P772_MAN_UM.DOCX PSO_7_0_P772_MAN_UM.PDF Technical manual Security guide PSO_7_0_P772_TM.DOCX PSO_7_0_P772_TM.PDF Deployment, Installation Back-Out PSO_7_0_P772_DIBRG.DOCX and Rollback Guide PSO_7_0_P772_DIBRG.PDF Patch Installation: ------------------- See the Deployment, Installation, Back-Out and Rollback Guide (DIBRG) for this patch for detailed installation instructions. Post-Installation: ------------------------------- See the Deployment, Installation, Back-Out and Rollback Guide (DIBRG) for this patch for post-installation instructions. Back-Out/Roll Back Plan: ------------------------ The backout plan is provided as part of the Deployment, Installation, Back-Out and Rollback Guide (DIBRG) for this patch. Refer to section 5, Back-Out Procedure. Routine Information: ==================== The second line of each of these routines now looks like: ;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;9/30/97;Build 105 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSO772EC Before: n/a After: B8100141 **772** Routine Name: PSO772P0 Before: n/a After:B132147116 **772** Routine Name: PSO772P1 Before: n/a After:B151585732 **772** Routine Name: PSO772P10 Before: n/a After:B129691525 **772** Routine Name: PSO772P11 Before: n/a After:B123233802 **772** Routine Name: PSO772P12 Before: n/a After: B64105982 **772** Routine Name: PSO772P13 Before: n/a After:B137235233 **772** Routine Name: PSO772P14 Before: n/a After:B141299867 **772** Routine Name: PSO772P15 Before: n/a After:B114017141 **772** Routine Name: PSO772P16 Before: n/a After: B88651155 **772** Routine Name: PSO772P17 Before: n/a After:B131841754 **772** Routine Name: PSO772P18 Before: n/a After:B124805690 **772** Routine Name: PSO772P19 Before: n/a After:B124683543 **772** Routine Name: PSO772P2 Before: n/a After:B125863222 **772** Routine Name: PSO772P20 Before: n/a After:B142966689 **772** Routine Name: PSO772P21 Before: n/a After:B124145359 **772** Routine Name: PSO772P22 Before: n/a After:B141836702 **772** Routine Name: PSO772P23 Before: n/a After:B140593060 **772** Routine Name: PSO772P24 Before: n/a After: B29903192 **772** Routine Name: PSO772P25 Before: n/a After:B118272032 **772** Routine Name: PSO772P26 Before: n/a After:B140404244 **772** Routine Name: PSO772P27 Before: n/a After:B142271228 **772** Routine Name: PSO772P28 Before: n/a After:B139884660 **772** Routine Name: PSO772P3 Before: n/a After:B115015438 **772** Routine Name: PSO772P4 Before: n/a After: B44407612 **772** Routine Name: PSO772P5 Before: n/a After:B137050610 **772** Routine Name: PSO772P6 Before: n/a After:B139243328 **772** Routine Name: PSO772P7 Before: n/a After:B127582764 **772** Routine Name: PSO772P8 Before: n/a After:B135287828 **772** Routine Name: PSO772P9 Before: n/a After:B150911076 **772** Routine Name: PSO772PI Before: n/a After: B16216842 **772** Routine Name: PSOASAP Before: B88963366 After: B88865869 **451,496,625,772** Routine Name: PSOASAP0 Before:B178203552 After:B167408199 **408,451,496,504,625,630,659, 705,772** Routine Name: PSOASAP1 Before: n/a After: B11043884 **772** Routine Name: PSOASAP2 Before: n/a After: B42656303 **772** Routine Name: PSOSPMA3 Before:B171617912 After:B194309910 **451,625,772** Routine Name: PSOSPMB3 Before: B46180556 After: B60589074 **451,772** Routine Name: PSOSPML3 Before: B58248609 After: B69444134 **408,451,625,772** Routine Name: PSOSPMU0 Before: B33044815 After: B44818174 **451,625,772** Routine Name: PSOSPMU2 Before: B20209131 After: B66763079 **451,625,772** Routine Name: PSOSPMU3 Before:B138473139 After:B197984134 **451,625,772** Routine Name: PSOSPMUT Before:B206058275 After:B207897041 **408,451,549,625,630,772** Routine list of preceding patches: 705 ============================================================================= User Information: Entered By : Date Entered : AUG 28, 2024 Completed By: Date Completed: AUG 01, 2025 Released By : Date Released : AUG 01, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT