$TXT Created by KRN.FO-OAKLAND.DOMAIN.EXT (KIDS) on Thursday, 12/05/19 at 09:30 ============================================================================= Run Date: FEB 20, 2020 Designation: XU*8*723 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #560 Status: Released Compliance Date: MAR 22, 2020 ============================================================================= Associated patches: (v)XU*8*678 <<= must be installed BEFORE `XU*8*723' Subject: NEW FIELD CERNER IN THE INSTITUTION FILE Category: - Routine - Data Dictionary Description: ============ This patch adds a new field CERNER (#102) in the INSTITUTION file (#4) to support Patient Record Flag (PRC) to indicate if a facility has been converted to CERNER, and a new API that returns value of this field. This patch also includes the new field CERNER into the Institution Master File (IMF) update process by appending data to the end of the Institution (ZIN) segment. The adding will allow IMF to populate the new field value to all facilities. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- INSTITUTION (#4) CERNER (#102) New Forms Associated: Form Name File # 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 Additional Information: N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- INC8554017 Problem: ---------- The Patient Record Flag application team requested a new field, CERNER, to indicate if a facility in the INSTITUTION file has been concerted to CERNER. Resolution: ----------- - Add a new field CERNER(#4) in the INSTITUTION file(#4): DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 4,102 CERNER 102;1 SET '0' FOR NO; '1' FOR YES; LAST EDITED: DEC 03, 2019 HELP-PROMPT: Enter "0" or "1". DESCRIPTION: This field indicates if a facility has been converted to CERNER. - Create a new API to return the value of CERNER field: $$CERNER^XUAF4(STA) CERNER(STA) ; Check if a facility has been converted to CERNER ; Take in STA = Station number ; Return -1 for invalid station number ; Return 1 for CERNER station N XUSIEN S XUSIEN=+$$IEN^XUAF4(STA) I XUSIEN'>0 Q "-1^"_STA_" is not a valid station number" Q $P($G(^DIC(4,XUSIEN,102)),U) - Update the MFS in the HL7 message that includes the new field CERNER to poplulate data at sites. Test Sites: ----------- ALTOONA, PA VAMC CHARLESTON, SC VAMC Software and Documentation Retrieval Instructions: ---------------------------------------------------- The software for this patch is being released as a KIDS PackMan message. There's no updated Documentation being released with this patch. Blood Bank Team Coordination ============================ Blood Bank Clearance: EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8*723 contains changes to a package referenced in VHA OI SEPG SOP 192-023 Review of VISTA Patches for Effects on VISTA Blood Bank Software. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch XU*8*723 have no effect on Blood Bank software functionality, therefore RISK is none. 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 fewer than 5 minutes to install. Installation Instructions: -------------------------- 1. Choose the PackMan message containing this patch. 2. Choose the INSTALL/CHECK MESSAGE PackMan option. 3. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, you may elect to use the following options. When prompted for the INSTALL NAME enter the patch #XU*8*723: a. Backup a Transport Global - This option will create a backup message of any routines exported with this 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 this patch is installed. It compares all components of this 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. 4. From the Installation Menu, select the Install Package(s) option and choose the patch to install. 5. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//N 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//N 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//N/A 8. If prompted 'Delay Install (Minutes): (0 - 60): 0//' respond 0. Post-Installation Instructions ------------------------------ No further action needed. Backout and Rollback Procedure: ------------------------------- This patch consists of three routines. During the VistA Installation Procedure of the KIDS build, the installer should back up the modified routines by the use of the 'Backup a Transport Global' action (step 3a in the Installations Instructions below). If rollback/backout is required, the installer can restore the routines using the MailMan message that were saved prior to installing the patch. This patch also added a new field CERNER in the INSTITUION file (#4). If assistance is needed to rollback/backout the patch, please log a SNOW ticket. Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**;Jul 10, 1995;Build 3 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XUAF4 Before: B47165433 After: B50686588 **43,112,206,209,232,217,261, 394,549,555,723** Routine Name: XUMF04 Before: B21394417 After: B23190073 **549,678,723** Routine Name: XUMF04H Before: B48910610 After: B50323843 **549,678,698,723** Routine list of preceding patches: 555, 698 ============================================================================= User Information: Entered By : Date Entered : DEC 02, 2019 Completed By: Date Completed: FEB 20, 2020 Released By : Date Released : FEB 20, 2020 ============================================================================= Packman Mail Message: ===================== $END TXT