Extensions for Using Data Elements from FHIR STU3 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R4B - Downloaded Version null See the Directory of published versions

ValueSet: R3V3AcknowledgementTypeForR4B

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-v3-AcknowledgementType-for-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3V3AcknowledgementTypeForR4B

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/v3-AcknowledgementType|2016-11-11 for use in FHIR R4B.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/v3-AcknowledgementType|2016-11-11 as defined in FHIR STU3 in FHIR R4B.

The source value set is bound to the following FHIR STU3 elements:

Across FHIR versions, the value set has been mapped as:

  • http://hl7.org/fhir/ValueSet/v3-AcknowledgementType|2016-11-11
  • http://terminology.hl7.org/ValueSet/v3-AcknowledgementType|2018-08-12

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments: All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (6). FHIR ValueSet http://hl7.org/fhir/ValueSet/v3-AcknowledgementType|2016-11-11, defined in FHIR STU3 does not have any mapping to FHIR R4B

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://hl7.org/fhir/v3/AcknowledgementType version 📍2016-11-11
    CodeDisplayDefinition
    AAApplication Acknowledgement AcceptReceiving application successfully processed message.
    AEApplication Acknowledgement ErrorReceiving application found error in processing message. Sending error response with additional error detail information.
    ARApplication Acknowledgement RejectReceiving application failed to process message for reason unrelated to content or format. Original message sender must decide on whether to automatically send message again.
    CAAccept Acknowledgement Commit AcceptReceiving message handling service accepts responsibility for passing message onto receiving application.
    CEAccept Acknowledgement Commit ErrorReceiving message handling service cannot accept message for any other reason (e.g. message sequence number, etc.).
    CRAccept Acknowledgement Commit RejectReceiving message handling service rejects message if interaction identifier, version or processing mode is incompatible with known receiving application role information.

 

Expansion

This value set expansion contains 6 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/v3/AcknowledgementType2016-11-11  AAApplication Acknowledgement AcceptReceiving application successfully processed message.
http://hl7.org/fhir/v3/AcknowledgementType2016-11-11  AEApplication Acknowledgement ErrorReceiving application found error in processing message. Sending error response with additional error detail information.
http://hl7.org/fhir/v3/AcknowledgementType2016-11-11  ARApplication Acknowledgement RejectReceiving application failed to process message for reason unrelated to content or format. Original message sender must decide on whether to automatically send message again.
http://hl7.org/fhir/v3/AcknowledgementType2016-11-11  CAAccept Acknowledgement Commit AcceptReceiving message handling service accepts responsibility for passing message onto receiving application.
http://hl7.org/fhir/v3/AcknowledgementType2016-11-11  CEAccept Acknowledgement Commit ErrorReceiving message handling service cannot accept message for any other reason (e.g. message sequence number, etc.).
http://hl7.org/fhir/v3/AcknowledgementType2016-11-11  CRAccept Acknowledgement Commit RejectReceiving message handling service rejects message if interaction identifier, version or processing mode is incompatible with known receiving application role information.

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