This page is part of the FHIR Specification v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes). The current version is 5.0.0. For a full list of available versions, see the Directory of published versions
Orders and Observations Work Group | Maturity Level: 2 | Trial Use | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/udi-entry-type
|
Version: 6.0.0-ballot1 | |||
draft as of 2020-12-28 | Computable Name: UDIEntryType | |||
Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.211 |
This value set is used in the following places:
Codes to identify how UDI data was entered.
http://hl7.org/fhir/udi-entry-type
This expansion generated 18 Dec 2023
Expansion based on codesystem UDI Entry Type v6.0.0-ballot1 (CodeSystem)
This value set contains 7 concepts
Code | System | Display | Definition |
barcode | http://hl7.org/fhir/udi-entry-type | Barcode | a barcodescanner captured the data from the device label. |
rfid | http://hl7.org/fhir/udi-entry-type | RFID | An RFID chip reader captured the data from the device label. |
manual | http://hl7.org/fhir/udi-entry-type | Manual | The data was read from the label by a person and manually entered. (e.g. via a keyboard). |
card | http://hl7.org/fhir/udi-entry-type | Card | The data originated from a patient's implant card and was read by an operator. |
self-reported | http://hl7.org/fhir/udi-entry-type | Self Reported | The data originated from a patient source and was not directly scanned or read from a label or card. |
electronic-transmission | http://hl7.org/fhir/udi-entry-type | 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 | http://hl7.org/fhir/udi-entry-type | 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 |