Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3 R2

8.14 Resource Device - Content

Responsible Owner: Orders and Observations icon Work Group Maturity Level : 2   Trial Use Security Category : Business Compartments : Not linked to any defined compartments Device

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.

Note to Implementers: For an overview of this resource and others in the Device domain, also see the module page .

Note to Implementers: The owner has been removed from Device and is now included in DeviceAssociation as .relationship of the subject. Please comment on the revision if there are issues with removing the identification of individuals in the Device resource.

Note to Implementers: Extensions have been created and are now available to represent previously removed Device elements and new concepts. These include:

  • device-mode , device-cycle , device-duration , device-gateway , and device-endpoint
  • device-alertDetection – describes the alert detection activation states for the overall device
  • device-conformsTo-source – represents the source of the device specification

Links to these extensions can be found in the FHIR Extension Pack . Feedback from implementers is welcomed to inform further refinement and usage guidance.

This resource is an administrative a base resource that tracks individual instances of a device and their location. It is referenced by other resources for recording which device performed an action such as a procedure or an observation, referenced when prescribing and which device was implanted in or explanted from a patient, dispensing devices for a device to a patient use for their use, managing inventory, or when requesting a specific device for ordering supplies, a patient's use. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Medical devices may also include some types of software.

Non-medical devices may include items such as a machine, cellphone, computer, software application or algorithm, etc. In short, a Device can range from a tongue depressor to an MRI. The fields in the Device resource must be flexible enough to cover this range.

The resource may be used to record and transmit document the Unique Device Identifier (UDI) and information about a device where appropriate or necessary according to local jurisdictions over time. Additional information about UDI is provided in the Unique Device Identifier (UDI) section.

Devices may be categorized and may be associated with one or more categories. Device category examples include, but are not limited to: active, communicating, durable medical equipment, home use, implantable, InVitro diagnostics, personal health, point-of-care, single use, re-usable, and software. See DeviceDefinition for detailed descriptions of device categories.

When referring to a specific instance, even without specific instance details, Device is to be used, not a DeviceDefinition. The context of a data exchange indicates whether the data is representing a physical instance or a "kind", not the presence of instance data such as a patient's implant. lot and serial numbers.

Some examples:

  1. In a Procedure, reporting the use of a pump for which we have no instance data - the pump is a physical instance. Whether the lot number (for example) is known or not, depends on the circumstance - in another Procedure or in an update of the Procedure, the lot number could be added. Hence the use of Device.
  2. When a device gets replaced by another device of the same type. In this case, a procedure indicates that one instance of the device is removed/explanted/discarded, and another instance is used. These are physical instances for which instance data might exist and be known, or not.

These are Note to Implementers: The module pages under development by Orders and Observations will further describe the variations of device related use cases across the device resources, e.g., Device, DeviceDefinition, DeviceAssociation, DeviceDispense, DeviceMetric, DeviceRequest, and Device Usage.

There are several resources that can be used to represent device related events, requests or definitions. The following Resources should be used in the following manner:

  • Device (this resource)
  • DeviceDefinition -  - Describes a "kind" of device - not a physical instance, cut a "catalog entry" where a specific instance of the device. A kind of device is frequently defined and documented by the manufacturer, reseller, or regulator. regulatory. Documentation would include any information that applies to all instances of a device, and may be published through a catalog. For example, the characteristics of a test analyzer, x-ray machine, or wheelchair.
  • DeviceMetric -  - Describes a measurement, calculation or setting capability of a medical device. device instance. A Device may include multiple device metrics, each yielding a different observation. The DeviceMetric models the properties of the Observations generated by and/or about the device such as whether or not the Observation is a setting. A DeviceMetric describes aspects of the device that may change over time. In FHIR, contrast, the "Device" Device.property is used to capture inherent, essentially fixed, characteristics of the "administrative" resource device, such as a "large" blood pressure cuff, the bore size of an MRI, the color of a lead. (Such static characteristics may also be recorded in DeviceDefinition.).
  • DeviceAssociation  - Records the association of a device with a subject and/or operator (e.g. a Patient by ownership, or a Practitioner by usage during a procedure). DeviceAssociation should be used for ownenship/custiodianship.
  • DeviceAlert  - Represents a single alert or alarm condition detected and signaled by a patient-connected health / medical device to create clinician’s awareness of a patient safety risk that needs to be addressed.
  • DeviceRequest - The workflow step to request/order the use of a device (it does in a specific context.
  • DeviceDispense icon - The workflow step to manage the distribution of the device.
  • SupplyRequest icon - The workflow step to request/order supplies that would be needed beyond the devices in the DeviceRequest.
  • SupplyDelivery icon - The workflow step to manage the distribution of supplies that are ordered beyone the devices in the DeviceDispense.
  • DeviceUsage icon - To record the use of a device that is not change much covered by a procedure - i.e., patient reported use of a device.
  • NutritionOrder  - An order for nutrition can request to a specific device to administer enteral feeding.
  • Observation  - A measurement can be generated by many types of devices. It may be linked to and has manufacturer information etc.), whereas supplemented by data about the DeviceComponent current structure and status of the device itself in one or more Device or DeviceMetric (which is really resources.
  • Procedure  - A procedure can be performed using a kind variety of DeviceComponent) model devices, or a device can be implanted or otherwise associated with a patient. A procedure may also record the physical part, including operation status and inclusion of an additive.
  • MedicationAdministration  - A medication administration can be performed using a variety of devices.

In FHIR, the Device represents either the device in total, or a component of an encapsulating device when there is much more volatile. The physical composition a need for individual tracking of a component. A Device as a component then points to the parent device it is represented by part of. The top-level Device captures the Devices pointing to their "parent". actual data about the instance of the device and the instances of all its children that either provides identifying characteristics of the Device (including applicable UDI – unique device identification) and data that can vary dynamically by device, e.g., specific settings at a particular point in time.

Devices differ from medications because they are not "used up" - they remain active in or for a patient in an ongoing fashion. However, the specific boundary between medications and for a longer duration. They also may be re-used, particularly non-implanted devices is defined at the implementation level and this standard does not enforce those used for diagnostics and procedures. Frequently, when a boundary device is packaged with a medication, the exception ordering, dispense, and administration processes typically focus on the medication aspects and reference the device.

In the case of devices that an infusion pump, while some actions are implanted in focused on the device (e.g., ordering to a patient. The room or maintaining the pump), the focus is as well on the medication while the device is used for administration. However, that separation is not always as clear and may be impacted by specific implementations. Regardless, the  Medication resource  resource should not be used to represent implanted devices. This resource (implanted) devices, rather reference the relationship where an actual device needs to be tracked in addition to the medication. In some sense the Medication is referenced analogous to the Observation generated by Signature , a Blood Pressure personal health device. The Observation resource contains the blood pressure values, units and the time stamp while the Device resource contains the manufacturer name, model number, serial number, firmware and hardware versions, exchange protocol information, any clock capabilities, etc.

Structure

0..1 0..* online | paused | standby | offline | not-ready Date Date udi-label-name 0..1 CodeableConcept The actual design of The 0..1 A single component of 1..1 The actual configuration settings Property value as a quantity Property value as a code, e.g., NTP4 (synced to NTP) Reference uri
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . Device TU DomainResource Item used in healthcare
+ Rule: only one Device.name.display SHALL be true when there is more than one Device.name

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier 0..* Identifier Instance identifier

. . . definition 0..1 Reference canonical ( DeviceDefinition ) The reference to the definition for the device
. . . udiCarrier Σ 0..* BackboneElement Unique Device Identifier (UDI) Barcode string value

. . . . deviceIdentifier Σ 1..1 string Mandatory fixed portion of UDI
. . . . issuer deviceIdentifierSystem 0..1 uri The namespace for the device identifier value
0..1
. . . . issuer Σ 1..1 uri UDI Issuing Organization
. . . . jurisdiction 0..1 uri Regional UDI authority
. . . . carrierAIDC Σ 0..1 base64Binary UDI Machine Readable Barcode String value
. . . . carrierHRF Σ 0..1 string UDI Human Readable Barcode String value
. . . . entryType 0..1 code barcode | rfid | manual + | card | self-reported | electronic-transmission | unknown
UDIEntryType Binding: UDI Entry Type ( Required )
. . statusReason . availabilityStatus 0..1 CodeableConcept lost | transduc-discon damaged | hw-discon destroyed | off available
FHIRDeviceStatusReason Binding: FHIR Device Availability Status ( Extensible )
. . distinctIdentifier . biologicalSourceEvent 0..1 string Identifier A production identifier of the donation, collection, or pooling event from which biological material in this device was derived
The distinct identification string
. . . manufacturer 0..1 string Name of device manufacturer
. . . manufactureDate 0..1 dateTime A production identifier that indicates the date when the device was made
. . . expirationDate 0..1 dateTime A production identifier that indicates the date and time of expiry of this device (if applicable)
. . . lotNumber 0..1 string A production identifier that indicates the Lot number of manufacture
. . . serialNumber 0..1 string A production identifier that indicates the Serial number assigned by the manufacturer
. . deviceName . name C 0..* BackboneElement The name or names of the device as given by known to the manufacturer and/or patient

. . . name . value Σ 1..1 string The name of term that names the device
. . . . type Σ 1..1 code CodeableConcept registered-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other
DeviceNameType Binding: Device Name Type ( Required Extensible )
. . . . display ?! Σ C 0..1 boolean The preferred device name
. . . modelNumber 0..1 string The manufacturer's model number for the device
. . . partNumber 0..1 string The part number or catalog number of the device
. . . type category 0..* CodeableConcept Indicates a high-level grouping of the device
Binding: FHIR Device Category ( Example )

