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

CodeSystem: Obligation Alone Codes (Experimental)

Official URL: http://v2.hl7.org/fhir/CodeSystem/obligationAlone Version: 0.1.0
Active as of 2026-03-26 Computable Name: ObligationAloneCodes

This is the Obligation CodeSystem (alone) as part of the triplet.

This Code system is referenced in the content logical definition of the following value sets:

Properties

This code system defines the following properties for its concepts

NameCodeURITypeDescription
Parent parent http://hl7.org/fhir/concept-properties#parent code
actor actor code what type of actor
Comment comment http://hl7.org/fhir/concept-properties#comment string comments/remarks

Concepts

This case-sensitive code system http://v2.hl7.org/fhir/CodeSystem/obligationAlone defines the following codes in a Is-A hierarchy:

LvlCodeDisplayDefinitionParentactorComment
1 send send populate with values from somewhere creator prohibited elements can be expressed by 'SHALL NOT send'.
2   from-ui from UI Take the data from UI, so that the user has the ability to enter it. send
3     from-textfield from textfield in UI Take the data from a test input field from-ui too explicit/dedicated, concerns application details
3     from-widget from widget in UI Take the data from a specific widget from-ui too explicit/dedicated, concerns application details
3     from-combobox from combobox in UI Take the data from a combobox from-ui too explicit/dedicated, concerns application details
2   from-store from persistence layer Take data from storage/persistence layer. send
2   from-input from input stream As a router, take data from input stream. send router
2   as-constant constant added as constant to the data, no special treatment done internally send
1 process process/receive Data received is processed as needed for general message consumption, store permitted. consumer elements that are to be ignored can be expressed by 'SHALL NOT process'.
2   follow-up follow-up activity what to do internally
3     display display/present (UI) present the data on a display follow-up
3     store store store/persist the data somewhere follow-up router
4       archive archive store/persist the archive which ensures longlasting access
4       in-database store in a database store in a database too explicit/dedicated, concerns application details
4       in-file store in a file store in a file too explicit/dedicated, concerns application details
3     print print print the data (somewhere) follow-up
3     eval evaluate consider the data in order to interpret other correctly follow-up
3     integrate integrate into data to UPDATE existing data by merging other data with the existing data in a controlled manner follow-up
3     forward forward as a router forward to the next recipient follow-up router
2   respond activity as response what to respond
3     warning return warnings return possible warnings respond
4       error return error return possible errors warning
1 other other obligations other obligations beyond
2   explain explain provide an explanation in a capability statement how this element is handled other