This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 

Detailed Descriptions for the elements in the DeviceUseRequest resource.
| DeviceUseRequest | |
| Definition | 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. |
| Control | 1..1 |
| Summary | true |
| DeviceUseRequest.bodySite[x] | |
| Definition | Indicates the site on the subject's body where the device should be used ( i.e. the target site). |
| Control | 0..1 |
| Type | CodeableConcept|Reference(BodySite) |
| [x] Note | See Choice of Data Types for further information about how to use [x] |
| Requirements | Knowing where the device is targeted is important for tracking if multiple sites are possible. |
| Summary | true |
| DeviceUseRequest.status | |
| Definition | The status of the request. |
| Control | 0..1 |
| Binding | DeviceUseRequestStatus: Codes representing the status of the request. (Required) |
| Type | code |
| Is Modifier | true |
| Summary | true |
| DeviceUseRequest.device | |
| Definition | The details of the device to be used. |
| Control | 1..1 |
| Type | Reference(Device) |
| Summary | true |
| DeviceUseRequest.encounter | |
| Definition | An encounter that provides additional context in which this request is made. |
| Control | 0..1 |
| Type | Reference(Encounter) |
| Summary | true |
| DeviceUseRequest.identifier | |
| Definition | Identifiers assigned to this order by the orderer or by the receiver. |
| Note | This is a business identifer, not a resource identifier (see discussion) |
| Control | 0..* |
| Type | Identifier |
| Summary | true |
| DeviceUseRequest.indication | |
| Definition | Reason or justification for the use of this device. |
| Control | 0..* |
| Type | CodeableConcept |
| Summary | true |
| DeviceUseRequest.notes | |
| Definition | 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 statement. |
| Control | 0..* |
| Type | string |
| Summary | true |
| DeviceUseRequest.prnReason | |
| Definition | The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%. |
| Control | 0..* |
| Type | CodeableConcept |
| Summary | true |
| DeviceUseRequest.orderedOn | |
| Definition | The time when the request was made. |
| Control | 0..1 |
| Type | dateTime |
| Summary | true |
| DeviceUseRequest.recordedOn | |
| Definition | The time at which the request was made/recorded. |
| Control | 0..1 |
| Type | dateTime |
| Summary | true |
| DeviceUseRequest.subject | |
| Definition | The patient who will use the device. |
| Control | 1..1 |
| Type | Reference(Patient) |
| Summary | true |
| DeviceUseRequest.timing[x] | |
| Definition | 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". |
| Control | 0..1 |
| Type | Timing|Period|dateTime |
| [x] Note | See Choice of Data Types for further information about how to use [x] |
| Summary | true |
| DeviceUseRequest.priority | |
| Definition | Characterizes how quickly the use of device must be initiated. Includes concepts such as stat, urgent, routine. |
| Control | 0..1 |
| Binding | DeviceUseRequestPriority: Codes representing the priority of the request. (Required) |
| Type | code |
| Summary | true |