. . . type 0..* CodeableConcept The kind or type of device
Binding: Device Type ( Example )

. . specialization . deviceVersion 0..* BackboneElement The capabilities supported on a device, the standards to which actual design of the device conforms for a particular purpose, and used for or software version running on the communication device

. . . systemType . type 0..1 CodeableConcept The type of the device version, e.g. manufacturer, approved, internal
Binding: Device Version Type ( Example )
1..1
. . . . component 0..1 Identifier The standard that is used hardware or software module of the device to operate and communicate which the version applies
. . . . version installDate 0..1 dateTime The date the version was installed on the device
0..1
. . . . value 1..1 string The version of the standard that is used to operate and communicate text
. . version . conformsTo 0..* BackboneElement Identifies the device standards, specifications, or software version running on formal guidances for the capabilities supported by the device

. . . type . category 0..1 CodeableConcept Describes the common type of the device version standard, specification, or formal guidance. communication | performance | measurement
Binding: Device Specification Category ( Example )
. . . component . specification 1..1 Identifier CodeableConcept Identifies the standard, specification, or formal guidance that the device version adheres to
Binding: Device Specification Type ( Example )
. . . value . version 0..1 string Specific form or variant of the standard
The version text
. . . property 0..* BackboneElement Inherent, essentially fixed, characteristics of a device as it actually operates, the device. e.g., regulation status, time properties properties, size, material, etc.

. . . . type 1..1 CodeableConcept Code that specifies the property DeviceDefinitionPropetyCode (Extensible) being represented
Binding: Device Property Type (Example only) ( Example )
. . . valueQuantity . value[x] 1..1 Value of the property
0..*
. . . . . valueQuantity Quantity
. . . valueCode . . valueCodeableConcept 0..* CodeableConcept
. . . . patient . valueString string
. . . . . valueBoolean 0..1 Reference ( Patient boolean ) Patient to whom Device is affixed
. . . . owner . valueInteger integer
. . . . . valueRange 0..1 Reference ( Organization Range ) Organization responsible for device
. . . . . contact valueAttachment Attachment
. . . additive 0..* ContactPoint BackboneElement Material added to a container device
Details for human/organization for support
. . . location . type 1..1 CodeableReference ( SubstanceDefinition ) The additive substance
Binding: Substance Code ( Example )
0..1
. . . . quantity ( Location ) 0..1 SimpleQuantity Quantity of additive substance within container
Where the device is found
. . url . contact 0..* ContactPoint Details for human/organization for support

0..1
. . . location Network address to contact 0..1 Reference ( Location ) Where the device is found
. . . note 0..* Annotation Device notes and comments

. . . safety Σ 0..* CodeableConcept Safety Characteristics of Device
Binding: Device Safety ( Example )

. . . parent 0..1 Reference ( Device ) The parent higher level or encompassing device that this device is a logical part of

doco Documentation for this format icon

See the Extensions for this resource

UML Diagram ( Legend )

Device ( DomainResource ) Unique instance identifiers assigned to a device by manufacturers other organizations or owners identifier : Identifier [0..*] The reference to the definition for the device definition : Reference canonical [0..1] « DeviceDefinition » Status The Device record status. This is not the status of the Device device like availability (this element modifies the meaning of other elements) status : code [0..1] « The availability status of the device. null (Strength=Required) FHIRDeviceStatus ! » Reason for the dtatus The availability of the Device availability device statusReason availabilityStatus : CodeableConcept [0..*] [0..1] « The availability status reason of the device. null (Strength=Extensible) FHIRDeviceStatusReason FHIRDeviceAvailabilityStatus + » The distinct identification string as required by regulation for a human cell, tissue, A production identifier of the donation, collection, or cellular and tissue-based product pooling event from which biological material in this device was derived distinctIdentifier biologicalSourceEvent : string Identifier [0..1] A name of the manufacturer or entity legally responsible for the device manufacturer : string [0..1] The date and time when the device was manufactured manufactureDate : dateTime [0..1] The date and time beyond which this device is no longer valid or should not be used (if applicable) expirationDate : dateTime [0..1] Lot number assigned by the manufacturer lotNumber : string [0..1] The serial number assigned by the organization when the device was manufactured serialNumber : string [0..1] The manufacturer's model number for the device modelNumber : string [0..1] The part number or catalog number of the device partNumber : string [0..1] The kind Devices may be associated with one or type of device more categories type category : CodeableConcept [0..1] [0..*] « Codes to identify medical devices. null (Strength=Example) DeviceType FHIRDeviceCategory ?? » Patient information, If the The kind or type of device. A device is affixed to a person patient : Reference [0..1] « Patient » An organization instance may have more than one type - in which case those are the types that is responsible for apply to the provision and ongoing maintenance specific instance of the device owner type : Reference CodeableConcept [0..1] [0..*] « Organization null (Strength=Example) DeviceType ?? » Contact details for an organization or a particular human that is responsible for the device contact : ContactPoint [0..*] The place where the device can be found location : Reference [0..1] « Location » A network address on which the device may be contacted directly url : uri [0..1] Descriptive information, usage information or implantation information that is not captured in an existing element note : Annotation [0..*] Provides additional safety characteristics about a medical device. For example devices containing latex safety : CodeableConcept [0..*] « null (Strength=Example) DeviceSafety ?? » The parent higher level or encompassing device that this device is a logical part of parent : Reference [0..1] « Device » UdiCarrier The device identifier (DI) (UDI-DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device. The UDI-DI portion is placed on a device label or package. Note that the DeviceDefinition may include multiple UDI-DIs if it is sold in multiple jurisdictions deviceIdentifier : string [1..1] Establishes the namespace for the issuing agency's system (e.g, GS1's GTIN, ICCBBA's ISBT-128) used to create the device identifier deviceIdentifierSystem : uri [0..1] Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include : include: 1) GS1: http://hl7.org/fhir/NamingSystem/gs1-di, 2) HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-dI, http://hl7.org/fhir/NamingSystem/hibcc-diI, 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 # Informationsstelle für Arzneispezialitäten (IFA GmbH) (EU only): http://hl7.org/fhir/NamingSystem/ifa-gmbh-di issuer : uri [0..1] [1..1] 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 http://hl7.org/fhir/NamingSystem/us-fda-udi or in the European Union by the European Commission http://hl7.org/fhir/NamingSystem/eu-ec-udi jurisdiction : uri [0..1] 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 , 2D Matrix, or RFID. Because of limitations on character sets in XML Some AIDC representations contain non-printable characters and the need to round-trip JSON data through XML, cannot be represented in a string format. For this reason, AIDC Formats *SHALL* format SHALL be base64 base64Binary encoded carrierAIDC : base64Binary [0..1] The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device carrierHRF : string [0..1] A coded entry to indicate how the data was entered entryType : code [0..1] « Codes to identify how UDI data was entered. null (Strength=Required) UDIEntryType ! » DeviceName Name The actual name of that identifies the device name value : string [1..1] The type Indicates the kind of deviceName. UDILabelName name. RegisteredName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName type : code CodeableConcept [1..1] « The type of null (Strength=Extensible) DeviceNameType + » Indicates the default or preferred name to be displayed (this element modifies the device meaning of other elements) display : boolean [0..1] « This element has or is referred by. (Strength=Required) affected by some invariants DeviceNameType ! C » Specialization DeviceVersion The standard that is used to operate and communicate type of the device version, e.g. manufacturer, approved, internal systemType type : CodeableConcept [1..1] [0..1] « null (Strength=Example) DeviceVersionType ?? » The version hardware or software module of the standard that is used device to operate and communicate which the version applies component : Identifier [0..1] The date the version was installed on the device installDate : string dateTime [0..1] The version text value : string [1..1] Version ConformsTo The Describes the type of the device version standard, specification, or formal guidance type category : CodeableConcept [0..1] « null (Strength=Example) DeviceSpecificationCategory ?? » A single component of Code that identifies the specific standard, specification, protocol, formal guidance, regulation, legislation, or certification scheme to which the device version adheres component specification : Identifier CodeableConcept [0..1] [1..1] « null (Strength=Example) DeviceSpecificationType ?? » The version text Identifies the specific form or variant of the standard, specification, or formal guidance. This may be a 'version number', release, document edition, publication year, or other label value version : string [1..1] [0..1] Property Code that specifies the property DeviceDefinitionPropetyCode (Extensible) property, such as resolution, color, size, being represented type : CodeableConcept [1..1] « null (Strength=Example) DevicePropertyType ?? » Property The value as a quantity of the property specified by the associated property.type code valueQuantity value[x] : DataType [1..1] « Quantity [0..*] | CodeableConcept | string | boolean | integer | Range | Attachment » Additive Property value The type of the substance added to the container. This is represented as a code, e.g., NTP4 (synced to NTP) concept from a code system or described in a Substance resource valueCode type : CodeableConcept CodeableReference [0..*] [1..1] « SubstanceDefinition ; null (Strength=Example) SubstanceCode ?? » The quantity of the additive substance in the container; may be volume, dimensions, or other appropriate measurements, depending on the container and additive substance type quantity : Quantity ( SimpleQuantity ) [0..1] Unique device identifier Device Identifier (UDI) assigned to placed on a device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction UDIs if it is sold, or for sold in multiple jurisdictions it could have been sold udiCarrier [0..*] 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 deviceName name [0..*] The capabilities supported on a device, the standards to which actual design of the device conforms for a particular purpose, and used for or software version running on the communication device specialization deviceVersion [0..*] The actual design of Identifies the device standards, specifications, or software version running on formal guidances for the capabilities supported by the device. The device may be certified as conformant to these specifications e.g., communication, performance, process, measurement, or specialization standards version conformsTo [0..*] The actual configuration settings Static or essentially fixed characteristics or features of a the device as it actually operates, e.g., regulation status, (e.g., time properties or timing attributes, resolution, accuracy, intended use or instructions for use, and physical attributes) that are not otherwise captured in more specific attributes property [0..*] Material added to a container device (typically used in specimen collection or initial processing). The material may be added by the device manufacturer or by a different party subsequent to manufacturing additive [0..*]

