Obligation Discussion
0.4.1 - Working Draft to present the Concept Ideas and Background Details (FO)

Obligation Discussion - Local Development build (v0.4.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: Data Expectation ValueSet (Experimental)

Official URL: http://v2.hl7.org/fhir/ValueSet/dataExpectation Version: 0.1.0
Active as of 2022-08-17 Responsible: FO Computable Name: VsDataExepectation

Valueset for data expectations


Logical Definition (CLD)



Expansion based on codesystem Data Expectation Codes v0.1.0 (CodeSystem)

This value set contains 18 concepts.


data fits to expectations/specification


preserve what you get


exactly what is specified, nothing else


allow for modifications of the data


taken by association


in an equivalent way


Data received is preserved by 1:1 mapping/translation to an internal value that is semantically equivalent, that preserves the temporal aspect of the translation.

  semanticallyhttp://v2.hl7.org/fhir/CodeSystem/dataExpectationtranslate semantically

Two concepts are semantically equivalent if they can substitute for each other in the defined use case with no loss of information used to define the concept.

  clinicallyhttp://v2.hl7.org/fhir/CodeSystem/dataExpectationtranslate clinically

Two concepts are clinically equivalent if they can substitute for each other in the defined use case with no impact on clinical interpretation by a trained clinician. This may include further refinements based on the specific domain, e.g., for Lab use case, this would require interpretation that includes the impact of differences in normal ranges.


Use referenced data based on stored pointer; stored data is displayed by linking to the corresponding stored value most often the case for data elements that are STORED EXACT by ASSOCIATION.

  truncatehttp://v2.hl7.org/fhir/CodeSystem/dataExpectationcut off data

cut off remaining characters from the data thereby shortening the data

  more-detailshttp://v2.hl7.org/fhir/CodeSystem/dataExpectationadditional details/values

extends the expected data with more/own information, e.g. appartment if street is specified

  more-structurehttp://v2.hl7.org/fhir/CodeSystem/dataExpectationadditional substructures

provides the data with more granular details, e.g. house number for an address line

  missinghttp://v2.hl7.org/fhir/CodeSystem/dataExpectationdata is missing/not available

provide a null-flavor/absent reason

  constanthttp://v2.hl7.org/fhir/CodeSystem/dataExpectationadded as a constant

this value has no valid representation or meaning in the sending application, it is just added because it is required to be there

  unexpectedhttp://v2.hl7.org/fhir/CodeSystem/dataExpectationunexpected values

how to manage unexpected data (as sender or receiver)

  replaceshttp://v2.hl7.org/fhir/CodeSystem/dataExpectationnew/other values

replaces the expected data by something else

  considerhttp://v2.hl7.org/fhir/CodeSystem/dataExpectationconsider unexpected values

take vare of values that are coming but not described/specified. Allows for warnings

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code