- Unique Device Identifier (UDI) Barcode string [Unique device identifier (UDI)](device.html#5.11.3.2.2) assigned to device label or package.
-
-
Key: = Must support, = QICore-defined extension, = Is-Modifier
Field Card. Type and Description 
carrierAIDC 0..1StringThe full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - E.g a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats *SHALL* be base64 encoded.carrierHRF 0..1StringThe full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.deviceIdentifier 0..1StringThe device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.entryType 0..1StringA coded entry to indicate how the data was entered.Binding: UDIEntryType (Required)
id 0..1Stringunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.issuer 0..1StringOrganization that is charged with issuing UDIs for devices. For example, the US FDA issuers include : 1) GS1: http://hl7.org/fhir/NamingSystem/gs1-di, 2) HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-dI, 3) ICCBBA for blood containers: http://hl7.org/fhir/NamingSystem/iccbba-blood-di, 4) ICCBA for other devices: http://hl7.org/fhir/NamingSystem/iccbba-other-di.jurisdiction 0..1StringThe identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace. with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi.name 0..1StringName of device as used in labeling or catalog.Key: = Must support, = QICore-defined extension, = Is-Modifier
-