Current Build
Orders and Observations Work GroupMaturity Level: 0 Trial UseSecurity Category: Patient Compartments: Device, Patient

Detailed Descriptions for the elements in the DeviceUseStatement resource.

DeviceUseStatement
Element IdDeviceUseStatement
Definition

A record of a device being used by a patient where the record is the result of a report from the patient or another clinician.

Cardinality0..*
TypeDomainResource
DeviceUseStatement.identifier
Element IdDeviceUseStatement.identifier
Definition

An external identifier for this statement such as an IRI.

NoteThis is a business identifier, not a resource identifier (see discussion)
Cardinality0..*
TypeIdentifier
Summarytrue
DeviceUseStatement.basedOn
Element IdDeviceUseStatement.basedOn
Definition

A plan, proposal or order that is fulfilled in whole or in part by this DeviceUseStatement.

Cardinality0..*
TypeReference(ServiceRequest)
Requirements

Allows tracing of authorization for the DeviceUseStatement and tracking whether proposals/recommendations were acted upon.

Alternate Namesfulfills
Summarytrue
DeviceUseStatement.status
Element IdDeviceUseStatement.status
Definition

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.

Cardinality1..1
Terminology BindingDeviceUseStatementStatus (Required)
Typecode
Is Modifiertrue (Reason: This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)
Summarytrue
Comments

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.

DeviceUseStatement.subject
Element IdDeviceUseStatement.subject
Definition

The patient who used the device.

Cardinality1..1
TypeReference(Patient | Group)
PatternsReference(Patient,Group): Common patterns = Participant
Summarytrue
DeviceUseStatement.derivedFrom
Element IdDeviceUseStatement.derivedFrom
Definition

Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

Cardinality0..*
TypeReference(ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference)
PatternsReference(ServiceRequest,Procedure,Claim,Observation,QuestionnaireResponse,DocumentReference): No common pattern
Summarytrue
Comments

The most common use cases for deriving a DeviceUseStatement 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 DeviceUseStatement from.

DeviceUseStatement.timing[x]
Element IdDeviceUseStatement.timing[x]
Definition

How often the device was used.

Cardinality0..1
TypeTiming|Period|dateTime
[x] NoteSee Choice of Data Types for further information about how to use [x]
Summarytrue
DeviceUseStatement.recordedOn
Element IdDeviceUseStatement.recordedOn
Definition

The time at which the statement was made/recorded.

Cardinality0..1
TypedateTime
Summarytrue
DeviceUseStatement.source
Element IdDeviceUseStatement.source
Definition

Who reported the device was being used by the patient.

Cardinality0..1
TypeReference(Patient | Practitioner | PractitionerRole | RelatedPerson)
PatternsReference(Patient,Practitioner,PractitionerRole,RelatedPerson): Common patterns = Participant
Summarytrue
DeviceUseStatement.device
Element IdDeviceUseStatement.device
Definition

The details of the device used.

Cardinality1..1
TypeReference(Device)
Summarytrue
DeviceUseStatement.reasonCode
Element IdDeviceUseStatement.reasonCode
Definition

Reason or justification for the use of the device.

Cardinality0..*
TypeCodeableConcept
Summarytrue
DeviceUseStatement.reasonReference
Element IdDeviceUseStatement.reasonReference
Definition

Indicates another resource whose existence justifies this DeviceUseStatement.

Cardinality0..*
TypeReference(Condition | Observation | DiagnosticReport | DocumentReference)
PatternsReference(Condition,Observation,DiagnosticReport,DocumentReference): Common patterns = Event
Summarytrue
DeviceUseStatement.bodySite
Element IdDeviceUseStatement.bodySite
Definition

Indicates the anotomic location on the subject's body where the device was used ( i.e. the target).

Cardinality0..1
Terminology BindingSNOMED CT Body Structures (Example)
TypeCodeableConcept
Requirements

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.

Summarytrue
DeviceUseStatement.note
Element IdDeviceUseStatement.note
Definition

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.

Cardinality0..*
TypeAnnotation