============================================================================= Run Date: JUL 15, 2004 Designation: EC*2*54 Package : EC - EVENT CAPTURE Priority: Mandatory Version : 2 SEQ #57 Status: Released Compliance Date: AUG 15, 2004 ============================================================================= Associated patches: (v)EC*2*49 <<= must be installed BEFORE `EC*2*54' (v)EC*2*50 <<= must be installed BEFORE `EC*2*54' (v)PX*1*130 <<= must be installed BEFORE `EC*2*54' (v)SD*5.3*325 <<= must be installed BEFORE `EC*2*54' Subject: COMBAT VETERAN PHASE II - EVENT CAPTURE Category: - Routine - Data Dictionary - Enhancement (Mandatory) Description: ============ ***********************************NOTE*************************************** This patch does NOT conflict with CoreFLS and can be installed at CoreFLS sites. ****************************************************************************** PATCH OVERVIEW The Chief Business Office (CBO) is requesting modifications to several Veterans Health Information Systems and Technology Architecture (VistA) packages to support implementation of VHA Directive 2002-049 - "Combat Veterans Are Eligible For Medical Services For 2-Years After Separation From Military Service Notwithstanding Lack Of Evidence For Service Connection", which iterates VA's policy to provide medical care and other medical services to combat veterans despite the absence of proof of service connection. Software to support the Combat Veteran (CV) initiative is being developed and introduced in a phased implementation strategy. The reason for this type of deployment is due to the complexity of the functionality and the number of product line dependencies. Phase I: Combat Veteran Interim Solution (CVIS) was a VistA only solution that involved development in the Integrated Billing (IB) and Registration/Enrollment product lines. It provided the logic to identify those veterans who met the criteria for the combat veteran eligibility and provided billing reports cross-referenced against this identifier to aid in the copayment billing process. Phase II of this initiative will involve multiple product lines and additional VistA only development. The main goals of Phase II will be to fully automate the copayment billing processing of combat vets based on episode of care by providing the appropriate questions at check-out as supplied by CPRS. Product lines that have a stake in Phase II development include Enrollment/Registration (VistA), IB, Outpatient Pharmacy, Consolidated Mail Outpatient Pharmacy (CMOP), CPRS/TIU, Patient Care Encounter (PCE), Ambulatory Care, Event Capture, Scheduling and PTF. The National Patient Care Database (NPCD) will also require modifications to capture workload reporting. The patches are listed below in the order that they must be installed. It should be noted all patches with the exception of the PIMS host file have been previously released and the installation status of those patches should be validated at your site prior to installation the PIMS build: Outpatient Pharmacy: PSO*7*157 - Release Date, May 13, 2004 PSX*2*50 - Release Date, May 13, 2004 CPRS: OR*3.0*190 - Release Date, July 12, 2004 Integrated Billing: IB*2.0*247 - Release Date, June 9, 2004 PCE/PTF/Event Capture/Scheduling PIMS Host file PX*1.0*130 SD*5.3*325 DG*5.3*565 EC*2.0*54 Product Features There are three main areas addressed by this enhancement: a. Identification/Notification of a CV Status veteran seeking medical care o The clinical applications shall obtain the CV Status for those veterans who qualify as such per the directive o The CV Status identification shall be displayed to the appropriate audience (pharmacist, clinician providing care, intake personnel, schedulers, etc.) o Provider shall be able to identify whether care provided CV veteran was for a condition potentially related to combat service in the same manner as identification of exposure related care; care for SC conditions, etc. b. Assistance in the communication of a treatment being determined as Combat Related o Provide a means for the billing and pharmacy software package to identify these patients and services provided care for a combat related condition c. Automatically precludes inpatient and outpatient medical care, prescription and Long-term care copayments for CV Status veterans whose treatment/service has been deemed combat related by provider or unless changed by pharmacist. Patch EC*2*54 addresses the addition of a new classification, Combat Veteran, to the Event Capture package. The Roll-n-scroll and GUI application were both updated. This patch is contained in the MULTIPLE BUILD DISTRIBUTION: COMBAT VET PHASE II PIMS 1.0 COMBAT VETERAN ADDITION TO ECS I. Overview This patch updates EVENT CAPTURE v2.0 to handle the new classification, Combat Veteran. A 'Yes' or 'No' response will be indicated when a procedure event is related to a Combat Veteran status. The following patches must be installed in order for the Combat Veteran classification to function correctly - SD*5.3*325 and PX*1*130. The options that will be affected by this installation are EVENT CAPTURE DATA ENTRY and NIGHTLY DATA FEED TO PCE. II. Functional If a veteran has reported having been a Combat Veteran, then the Event Capture software will ask the user to indicate if the procedure is related to Combat Veteran. The system will prompt the user with 'Was treatment related to Combat Veteran?'. The user can then choose to respond with Y-Yes or N-No. This change affects all four options of Event Capture roll-n-scroll and the two ECS GUI data entry options. Roll-n-scroll options Enter/Edit Patient Procedures Batch Enter Data by Patient Data Entry (Batch) by Procedure Multiple Dates/Multiple Procedures Data Entry ECS GUI options Data Entry by Patient Data Entry by Procedure III. Technical o A new field, COMBAT VETERAN (#40) was added to the EVENT CAPTURE PATIENT file (#721) to capture the classification Combat Veteran. The data is stored at "P;11" - the 11th piece of the P node. o The 20th piece of the PCE DATA FEED field (#30) now contains the Combat Veteran value. The Technical description of this field was updated to list each piece of data that comprise the PCE data feed. o Sixteen (16) routines and two (2) input templates were modified. The templates EC CREATE PATIENT ENTRY and EC FILE PCE NODE are used within ListMan for filing the 'P' and 'PCE' nodes in file 721. o Delphi ufrmEditPatientProc and urfmEditProcPatients2 were modified to add the new classification in ECS GUI. IV. Data Entry Example o Below is an example of Combat Veteran using the VISTA roll-n-scroll ENTER/Edit Patient Procedures option. Select Event Capture Data Entry Option: ENTER/Edit Patient Procedures Event Capture Locations: 1. ALBANY 2. ALBANY OPC 3. TROY Select Number: 1 Select DSS Unit: SEND TO PCE M3211 Location: ALBANY DSS Unit: SEND TO PCE Select Patient: '735 HUNTER,RICK B 4-25-65 000007654 YES SC VETERAN KRUSHER,BETTY Warning : You have selected a test patient. Enrollment Priority: GROUP 6 Category: IN PROCESS End Date: Combat Vet Status: ELIGIBLE End Date: 12/30/2005 Enter Date and Time of Procedure: NOW// (NOV 21, 2003@13:06) This patient is an Outpatient Categories within SEND TO PCE: 1. PLWTESTING 2. SAM 3. LOCAL ONE Select Number: 1 Category: PLWTESTING Enter Procedure: 1 21046 REMOVE MANDIBLE CYST COMPLEX (#21046) ENTERING A NEW PROCEDURE FOR HUNTER,RICK B ... LOCATION: ALBANY SERVICE: SOCIAL WORK SECTION: SOCIAL WORK CATEGORY: PLWTESTING PROCEDURE: 21046 REMOVE MANDIBLE CYST COMPLEX (#21046) Modifier: Volume: 1// ORDERING SECTION: SOCIAL WORK// ASSOCIATED CLINIC: SOCIAL WORK// Primary ICD-9 Code: V50.1 PLASTIC SURGERY NEC ...OK? Yes// (Yes) Secondary ICD-9 Code: --- Classification --- [Required] Was treatment related to Combat? YES// Was treatment related to Military Sexual Trauma? YES Was treatment related to Head and/or Neck Cancer? NO// Provider: OLINGER,BRIAN Occupation: Physicians (M.D. and D.O.) Specialty: Physician/Osteopath Subspecialty: Addiction Medicine Provider #2: Press RETURN to continue: o After the recurring EC NIGHT 'Nightly Data Feed to PCE' option has run (this job is queued to run every night and transfers ECS records to PCE), the PCE Encounter Viewer (PXCE ENCOUNTER VIEWER) option may be used to confirm that the new classification was sent to PCE. Test Sites ---------- Altoona, PA Sioux Falls, SD Madison, WI West LA 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: ;;2.0; EVENT CAPTURE ;**[patch list]**;8 May 96 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== ========== ECBEN 10506836 10525566 4,5,10,17,42,54 ECBEN1B 11339823 11474793 4,5,10,13,17,23,41,42,50,54 ECBEN2U 13837760 14203624 4,5,7,10,17,18,23,42,47,54 ECBENF 7049894 6770341 4,5,13,17,18,23,42,54 ECBEP 10824330 10855714 4,5,10,17,42,54 ECBEP1B 18442955 18509803 1,4,5,10,13,17,18,42,47,54 ECBEP2A 13266079 13428396 4,5,10,13,17,18,23,33,41,42,54 ECBEPF 6223579 6313225 4,5,13,17,18,23,42,54 ECEFPAT 11547175 11554214 25,32,39,42,47,49,54 ECKILL 9994730 10035771 4,5,10,17,18,23,42,54 ECMLMF 8211644 8373000 5,10,15,13,17,18,23,42,54 ECMLMN 10281031 10304353 5,10,15,13,17,18,23,42,47,54 ECMUTL1 10164359 10722024 5,10,15,13,17,23,41,42,50,54 ECPCEU 9234966 9129994 4,5,7,10,17,18,23,42,54 ECUERPC1 8693700 9193631 25,33,42,46,47,54 ECUTL1 6479960 7596050 10,13,17,42,54 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: COMBAT_VET_PHASE_II_PIMS.KID Multi-Package Build: COMBAT VET PHASE II PIMS 1.0 Builds: PX*1.0*130 : SD*5.3*325 : DG*5.3*565 : EC*2.0*54 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 --------- ----------- COMBAT_VET_PHASE_II_PIMS.KID Host file containing KIDS software distribution EC2_0P54.EXE Event Capture GUI Change Pages to the following documentations are included in the files below. DG_53_P565_UM.PDF PIMS V5.3 User Manual EC_2_P54_CB.PDF Event Capture V2.0 Cook Book EC_2_P54_UM.PDF Event Capture V2.0 User Manual PX_1_P130_TM.PDF PCE V1.0 Technical Manual PX_1_P130_UM.PDF PCE V1.0 User Manual SD_53_P325_TM.PDF PIMS V5.3 Technical Manual SD_53_P325_UM.PDF PIMS V5.3 User Manual * Note: Use ASCII mode when transferring the .KID file. Use Binary mode when transferring the .EXE and .PDF files. The .PDF files can be read on a PC using the Adobe Acrobat Reader program. INSTALLATION INSTRUCTIONS: ========================= ** It is recommended that this patch NOT be installed less ** ** than seven days before AmbCare's monthly close-out ** This patch can be installed with users on the system, however it should be installed during off hours to minimize disruption to users. This patch affects the check-out process and must be installed when the SCDX AMBCAR NIGHTLY XMIT background job is not running. Installation will take less than 10 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. DG*5.3*497 DG*5.3*510 DG*5.3*524 DG*5.3*576 DG*5.3*590 DG*5.3*602 EC*2.0*49 EC*2.0*50 SD*5.3*244 SD*5.3*254 SD*5.3*258 SD*5.3*293 PX*1.0*96 PX*1.0*112 PX*1.0*115 PX*1.0*116 PX*1.0*121 PX*1.0*122 PX*1.0*117 1. Download the KIDS file COMBAT_VET_PHASE_II_PIMS.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: COMBAT_VET_PHASE_II_PIMS.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 - PX*1.0*130, SD*5.3*325, DG*5.3*565, EC*2.0*54): 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 COMBAT VET PHASE II PIMS 1.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: SCDX AMBCAR NIGHTLY XMIT Ambulatory Care Nightly Transmission to NPCDB SDAM APPT MGT Appointment Management SDAM APPT CHECK IN/OUT Appointment Check-in/Check-out SDADDEDIT Add/Edit Stop Codes SDAPP Appointment Menu SDI Check-in/Unsched. Visit SDM Make Appointment PXCE ENCOUNTER DATA ENTRY PCE Encounter Data Entry PXCE ENCOUNTER ENTRY & DELETE PCE Encounter Data Entry & Delete PXCE ENCOUNTER ENTRY NO DELETE PCE Encounter Entry Without Delete PXCE ENCOUNTER ENTRY SUPER PCE Encounter Data Entry - Supervisor ECENTER Event Capture Data Entry EC NIGHT Nightly Data Feed to PCE When prompted to select the protocols you would like to place out of order, enter the following: SDAM PCE EVENT Process PCE Event Data PXK VISIT DATA EVENT VISIT RELATED DATA PXCA DATA EVENT PCE Device Interface Module's Data Event 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. 10. The pre and post install routines SD53325 and SD53325A can be deleted after receiving the message that the SD*5.3*325 post init has run to completion. Routine Information: ==================== Routine Name: - ECBEN Routine Checksum: Routine Name: - ECBEN1B Routine Checksum: Routine Name: - ECBEN2U Routine Checksum: Routine Name: - ECBENF Routine Checksum: Routine Name: - ECBEP Routine Checksum: Routine Name: - ECBEP1B Routine Checksum: Routine Name: - ECBEP2A Routine Checksum: Routine Name: - ECBEPF Routine Checksum: Routine Name: - ECEFPAT Routine Checksum: Routine Name: - ECKILL Routine Checksum: Routine Name: - ECMLMF Routine Checksum: Routine Name: - ECMLMN Routine Checksum: Routine Name: - ECMUTL1 Routine Checksum: Routine Name: - ECPCEU Routine Checksum: Routine Name: - ECUERPC1 Routine Checksum: Routine Name: - ECUTL1 Routine Checksum: ============================================================================= User Information: Entered By : MORRISON,JENNIFER Date Entered : OCT 28, 2003 Completed By: OLINGER,BRIAN Date Completed: JUL 14, 2004 Released By : STRICKLAND,JOAN C Date Released : JUL 15, 2004 ============================================================================= Packman Mail Message: ===================== No routines included