XML Template

<

<Device xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Instance identifier --></identifier>
 <</definition>
 <
  <
  <<a href="device-definitions.html#Device.udiCarrier.issuer" title="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." class="dict">
  <
  <
  <
  <

 <definition><!-- 0..1 canonical(DeviceDefinition) The reference to the definition for the device --></definition>
 <udiCarrier>  <!-- 0..* Unique Device Identifier (UDI) value -->
  <deviceIdentifier value="[string]"/><!-- 1..1 Mandatory fixed portion of UDI -->
  <deviceIdentifierSystem value="[uri]"/><!-- 0..1 The namespace for the device identifier value -->
  <issuer value="[uri]"/><!-- 1..1 UDI Issuing Organization -->
  <jurisdiction value="[uri]"/><!-- 0..1 Regional UDI authority -->
  <carrierAIDC value="[base64Binary]"/><!-- 0..1 UDI Machine Readable value -->
  <carrierHRF value="[string]"/><!-- 0..1 UDI Human Readable value -->
  <entryType value="[code]"/><!-- 0..1 barcode | rfid | manual | card | self-reported | electronic-transmission | unknown -->

 </udiCarrier>
 <
 <</statusReason>
 <
 <
 <
 <
 <
 <
 <
  <
  <<a href="device-definitions.html#Device.deviceName.type" title="The type of deviceName.
UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName." class="dict">
 </deviceName>
 <
 <
 <</type>
 <
  <</systemType>
  <
 </specialization>
 <
  <</type>
  <</component>
  <
 </version>
 <
  <</type>
  <</valueQuantity>
  <</valueCode>

 <status value="[code]"/><!-- 0..1 active | inactive | entered-in-error | unknown -->
 <availabilityStatus><!-- 0..1 CodeableConcept lost | damaged | destroyed | available --></availabilityStatus>
 <biologicalSourceEvent><!-- 0..1 Identifier A production identifier of the donation, collection, or pooling event from which biological material in this device was derived --></biologicalSourceEvent>
 <manufacturer value="[string]"/><!-- 0..1 Name of device manufacturer -->
 <manufactureDate value="[dateTime]"/><!-- 0..1 A production identifier that indicates the date when the device was made -->
 <expirationDate value="[dateTime]"/><!-- 0..1 A production identifier that indicates the date and time of expiry of this device (if applicable) -->
 <lotNumber value="[string]"/><!-- 0..1 A production identifier that indicates the Lot number of manufacture -->
 <serialNumber value="[string]"/><!-- 0..1 A production identifier that indicates the Serial number assigned by the manufacturer -->
 <name>  <!-- I 0..* The name or names of the device as known to the manufacturer and/or patient -->
  <value value="[string]"/><!-- 1..1 The term that names the device -->
  <type><!-- 1..1 CodeableConcept registered-name | user-friendly-name | patient-reported-name --></type>
  <display value="[boolean]"/><!-- I 0..1 The preferred device name -->
 </name>
 <modelNumber value="[string]"/><!-- 0..1 The manufacturer's model number for the device -->
 <partNumber value="[string]"/><!-- 0..1 The part number or catalog number of the device -->
 <category><!-- 0..* CodeableConcept Indicates a high-level grouping of the device --></category>
 <type><!-- 0..* CodeableConcept The kind or type of device --></type>
 <deviceVersion>  <!-- 0..* The actual design of the device or software version running on the device -->
  <type><!-- 0..1 CodeableConcept The type of the device version, e.g. manufacturer, approved, internal --></type>
  <component><!-- 0..1 Identifier The hardware or software module of the device to which the version applies --></component>
  <installDate value="[dateTime]"/><!-- 0..1 The date the version was installed on the device -->
  <value value="[string]"/><!-- 1..1 The version text -->
 </deviceVersion>
 <conformsTo>  <!-- 0..* Identifies the standards, specifications, or formal guidances for the capabilities supported by the device -->
  <category><!-- 0..1 CodeableConcept Describes the common type of the standard, specification, or formal guidance.  communication | performance | measurement --></category>
  <specification><!-- 1..1 CodeableConcept Identifies the standard, specification, or formal guidance that the device adheres to --></specification>
  <version value="[string]"/><!-- 0..1 Specific form or variant of the standard -->
 </conformsTo>
 <property>  <!-- 0..* Inherent, essentially fixed, characteristics of the device.  e.g., time properties, size, material, etc. -->
  <type><!-- 1..1 CodeableConcept Code that specifies the property being represented --></type>
  <value[x]><!-- 1..1 Quantity|CodeableConcept|string|boolean|integer|Range|
    Attachment Value of the property --></value[x]>
 </property>
 <</patient>
 <</owner>

 <additive>  <!-- 0..* Material added to a container device -->
  <type><!-- 1..1 CodeableReference(SubstanceDefinition) The additive substance --></type>
  <quantity><!-- 0..1 Quantity(SimpleQuantity) Quantity of additive substance within container --></quantity>
 </additive>

 <contact><!-- 0..* ContactPoint Details for human/organization for support --></contact>
 <location><!-- 0..1 Reference(Location) Where the device is found --></location>
 <

 <note><!-- 0..* Annotation Device notes and comments --></note>
 <</safety>
 <</parent>

 <safety><!-- 0..* CodeableConcept Safety Characteristics of Device --></safety>
 <parent><!-- 0..1 Reference(Device) The higher level or encompassing device that this device is a logical part of --></parent>

</Device>

JSON Template

{doco
  "resourceType" : "",

  "resourceType" : "Device",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Instance identifier
  "
  "
    "
    "<a href="device-definitions.html#Device.udiCarrier.issuer" title="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." class="dict">issuer
    "
    "
    "
    "

  "definition" : "<canonical(DeviceDefinition)>", // The reference to the definition for the device
  "udiCarrier" : [{ // Unique Device Identifier (UDI) value
    "deviceIdentifier" : "<string>", // R!  Mandatory fixed portion of UDI
    "deviceIdentifierSystem" : "<uri>", // The namespace for the device identifier value
    "issuer" : "<uri>", // R!  UDI Issuing Organization
    "jurisdiction" : "<uri>", // Regional UDI authority
    "carrierAIDC" : "<base64Binary>", // UDI Machine Readable value
    "carrierHRF" : "<string>", // UDI Human Readable value
    "entryType" : "<code>" // barcode | rfid | manual | card | self-reported | electronic-transmission | unknown

  }],
  "
  "
  "
  "
  "
  "
  "
  "
  "
    "
    "<a href="device-definitions.html#Device.deviceName.type" title="The type of deviceName.
UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName." class="dict">type

  "status" : "<code>", // active | inactive | entered-in-error | unknown
  "availabilityStatus" : { CodeableConcept }, // lost | damaged | destroyed | available
  "biologicalSourceEvent" : { Identifier }, // A production identifier of the donation, collection, or pooling event from which biological material in this device was derived
  "manufacturer" : "<string>", // Name of device manufacturer
  "manufactureDate" : "<dateTime>", // A production identifier that indicates the date when the device was made
  "expirationDate" : "<dateTime>", // A production identifier that indicates the date and time of expiry of this device (if applicable)
  "lotNumber" : "<string>", // A production identifier that indicates the Lot number of manufacture
  "serialNumber" : "<string>", // A production identifier that indicates the Serial number assigned by the manufacturer
  "name" : [{ // I The name or names of the device as known to the manufacturer and/or patient
    "value" : "<string>", // R!  The term that names the device
    "type" : { CodeableConcept }, // R!  registered-name | user-friendly-name | patient-reported-name
    "display" : <boolean> // I The preferred device name

  }],
  "
  "
  "
  "
    "
    "

  "modelNumber" : "<string>", // The manufacturer's model number for the device
  "partNumber" : "<string>", // The part number or catalog number of the device
  "category" : [{ CodeableConcept }], // Indicates a high-level grouping of the device
  "type" : [{ CodeableConcept }], // The kind or type of device
  "deviceVersion" : [{ // The actual design of the device or software version running on the device
    "type" : { CodeableConcept }, // The type of the device version, e.g. manufacturer, approved, internal
    "component" : { Identifier }, // The hardware or software module of the device to which the version applies
    "installDate" : "<dateTime>", // The date the version was installed on the device
    "value" : "<string>" // R!  The version text

  }],
  "
    "
    "
    "

  "conformsTo" : [{ // Identifies the standards, specifications, or formal guidances for the capabilities supported by the device
    "category" : { CodeableConcept }, // Describes the common type of the standard, specification, or formal guidance.  communication | performance | measurement
    "specification" : { CodeableConcept }, // R!  Identifies the standard, specification, or formal guidance that the device adheres to
    "version" : "<string>" // Specific form or variant of the standard

  }],
  "
    "
    "
    "

  "property" : [{ // Inherent, essentially fixed, characteristics of the device.  e.g., time properties, size, material, etc.
    "type" : { CodeableConcept }, // R!  Code that specifies the property being represented
    // value[x]: Value of the property. One of these 7:

    "valueQuantity" : { Quantity },
    "valueCodeableConcept" : { CodeableConcept },
    "valueString" : "<string>",
    "valueBoolean" : <boolean>,
    "valueInteger" : <integer>,
    "valueRange" : { Range },
    "valueAttachment" : { Attachment }
  }],
  "additive" : [{ // Material added to a container device
    "type" : { CodeableReference(SubstanceDefinition) }, // R!  The additive substance
    "quantity" : { Quantity(SimpleQuantity) } // Quantity of additive substance within container

  }],
  "
  "

  "contact" : [{ ContactPoint }], // Details for human/organization for support
  "location" : { Reference(Location) }, // Where the device is found
  "

  "note" : [{ Annotation }], // Device notes and comments
  "
  "

  "safety" : [{ CodeableConcept }], // Safety Characteristics of Device
  "parent" : { Reference(Device) } // The higher level or encompassing device that this device is a logical part of

}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:;

