$TXT Created by DAVIS,PAULETTE T at DEVCRN.FO-ALBANY.MED.VA.GOV (KIDS) on Monday, 02/22/10 at 11:25 ============================================================================= Run Date: MAR 26, 2010 Designation: DG*5.3*800 Package : DG - REGISTRATION Priority: Mandatory Version : 5.3 SEQ #726 Status: Released Compliance Date: APR 26, 2010 ============================================================================= Associated patches: (v)DG*5.3*449 <<= must be installed BEFORE `DG*5.3*800' (v)DG*5.3*697 <<= must be installed BEFORE `DG*5.3*800' (v)DG*5.3*707 <<= must be installed BEFORE `DG*5.3*800' (v)XWB*1.1*54 <<= must be installed BEFORE `DG*5.3*800' Subject: VETERAN ON-LINE APPLICATION (VOA) ENHANCEMENT Category: - Data Dictionary - Routine - Enhancement (Mandatory) Description: ============ DG*5.3*449, DG*5.3*697, DG*5.3*707, and XWB*1.1*54 are required builds for patch DG*5.3*800. Background Information: The Veteran On-Line Application (VOA) project is a collaborative effort by the MyHealtheVet veteran web-portal, the National Enrollment Service (ESR), Person Services Identity Management (PSIM), the Master Patient Index (MPI), and the VistA Patient Information Management System (PIMS) application. *** PLEASE NOTE ALL CHANGES INTRODUCED BY THIS PATCH WILL BE DORMANT / HIDDEN TO USERS UNTIL THE RELEASE OF VOA EXPECTED LATER IN 2010. As soon as the Veterans' Online Application (VOA) system is fully implemented, the MyHealtheVet veteran web-portal and the National Enrollment System (ESR) will make it easier for a veteran to register for medical benefits from VHA via the World Wide Web. This release supports the implementation of VOA; however, the functionality introduced herein is being released in a dormant state. Application process flow via VOA (presumes implementation of VOA system): 1) The veteran completes the web-based application. 2) The veteran's data is passed to the MPI through the Enrollment System Redesign (ESR) and Person Services Identity Management (PSIM). 3) A record is created on the MPI and receives a National Integration Control Number (ICN). The ICN is the unique identification number. The record is initially created with a TEMPORARY ID State. 4) After a vetting process by ESR to determine the applicant's Enrollment Status, the ID State on the MPI is changed to PERMANENT. If warranted, this could be the result of in-person authentication. 5) At that point, the VAFC VOA ADD PATIENT Remote Procedure (introduced by this patch) will be called to remotely add the patient to the Preferred Facility's VistA database. The following enhancements are distributed in patch DG*5.3*800 for the MPI and PIMS portion of the new functionality. Item #1: A new Remote Procedure, VAFC VOA ADD PATIENT, has been created to allow the remote creation of a VistA PATIENT (#2) record at the Preferred Facility for the Veteran On-Line Application (VOA) project. In order for the VAFC VOA ADD PATIENT Remote Procedure to function properly, RPC Broker patch XWB*1.1*54 MUST be installed and is a required patch for DG*5.3*800. Item #2: The VAFCPTAD routine is invoked by the VAFC VOA ADD PATIENT Remote Procedure. Each required field necessary for the creation of a valid patient record is checked to ensure that the data meets the same input standards as a record created locally. If any field fails the validity checks, the record is not created, and a reject or fail message is returned to PSIM and ESR. If all required fields pass the validity checks, a new record is created on VistA, and the DFN for that record is returned to PSIM and ESR. Reference private integration control registration # 5364 for detailed information. Item #3: The IN-PERSON PROOFED (#.08) field has been added to the TREATING FACILITY LIST (#391.91) file on VistA. This field is updated when the In-Person Authentication process is completed. Item #4: In routines VAFCTFIN and VAFCTFU code enhancements were made to the MFN-M05 (Treating Facility Master File Update) processor to include the processing of the IN-PERSON PROOFED (.08) field in the TREATING FACILITY LIST (#391.91) file. This change supports the processing and updating of VistA files to allow VistAWeb and/or CPRS to see (or not see) the MyHealtheVet system record on the VistA site, based on the value of the IN-PERSON PROOFED (.08) field. Item #5: The existing "Get Treating Facility" API in routine VAFCTFU1 was enhanced to support the MyHealtheVet In-Person Authentication process. MyHealtheVet requires that records be screened from the VistAWeb and/or CPRS user list at the VistA site if the In-Person Authentication process has not been completed. If the IN-PERSON PROOFED (.08) field in the TREATING FACILITY LIST (#391.91) file for the MyHealtheVet (200MH) entry is not set to YES, then that record is not returned by the API or related Remote Procedure Call. Item #6: In-Person Authentication has already been performed on a large number of patient records in the VistA TREATING FACILITY LIST (#391.91) file. These records need to have the IN-PERSON PROOFED (.08) field set to YES so they are accessible to CPRS and/or VistAWeb. Post-init routine, DG53800P, examines the TREATING FACILITY LIST (391.91) file. For the MyHealtheVet (200MH) records, it sets the IN-PERSON PROOFED (.08) field to YES. New Remote Procedure: ===================== VAFC VOA ADD PATIENT This Remote Procedure Call allows the remote creation of a VistA PATIENT (#2) record at the Preferred Facility for the Veteran On-Line Application (VOA) project. Fields Included in this Patch: ============================== Field Name (Number) File Name (Number) -------------------------------------------------------------- IN-PERSON PROOFED (#.08) TREATING FACILITY LIST (#391.91) Documentation Update: ===================== The following MASTER PATIENT INDEX/PATIENT DEMOGRAPHICS (MPI/PD) VISTA documentation is available, updated for patch DG*5.3*800. Facilities should download the revised documentation listed as follows: Release Notes DG5_3_800RN.PDF The preferred retrieval method is to FTP from the ANONYMOUS.SOFTWARE directory at: DOWNLOAD.VISTA.MED.VA.GOV This transmits the file from the first available FTP server. Sites may also elect to retrieve software directly from one of the following servers. OI Field Office FTP Address Directory ------------------------------------------------------------------ Albany ftp.fo-albany.med.va.gov ANONYMOUS.SOFTWARE Hines ftp.fo-hines.med.va.gov ANONYMOUS.SOFTWARE Salt Lake City ftp.fo-slc.med.va.gov ANONYMOUS.SOFTWARE Note: The file must be transferred in binary or IMAGE, not ASCII, mode. The document can also be downloaded from the VistA Documentation Library (VDL) Web page in both Acrobat PDF and MS-Word DOC formats: http://www.va.gov/vdl/application.asp?appid=16 Associated Remedy Ticket(s): ============================ There are no associated Remedy Tickets. Associated New Service Request (NSR): ===================================== Request ID: 20070610 Test Sites: =========== Altoona, PA North Texas HCS Phoenix, AZ Post-Install Routine: ===================== The post-init routine is queued to run in the background. Routine, DG53800P, examines the TREATING FACILITY LIST (391.91) file. For the MyHealtheVet (200MH) records, the IN-PERSON PROOFED (.08) field is set to YES. When the process finishes, the patch installer will be notified with an e-mail message. This message provides the task number, begin time, and end time for the process. In the event that you wish to stop the process after it has started, you can use the STOP^DG53800P line tag. The process can be restarted by using the STRTAGN^DG53800P line tag. Installation Instructions: ========================== This patch takes less than 2 minutes to install. This patch should be loaded during non-peak hours to minimize disruption to the users. 1. Users are allowed on the system during patch installation. 2. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. Note: TEXT PRINT/DISPLAY option in the PackMan menu will display the patch text only. 3. From the Kernel Installation and Distribution System Menu, select the Installation menu. 4. From this menu, you may elect to use the following options: (a) Backup a Transport Global. (b) Compare Transport Global to Current System. (c) Verify Checksums in Transport Global. (d) Print Transport Global. 5. Use the Install Package(s) option and select the package DG*5.3*800. 6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', respond NO. 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', respond YES. The following OPTIONS should be disabled during the installation. Register a Patient [DG REGISTER PATIENT] Load/Edit Patient Data [DG LOAD PATIENT DATA] Electronic 10-10EZ Processing [EAS EZ 1010EZ PROCESSING] Preregister a Patient [DGPRE PRE-REGISTER OPTION] UPDATE BATCH JOB FOR HL7 v2.3 [VAFC BATCH UPDATE] 8. Routine DG53800P can be deleted from your system after the patch installer has been notified via e-mail that the task has run to completion. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Registration;**[Patch List]**;Aug 13, 1993;Build 4 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: DG53800P Before: n/a After: B18028040 **800** Routine Name: VAFCPTAD Before: B2093553 After: B64926627 **149,800** Routine Name: VAFCTFIN Before: B22721949 After: B24080050 **428,474,520,639,707,800** Routine Name: VAFCTFU Before: B41840382 After: B43187604 **149,240,261,255,316,392,440, 428,474,520,697,800** Routine Name: VAFCTFU1 Before: B9279546 After: B9951191 **261,392,448,449,800** Routine list of preceding patches: 449, 697, 707 ============================================================================= User Information: Entered By : DAVIS,PAULETTE Date Entered : NOV 14, 2008 Completed By: ALDERMAN,MATT S Date Completed: MAR 25, 2010 Released By : GROOMS,ANTHONY E Date Released : MAR 26, 2010 ============================================================================= Packman Mail Message: ===================== $END TXT