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/obligationContentConsumptionProposed | Version: 0.1.0 | |||
Draft as of 2024-05-08 | Computable Name: ObligationProposedContentConsumptionCodesVS |
This valueset represents the proposed obligation codes for consuming the content.
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
Code | Display | Definition |
MAY:persist | MAY store the data | Conformant applications MAY store the data. |
MAY:modify | MAY modify the data | Conformant applications MAY, i.e. are allowed to modify the data. |
MAY:print | MAY print data | Conformant applications MAY print the data. |
SHOULD:(persist)in-database | SHOULD store the data in a database | Conformant applications are asked to store the data in a database. |
SHOULD:process | SHOULD process the data | Conformant applications SHOULD process the data in some meaningful way. |
SHOULD:display | SHOULD display the data | Conformant applications SHOULD display the data in some meaningful way. |
SHOULD:document | SHOULD document how the data is used | Conformant applications SHOULD document the way the data is used in some (meaningful) way. |
SHOULD:print | SHOULD print data | Conformant applications SHOULD print the data. |
SHALL:document | SHALL document how the data is used | Conformant applications SHALL document the way the data is used in some (meaningful) way. |
SHALL:print | SHALL print data | Conformant applications SHALL print the data. |
SHALL:persist | SHALL store the data somewhere | Conformant applications SHALL store the data in some way. |
SHALL:persist:exactly | SHALL store the data somewhere, but exactly as is sent | Conformant applications SHALL store the data in a way that the originally data from the instance can be reestablished. |
MAYNOT:process | MAY NOT process data | Conformant applications MAY NOT process data, aka of ignoring. |
SHOULDNOT:process | SHOULD NOT process the data | Conformant applications SHOULD NOT process the data in some meaningful way. |
SHOULDNOT:modify | SHOULD NOT modify the data | Conformant applications SHOULD NOT modiify the data in any way. |
SHALLNOT:process | SHALL NOT process the data | Conformant applications SHALL NOT process the data in some meaningful way. |
SHALLNOT:modify | SHALL NOT modify the data | Conformant applications SHALL NOT modiify the data in any way. |
SHALLNOT:follow-up:truncate | SHALL NOT truncate data | Conformant applications SHALL NOT cut off data. |
Expansion based on codesystem Proposed Obligation Codes v0.1.0 (CodeSystem)
This value set contains 18 concepts.
Code | System | Display | Definition |
MAY:persist | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | MAY store the data | Conformant applications MAY store the data. |
MAY:modify | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | MAY modify the data | Conformant applications MAY, i.e. are allowed to modify the data. |
MAY:print | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | MAY print data | Conformant applications MAY print the data. |
SHOULD:(persist)in-database | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD store the data in a database | Conformant applications are asked to store the data in a database. |
SHOULD:process | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD process the data | Conformant applications SHOULD process the data in some meaningful way. |
SHOULD:display | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD display the data | Conformant applications SHOULD display the data in some meaningful way. |
SHOULD:document | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD document how the data is used | Conformant applications SHOULD document the way the data is used in some (meaningful) way. |
SHOULD:print | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD print data | Conformant applications SHOULD print the data. |
SHALL:document | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL document how the data is used | Conformant applications SHALL document the way the data is used in some (meaningful) way. |
SHALL:print | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL print data | Conformant applications SHALL print the data. |
SHALL:persist | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL store the data somewhere | Conformant applications SHALL store the data in some way. |
SHALL:persist:exactly | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL store the data somewhere, but exactly as is sent | Conformant applications SHALL store the data in a way that the originally data from the instance can be reestablished. |
MAYNOT:process | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | MAY NOT process data | Conformant applications MAY NOT process data, aka of ignoring. |
SHOULDNOT:process | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD NOT process the data | Conformant applications SHOULD NOT process the data in some meaningful way. |
SHOULDNOT:modify | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHOULD NOT modify the data | Conformant applications SHOULD NOT modiify the data in any way. |
SHALLNOT:process | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL NOT process the data | Conformant applications SHALL NOT process the data in some meaningful way. |
SHALLNOT:modify | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL NOT modify the data | Conformant applications SHALL NOT modiify the data in any way. |
SHALLNOT:follow-up:truncate | http://v2.hl7.org/fhir/CodeSystem/obligationProposed | SHALL NOT truncate data | Conformant applications SHALL NOT cut off 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 |