DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 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

5.13 Resource DeviceUseRequest - Content

This resource is marked as a draft.

Clinical Decision Support Work GroupMaturity Level: 0Compartments: Device, Patient

Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.

5.13.1 Scope and Usage

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 describes the request for the use of a device by a patient. The device may be any pertinent device specified in the Device resource. Examples of devices that may be requested include wheelchair, hearing aids, or an insulin pump. The request may lead to the dispensing of the device to the patient or for use by the patient.

The device use request may represent an order or a prescription entered by a practitioner in a CPOE system or a proposal made by a clinical decision support (CDS) system based on a patient's clinical record and context of care.

5.13.2 Boundaries and Relationships

Certain devices must be implanted via a surgical or other procedure. The data about the implantation or explantation is represented in the Procedure or ProcedureRequest resource, as appropriate. Some devices create observations. These observations are recorded as resources of type DeviceObservationReport.

This resource is referenced by CarePlan and ClinicalImpression

5.13.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseRequest ΣDomainResourceA request for a patient to use or be given a medical device
... bodySite[x] Σ0..1Target body site
.... bodySiteCodeableConceptCodeableConcept
.... bodySiteReferenceReference(BodySite)
... status ?! Σ0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted
DeviceUseRequestStatus (Required)
... device Σ1..1Reference(Device)Device requested
... encounter Σ0..1Reference(Encounter)Encounter motivating request
... identifier Σ0..*IdentifierRequest identifier
... indication Σ0..*CodeableConceptReason for request
... notes Σ0..*stringNotes or comments
... prnReason Σ0..*CodeableConceptPRN
... orderedOn Σ0..1dateTimeWhen ordered
... recordedOn Σ0..1dateTimeWhen recorded
... subject Σ1..1Reference(Patient)Focus of request
... timing[x] Σ0..1Schedule for use
.... timingTimingTiming
.... timingPeriodPeriod
.... timingDateTimedateTime
... priority Σ0..1coderoutine | urgent | stat | asap
DeviceUseRequestPriority (Required)

doco Documentation for this format

UML Diagram

DeviceUseRequest (DomainResource)Indicates the site on the subject's body where the device should be used ( i.e. the target site)bodySite[x] : Type [0..1] « CodeableConcept|Reference(BodySite) »The status of the request (this element modifies the meaning of other elements)status : code [0..1] « Codes representing the status of the request. (Strength=Required)DeviceUseRequestStatus! »The details of the device to be useddevice : Reference [1..1] « Device »An encounter that provides additional context in which this request is madeencounter : Reference [0..1] « Encounter »Identifiers assigned to this order by the orderer or by the receiveridentifier : Identifier [0..*]Reason or justification for the use of this deviceindication : CodeableConcept [0..*]Details about this request 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 statementnotes : string [0..*]The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%prnReason : CodeableConcept [0..*]The time when the request was madeorderedOn : dateTime [0..1]The time at which the request was made/recordedrecordedOn : dateTime [0..1]The patient who will use the devicesubject : Reference [1..1] « Patient »The timing schedule for the use of the device The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013"timing[x] : Type [0..1] « Timing|Period|dateTime »Characterizes how quickly the use of device must be initiated. Includes concepts such as stat, urgent, routinepriority : code [0..1] « Codes representing the priority of the request. (Strength=Required)DeviceUseRequestPriority! »

XML Template

<DeviceUseRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <bodySite[x]><!-- 0..1 CodeableConcept|Reference(BodySite) Target body site --></bodySite[x]>
 <status value="[code]"/><!-- 0..1 proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted -->
 <device><!-- 1..1 Reference(Device) Device requested --></device>
 <encounter><!-- 0..1 Reference(Encounter) Encounter motivating request --></encounter>
 <identifier><!-- 0..* Identifier Request identifier --></identifier>
 <indication><!-- 0..* CodeableConcept Reason for request --></indication>
 <notes value="[string]"/><!-- 0..* Notes or comments -->
 <prnReason><!-- 0..* CodeableConcept PRN --></prnReason>
 <orderedOn value="[dateTime]"/><!-- 0..1 When ordered -->
 <recordedOn value="[dateTime]"/><!-- 0..1 When recorded -->
 <subject><!-- 1..1 Reference(Patient) Focus of request --></subject>
 <timing[x]><!-- 0..1 Timing|Period|dateTime Schedule for use --></timing[x]>
 <priority value="[code]"/><!-- 0..1 routine | urgent | stat | asap -->
