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/ConceptMap/MapOriginalToProposed | Version: 5.0.0 | |||
Draft as of 2024-04-25 | Responsible: FO |
Realm: |
Computable Name: MapOriginalToProposed |
A mapping between the FHIR obligation codes, 5.0.0, and the ones proposed here.
The purpose is just to help to understand how current codes would be used in the future
Mapping from http://hl7.org/fhir/CodeSystem/obligation|5.1.0-cibuild to Proposed Obligation Codes VS (active only)
DRAFT (not intended for production usage). Published on 2024-04-25 by FO.
A mapping between the FHIR obligation codes, 5.0.0, and the ones proposed here.
Group 1 Mapping from Obligation Codes (version 5.1.0) to Proposed Obligation Codes
Source Code | Relationship | Target Code | Comment |
SHALL:able-to-populate | is equivalent to | SHALL:populate (SHALL populate with data) | the ability to populate something has to be proven by provding the data |
SHOULD:able-to-populate | is related to | SHOULD:populate (SHOULD populate with data) | |
MAY:able-to-populate | is related to | MAY:populate (MAY populate with data) | |
SHALL:populate | is equivalent to | SHALL:populate (SHALL populate with data) | |
SHOULD:populate | is equivalent to | SHOULD:populate (SHOULD populate with data) | |
SHALL:in-narrative | is equivalent to | SHALL:(populate)into-narrative (SHALL populate into-narrative) | specific for FHIR |
SHOULD:in-narrative | is equivalent to | SHOULD:(populate)into-narrative (SHOULD populate into-narrative) | specific for FHIR |
MAY:in-narrative | is equivalent to | MAY:(populate)into-narrative (MAY populate into-narrative) | specific for FHIR |
SHALL:exclude-narrative | is equivalent to | SHALLNOT:(populate)into-narrative (SHALL NOT populate into-narrative) | specific for FHIR |
SHOULD:exclude-narrative | is equivalent to | SHOULDNOT:(populate)into-narrative (SHOULD NOT populate into-narrative) | specific for FHIR |
SHALL:user-input | is equivalent to | SHALL:(populate)from-ui (SHALL populate data taken from ui) | |
SHOULD:user-input | is equivalent to | SHOULD:(populate)from-ui (SHOULD populate with data taken from ui) | |
MAY:user-input | is equivalent to | MAY:(populate)from-ui (MAY populate with data taken from ui) | |
SHALL:explain | is equivalent to | SHALL:document (SHALL document how the data is used) | |
SHOULD:explain | is equivalent to | SHOULD:document (SHOULD document how the data is used) | |
SHALL:persist | is equivalent to | SHALL:persist (SHALL store the data somewhere) | |
SHOULD:persist | is equivalent to | SHOULD:persist (SHOULD store the data) | |
MAY:persist | is equivalent to | MAY:persist (MAY store the data) | |
SHALL:no-alter | is equivalent to | SHALLNOT:modify (SHALL NOT modify the data) | instead of duplicate (inverse) codes the negation should be used |
SHOULD:no-alter | is equivalent to | SHOULDNOT:modify (SHOULD NOT modify the data) | instead of duplicate (inverse) codes the negation should be used |
MAY:alter | is equivalent to | MAY:modify (MAY modify the data) | |
SHALL:no-error | is equivalent to | SHALLNOT:error (SHALL NOT return an error to the sender of the data) | |
SHOULD:no-error | is equivalent to | SHOULDNOT:error (SHOULD NOT return an error to the sender of the data) | |
SHALL:reject-invalid | is equivalent to | SHALL:reject-invalid (SHALL reject invalid data) | |
SHOULD:reject-invalid | is equivalent to | SHOULD:reject-invalid (SHOULD reject invalid data) | |
SHALL:accept-invalid | is equivalent to | SHALL:accept-invalid (SHALL accept invalid data) | |
SHOULD:accept-invalid | is equivalent to | SHOULD:accept-invalid (SHOULD accept invalid data) | |
SHALL:handle | is equivalent to | SHALL:process (SHALL process the data) | |
SHOULD:handle | is equivalent to | SHOULD:process (SHOULD process the data) | |
SHALL:display | is equivalent to | SHALL:display (SHALL display the data) | |
SHOULD:display | is equivalent to | SHOULD:display (SHOULD display the data) | |
MAY:display | is equivalent to | SHOULD:display (SHOULD display the data) | |
SHALL:process | is equivalent to | SHALL:process (SHALL process the data) | what is the difference to SHALL:handle? |
SHOULD:process | is equivalent to | SHOULD:process (SHOULD process the data) | |
MAY:process | is related to | MAY:process (MAY process the data) | |
SHALL:print | is equivalent to | SHALL:print (SHALL print data) | |
SHOULD:print | is equivalent to | SHOULD:print (SHOULD print data) | |
MAY:print | is equivalent to | MAY:print (MAY print data) | |
SHALL:ignore | is equivalent to | SHALLNOT:process (SHALL NOT process the data) | |
SHOULD:ignore | is equivalent to | SHOULDNOT:process (SHOULD NOT process the data) | |
MAY:ignore | is equivalent to | MAYNOT:process (MAY NOT process data) | MAYNOT normally does not make sense. |
v2-re | is equivalent to | SHALL:process (SHALL process the data) | |
ihe-r2 | is equivalent to | SHALL:process (SHALL process the data) | |
std | is equivalent to | SHALL:process (SHALL process the data) |