C-CDA on FHIR
1.2.0 - STU 1 United States of America flag

This page is part of the C-CDA on FHIR Implementation Guide (v1.2.0: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

FHIR to C-CDA Procedures

FHIR US Core → C-CDA Mapping

While multiple vendors participated in CDA → FHIR mappings at a connectathon, only a single vendor (Cerner/Oracle) has participated in the FHIR → CDA mapping. We welcome feedback on these mappings which represent less than a multi-vendor consensus at this time.


This page provides a mapping from FHIR to CDA. For the CDA to FHIR mapping, please refer to Procedures CDA → FHIR. For guidance on how to read the table below, see Reading the C-CDA ↔ FHIR Mapping Pages.

Note on template selection

It also specifies a template for “all interventional, non-interventional, surgical, diagnostic, or therapeutic procedures or treatments pertinent to the patient historically at the time the document is generated.” For this reason, we recommend mapping FHIR Procedures to Procedure Activity Procedure when using the C-CDA R3/E1 guide for the targeted C-CDA, while guidance on mapping to the other templates when generating an older version C-CDA will be forthcoming.

FHIR to C-CDA

FHIR
Procedure
C-CDA¹
Procedure Activity procedure
Transform Steps
.identifier /id CDA id ↔ FHIR identifier
.status /statusCode FHIR status → CDA statusCode
.code /code CDA coding ↔ FHIR CodeableConcept
.performedDateTime /effectiveTime/@value CDA ↔ FHIR Time/Dates
.performedPeriod.start /effectiveTime/low CDA ↔ FHIR Time/Dates
.performedPeriod.end /effectiveTime/high CDA ↔ FHIR Time/Dates
.performer.actor /performer CDA ↔ FHIR Provenance
.performer.onBehalfOf /perfomer/assignedEntity/representedOrganization CDA ↔ FHIR Provenance
.location Service Delivery Location
/participant[@typeCode=”LOC”]
/participantRole
 
.reasonCode Indication
/entryRelationship[@typeCode=”RSON”]
/observation/value
CDA coding ↔ FHIR CodeableConcept
.bodySite /targetSiteCode CDA coding ↔ FHIR CodeableConcept
Annotation
.note
Comment Activity
entryRelationship/act[code@code=”48767-8”]/entryRelationship/act/text
 

1. XPath abbrievated for C-CDA Procedure as:
ClinicalDocument/component/structuredBody/component/section[code/@code=”47519-4”]/entry/procedure

Illustrative example

No examples available (of FHIR to C-CDA) at this time.

Prior work and Expanded Spreadsheets

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