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
Official URL: http://v2.hl7.org/fhir/ValueSet/obligationAlone | Version: 0.1.0 | |||
Active as of 2022-08-17 | Responsible: FO | Computable Name: VsObligationAloneCodes |
Valueset for obligations (alone)
References
http://v2.hl7.org/fhir/CodeSystem/obligationAlone
Expansion based on codesystem Obligation Alone Codes v0.1.0 (CodeSystem)
This value set contains 24 concepts.
Code | System | Display | Definition |
send | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | send | populate with values from somewhere |
from-ui | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | from UI | Take the data from UI, so that the user has the ability to enter it. |
from-textfield | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | from textfield in UI | Take the data from a test input field |
from-widget | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | from widget in UI | Take the data from a specific widget |
from-combobox | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | from combobox in UI | Take the data from a combobox |
from-store | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | from persistence layer | Take data from storage/persistence layer. |
from-input | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | from input stream | As a router, take data from input stream. |
as-constant | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | constant | added as constant to the data, no special treatment done internally |
process | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | process/receive | Data received is processed as needed for general message consumption, store permitted. |
follow-up | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | follow-up activity | what to do internally |
display | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | display/present (UI) | present the data on a display |
store | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | store | store/persist the data somewhere |
archive | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | archive | store/persist the archive which ensures longlasting access |
in-database | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | store in a database | store in a database |
in-file | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | store in a file | store in a file |
http://v2.hl7.org/fhir/CodeSystem/obligationAlone | print the data (somewhere) | ||
eval | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | evaluate | consider the data in order to interpret other correctly |
integrate | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | integrate into data | to UPDATE existing data by merging other data with the existing data in a controlled manner |
forward | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | forward | as a router forward to the next recipient |
respond | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | activity as response | what to respond |
warning | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | return warnings | return possible warnings |
error | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | return error | return possible errors |
other | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | other obligations | other obligations beyond |
explain | http://v2.hl7.org/fhir/CodeSystem/obligationAlone | explain | provide an explanation in a capability statement how this element is handled |
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 |