Notifications
Clear all

Same-as-link (SAL) modeling when the merges/duplicate matching can and do change


Posts: 8
Topic starter
(@scott)
Active Member
Joined: 1 year ago

I am working on a medical system that spans 1000 hospitals.  currently have a merge process to identify medical record numbers (MRN - a BK for the patient) and match them across hospitals.  However, the internal matching within the hospitals themselves is inconsistent. 

Hospitals often have multiple electronic medical record (EMR) systems and have little to no standardization or quality control.  We have a situation where we have matched records that are "rematched" in different ways.  For example, we have three MRNs (BKs) 1, 2, and 3.  periodically we receive new feeds from the hospitals, and the matching/merging can be different.  For example...

January 1 feed:

MRN | Duplicate MRN

1      |   1

1      |   2

1      |   3

 

February 1 feed:

MRN | Duplicate MRN

1      |   1

1      |   2

3      |   3

And yet later:

 

March 1 feed:

MRN | Duplicate MRN

1      |   1

3      |   2

3      |   3

 

I'm sure that this is not new, how has this been addressed in a cogent manner?  I am not even dealing with cross-hospital matching and SAL logic. 

Reply
4 Replies