Difference between revisions of "Patient Merge"
From VistApedia
| Line 2: | Line 2: | ||
=== Intro === | === Intro === | ||
| − | Patient Merge is a complex piece of software. Be sure to read the manual. This will provider an overview of how to use it with WV. | + | Patient Merge is a complex piece of software. Be sure to read the [http://www.va.gov/vdl/application.asp?appid=2 manual]. This will provider an overview of how to use it with WV. |
| − | === Patient Merge | + | === Patient Merge Use Issues with WV === |
There are few WV-related issues with Patient Merge that first need to be resolved. | There are few WV-related issues with Patient Merge that first need to be resolved. | ||
* Due to various issues on how the MPI Parameters and the Local Site are set-up, the software may try to contact the MPI to resolve a merge, and fail to merge as a result. | * Due to various issues on how the MPI Parameters and the Local Site are set-up, the software may try to contact the MPI to resolve a merge, and fail to merge as a result. | ||
| − | * Patch XT*7.3*113 takes away the ability for the local site to search the patient file for duplicates, and relegates that ability only to the Central MPI. | + | * Patch [http://mirrors.medsphere.org/pub/downloads.va.gov/files/FOIA/Software/Patches_By_Application/XT-KERNEL%20TOOLKIT/XT-7P3_SEQ-94_PAT-113.TXT XT*7.3*113] takes away the ability for the local site to search the patient file for duplicates, and relegates that ability only to the Central MPI. |
* X-ref ALK3 in file 15 on the Merge Status field has a bug in it. A completed merge (Merge Status = Merged) does not delete the ALK index entry. Thus, the IHS patient lookup routine erroneously says that the patient is a potential duplicate patient even though the patient has been merged already. I am not sure where the bug lies (IHS patient lookup or the Patient Merge software), but the ALK x-ref documentation says it's supposed to be deleted when it's merged. | * X-ref ALK3 in file 15 on the Merge Status field has a bug in it. A completed merge (Merge Status = Merged) does not delete the ALK index entry. Thus, the IHS patient lookup routine erroneously says that the patient is a potential duplicate patient even though the patient has been merged already. I am not sure where the bug lies (IHS patient lookup or the Patient Merge software), but the ALK x-ref documentation says it's supposed to be deleted when it's merged. | ||
Revision as of 21:50, 25 August 2011
Written by Sam Habiel. Questions? http://groups.google.com/group/hardhats.
Intro
Patient Merge is a complex piece of software. Be sure to read the manual. This will provider an overview of how to use it with WV.
Patient Merge Use Issues with WV
There are few WV-related issues with Patient Merge that first need to be resolved.
- Due to various issues on how the MPI Parameters and the Local Site are set-up, the software may try to contact the MPI to resolve a merge, and fail to merge as a result.
- Patch XT*7.3*113 takes away the ability for the local site to search the patient file for duplicates, and relegates that ability only to the Central MPI.
- X-ref ALK3 in file 15 on the Merge Status field has a bug in it. A completed merge (Merge Status = Merged) does not delete the ALK index entry. Thus, the IHS patient lookup routine erroneously says that the patient is a potential duplicate patient even though the patient has been merged already. I am not sure where the bug lies (IHS patient lookup or the Patient Merge software), but the ALK x-ref documentation says it's supposed to be deleted when it's merged.
I created a patch to resolve these issues and you can find it here. This patch depends XT*7.3*113, as it fixes a change in that patch.
- Description: JJIH_PT_MERGE_SOFTWARE_UPDATES_0100.txt
- Kids: JJIH_PT_MERGE_SOFTWARE_UPDATES_0100.kids