[ a fhir:Device;

  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from 
  # from 
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:<a href="device-definitions.html#Device.udiCarrier.issuer" title="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." class="dict">Device.udiCarrier.issuer
    fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:<a href="device-definitions.html#Device.deviceName.type" title="The type of deviceName.
UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName." class="dict">Device.deviceName.type
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* Instance identifier
  fhir:definition [ canonical(DeviceDefinition) ] ; # 0..1 The reference to the definition for the device
  fhir:udiCarrier ( [ # 0..* Unique Device Identifier (UDI) value
    fhir:deviceIdentifier [ string ] ; # 1..1 Mandatory fixed portion of UDI
    fhir:deviceIdentifierSystem [ uri ] ; # 0..1 The namespace for the device identifier value
    fhir:issuer [ uri ] ; # 1..1 UDI Issuing Organization
    fhir:jurisdiction [ uri ] ; # 0..1 Regional UDI authority
    fhir:carrierAIDC [ base64Binary ] ; # 0..1 UDI Machine Readable value
    fhir:carrierHRF [ string ] ; # 0..1 UDI Human Readable value
    fhir:entryType [ code ] ; # 0..1 barcode | rfid | manual | card | self-reported | electronic-transmission | unknown
  ] ... ) ;
  fhir:status [ code ] ; # 0..1 active | inactive | entered-in-error | unknown
  fhir:availabilityStatus [ CodeableConcept ] ; # 0..1 lost | damaged | destroyed | available
  fhir:biologicalSourceEvent [ Identifier ] ; # 0..1 A production identifier of the donation, collection, or pooling event from which biological material in this device was derived
  fhir:manufacturer [ string ] ; # 0..1 Name of device manufacturer
  fhir:manufactureDate [ dateTime ] ; # 0..1 A production identifier that indicates the date when the device was made
  fhir:expirationDate [ dateTime ] ; # 0..1 A production identifier that indicates the date and time of expiry of this device (if applicable)
  fhir:lotNumber [ string ] ; # 0..1 A production identifier that indicates the Lot number of manufacture
  fhir:serialNumber [ string ] ; # 0..1 A production identifier that indicates the Serial number assigned by the manufacturer
  fhir:name ( [ # 0..* I The name or names of the device as known to the manufacturer and/or patient
    fhir:value [ string ] ; # 1..1 The term that names the device
    fhir:type [ CodeableConcept ] ; # 1..1 registered-name | user-friendly-name | patient-reported-name
    fhir:display [ boolean ] ; # 0..1 I The preferred device name
  ] ... ) ;
  fhir:modelNumber [ string ] ; # 0..1 The manufacturer's model number for the device
  fhir:partNumber [ string ] ; # 0..1 The part number or catalog number of the device
  fhir:category  ( [ CodeableConcept ] ... ) ; # 0..* Indicates a high-level grouping of the device
  fhir:type  ( [ CodeableConcept ] ... ) ; # 0..* The kind or type of device
  fhir:deviceVersion ( [ # 0..* The actual design of the device or software version running on the device
    fhir:type [ CodeableConcept ] ; # 0..1 The type of the device version, e.g. manufacturer, approved, internal
    fhir:component [ Identifier ] ; # 0..1 The hardware or software module of the device to which the version applies
    fhir:installDate [ dateTime ] ; # 0..1 The date the version was installed on the device
    fhir:value [ string ] ; # 1..1 The version text
  ] ... ) ;
  fhir:conformsTo ( [ # 0..* Identifies the standards, specifications, or formal guidances for the capabilities supported by the device
    fhir:category [ CodeableConcept ] ; # 0..1 Describes the common type of the standard, specification, or formal guidance.  communication | performance | measurement
    fhir:specification [ CodeableConcept ] ; # 1..1 Identifies the standard, specification, or formal guidance that the device adheres to
    fhir:version [ string ] ; # 0..1 Specific form or variant of the standard
  ] ... ) ;
  fhir:property ( [ # 0..* Inherent, essentially fixed, characteristics of the device.  e.g., time properties, size, material, etc.
    fhir:type [ CodeableConcept ] ; # 1..1 Code that specifies the property being represented
    # value[x] : 1..1 Value of the property. One of these 7
      fhir:value [  a fhir:Quantity ; Quantity ]
      fhir:value [  a fhir:CodeableConcept ; CodeableConcept ]
      fhir:value [  a fhir:String ; string ]
      fhir:value [  a fhir:Boolean ; boolean ]
      fhir:value [  a fhir:Integer ; integer ]
      fhir:value [  a fhir:Range ; Range ]
      fhir:value [  a fhir:Attachment ; Attachment ]
  ] ... ) ;
  fhir:additive ( [ # 0..* Material added to a container device
    fhir:type [ CodeableReference(SubstanceDefinition) ] ; # 1..1 The additive substance
    fhir:quantity [ Quantity(SimpleQuantity) ] ; # 0..1 Quantity of additive substance within container
  ] ... ) ;
  fhir:contact  ( [ ContactPoint ] ... ) ; # 0..* Details for human/organization for support
  fhir:location [ Reference(Location) ] ; # 0..1 Where the device is found
  fhir:note  ( [ Annotation ] ... ) ; # 0..* Device notes and comments
  fhir:safety  ( [ CodeableConcept ] ... ) ; # 0..* Safety Characteristics of Device
  fhir:parent [ Reference(Device) ] ; # 0..1 The higher level or encompassing device that this device is a logical part of

]

Changes since R3 from both R4 and R4B

Device
Device.definition
  • Added Element Type changed from Reference(DeviceDefinition) to canonical(DeviceDefinition)
Device.udiCarrier Device.udiCarrier.deviceIdentifier
  • Added Element Min Cardinality changed from 0 to 1
Device.udiCarrier.deviceIdentifier Device.udiCarrier.deviceIdentifierSystem
  • Added Element
Device.udiCarrier.issuer
  • Added Element Min Cardinality changed from 0 to 1
Device.udiCarrier.jurisdiction Device.udiCarrier.entryType
  • Added Element Add code electronic-transmission
Device.udiCarrier.carrierAIDC Device.availabilityStatus
  • Added Element
Device.udiCarrier.carrierHRF Device.biologicalSourceEvent
  • Added Element
Device.name
  • Renamed from deviceName to name
Device.udiCarrier.entryType Device.name.value
  • Added Mandatory Element
Device.status Device.name.type
  • Moved from Device.deviceName to Device.name
  • Type changed from code to CodeableConcept
  • Change value set binding strength from http://hl7.org/fhir/ValueSet/device-status required to http://hl7.org/fhir/ValueSet/device-status|4.0.1 extensible
Device.statusReason Device.name.display
  • Added Element
Device.distinctIdentifier Device.category
  • Added Element
Device.serialNumber Device.type
  • Added Element Max Cardinality changed from 1 to *
Device.deviceName Device.deviceVersion
  • Added Element
Device.deviceName.name Device.deviceVersion.type
  • Added Mandatory Element
Device.deviceName.type Device.deviceVersion.component
  • Added Mandatory Element
Device.modelNumber Device.deviceVersion.installDate
  • Added Element
Device.partNumber Device.deviceVersion.value
  • Added Mandatory Element
Device.specialization Device.conformsTo
  • Added Element Renamed from specialization to conformsTo
Device.specialization.systemType Device.conformsTo.category
  • Added Mandatory Element
Device.specialization.version Device.conformsTo.specification
  • Added Mandatory Element
Device.version Device.conformsTo.version
  • Max Cardinality changed from 1 to * Type changed Moved from string Device.specialization to BackboneElement Device.conformsTo
Device.version.type Device.property.value[x]
  • Added Mandatory Element
Device.version.component Device.additive
  • Added Element
Device.version.value Device.additive.type
  • Added Mandatory Element
Device.property Device.additive.quantity
  • Added Element
Device.property.type Device.statusReason
  • Added Mandatory Element Deleted (-> reason was removed. DeviceAssociation can be used)
Device.distinctIdentifier
  • Deleted
Device.deviceName.name
  • Deleted
Device.specialization.systemType
  • Deleted
Device.version
  • Deleted
Device.property.valueQuantity
  • Added Element Deleted
Device.property.valueCode
  • Added Element Deleted
Device.parent Device.patient
  • Added Element Deleted (-> patient association is in DeviceAssociation)
Device.udi Device.owner
  • deleted Deleted
Device.model Device.url
  • deleted Deleted

See the Full Difference for further information

This analysis is available for R4 as XML or JSON . See R3 <--> R4 Conversion Maps (status = 9 tests that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors). ) for R4B as XML or JSON .

