C-CDA vs FHIR: Clinical Documents vs Resources
Understanding the fundamental architectural differences between C-CDA XML documents and FHIR resources, and how modern healthcare systems use both.
Disclaimer: This guide is provided by Efneze for educational and technical reference purposes only. HL7®, FHIR®, and related standards are trademarks of Health Level Seven International. Efnezeis not affiliated with or endorsed by Health Level Seven International. For official requirements, always refer to the applicable official specification and your organization's implementation guidance.
The Core Difference
C-CDA (Consolidated Clinical Document Architecture) is a document standard. It encodes a complete clinical summary as a single, human-readable XML document. Think of it like a structured medical chart note.
FHIR (Fast Healthcare Interoperability Resources) is a data API standard. It models individual clinical facts as discrete, linkable resources. Think of it like a database of clinical records exposed via REST APIs.
When C-CDA Is Used
C-CDA is the standard for document-based information exchange, primarily in transitions of care:
- Patient discharge from hospital to rehabilitation facility
- Referrals from primary care to specialist
- Patient health record downloads from EHR patient portals
- Public health reporting, including immunization registry workflows
C-CDA is commonly evaluated when a complete clinical snapshot needs to be transmitted as a package, including narrative text, structured data, and embedded coded values in a single document.
When FHIR Is Used
FHIR is the standard for API-based, resource-level data access:
- SMART on FHIR apps reading specific patient data such as labs or medications
- Payer-to-provider clinical data exchange
- Population health analytics pulling data across patient cohorts
- EHR vendor APIs
- Systems that support clinical or operational workflows involving timely patient data exchange
Converting C-CDA to FHIR
Many healthcare data engineering projects require converting C-CDA documents into FHIR resources for analytics or application use. The conversion maps C-CDA sections to FHIR resource types:
| C-CDA Section | FHIR Resource(s) |
|---|---|
| Problem List | Condition |
| Medications | MedicationRequest, MedicationStatement |
| Allergies | AllergyIntolerance |
| Vital Signs | Observation (category: vital-signs) |
| Laboratory Results | Observation (category: laboratory), DiagnosticReport |
| Procedures | Procedure |
| Immunizations | Immunization |
| Encounters | Encounter |
| Assessment & Plan | CarePlan, ClinicalImpression |
| Social History | Observation (category: social-history) |
| Patient Demographics | Patient |
| Providers | Practitioner, PractitionerRole |
Practical Recommendation
For modern healthcare data platforms, use both: accept C-CDA documents at integration points such as hospital transitions and referrals, convert them to FHIR resources for your canonical data store, and expose FHIR APIs for downstream consumers. This pattern provides broad compatibility while future-proofing your architecture.