This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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 | Trial Use | Security Category: Patient | 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. |
Cardinality | 0..* |
Type | DomainResource |
DeviceUseStatement.identifier | |
Element Id | DeviceUseStatement.identifier |
Definition | An external identifier for this statement such as an IRI. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Cardinality | 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. |
Cardinality | 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. |
Cardinality | 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. |
Cardinality | 1..1 |
Type | Reference(Patient | Group) |
Patterns | Reference(Patient,Group): Common patterns = Participant |
Summary | true |
DeviceUseStatement.derivedFrom | |
Element Id | DeviceUseStatement.derivedFrom |
Definition | Allows linking the DeviceUseStatement to the underlying Request, or to other information that supports or is used to derive the DeviceUseStatement. |
Cardinality | 0..* |
Type | Reference(ServiceRequest | Procedure | Claim | Observation | QuestionnaireResponse | DocumentReference) |
Patterns | Reference(ServiceRequest,Procedure,Claim,Observation,QuestionnaireResponse,DocumentReference): No common pattern |
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. |
Cardinality | 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. |
Cardinality | 0..1 |
Type | dateTime |
Summary | true |
DeviceUseStatement.source | |
Element Id | DeviceUseStatement.source |
Definition | Who reported the device was being used by the patient. |
Cardinality | 0..1 |
Type | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson) |
Patterns | Reference(Patient,Practitioner,PractitionerRole,RelatedPerson): Common patterns = Participant |
Summary | true |
DeviceUseStatement.device | |
Element Id | DeviceUseStatement.device |
Definition | The details of the device used. |
Cardinality | 1..1 |
Type | Reference(Device) |
Summary | true |
DeviceUseStatement.reason | |
Element Id | DeviceUseStatement.reason |
Definition | Reason or justification for the use of the device. A coded concept, or another resource whose existence justifies this DeviceUseStatement. |
Cardinality | 0..* |
Type | CodeableReference(Condition | Observation | DiagnosticReport | DocumentReference) |
Patterns | CodeableReference(Condition,Observation,DiagnosticReport,DocumentReference): Common patterns = Event |
Summary | true |
DeviceUseStatement.bodySite | |
Element Id | DeviceUseStatement.bodySite |
Definition | Indicates the anotomic location on the subject's body where the device was used ( i.e. the target). |
Cardinality | 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/bodySite. |
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. |
Cardinality | 0..* |
Type | Annotation |