C-CDA on FHIR
2.0.0-ballot - STU 2 Ballot United States of America flag

This page is part of the C-CDA on FHIR Implementation Guide (v2.0.0-ballot: STU 2 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 1.2.0. For a full list of available versions, see the Directory of published versions

FHIR to C-CDA Vital Signs

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

FHIR Vitals that are grouped into a panel using the memberOf property are mapped to a CDA Vital Signs Organizer.

FHIR Observation Panel to C-CDA Vital Signs Organizer

FHIR
Vital Signs Observation		 C-CDA¹
Vital SignsOrganizer		 Transform Steps
.identifier /id FHIR identifier ↔ CDA id
.category = vital-signs    
.code = 85353-1   CDA coding ↔ FHIR CodeableConcept
.status /statusCode FHIR Observation Status → CDA Result Status
CDA requires 'completed', which will usually be the case
.effectiveDateTime /effectiveTime Use value
.effectivePeriod /effectiveTime Use high and low
CDA ↔ FHIR Time/Dates
.hasMember component Reference to each vital sign observation

FHIR Observation to C-CDA Vital Signs Observation

FHIR
Vital Signs Observation		 C-CDA¹
Vital Sign Observation		 Transform Steps
.identifier /id FHIR identifier ↔ CDA id
.code /code FHIR CodeableConcept ↔ CDA coding
.status /statusCode Set to completed
.effectiveDateTime /effectiveTime Use value
.effectivePeriod /effectiveTime Use high and low
CDA ↔ FHIR Time/Dates
.valueQuantity /value If not null
FHIR ↔ CDA Quantities
.dataAbsentReason /value@nullFlavor If value is null
FHIR DataAbsentReason ↔ CDA NullFlavor
.interpretation /interpretationCode FHIR CodeableConcept ↔ CDA coding
.method /methodCode FHIR CodeableConcept ↔ CDA coding
.bodySite /targetSiteCode FHIR CodeableConcept ↔ CDA coding

Illustrative example