$TXT Created by CASTLE,JOHN at INOCACHE.FO-BIRM.MED.VA.GOV (KIDS) on Monday, 03/03/08 at 15:45 ============================================================================= Run Date: AUG 20, 2008 Designation: PSS*1*94 Package : PSS - PHARMACY DATA MANAGEMENT Priority: Mandatory Version : 1 SEQ #122 Status: Released Compliance Date: OCT 06, 2008 ============================================================================= Associated patches: (v)PSS*1*59 <<= must be installed BEFORE `PSS*1*94' (v)PSS*1*88 <<= must be installed BEFORE `PSS*1*94' (v)PSS*1*113 <<= must be installed BEFORE `PSS*1*94' (v)PSS*1*118 <<= must be installed BEFORE `PSS*1*94' Subject: PHARMACY CHANGES TO SUPPORT CPRS GUI V27 AND IMR PHASE III Category: - Input Template - Routine - Enhancement (Mandatory) Description: ============ **WARNING** This patch must be installed immediately before the main Computerized Patient Record System (CPRS) GUI v27 host file OR_PSJ_PSO_27.KID. It is recommended that PSS*1.0*94 not be installed until the site is ready to install the CPRS GUI v27 host file. 1. In support of the project Inpatient Medications Requirements for the Special Focus Group Initial Request Analysis (IMR) Phase III, two changes have been made in the input template PSSJ SCHEDULE EDIT. First, if the schedule type is continuous and it is an odd schedule, the system will no longer allow the entry of administration times. Continuous, non-odd schedules will still require administration times. 2. The second IMR change for the input template is if the schedule type is on-call, the system will no longer require a frequency. This will address remedy ticket HD131460. 3. In support of the CPRS GUI v27 release, the validation of schedules from the GUI has been modified. The change was to allow day-of-week schedules to be entered in the format: day@schedule. Schedule, in this case, is an already defined schedule such as BID. So, now a day-of-week schedule may be entered as MO-WE-FR@BID to signify you want to use the BID administration times on Monday, Wednesday and Friday. 4. In support of CPRS GUI v27, a modification has been made to the list of available Medication Routes sent back to CPRS from Inpatient Pharmacy when using the IV Dialog. If there is one orderable item in the order, Inpatient Pharmacy will return any default med route that may be defined in the PHARMACY ORDERABLE ITEM file #50.7 along with any other med routes defined for the DOSAGE FORM file #50.606. Duplicate entries will be removed. If there is more than one orderable item in the order, Inpatient Pharmacy will return a list of the common med routes that match all orderable items. 5. In support of CPRS GUI v27, remedy ticket, HD220080 - "^ in the Schedule field" was addressed. Problem: -------- Users are allowed to include an "^" in the schedule when placing an order in CPRS GUI v27. Resolution: ----------- Routine PSSGSGUI will be modified to disallow an "^" in the text of a schedule. 6. The routine PSS0088 is being deleted with this patch. The routine was part of patch PSS*1.0*88, and was used simply as a tally routine to identify medication routes that needed to be reviewed when the functionality of PSS*1.0*88 was installed. The tally routine's functionality is no longer necessary, so the routine will be deleted. 7. In support of CPRS GUI v27, the array of schedules from the ADMINISTRATION SCHEDULE file #51.1 that is returned to CPRS for schedule selection on an order is being modified. Currently, a site can have multiple schedules with the same name for the same package. The array of schedules presented for selection in CPRS GUI v26 only takes the schedule with the lowest IEN number in the ADMINISTRATION SCHEDULE file #51.1 if a duplicate exists. With the changes in CPRS GUI v27, if there is a duplicate schedule, and if one of them contains ward-specific admin times for the ward location of the patient, the schedule returned for inclusion in the array of selectable schedules in CPRS will be the one with the ward- specific admin times. If no duplicate has ward-specific admin times for the ward location of the patient, the schedule with the lowest IEN number will be returned. If both (or more than one) duplicate schedules have ward-specific admin times for the ward location of the patient, the schedule with the lowest IEN number in the ADMINISTRATION SCHEDULE file #51.1 will be the schedule in the array returned to CPRS. Associated PSIs: ================ N/A Associated Remedy Tickets: ========================== HD131460 - On-Call Schedule Requires a Frequency HD220080 - ^ in the Schedule field Associated NSRs: ================ N/A Associated E3Rs: ================ N/A Test Sites: =========== Charleston, SC Cleveland, OH Heartland East Hudson Valley HCS, NY Loma Linda, CA Northern California HCS, CA Palo Alto HCS, CA Philadelphia, PA San Diego, CA Tampa, FL Documentation Retrieval: ======================== Sites may retrieve documentation in one of the following ways: 1. The preferred method is to FTP the files from download.vista.med.va.gov, which will transmit the files from the first available FTP server. 2. Sites may also elect to retrieve documentation directly from a specific server as follows: Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov 3. Documentation can also be retrieved from VISTA Documentation Library (VDL) on the Internet at the following address, http://www.va.gov/vdl. The documentation distribution includes: FILENAME DESCRIPTION PSS_1_TM_R0808.PDF Pharmacy Data Management Technical Manual/ Security Guide PSS_1_P94_TM_CP.PDF Pharmacy Data Management Technical Manual/ Security Guide Change Pages PSS_1_UM_R0808.PDF Pharmacy Data Management User Manual PSS_1_P94_UM_CP.PDF Pharmacy Data Management User Manual Change Pages PSJ_5_PSO_7_PSS_1_RN.PDF Pharmacy Changes to Support CPRS GUI v27 Release Notes Installation Instructions: ========================== This patch can be installed with users on the system. Installation will take less than 1 minute. Suggested time to install: non-peak requirement hours. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. From the Kernel Installation & Distribution System menu, select the Installation menu. 3. From this menu, you may select to use the following options (when prompted for INSTALL NAME, enter PSS*1.0*94): a. Backup a Transport Global - this option will create a backup message of any routines exported with the patch. It will NOT backup any other changes such as DDs or templates. b. Compare Transport Global to Current System - this option will allow you to view all changes that will be made when the patch is installed. It compares all components of the patch (routines, DDs, templates, etc.). c. Verify Checksums in Transport Global - this option will ensure the integrity of the routines that are in the transport global. 4. Use the Install Package(s) option and select the package PSS*1.0*94. 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" respond NO. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;PHARMACY DATA MANAGEMENT;**[Patch List]**;9/30/97;Build 26 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSS0088 Before: B6455787 After: Delete Routine Name: PSS51P1 Before: B18714317 After: B19742869 **85,91,108,118,94** Routine Name: PSS51P2 Before: B48310663 After: B49298593 **85,112,118,88,94** Routine Name: PSSGSGUI Before: B19690697 After: B24433132 **12,27,38,44,56,59,94** Routine Name: PSSJORDF Before: B11344791 After: B36649764 **5,13,34,38,69,113,94** Routine Name: PSSSCHED Before: n/a After: B15804053 **94** ============================================================================= User Information: Entered By : CRUMLEY,JAMIE Date Entered : APR 18, 2005 Completed By: FARMER,LINDA Date Completed: AUG 19, 2008 Released By : VECE,VIRGINIA Date Released : AUG 20, 2008 ============================================================================= Packman Mail Message: ===================== $END TXT