eHealth Infrastructure (v2020.2)

StructureDefinition: 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 life cycle of DeviceUseStatement resources is normally managed by the SSL subsystem, when an SSL supplier or a practitioner signals that a device has been delivered to a patient. At this time the Device Service is searched for an existing instance of this Device resource and a DeviceUseStatement referencing this Device is created.

When the SSL subsystem is signaled that a Device is no longer being used, it will update the corresponding DeviceUseStatement automatically.

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

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.

Formal Views of Profile Content

The official URL for this profile is: 

http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement

This profile builds on DeviceUseStatement.

This profile was published on Tue Mar 31 08:26:16 UTC 2020 as a draft by ehealth.sundhed.dk.

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

This structure is derived from DeviceUseStatement

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..*DeviceUseStatementA record of a device being used by a patient.
... extension 0..*ExtensionSlice: Unordered, Open by value:url
... ehealth-deviceusestatement-context 1..1Reference()The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... subject 1..1Reference(eHealth Patient) {r}
... source 0..1Reference(eHealth Patient | eHealth Practitioner | eHealth RelatedPerson) {r}
... device 1..1Reference(eHealth Device) {r}
... indication 0..*CodeableConceptBinding: Device Use Reason (required)
.... coding 0..*CodingBinding: Device Use Reason (required)
... note 0..*AnnotationAdditional details (comments, instructions)
.... author[x] 0..1
..... authorReferenceReference(eHealth Practitioner | eHealth Patient | eHealth RelatedPerson)
..... authorStringstring

doco Documentation for this format

This structure is derived from DeviceUseStatement

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement I0..*DeviceUseStatementA record of a device being used by a patient.
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
Max Binding: All Languages
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... ehealth-deviceusestatement-context I1..1Reference()The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierExternal identifier for this record
... status ?!Σ1..1codeactive | completed | entered-in-error +
Binding: DeviceUseStatementStatus (required)
... subject 1..1Reference(eHealth Patient) {r}Patient using device
... whenUsed 0..1PeriodPeriod device was used
... timing[x] 0..1How often the device was used
.... timingTimingTiming
.... timingPeriodPeriod
.... timingDateTimedateTime
... recordedOn 0..1dateTimeWhen statement was recorded
... source 0..1Reference(eHealth Patient | eHealth Practitioner | eHealth RelatedPerson) {r}Who made the statement
... device 1..1Reference(eHealth Device) {r}Reference to device used
... indication 0..*CodeableConceptWhy device was used
Binding: Device Use Reason (required)
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ0..*CodingCode defined by a terminology system
Binding: Device Use Reason (required)
.... text Σ0..1stringPlain text representation of the concept
... bodySite 0..1CodeableConceptTarget body site
Binding: SNOMED CT Body Structures (example)
... note 0..*AnnotationAdditional details (comments, instructions)
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
Slice: Unordered, Open by value:url
.... author[x] Σ0..1Individual responsible for the annotation
..... authorReferenceReference(eHealth Practitioner | eHealth Patient | eHealth RelatedPerson)
..... authorStringstring
.... time Σ0..1dateTimeWhen the annotation was made
.... text 1..1stringThe annotation - text content

doco Documentation for this format

Differential View

This structure is derived from DeviceUseStatement

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement 0..*DeviceUseStatementA record of a device being used by a patient.
... extension 0..*ExtensionSlice: Unordered, Open by value:url
... ehealth-deviceusestatement-context 1..1Reference()The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... subject 1..1Reference(eHealth Patient) {r}
... source 0..1Reference(eHealth Patient | eHealth Practitioner | eHealth RelatedPerson) {r}
... device 1..1Reference(eHealth Device) {r}
... indication 0..*CodeableConceptBinding: Device Use Reason (required)
.... coding 0..*CodingBinding: Device Use Reason (required)
... note 0..*AnnotationAdditional details (comments, instructions)
.... author[x] 0..1
..... authorReferenceReference(eHealth Practitioner | eHealth Patient | eHealth RelatedPerson)
..... authorStringstring

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseStatement I0..*DeviceUseStatementA record of a device being used by a patient.
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Common Languages (extensible)
Max Binding: All Languages
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... ehealth-deviceusestatement-context I1..1Reference()The careplan context for the device use
URL: http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-deviceusestatement-context
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierExternal identifier for this record
... status ?!Σ1..1codeactive | completed | entered-in-error +
Binding: DeviceUseStatementStatus (required)
... subject 1..1Reference(eHealth Patient) {r}Patient using device
... whenUsed 0..1PeriodPeriod device was used
... timing[x] 0..1How often the device was used
.... timingTimingTiming
.... timingPeriodPeriod
.... timingDateTimedateTime
... recordedOn 0..1dateTimeWhen statement was recorded
... source 0..1Reference(eHealth Patient | eHealth Practitioner | eHealth RelatedPerson) {r}Who made the statement
... device 1..1Reference(eHealth Device) {r}Reference to device used
... indication 0..*CodeableConceptWhy device was used
Binding: Device Use Reason (required)
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ0..*CodingCode defined by a terminology system
Binding: Device Use Reason (required)
.... text Σ0..1stringPlain text representation of the concept
... bodySite 0..1CodeableConceptTarget body site
Binding: SNOMED CT Body Structures (example)
... note 0..*AnnotationAdditional details (comments, instructions)
.... id 0..1stringxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
Slice: Unordered, Open by value:url
.... author[x] Σ0..1Individual responsible for the annotation
..... authorReferenceReference(eHealth Practitioner | eHealth Patient | eHealth RelatedPerson)
..... authorStringstring
.... time Σ0..1dateTimeWhen the annotation was made
.... text 1..1stringThe annotation - text content

doco Documentation for this format

 

Terminology Bindings

PathConformanceValueSet
DeviceUseStatement.languageextensibleCommon Languages
Max Binding: All Languages
DeviceUseStatement.statusrequiredDeviceUseStatementStatus
DeviceUseStatement.indicationrequiredDeviceUseReason
DeviceUseStatement.indication.codingrequiredDeviceUseReason
DeviceUseStatement.bodySiteexampleSNOMED CT Body Structures

Constraints

IdPathDetailsRequirements
dom-2DeviceUseStatementIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-1DeviceUseStatementIf the resource is contained in another resource, it SHALL NOT contain any narrative
: contained.text.empty()
dom-4DeviceUseStatementIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-3DeviceUseStatementIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
: contained.where(('#'+id in %resource.descendants().reference).not()).empty()
ele-1DeviceUseStatement.extension:contextAll FHIR elements must have a @value or children
: hasValue() | (children().count() > id.count())
ext-1DeviceUseStatement.extension:contextMust have either extensions or value[x], not both
: extension.exists() != value.exists()
.