DeviceDefinition
Introduction
Note to Balloters: To ensure the DeviceDefinition resource is ready for Normative status, we are seeking ballot comments on the substantive content. The key changes made since R5 include:
- Updated DeviceDefinition to a CanonicalResource and the necessary element and search parameter changes.
- Removed DeviceDefinition.owner.
All OO Resources were updated to use the canonical, however other Resources (not owned by the OO Work Group) might not have the canonical reference to DeviceDefinition.
Scope and Usage
The DeviceDefinition resource is used to describe the common characteristics and capabilities of a device of a certain type or kind, e.g., a certain model or class of a device such as a x-ray model or personal wearable device model, whereas a Device resource documents an actual instance of a device such as the actual x-ray machine that is installed or the personal wearable device being worn. Devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health, as well as devices such as a machine, cellphone, computer, software, application, etc.
Devices can also be subdivided into the following categories:
Active device
'Active device' means any device, the operation of which depends on a source of energy other than that generated by the human body for that purpose, or by gravity, and which acts by changing the density of or converting that energy. Devices intended to transmit energy, substances or other elements between an active device and the patient, without any significant change, shall not be deemed to be active devices. Software shall also be deemed to be an active device. MDR (EU) 2017/745
Active Implantable Medical Devices include the definition for both active devices and implantable devices (see below). Examples include: Implantable cardiac pacemakers; Implantable defibrillator; Implantable neurostimulator systems; Leads, electrodes, adaptors for implantable pulse generators; Brachytherapy systems; Ventricular Assist Devices (VADs); Cochlear implants; Implantable infusion pumps; Implantable glucose monitors; Micro Electro-Mechanical Systems (MEMS); and their accessories where applicable.
Communicating device
This category of devices communicates electronically to peer information systems or possibly another device. In addition to patient observations for use by clinicians in providing care and for building a health record, the device communicates metadata about its own state and the protocol used to transfer that information.
To support the use and evaluate the reliability of the patient data, it is important to collect and record data about the identity and operational status of the device that generated the observations. The Device resource is an important locus for such information. The information it generates for clinical and other purposes goes into other resources such as the Observation or Medication resource depending upon what the device does. To support device-related information about Communicating Medical Devices the Device resource needs to have elements that describe not only the basic information like the serial number, manufacturer name and model number, but information about the protocol, its version, its certification, the properties it has to perform its purposed tasks such as internal clocks, synchronization state, resolution, etc.
Durable Medical Equipment
Equipment and supplies that provide therapeutic benefits to a patient in need because of certain medical conditions and/or illnesses, and which are ordered by a health care provider for everyday or extended use.
Examples include: oxygen equipment, suction pumps, traction equipment, home infusion services, continuous positive airway pressure (CPAP) devices, hospital beds, wheelchairs, crutches walkers, canes, or blood testing strips and meters for diabetics.
Home Use device
A home use medical device is a medical device intended for users in any environment outside of a professional healthcare facility (although that does not preclude such devices being used in a professional healthcare facility).
- A user is a patient (care recipient), caregiver, or family member that directly uses the device or provides assistance in using the device.
- A qualified healthcare professional is a licensed or non-licensed healthcare professional with proficient skill and experience with the use of the device so that they can aid or train care recipients and caregivers to use and maintain the device.
Implantable device
Implant means a device that is placed into a surgically or naturally formed cavity of the human body. A device is regarded as an implant for the purpose of this part only if it is intended to remain implanted continuously for a period of 30 days or more, unless the Commissioner determines otherwise to protect human health. 21CFR Part 860.3 Accessed 12 May 2022
'Implantable device' means any device, including those that are partially or wholly absorbed (i.e., a bioresorbable substance which is taken in or degraded) by the body, which is intended:
- to be totally introduced into the human body, or
- to replace an epithelial surface or the surface of the eye,
by clinical intervention and which is intended to remain in place after the procedure.
Any device intended to be partially introduced into the human body by clinical intervention and intended to remain in place after the procedure for at least 30 days shall also be deemed to be an implantable device; MDR (EU) 2017/745 Accessed 12 May 2022
InVitro Medical device
In vitro diagnostics (IVD) are tests done on samples such as blood or tissue that have been taken from the human body. In vitro diagnostics can detect diseases or other conditions, and can be used to monitor a person 's overall health to help cure, treat, or prevent diseases.
In vitro diagnostics may also be used in precision medicine to identify patients who are likely to benefit from specific treatments or therapies. These in vitro diagnostics can include next generation sequencing tests, which scan a person 's DNA to detect genomic variations.
Some tests are used in laboratory or other health professional settings and other tests are for consumers to use at home. US Food and Drug Administration Center for Devices and Radiological Health In Vitro Diagnostics and Drug Administration Center for Devices and Radiological Health In Vitro Diagnostics Accessed 12 May 2022
Patient-use device
Patient-use (also known as personal health device), or home use devices, intended for users in any environment outside of a professional healthcare facility. This includes devices intended for use in both professional healthcare facilities and homes US Food and Drug Administration Center for Devices and Radiological Health. Home Use Devices.
Accessed 13 March 2020. Personal Health Devices (PHDs) are the subset of patient-use devices that report their information to a peer via a protocol.
Personal Health device (PHD)
One class of communicating devices is the Personal Health Device or PHD. PHDs are medical devices that can be used by patients or others who are typically not medical professions, to gather patient observations and information. These devices can often be purchased in department stores or online by anyone. They may be regulated as medical devices, or not.
PHDs include the popular fitness trackers often combined with heart rate monitors, but also blood pressure monitors, weight scales, pulse oximeters, thermometers, and, for those that require them, glucose meters. Over time more sophisticated devices such as continuous glucose monitors, insulin pumps, vital signs monitors including ECGs, and even spirometers are entering the PHD consumer market. These devices communicate measurement data and data about themselves via a digital transport protocol to some peer entity, often a mobile phone or tablet. The protocol may follow a standard but most protocols are proprietary. In either case, it is common practice for manufacturers to provide free applications that run on these mobile platforms for the purpose of communicating with their devices.
The fields populated in the Device resource by PHDs, typically via a gateway, is the information a PHD reports about itself electronically. There is no input by the patient except for information the patient may enter on the device through some UI. This device reporting capability distinguishes communicating PHDs from the general set of patient-use devices.
Point-of-Care Device (PoCD)
Point-of-care medical devices (PoCD) are intended for use by qualified professionals. PoCDs are typically found at the patient's bedside and convey measurements and supporting data to receiving systems for use in electronic medical records, clinical decision support, and medical data archiving for aggregate quality measurement and research purposes.
PoCDs are of another level of complexity compared to PHDs: they include devices like multi-parameter physiological patient monitors, anesthesia workstations, infusion pumps and numerous other kinds of devices that provide near-real-time information about patient condition or therapy, potentially including dozens or hundreds of variables coming from a single device system. They may be structurally complex, involving multiple subsystems that are themselves complex, such as a ventilator or gas analyzer functioning within an anesthesia workstation, or pluggable modules in a patient monitor controlling invasive blood pressure or gathering EEG data.
Information systems using such data need to be able to understand the structure and dynamic state of the devices originating them. This requires more than a single Device resource - a hierarchy of Device resources is constructed carrying data about the top-level containing device (for example a monitor), and a hierarchy of contained Device resources representing subsystems (in the monitor, builtin and attached modular measurement capabilities), channels, and DeviceMetric resources representing individual measurements or computations.
Single-Use device
A device that is intended to be used on one individual during a single procedure; MDR (EU) 2017/745 Accessed 12 May 2022
Reusable device
Reusable medical devices are devices that health care providers can reuse to diagnose and treat one or multiple patients. Examples of reusable medical devices include surgical forceps, endoscopes and laryngoscopes. US Food and Drug Administration Center for Devices and Radiological Health Reusable Medical Devices
Software
A Device may be a software component or application. A software item like a data transformer or converter, or a clinical support algorithm, may be an independently deployed, managed and configured entity that contributes to patient care and needs to be documented just a surely as, say, a physical cardiac monitor. It can also represent the relationship of the software item to other device and information system components through reference linkages. This category includes software regardless of whether or not is regulated. Device instances documenting software items are important to traceability of data and analyzing adverse events, and so have important patient safety roles. These may also be considered Digital therapeutics (DTx) in some contexts.
Software as a medical device may include not only traditional applications but also standalone algorithms, rule engines, artificial intelligence (AI), machine learning (ML) components, and decision-support modules. These software-based devices may operate independently or be embedded within physical hardware to be used in clinical and non-clinical contexts.
Boundaries and Relationships
There are a number of resources that either represent other aspects of a device and/or reference a DeviceDefinition:
DeviceDefinition: this resource.
Device: Represents an actual instance of the device, references the DeviceDefinition for further description and characteristics of the device that do not change across the same “kind” of device. For example, the physical characteristic would not change, while the actual configuration used is within the valid configurations that may be documented in the DeviceDefinition.
Where the DeviceDefinition is referenced by other resources listed in References to this Resource, beyond Device, the DeviceDefinition is a choice between DeviceDefinition and a Device depending on whether a specific device is to be considered or a kind of device. For example one may indicate a specific device as part of a ServiceRequest order detail or a kind of device using DeviceDefinition; one may indicate a specific device to always perform the observation or a kind of device as part of an ObservationDefinition; one may document a specific device or kind of device used to collect a Specimen.
Note that in some jurisdictions a regulated product might not be considered a device, but may be regulated as a medication or a biologic. These boundaries are not controlled for in the FHIR Resources, but should be considered when working in the healthcare product space, specifically:
- Medication: Represents a medication, including its ingredients. Depending on jurisdictions, certain drugs may be classified as devices, or devices that include medications such as stents, may be classified as medications. These jurisdictional differences may lead to the same “thing” being documented using a Medication or DeviceDefinition and subsequently a Device.
- Substance: A homogenuous material with a definite composition that may be used in a medication, nutrition product, and/or the production of a biologically derived product or device, but is in itself not considered either of those from a jurisdictional perspective.
- BiologicallyDerivedProduct: A material substance originating from a biological entity, while a device is primarily manufactured from non-biological materials, although may contain some biologically derived content making it similarly subject to jurisdictional determination whether to consider such “thing” a device or medication.
- NutritionProduct: A food or supplement that is consumed by a patient for nutritional value. A device may be used to enable feeding a patient, or may be ingested for internal observations, but it is not digested.
Notes
Notes:
StructureDefinition
Elements (Simplified)
- DeviceDefinition [0..*]: - The definition of a kind of device or device component
- DeviceDefinition.url [0..1]: uri Canonical identifier for this DeviceDefinition, represented as an absolute URI (globally unique)
- DeviceDefinition.identifier [0..*]: Identifier Additional identifier for the DeviceDefinition
- DeviceDefinition.version [0..1]: string Business version of the DeviceDefinition
- DeviceDefinition.versionAlgorithm[x] [0..1]: string, Coding extensible:version-algorithm How to compare versions
- DeviceDefinition.name [0..1]: string Name for this DeviceDefinition (computer friendly)
- DeviceDefinition.title [0..1]: string Name for this DeviceDefinition (human friendly)
- DeviceDefinition.status [1..1]: code required:publication-status|6.0.0-ballot4 draft | active | retired | unknown
- DeviceDefinition.experimental [0..1]: boolean For testing only - never for real usage
- DeviceDefinition.date [0..1]: dateTime Date last changed
- DeviceDefinition.publisher [0..1]: string Name of the publisher/steward (organization or individual)
- DeviceDefinition.contact [0..*]: ContactDetail Contact details for the publisher
- DeviceDefinition.description [0..1]: markdown Natural language description of the DeviceDefinition
- DeviceDefinition.useContext [0..*]: UsageContext The context that the content is intended to support
- DeviceDefinition.jurisdiction [0..*]: CodeableConcept extensible:jurisdiction Jurisdiction of the authority that maintains the DeviceDefinition (if applicable)
- DeviceDefinition.purpose [0..1]: markdown Why this DeviceDefinition is defined
- DeviceDefinition.copyright [0..1]: markdown Notice about intellectual property ownership, can include restrictions on use
- DeviceDefinition.copyrightLabel [0..1]: string Copyright holder and year(s)
- DeviceDefinition.approvalDate [0..1]: date When DeviceDefinition was approved by publisher
- DeviceDefinition.lastReviewDate [0..1]: date Date on which the asset content was last reviewed by the publisher
- DeviceDefinition.effectivePeriod [0..1]: Period The effective date range for the DeviceDefinition
- DeviceDefinition.partNumber [0..1]: string The part number or catalog number of the device
- DeviceDefinition.manufacturer [0..1]: Reference(Organization) Name of device manufacturer
- DeviceDefinition.modelNumber [0..1]: string The catalog or model number for the device for example as defined by the manufacturer
- DeviceDefinition.udiDeviceIdentifier [0..*]: BackboneElement Unique Device Identifier (UDI) Barcode string
- DeviceDefinition.udiDeviceIdentifier.deviceIdentifier [1..1]: string The identifier that is to be associated with every Device that references this DeviceDefintiion for the issuer and jurisdiction provided in the DeviceDefinition.udiDeviceIdentifier
- DeviceDefinition.udiDeviceIdentifier.issuer [1..1]: uri The organization that assigns the identifier algorithm
- DeviceDefinition.udiDeviceIdentifier.jurisdiction [1..1]: uri The jurisdiction to which the deviceIdentifier applies
- DeviceDefinition.udiDeviceIdentifier.marketDistribution [0..*]: BackboneElement Indicates whether and when the device is available on the market
- DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod [1..1]: Period Begin and end dates for the commercial distribution of the device
- DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction [1..1]: uri National state or territory where the device is commercialized
- DeviceDefinition.udiDeviceIdentifier.deviceIdentifierSystem [0..1]: uri The namespace for the device identifier value
- DeviceDefinition.regulatoryIdentifier [0..*]: BackboneElement Regulatory identifier(s) associated with this device
- DeviceDefinition.regulatoryIdentifier.type [1..1]: code required:devicedefinition-regulatory-identifier-type basic | master | license
- DeviceDefinition.regulatoryIdentifier.identifier [1..1]: string The identifier itself
- DeviceDefinition.regulatoryIdentifier.issuer [1..1]: uri The organization that issued this identifier
- DeviceDefinition.regulatoryIdentifier.jurisdiction [1..1]: uri Relevant jurisdiction governing the identifier
- DeviceDefinition.regulatoryIdentifier.identifierSystem [0..1]: uri The namespace for the device identifier value
- DeviceDefinition.deviceName [0..*]: BackboneElement The name or names of the device as given by the manufacturer
- DeviceDefinition.deviceName.name [1..1]: string A name that is used to refer to the device
- DeviceDefinition.deviceName.type [1..1]: CodeableConcept extensible:device-nametype registered-name | user-friendly-name | patient-reported-name
- DeviceDefinition.classification [0..*]: BackboneElement What kind of device or device system this is
- DeviceDefinition.classification.type [1..1]: CodeableConcept example:device-type A classification or risk class of the device model
- DeviceDefinition.classification.justification [0..*]: RelatedArtifact Further information qualifying this classification of the device model
- DeviceDefinition.conformsTo [0..*]: BackboneElement Identifies the standards, specifications, or formal guidances for the capabilities supported by the device
- DeviceDefinition.conformsTo.category [0..1]: CodeableConcept example:device-specification-category Describes the common type of the standard, specification, or formal guidance
- DeviceDefinition.conformsTo.specification [1..1]: CodeableConcept example:device-specification-type Identifies the standard, specification, or formal guidance that the device adheres to the Device Specification type
- DeviceDefinition.conformsTo.version [0..*]: string The specific form or variant of the standard, specification or formal guidance
- DeviceDefinition.conformsTo.source [0..*]: RelatedArtifact Standard, regulation, certification, or guidance website, document, or other publication, or similar, supporting the conformance
- DeviceDefinition.hasPart [0..*]: BackboneElement A device, part of the current one
- DeviceDefinition.hasPart.definition[x] [1..1]: canonical, CodeableConcept example:device-type Reference to the part
- DeviceDefinition.hasPart.count [0..1]: integer Number of occurrences of the part
- DeviceDefinition.packaging [0..*]: BackboneElement Information about the packaging of the device, i.e. how the device is packaged
- DeviceDefinition.packaging.identifier [0..1]: Identifier Business identifier of the packaged medication
- DeviceDefinition.packaging.type [0..1]: CodeableConcept A code that defines the specific type of packaging
- DeviceDefinition.packaging.count [0..1]: integer The number of items contained in the package (devices or sub-packages)
- DeviceDefinition.packaging.distributor [0..*]: BackboneElement An organization that distributes the packaged device
- DeviceDefinition.packaging.distributor.name [0..1]: string Distributor's human-readable name
- DeviceDefinition.packaging.distributor.organizationReference [0..*]: Reference(Organization) Distributor as an Organization resource
- DeviceDefinition.packaging.udiDeviceIdentifier [0..*]: - Unique Device Identifier (UDI) Barcode string on the packaging
- DeviceDefinition.packaging.packaging [0..*]: - Allows packages within packages
- DeviceDefinition.deviceVersion [0..*]: BackboneElement The version of the device or software
- DeviceDefinition.deviceVersion.type [0..1]: CodeableConcept The type of the device version, e.g. manufacturer, approved, internal
- DeviceDefinition.deviceVersion.component [0..1]: Identifier The hardware or software module of the device to which the version applies
- DeviceDefinition.deviceVersion.value [1..1]: string The version text
- DeviceDefinition.safety [0..*]: CodeableConcept example:device-safety Safety characteristics of the device
- DeviceDefinition.shelfLifeStorage [0..*]: ProductShelfLife Shelf Life and storage information
- DeviceDefinition.outputLanguage [0..*]: code required:all-languages Language code for the human-readable text strings produced by the device (all supported)
- DeviceDefinition.property [0..*]: BackboneElement Inherent, essentially fixed, characteristics of this kind of device, e.g., time properties, size, etc
- DeviceDefinition.property.type [1..1]: CodeableConcept example:device-property-type Code that specifies the property being represented
- DeviceDefinition.property.value[x] [1..1]: Quantity, CodeableConcept, string, boolean, integer, Range, Attachment Value of the property
- DeviceDefinition.link [0..*]: BackboneElement An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device
- DeviceDefinition.link.relation [1..1]: Coding extensible:devicedefinition-relationtype The type indicates the relationship of the related device to the device instance
- DeviceDefinition.link.relatedDevice[x] [1..1]: canonical, CodeableConcept example:device-type A reference to the linked device
- DeviceDefinition.note [0..*]: Annotation Device notes and comments
- DeviceDefinition.material [0..*]: BackboneElement A substance used to create the material(s) of which the device is made
- DeviceDefinition.material.substance [1..1]: CodeableConcept example:substance-code A relevant substance that the device contains, may contain, or is made of
- DeviceDefinition.material.alternate [0..1]: boolean Indicates an alternative material of the device
- DeviceDefinition.material.allergenicIndicator [0..1]: boolean Whether the substance is a known or suspected allergen
- DeviceDefinition.productionIdentifierInUDI [0..*]: CodeableConcept extensible:device-productidentifierinudi lot-number | manufactured-date | serial-number | expiration-date | biological-source | software-version
- DeviceDefinition.guideline [0..1]: BackboneElement Information aimed at providing directions for the usage of this model of device
- DeviceDefinition.guideline.useContext [0..*]: UsageContext The circumstances that form the setting for using the device
- DeviceDefinition.guideline.usageInstruction [0..1]: markdown Detailed written and visual directions for the user on how to use the device
- DeviceDefinition.guideline.relatedArtifact [0..*]: RelatedArtifact A source of information or reference for this guideline
- DeviceDefinition.guideline.indication [0..*]: CodeableConcept A clinical condition for which the device was designed to be used
- DeviceDefinition.guideline.contraindication [0..*]: CodeableConcept A specific situation when a device should not be used because it may cause harm
- DeviceDefinition.guideline.warning [0..*]: CodeableConcept Specific hazard alert information that a user needs to know before using the device
- DeviceDefinition.guideline.intendedUse [0..1]: string A description of the general purpose or medical use of the device or its function
- DeviceDefinition.correctiveAction [0..1]: BackboneElement Tracking of latest field safety corrective action
- DeviceDefinition.correctiveAction.recall [1..1]: boolean Whether the corrective action was a recall
- DeviceDefinition.correctiveAction.scope [0..1]: code required:device-correctiveactionscope model | lot-numbers | serial-numbers
- DeviceDefinition.correctiveAction.period [1..1]: Period Start and end dates of the corrective action
- DeviceDefinition.chargeItem [0..*]: BackboneElement Billing code or reference associated with the device
- DeviceDefinition.chargeItem.chargeItemCode [1..1]: CodeableReference example:service-uscls The code or reference for the charge item
- DeviceDefinition.chargeItem.count [1..1]: Quantity Coefficient applicable to the billing code
- DeviceDefinition.chargeItem.effectivePeriod [0..1]: Period A specific time period in which this charge item applies
- DeviceDefinition.chargeItem.useContext [0..*]: UsageContext The context to which this charge item applies
Mappings
- DeviceDefinition Mappings — 24 mapping entries
Resource Packs
list-DeviceDefinition-packs.xml
<?xml version="1.0" encoding="UTF-8"?>
<List xmlns="http://hl7.org/fhir">
<id value="DeviceDefinition-packs"/>
<status value="current"/>
<mode value="working"/>
</List>
Search Parameters
- identifier — token — The identifier of the component —
DeviceDefinition.identifier | DeviceDefinition.udiDeviceIdentifier - type — token — The device type —
DeviceDefinition.classification.type - conforms-to-category — token — The category of the conformance —
DeviceDefinition.conformsTo.category - specification — token — The specification that the device conforms to —
DeviceDefinition.conformsTo.specification - specification-version — composite — A composite of both specification and version —
DeviceDefinition.conformsTo - device-name — string — A server defined search that may match any of the string fields in DeviceDefinition.name or DeviceDefinition.classification.type - the latter to search for 'generic' devices. —
DeviceDefinition.deviceName.name | DeviceDefinition.classification.type.coding.display | DeviceDefinition.classification.type.text - manufacturer — reference — The manufacturer of the device —
DeviceDefinition.manufacturer - publisher — string — The contact for the publisher of the device definition —
DeviceDefinition.contact.name | DeviceDefinition.publisher - model-number — token — The model of the device —
DeviceDefinition.modelNumber - version — token — The specific version of the device —
DeviceDefinition.deviceVersion.value - version-type — composite — Value and type of version —
DeviceDefinition.deviceVersion - has-part-canonical — reference — The component part device definition —
DeviceDefinition.hasPart.definition.ofType(canonical) - has-part-code — token — The component part device type —
DeviceDefinition.hasPart.definition.ofType(CodeableConcept) - part-number — string — The part number or catalog number of the device. —
DeviceDefinition.partNumber - url — uri — The uri that identifies the code system —
DeviceDefinition.url - experimental — token — Whether the DeviceDefinition is experimental —
DeviceDefinition.experimental
Examples
- devicedefinition-example — devicedefinition-example
- devicedefinition-example-prodspec — devicedefinition-example-prodspec
- devicedefinition-examples-header — devicedefinition-examples-header
- example — devicedefinition-example — General DeviceDefinition example
- example-prodspec — devicedefinition-example-prodspec — General DeviceDefinition example 2
Mapping Exceptions
devicedefinition-fivews-mapping-exceptions.xml
Unmapped Elements
- FiveWs.author — Unknown
- FiveWs.actor — Unknown
- FiveWs.cause — Unknown
- FiveWs.where — Unknown
- FiveWs.context — Unknown
- FiveWs.init — Unknown
- FiveWs.source — Unknown
- FiveWs.who — Unknown
- FiveWs.grade — Unknown
- FiveWs.planned — Unknown
- FiveWs.subject — Unknown