eHealth Infrastructure
3.0.0 - release

eHealth Infrastructure - Local Development build (v3.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: ehealth-device

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-device Version: 3.0.0
Active as of 2024-05-16 Computable Name: ehealth-device

Introduction

This resource identifies a specific instance 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. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc.

Because the Device resource represents a specific instance of a Device, it must have at least one identifier, such as a serial no., which together with the manufacturer and model uniquely identifies the device instance.

Each Device can be related to a number of suppliers with different roles; such as e.g. the provisioner, and suppliers of user training, maintenance, or decommissioning of the device.

Scope and Usage

In eHealth Devices are registered as FHIR resources when they are actively used in a current CarePlan for a Patient. The relation between a CarePlan and a Device is represented by a DeviceUseStatement resource.

The main purpose of registering a specific Device to a Patient through a CarePlan is purely clinical; not logistical. If for example at some point it is determined that a specific device has yielded erroneous or biased measurements, it may be important to track which patients have used this device.

Device resources are created and updated automatically based on actions and information provided in the Service, Support & Logistics (SSL) domain of the eHealth Infrastructure. The use of Device therefore concerns reading and searching only.

Life cycle

The SSL services manage the lifecycle of Device resources. When the SSL services receive a message that a device has been delivered to a patient, then the SSL services create a Device resource and relate it to the Patient’s CarePlan through a DeviceUseStatement.

Privately owned devices

Bring your own device (BYOD), where the patient provides the device him or herself, is indicated with the extension Device.privatelyOwned being set to true. In all other cases, it is set to null or false.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Device

NameFlagsCard.TypeDescription & Constraintsdoco
.. Device Device
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... privatelyOwned 0..1booleanTrue if this device is owned or provided by the patient.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-device-privatelyOwned
... suppliers 0..*(Complex)Different types of suppliers for a device.
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-device-suppliers
... type 0..1CodeableConceptThe kind or type of device
Binding: Device Types (required)
... patient 0..0
... owner 0..1Reference(ehealth-organization) {r}Organization responsible for device
... note
.... Slices for author[x] 0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotation
Slice: Unordered, Open by type:$this
..... author[x]:authorReference 0..1Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson)Individual responsible for the annotation
..... author[x]:authorString 0..1stringIndividual responsible for the annotation

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Device.typerequiredDeviceTypes
http://ehealth.sundhed.dk/vs/device-types
from this IG

 

Other representations of profile: CSV, Excel, Schematron