FHIR Data Absent Reason to C-CDA NullFlavor

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. For a full list of available versions, see the Directory of published versions

ConceptMap: FHIR Data Absent Reason to C-CDA NullFlavor

Official URL: http://hl7.org/fhir/us/ccda/ConceptMap/FC-DataAbsentReasonNullFlavor				Version: 1.2.0
Active as of 2024-03-12				Computable Name: FHIRtoCCDADataAbsentReasonNullFlavor

FHIR Data Absent Reason to C-CDA NullFlavor. Adapted from https://hl7.org/fhir/R4/cm-data-absent-reason-v3.html but several key changes have been made. Note that this prior concept map (from R4) is no longer included in current FHIR build.

Mapping from DataAbsentReason to NullFlavor

ACTIVE. Published on 2024-03-12 19:27:21+0000 by HL7 International / Cross-Group Projects (HL7 International / Cross-Group Projects: http://www.hl7.org/Special/com...).

FHIR Data Absent Reason to C-CDA NullFlavor. Adapted from https://hl7.org/fhir/R4/cm-data-absent-reason-v3.html but several key changes have been made. Note that this prior concept map (from R4) is no longer included in current FHIR build.

Group 1Mapping from DataAbsentReason to NullFlavor

Source Code

Relationship

Target Code

Comment

unknown

maps to wider concept

NI (NoInformation)

In CDA, 'UNK' means 'a proper value is applicable, but not known.' Guidance has been to use this when the value is known to exist and to use the broader 'NI' when no specific information about why the value is unknown. FHIR's data absent reason of 'unknown' better maps to 'NI'.

asked-unknown (Asked But Unknown)

is equivalent to

ASKU (asked but unknown)

temp-unknown (Temporarily Unknown)

is equivalent to

NAV (temporarily unavailable)

not-asked

is equivalent to

NASK (not asked)

asked-declined (Asked But Declined)

maps to wider concept

UNK (unknown)