This page is part of the C-CDA on FHIR Implementation Guide (v1.2.0-ballot: STU 1 Ballot 4) based on FHIR R4. The current version which supercedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions
This page provides a mapping from CDA to FHIR. For the FHIR to CDA mapping, please refer to Patient FHIR → CDA. For guidance on how to read the table below, see Reading the C-CDA ↔ FHIR Mapping Pages
C-CDA¹ US Realm Header recordTarget |
FHIR Patient |
Transform Steps |
---|---|---|
/patientRole/id | .identifier | CDA id ↔ FHIR identifier |
/patientRole/addr | .address | CDA addr ↔ FHIR address |
/patientRole/telecom | .telecom | CDA telecom ↔ FHIR telecom |
/patientRole/patient/name | .name | CDA name ↔ FHIR name |
/patientRole/patient/administrativeGenderCode | .gender | CDA coding ↔ FHIR CodeableConcept CDA administrativeGender → FHIR gender |
/patientRole/patient/birthTime | .birthDate | CDA ↔ FHIR Time/Dates |
/patientRole/patient/maritalStatusCode | .maritalStatus | CDA coding ↔ FHIR CodeableConcept |
/patientRole/patient/raceCode | .extension:us-core-race | CDA coding ↔ FHIR CodeableConcept This should map to ombCategory extension |
/patientRole/patient/sdtc:raceCode | .extension:us-core-race | CDA coding ↔ FHIR CodeableConcept |
/patientRole/patient/ethnicGroupCode | .extension:us-core-ethnicity | CDA coding ↔ FHIR CodeableConcept This should map to ombCategory extension |
/patientRole/patient/sdtc:ethnicGroupCode | .extension:us-core-ethnicity | CDA coding ↔ FHIR CodeableConcept |
/patientRole/patient/languageCommunication/languageCode | .communication.language | |
/patientRole/patient/languageCommunication/preferenceInd | .communication.preferred | |
/patientRole/providerOrganization | .managingOrganization |
1. XPath abbrievated for C-CDA US Realm recordTarget as:
ClinicalDocument/recordTarget/
An illustrative example with higlighting is shown above based on the consensus of mapping and guidance. Not all possible elements in CDA or FHIR may be represented. To access the content for the above example, click on the links below.
The consensus mapping example developed through multiple vendors are available below:
As reviewed in the methodology, a more comprehensive review was performed via spreadsheets. These spreadsheets have been consolidated and further revised in the tables above but are provided for reference here