eHealth Infrastructure
3.3.0 - ci-build Denmark flag

eHealth Infrastructure, published by Den telemedicinske infrastruktur (eHealth Infrastructure). This guide is not an authorized publication; it is the continuous build for version 3.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/fut-infrastructure/implementation-guide/ and changes regularly. See the Directory of published versions

Resource Profile: ehealth-deviceusestatement

Official URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement Version: 3.3.0
Active as of 2024-12-20 Computable Name: ehealth-deviceusestatement

Introduction

The DeviceUseStatement resource represents a record of a device being used by a patient in the context of a careplan over a certain period of time.

Scope and Usage

This resource records the use of a healthcare-related device by a patient in the context of a careplan. The resource can be used to note the use of a clinical device such as a spyrometer, blood pressure monitor, and other devices required to fulfil the careplan.

If the same device is used simultaneously for the fulfilment of more than one careplan for the same patient, then more than one active DeviceUseStatement will exist.

A DeviceUseStatement is considered active only when its status field is Active. For logging purposes the whenUsed element is updated to reflect the period in which the DeviceUseStatement is active; but this element alone does not indicate whether the the DeviceUseStatement is Active or not. A DeviceUseStatement which is Active will have a whenUsed.end which is null.

DeviceUseStatements which have been in status Active cannot be deleted.

DeviceUseStatements 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 DeviceUseStatements therefore concerns reading and searching only.

Life cycle

The SSL services manage the lifecycle of DeviceUseStatement resources. When the SSL services receive a message that a device has been delivered to a patient, then the SSL services first creates a Device, and subsequently a DeviceUseStatement with reference to the created Device resource.

When the SSL services are signaled that a Device is no longer being used, then the SSL services will update the corresponding DeviceUseStatement automatically.

It is possible for a Practitioner (as opposed to the SSL services) to also create and maintain DeviceUseStatements; and also to override what was set by the SSL services.

It can be relevant for a Practitioner to create a DeviceUseStatement in the case where a patient uses a privately owned Device instead of an SSL provisioned device.

Usage:

  • This Resource Profile is not used by any profiles in this Implementation Guide

Formal Views of Profile Content

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

This structure is derived from DeviceUseStatement

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..* DeviceUseStatement Record of use of a device
... Slices for extension 1..* Extension Extension
Slice: Unordered, Open by value:url
.... Context 1..1 Reference(ehealth-careplan) {r} The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... subject 1..1 Reference(ehealth-patient) {r} Patient using device
... source 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r} Who made the statement
... note
.... Slices for author[x] 0..1 Reference(Practitioner | Patient | RelatedPerson | Organization), string Individual responsible for the annotation
Slice: Unordered, Open by type:$this
..... author[x]:authorReference 0..1 Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson) Individual responsible for the annotation
..... author[x]:authorString 0..1 string Individual responsible for the annotation

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..* DeviceUseStatement Record of use of a device
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
ele-1: All FHIR elements must have a @value or children
... Slices for extension 1..* Extension Extension
Slice: Unordered, Open by value:url
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... Context 1..1 Reference(ehealth-careplan) {r} The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... subject Σ 1..1 Reference(ehealth-patient) {r} Patient using device
ele-1: All FHIR elements must have a @value or children
... source Σ 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r} Who made the statement
ele-1: All FHIR elements must have a @value or children
... device Σ 1..1 Reference(ehealth-device) Reference to device used
ele-1: All FHIR elements must have a @value or children

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
DeviceUseStatement.statusrequiredDeviceUseStatementStatus
http://hl7.org/fhir/ValueSet/device-statement-status|4.0.1
from the FHIR Standard
NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..* DeviceUseStatement Record of use of a device
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
... contained 0..* Resource Contained, inline Resources
... Slices for extension 1..* Extension Extension
Slice: Unordered, Open by value:url
.... Context 1..1 Reference(ehealth-careplan) {r} The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..* Identifier External identifier for this record
... basedOn Σ 0..* Reference(ServiceRequest) Fulfills plan, proposal or order
... status ?!Σ 1..1 code active | completed | entered-in-error +
Binding: DeviceUseStatementStatus (required): A coded concept indicating the current status of the Device Usage.

... subject Σ 1..1 Reference(ehealth-patient) {r} Patient using device
... derivedFrom Σ 0..* Reference(ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference) Supporting information
... timing[x] Σ 0..1 How often the device was used
.... timingTiming Timing
.... timingPeriod Period
.... timingDateTime dateTime
... recordedOn Σ 0..1 dateTime When statement was recorded
... source Σ 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r} Who made the statement
... device Σ 1..1 Reference(ehealth-device) Reference to device used
... reasonCode Σ 0..* CodeableConcept Why device was used
... reasonReference Σ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media) Why was DeviceUseStatement performed?
... bodySite Σ 0..1 CodeableConcept Target body site
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

