============================================================================= Run Date: APR 11, 2005 Designation: PX*1*151 Package : PX - PCE PATIENT CARE ENCOUNTER Priority: Mandatory Version : 1 SEQ #121 Status: Released Compliance Date: MAY 12, 2005 ============================================================================= Associated patches: (v)PX*1*147 <<= must be installed BEFORE `PX*1*151' Subject: RSC - PCE RESTRICTING STOP CODES Category: - Routine - Enhancement (Mandatory) - Informational Description: ============ ****** A L E R T ****** Prior to installing the host file, it is strongly recommended that sites run the following reports - SD CLN STOP CODE REP... Non-Conforming Clinics Stop Code Report ECX CLN STOP REP... DSS Identifier Non-Conforming Clinics Report Run the reports, selecting the Active Clinics. It is highly recommended that all non-conforming clinics be corrected prior to installing the host file. Although it is not absolutely necessary to correct these clinics before installation, use of clinics with non-conforming stop codes will not be permitted after the installation. ****** ********* ****** Introduction ============ The Deputy Director of Health Administration Center (HAC) DSS, requested enhancements to VistA to implement an electronic means of restricting medical centers from entering secondary DSS stop codes, also known as DSS Identifiers, in the primary DSS stop code position and to prevent stations from using stop codes in the secondary position that should be primary only. Technical --------- Patient Care Encounter application was modified to check the clinic associated with an encounter to ensure that its corresponding stop pairs conform to the stop code restriction. The following components were affected:- o Routines PXBAPI1, PXCEVSIT and PXCE were modified to call API, $$CLNCK^SDUTL2 which checks to ensure a clinic has a valid stop code pairs in accordance with restriction type. o PCE was added as a subscriber to IA#4652 to use API $$CLNCK^SDUTL2. Functional ---------- The following options were affected by the restricting stop code project. Users will not be able to select clinics with non-conforming stop codes. PCE Encounter Data Entry and Delete [PXCE ENCOUNTER ENTRY & DELETE] PCE Encounter Data Entry without Delete [PXCE ENCOUNTER ENTRY NO DELETE] PCE Encounter Data Entry - Supervisor [PXCE ENCOUNTER ENTRY SUPER] PCE Encounter Data Entry [PXCE ENCOUNTER DATA ENTRY] Action: AD Add Standalone Enc. Test Sites ---------- Cheyenne, WY Little Rock, AR Minneapolis, MN Portland, OR ROUTINE SUMMARY: ================ The following is a list of the routine(s) included in this patch. The second line of each of these routine(s) will look like: ;;1.0;PCE PATIENT CARE ENCOUNTER;**[patch list]**;Aug 12, 1996 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== ========== PXBAPI1 8718447 8965151 1,9,23,56,104 111,113,122,116,130,147,151 PXCE 11539890 11857361 25,47,52,64,75 78,147,151 PXCEVSIT 6845646 7151169 9,23,70,116,147 151 SOFTWARE AND DOCUMENTATION RETRIEVAL ==================================== The software for this patch is not being distributed through the National Patch Module. This patch is being distributed as a host file. The host file is a multi-package build containing four (4) KIDS builds. Host file name: RSC_2_0.KID Multi-Package Build: RSC 2.0 Builds: SD*5.3*380 PX*1.0*151 EC*2.0*65 ECX*3.0*72 Sites may retrieve the software and documentation directly using FTP from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Albany: ftp.fo-albany.med.va.gov Hines: ftp.fo-hines.med.va.gov Salt Lake City: ftp.fo-slc.med.va.gov The following files will be available: File Name Description --------- ----------- RSC_2_0.KID Host file containing KIDS software distribution DSS_3_FY2005_UM.PDF DSS User Manual EC_GUI_UM.PDF EC GUI User Manual PXTM.PDF PCE Technical Manual PXUM.PDF PCE User Manual SUPV.PDF Scheduling User Manual Supervisor Menu * Note: Use ASCII mode when transferring the .KID file. Use Binary mode when transferring the .PDF files. The .PDF files can be read on a PC using the Adobe Acrobat Reader program. INSTALLATION INSTRUCTIONS: ========================= This patch can be installed with users on the system, however it should be installed during off hours to minimize disruption to users. Installation will take less than 5 minutes. Note: The following is a list of REQUIRED builds for this multi-package distribution. KIDS will not allow the installation of this patch without the prior installation of them. EC*2.0*54 EC*2.0*55 ECX*3.0*60 PX*1.0*147 SD*5.3*168 SD*5.3*303 1. Download the KIDS file RSC_2_0.KID from the ANONYMOUS.SOFTWARE directory of either Albany, Hines or the Salt Lake OIFO to the appropriate directory on your system. 2. Use LOAD A DISTRIBUTION option on the KIDS INSTALLATION menu, and enter: RSC_2_0.KID 3. Review your mapped set. If any of the routines listed in the ROUTINE SUMMARY section are mapped, they should be removed from the mapped set at this time. 4. From the Kernel Installation and Distribution System Menu, select the Installation menu. 5. From this menu, you may elect to use the following options (when prompted for INSTALL NAME, enter the appropriate patch designation - SD*5.3*380, PX*1.0*151, EC*2.0*65, or ECX*3.0*72. 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 allow you to ensure the integrity of the routines that are in the transport global. d. Print Transport Global - this option will allow you to view the components of the KIDS build. 6. Use the Install Package(s) option and select the package RSC 2.0. 7. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//',respond NO. 8. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', respond YES. When prompted to select the options you would like to place out of order, enter the following: ECENTER Event Capture Data Entry ECMGR Event Capture Management Menu ECX SETUP CLINIC Set Up for DSS Clinic Information PXCE ENCOUNTER DATA ENTRY PCE Encounter Data Entry PXCE ENCOUNTER ENTRY SUPER PCE Encounter Data Entry - Supervisor PXCE ENCOUNTER ENTRY & DELETE PCE Encounter Data Entry and Delete PXCE ENCOUNTER ENTRY NO DELETE PCE Encounter Data Entry without Delete SDADDEDIT Add/Edit Stop Codes SDAM APPT MGT Appointment Management SDBUILD Set up a Clinic SDI Check-in/Unsched. Visit SDM Make Appointment SDMULTICLINIC Multiple Clinic Display/Book SDMULTIBOOK Multiple Appointment Booking SDRESTORE Restore Clinic Availability SD INACTIVATE Inactivate a clinic SD REACT Reactivate a Clinic 9. If routines were unmapped as part of step 3, they should be returned to the mapped set once the installation has run to completion. Routine Information: ==================== Routine Name: - PXCEVSIT Routine Checksum: Routine Name: - PXCE Routine Checksum: Routine Name: - PXBAPI1 Routine Checksum: ============================================================================= User Information: Entered By : MORRISON,JENNIFER Date Entered : JUN 17, 2004 Completed By: LAVERTY,TIM Date Completed: APR 08, 2005 Released By : HEUER,CINDY Date Released : APR 11, 2005 ============================================================================= Packman Mail Message: ===================== No routines included