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

ValueSet: Proposed Transport-oriented Obligation Codes VS (Experimental)

Official URL: http://v2.hl7.org/fhir/ValueSet/obligationTransportProposed Version: 0.1.0
Draft as of 2024-05-08 Computable Name: ObligationProposedTransportCodesVS

This valueset represents the proposed obligation codes for managing transport requirements.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://v2.hl7.org/fhir/CodeSystem/obligationProposed
    CodeDisplayDefinition
    SHOULD:sendSHOULD send the instanceConformant applications SHOULD send the instance.
    SHOULD:receiveSHOULD be able to receive the dataConformant applications SHOULD be able to receive the data.
    SHOULD:accept-invalidSHOULD accept invalid dataConformant applications SHOULD accept invalid data.
    SHOULD:reject-invalidSHOULD reject invalid dataConformant applications SHOULD reject invalid data.
    SHALL:sendSHALL send the instanceConformant applications SHALL send the instance.
    SHALL:receiveSHALL be able to receive the dataConformant applications SHALL be able to receive the data.
    SHALL:accept-invalidSHALL accept invalid dataConformant applications SHALL accept invalid data.
    SHALL:reject-invalidSHALL reject invalid dataConformant applications SHALL reject invalid data.
    SHOULDNOT:errorSHOULD NOT return an error to the sender of the dataConformant applications SHOULD NOT reurn an erorr to the sender of the data.
    SHALLNOT:errorSHALL NOT return an error to the sender of the dataConformant applications SHALL NOT reurn an erorr to the sender of the data.

 

Expansion

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

This value set contains 10 concepts.

CodeSystemDisplayDefinition
  SHOULD:sendhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHOULD send the instance

Conformant applications SHOULD send the instance.

  SHOULD:receivehttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHOULD be able to receive the data

Conformant applications SHOULD be able to receive the data.

  SHOULD:accept-invalidhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHOULD accept invalid data

Conformant applications SHOULD accept invalid data.

  SHOULD:reject-invalidhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHOULD reject invalid data

Conformant applications SHOULD reject invalid data.

  SHALL:sendhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHALL send the instance

Conformant applications SHALL send the instance.

  SHALL:receivehttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHALL be able to receive the data

Conformant applications SHALL be able to receive the data.

  SHALL:accept-invalidhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHALL accept invalid data

Conformant applications SHALL accept invalid data.

  SHALL:reject-invalidhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHALL reject invalid data

Conformant applications SHALL reject invalid data.

  SHOULDNOT:errorhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHOULD NOT return an error to the sender of the data

Conformant applications SHOULD NOT reurn an erorr to the sender of the data.

  SHALLNOT:errorhttp://v2.hl7.org/fhir/CodeSystem/obligationProposedSHALL NOT return an error to the sender of the data

Conformant applications SHALL NOT reurn an erorr to the sender of the 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