Obligation Discussion
0.5.1 - Working Draft to present the Concept Ideas and Background Details (FO)
Obligation Discussion
0.5.1 - Working Draft to present the Concept Ideas and Background Details (FO)
Obligation Discussion, published by . This guide is not an authorized publication; it is the continuous build for version 0.5.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/obligation/ and changes regularly. See the Directory of published versions
| Official URL: http://v2.hl7.org/fhir/ValueSet/dataExpectation | Version: 0.1.0 | |||
| Active as of 2022-08-17 | Computable Name: VsDataExepectation | |||
Valueset for data expectations
References
http://v2.hl7.org/fhir/CodeSystem/dataExpectation version 📦0.1.0
Expansion performed internally based on codesystem Data Expectation Codes v0.1.0 (CodeSystem)
This value set contains 18 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | expected | expected | data fits to expectations/specification | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | unaltered | preserve | preserve what you get | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | exactly | exactly | exactly what is specified, nothing else | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | modify | modify | allow for modifications of the data | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | assocation | assocation | taken by association | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | equivalent | equivalent | in an equivalent way | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | translate | translate | 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. | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | semantically | translate 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. | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | clinically | translate 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. | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | reference | reference | 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. | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | truncate | cut off data | cut off remaining characters from the data thereby shortening the data | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | more-details | additional details/values | extends the expected data with more/own information, e.g. appartment if street is specified | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | more-structure | additional substructures | provides the data with more granular details, e.g. house number for an address line | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | missing | data is missing/not available | provide a null-flavor/absent reason | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | constant | added 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 | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | unexpected | unexpected values | how to manage unexpected data (as sender or receiver) | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | replaces | new/other values | replaces the expected data by something else | ||
http://v2.hl7.org/fhir/CodeSystem/dataExpectation | consider | consider 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 |