... note 0..* Annotation Addition details (comments, instructions)
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... Slices for author[x] Σ 0..1 Individual responsible for the annotation
Slice: Unordered, Closed by type:$this
..... authorReference Reference(Practitioner | Patient | RelatedPerson | Organization)
..... authorString string
..... author[x]:authorReference Σ 0..1 Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson) Individual responsible for the annotation
..... author[x]:authorString Σ 0..1 string Individual responsible for the annotation
.... time Σ 0..1 dateTime When the annotation was made
.... text Σ 1..1 markdown The annotation - text content (as markdown)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
DeviceUseStatement.languagepreferredCommonLanguages
http://hl7.org/fhir/ValueSet/languages
from the FHIR Standard
Additional Bindings Purpose
AllLanguages Max Binding
DeviceUseStatement.statusrequiredDeviceUseStatementStatus
http://hl7.org/fhir/ValueSet/device-statement-status|4.0.1
from the FHIR Standard
DeviceUseStatement.bodySiteexampleSNOMEDCTBodyStructures
http://hl7.org/fhir/ValueSet/body-site
from the FHIR Standard

Differential View

This structure is derived from DeviceUseStatement

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..* DeviceUseStatement Record of use of a device
... Slices for extension 1..* Extension Extension
Slice: Unordered, Open by value:url
.... Context 1..1 Reference(ehealth-careplan) {r} The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... subject 1..1 Reference(ehealth-patient) {r} Patient using device
... source 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r} Who made the statement
... note
.... Slices for author[x] 0..1 Reference(Practitioner | Patient | RelatedPerson | Organization), string Individual responsible for the annotation
Slice: Unordered, Open by type:$this
..... author[x]:authorReference 0..1 Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson) Individual responsible for the annotation
..... author[x]:authorString 0..1 string Individual responsible for the annotation

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..* DeviceUseStatement Record of use of a device
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
ele-1: All FHIR elements must have a @value or children
... Slices for extension 1..* Extension Extension
Slice: Unordered, Open by value:url
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... Context 1..1 Reference(ehealth-careplan) {r} The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... subject Σ 1..1 Reference(ehealth-patient) {r} Patient using device
ele-1: All FHIR elements must have a @value or children
... source Σ 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r} Who made the statement
ele-1: All FHIR elements must have a @value or children
... device Σ 1..1 Reference(ehealth-device) Reference to device used
ele-1: All FHIR elements must have a @value or children

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
DeviceUseStatement.statusrequiredDeviceUseStatementStatus
http://hl7.org/fhir/ValueSet/device-statement-status|4.0.1
from the FHIR Standard

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..* DeviceUseStatement Record of use of a device
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
... contained 0..* Resource Contained, inline Resources
... Slices for extension 1..* Extension Extension
Slice: Unordered, Open by value:url
.... Context 1..1 Reference(ehealth-careplan) {r} The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..* Identifier External identifier for this record
... basedOn Σ 0..* Reference(ServiceRequest) Fulfills plan, proposal or order
... status ?!Σ 1..1 code active | completed | entered-in-error +
Binding: DeviceUseStatementStatus (required): A coded concept indicating the current status of the Device Usage.

... subject Σ 1..1 Reference(ehealth-patient) {r} Patient using device
... derivedFrom Σ 0..* Reference(ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference) Supporting information
... timing[x] Σ 0..1 How often the device was used
.... timingTiming Timing
.... timingPeriod Period
.... timingDateTime dateTime
... recordedOn Σ 0..1 dateTime When statement was recorded
... source Σ 0..1 Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson) {r} Who made the statement
... device Σ 1..1 Reference(ehealth-device) Reference to device used
... reasonCode Σ 0..* CodeableConcept Why device was used
... reasonReference Σ 0..* Reference(Condition | Observation | DiagnosticReport | DocumentReference | Media) Why was DeviceUseStatement performed?
... bodySite Σ 0..1 CodeableConcept Target body site
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

... note 0..* Annotation Addition details (comments, instructions)
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... Slices for author[x] Σ 0..1 Individual responsible for the annotation
Slice: Unordered, Closed by type:$this
..... authorReference Reference(Practitioner | Patient | RelatedPerson | Organization)
..... authorString string
..... author[x]:authorReference Σ 0..1 Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson) Individual responsible for the annotation
..... author[x]:authorString Σ 0..1 string Individual responsible for the annotation
.... time Σ 0..1 dateTime When the annotation was made
.... text Σ 1..1 markdown The annotation - text content (as markdown)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
DeviceUseStatement.languagepreferredCommonLanguages
http://hl7.org/fhir/ValueSet/languages
from the FHIR Standard
Additional Bindings Purpose
AllLanguages Max Binding
DeviceUseStatement.statusrequiredDeviceUseStatementStatus
http://hl7.org/fhir/ValueSet/device-statement-status|4.0.1
from the FHIR Standard
DeviceUseStatement.bodySiteexampleSNOMEDCTBodyStructures
http://hl7.org/fhir/ValueSet/body-site
from the FHIR Standard

 

Other representations of profile: CSV, Excel, Schematron