Structure

0..1 0..* online | paused | standby | offline | not-ready Date Date udi-label-name 0..1 CodeableConcept The actual design of The 0..1 A single component of 1..1 The actual configuration settings Property value as a quantity Property value as a code, e.g., NTP4 (synced to NTP) Reference uri
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . Device TU DomainResource Item used in healthcare
+ Rule: only one Device.name.display SHALL be true when there is more than one Device.name

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier 0..* Identifier Instance identifier

. . . definition 0..1 Reference canonical ( DeviceDefinition ) The reference to the definition for the device
. . . udiCarrier Σ 0..* BackboneElement Unique Device Identifier (UDI) Barcode string value

. . . . deviceIdentifier Σ 1..1 string Mandatory fixed portion of UDI
. . . . issuer deviceIdentifierSystem 0..1 uri The namespace for the device identifier value
0..1
. . . . issuer Σ 1..1 uri UDI Issuing Organization
. . . . jurisdiction 0..1 uri Regional UDI authority
. . . . carrierAIDC Σ 0..1 base64Binary UDI Machine Readable Barcode String value
. . . . carrierHRF Σ 0..1 string UDI Human Readable Barcode String value
. . . . entryType 0..1 code barcode | rfid | manual + | card | self-reported | electronic-transmission | unknown
UDIEntryType Binding: UDI Entry Type ( Required )
. . statusReason . availabilityStatus 0..1 CodeableConcept lost | transduc-discon damaged | hw-discon destroyed | off available
FHIRDeviceStatusReason Binding: FHIR Device Availability Status ( Extensible )
. . distinctIdentifier . biologicalSourceEvent 0..1 string Identifier A production identifier of the donation, collection, or pooling event from which biological material in this device was derived
The distinct identification string
. . . manufacturer 0..1 string Name of device manufacturer
. . . manufactureDate 0..1 dateTime A production identifier that indicates the date when the device was made
. . . expirationDate 0..1 dateTime A production identifier that indicates the date and time of expiry of this device (if applicable)
. . . lotNumber 0..1 string A production identifier that indicates the Lot number of manufacture
. . . serialNumber 0..1 string A production identifier that indicates the Serial number assigned by the manufacturer
. . deviceName . name C 0..* BackboneElement The name or names of the device as given by known to the manufacturer and/or patient

. . . name . value Σ 1..1 string The name of term that names the device
. . . . type Σ 1..1 code CodeableConcept registered-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other
DeviceNameType Binding: Device Name Type ( Required Extensible )
. . . . display ?! Σ C 0..1 boolean The preferred device name
. . . modelNumber 0..1 string The manufacturer's model number for the device
. . . partNumber 0..1 string The part number or catalog number of the device
. . . type category 0..* CodeableConcept Indicates a high-level grouping of the device
Binding: FHIR Device Category ( Example )

. . . type 0..* CodeableConcept The kind or type of device
Binding: Device Type ( Example )

. . specialization . deviceVersion 0..* BackboneElement The capabilities supported on a device, the standards to which actual design of the device conforms for a particular purpose, and used for or software version running on the communication device

. . . systemType . type 0..1 CodeableConcept The type of the device version, e.g. manufacturer, approved, internal
Binding: Device Version Type ( Example )
1..1
. . . . component 0..1 Identifier The standard that is used hardware or software module of the device to operate and communicate which the version applies
. . . . version installDate 0..1 dateTime The date the version was installed on the device
0..1
. . . . value 1..1 string The version of the standard that is used to operate and communicate text
. . version . conformsTo 0..* BackboneElement Identifies the device standards, specifications, or software version running on formal guidances for the capabilities supported by the device

. . . type . category 0..1 CodeableConcept Describes the common type of the device version standard, specification, or formal guidance. communication | performance | measurement
Binding: Device Specification Category ( Example )
. . . component . specification 1..1 Identifier CodeableConcept Identifies the standard, specification, or formal guidance that the device version adheres to
Binding: Device Specification Type ( Example )
. . . value . version 0..1 string Specific form or variant of the standard
The version text
. . . property 0..* BackboneElement Inherent, essentially fixed, characteristics of a device as it actually operates, the device. e.g., regulation status, time properties properties, size, material, etc.

. . . . type 1..1 CodeableConcept Code that specifies the property DeviceDefinitionPropetyCode (Extensible) being represented
Binding: Device Property Type (Example only) ( Example )
. . . valueQuantity . value[x] 1..1 Value of the property
0..*
. . . . . valueQuantity Quantity
. . . valueCode . . valueCodeableConcept 0..* CodeableConcept
. . . . patient . valueString string
. . . . . valueBoolean 0..1 Reference ( Patient boolean ) Patient to whom Device is affixed
. . . . owner . valueInteger integer
. . . . . valueRange 0..1 Reference ( Organization Range ) Organization responsible for device
. . . . . contact valueAttachment Attachment
. . . additive 0..* ContactPoint BackboneElement Material added to a container device
Details for human/organization for support
. . . location . type 1..1 CodeableReference ( SubstanceDefinition ) The additive substance
Binding: Substance Code ( Example )
0..1
. . . . quantity ( Location ) 0..1 SimpleQuantity Quantity of additive substance within container
Where the device is found
. . url . contact 0..* ContactPoint Details for human/organization for support

0..1
. . . location Network address to contact 0..1 Reference ( Location ) Where the device is found
. . . note 0..* Annotation Device notes and comments

. . . safety Σ 0..* CodeableConcept Safety Characteristics of Device
Binding: Device Safety ( Example )

. . . parent 0..1 Reference ( Device ) The parent higher level or encompassing device that this device is a logical part of

doco Documentation for this format icon

See the Extensions for this resource

UML Diagram ( Legend )

Device ( DomainResource ) Unique instance identifiers assigned to a device by manufacturers other organizations or owners identifier : Identifier [0..*] The reference to the definition for the device definition : Reference canonical [0..1] « DeviceDefinition » Status The Device record status. This is not the status of the Device device like availability (this element modifies the meaning of other elements) status : code [0..1] « The availability status of the device. null (Strength=Required) FHIRDeviceStatus ! » Reason for the dtatus The availability of the Device availability device statusReason availabilityStatus : CodeableConcept [0..*] [0..1] « The availability status reason of the device. null (Strength=Extensible) FHIRDeviceStatusReason FHIRDeviceAvailabilityStatus + » The distinct identification string as required by regulation for a human cell, tissue, A production identifier of the donation, collection, or cellular and tissue-based product pooling event from which biological material in this device was derived distinctIdentifier biologicalSourceEvent : string Identifier [0..1] A name of the manufacturer or entity legally responsible for the device manufacturer : string [0..1] The date and time when the device was manufactured manufactureDate : dateTime [0..1] The date and time beyond which this device is no longer valid or should not be used (if applicable) expirationDate : dateTime [0..1] Lot number assigned by the manufacturer lotNumber : string [0..1] The serial number assigned by the organization when the device was manufactured serialNumber : string [0..1] The manufacturer's model number for the device modelNumber : string [0..1] The part number or catalog number of the device partNumber : string [0..1] The kind Devices may be associated with one or type of device more categories type category : CodeableConcept [0..1] [0..*] « Codes to identify medical devices. null (Strength=Example) DeviceType FHIRDeviceCategory ?? » Patient information, If the The kind or type of device. A device is affixed to a person patient : Reference [0..1] « Patient » An organization instance may have more than one type - in which case those are the types that is responsible for apply to the provision and ongoing maintenance specific instance of the device owner type : Reference CodeableConcept [0..1] [0..*] « Organization null (Strength=Example) DeviceType ?? » Contact details for an organization or a particular human that is responsible for the device contact : ContactPoint [0..*] The place where the device can be found location : Reference [0..1] « Location » A network address on which the device may be contacted directly url : uri [0..1] Descriptive information, usage information or implantation information that is not captured in an existing element note : Annotation [0..*] Provides additional safety characteristics about a medical device. For example devices containing latex safety : CodeableConcept [0..*] « null (Strength=Example) DeviceSafety ?? » The parent higher level or encompassing device that this device is a logical part of parent : Reference [0..1] « Device » UdiCarrier The device identifier (DI) (UDI-DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device. The UDI-DI portion is placed on a device label or package. Note that the DeviceDefinition may include multiple UDI-DIs if it is sold in multiple jurisdictions deviceIdentifier : string [1..1] Establishes the namespace for the issuing agency's system (e.g, GS1's GTIN, ICCBBA's ISBT-128) used to create the device identifier deviceIdentifierSystem : uri [0..1] Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include : include: 1) GS1: http://hl7.org/fhir/NamingSystem/gs1-di, 2) HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-dI, http://hl7.org/fhir/NamingSystem/hibcc-diI, 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 # Informationsstelle für Arzneispezialitäten (IFA GmbH) (EU only): http://hl7.org/fhir/NamingSystem/ifa-gmbh-di issuer : uri [0..1] [1..1] 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 http://hl7.org/fhir/NamingSystem/us-fda-udi or in the European Union by the European Commission http://hl7.org/fhir/NamingSystem/eu-ec-udi jurisdiction : uri [0..1] 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 , 2D Matrix, or RFID. Because of limitations on character sets in XML Some AIDC representations contain non-printable characters and the need to round-trip JSON data through XML, cannot be represented in a string format. For this reason, AIDC Formats *SHALL* format SHALL be base64 base64Binary encoded carrierAIDC : base64Binary [0..1] The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device carrierHRF : string [0..1] A coded entry to indicate how the data was entered entryType : code [0..1] « Codes to identify how UDI data was entered. null (Strength=Required) UDIEntryType ! » DeviceName Name The actual name of that identifies the device name value : string [1..1] The type Indicates the kind of deviceName. UDILabelName name. RegisteredName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName type : code CodeableConcept [1..1] « The type of null (Strength=Extensible) DeviceNameType + » Indicates the default or preferred name to be displayed (this element modifies the device meaning of other elements) display : boolean [0..1] « This element has or is referred by. (Strength=Required) affected by some invariants DeviceNameType ! C » Specialization DeviceVersion The standard that is used to operate and communicate type of the device version, e.g. manufacturer, approved, internal systemType type : CodeableConcept [1..1] [0..1] « null (Strength=Example) DeviceVersionType ?? » The version hardware or software module of the standard that is used device to operate and communicate which the version applies component : Identifier [0..1] The date the version was installed on the device installDate : string dateTime [0..1] The version text value : string [1..1] Version ConformsTo The Describes the type of the device version standard, specification, or formal guidance type category : CodeableConcept [0..1] « null (Strength=Example) DeviceSpecificationCategory ?? » A single component of Code that identifies the specific standard, specification, protocol, formal guidance, regulation, legislation, or certification scheme to which the device version adheres component specification : Identifier CodeableConcept [0..1] [1..1] « null (Strength=Example) DeviceSpecificationType ?? » The version text Identifies the specific form or variant of the standard, specification, or formal guidance. This may be a 'version number', release, document edition, publication year, or other label value version : string [1..1] [0..1] Property Code that specifies the property DeviceDefinitionPropetyCode (Extensible) property, such as resolution, color, size, being represented type : CodeableConcept [1..1] « null (Strength=Example) DevicePropertyType ?? » Property The value as a quantity of the property specified by the associated property.type code valueQuantity value[x] : DataType [1..1] « Quantity [0..*] | CodeableConcept | string | boolean | integer | Range | Attachment » Additive Property value The type of the substance added to the container. This is represented as a code, e.g., NTP4 (synced to NTP) concept from a code system or described in a Substance resource valueCode type : CodeableConcept CodeableReference [0..*] [1..1] « SubstanceDefinition ; null (Strength=Example) SubstanceCode ?? » The quantity of the additive substance in the container; may be volume, dimensions, or other appropriate measurements, depending on the container and additive substance type quantity : Quantity ( SimpleQuantity ) [0..1] Unique device identifier Device Identifier (UDI) assigned to placed on a device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction UDIs if it is sold, or for sold in multiple jurisdictions it could have been sold udiCarrier [0..*] 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 deviceName name [0..*] The capabilities supported on a device, the standards to which actual design of the device conforms for a particular purpose, and used for or software version running on the communication device specialization deviceVersion [0..*] The actual design of Identifies the device standards, specifications, or software version running on formal guidances for the capabilities supported by the device. The device may be certified as conformant to these specifications e.g., communication, performance, process, measurement, or specialization standards version conformsTo [0..*] The actual configuration settings Static or essentially fixed characteristics or features of a the device as it actually operates, e.g., regulation status, (e.g., time properties or timing attributes, resolution, accuracy, intended use or instructions for use, and physical attributes) that are not otherwise captured in more specific attributes property [0..*] Material added to a container device (typically used in specimen collection or initial processing). The material may be added by the device manufacturer or by a different party subsequent to manufacturing additive [0..*]

