$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Thursday, 10/16/25 at 09:58 ============================================================================= Run Date: MAR 19, 2026 Designation: PSS*1*268 Package : PSS - PHARMACY DATA MANAGEMENT Priority: Mandatory Version : 1 SEQ #234 Status: Released Compliance Date: APR 19, 2026 ============================================================================= Associated patches: (v)PSS*1*224 <<= must be installed BEFORE `PSS*1*268' (v)PSS*1*262 <<= must be installed BEFORE `PSS*1*268' Subject: ADDITIONAL FIXES FOR FIRST DATABANK (FDB) FRAMEWORK 4.5 UPGRADE Category: - Routine - Data Dictionary Description: ============ This patch includes the following updates required for the upgrade from First Databank (FDB) MedKnowledge Framework (Fwk) version 3.3 to version 4.5. It also includes a fix for a possible undefined error when running the Check PEPS Services Setup [PSS CHECK PEPS SERVICES SETUP] Option. (1) The Dosing Order checks are updated to show General Dosing Range messaging information when applicable. There are some scenarios that information is not displayed. (2) Updates the DESCRIPTION and HELP-PROMPT of the DOSING CHECK FREQUENCY (#11) Field of the ADMINISTRATION SCHEDULE (#51.1) File. (3) Adds a description to the SYNONYM (#51.242) Subfile of the DOSE UNITS (#51.24) File. (4) Fixes an error that sometimes occurs when running the Check PEPS Services Setup [PSS CHECK PEPS SERVICES SETUP] Option, located under the Peps Services [PSS PEPS SERVICES] Menu Option, located under the Pharmacy Data Management [PSS MGR] Menu Option. 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 ------------------ ------------------- -------------------- ADMINISTRATION SCHEDULE DOSING CHECK FREQUENCY Modified (#51.1) (#11) DOSE UNIT (#51.24) SYNONYM (#2) Modified 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: ----------------------- New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. INC38976604 - Unable to convert units "melt" to "milliliter/day" Problem: -------- The Dosing Order checks are updated to show General Dosing Range messaging information when applicable. There are some scenarios where that information should display but does not. Resolution: ----------- Logic is updated for the display of the General Dosing Range messaging. Routine PSSDSEXC in DAILY, removed the conditional on PSSDBCAR ..I $G(PSSDBADJ(PSSDWE5))'="",'PSSDWADJ D ADJUS ;268 I PSSDWE9=5,'$P(PSSDBCAR(PSSDWE5),"^",29) S PSSDWGFB=1 I PSSDWE9=5 S PSSDWGFB=1 ;268 Q 2. INC40266361 - Help prompt of DOSING CHECK FREQUENCY needs update Problem: -------- The DESCRIPTION and HELP-PROMPT of the DOSING CHECK FREQUENCY (#11) Field of the ADMINISTRATION SCHEDULE (#51.1) File needs updated. Resolution: ---------- Updates the DESCRIPTION and HELP-PROMPT of the DOSING CHECK FREQUENCY (#11) Field of the ADMINISTRATION SCHEDULE (#51.1) File. 3. INC40265960 - Description missing in SYNONYM (#51.242) Subfile of the VistA DOSE UNITS (#51.24) File. Problem: -------- There is no description in the SYNONYM (#51.242) Subfile of the DOSE UNITS (#52.41) File. Resolution: ----------- Adds a description to the SYNONYM (#51.242) Subfile of the DOSE UNITS (#51.24) File. 4. INC40265642 - Possible undefined error in the Check PEPS Services Setup [PSS CHECK PEPS SERVICES SETUP] option. Problem: -------- An error sometimes occurs when running the Check PEPS Services Setup [PSS CHECK PEPS SERVICES SETUP] Option, located under the Peps Services [PSS PEPS SERVICES] Menu Option, located under the Pharmacy Data Management [PSS MGR] Menu Option. Resolution: ----------- The logic has been updated. Routine PSSPGXUT: The variable PSSCPSOV has been Newed at PGXCHK+2, and then at PGXCHK+6 it is set to 1, indicating the Check PEPS Services Setup [PSS CHECK PEPS SERVICES SETUP] Option is being executed: S GENE="CYP2C19",(PSSDXC,PSSCPSOV)=1 Routine PSSPGXPR: At line COUNT+10, the following line has been added that checks for the above mentioned PSSCPOSV variable, and if defined, the code skips the next three lines of suppression logic: I $G(PSSCPSOV) G NOSP Test Sites: ----------- VA Eastern Colorado HCS Aurora, CO VA Shreveport HCS Shreveport, LA Test Sites - SNOW Change Order #: --------------------------------- VA Eastern Colorado HCS: CHG0690179 VA Shreveport HCS: CHG0692872 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is not included in this release. Documentation Title File Name --------------------------------------------------------------------- N/A Patch Installation: ------------------- Pre/Post Installation Overview: Pre-Installation Instructions: It is recommended these patches be installed during non-peak hours for Pharmacy Data Management package usage and medication order entry processes in both Computerized Patient Record System (CPRS) and Pharmacy applications, to minimize potential disruption to users. This patch should take less than five minutes to install. There are no menu options to disable. 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. ) 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 PSS*1*268 iii. 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// 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 . ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer . iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer . Post-Installation Instructions: There are no Post-Installation steps. Validation of Installation: --------------------------------- The installation can be verified by printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the build contained in the PSS*1*268 patch has been installed, the first two lines of the routine will contain the designation of this patch in the patch list section on line 2. 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 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 build 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 build from the backup created. 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 routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the build contained in the PSS*1*268 patch has been backed out, the first two lines of the routine will no longer contain the designation of this patch in the patch list section on line 2. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;PHARMACY DATA MANAGEMENT;**[Patch List]**;9/30/97;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSSDSEXC Before:B207462933 After:B207429349 **117,160,178,206,224,268** Routine Name: PSSPGXPR Before:B155353191 After:B153686641 **262,268** Routine Name: PSSPGXUT Before:B106896957 After:B111298039 **262,268** Routine list of preceding patches: 224, 262 ============================================================================= User Information: Entered By : Date Entered : JUN 27, 2025 Completed By: Date Completed: MAR 19, 2026 Released By : Date Released : MAR 19, 2026 ============================================================================= Packman Mail Message: ===================== $END TXT