$TXT Created by FRANCE,VENESSA at VMPDEV20.FO-BAYPINES.MED.VA.GOV (KIDS) on Wednesday, 05/21/08 at 08:16 ============================================================================= Run Date: JUL 23, 2008 Designation: PSS*1*134 Package : PSS - PHARMACY DATA MANAGEMENT Priority: Mandatory Version : 1 SEQ #121 Status: Released Compliance Date: AUG 23, 2008 ============================================================================= Subject: REPORT OF REFORMATTED LOCAL POSSIBLE DOSES Category: - Routine Description: ============ The Institute of Safe Medication Practices (ISMP) recommends providing a space between the strength and units. Based upon this it was decided to add a space between the strength (dose) and units wherever they are displayed for Possible Dosages. PSS*1.0*78 created an API that other code can call and send the Possible Dose and it will reformat it with a leading zero for values less than one and add a space between the dose and units. The question arose as to whether Local Possible Doses should also be sent through the API to be reformatted. Since Local Possible Dose is a free text field in the data dictionary, this patch will create a report to verify that after the Local Possible Dose is sent through the new API it will be formatted correctly. This patch will create a post install routine that will loop through the Drug file (#50) and get all the Local Possible Doses for each drug and call a copy of the API to reformat it. A report will then be generated that will display the drug ien, drug name, original Local Possible Dose and the reformatted Local Possible Dose. The report will be sent to the holders of the PSNMGR key. Associated Remedy ticket(s): --------------------------------- HD000000067761 Possible Doses - no space between dose and units Associated NSR(s): ------------------ N/A Test Sites: ----------- Charleston Denver Memphis REMEDY OVERVIEW: ============== HD000000067761 Possible Doses - no space between dose and units Problem: -------- Patch PSS*1.0*78 created an API that other code can call and send the Possible Dose and it will reformat it with a leading zero for values less than one and add a space between the dose and units. The question arose as to whether Local Possible Doses should also be sent through the API to be reformatted. Since Local Possible Dose is a free text field in the data dictionary, this patch will create a report to verify that after the Local Possible Dose is sent through the new API it will be formatted correctly. Resolution: ----------- A Post-Install routine will create a report to loop through all Local Possible Doses for all drugs in the Drug file (#50) and reformat them using a copy of the new API developed with patch PSS*1.0*78. **This patch does not actually change any entry in the Local Possible Dosage field in the Drug File.** The report will be sent to the holders of the PSNMGR key and will display the drug ien, drug name, original Local Possible Dose and reformatted Local Possible Dose. Once the report has been received, the holder should review the entire report to identify any drug/dosage combinations that appear to be incorrect. Examples: INFLUENZA VIRUS VACCINE 2004-2005 (#7642) 0.5ML 00.5 ML BUDESONIDE 0.25MG/2ML INH SUSP 2ML (#524) ONE AMPULE (0.25MG/2ML) ONE AMPULE (0.25 MG / 2 ML ) *************************IMPORTANT******************************** *After identifying any drug/dosage combinations that appear to be* *incorrect, please e-mail your findings to Venessa.France@va.gov.* ****************************************************************** ================INSTALLATION INSTRUCTIONS ================= It is not necessary to disable any options. You may install these routines at any time without interruption to users. It should take less than 2 minutes to install this patch. 1. Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 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*134) a. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. b. Print Transport Global - This option will allow you to view the components of the KIDS build. c. 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 components of this patch (routines, DD's, templates, etc.). d. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. 4. Use the Install Package(s) option and select the package PSS*1.0*134. 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 8 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSSP134 Before: n/a After: B10985716 **134** ============================================================================= User Information: Entered By : FRANCE,VENESSA Date Entered : APR 04, 2008 Completed By: HEFFERNAN,COREY Date Completed: JUL 23, 2008 Released By : CAMPBELL,THOMAS Date Released : JUL 23, 2008 ============================================================================= Packman Mail Message: ===================== $END TXT