Patient Merge - Revision history

Shabiel: /* Patient Merge Use Issues with FOIA (as of February 2019) */

2019-05-23T17:42:41Z

Patient Merge Use Issues with FOIA (as of February 2019)

@@ Line 15: / Line 15: @@
 === Patient Merge Use Issues with FOIA (as of February 2019) ===
-* Two packages have custom routines that affect record merge: CLINICAL INFO RESOURCE NETWORK (RG) and NDBI (A7R). The first one tries to talk to the MPI; and second one references a routine that doesn't exist. You need to go to the package file and remove the patient file merge from field 20 for each of those entries.
+* Two packages have custom routines that affect record merge: CLINICAL INFO RESOURCE NETWORK (RG) and NDBI (A7R). The first one tries to talk to the MPI; and second one references a routine that doesn't exist. You need to go to the package file and remove the patient file merge from field 20 for each of those entries. Here's a screenscrape:
 * Patch [https://foia-vista.osehra.org/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. You do not need to use this to use the package, but it makes finding the potential duplicate patients much easier. To undo this, in routine XDRDCOMP, change:
 <pre>

Shabiel: /* Patient Merge Use on VISTA (Quick and Dirty) */

2019-05-23T17:20:40Z

Patient Merge Use on VISTA (Quick and Dirty)

← Older revision		Revision as of 17:20, 23 May 2019
Line 523:		Line 523:
	</pre>		</pre>

	If you ever see <tt>NO PAIRS LEFT</tt> and then <tt> STOPPED </tt>, it means that your patient merge failed.		If you ever see <tt>NO PAIRS LEFT</tt> and then <tt> STOPPED </tt>, it means that your patient merge failed. I traced it, and it usually means that it's running through the package routines that do the merge (field 20 in the package file), and one of them decided to abort. Check to see which package that is, and you may have to debug to see why it decided to reject the merge.

	=== Patient Merge on VISTA (The Proper Way) ===		=== Patient Merge on VISTA (The Proper Way) ===

Shabiel: /* Patient Merge Use Issues with FOIA (as of February 2019) */

2019-05-23T17:17:12Z

Patient Merge Use Issues with FOIA (as of February 2019)

@@ Line 15: / Line 15: @@
 === Patient Merge Use Issues with FOIA (as of February 2019) ===
-* Two packages have custom routines that affect record merge: CLINICAL INFO RESOURCE NETWORK (RG) and NDBI (A7R). The first one tries to talk to the MPI; and second one references a routine that doesn't exist. You need to go to the package file and remove the patient file merge from field 20.
+* Two packages have custom routines that affect record merge: CLINICAL INFO RESOURCE NETWORK (RG) and NDBI (A7R). The first one tries to talk to the MPI; and second one references a routine that doesn't exist. You need to go to the package file and remove the patient file merge from field 20 for each of those entries.
 === Prerequisite Set-up Before Using Patient Merge ===

Shabiel: /* Patient Merge Use Issues with WV */

2019-05-23T17:11:34Z

Patient Merge Use Issues with WV

← Older revision		Revision as of 17:11, 23 May 2019
Line 7:		Line 7:
	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. The actual issue should be present in any WV installation that uses the site number of 050; as the MPI thinks when comparing ICN's that start with 50 (from 050) that they are national since 050 isn't the same 50. An MPI bug to be sure, but why bother?		* 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. The actual issue should be present in any WV installation that uses the site number of 050; as the MPI thinks when comparing ICN's that start with 50 (from 050) that they are national since 050 isn't the same 50. An MPI bug to be sure, but why bother?
	* 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 XT7.3113] takes away the ability for the local site to search the patient file for duplicates, and relegates that ability only to the Central MPI. It looks like it has affected several places; so I need to fix all these different places. For now, I fixed only one routine which matters to me: Potential Duplicate Patient Search.		* Patch [https://foia-vista.osehra.org/Patches_By_Application/XT-KERNEL%20TOOLKIT/XT-7P3_SEQ-94_PAT-113.TXT XT7.3113] takes away the ability for the local site to search the patient file for duplicates, and relegates that ability only to the Central MPI. It looks like it has affected several places; so I need to fix all these different places. For now, I fixed only one routine which matters to me: Potential Duplicate Patient Search.
	* 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.

Shabiel at 16:15, 23 May 2019

2019-05-23T16:15:36Z

← Older revision		Revision as of 16:15, 23 May 2019
Line 13:		Line 13:
	* Description: [[:File:JJIH_PT_MERGE_SOFTWARE_UPDATES_0110.txt]]		* Description: [[:File:JJIH_PT_MERGE_SOFTWARE_UPDATES_0110.txt]]
	* Kids: [[:File:JJIH_PT_MERGE_SOFTWARE_UPDATES_0110.kids.txt]]		* Kids: [[:File:JJIH_PT_MERGE_SOFTWARE_UPDATES_0110.kids.txt]]

			=== Patient Merge Use Issues with FOIA (as of February 2019) ===
			* Two packages have custom routines that affect record merge: CLINICAL INFO RESOURCE NETWORK (RG) and NDBI (A7R). The first one tries to talk to the MPI; and second one references a routine that doesn't exist. You need to go to the package file and remove the patient file merge from field 20.

	=== Prerequisite Set-up Before Using Patient Merge ===		=== Prerequisite Set-up Before Using Patient Merge ===

Shabiel at 15:59, 23 May 2019

2019-05-23T15:59:55Z

← Older revision		Revision as of 15:59, 23 May 2019
Line 11:		Line 11:

	I created a patch to resolve these issues and you can find it here. This patch depends XT7.3113, as it fixes a change in that patch.		I created a patch to resolve these issues and you can find it here. This patch depends XT7.3113, as it fixes a change in that patch.
	* Description: [~~http~~://bazaar.launchpad.net/~sam-habiel/astronaut-vista-server/enhancements/download/sam.habiel%40gmail.com-20110825211457-zvgppwvs0tgbsip9/jjih_pt_merge_softwa-20110825211406-sj7iowsxtttd0sa3-2/JJIH_PT_MERGE_SOFTWARE_UPDATES_0100.txt JJIH_PT_MERGE_SOFTWARE_UPDATES_0100.txt]		* Description: [[:File:JJIH_PT_MERGE_SOFTWARE_UPDATES_0110.txt]]
	* Kids: [~~http~~://bazaar.launchpad.net/~sam-habiel/astronaut-vista-server/enhancements/download/sam.habiel%40gmail.com-20110825211457-zvgppwvs0tgbsip9/jjih_pt_merge_softwa-20110825211406-sj7iowsxtttd0sa3-1/JJIH_PT_MERGE_SOFTWARE_UPDATES_0100.kids ~~JJIH_PT_MERGE_SOFTWARE_UPDATES_0100~~.~~kids~~]		* Kids: [[:File:JJIH_PT_MERGE_SOFTWARE_UPDATES_0110.kids.txt]]

	=== Prerequisite Set-up Before Using Patient Merge ===		=== Prerequisite Set-up Before Using Patient Merge ===

Shabiel: /* Prerequisite Set-up Before Using Patient Merge */

2019-05-23T15:29:15Z

Prerequisite Set-up Before Using Patient Merge

← Older revision		Revision as of 15:29, 23 May 2019
Line 20:		Line 20:
	* '''XDR''' (for day to day use of Patient Merge)		* '''XDR''' (for day to day use of Patient Merge)
	* '''XDRMGR''' (for Manager Operations: doing the actual merge, Site Parameters)		* '''XDRMGR''' (for Manager Operations: doing the actual merge, Site Parameters)
			* '''DG ELIGIBILITY''' (ditto)

	=== Patient Merge Set-Up on VISTA ===		=== Patient Merge Set-Up on VISTA ===

NeilArmstrong: Added a glossary link to Action~

2012-07-30T23:48:55Z

Added a glossary link to Action~

← Older revision		Revision as of 23:48, 30 July 2012
Line 399:		Line 399:
	S SELECT/REVIEW OVERWRITES		S SELECT/REVIEW OVERWRITES

	Select Action: HEALTH SUMMARY// VERIFIED DUPLICATE		Select [[Action~\|Action]]: HEALTH SUMMARY// VERIFIED DUPLICATE


Line 580:		Line 580:
	S SELECT/REVIEW OVERWRITES		S SELECT/REVIEW OVERWRITES

	Select Action: HEALTH SUMMARY// v VERIFIED DUPLICATE		Select [[Action~\|Action]]: HEALTH SUMMARY// v VERIFIED DUPLICATE

NeilArmstrong: Added a glossary link to Record~

2012-04-12T13:07:53Z

Added a glossary link to Record~

Show changes

NeilArmstrong: Added Glossary Link to Prompt~

2012-03-06T16:46:06Z

Added Glossary Link to Prompt~

← Older revision		Revision as of 16:46, 6 March 2012
Line 562:		Line 562:


	At the following prompt select a POTENTIAL DUPLICATE ENTRY. If a selection		At the following [[prompt~\|Prompt]] select a POTENTIAL DUPLICATE ENTRY. If a selection
	is not made, you will be given a chance to select from a list if you		is not made, you will be given a chance to select from a list if you
	want to. Otherwise, you will be returned to the menu system.		want to. Otherwise, you will be returned to the menu system.
Line 594:		Line 594:
	D2//		D2//

	At the following prompt select a POTENTIAL DUPLICATE ENTRY. If a selection		At the following [[prompt~\|Prompt]] select a POTENTIAL DUPLICATE ENTRY. If a selection
	is not made, you will be given a chance to select from a list if you		is not made, you will be given a chance to select from a list if you
	want to. Otherwise, you will be returned to the menu system.		want to. Otherwise, you will be returned to the menu system.