Full checklist › USCDI / C-CDA portability completeness
USCDI / C-CDA portability completeness High-risk silent loss
Use the cert-named US Core / USCDI version as the minimum completeness checklist. Anything in USCDI that doesn't round-trip is, by definition, silent loss of portable data.
Anchored to:
• USCDI — US Core Data for Interoperability — ONC/ASTP (Standardized data classes/elements; the portability baseline.)
• C-CDA (Consolidated CDA) — HL7 International (Document-exchange realization; R2.1 common portability baseline.)
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
- Use the cert-named US Core / USCDI version (currently US Core 6.1.0 → USCDI v3) as the minimum completeness checklist — verify your obligation's named version.
- Reconcile every required USCDI element: row-count + coded-element + code-system-URI checks between source and target.
- Generate a C-CDA (CCD) from a sample patient in both systems and diff the coded entries, not just the rendered document.
- Document any USCDI element that doesn't round-trip and treat it as a defect, not an acceptable loss.
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.