FHIR Release 3 (STU) R4 Ballot #1 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.0.2: STU 3). (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3 R2

Orders and Observations Work Group Maturity Level : 0   Draft Compartments : Device , Patient

Detailed Descriptions for the elements in the DeviceUseStatement resource.

DeviceUseStatement
Element Id DeviceUseStatement
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.

Control 1..1
DeviceUseStatement.identifier
Element Id DeviceUseStatement.identifier
Definition

An external identifier for this statement such as an IRI.

Note This is a business identifer, not a resource identifier (see discussion )
Control 0..*
Type Identifier
Summary true
DeviceUseStatement.basedOn
Element Id DeviceUseStatement.basedOn
Definition

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

Control 0..*
Type Reference ( ServiceRequest )
Requirements

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

Alternate Names fulfills
Summary true
DeviceUseStatement.status
Element Id DeviceUseStatement.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.

Control 1..1
Terminology Binding DeviceUseStatementStatus ( Required )
Type code
Is Modifier true (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)
Summary true
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 Id DeviceUseStatement.subject
Definition

The patient who used the device.

Control 1..1
Type Reference ( Patient | Group )
Summary true
DeviceUseStatement.whenUsed DeviceUseStatement.derivedFrom
Element Id DeviceUseStatement.derivedFrom
Definition

The time period over which Allows linking the device was used. DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement.

Control 0..1 0..*
Type Period Reference ( ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference )
Summary true
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 Id DeviceUseStatement.timing[x]
Definition

How often the device was used.

Control 0..1
Type Timing | Period | dateTime
[x] Note See Choice of Data Types for further information about how to use [x]
Summary true
DeviceUseStatement.recordedOn
Element Id DeviceUseStatement.recordedOn
Definition

The time at which the statement was made/recorded.

Control 0..1
Type dateTime
Summary true
DeviceUseStatement.source
Element Id DeviceUseStatement.source
Definition

Who reported the device was being used by the patient.

Control 0..1
Type Reference ( Patient | Practitioner | RelatedPerson )
Summary true
DeviceUseStatement.device
Element Id DeviceUseStatement.device
Definition

The details of the device used.

Control 1..1
Type Reference ( Device )
Summary true
DeviceUseStatement.indication DeviceUseStatement.reasonCode
Element Id DeviceUseStatement.reasonCode
Definition

Reason or justification for the use of the device.

Control 0..*
Type CodeableConcept
Summary true
DeviceUseStatement.reasonReference
Element Id DeviceUseStatement.reasonReference
Definition

Indicates another resource whose existence justifies this DeviceUseStatement.

Control 0..*
Type Reference ( Condition | Observation | DiagnosticReport | DocumentReference | Media )
Summary true
DeviceUseStatement.bodySite
Element Id DeviceUseStatement.bodySite
Definition

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

Control 0..1
Terminology Binding SNOMED CT Body Structures ( Example )
Type CodeableConcept
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/body-site-instance http://hl7.org/fhir/StructureDefinition/body-structure .

Summary true
DeviceUseStatement.note
Element Id DeviceUseStatement.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.

Control 0..*
Type Annotation