Release 5 Preview #1
WorkflowThis 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 |
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.
These resources have not yet undergone proper review by PC, CQI, CDS, and OO. At this time, they are to be considered only as draft resource proposals for potential submission.
This resource is an event resource from a FHIR workflow perspective - see Workflow. It is the intent of the Orders and Observation Workgroup to align this resource with the workflow pattern for event resources.
This resource records the use of a healthcare-related device by a patient. The record is the result of a report of use by the patient, another provider or a related person. The resource can be used to note the use of an assistive device such as a wheelchair or hearing aid, a contraceptive such an intra-uterine device, or other implanted devices such as a pacemaker.
This resource is different from DeviceRequest which records a request to use the device. This also is distinct from the Procedure resource which may describe the implantation or explantation of a device.
No resources refer to this resource directly.
This resource implements the Event pattern.
Structure
UML Diagram (Legend)
XML Template
<DeviceUseStatement xmlns="http://hl7.org/fhir"><!-- from Resource: id, meta, implicitRules, and language --> <!-- from DomainResource: text, contained, extension, and modifierExtension --> <identifier><!-- 0..* Identifier External identifier for this record --></identifier> <basedOn><!-- 0..* Reference(ServiceRequest) Fulfills plan, proposal or order --></basedOn> <status value="[code]"/><!-- 1..1 active | completed | entered-in-error + --> <subject><!-- 1..1 Reference(Group|Patient) Patient using device --></subject> <derivedFrom><!-- 0..* Reference(Claim|DocumentReference|Observation|Procedure| QuestionnaireResponse|ServiceRequest) Supporting information --></derivedFrom> <timing[x]><!-- 0..1 Timing|Period|dateTime How often the device was used --></timing[x]> <recordedOn value="[dateTime]"/><!-- 0..1 When statement was recorded --> <source><!-- 0..1 Reference(Patient|Practitioner|PractitionerRole|RelatedPerson) Who made the statement --></source> <device><!-- 1..1 Reference(Device) Reference to device used --></device> <reason><!-- 0..* CodeableReference(Condition|DiagnosticReport|DocumentReference| Observation) Why device was used --></reason> <bodySite><!-- 0..1 CodeableConcept Target body site --></bodySite> <note><!-- 0..* Annotation Addition details (comments, instructions) --></note> </DeviceUseStatement>
JSON Template
{
"resourceType" : "DeviceUseStatement",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // External identifier for this record
"basedOn" : [{ Reference(ServiceRequest) }], // Fulfills plan, proposal or order
"status" : "<code>", // R! active | completed | entered-in-error +
"subject" : { Reference(Group|Patient) }, // R! Patient using device
"derivedFrom" : [{ Reference(Claim|DocumentReference|Observation|Procedure|
QuestionnaireResponse|ServiceRequest) }], // Supporting information
// timing[x]: How often the device was used. One of these 3:
"timingTiming" : { Timing },
"timingPeriod" : { Period },
"timingDateTime" : "<dateTime>",
"recordedOn" : "<dateTime>", // When statement was recorded
"source" : { Reference(Patient|Practitioner|PractitionerRole|RelatedPerson) }, // Who made the statement
"device" : { Reference(Device) }, // R! Reference to device used
"reason" : [{ CodeableReference(Condition|DiagnosticReport|DocumentReference|
Observation) }], // Why device was used
"bodySite" : { CodeableConcept }, // Target body site
"note" : [{ Annotation }] // Addition details (comments, instructions)
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .
Changes since R3
| DeviceUseStatement | |
| DeviceUseStatement.status |
|
| DeviceUseStatement.reason |
|
| DeviceUseStatement.reasonCode |
|
| DeviceUseStatement.reasonReference |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and all r3 resources are valid.)
Structure
XML Template
<DeviceUseStatement xmlns="http://hl7.org/fhir">
JSON Template
{
"resourceType" : "DeviceUseStatement",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // External identifier for this record
"basedOn" : [{ Reference(ServiceRequest) }], // Fulfills plan, proposal or order
"status" : "<code>", // R! active | completed | entered-in-error +
"subject" : { Reference(Group|Patient) }, // R! Patient using device
"derivedFrom" : [{ Reference(Claim|DocumentReference|Observation|Procedure|
QuestionnaireResponse|ServiceRequest) }], // Supporting information
// timing[x]: How often the device was used. One of these 3:
"timingTiming" : { Timing },
"timingPeriod" : { Period },
"timingDateTime" : "<dateTime>",
"recordedOn" : "<dateTime>", // When statement was recorded
"source" : { Reference(Patient|Practitioner|PractitionerRole|RelatedPerson) }, // Who made the statement
"device" : { Reference(Device) }, // R! Reference to device used
"reason" : [{ CodeableReference(Condition|DiagnosticReport|DocumentReference|
Observation) }], // Why device was used
"bodySite" : { CodeableConcept }, // Target body site
"note" : [{ Annotation }] // Addition details (comments, instructions)
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .
Changes since Release 3
| DeviceUseStatement | |
| DeviceUseStatement.status |
|
| DeviceUseStatement.reason |
|
| DeviceUseStatement.reasonCode |
|
| DeviceUseStatement.reasonReference |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and all r3 resources are valid.)
See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis a
| Path | Definition | Type | Reference |
|---|---|---|---|
| DeviceUseStatement.status | A coded concept indicating the current status of the Device Usage. | Required | DeviceUseStatementStatus |
| DeviceUseStatement.bodySite | Codes describing anatomical locations. May include laterality. | Example | SNOMEDCTBodyStructures |
Notes to reviewers:
At this time, the code bindings are placeholders to be fleshed out upon further review by the community.
Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.
| Name | Type | Description | Expression | In Common |
| device | reference | Search by device | DeviceUseStatement.device (Device) | |
| identifier | token | Search by identifier | DeviceUseStatement.identifier | |
| patient | reference | Search by subject - a patient | DeviceUseStatement.subject (Group, Patient) | 33 Resources |
| subject | reference | Search by subject | DeviceUseStatement.subject (Group, Patient) |
FHIR ®© HL7.org 2011+. FHIR CI Build hl7.fhir.core#4.2.0 (GitHub f996518d66) generated on Tue, Dec 31, 2019 21:11+1100.
Links: Search |
Version History |
Table of Contents |
QA Page |
Compare to R4 |
|
Propose a change