Release 5 Draft Ballot

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions Code System

Orders and Observations Work Group Maturity Level: 2Trial Use Use Context: Any

This is a code system defined by the FHIR project.


Defining URL:

Codes to identify how UDI data was entered.

Committee:Orders and Observations Work Group
OID:2.16.840.1.113883.4.642.1.212 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: UDIEntryType (Codes to identify how UDI data was entered.)

This code system defines the following codes:

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 code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code