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

ValueSet: Proposed Obligation Codes VS (complete) (Experimental)

Official URL: http://v2.hl7.org/fhir/ValueSet/obligationProposed Version: 0.1.0
Draft as of 2026-03-26 Computable Name: ObligationProposedCodesVS

This valueset represents the proposed obligation codes.

References

Logical Definition (CLD)

 

Expansion

Expansion performed internally based on codesystem Proposed Obligation Codes v0.1.0 (CodeSystem)

This value set contains 177 concepts

SystemCodeDisplay (en)DefinitionJSONXML
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  NegationNegationNegate the meaning of the concepts that inherit 'negation'. (Negation is not negated again.)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAYNOTMAYNOTIt is to the developers choice whether an element is probably not supported.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULDNOTSHOULD NOTit is a recommendation NOT to take care of this element (for some reasons)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOTSHALL NOTit is forbidden to handle this element
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:populate:more-detailsSHALL NOT populate more data than is specifiedConformant applications SHALL NOT populatae more data than is specified. The specification is closed.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:populate:missingSHALL NOT populate info about missing data, ie. data absent reasonsConformant applications SHALL NOT populate a reason for missing information.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v3-mv3: Mmandatory in HL7 V3
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:follow-up:truncateSHALL NOT truncate dataConformant applications SHALL NOT cut off data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:(populate):in-narrativeSHALL NOT add to narrativeConformant applications SHALL NOT add this data to the narrative.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:processSHALL NOT process the dataConformant applications SHALL NOT process the data in some meaningful way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:modifySHALL NOT modify the dataConformant applications SHALL NOT modiify the data in any way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:errorSHALL NOT return an error to the sender of the dataConformant applications SHALL NOT reurn an erorr to the sender of the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v3-xv3: Xforbidden in HL7 V3
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULDNOT:processSHOULD NOT process the dataConformant applications SHOULD NOT process the data in some meaningful way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULDNOT:modifySHOULD NOT modify the dataConformant applications SHOULD NOT modiify the data in any way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULDNOT:errorSHOULD NOT return an error to the sender of the dataConformant applications SHOULD NOT reurn an erorr to the sender of the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v2-xv2: Xforbidden in v2
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v2-bv2: Bbackwards use in v2 only
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v2-wv2: Wwithdrawn use in v2 only
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAYNOT:processMAY NOT process dataConformant applications MAY NOT process data, aka of ignoring.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  Verbsconformance verbsConformance verbs are to be used to define the requirement level that is the foundation to indicate what has to be tested.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAYMAYit is to the developers choice whether an element is supported or not
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULDSHOULDIt is a recommendation to take care of this element
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLSHALLThis verb denotes a testable requirement.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:(populate)from-uiSHALL populate data taken from uiConformant applications SHALL take data from a UI and provide it.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:(populate)from-ui:more-detailsSHALL populate with data taken from ui perhaps with more detailsConformant applications SHALL take data from a UI and bring it into the instance. It is allowed to provide more details then specified.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:sendSHALL send the instanceConformant applications SHALL send the instance.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:persistSHALL store the data somewhereConformant applications SHALL store the data in some way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:persist:exactlySHALL store the data somewhere, but exactly as is sentConformant applications SHALL store the data in a way that the originally data from the instance can be reestablished.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:printSHALL print dataConformant applications SHALL print the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:documentSHALL document how the data is usedConformant applications SHALL document the way the data is used in some (meaningful) way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:reject-invalidSHALL reject invalid dataConformant applications SHALL reject invalid data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:accept-invalidSHALL accept invalid dataConformant applications SHALL accept invalid data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:receiveSHALL be able to receive the dataConformant applications SHALL be able to receive the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v2-rv2: Rrequired in v2.x
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v2-rev2: RErequired but may be empty in v2.x
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v3-rv3: Rrequired in HL7 V3
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  xDT-MxDT: MMUSS in xDT (unbedingtes Mussfeld)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  xDT-mxDT: mmuss in xDT (bedingtes Mussfeld)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  xDT-KxDT: KKANN in xDT (unbedingts KANNfeld)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  xDT-kxDT: kkann in xDT (bedingtes Kannfeld)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:(populate)from-uiSHOULD populate with data taken from uiConformant applications SHOULD take data from a UI and provide it.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:(persist)in-databaseSHOULD store the data in a databaseConformant applications are asked to store the data in a database.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:printSHOULD print dataConformant applications SHOULD print the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:documentSHOULD document how the data is usedConformant applications SHOULD document the way the data is used in some (meaningful) way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:displaySHOULD display the dataConformant applications SHOULD display the data in some meaningful way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:displaySHALL display the dataConformant applications SHALL display the data in some meaningful way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:reject-invalidSHOULD reject invalid dataConformant applications SHOULD reject invalid data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:accept-invalidSHOULD accept invalid dataConformant applications SHOULD accept invalid data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:receiveSHOULD be able to receive the dataConformant applications SHOULD be able to receive the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:populateMAY populate with dataConformant applications MAY take and provide data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:populate:missingMAY populate data element with why orig data is missingConformant applications MAY populate the element why the original data is missing.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:populateSHOULD populate with dataConformant applications SHOULD take and provide data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:(populate)into-narrativeMAY populate into-narrativeConformant applications MAY populate element into narrative text as well.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:(populate)into-narrativeSHOULD populate into-narrativeConformant applications SHOULD populate element into narrative text as well.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:(populate)into-narrativeSHALL populate into-narrativeConformant applications SHALL populate element into narrative text as well.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:populateSHALL populate with dataConformant applications SHOULD take and provide data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ihe-r2IHE: R2R2 in IHE v2.x specs
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:(populate)from-uiMAY populate with data taken from uiConformant applications MAY take data from a UI and provide it.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:persistMAY store the dataConformant applications MAY store the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:populate:more-structureMAY populate the data in more structured wayConformant applications are allowed to populate the data with more structure. For example, to split an address line into streetname and house number.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:modifyMAY modify the dataConformant applications MAY, i.e. are allowed to modify the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:printMAY print dataConformant applications MAY print the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MAY:processMAY process the dataConformant applications MAY process the data somehow.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:processSHOULD process the dataConformant applications SHOULD process the data in some meaningful way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALL:processSHALL process the dataConformant applications SHALL process the data in some meaningful way.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  FunctionalTypeFunctional Type of RequirementFunctional Type of Requirement
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  functionalfunctionalfunctional requirement
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  internalinternal functionalfunction that operates on the internal data management
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  returnreturn functionalfunctional requirement on direct returns
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  responseresponse functionfunctional requirement to prepare responses
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  forwardforwarding functionfunctional requirement to forward data
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  datadatadata requirement
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  TestableType of TestingType of Testing
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  testabletestablerequirement is testable
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  testableByMachinemachine testablerequirement is testable by a machine
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  testableByHumanhuman testablerequirement is testable by a human (inspection)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  withChecklistchecklistrequirement is testable by using a checklist
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  notTestabletestablerequirement is not testable
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ActorTypeType of ActorAn actor can operate in two ways: with the content itself, or as a manager of the instance.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  transporttransporthandle the transport of data once the instance is available/accessible
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  sendersendersender (transmitter) of data
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  sendsendconvey instance with values to somewhere
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  receiverreceiverreceiver of data
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ConsumerObligationsResource Consumer ObligationsObligation for Consumer
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  receivereceivereceive data form somewhere
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  processprocesshandle data from instances as needed for general message consumption, store permitted.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  follow-upfollow-up activitywhat to do internally
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  displaydisplay/present (UI)present the data on a display
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  persistpersistpersist/store the data somewhere
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  archivearchivepersist/store the archive which ensures longlasting access
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  in-databasepersist in a databasepersist in a database
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  in-filestore in a filestore in a file
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  printprintprint the data (somewhere)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  evalevaluateconsider the data in order to interpret other correctly
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  integrateintegrate into datato UPDATE existing data by merging other data with the existing data in a controlled manner
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  respondactivity as responsewhat to respond
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  warningreturn warningsreturn possible warnings
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  errorreturn errorreturn possible errors
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  reject-invalidreject invalid datareject if data is invalid
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  accept-invalidaccept invalid dataaccept if data is invalid
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  routerrouterrouter of data: shall be receiver and sender!
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  from-inputfrom input streamAs a router, take data from input stream.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ExchangerObligationsResource Exchanger Obligationsneeds clarification ...
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  routeroute forwardas a router forward to the next recipient
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  contentcontent mngmtmanage the data itself
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  creatorcreatorcreator of data
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  populatepopulatepopulate with values from somewhere
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  from-uifrom UITake the data from UI, so that the user has the ability to enter it.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  from-storefrom persistence layerTake data from storage/persistence layer.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  generategenerate this dataThis data can be generated.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  from-othergenerate from other valuesThis data can be generated from other data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  sequencegenerate a sequence number
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  as-constantconstantadded as constant to the data, no special treatment done internally
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  into-narrativenarrativeadded to the narrative, no special treatment done internally
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  DataObligationObligations on DataData Obligations
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  expectedexpecteddata fits to expectations/specification
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  unalteredpreservepreserve what you get
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  exactlyexactlyexactly what is specified, nothing else
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  modifymodifyallow for modifications of the data
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  assocationassocationtaken by association
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  equivalentequivalentin an equivalent way
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  translatetranslateData received is preserved by 1:1 mapping/translation to an internal value that is semantically equivalent, that preserves the temporal aspect of the translation.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  semanticallytranslate semanticallyTwo concepts are semantically equivalent if they can substitute for each other in the defined use case with no loss of information used to define the concept.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  clinicallytranslate clinicallyTwo concepts are clinically equivalent if they can substitute for each other in the defined use case with no impact on clinical interpretation by a trained clinician. This may include further refinements based on the specific domain, e.g., for Lab use case, this would require interpretation that includes the impact of differences in normal ranges.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  referencereferenceUse referenced data based on stored pointer; stored data is displayed by linking to the corresponding stored value most often the case for data elements that are STORED EXACT by ASSOCIATION.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  truncatecut off datacut off remaining characters from the data thereby shortening the data
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  more-detailsadditional details/valuesextends the expected data with more/own information, e.g. appartment if street is specified
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  more-structureadditional substructuresprovides the data with more granular details, e.g. house number for an address line
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  missingdata is missing/not availableprovide a null-flavor/absent reason
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  constantadded as a constantthis value has no valid representation or meaning in the sending application, it is just added because it is required to be there
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  unexpectedunexpected valueshow to manage unexpected data (as sender or receiver)
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  replacesnew/other valuesreplaces the expected data by something else
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  considerconsider unexpected valuestake vare of values that are coming but not described/specified. Allows for warnings
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  consumerconsumerConsumer of data
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ActorActor of CommunicationActor, i.e. indirect direction of communication
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  bothsender and/or receiverboth: sender+receiver resp. creator+consumer
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  DeviceDevice for ActivityDevice to be used for the activity
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  screenscreenscreen/display
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  wideScreenwide screenwide screen/display
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  radScreenradiologic screenscreen/display capable of showing radiologic results
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  printerprinterprinter
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  laserPrinterlaser printerlaser printer
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  matrixPrintermatrix printermatrix printer
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  portableStorageportable storage deviceportable storage device
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  usbStickusb stickUSB Stick
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  tapeDrivetape drivetape drive
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  MediaMediadifferent media to be used with specialised devices
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  paperpaperpaper
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  stickstickstick
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  discdiscdisc
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  tapetapetape
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ElementLevelLevel of ApplicationOn which level to apply this obligation: root, node, or leaf
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  rooton root nodeapply obligation on root node only
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  nodeon any nodeapply on any node that is not root or leaf
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  leafon leaf nodeapply on leaf node only
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  allon all levelsapplication on all levels possible
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  notRootall but rootapply on non-root nodes only
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  notLeafall but leafapply on non-leaf nodes
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ActivityActivityActivities, aka of general obligation
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  FunctionalObligationsFunctional ObligationsFunctional Obligation describing processsing functionalities
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ProducerObligationsResource Producer Obligations
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  OtherObligationsResource Other ObligationsOther obligations beyond what has been described above.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  explainexplainprovide an explanation in a capability statement how this element is handled
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  documentdocumentdocument the use of this element in a separate document
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  CombinedObligationscombined obligationsThe children can be used to encode obligations for data elements. Terms in parenthesis are shown for readability. This list is not complete, and only provides some reasonable samples.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULDNOT:(populate)into-narrativeSHOULD NOT populate into-narrativeConformant applications SHOULD NOT populate element into narrative text.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHALLNOT:(populate)into-narrativeSHALL NOT populate into-narrativeConformant applications SHALL NOT populate element into narrative text.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:sendSHOULD send the instanceConformant applications SHOULD send the instance.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  SHOULD:persistSHOULD store the dataConformant applications SHOULD store the data.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ForeignStandardsconcept codes from other standardsOther standards use specific terms for optionality/usage that should be conceptualized here.
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v2v2 concept codesoptionality/usage codes from v2
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  v3V3 concept codesoptionality/usage codes from V3/CDA
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  iheIHE concept codesoptionality/usage codes from IHE
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ihe-rIHE: Rrequired in IHE v2.x specs
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  ihe-xIHE: XX in IHE v2.x specs
http://v2.hl7.org/fhir/CodeSystem/obligationProposed  xDTGerman xDT standardsThe German xDT standard family has a very specific set of codes and is just presented here for completeness and demonstration purposes

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