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/obligationTransportProposed | Version: 0.1.0 | |||
| Draft as of 2026-03-26 | Computable Name: ObligationProposedTransportCodesVS | |||
This valueset represents the proposed obligation codes for managing transport requirements.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed version 📦0.1.0| Code | Display | Definition |
| SHOULD:send | SHOULD send the instance | Conformant applications SHOULD send the instance. |
| SHOULD:receive | SHOULD be able to receive the data | Conformant applications SHOULD be able to receive the data. |
| SHOULD:accept-invalid | SHOULD accept invalid data | Conformant applications SHOULD accept invalid data. |
| SHOULD:reject-invalid | SHOULD reject invalid data | Conformant applications SHOULD reject invalid data. |
| SHALL:send | SHALL send the instance | Conformant applications SHALL send the instance. |
| SHALL:receive | SHALL be able to receive the data | Conformant applications SHALL be able to receive the data. |
| SHALL:accept-invalid | SHALL accept invalid data | Conformant applications SHALL accept invalid data. |
| SHALL:reject-invalid | SHALL reject invalid data | Conformant applications SHALL reject invalid data. |
| SHOULDNOT:error | SHOULD NOT return an error to the sender of the data | Conformant applications SHOULD NOT reurn an erorr to the sender of the data. |
| SHALLNOT:error | SHALL NOT return an error to the sender of the data | Conformant applications SHALL NOT reurn an erorr to the sender of the data. |
Expansion performed internally based on codesystem Proposed Obligation Codes v0.1.0 (CodeSystem)
This value set contains 10 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD:send | SHOULD send the instance | Conformant applications SHOULD send the instance. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD:receive | SHOULD be able to receive the data | Conformant applications SHOULD be able to receive the data. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD:accept-invalid | SHOULD accept invalid data | Conformant applications SHOULD accept invalid data. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD:reject-invalid | SHOULD reject invalid data | Conformant applications SHOULD reject invalid data. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL:send | SHALL send the instance | Conformant applications SHALL send the instance. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL:receive | SHALL be able to receive the data | Conformant applications SHALL be able to receive the data. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL:accept-invalid | SHALL accept invalid data | Conformant applications SHALL accept invalid data. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL:reject-invalid | SHALL reject invalid data | Conformant applications SHALL reject invalid data. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULDNOT:error | SHOULD NOT return an error to the sender of the data | Conformant applications SHOULD NOT reurn an erorr to the sender of the data. | ||
http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALLNOT:error | SHALL NOT return an error to the sender of the data | Conformant applications SHALL NOT reurn an erorr to the sender of the data. |
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 |