$TXT Created by FINNIE,DONALD R at CMLCACHE.FO-BIRM.MED.VA.GOV (KIDS) on Tuesday, 12/09/08 at 14:05 ============================================================================= Run Date: MAR 18, 2009 Designation: PSB*3*28 Package : PSB - BAR CODE MED ADMIN Priority: Mandatory Version : 3 SEQ #35 Status: Released Compliance Date: APR 18, 2009 ============================================================================= Associated patches: (v)PSB*3*25 <<= must be installed BEFORE `PSB*3*28' (v)PSB*3*43 <<= must be installed BEFORE `PSB*3*28' Subject: BCMA MANAGING SCANNING FAILURES (BCMA MSF) Category: - Other - Routine - Enhancement (Mandatory) - Data Dictionary Description: ============ ATTENTION: This patch includes a new Graphical User Interface (GUI) executable file. Installation of this GUI is required immediately after the KIDS install for the Patch to function. WARNING FOR ALL SITES CURRENTLY USING WMA (Wireless Medication Administration) From CareFusion Installation of BCMA Patch PSB*3.0*28 may cause your WMA application to stop functioning as you would expect it to. In order for the WMA devices to work properly with PSB*3.0*28 installed, you must contact CareFusion, the WMA vendor, to obtain the most current version of the WMA software. Please test this patch thoroughly in your TEST environment before installing into PRODUCTION. If you encounter any issues with the WMA application, please report them to CareFusion. For retrieval and installation instructions, please see the Client Installation Instructions section. This patch is a component of the Bar Code Medication Administration (BCMA) V. 3.0 Managing Scanning Failures (MSF) project. The main function of PSB*3*28 and the corresponding BCMA GUI software is to document scanning failures during BCMA patient and medication verification. Please see the Release Notes for more details on the following enhancements. 1. Enhancement: Document Unable to Scan events. This patch will enable the user to document Unable to Scan events that occur during BCMA patient and medication verification. The Computerized Patient Record System (CPRS) Medication Order Button does not support Unable to Scan functionality. Administration of Ward Stock IV orders is partially supported by Unable to Scan functionality. Users can select Unable to Scan - Create WS, enter a reason for the scanning failure and optional comment, then proceed with the normal ward stock work flow. 2. Enhancement: Send a MailMan message for each Unable to Scan event. When a user documents an Unable to Scan event, a message will be sent to persons who are members of the mail group established via the BCMA Site Parameter's Unable to Scan mail group field setting. This message will also be sent to the user submitting the Unable to Scan event documentation. 3. Enhancement: Add two new Unable to Scan Reports. The Unable to Scan Detailed and Summary reports provide BCMA wristband and Medication scanning failure data. These reports can only be executed by persons holding the PSB UNABLE TO SCAN security key. Users can specify a variety of selection criteria at report run time. These new reports are only available through the BCMA GUI. 4. Enhancement: Added report enhancements to the MSF Unable to Scan reports to be consistent with other BCMA reports. Features include: Added user specified report criteria on report headers; added preview, print (directly to printer), and queuing functionality; added print by Ward functionality; added check boxes on report dialogs to filter ward drop-down list. 5. Enhancement: Added Division Filtering to Unable to Scan Reports. The user's division is detected upon login, and used to filter Entire Facility and Nurse Unit options on the Summary Report, and All Patients/Wards option on the Detailed Report. 6. Enhancement: Replaced Take Action on WS with Take Action on Bag. Added Take Action on Bag option to the IV Bag Chronology Window to allow user to take action on Infusing or Stopped bags without having to rescan the IV bag or enter a duplicate Unable to Scan event. This new option applies to both pharmacy IV bags and Ward Stock IV bags. 7. Enhancement: Added a new mode called "Limited Access BCMA" that provides medication administering users the ability to access BCMA without being at the patient's bedside. It allows access to patient records for non-medication administration documentation, review, and reporting purposes, without having to scan patient wristbands or register erroneous Unable to Scan events. Associated New Service Requests: ================================ 20041102 Associated E3Rs: ================ N/A Associated Patient Safety Issues: ================================= N/A Associated Remedy Tickets: ========================== N/A Test Sites: =========== Charleston, SC (Large) Durham, NC (Large) East Orange, NJ (Large/Integrated) Fargo, ND (Medium) Iron Mountain, MI (Small) Loma Linda, CA (Large) Manchester, NH (Medium) Minneapolis, MN (Large) Phoenix, AZ (Large) Pittsburgh HCS, PA (Large) Tampa, FL (Large) Upstate New York HCS (Large/Integrated) Washington, D.C. (Large) West Palm Beach, FL (Large) Server Installation Instructions: ================================= This patch can be loaded with users on the system. Installation will take less than 1 minute. Suggested time to install: non-peak requirement hours. PC Client users should not be accessing the Client Software. 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 patch PSB*3.0*28) 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 patch PSB*3.0*28. 5. When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//" respond NO. 6. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//" respond NO. 7. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//" respond NO. 8. Please refer to the Release Notes for additional set up instructions. Example Installation: ===================== Select Installation Option: INStall Package(s) Select INSTALL NAME: PSB*3.0*28 Loaded from Distribution 12/7/08@18:09:52 => PSB*3*28 This Distribution was loaded on Dec 07, 2008@18:09:52 with header of PSB*3*28 It consisted of the following Install(s): PSB*3.0*28 Checking Install for Package PSB*3.0*28 Install Questions for PSB*3.0*28 Incoming Files: 53.69 BCMA REPORT REQUEST (Partial Definition) Note: You already have the 'BCMA REPORT REQUEST' File. 53.77 BCMA UNABLE TO SCAN LOG Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO// Want KIDS to INHIBIT LOGONs during the install? NO// Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// Enter the Device you want to print the Install messages. You can queue the install by enter a 'Q' at the device prompt. Enter a '^' to abort the install. DEVICE: HOME// COMPUTER ROOM Install Started for PSB*3.0*28 : Dec 07, 2008@18:13:26 Build Distribution Date: Dec 07, 2008 Installing Routines: Dec 07, 2008@18:13:26 Running Pre-Install Routine: ^PSBPRE28 Installing Data Dictionaries: Dec 07, 2008@18:13:26 Installing PACKAGE COMPONENTS: Installing SECURITY KEY Installing REMOTE PROCEDURE PSB*3.0*28 ---------------------------------------------------------------------------- Installing OPTION Installing PARAMETER DEFINITION Dec 07, 2008@18:13:26 Updating Routine file... Updating KIDS files... PSB*3.0*28 Installed. Dec 07, 2008@18:13:26 Install Message sent #527646 ---------------------------------------------------------------------------- [------------------------------------------------------------] 100% | 25 50 75 | Complete [------------------------------------------------------------] Install Completed Client Installation Instructions: ================================= The software distribution includes these modified files: FILE NAME DESCRIPTION FILE VERSION BYTES CHECKSUM BCMA.CHM Client help file 237 KB n/a BCMA.EXE Client 3.0.28.72 2,308 KB 6DC2B4DD BCMAPAR.EXE Site parameter 3.0.28.41 1,024 KB E823C20E BCMAPAR.CHM Client help file n/a INFOLIST.TXT Setup information n/a README.TXT Misc. information n/a 1. Prior client compatible with patch: NO 2. Client can be copied instead of installed: YES Note: Use Binary mode to retrieve the .EXE file. To obtain the updated .EXE, use FTP to retrieve PSB3_0P28.EXE (3,075 KB) from one of the following OI Field Offices' ANONYMOUS.SOFTWARE directories: OI Field Office FTP Address Directory Albany ftp.fo-albany.med.va.gov anonymous.software Hines ftp.fo-hines.med.va.gov anonymous.software Salt Lake City ftp.fo-slc.med.va.gov anonymous.software If BCMA is currently running, please exit BCMA. This client installation patch file can be used to upgrade an existing version of BCMA, or can be used for a brand new installation. 1. Double Click on PSB3_0P28.EXE which will launch the InstallShield Wizard. 2. When the InstallShield Wizard Welcome screen is displayed, click "Next". 3. On the Choose Destination Location screen, simply click "Next" If you would like to change the destination folder to one other than default, click "Browse" to navigate to the folder of your choice. Click "Next". 4. On the "Setup Type" Screen select one of the following: a. Typical - installs only the BCMA client program which is necessary for medication administration. b. Complete - installs the BCMA client and the GUI BCMA site parameters definition program. c. Custom - allows you to select which programs to install Typical is selected by default. Click "Next". 5. The InstallShield Wizard Ready to Install the Program screen will display. Click "Install" to proceed with the installation. 6. The InstallShield Wizard Complete screen will be displayed. Click "Finish" and the BCMA installation is now complete. 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: FILE NAME DESCRIPTION ------------------------------------- ----------------------------------- PSB_3_UM_CHAPTERS_1_THRU_4_R0109.PDF GUI User Manual, Chapters 1 thru 4 PSB_3_UM_CHAPTERS_5_THRU_11_R0109.PDF GUI User Manual, Chapters 5 thru 11 PSB_3_TM_R0109.PDF Technical Manual/Security Guide PSB_3_P28_TM_CP.PDF Technical Manual/Security Guide Change Pages PSB_3_MGR_UM_R0109.PDF Manager's User Manual PSB_3_P28_RN.PDF Release Notes Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;BAR CODE MED ADMIN;**[Patch List]**;Mar 2004;Build 9 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSBMLEN1 Before: B45353757 After: B51812368 **3,4,9,11,13,28** Routine Name: PSBMLU Before: B6301609 After: B27638405 **6,11,13,28** Routine Name: PSBO Before: B64731627 After: B72486481 **13,32,2,25,28** Routine Name: PSBO1 Before: B7589446 After: B7501769 **4,13,32,2,43,28** Routine Name: PSBODL1 Before: B38589946 After: B38252588 **5,9,32,28** Routine Name: PSBOSF Before: n/a After:B209435927 **28** Routine Name: PSBOST Before: n/a After:B104649438 **28** Routine Name: PSBPAR Before: B21353739 After: B22807367 **13,28** Routine Name: PSBPRE28 Before: n/a After: B68160 **28** Routine Name: PSBRPC Before: B83859906 After: B87760637 **6,3,4,13,32,28** Routine Name: PSBRPC3 Before: B308923 After: B309069 **6,3,4,16,13,10,32,28** Routine Name: PSBVDLU3 Before: B39144184 After: B91584919 **13,38,28** ============================================================================= User Information: Entered By : JACKSON,TODD Date Entered : FEB 17, 2006 Completed By: FARMER,LINDA Date Completed: MAR 04, 2009 Released By : CONNOLLY,BARBARA Date Released : MAR 18, 2009 ============================================================================= Packman Mail Message: ===================== $END TXT