XML Template

<

<Device xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Instance identifier --></identifier>
 <</definition>
 <
  <
  <<a href="device-definitions.html#Device.udiCarrier.issuer" title="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." class="dict">
  <
  <
  <
  <

 <definition><!-- 0..1 canonical(DeviceDefinition) The reference to the definition for the device --></definition>
 <udiCarrier>  <!-- 0..* Unique Device Identifier (UDI) value -->
  <deviceIdentifier value="[string]"/><!-- 1..1 Mandatory fixed portion of UDI -->
  <deviceIdentifierSystem value="[uri]"/><!-- 0..1 The namespace for the device identifier value -->
  <issuer value="[uri]"/><!-- 1..1 UDI Issuing Organization -->
  <jurisdiction value="[uri]"/><!-- 0..1 Regional UDI authority -->
  <carrierAIDC value="[base64Binary]"/><!-- 0..1 UDI Machine Readable value -->
  <carrierHRF value="[string]"/><!-- 0..1 UDI Human Readable value -->
  <entryType value="[code]"/><!-- 0..1 barcode | rfid | manual | card | self-reported | electronic-transmission | unknown -->

 </udiCarrier>
 <
 <</statusReason>
 <
 <
 <
 <
 <
 <
 <
  <
  <<a href="device-definitions.html#Device.deviceName.type" title="The type of deviceName.
UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName." class="dict">
 </deviceName>
 <
 <
 <</type>
 <
  <</systemType>
  <
 </specialization>
 <
  <</type>
  <</component>
  <
 </version>
 <
  <</type>
  <</valueQuantity>
  <</valueCode>

 <status value="[code]"/><!-- 0..1 active | inactive | entered-in-error | unknown -->
 <availabilityStatus><!-- 0..1 CodeableConcept lost | damaged | destroyed | available --></availabilityStatus>
 <biologicalSourceEvent><!-- 0..1 Identifier A production identifier of the donation, collection, or pooling event from which biological material in this device was derived --></biologicalSourceEvent>
 <manufacturer value="[string]"/><!-- 0..1 Name of device manufacturer -->
 <manufactureDate value="[dateTime]"/><!-- 0..1 A production identifier that indicates the date when the device was made -->
 <expirationDate value="[dateTime]"/><!-- 0..1 A production identifier that indicates the date and time of expiry of this device (if applicable) -->
 <lotNumber value="[string]"/><!-- 0..1 A production identifier that indicates the Lot number of manufacture -->
 <serialNumber value="[string]"/><!-- 0..1 A production identifier that indicates the Serial number assigned by the manufacturer -->
 <name>  <!-- I 0..* The name or names of the device as known to the manufacturer and/or patient -->
  <value value="[string]"/><!-- 1..1 The term that names the device -->
  <type><!-- 1..1 CodeableConcept registered-name | user-friendly-name | patient-reported-name --></type>
  <display value="[boolean]"/><!-- I 0..1 The preferred device name -->
 </name>
 <modelNumber value="[string]"/><!-- 0..1 The manufacturer's model number for the device -->
 <partNumber value="[string]"/><!-- 0..1 The part number or catalog number of the device -->
 <category><!-- 0..* CodeableConcept Indicates a high-level grouping of the device --></category>
 <type><!-- 0..* CodeableConcept The kind or type of device --></type>
 <deviceVersion>  <!-- 0..* The actual design of the device or software version running on the device -->
  <type><!-- 0..1 CodeableConcept The type of the device version, e.g. manufacturer, approved, internal --></type>
  <component><!-- 0..1 Identifier The hardware or software module of the device to which the version applies --></component>
  <installDate value="[dateTime]"/><!-- 0..1 The date the version was installed on the device -->
  <value value="[string]"/><!-- 1..1 The version text -->
 </deviceVersion>
 <conformsTo>  <!-- 0..* Identifies the standards, specifications, or formal guidances for the capabilities supported by the device -->
  <category><!-- 0..1 CodeableConcept Describes the common type of the standard, specification, or formal guidance.  communication | performance | measurement --></category>
  <specification><!-- 1..1 CodeableConcept Identifies the standard, specification, or formal guidance that the device adheres to --></specification>
  <version value="[string]"/><!-- 0..1 Specific form or variant of the standard -->
 </conformsTo>
 <property>  <!-- 0..* Inherent, essentially fixed, characteristics of the device.  e.g., time properties, size, material, etc. -->
  <type><!-- 1..1 CodeableConcept Code that specifies the property being represented --></type>
  <value[x]><!-- 1..1 Quantity|CodeableConcept|string|boolean|integer|Range|
    Attachment Value of the property --></value[x]>
 </property>
 <</patient>
 <</owner>

 <additive>  <!-- 0..* Material added to a container device -->
  <type><!-- 1..1 CodeableReference(SubstanceDefinition) The additive substance --></type>
  <quantity><!-- 0..1 Quantity(SimpleQuantity) Quantity of additive substance within container --></quantity>
 </additive>

 <contact><!-- 0..* ContactPoint Details for human/organization for support --></contact>
 <location><!-- 0..1 Reference(Location) Where the device is found --></location>
 <

 <note><!-- 0..* Annotation Device notes and comments --></note>
 <</safety>
 <</parent>

 <safety><!-- 0..* CodeableConcept Safety Characteristics of Device --></safety>
 <parent><!-- 0..1 Reference(Device) The higher level or encompassing device that this device is a logical part of --></parent>

</Device>

JSON Template

