Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

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

ValueSet: R5UdiEntryTypeForR4

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-udi-entry-type-for-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 2 Responsible: Orders and Observations Computable Name: R5UdiEntryTypeForR4

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/udi-entry-type 5.0.0 for use in FHIR R4 that is appropriate for use but unavailable in http://hl7.org/fhir/ValueSet/udi-entry-type|4.0.1.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/udi-entry-type|5.0.0 as defined in FHIR R5 in FHIR R4.

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

  • Device.udiCarrier.entryType as Required

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

  • http://hl7.org/fhir/ValueSet/udi-entry-type|5.0.0
  • http://hl7.org/fhir/ValueSet/udi-entry-type|4.3.0
  • http://hl7.org/fhir/ValueSet/udi-entry-type|4.0.1

The following concepts are not included in this cross-version definition because they have valid representations:

  • http://hl7.org/fhir/udi-entry-type#barcode
  • http://hl7.org/fhir/udi-entry-type#card
  • http://hl7.org/fhir/udi-entry-type#manual
  • http://hl7.org/fhir/udi-entry-type#rfid
  • http://hl7.org/fhir/udi-entry-type#self-reported

Following are the generation technical comments: One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. One or more source concepts are narrower than their targets, so the value set relationship is narrowed. The source value set has more active concepts (7) than the target (6), so the source is broader than the target. All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (6). Using explicit mapping from http://hl7.org/fhir/ValueSet/udi-entry-type|5.0.0 to http://hl7.org/fhir/ValueSet/udi-entry-type|4.0.1 in http://hl7.org/fhir/uv/xver/5.0/ConceptMap/R5-UdiEntryType-R4-UdiEntryType (ConceptMap-R5-UdiEntryType-R4-UdiEntryType.json)

References

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/udi-entry-type version 📍5.0.0
    CodeDisplayDefinition
    electronic-transmissionElectronic TransmissionThe UDI information was received electronically from the device through a communication protocol, such as the IEEE 11073 20601 version 4 exchange protocol over Bluetooth or USB.
    unknownUnknownThe method of data capture has not been determined.

 

Expansion

This value set expansion contains 2 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/udi-entry-type5.0.0  electronic-transmissionElectronic TransmissionThe UDI information was received electronically from the device through a communication protocol, such as the IEEE 11073 20601 version 4 exchange protocol over Bluetooth or USB.
http://hl7.org/fhir/udi-entry-type5.0.0  unknownUnknownThe method of data capture has not been determined.

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