Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R3 R2

5.11 Resource DeviceComponent - Content

Health Care Devices Work GroupMaturity Level: 1Compartments: Device

Describes the characteristics, operational status and capabilities of a medical-related component of a medical device.

5.11.1 Scope and Usage

The DeviceComponent resource is used to describe the characteristics, operational status and capabilities of a medical-related component of a medical device. It can be a physical component that is integrated inside the device, a removable physical component, or a non-physical component that allows physiological measurement data and its derived data to be grouped in a hierarchical information organization.

Note:

For the initial scope, this DeviceComponent resource is only applicable to describe a single node in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard and that does not represent a metric. Examples for such a node are MDS, VMD, or Channel.

5.11.2 Boundaries and Relationships

The DeviceComponent allows us to change the configuration of the device without having to change the device resource instance. The life-cycle of the configuration may be completely different than the one of the device itself.

There are several related resources

5.11.3 Background and Context

5.11.3.1 Structure of a DeviceComponent Resource

A Context Scanner object of a medical device that implements or derives from ISO/IEEE 11073 standard is responsible for observing device configuration changes. After instantiation, the Context Scanner object is responsible for announcing the object instances in the device's MDIB, a hierarchical containment (MDS->VMD->Channel->Metric). The DeviceComponent resource can be used to describe the characteristics, operational status and capabilities of a medical-related component of a medical device. It can be a physical component that is integrated inside the device, a removable physical component, or a non-physical component that allows physiological measurement data and its derived data to be grouped in a hierarchical information organization. Devices are conceptualized using the following main structure:

  1. MedicalDeviceSystem - An actual device that external systems communicate with. In 11073, this is known as a MDS.
  2. VirtualMedicalDevice - A medical-related subsystem of a medical device. It can either be a physical hardware piece or a pure software plugin component of a medical device. In 11073, this is known as a VMD.
  3. Channel - A non-physical component that allows physiological measurement data and its derived data to be grouped in a hierarchical information organization.

Very simple devices may have only a single virtual device with a single channel and one metric, while complex devices may have multiple items at every level.

This resource is referenced by devicemetric

5.11.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceComponent ΣDomainResourceAn instance of a medical-related component of a medical device
... type Σ1..1CodeableConceptWhat kind of component it is
ComponentType (Preferred)
... identifier Σ1..1IdentifierInstance id assigned by the software stack
... lastSystemChange Σ1..1instantRecent system change timestamp
... source Σ0..1Reference(Device)A source device of this component
... parent Σ0..1Reference(DeviceComponent)Parent resource link
... operationalStatus Σ0..*CodeableConceptComponent operational status
... parameterGroup Σ0..1CodeableConceptCurrent supported parameter group
... measurementPrinciple Σ0..1codeother | chemical | electrical | impedance | nuclear | optical | thermal | biological | mechanical | acoustical | manual+
Measmnt-Principle (Required)
... productionSpecification Σ0..*BackboneElementProduction specification of the component
.... specType Σ0..1CodeableConceptSpecification type
.... componentId Σ0..1IdentifierInternal component unique identification
.... productionSpec Σ0..1stringA printable string defining the component
... languageCode Σ0..1CodeableConceptLanguage code for the human-readable text strings produced by the device
Language (Required)

doco Documentation for this format

UML Diagram

