$TXT Created by CDVF.DEVSLC.DOMAIN.EXT (KIDS) on Thursday, 12/12/24 at 11:30 ============================================================================= Run Date: APR 23, 2025 Designation: PX*1*248 Package : PX - PCE PATIENT CARE ENCOUNTER Priority: Mandatory Version : 1 SEQ #183 Status: Released Compliance Date: MAY 23, 2025 ============================================================================= Associated patches: (v)PX*1*238 <<= must be installed BEFORE `PX*1*248' Subject: PCE ENCOUNTER LOOKUP REFINEMENTS Category: - Routine Description: ============ This patch addresses the following issues: - When filing PCE data from Event Capture, it was sometimes filing to a duplicate visit instead of the existing primary visit. - When a user scans in non-VA (historical) files via VistA Imaging Capture using different Hospital Locations, it was sometimes filing to the same visit, instead of to different visits. - When filing suspended or reopened surgeries from WebVIRR, PCE is filing the PCE data to a duplicate surgery visit instead of to the existing visit. Review the Defect Tracking System Ticket(s) & Overview section below for details. EHRM Impact Statement: ---------------------- This patch can be installed at all sites, including EHRM converted sites. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: 1. INC34787443 - Consult association is bringing in a different Visit location than selected Duplicates: INC34642423, INC34842892, INC34988032 Problem: -------- When a user scans in non-VA (historical) images via VistA Imaging Capture for the same patient and date/time, but different Hospital Locations, the subsequent images/notes get linked to the same visit as the first one, instead of creating a new visit using the different Hospital Location. From the user's perspective, the issue they see is that when they look at the note in CPRS, it is showing the wrong location. (The issue only happens if the Hospital Locations have the same Stop Code Number (File #44, Field #8)). Resolution: ----------- When filing PCE data, the system tries to determine if the data should be filed to an existing visit or if it needs to create a new visit. When trying to determine if there is an existing matching visit for the data being filed, patch PX*1*238 made a change to not require the Hospital Locations to match when filing historical data. This patch will restore the previous behavior, and file the data to a new visit if the Hospital Locations do not match (even when filing historical data). 2. INC34876576 - Event Capture filing data to duplicate Visit Duplicates: INC34881000, INC34826510, INC34883847, INC34858477, INC34902410, INC34984898, INC34905855, INC35035138, INC35017549, INC35093294, INC35243180, and INC34861118, INC36199224 Problem: -------- When filing PCE data from Event Capture, it was filing to a duplicate visit instead of the existing primary visit. (It only occurred for Hospital Location entries (file #44) whose Stop Code Number's IEN matched one of the numbers listed in the ANCILLARY DSS ID file (#150.1)). Resolution: ----------- When filing PCE data, the system tries to determine if the data should be filed to an existing visit or if it needs to create a new visit. When trying to determine if there is an existing matching visit for the data being filed, patch PX*1*238 required that the Service Categories match. However, there are some exceptions; one being, that it allows for a Service Category of X (Ancillary) to match A (Ambulatory), as long as the Hospital Location's Stop Code Number was not an ancillary code (defined by the code not being listed in the ANCILLARY DSS ID file (#150.1)). However, when checking if the Stop Code Number was listed in file #150.1, it was using the IEN instead of the actual three-digit AMIS reporting code. This patch corrects that. 3. INC35008974 - Filing suspended or reopened surgeries creates a duplicate surgery encounter Duplicates: INC35393629 Problem: -------- When filing suspended or reopened surgeries from WebVIRR, PCE is filing the PCE data to a duplicate surgery visit instead of to the existing visit. Resolution: ----------- Surgery encounters are created with a Service Category of S. When these encounters are checked-out Scheduling changes the Service Category to A if the patient is an outpatient and to I if the patient is an inpatient. A change was made to check if the encounter has been checked out and if it has, to match a visit with the changed Service Category. 4. INC35623462 - R1 - (AMA) Lab 00S Encounter issue Problem: -------- In some cases, Lab is passing the visit date/time as a "string date", which causes the lookup to fail to find an existing visit resulting in the creation of a duplicate visit. Resolution: ----------- If the visit date/times is passed as a "string date" it is converted into a valid FileMan date. Test Sites: ----------- Huntington VAMC (Huntington, WV) Palo Alto VAMC (Palo Alto, CA) Sioux Falls VAMC (Sioux Falls, SD) Test Sites - SNOW Change Order #: Huntington VAMC: CHGO590579 Palo Alto VAMC: CHGO582630 Sioux Falls VAMC: CHGO582619 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE Documentation Title Name File --------------------------------------------------------------- Patient Care Encounter (PCE) User Manual PX_UM.DOCX PX_UM.PDF Patch Installation: ------------------- Pre/Post Installation Overview: Pre-Installation Instructions: This patch may be installed with users on the system, although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch or build name. (ex. PX*1.0*248) B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter PX*1.0*248 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. C. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. 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 of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO. Post-Installation Instructions: There are no post-installation tasks to complete. Back-Out/Roll Back Plan: ------------------------ Back-out will be done only with the concurrence and participation of the development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between the development team, VA site/region personnel and other appropriate VA personnel. In order to back-out this patch, the site/region should have saved a backup using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The PackMan containing the back-up can be installed using the Installation Menu on the Kernel Installation and Distribution System Menu. Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;PCE PATIENT CARE ENCOUNTER;**[Patch List]**;Aug 12, 1996;Build 6 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PXAIVST Before: B57755944 After: B64019963 **5,9,15,74,111,96,130,124,164, 168,211,238,248** Routine Name: PXUTLVST Before: B39753642 After: B30805851 **238,248** Routine list of preceding patches: 238 ============================================================================= User Information: Entered By : Date Entered : AUG 29, 2024 Completed By: Date Completed: APR 15, 2025 Released By : Date Released : APR 23, 2025 ============================================================================= Packman Mail Message: ===================== $END TXT