{doco
  "resourceType" : "",

  "resourceType" : "Device",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Instance identifier
  "
  "
    "
    "<a href="device-definitions.html#Device.udiCarrier.issuer" title="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." class="dict">issuer
    "
    "
    "
    "

  "definition" : "<canonical(DeviceDefinition)>", // The reference to the definition for the device
  "udiCarrier" : [{ // Unique Device Identifier (UDI) value
    "deviceIdentifier" : "<string>", // R!  Mandatory fixed portion of UDI
    "deviceIdentifierSystem" : "<uri>", // The namespace for the device identifier value
    "issuer" : "<uri>", // R!  UDI Issuing Organization
    "jurisdiction" : "<uri>", // Regional UDI authority
    "carrierAIDC" : "<base64Binary>", // UDI Machine Readable value
    "carrierHRF" : "<string>", // UDI Human Readable value
    "entryType" : "<code>" // barcode | rfid | manual | card | self-reported | electronic-transmission | unknown

  }],
  "
  "
  "
  "
  "
  "
  "
  "
  "
    "
    "<a href="device-definitions.html#Device.deviceName.type" title="The type of deviceName.
UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName." class="dict">type

  "status" : "<code>", // active | inactive | entered-in-error | unknown
  "availabilityStatus" : { CodeableConcept }, // lost | damaged | destroyed | available
  "biologicalSourceEvent" : { Identifier }, // A production identifier of the donation, collection, or pooling event from which biological material in this device was derived
  "manufacturer" : "<string>", // Name of device manufacturer
  "manufactureDate" : "<dateTime>", // A production identifier that indicates the date when the device was made
  "expirationDate" : "<dateTime>", // A production identifier that indicates the date and time of expiry of this device (if applicable)
  "lotNumber" : "<string>", // A production identifier that indicates the Lot number of manufacture
  "serialNumber" : "<string>", // A production identifier that indicates the Serial number assigned by the manufacturer
  "name" : [{ // I The name or names of the device as known to the manufacturer and/or patient
    "value" : "<string>", // R!  The term that names the device
    "type" : { CodeableConcept }, // R!  registered-name | user-friendly-name | patient-reported-name
    "display" : <boolean> // I The preferred device name

  }],
  "
  "
  "
  "
    "
    "

  "modelNumber" : "<string>", // The manufacturer's model number for the device
  "partNumber" : "<string>", // The part number or catalog number of the device
  "category" : [{ CodeableConcept }], // Indicates a high-level grouping of the device
  "type" : [{ CodeableConcept }], // The kind or type of device
  "deviceVersion" : [{ // The actual design of the device or software version running on the device
    "type" : { CodeableConcept }, // The type of the device version, e.g. manufacturer, approved, internal
    "component" : { Identifier }, // The hardware or software module of the device to which the version applies
    "installDate" : "<dateTime>", // The date the version was installed on the device
    "value" : "<string>" // R!  The version text

  }],
  "
    "
    "
    "

  "conformsTo" : [{ // Identifies the standards, specifications, or formal guidances for the capabilities supported by the device
    "category" : { CodeableConcept }, // Describes the common type of the standard, specification, or formal guidance.  communication | performance | measurement
    "specification" : { CodeableConcept }, // R!  Identifies the standard, specification, or formal guidance that the device adheres to
    "version" : "<string>" // Specific form or variant of the standard

  }],
  "
    "
    "
    "

  "property" : [{ // Inherent, essentially fixed, characteristics of the device.  e.g., time properties, size, material, etc.
    "type" : { CodeableConcept }, // R!  Code that specifies the property being represented
    // value[x]: Value of the property. One of these 7:

    "valueQuantity" : { Quantity },
    "valueCodeableConcept" : { CodeableConcept },
    "valueString" : "<string>",
    "valueBoolean" : <boolean>,
    "valueInteger" : <integer>,
    "valueRange" : { Range },
    "valueAttachment" : { Attachment }
  }],
  "additive" : [{ // Material added to a container device
    "type" : { CodeableReference(SubstanceDefinition) }, // R!  The additive substance
    "quantity" : { Quantity(SimpleQuantity) } // Quantity of additive substance within container

  }],
  "
  "

  "contact" : [{ ContactPoint }], // Details for human/organization for support
  "location" : { Reference(Location) }, // Where the device is found
  "

  "note" : [{ Annotation }], // Device notes and comments
  "
  "

  "safety" : [{ CodeableConcept }], // Safety Characteristics of Device
  "parent" : { Reference(Device) } // The higher level or encompassing device that this device is a logical part of

}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:;

[ a fhir:Device;

  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from 
  # from 
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:<a href="device-definitions.html#Device.udiCarrier.issuer" title="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." class="dict">Device.udiCarrier.issuer
    fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:<a href="device-definitions.html#Device.deviceName.type" title="The type of deviceName.
UDILabelName | UserFriendlyName | PatientReportedName | ManufactureDeviceName | ModelName." class="dict">Device.deviceName.type
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
    fhir:
    fhir:
    fhir:
  ], ...;
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension
  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* Instance identifier
  fhir:definition [ canonical(DeviceDefinition) ] ; # 0..1 The reference to the definition for the device
  fhir:udiCarrier ( [ # 0..* Unique Device Identifier (UDI) value
    fhir:deviceIdentifier [ string ] ; # 1..1 Mandatory fixed portion of UDI
    fhir:deviceIdentifierSystem [ uri ] ; # 0..1 The namespace for the device identifier value
    fhir:issuer [ uri ] ; # 1..1 UDI Issuing Organization
    fhir:jurisdiction [ uri ] ; # 0..1 Regional UDI authority
    fhir:carrierAIDC [ base64Binary ] ; # 0..1 UDI Machine Readable value
    fhir:carrierHRF [ string ] ; # 0..1 UDI Human Readable value
    fhir:entryType [ code ] ; # 0..1 barcode | rfid | manual | card | self-reported | electronic-transmission | unknown
  ] ... ) ;
  fhir:status [ code ] ; # 0..1 active | inactive | entered-in-error | unknown
  fhir:availabilityStatus [ CodeableConcept ] ; # 0..1 lost | damaged | destroyed | available
  fhir:biologicalSourceEvent [ Identifier ] ; # 0..1 A production identifier of the donation, collection, or pooling event from which biological material in this device was derived
  fhir:manufacturer [ string ] ; # 0..1 Name of device manufacturer
  fhir:manufactureDate [ dateTime ] ; # 0..1 A production identifier that indicates the date when the device was made
  fhir:expirationDate [ dateTime ] ; # 0..1 A production identifier that indicates the date and time of expiry of this device (if applicable)
  fhir:lotNumber [ string ] ; # 0..1 A production identifier that indicates the Lot number of manufacture
  fhir:serialNumber [ string ] ; # 0..1 A production identifier that indicates the Serial number assigned by the manufacturer
  fhir:name ( [ # 0..* I The name or names of the device as known to the manufacturer and/or patient
    fhir:value [ string ] ; # 1..1 The term that names the device
    fhir:type [ CodeableConcept ] ; # 1..1 registered-name | user-friendly-name | patient-reported-name
    fhir:display [ boolean ] ; # 0..1 I The preferred device name
  ] ... ) ;
  fhir:modelNumber [ string ] ; # 0..1 The manufacturer's model number for the device
  fhir:partNumber [ string ] ; # 0..1 The part number or catalog number of the device
  fhir:category  ( [ CodeableConcept ] ... ) ; # 0..* Indicates a high-level grouping of the device
  fhir:type  ( [ CodeableConcept ] ... ) ; # 0..* The kind or type of device
  fhir:deviceVersion ( [ # 0..* The actual design of the device or software version running on the device
    fhir:type [ CodeableConcept ] ; # 0..1 The type of the device version, e.g. manufacturer, approved, internal
    fhir:component [ Identifier ] ; # 0..1 The hardware or software module of the device to which the version applies
    fhir:installDate [ dateTime ] ; # 0..1 The date the version was installed on the device
    fhir:value [ string ] ; # 1..1 The version text
  ] ... ) ;
  fhir:conformsTo ( [ # 0..* Identifies the standards, specifications, or formal guidances for the capabilities supported by the device
    fhir:category [ CodeableConcept ] ; # 0..1 Describes the common type of the standard, specification, or formal guidance.  communication | performance | measurement
    fhir:specification [ CodeableConcept ] ; # 1..1 Identifies the standard, specification, or formal guidance that the device adheres to
    fhir:version [ string ] ; # 0..1 Specific form or variant of the standard
  ] ... ) ;
  fhir:property ( [ # 0..* Inherent, essentially fixed, characteristics of the device.  e.g., time properties, size, material, etc.
    fhir:type [ CodeableConcept ] ; # 1..1 Code that specifies the property being represented
    # value[x] : 1..1 Value of the property. One of these 7
      fhir:value [  a fhir:Quantity ; Quantity ]
      fhir:value [  a fhir:CodeableConcept ; CodeableConcept ]
      fhir:value [  a fhir:String ; string ]
      fhir:value [  a fhir:Boolean ; boolean ]
      fhir:value [  a fhir:Integer ; integer ]
      fhir:value [  a fhir:Range ; Range ]
      fhir:value [  a fhir:Attachment ; Attachment ]
  ] ... ) ;
  fhir:additive ( [ # 0..* Material added to a container device
    fhir:type [ CodeableReference(SubstanceDefinition) ] ; # 1..1 The additive substance
    fhir:quantity [ Quantity(SimpleQuantity) ] ; # 0..1 Quantity of additive substance within container
  ] ... ) ;
  fhir:contact  ( [ ContactPoint ] ... ) ; # 0..* Details for human/organization for support
  fhir:location [ Reference(Location) ] ; # 0..1 Where the device is found
  fhir:note  ( [ Annotation ] ... ) ; # 0..* Device notes and comments
  fhir:safety  ( [ CodeableConcept ] ... ) ; # 0..* Safety Characteristics of Device
  fhir:parent [ Reference(Device) ] ; # 0..1 The higher level or encompassing device that this device is a logical part of

]

Changes since Release 3 from both R4 and R4B

Device
Device.definition
  • Added Element Type changed from Reference(DeviceDefinition) to canonical(DeviceDefinition)
Device.udiCarrier Device.udiCarrier.deviceIdentifier
  • Added Element Min Cardinality changed from 0 to 1