DeviceComponent (DomainResource)Describes the specific component type as defined in the object-oriented or metric nomenclature partitiontype : CodeableConcept [1..1] « Describes the type of the component. (Strength=Preferred)ComponentType? »Describes the local assigned unique identification by the software. For example: handle IDidentifier : Identifier [1..1]Describes the timestamp for the most recent system change which includes device configuration or setting changelastSystemChange : instant [1..1]Describes the link to the source Device that contains administrative device information such as manufacture, serial number, etcsource : Reference [0..1] « Device »Describes the link to the parent resource. For example: Channel is linked to its VMD parentparent : Reference [0..1] « DeviceComponent »Indicates current operational status of the device. For example: On, Off, Standby, etcoperationalStatus : CodeableConcept [0..*]Describes the parameter group supported by the current device component that is based on some nomenclature, e.g. cardiovascularparameterGroup : CodeableConcept [0..1]Describes the physical principle of the measurement. For example: thermal, chemical, acoustical, etcmeasurementPrinciple : code [0..1] « Different measurement principle supported by the device. (Strength=Required)Measmnt-Principle! »Describes the language code for the human-readable text string produced by the device. This language code will follow the IETF language tag. Example: en-USlanguageCode : CodeableConcept [0..1] « A human language. (Strength=Required)Language! »ProductionSpecificationDescribes the specification type, such as, serial number, part number, hardware revision, software revision, etcspecType : CodeableConcept [0..1]Describes the internal component unique identification. This is a provision for manufacture specific standard components using a private OID. 11073-10101 has a partition for private OID semantic that the manufacture can make use ofcomponentId : Identifier [0..1]Describes the printable string defining the componentproductionSpec : string [0..1]Describes the production specification such as component revision, serial number, etcproductionSpecification[0..*]

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceComponent ΣDomainResourceAn instance of a medical-related component of a medical device
... type Σ1..1CodeableConceptWhat kind of component it is
ComponentType (Preferred)
... identifier Σ1..1IdentifierInstance id assigned by the software stack
... lastSystemChange Σ1..1instantRecent system change timestamp
... source Σ0..1Reference(Device)A source device of this component
... parent Σ0..1Reference(DeviceComponent)Parent resource link
... operationalStatus Σ0..*CodeableConceptComponent operational status
... parameterGroup Σ0..1CodeableConceptCurrent supported parameter group
... measurementPrinciple Σ0..1codeother | chemical | electrical | impedance | nuclear | optical | thermal | biological | mechanical | acoustical | manual+
Measmnt-Principle (Required)
... productionSpecification Σ0..*BackboneElementProduction specification of the component
.... specType Σ0..1CodeableConceptSpecification type
.... componentId Σ0..1IdentifierInternal component unique identification
.... productionSpec Σ0..1stringA printable string defining the component
... languageCode Σ0..1CodeableConceptLanguage code for the human-readable text strings produced by the device
Language (Required)

doco Documentation for this format

UML Diagram

DeviceComponent (DomainResource)Describes the specific component type as defined in the object-oriented or metric nomenclature partitiontype : CodeableConcept [1..1] « Describes the type of the component. (Strength=Preferred)ComponentType? »Describes the local assigned unique identification by the software. For example: handle IDidentifier : Identifier [1..1]Describes the timestamp for the most recent system change which includes device configuration or setting changelastSystemChange : instant [1..1]Describes the link to the source Device that contains administrative device information such as manufacture, serial number, etcsource : Reference [0..1] « Device »Describes the link to the parent resource. For example: Channel is linked to its VMD parentparent : Reference [0..1] « DeviceComponent »Indicates current operational status of the device. For example: On, Off, Standby, etcoperationalStatus : CodeableConcept [0..*]Describes the parameter group supported by the current device component that is based on some nomenclature, e.g. cardiovascularparameterGroup : CodeableConcept [0..1]Describes the physical principle of the measurement. For example: thermal, chemical, acoustical, etcmeasurementPrinciple : code [0..1] « Different measurement principle supported by the device. (Strength=Required)Measmnt-Principle! »Describes the language code for the human-readable text string produced by the device. This language code will follow the IETF language tag. Example: en-USlanguageCode : CodeableConcept [0..1] « A human language. (Strength=Required)Language! »ProductionSpecificationDescribes the specification type, such as, serial number, part number, hardware revision, software revision, etcspecType : CodeableConcept [0..1]Describes the internal component unique identification. This is a provision for manufacture specific standard components using a private OID. 11073-10101 has a partition for private OID semantic that the manufacture can make use ofcomponentId : Identifier [0..1]Describes the printable string defining the componentproductionSpec : string [0..1]Describes the production specification such as component revision, serial number, etcproductionSpecification[0..*]

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

5.11.4.1 Terminology Bindings

PathDefinitionTypeReference
DeviceComponent.type Describes the type of the component.PreferredIEEE 11073-10101
DeviceComponent.operationalStatus Codes representing the current status of the device - on, off, suspended, etc.UnknownNo details provided yet
DeviceComponent.parameterGroup Codes identifying groupings of parameters; e.g. Cardiovascular.UnknownNo details provided yet
DeviceComponent.measurementPrinciple Different measurement principle supported by the device.RequiredMeasmnt-Principle
DeviceComponent.productionSpecification.specType Codes for device specification types such as serial number, part number, hardware revision, software revision, etc.UnknownNo details provided yet
DeviceComponent.languageCode A human language.RequiredIETF language tag

5.11.5 Notes:

  • The correct codes for the medical device system (MDS), virtual medical device (VMD), and Channel will be specified in the profiles for specific types of device component. Generally, these codes are registered in the RTM Management service , but this is not required. See Terminology Systems for the correct representation of these codes in a Coding data type.

5.11.6 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
parentreferenceThe parent DeviceComponent resourceDeviceComponent.parent
(DeviceComponent)
sourcereferenceThe device sourceDeviceComponent.source
(Device)
typetokenThe device component typeDeviceComponent.type