How should duplicates be resolved when a patient has multiple MRNs across sites?

Prepare for EpicCare Everywhere Exam with our comprehensive quizzes. Practice with multiple choice questions and detailed explanations. Boost your chances of success!

Multiple Choice

How should duplicates be resolved when a patient has multiple MRNs across sites?

Explanation:
When resolving duplicates across sites, the goal is to establish one canonical patient record by accurately matching and merging duplicates so all data follows the patient. Robust patient matching uses demographic data, encounter history, and other identifiers to determine that different MRNs belong to the same person. Once identified, linking those MRNs and merging the charts under data stewardship creates a single canonical record with a global identifier, ensuring every piece of information—demographics, encounters, medications, allergies, labs, and more—contributes to one longitudinal view. This unified record enables safe, coordinated care across locations and preserves data provenance through audit trails and governance. Creating a new canonical record without linking MRNs fragments data; deleting duplicates or ignoring duplicates breaks history and safety by losing context or duplicating records.

When resolving duplicates across sites, the goal is to establish one canonical patient record by accurately matching and merging duplicates so all data follows the patient. Robust patient matching uses demographic data, encounter history, and other identifiers to determine that different MRNs belong to the same person. Once identified, linking those MRNs and merging the charts under data stewardship creates a single canonical record with a global identifier, ensuring every piece of information—demographics, encounters, medications, allergies, labs, and more—contributes to one longitudinal view. This unified record enables safe, coordinated care across locations and preserves data provenance through audit trails and governance. Creating a new canonical record without linking MRNs fragments data; deleting duplicates or ignoring duplicates breaks history and safety by losing context or duplicating records.

Subscribe

Get the latest from Examzify

You can unsubscribe at any time. Read our privacy policy