eHealth Infrastructure (v2020.7)
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.
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.
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.
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 Oct 27 14:11:48 UTC 2020 as a draft by ehealth.sundhed.dk.
Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.
| Path | Conformance | ValueSet |
| DeviceUseStatement.language | extensible | Common Languages Max Binding: All Languages |
| DeviceUseStatement.status | required | DeviceUseStatementStatus |
| DeviceUseStatement.indication | required | DeviceUseReason |
| DeviceUseStatement.indication.coding | required | DeviceUseReason |
| DeviceUseStatement.bodySite | example | SNOMED CT Body Structures |
| Id | Path | Details | Requirements |
| dom-2 | DeviceUseStatement | If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty() | |
| dom-1 | DeviceUseStatement | If the resource is contained in another resource, it SHALL NOT contain any narrative : contained.text.empty() | |
| dom-4 | DeviceUseStatement | If 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-3 | DeviceUseStatement | If 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-1 | DeviceUseStatement.extension:context | All FHIR elements must have a @value or children : hasValue() | (children().count() > id.count()) | |
| ext-1 | DeviceUseStatement.extension:context | Must have either extensions or value[x], not both : extension.exists() != value.exists() |
DeviceUseStatement
extension
subject
indication
author[x]
