A type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.

Allows institutions to track their devices.

Unique instance identifiers assigned to a device by manufacturers other organizations or owners.

The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.

The name used to display by default when the device is referenced. Based on intent of use by the resource creator, this may reflect one of the names in Device.deviceName, or may be another simple name.

The reference to the definition for the device.

Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.

UDI may identify an unique instance of a device, or it may only identify the type of the device. See UDI mappings for a complete mapping of UDI parts to Device.

The device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.

Organization 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.

The 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.

Allows a recipient of a UDI to know which database will contain the UDI-associated metadata.

The 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.

The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.

If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.

A coded entry to indicate how the data was entered.

Supports a way to distinguish hand entered from machine read data.

Status of the Device record. This is not the status of the device like availability.

This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.

Reason for the status of the Device record. For example, why is the record not active.

The distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product.

For example, this applies to devices in the United States regulated under Code of Federal Regulation 21CFR§1271.290(c).

A name of the manufacturer or entity legally responsible for the device.

The date and time when the device was manufactured.

The date and time beyond which this device is no longer valid or should not be used (if applicable).

Lot number assigned by the manufacturer.

The serial number assigned by the organization when the device was manufactured.

Alphanumeric Maximum 20.

This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.

The name that identifies the device.

The type of deviceName. Note that ManufactureDeviceName means that the name is the name as given by the manufacturer, not the name of the manufacturer. UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName.

The manufacturer's model number for the device.

The part number or catalog number of the device.

Alphanumeric Maximum 20.

The kind or type of device. A device instance may have more than one type - in which case those are the types that apply to the specific instance of the device.

The device function, including in some cases whether or not the functionality conforms to some standard. For example, a PHD blood pressure specialization indicates that the device conforms to the IEEE 11073-10407 Blood Pressure Specialization. This is NOT an alternate name or an additional descriptive name given by the manufacturer. That would be found in the deviceName element. In the PHD case, there are 11073 10101 nomenclature codes that define the specialization standards and that will be used, for example, in the PHD case for the specialization.systemType element. The specialization.version would be the version of the standard if the systemType referred to a standard.

The standard that is used to operate and communicate.

The version of the standard that is used to operate and communicate.

The actual design of the device or software version running on the device.

The type of the device version, e.g. manufacturer, approved, internal.

The hardware or software module of the device to which the version applies.

Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.

The version text.

The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.

Code that specifies the property being represented. No codes are specified but the MDC codes are an example: https://build.fhir.org/mdc.html.

Property value as a quantity.

Property value as a code, e.g., NTP4 (synced to NTP).

Patient information, if the device is affixed to, or associated to a patient for their specific use, irrespective of the procedure, use, observation, or other activity that the device is involved in.

If the device is implanted, or otherwise in use by the patient (e.g., wheelchair, oxygen tank), without further describing its specific use, then the device needs to be associated to the patient.

The status of the device itself - whether it is switched on, or activated, etc.

on |off | standby.

The reasons given for the current operational status - i.e. why is the device switched on etc.

The state of the usage or application of the device - whether the device is implanted, or explanted, or attached to the patient.

implanted|explanted|attached.

The reasons given for the current association status - i.e. why is the device explanted, or attached to the patient, etc.

An organization that is responsible for the provision and ongoing maintenance of the device.

Contact details for an organization or a particular human that is responsible for the device.

used for troubleshooting etc.

The place where the device can be found.

Device.location can be used to track device location.

A network address on which the device may be contacted directly.

If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.

Descriptive information, usage information or implantation information that is not captured in an existing element.

Provides additional safety characteristics about a medical device. For example devices containing latex.

The device that this device is attached to or is part of.