Full checklist › Dropped HL7 v2 / FHIR interface feeds
Dropped HL7 v2 / FHIR interface feeds High-risk silent loss
Lab (ORU), registration (ADT), radiology, and pharmacy interfaces silently aren't reconnected after cutover — the classic migration failure where the data stops flowing and nobody notices for days.
Anchored to:
• HL7 v2 Messaging (ADT / ORU) — HL7 International (Latest v2.9.1; v2.5.1 common in US production. (Page serves 202 to scripts; resolves in browser.))
General IT / operational guidance — not medical, legal, or compliance advice. This is a data-integrity validation checklist for EHR migration. Standards and versions revise; verify every citation and version against the live owner page and confirm requirements with your EHR vendor and your organization's compliance/HIM team before acting.
What to validate
- Reconcile that EVERY inbound/outbound interface (lab ORU, ADT registration, radiology, pharmacy) is reconnected AND tested post-cutover with a live message.
- Confirm Z-segments and custom OBX fields aren't dropped in translation.
- Verify MSH-9 trigger events map correctly (e.g., ADT^A01..A08) on the new engine.
- Confirm OBX units, reference ranges, and abnormal flags survive on result messages.
- Reconcile MRN crosswalks so messages route to the right patient; reconcile message counts source vs target for the cutover window.
Get the runnable validation toolkit →All 7 failure modes
Not medical advice. IT/operational guidance for EHR data-migration validation, anchored to official HL7/FHIR, ONC/ASTP, HIPAA (eCFR), and code-system sources. Last verified 2026-06-22. Verify versions and requirements with your vendor and compliance team. Some outbound links may be referral links.