Device Model & Device Instance
Overview
These "Device" profile defines the master data of the generic device (model number, version of firmware, manufacturer, etc), other instance-level information like Serial Number and Device settings - as properties.
Structure definition - Devices_DeviceModel :
Canonical url - http://roche.com/fhir/iop/StructureDefinition/Devices_DeviceModel
Devices_DeviceModel (Device) | I | Device | There are no (further) constraints on this element Element idDevice Item used in healthcare DefinitionA 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.
| |
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDevice.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDevice.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDevice.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). IETF language tag for a human language
| |
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idDevice.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
|
contained | I | 0..* | Resource | There are no (further) constraints on this element Element idDevice.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
|
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | I | 0..0 | Identifier | There are no (further) constraints on this element Element idDevice.identifier Instance identifier DefinitionUnique instance identifiers assigned to a device by manufacturers other organizations or owners. Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.
|
displayName | 0..0 | string | There are no (further) constraints on this element Element idDevice.displayName The name used to display by default when the device is referenced DefinitionThe name used to display by default when the device is referenced. Based on intent of use by the resource creator, this may reflect one of the names in Device.name, or may be another simple name. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
definition | 0..0 | CodeableReference(DeviceDefinition) | There are no (further) constraints on this element Element idDevice.definition The reference to the definition for the device DefinitionThe reference to the definition for the device. CodeableReference(DeviceDefinition) Constraints
| |
udiCarrier | Σ | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.udiCarrier Unique Device Identifier (UDI) Barcode string DefinitionUnique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. UDI may identify an unique instance of a device, or it may only identify the type of the device. See UDI mappings for a complete mapping of UDI parts to Device.
|
status | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idDevice.status active | inactive | entered-in-error DefinitionThe Device record status. This is not the status of the device like availability. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size The record status of the device.
|
availabilityStatus | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idDevice.availabilityStatus lost | damaged | destroyed | available DefinitionThe availability of the device. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The availability status reason of the device.
| |
biologicalSourceEvent | I | 0..0 | Identifier | There are no (further) constraints on this element Element idDevice.biologicalSourceEvent An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled Alternate namesDistinct Identification Code (DIC) DefinitionAn identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled. Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier.
|
manufacturer | 0..0 | string | There are no (further) constraints on this element Element idDevice.manufacturer Name of device manufacturer DefinitionA name of the manufacturer or entity legally responsible for the device. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
manufactureDate | 0..0 | dateTime | There are no (further) constraints on this element Element idDevice.manufactureDate Date when the device was made DefinitionThe date and time when the device was manufactured. UTC offset is allowed for dates and partial dates
| |
expirationDate | 0..0 | dateTime | There are no (further) constraints on this element Element idDevice.expirationDate Date and time of expiry of this device (if applicable) DefinitionThe date and time beyond which this device is no longer valid or should not be used (if applicable). UTC offset is allowed for dates and partial dates
| |
lotNumber | 0..0 | string | There are no (further) constraints on this element Element idDevice.lotNumber Lot number of manufacture DefinitionLot number assigned by the manufacturer. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
serialNumber | 0..0 | string | There are no (further) constraints on this element Element idDevice.serialNumber Serial number assigned by the manufacturer DefinitionThe serial number assigned by the organization when the device was manufactured. Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier. When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type. Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_.
| |
name | I | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.name The name or names of the device as known to the manufacturer and/or patient DefinitionThis 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.
|
modelNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.modelNumber The manufacturer's model number for the device DefinitionThe manufacturer's model number for the device. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
partNumber | 0..0 | string | There are no (further) constraints on this element Element idDevice.partNumber The part number or catalog number of the device DefinitionThe part number or catalog number of the device. Alphanumeric Maximum 20.
| |
category | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDevice.category Indicates a high-level grouping of the device DefinitionDevices may be associated with one or more categories. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Categories of medical devices.
| |
type | 0..* | CodeableConceptBinding | Element idDevice.type The kind or type of device DefinitionThe kind or type of device. A device instance may have more than one type - in which case those are the types that apply to the specific instance of the device. Multiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor. Codes to identify medical devices.
| |
version | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.version The actual design of the device or software version running on the device DefinitionThe actual design of the device or software version running on the device.
| |
conformsTo | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.conformsTo Identifies the standards, specifications, or formal guidances for the capabilities supported by the device DefinitionIdentifies the standards, specifications, or 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.
| |
property | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.property Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. DefinitionStatic or essentially fixed characteristics or features of the device (e.g., time or timing attributes, resolution, accuracy, intended use or instructions for use, and physical attributes) that are not otherwise captured in more specific attributes. Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific [DeviceMetric] and recorded using [Observation]. Static characteristics of a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition.
| |
mode | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDevice.mode The designated condition for performing a task DefinitionThe designated condition for performing a task with the device. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Operational mode of a device.
| |
cycle | I | 0..0 | Count | There are no (further) constraints on this element Element idDevice.cycle The series of occurrences that repeats during the operation of the device DefinitionThe series of occurrences that repeats during the operation of the device. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
duration | I | 0..0 | Duration | There are no (further) constraints on this element Element idDevice.duration A measurement of time during the device's operation (e.g., days, hours, mins, etc.) DefinitionA measurement of time during the device's operation (e.g., days, hours, mins, etc.). The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
owner | I | 0..0 | Reference(Organization) | There are no (further) constraints on this element Element idDevice.owner Organization responsible for device DefinitionAn organization that is responsible for the provision and ongoing maintenance of the device. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
contact | I | 0..0 | ContactPoint | There are no (further) constraints on this element Element idDevice.contact Details for human/organization for support DefinitionContact details for an organization or a particular human that is responsible for the device. used for troubleshooting etc.
|
location | I | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idDevice.location Where the device is found DefinitionThe place where the device can be found. Device.location can be used to track device location. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
url | 0..0 | uri | There are no (further) constraints on this element Element idDevice.url Network address to contact device DefinitionA network address on which the device may be contacted directly. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.
| |
endpoint | I | 0..0 | Reference(Endpoint) | There are no (further) constraints on this element Element idDevice.endpoint Technical endpoints providing access to electronic services provided by the device DefinitionTechnical endpoints providing access to services provided by the device defined at this resource. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
gateway | 0..0 | CodeableReference(Device) | There are no (further) constraints on this element Element idDevice.gateway Linked device acting as a communication/data collector, translator or controller DefinitionThe linked device acting as a communication controller, data collector, translator, or concentrator for the current device (e.g., mobile phone application that relays a blood pressure device's data). The Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead.
| |
note | 0..0 | Annotation | There are no (further) constraints on this element Element idDevice.note Device notes and comments DefinitionDescriptive information, usage information or implantation information that is not captured in an existing element. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
safety | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDevice.safety Safety Characteristics of Device DefinitionProvides additional safety characteristics about a medical device. For example devices containing latex. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
|
parent | I | 0..0 | Reference(Device) | There are no (further) constraints on this element Element idDevice.parent The higher level or encompassing device that this device is a logical part of DefinitionThe higher level or encompassing device that this device is a logical part of. For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules. These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in.
|
Attribute description :
Attribute | Description | Terminology reference |
---|---|---|
modelNumber | Model number referred to a uniquely identified device. | |
Type | Categorization of a device by its nature. | device-kind |
Structure definition - Devices_DeviceInstance :
Canonical url - http://roche.com/fhir/iop/StructureDefinition/Devices_DeviceInstance
Devices_DeviceInstance (Device) | I | Device | There are no (further) constraints on this element Element idDevice Item used in healthcare DefinitionA 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.
| |
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idDevice.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDevice.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDevice.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDevice.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). IETF language tag for a human language
| |
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idDevice.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
|
contained | I | 0..* | Resource | There are no (further) constraints on this element Element idDevice.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
|
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
deviceSettings | I | 0..* | Extension(Complex) | Element idDevice.extension:deviceSettings Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttp://roche.com/fhir/iop/StructureDefinition/DeviceSettings Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idDevice.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | I | 0..0 | Identifier | There are no (further) constraints on this element Element idDevice.identifier Instance identifier DefinitionUnique instance identifiers assigned to a device by manufacturers other organizations or owners. Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.
|
displayName | 0..0 | string | There are no (further) constraints on this element Element idDevice.displayName The name used to display by default when the device is referenced DefinitionThe name used to display by default when the device is referenced. Based on intent of use by the resource creator, this may reflect one of the names in Device.name, or may be another simple name. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
definition | 0..0 | CodeableReference(DeviceDefinition) | There are no (further) constraints on this element Element idDevice.definition The reference to the definition for the device DefinitionThe reference to the definition for the device. CodeableReference(DeviceDefinition) Constraints
| |
udiCarrier | Σ | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.udiCarrier Unique Device Identifier (UDI) Barcode string DefinitionUnique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold. UDI may identify an unique instance of a device, or it may only identify the type of the device. See UDI mappings for a complete mapping of UDI parts to Device.
|
status | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idDevice.status active | inactive | entered-in-error DefinitionThe Device record status. This is not the status of the device like availability. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size The record status of the device.
|
availabilityStatus | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idDevice.availabilityStatus lost | damaged | destroyed | available DefinitionThe availability of the device. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The availability status reason of the device.
| |
biologicalSourceEvent | I | 0..0 | Identifier | There are no (further) constraints on this element Element idDevice.biologicalSourceEvent An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled Alternate namesDistinct Identification Code (DIC) DefinitionAn identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled. Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier.
|
manufacturer | 0..0 | string | There are no (further) constraints on this element Element idDevice.manufacturer Name of device manufacturer DefinitionA name of the manufacturer or entity legally responsible for the device. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
manufactureDate | 0..0 | dateTime | There are no (further) constraints on this element Element idDevice.manufactureDate Date when the device was made DefinitionThe date and time when the device was manufactured. UTC offset is allowed for dates and partial dates
| |
expirationDate | 0..0 | dateTime | There are no (further) constraints on this element Element idDevice.expirationDate Date and time of expiry of this device (if applicable) DefinitionThe date and time beyond which this device is no longer valid or should not be used (if applicable). UTC offset is allowed for dates and partial dates
| |
lotNumber | 0..0 | string | There are no (further) constraints on this element Element idDevice.lotNumber Lot number of manufacture DefinitionLot number assigned by the manufacturer. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
serialNumber | 0..1 | string | There are no (further) constraints on this element Element idDevice.serialNumber Serial number assigned by the manufacturer DefinitionThe serial number assigned by the organization when the device was manufactured. Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier. When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type. Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_.
| |
name | I | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.name The name or names of the device as known to the manufacturer and/or patient DefinitionThis 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.
|
modelNumber | 0..0 | string | There are no (further) constraints on this element Element idDevice.modelNumber The manufacturer's model number for the device DefinitionThe manufacturer's model number for the device. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
| |
partNumber | 0..0 | string | There are no (further) constraints on this element Element idDevice.partNumber The part number or catalog number of the device DefinitionThe part number or catalog number of the device. Alphanumeric Maximum 20.
| |
category | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDevice.category Indicates a high-level grouping of the device DefinitionDevices may be associated with one or more categories. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Categories of medical devices.
| |
type | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDevice.type The kind or type of device DefinitionThe kind or type of device. A device instance may have more than one type - in which case those are the types that apply to the specific instance of the device. Multiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor. Codes to identify medical devices.
| |
version | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.version The actual design of the device or software version running on the device DefinitionThe actual design of the device or software version running on the device.
| |
conformsTo | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.conformsTo Identifies the standards, specifications, or formal guidances for the capabilities supported by the device DefinitionIdentifies the standards, specifications, or 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.
| |
property | 0..0 | BackboneElement | There are no (further) constraints on this element Element idDevice.property Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. DefinitionStatic or essentially fixed characteristics or features of the device (e.g., time or timing attributes, resolution, accuracy, intended use or instructions for use, and physical attributes) that are not otherwise captured in more specific attributes. Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific [DeviceMetric] and recorded using [Observation]. Static characteristics of a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition.
| |
mode | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDevice.mode The designated condition for performing a task DefinitionThe designated condition for performing a task with the device. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Operational mode of a device.
| |
cycle | I | 0..0 | Count | There are no (further) constraints on this element Element idDevice.cycle The series of occurrences that repeats during the operation of the device DefinitionThe series of occurrences that repeats during the operation of the device. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
duration | I | 0..0 | Duration | There are no (further) constraints on this element Element idDevice.duration A measurement of time during the device's operation (e.g., days, hours, mins, etc.) DefinitionA measurement of time during the device's operation (e.g., days, hours, mins, etc.). The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
owner | I | 0..0 | Reference(Organization) | There are no (further) constraints on this element Element idDevice.owner Organization responsible for device DefinitionAn organization that is responsible for the provision and ongoing maintenance of the device. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
contact | I | 0..0 | ContactPoint | There are no (further) constraints on this element Element idDevice.contact Details for human/organization for support DefinitionContact details for an organization or a particular human that is responsible for the device. used for troubleshooting etc.
|
location | I | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idDevice.location Where the device is found DefinitionThe place where the device can be found. Device.location can be used to track device location. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
url | 0..0 | uri | There are no (further) constraints on this element Element idDevice.url Network address to contact device DefinitionA network address on which the device may be contacted directly. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.
| |
endpoint | I | 0..0 | Reference(Endpoint) | There are no (further) constraints on this element Element idDevice.endpoint Technical endpoints providing access to electronic services provided by the device DefinitionTechnical endpoints providing access to services provided by the device defined at this resource. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
gateway | 0..0 | CodeableReference(Device) | There are no (further) constraints on this element Element idDevice.gateway Linked device acting as a communication/data collector, translator or controller DefinitionThe linked device acting as a communication controller, data collector, translator, or concentrator for the current device (e.g., mobile phone application that relays a blood pressure device's data). The Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead.
| |
note | 0..0 | Annotation | There are no (further) constraints on this element Element idDevice.note Device notes and comments DefinitionDescriptive information, usage information or implantation information that is not captured in an existing element. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
safety | Σ | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idDevice.safety Safety Characteristics of Device DefinitionProvides additional safety characteristics about a medical device. For example devices containing latex. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
|
parent | I | 0..1 | Reference(Device) | There are no (further) constraints on this element Element idDevice.parent The higher level or encompassing device that this device is a logical part of DefinitionThe higher level or encompassing device that this device is a logical part of. For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules. These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in.
|
Attribute description :
Attribute | Description | Terminology reference |
---|---|---|
serial number | Unique Device Business Identifier. | |
Parent | Hierarchical relationship to other Device that controls this instance. | |
extension : settings | Properties defined as settings for the device's functioning. | device-settings-codes |
Data Flow for Device(s) profiles :
Could not find subject. Project was not found for Devices-diagram.
Data Flow for write action :
Could not find subject. Project was not found for devices-dataflow.
1. 'Devices_DeviceModel' needs to be send as first resource (if not available prior)
2. 'Devices_DeviceInstance' should be send next with reference to parent resource 'Devices_DeviceModel' (if not available prior)