This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions
Detailed Descriptions for the elements in the DeviceUsage resource.
A record of a device being used by a patient where the record is the result of a report from the patient or a clinician.
An external identifier for this statement such as an IRI.
A plan, proposal or order that is fulfilled in whole or in part by this DeviceUsage.
Allows tracing of authorization for the DeviceUsage and tracking whether proposals/recommendations were acted upon.
A code representing the patient or other source's judgment about the state of the device used that this statement is about. Generally this will be active or completed.
DeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).
This element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.
This attribute indicates a category for the statement - The device statement may be made in an inpatient or outpatient settting (inpatient | outpatient | community | patientspecified).
The patient who used the device.
Allows linking the DeviceUsage to the underlying Request, or to other information that supports or is used to derive the DeviceUsage.
The most common use cases for deriving a DeviceUsage comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUsage from.
The encounter or episode of care that establishes the context for this device use statement.
How often the device was used.
The time at which the statement was recorded by informationSource.
The status of the device usage, for example always, sometimes, never. This is not the same as the status of the statement.
The reason for asserting the usage status - for example forgot, lost, stolen, broken.
This indicates how or if the device is being used.
Type of adherence.
Reason for adherence type.
Who reported the device was being used by the patient.
Code or Reference to device used.
Reason or justification for the use of the device. A coded concept, or another resource whose existence justifies this DeviceUsage.
When the status is not done, the reason code indicates why it was not done.
Indicates the anotomic location on the subject's body where the device was used ( i.e. the target).
Knowing where the device is targeted is important for tracking if multiple sites are possible. If more information than just a code is required, use the extension http://hl7.org/fhir/StructureDefinition/bodySite.
Details about the device statement that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.