</DeviceUseRequest>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseRequest ΣDomainResourceA request for a patient to use or be given a medical device
... bodySite[x] Σ0..1Target body site
.... bodySiteCodeableConceptCodeableConcept
.... bodySiteReferenceReference(BodySite)
... status ?! Σ0..1codeproposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted
DeviceUseRequestStatus (Required)
... device Σ1..1Reference(Device)Device requested
... encounter Σ0..1Reference(Encounter)Encounter motivating request
... identifier Σ0..*IdentifierRequest identifier
... indication Σ0..*CodeableConceptReason for request
... notes Σ0..*stringNotes or comments
... prnReason Σ0..*CodeableConceptPRN
... orderedOn Σ0..1dateTimeWhen ordered
... recordedOn Σ0..1dateTimeWhen recorded
... subject Σ1..1Reference(Patient)Focus of request
... timing[x] Σ0..1Schedule for use
.... timingTimingTiming
.... timingPeriodPeriod
.... timingDateTimedateTime
... priority Σ0..1coderoutine | urgent | stat | asap
DeviceUseRequestPriority (Required)

doco Documentation for this format

UML Diagram

DeviceUseRequest (DomainResource)Indicates the site on the subject's body where the device should be used ( i.e. the target site)bodySite[x] : Type [0..1] « CodeableConcept|Reference(BodySite) »The status of the request (this element modifies the meaning of other elements)status : code [0..1] « Codes representing the status of the request. (Strength=Required)DeviceUseRequestStatus! »The details of the device to be useddevice : Reference [1..1] « Device »An encounter that provides additional context in which this request is madeencounter : Reference [0..1] « Encounter »Identifiers assigned to this order by the orderer or by the receiveridentifier : Identifier [0..*]Reason or justification for the use of this deviceindication : CodeableConcept [0..*]Details about this request 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 statementnotes : string [0..*]The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%prnReason : CodeableConcept [0..*]The time when the request was madeorderedOn : dateTime [0..1]The time at which the request was made/recordedrecordedOn : dateTime [0..1]The patient who will use the devicesubject : Reference [1..1] « Patient »The timing schedule for the use of the device The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013"timing[x] : Type [0..1] « Timing|Period|dateTime »Characterizes how quickly the use of device must be initiated. Includes concepts such as stat, urgent, routinepriority : code [0..1] « Codes representing the priority of the request. (Strength=Required)DeviceUseRequestPriority! »

XML Template

<DeviceUseRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <bodySite[x]><!-- 0..1 CodeableConcept|Reference(BodySite) Target body site --></bodySite[x]>
 <status value="[code]"/><!-- 0..1 proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted -->
 <device><!-- 1..1 Reference(Device) Device requested --></device>
 <encounter><!-- 0..1 Reference(Encounter) Encounter motivating request --></encounter>
 <identifier><!-- 0..* Identifier Request identifier --></identifier>
 <indication><!-- 0..* CodeableConcept Reason for request --></indication>
 <notes value="[string]"/><!-- 0..* Notes or comments -->
 <prnReason><!-- 0..* CodeableConcept PRN --></prnReason>
 <orderedOn value="[dateTime]"/><!-- 0..1 When ordered -->
 <recordedOn value="[dateTime]"/><!-- 0..1 When recorded -->
 <subject><!-- 1..1 Reference(Patient) Focus of request --></subject>
 <timing[x]><!-- 0..1 Timing|Period|dateTime Schedule for use --></timing[x]>
 <priority value="[code]"/><!-- 0..1 routine | urgent | stat | asap -->
</DeviceUseRequest>

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

5.13.3.1 Terminology Bindings

PathDefinitionTypeReference
DeviceUseRequest.status Codes representing the status of the request.RequiredDeviceUseRequestStatus
DeviceUseRequest.priority Codes representing the priority of the request.RequiredDeviceUseRequestPriority

Notes to reviewers:

At this time, the code bindings are placeholders to be fleshed out upon further review by the community.

5.13.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
devicereferenceDevice requestedDeviceUseRequest.device
(Device)
patientreferenceSearch by subject - a patientDeviceUseRequest.subject
(Patient)
subjectreferenceSearch by subjectDeviceUseRequest.subject
(Patient)