This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Orders and Observations Work Group | Maturity Level: 2 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/udi-entry-type |
Version: | 4.6.0 |
Name: | UDIEntryType |
Title: | UDIEntryType |
Definition: | Codes to identify how UDI data was entered. |
Committee: | Orders and Observations Work Group |
OID: | 2.16.840.1.113883.4.642.3.211 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://hl7.org/fhir/udi-entry-type
This expansion generated 15 Apr 2021
This value set contains 7 concepts
Expansion based on UDIEntryType v4.6.0 (CodeSystem)
All codes from system http://hl7.org/fhir/udi-entry-type
Code | Display | Definition |
barcode | Barcode | a barcodescanner captured the data from the device label. |
rfid | RFID | An RFID chip reader captured the data from the device label. |
manual | Manual | The data was read from the label by a person and manually entered. (e.g. via a keyboard). |
card | Card | The data originated from a patient's implant card and was read by an operator. |
self-reported | Self Reported | The data originated from a patient source and was not directly scanned or read from a label or card. |
electronic-transmission | Electronic Transmission | The 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. |
unknown | Unknown | The method of data capture has not been determined. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | 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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |