forked from WorldVistA/VistA-M
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Patch Subject: MASTER VETERAN INDEX VISTA ENHANCEMENTS - ITERATION 15 Description: ============ ************************************************************************* * This patch may be installed with users on the system, however because * * the patient lookup routines are being exported with this patch, we * * strongly advise that it be installed after business hours. * ************************************************************************* DG*5.3*915 is the only required build for patch DG*5.3*919. NOTE: Master Patient Index (MPI) enhancements are being distributed in three VistA namespaces: DG, RG and MPIF. The enhancements related to this patch are only being distributed in the DG and MPIF VistA namespaces. MPIF*1.0*62 should be installed before DG*5.3*919 for non-legacy sites (do NOT install MPIF*1.0*62 on legacy sites), as the new Swipe/Scan process being exported in this patch will not work without MPIF*1.0*62. Therefore it is recommended that these patches be installed in the following order on non-legacy sites: MPIF*1.0*62 and then DG*5.3*919. DG*5.3*919 should be installed immediately after installing MPIF*1.0*62. NOTE: Legacy sites can install just the DG*5.3*919 patch, as legacy sites won't use the data capture process. MPIF*1.0*62 should NOT be installed on legacy sites. Enhancement The enhancement exported in this patch updates the routine DPTLK so that anytime a Veteran Health Information Card (VHIC) or the Department of Defense's (DoD) Common Access Card (CAC) is presented and swiped or scanned at the facility, the activity is captured and stored locally at the site in the ^XTMP("MPIFCARD") global location. This stored activity data which consists of the card's ID, type of Card (VHIC or CAC) and the event type (swipe or scan) will be downloaded nightly by the Master Patient Index (MPI) for use by the Healthcare Identity Management (HC IdM) team for reporting purposes. Issue WorldVistA#1 Routines DPTLK4 and DPTLK7 were updated so that the WHO ENTERED PATIENT field (#.096) in the PATIENT file (WorldVistA#2) is populated for new patients registered with the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. Issue WorldVistA#2 Finally, routines DPTLK4 and DPTLK7 were also updated to ensure that the 'NEW PATIENT ADDED TO SYSTEM' MailMan messages are generated when a new patient is registered at the Veterans Affairs Medical Center (VAMC) through the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. Patch Components ================ Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- N/A 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: New Service Requests (NSRs) ---------------------------- N/A Patient Safety Issues (PSIs) ----------------------------- N/A CA Ticket(s) & Overview --------------------------- 1. I7264886FY16 - WHO ENTERED PATIENT field (#.096) in the PATIENT file (WorldVistA#2) no longer populated Problem: -------- After the release of patch DG*5.3*915 it was determined that the WHO ENTERED PATIENT field (#.096) of the PATIENT file (WorldVistA#2) was not being populated after a new patient was registered with the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. After further investigation, this issue was found to be a long standing problem, but only when a patient was registered with either a legacy Veterans Identification Card (VIC) or the newer VHIC cards. This issue went unnoticed until now due to the limited use of these cards. Resolution: ----------- Updates were made to the patient registration software, specifically routines DPTLK4 and DPTLK7, to populate the WHO ENTERED PATIENT field (#.096) in the PATIENT file (WorldVistA#2) when a patient registration is performed with a legacy VIC or newer VHIC cards or through the REGISTER A PATIENT [DG REGISTER PATIENT] menu option. Note: This field is historically populated directly by the REGISTATION (DG) software and not a FileMan (FM) trigger. Test Sites: ---------- C.W. Bill Young (Bay Pines) VAMC Robley Rex (Louisville) VAMC VA Connecticut HCS Patch Installation: Pre/Post Installation Overview ------------------------------ There are no Pre/Post installation routine processes. Use default answers for KIDS load/install questions. Patch-Files: http://code.osehra.org/VistA.git/tree/b0ced814/Packages/Registration/Patches/DG_5.3_919
- Loading branch information
1 parent
9d203d0
commit 7dc3df9
Showing
14 changed files
with
439 additions
and
130 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
132 changes: 66 additions & 66 deletions
132
Packages/Health Level Seven/Globals/870+HL LOGICAL LINK.zwr
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.