R5 Final QA

This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - 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

4.4.1.462 ValueSet http://hl7.org/fhir/ValueSet/udi-entry-type

Orders and Observations icon Work Group Maturity Level: 2Trial Use Use Context: Country: World
Official URL: http://hl7.org/fhir/ValueSet/udi-entry-type Version: 5.0.0-draft-final
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.


 

This expansion generated 01 Mar 2023


This value set contains 7 concepts

Expansion based on UDI Entry Type v5.0.0-draft-final (CodeSystem)

CodeSystemDisplayDefinition
  barcodehttp://hl7.org/fhir/udi-entry-typeBarcode

a barcodescanner captured the data from the device label.

  rfidhttp://hl7.org/fhir/udi-entry-typeRFID

An RFID chip reader captured the data from the device label.

  manualhttp://hl7.org/fhir/udi-entry-typeManual

The data was read from the label by a person and manually entered. (e.g. via a keyboard).

  cardhttp://hl7.org/fhir/udi-entry-typeCard

The data originated from a patient's implant card and was read by an operator.

  self-reportedhttp://hl7.org/fhir/udi-entry-typeSelf Reported

The data originated from a patient source and was not directly scanned or read from a label or card.

  electronic-transmissionhttp://hl7.org/fhir/udi-entry-typeElectronic 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.

  unknownhttp://hl7.org/fhir/udi-entry-typeUnknown

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:

LvlA 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
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