$TXT Created by BRICKER,DENNIS at DEVFEX.FO-ALBANY.MED.VA.GOV (KIDS) on Thursday, 11/17/05 at 15:33 ============================================================================= Run Date: DEC 15, 2005 Designation: PX*1*174 Package : PX - PCE PATIENT CARE ENCOUNTER Priority: Mandatory Version : 1 SEQ #131 Status: Released Compliance Date: JAN 15, 2006 ============================================================================= Associated patches: (v)PX*1*124 install with patch `PX*1*174' Subject: CIDC PCE UPDATE Category: - Routine Description: ============ Description: =========== This patch, PX*1.0*174, addresses errors in PCE, post the install of the Clinical Indicator Data Capture(CIDC) patch, PX*1.0*124. ASSOCIATED REMEDY: ================== HD0000000114675: Subscript error in the PCE API ENCEVENT^PXKENC. Duplicates: HD0000000114639, HD0000000114933 HD0000000113587: Exclusions are required for the CIDC Missing Data Report(MDR). HD0000000113534: Missing disabilities during the clinical indicator prompts. HD0000000115301: Environmental indicators AO, IR, and EC are retained when edited NSC encounters are changed to be SC. HD0000000115033: PCE encounters that are edited by DATA2PCE with new diagnoses are having missing diagnosis SC/EI classifications defaulted from the encounter level. ASSOCIATED E3R(s): ================== N/A PARTICIPATING TEST SITES: ========================= Madison, WI North Chicago, IL Boston HCS, MA ______________________________ REMEDY OVERVIEW: ================= Remedy ticket: -------------- HD0000000114675: Subscript error in PCE API ENCEVENT^PXKENC. Duplicates: HD0000000114639, HD0000000114933 Problem: -------- Subscript errors post CIDC patch PX*1.0*124 as a result of attempts to perform CIDC updates for encounters with null visit numbers. Resolution: ---------- Changes were made to routines which prevent calling the PCE API ENCEVENT^PXKENC in the instance of null PCE visit numbers. --------------------------------------------------------------------- Remedy ticket: -------------- HD0000000113587: Exclusions required for the CIDC Missing Data Report(MDR). Problem: -------- Encounter defects appear on the CIDC Missing Data Report which should not be listed. The encounter defects and encounters that should be excluded from the MDR include: Historic encounters Test patients Child encounters Non-count clinics Missing Clinical indicators for Stop Codes in file #409.45 Missing SC/EI classifications for Stop Codes in file #409.45 Resolution: ---------- Modify the MDR routines to exclude the above listed encounter defects and encounters from the MDR. --------------------------------------------------------------------- Remedy ticket: -------------- HD0000000113534: Missing disabilities during the clinical indicator prompts.. Problem: -------- In the cases where the number of disabilities exceed four, the scrolling window provided to display disabilities at the beginning of the clinical indicator classification prompts needs to be expanded. Resolution: ---------- The solution is to provide for a full screen window to display the multiple disabilities, which includes elevator side bars to scroll back for disabilities which scroll off of the top of the display. --------------------------------------------------------------------- Remedy ticket: -------------- HD0000000115301: Environmental indicators AO, IR, and EC are retained when editing NSC encounters to be SC. Problem: -------- When editing an encounter which has been identified as Non-Service Connected(NSC), if the encounter becomes Service Connected(SC), the Environmental Indicators(EI) Agent Orange(AO), Irradiation(IR), and Environmental Contaminants(EC) are being retained when they should not display. Resolution: ---------- Force a delete of the classifications AO, IR and EC if an edited encounter switches from NSC to SC. Remedy ticket: -------------- HD0000000115033: PCE encounters that are edited by DATA2PCE with new diagnoses are having missing diagnosis SC/EI classifications defaulted from the encounter level. Problem: -------- When an encounter already exists in PCE, for example, through a scheduled appointment, and DATA2PCE is used to added diagnoses, if the diagnoses are missing SC/EI classifications, these classifications are being incorrectly defaulted from the encounter level. Resolution: ---------- Change the DATA2PCE routine that updates the diagnoses to retain any null clinical indicator SC/EI classifications that are being passed in by DATA2PCE. PCE will continue to perform error checking and not permit invalid data, and will continue to set to null AO, IR, and EC for SC diagnoses. ========================= Routine Summary The following routines are included in this patch. The second line of each of these routines now looks like: ;;1.0;PCE PATIENT CARE ENCOUNTER;**[Patch List]**;Aug 12, 1996 CHECK^XTSUMBLD results Routine Name Before Patch After Patch Patch List ============ ============ =========== ========== PXAIPOV 6323448 6759190 28,73,69,108,112,130, 124,174 PXBMPOV 3061834 3064876 11,14,108,124,174 PXCEC800 1342514 2100595 124,174 PXCECCLS 11982570 10316454 124,174 PXKMAIN 10876433 10945192 22,59,73,88,69,117, 130,124,174 PXRRMDR 19496035 20792062 124,174 PXRRMDR1 N/A 719779 174 INSTALLATION INSTRUCTIONS: ========================== This patch may be run with users on the system, but it is recommended that it be queued to run after normal business hours. Installation will take less than 5 minutes. Suggested time to install: non-peak requirement hours. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. Review your mapped set. If the routines are mapped, they should be removed from the mapped set at this time. 3. From the Kernel Installation & Distribution System menu, select the Installation menu. 4. From this menu, you may select to use the following options (when prompted for INSTALL NAME, enter PX*1.0*174) 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. d. Print Transport Global - this option will allow you to view the components of the KIDS build. 5. Use the Install Package(s) option and select the package PX*1.0*174. 6. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//" respond NO. 7. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//" respond NO. 8. If any routines were unmapped as part of step 2, they should be returned to the mapped set once the installation has run to completion. NOTE: Details of the changes applied by this patch are provided during the installation and may also be reviewed with the Install File Print option on the Utilities menu in the Kernel Installation and Distribution System. Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PXAIPOV Before: B20201014 After: B21994466 **28,73,69,108,112,130,124,174** Routine Name: PXBMPOV Before: B7483817 After: B7489251 **11,14,108,124,174** Routine Name: PXCEC800 Before: B2123321 After: B3063764 **124,174** Routine Name: PXCECCLS Before: B21659444 After: B19236518 **124,174** Routine Name: PXKMAIN Before: B41988947 After: B42253213 **22,59,73,88,69,117,130,124,174** Routine Name: PXRRMDR Before: B81741465 After: B78875508 **124,174** Routine Name: PXRRMDR1 Before: After: B1090646 **174** ============================================================================= User Information: Hold Date : NOV 30, 2005 Entered By : BRICKER,DENNIS Date Entered : OCT 04, 2005 Completed By: LYNCH,MARY F. Date Completed: DEC 09, 2005 Released By : FIELDS-BARNES,JANETTE Date Released : DEC 15, 2005 ============================================================================= Packman Mail Message: ===================== $END TXT