Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
Medium
-
US Core (FHIR)
-
Cross-Group Projects
-
General Guidance
-
many
-
-
Eric Haas/Brett Marquard: 13-0-1
-
Correction
-
Non-substantive
Description
Section 2.1.1.6 Missing Data provides direction for "If the source system does not have data for a required data element (in other words, where the minimum cardinality is > 0)"
#1 stipulates “For non-coded data elements, use the DataAbsentReason Extension in the data type"
#2 stupulates for “For coded data elements:
example, preferred, or extensible binding strengths (CodeableConcept datatypes):
- if the source systems has text but no coded data, only the text element is used.
- if there is neither text or coded data:
-
- use the appropriate “unknown” concept code from the value set if available
- if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System.”
Where are we to put the unknown concept from the DataAbsentReason Code System ?
Directions provided specifies this is to be used when the element cardinality is >0. The requesting system is expecting the coding in the element will represent the data that should go in the expected element based on rules set by the binding strengths.
If the coding is not what is expected, should the DataAbsentReason Extension in the data type be used.
Also, FHIR definition of preferred and extensible bindings does not stipulate that null flavors should be used as alternatives.