Device.udiCarrier.deviceIdentifier Device.udiCarrier.deviceIdentifierSystem
  • Added Element
Device.udiCarrier.issuer
  • Added Element Min Cardinality changed from 0 to 1
Device.udiCarrier.jurisdiction Device.udiCarrier.entryType
  • Added Element Add code electronic-transmission
Device.udiCarrier.carrierAIDC Device.availabilityStatus
  • Added Element
Device.udiCarrier.carrierHRF Device.biologicalSourceEvent
  • Added Element
Device.name
  • Renamed from deviceName to name
Device.udiCarrier.entryType Device.name.value
  • Added Mandatory Element
Device.status Device.name.type
  • Moved from Device.deviceName to Device.name
  • Type changed from code to CodeableConcept
  • Change value set binding strength from http://hl7.org/fhir/ValueSet/device-status required to http://hl7.org/fhir/ValueSet/device-status|4.0.1 extensible
Device.statusReason Device.name.display
  • Added Element
Device.distinctIdentifier Device.category
  • Added Element
Device.serialNumber Device.type
  • Added Element Max Cardinality changed from 1 to *
Device.deviceName Device.deviceVersion
  • Added Element
Device.deviceName.name Device.deviceVersion.type
  • Added Mandatory Element
Device.deviceName.type Device.deviceVersion.component
  • Added Mandatory Element
Device.modelNumber Device.deviceVersion.installDate
  • Added Element
Device.partNumber Device.deviceVersion.value
  • Added Mandatory Element
Device.specialization Device.conformsTo
  • Added Element Renamed from specialization to conformsTo
Device.specialization.systemType Device.conformsTo.category
  • Added Mandatory Element
Device.specialization.version Device.conformsTo.specification
  • Added Mandatory Element
Device.version Device.conformsTo.version
  • Max Cardinality changed from 1 to * Type changed Moved from string Device.specialization to BackboneElement Device.conformsTo
Device.version.type Device.property.value[x]
  • Added Mandatory Element
Device.version.component Device.additive
  • Added Element
Device.version.value Device.additive.type
  • Added Mandatory Element
Device.property Device.additive.quantity
  • Added Element
Device.property.type Device.statusReason
  • Added Mandatory Element Deleted (-> reason was removed. DeviceAssociation can be used)
Device.distinctIdentifier
  • Deleted
Device.deviceName.name
  • Deleted
Device.specialization.systemType
  • Deleted
Device.version
  • Deleted
Device.property.valueQuantity
  • Added Element Deleted
Device.property.valueCode
  • Added Element Deleted
Device.parent Device.patient
  • Added Element Deleted (-> patient association is in DeviceAssociation)
Device.udi Device.owner
  • deleted Deleted
Device.model Device.url
  • deleted Deleted

See the Full Difference for further information

This analysis is available for R4 as XML or JSON . See R3 <--> R4 Conversion Maps (status = 9 tests that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors). ) for R4B as XML or JSON .

 

See the Profiles & Extensions and the alternate Additional definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions , the spreadsheet version & the dependency analysis

Device.status Device.statusReason Device.deviceName.type Device.type
Path Definition ValueSet Type Reference Documentation
Device.udiCarrier.entryType UDIEntryType Required

Codes to identify how UDI data was entered.

Device.status FHIRDeviceStatus Required UDIEntryType

The status of the Device record.

Device.availabilityStatus FHIRDeviceAvailabilityStatus Extensible

The availability status of the device.

Device.name.type DeviceNameType Required Extensible FHIRDeviceStatus

The type of name the device is referred by.

Device.category FHIRDeviceCategory Example

The availability status reason association state of the device.

Device.type DeviceType Extensible Example

Codes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example.

Device.deviceVersion.type FHIRDeviceStatusReason DeviceVersionType Example

Describes the type of version

Device.conformsTo.category DeviceSpecificationCategory (a valid code from FHIR Device Specialization Category ) Example

The type kind of name standards used by the device is referred by. device.

Device.conformsTo.specification DeviceSpecificationType Required Example

The type or specification of a standard that devices can adhere to

Device.property.type DeviceNameType DevicePropertyType (a valid code from Device Property Type (Example only) ) Example

The fixed characteristics or conditions of the device. These codes are for example purposes only.

Device.additive.type SubstanceCode Example Codes to identify medical devices.

This value set contains concept codes for specific substances. It includes codes from SNOMED icon where concept is-a 105590001 (Substance (substance))

Device.safety DeviceSafety Example DeviceType

Codes used to identify medical devices safety characteristics. These codes are taken from the NCI Thesaurus icon and are provided here as a suggestive example.

UniqueKey Level Location Description Expression
img  dev-1 Rule (base) only one Device.name.display SHALL be true when there is more than one Device.name name.where(display=true).count() <= 1

Nearly all devices are assigned a string of characters to represent one or more identifiers or codes, which are usually printed or affixed to the device using either barcodes or RFIDs. The identifier or code can come from the manufacturer (for example, a 'serial number', 'reference number', or 'catalog number'), various institution and registries. Any of these identifiers or codes assigned to the device can and should be recorded in the device resource. However, there can there can be confusion where to represent them in the resource because codes and identifiers are represented in FHIR as semantically distinct elements and because organizations may conflate the term 'code' for an identifier or 'identifier' for a code in their names.

The identifier element is only intended for use when it's an actual identifier for a specific instance of a device. That would mean that each device would have a separate serial number and would be represented using this element - devices without serial numbers (for example, a box of syringes) would not. Concepts such as a reference number or catalog number or GTIN describe a code which represents a kind of device and are conveyed using the type element. Some sources of standard codes for devices and translations within type are listed below:

For systems that do have a system URI for device types (indicating the model number or part number), they can and should appear as codings in Device.type .

Device.type relates DeviceDefinition.classification.type using the same binding enabling referencing. Please see the Search Parameters for details on how to search for devices by type.

The International Medical Device Regulators Forum IMDRF UDI Working Group published UDI System for Medical Devices (Version 2.0) icon , the base specification for Unique Device Identifiers (UDI). The United States Food and Drug Administration has produced an implementation guide icon for Unique Device Identifiers (UDI) which implements the IMDRF specification and other jurisdictions may produce similar IMDRF implementation guides as well. The full UDI string that represents the barcode as printed on the packaging of the device or Automatic Identification and Data Capture (AIDC) representation is called the "UDI carrier". The UDI has 2 components*: components(1):

  • Device identifier (DI)**, (DI)(2), which is the actual identification component
  • Production identifier(s)(PI) which provide the means to track a device through its manufacture, distribution and use.
*non-UDI
  1. non-UDI elements may also appear within the UDI carrier. **a
  2. a "GTIN" (sometimes also called an EAN number) is a code developed by GS1 icon for the kind of device not an identifier for the device. A GTIN may appear on its own or it may appear in a UDI string as the DI component.

The DI of the UDI may be stored in a jurisdictional repository and used as the primary key to access other device information. For example, in the United States, the DI of the UDI is submitted in a device record to the Global Unique Device Identification Database (GUDID) icon . The UDI may identify an instance of a device uniquely (when the PI includes a serial number), or it may just identify the type of the device. The UDI is parsed into its constituent parts (DI, PI and other elements) by parsing rules developed by each Issuing Agency standard. Where the device has an assigned UDI, the other details carried in the resource (e.g., lot, expiration date, etc.) SHALL be consistent with the information encoded in the UDI string or registered in the local repository.

Best practice guidelines for transmitting UDI data using the Device resource dictate transmitting both the UDI Carrier and all components found within the UDI as described in Device UDI Mapping . Several examples are provided for further guidance.

Device.status is about the record, while .availabilityStatus is about the device itself.

Search parameters for this resource. See also the full list of search parameters for this resource , and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
biological-source-event token The biological source for the device Device.biologicalSourceEvent
code token The definition / type of the device (code) Device.type | Device.definition.resolve().classification.type
code-value-concept composite Code and value parameter pair On Device:
  specification: specification.ofType(CodeableConcept)
  version: version.ofType(string)
definition reference The definition / type of the device Device.definition
( DeviceDefinition )
device-name string A server defined search that may match any of the string fields in Device.deviceName Device.name or Device.type. Device.deviceName.name Device.name.value | Device.type.coding.display | Device.type.text
expiration-date date The expiration date of the device Device.expirationDate
identifier token Instance id from manufacturer, owner, and others Device.identifier
location reference A location, where the resource is found Device.location
( Location )
lot-number string The lot number of the device Device.lotNumber
manufacture-date date The manufacture date of the device Device.manufactureDate
manufacturer string The manufacturer of the device Device.manufacturer
model string The model of the device Device.modelNumber
parent organization reference The organization responsible for the parent device Device.owner Device.parent
( Organization Device )
serial-number patient reference string Patient information, if The serial number of the resource is affixed to a person device Device.patient ( Patient Device.serialNumber | Device.identifier.where(type='SNO')
) specification token The standards, specifications, or formal guidances. Device.conformsTo.specification
specification-version composite A composite of both specification and version On Device.conformsTo:
  specification: specification
  version: version
status token active | inactive | entered-in-error | unknown Device.status
type token The type of the device Device.type
udi-carrier-hrf udi-carrier string

UDI Barcode (RFID or other technology) string in *HRF* HRF format.

Device.udiCarrier.carrierHRF
udi-di string The udi Device Identifier (DI) Device.udiCarrier.deviceIdentifier
version url uri string Network address to contact The specific version of the device Device.url Device.deviceVersion.value
version-type composite Value and type of version On Device.deviceVersion:
  type: type
  value: value