STU3 Candidate

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

12.15 Resource DeviceUseRequest - Content

Orders and Observations Work GroupMaturity Level: 0Compartments: Device, Encounter, Patient, Practitioner

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.

12.15.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 is a request resource from a FHIR workflow perspective - see Workflow.

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.

12.15.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

12.15.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseRequest DomainResourceMedical device request
... identifier Σ0..*IdentifierRequest identifier
... definition Σ0..*Reference(Any)Protocol or definition
... basedOn Σ0..*Reference(Any)What request fulfills
... replaces Σ0..*Reference(Any)What request replaces
... requisition Σ0..1IdentifierIdentifier of composite request
... status ?!Σ0..1codedraft | active | suspended | completed | entered-in-error | cancelled
RequestStatus (Required)
... stage ?!Σ1..1CodeableConceptproposal | plan | original-order | encoded | reflex-order
RequestStage (Extensible)
... device[x] Σ1..1Device requested
Device Types (Example)
.... deviceReferenceReference(Device)
.... deviceCodeableConceptCodeableConcept
... subject Σ1..1Reference(Patient | Group | Location | Device)Focus of request
... context Σ0..1Reference(Encounter | EpisodeOfCare)Encounter or Episode motivating request
... occurrence[x] Σ0..1Desired time or schedule for use
.... occurrenceDateTimedateTime
.... occurrencePeriodPeriod
.... occurrenceTimingTiming
... authored Σ0..1dateTimeWhen recorded
... requester Σ0..1Reference(Device | Practitioner | Organization)Who/what is requesting diagnostics
... performerType Σ0..1CodeableConceptFille role
Participant Roles (Example)
... performer Σ0..1Reference(Practitioner | Organization | Patient | Device | RelatedPerson)Requested Filler
... reasonCode Σ0..*CodeableConceptCoded Reason for request
Condition/Problem/Diagnosis Codes (Example)
... reasonReference Σ0..*Reference(Any)Linked Reason for request
... supportingInfo 0..*Reference(Any)Additional clinical information
... note 0..*AnnotationNotes or comments
... relevantHistory 0..*Reference(Provenance)Request provenance

doco Documentation for this format

UML Diagram (Legend)

DeviceUseRequest (DomainResource)Identifiers assigned to this order by the orderer or by the receiveridentifier : Identifier [0..*]Protocol or definition followed by this request. For example: The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%definition : Reference [0..*] « Any »Plan/proposal/order fulfilled by this requestbasedOn : Reference [0..*] « Any »The request takes the place of the referenced completed or terminated request(s)replaces : Reference [0..*] « Any »Composite request this is part ofrequisition : Identifier [0..1]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)RequestStatus! »Whether the request is a proposal, plan, an original order or a reflex order (this element modifies the meaning of other elements)stage : CodeableConcept [1..1] « The kind of diagnostic request (Strength=Extensible)RequestStage+ »The details of the device to be useddevice[x] : Type [1..1] « Reference(Device)|CodeableConcept; Codes for devices that can be requested (Strength=Example)Device Types?? »The patient who will use the devicesubject : Reference [1..1] « Patient|Group|Location|Device »An encounter that provides additional context in which this request is madecontext : Reference [0..1] « Encounter|EpisodeOfCare »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"occurrence[x] : Type [0..1] « dateTime|Period|Timing »When the request transitioned to being actionableauthored : dateTime [0..1]Who/what is requesting diagnostics. The practitioner that holds legal responsibility for ordering the investigationrequester : Reference [0..1] « Device|Practitioner|Organization »Desired type of performer for doing the diagnostic testingperformerType : CodeableConcept [0..1] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example)Participant Roles?? »The desired perfomer for doing the diagnostic testingperformer : Reference [0..1] « Practitioner|Organization|Patient| Device|RelatedPerson »Reason or justification for the use of this devicereasonCode : CodeableConcept [0..*] « Diagnosis or problem codes justifying the reason for requesting the device. (Strength=Example)Condition/Problem/Diagnosis ?? »Reason or justification for the use of this devicereasonReference : Reference [0..*] « Any »Additional clinical information about the patient that may influence the request fulfilment. For example, this may includes body where on the subject's the device will be used ( i.e. the target site)supportingInfo : Reference [0..*] « Any »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 statementnote : Annotation [0..*]Key events in the history of the requestrelevantHistory : Reference [0..*] « Provenance »

XML Template

<DeviceUseRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Request identifier --></identifier>
 <definition><!-- 0..* Reference(Any) Protocol or definition --></definition>
 <basedOn><!-- 0..* Reference(Any) What request fulfills --></basedOn>
 <replaces><!-- 0..* Reference(Any) What request replaces --></replaces>
 <requisition><!-- 0..1 Identifier Identifier of composite request --></requisition>
 <status value="[code]"/><!-- 0..1 draft | active | suspended | completed | entered-in-error | cancelled -->
 <stage><!-- 1..1 CodeableConcept proposal | plan | original-order | encoded | reflex-order --></stage>
 <device[x]><!-- 1..1 Reference(Device)|CodeableConcept Device requested --></device[x]>
 <subject><!-- 1..1 Reference(Patient|Group|Location|Device) Focus of request --></subject>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Encounter or Episode motivating request --></context>
 <occurrence[x]><!-- 0..1 dateTime|Period|Timing Desired time or schedule for use --></occurrence[x]>
 <authored value="[dateTime]"/><!-- 0..1 When recorded -->
 <requester><!-- 0..1 Reference(Device|Practitioner|Organization) Who/what is requesting diagnostics --></requester>
 <performerType><!-- 0..1 CodeableConcept Fille role --></performerType>
 <performer><!-- 0..1 Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson) Requested Filler --></performer>
 <reasonCode><!-- 0..* CodeableConcept Coded Reason for request --></reasonCode>
 <reasonReference><!-- 0..* Reference(Any) Linked Reason for request --></reasonReference>
 <supportingInfo><!-- 0..* Reference(Any) Additional clinical information --></supportingInfo>
 <note><!-- 0..* Annotation Notes or comments --></note>
 <relevantHistory><!-- 0..* Reference(Provenance) Request provenance --></relevantHistory>
</DeviceUseRequest>

JSON Template

{doco
  "resourceType" : "DeviceUseRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Request identifier
  "definition" : [{ Reference(Any) }], // Protocol or definition
  "basedOn" : [{ Reference(Any) }], // What request fulfills
  "replaces" : [{ Reference(Any) }], // What request replaces
  "requisition" : { Identifier }, // Identifier of composite request
  "status" : "<code>", // draft | active | suspended | completed | entered-in-error | cancelled
  "stage" : { CodeableConcept }, // R!  proposal | plan | original-order | encoded | reflex-order
  // device[x]: Device requested. One of these 2:
  "deviceReference" : { Reference(Device) },
  "deviceCodeableConcept" : { CodeableConcept },
  "subject" : { Reference(Patient|Group|Location|Device) }, // R!  Focus of request
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Encounter or Episode motivating request
  // occurrence[x]: Desired time or schedule for use. One of these 3:
  "occurrenceDateTime" : "<dateTime>",
  "occurrencePeriod" : { Period },
  "occurrenceTiming" : { Timing },
  "authored" : "<dateTime>", // When recorded
  "requester" : { Reference(Device|Practitioner|Organization) }, // Who/what is requesting diagnostics
  "performerType" : { CodeableConcept }, // Fille role
  "performer" : { Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson) }, // Requested Filler
  "reasonCode" : [{ CodeableConcept }], // Coded Reason for request
  "reasonReference" : [{ Reference(Any) }], // Linked Reason for request
  "supportingInfo" : [{ Reference(Any) }], // Additional clinical information
  "note" : [{ Annotation }], // Notes or comments
  "relevantHistory" : [{ Reference(Provenance) }] // Request provenance
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:DeviceUseRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:DeviceUseRequest.identifier [ Identifier ], ... ; # 0..* Request identifier
  fhir:DeviceUseRequest.definition [ Reference(Any) ], ... ; # 0..* Protocol or definition
  fhir:DeviceUseRequest.basedOn [ Reference(Any) ], ... ; # 0..* What request fulfills
  fhir:DeviceUseRequest.replaces [ Reference(Any) ], ... ; # 0..* What request replaces
  fhir:DeviceUseRequest.requisition [ Identifier ]; # 0..1 Identifier of composite request
  fhir:DeviceUseRequest.status [ code ]; # 0..1 draft | active | suspended | completed | entered-in-error | cancelled
  fhir:DeviceUseRequest.stage [ CodeableConcept ]; # 1..1 proposal | plan | original-order | encoded | reflex-order
  # DeviceUseRequest.device[x] : 1..1 Device requested. One of these 2
    fhir:DeviceUseRequest.deviceReference [ Reference(Device) ]
    fhir:DeviceUseRequest.deviceCodeableConcept [ CodeableConcept ]
  fhir:DeviceUseRequest.subject [ Reference(Patient|Group|Location|Device) ]; # 1..1 Focus of request
  fhir:DeviceUseRequest.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter or Episode motivating request
  # DeviceUseRequest.occurrence[x] : 0..1 Desired time or schedule for use. One of these 3
    fhir:DeviceUseRequest.occurrenceDateTime [ dateTime ]
    fhir:DeviceUseRequest.occurrencePeriod [ Period ]
    fhir:DeviceUseRequest.occurrenceTiming [ Timing ]
  fhir:DeviceUseRequest.authored [ dateTime ]; # 0..1 When recorded
  fhir:DeviceUseRequest.requester [ Reference(Device|Practitioner|Organization) ]; # 0..1 Who/what is requesting diagnostics
  fhir:DeviceUseRequest.performerType [ CodeableConcept ]; # 0..1 Fille role
  fhir:DeviceUseRequest.performer [ Reference(Practitioner|Organization|Patient|Device|RelatedPerson) ]; # 0..1 Requested Filler
  fhir:DeviceUseRequest.reasonCode [ CodeableConcept ], ... ; # 0..* Coded Reason for request
  fhir:DeviceUseRequest.reasonReference [ Reference(Any) ], ... ; # 0..* Linked Reason for request
  fhir:DeviceUseRequest.supportingInfo [ Reference(Any) ], ... ; # 0..* Additional clinical information
  fhir:DeviceUseRequest.note [ Annotation ], ... ; # 0..* Notes or comments
  fhir:DeviceUseRequest.relevantHistory [ Reference(Provenance) ], ... ; # 0..* Request provenance
]

Changes since DSTU2

DeviceUseRequest
DeviceUseRequest.definition added Element
DeviceUseRequest.basedOn added Element
DeviceUseRequest.replaces added Element
DeviceUseRequest.requisition added Element
DeviceUseRequest.status Change value set from http://hl7.org/fhir/ValueSet/device-use-request-status to http://hl7.org/fhir/ValueSet/request-status
DeviceUseRequest.stage added Element
DeviceUseRequest.device[x] Renamed from device to device[x]
Add CodeableConcept
DeviceUseRequest.subject Add Reference(Group), Add Reference(Location), Add Reference(Device)
DeviceUseRequest.context Renamed from encounter to context
Add Reference(EpisodeOfCare)
DeviceUseRequest.occurrence[x] added Element
DeviceUseRequest.authored Renamed from orderedOn to authored
DeviceUseRequest.requester added Element
DeviceUseRequest.performerType added Element
DeviceUseRequest.performer added Element
DeviceUseRequest.reasonCode Renamed from indication to reasonCode
DeviceUseRequest.reasonReference added Element
DeviceUseRequest.supportingInfo added Element
DeviceUseRequest.note Renamed from notes to note
Type changed from string to Annotation
DeviceUseRequest.relevantHistory added Element
DeviceUseRequest.bodySite[x] deleted
DeviceUseRequest.prnReason deleted
DeviceUseRequest.recordedOn deleted
DeviceUseRequest.timing[x] deleted
DeviceUseRequest.priority deleted

See the Full Difference for further information

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceUseRequest DomainResourceMedical device request
... identifier Σ0..*IdentifierRequest identifier
... definition Σ0..*Reference(Any)Protocol or definition
... basedOn Σ0..*Reference(Any)What request fulfills
... replaces Σ0..*Reference(Any)What request replaces
... requisition Σ0..1IdentifierIdentifier of composite request
... status ?!Σ0..1codedraft | active | suspended | completed | entered-in-error | cancelled
RequestStatus (Required)
... stage ?!Σ1..1CodeableConceptproposal | plan | original-order | encoded | reflex-order
RequestStage (Extensible)
... device[x] Σ1..1Device requested
Device Types (Example)
.... deviceReferenceReference(Device)
.... deviceCodeableConceptCodeableConcept
... subject Σ1..1Reference(Patient | Group | Location | Device)Focus of request
... context Σ0..1Reference(Encounter | EpisodeOfCare)Encounter or Episode motivating request
... occurrence[x] Σ0..1Desired time or schedule for use
.... occurrenceDateTimedateTime
.... occurrencePeriodPeriod
.... occurrenceTimingTiming
... authored Σ0..1dateTimeWhen recorded
... requester Σ0..1Reference(Device | Practitioner | Organization)Who/what is requesting diagnostics
... performerType Σ0..1CodeableConceptFille role
Participant Roles (Example)
... performer Σ0..1Reference(Practitioner | Organization | Patient | Device | RelatedPerson)Requested Filler
... reasonCode Σ0..*CodeableConceptCoded Reason for request
Condition/Problem/Diagnosis Codes (Example)
... reasonReference Σ0..*Reference(Any)Linked Reason for request
... supportingInfo 0..*Reference(Any)Additional clinical information
... note 0..*AnnotationNotes or comments
... relevantHistory 0..*Reference(Provenance)Request provenance

doco Documentation for this format

UML Diagram (Legend)

DeviceUseRequest (DomainResource)Identifiers assigned to this order by the orderer or by the receiveridentifier : Identifier [0..*]Protocol or definition followed by this request. For example: The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x%definition : Reference [0..*] « Any »Plan/proposal/order fulfilled by this requestbasedOn : Reference [0..*] « Any »The request takes the place of the referenced completed or terminated request(s)replaces : Reference [0..*] « Any »Composite request this is part ofrequisition : Identifier [0..1]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)RequestStatus! »Whether the request is a proposal, plan, an original order or a reflex order (this element modifies the meaning of other elements)stage : CodeableConcept [1..1] « The kind of diagnostic request (Strength=Extensible)RequestStage+ »The details of the device to be useddevice[x] : Type [1..1] « Reference(Device)|CodeableConcept; Codes for devices that can be requested (Strength=Example)Device Types?? »The patient who will use the devicesubject : Reference [1..1] « Patient|Group|Location|Device »An encounter that provides additional context in which this request is madecontext : Reference [0..1] « Encounter|EpisodeOfCare »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"occurrence[x] : Type [0..1] « dateTime|Period|Timing »When the request transitioned to being actionableauthored : dateTime [0..1]Who/what is requesting diagnostics. The practitioner that holds legal responsibility for ordering the investigationrequester : Reference [0..1] « Device|Practitioner|Organization »Desired type of performer for doing the diagnostic testingperformerType : CodeableConcept [0..1] « Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (Strength=Example)Participant Roles?? »The desired perfomer for doing the diagnostic testingperformer : Reference [0..1] « Practitioner|Organization|Patient| Device|RelatedPerson »Reason or justification for the use of this devicereasonCode : CodeableConcept [0..*] « Diagnosis or problem codes justifying the reason for requesting the device. (Strength=Example)Condition/Problem/Diagnosis ?? »Reason or justification for the use of this devicereasonReference : Reference [0..*] « Any »Additional clinical information about the patient that may influence the request fulfilment. For example, this may includes body where on the subject's the device will be used ( i.e. the target site)supportingInfo : Reference [0..*] « Any »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 statementnote : Annotation [0..*]Key events in the history of the requestrelevantHistory : Reference [0..*] « Provenance »

XML Template

<DeviceUseRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Request identifier --></identifier>
 <definition><!-- 0..* Reference(Any) Protocol or definition --></definition>
 <basedOn><!-- 0..* Reference(Any) What request fulfills --></basedOn>
 <replaces><!-- 0..* Reference(Any) What request replaces --></replaces>
 <requisition><!-- 0..1 Identifier Identifier of composite request --></requisition>
 <status value="[code]"/><!-- 0..1 draft | active | suspended | completed | entered-in-error | cancelled -->
 <stage><!-- 1..1 CodeableConcept proposal | plan | original-order | encoded | reflex-order --></stage>
 <device[x]><!-- 1..1 Reference(Device)|CodeableConcept Device requested --></device[x]>
 <subject><!-- 1..1 Reference(Patient|Group|Location|Device) Focus of request --></subject>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Encounter or Episode motivating request --></context>
 <occurrence[x]><!-- 0..1 dateTime|Period|Timing Desired time or schedule for use --></occurrence[x]>
 <authored value="[dateTime]"/><!-- 0..1 When recorded -->
 <requester><!-- 0..1 Reference(Device|Practitioner|Organization) Who/what is requesting diagnostics --></requester>
 <performerType><!-- 0..1 CodeableConcept Fille role --></performerType>
 <performer><!-- 0..1 Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson) Requested Filler --></performer>
 <reasonCode><!-- 0..* CodeableConcept Coded Reason for request --></reasonCode>
 <reasonReference><!-- 0..* Reference(Any) Linked Reason for request --></reasonReference>
 <supportingInfo><!-- 0..* Reference(Any) Additional clinical information --></supportingInfo>
 <note><!-- 0..* Annotation Notes or comments --></note>
 <relevantHistory><!-- 0..* Reference(Provenance) Request provenance --></relevantHistory>
</DeviceUseRequest>

JSON Template

{doco
  "resourceType" : "DeviceUseRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Request identifier
  "definition" : [{ Reference(Any) }], // Protocol or definition
  "basedOn" : [{ Reference(Any) }], // What request fulfills
  "replaces" : [{ Reference(Any) }], // What request replaces
  "requisition" : { Identifier }, // Identifier of composite request
  "status" : "<code>", // draft | active | suspended | completed | entered-in-error | cancelled
  "stage" : { CodeableConcept }, // R!  proposal | plan | original-order | encoded | reflex-order
  // device[x]: Device requested. One of these 2:
  "deviceReference" : { Reference(Device) },
  "deviceCodeableConcept" : { CodeableConcept },
  "subject" : { Reference(Patient|Group|Location|Device) }, // R!  Focus of request
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Encounter or Episode motivating request
  // occurrence[x]: Desired time or schedule for use. One of these 3:
  "occurrenceDateTime" : "<dateTime>",
  "occurrencePeriod" : { Period },
  "occurrenceTiming" : { Timing },
  "authored" : "<dateTime>", // When recorded
  "requester" : { Reference(Device|Practitioner|Organization) }, // Who/what is requesting diagnostics
  "performerType" : { CodeableConcept }, // Fille role
  "performer" : { Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson) }, // Requested Filler
  "reasonCode" : [{ CodeableConcept }], // Coded Reason for request
  "reasonReference" : [{ Reference(Any) }], // Linked Reason for request
  "supportingInfo" : [{ Reference(Any) }], // Additional clinical information
  "note" : [{ Annotation }], // Notes or comments
  "relevantHistory" : [{ Reference(Provenance) }] // Request provenance
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:DeviceUseRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:DeviceUseRequest.identifier [ Identifier ], ... ; # 0..* Request identifier
  fhir:DeviceUseRequest.definition [ Reference(Any) ], ... ; # 0..* Protocol or definition
  fhir:DeviceUseRequest.basedOn [ Reference(Any) ], ... ; # 0..* What request fulfills
  fhir:DeviceUseRequest.replaces [ Reference(Any) ], ... ; # 0..* What request replaces
  fhir:DeviceUseRequest.requisition [ Identifier ]; # 0..1 Identifier of composite request
  fhir:DeviceUseRequest.status [ code ]; # 0..1 draft | active | suspended | completed | entered-in-error | cancelled
  fhir:DeviceUseRequest.stage [ CodeableConcept ]; # 1..1 proposal | plan | original-order | encoded | reflex-order
  # DeviceUseRequest.device[x] : 1..1 Device requested. One of these 2
    fhir:DeviceUseRequest.deviceReference [ Reference(Device) ]
    fhir:DeviceUseRequest.deviceCodeableConcept [ CodeableConcept ]
  fhir:DeviceUseRequest.subject [ Reference(Patient|Group|Location|Device) ]; # 1..1 Focus of request
  fhir:DeviceUseRequest.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter or Episode motivating request
  # DeviceUseRequest.occurrence[x] : 0..1 Desired time or schedule for use. One of these 3
    fhir:DeviceUseRequest.occurrenceDateTime [ dateTime ]
    fhir:DeviceUseRequest.occurrencePeriod [ Period ]
    fhir:DeviceUseRequest.occurrenceTiming [ Timing ]
  fhir:DeviceUseRequest.authored [ dateTime ]; # 0..1 When recorded
  fhir:DeviceUseRequest.requester [ Reference(Device|Practitioner|Organization) ]; # 0..1 Who/what is requesting diagnostics
  fhir:DeviceUseRequest.performerType [ CodeableConcept ]; # 0..1 Fille role
  fhir:DeviceUseRequest.performer [ Reference(Practitioner|Organization|Patient|Device|RelatedPerson) ]; # 0..1 Requested Filler
  fhir:DeviceUseRequest.reasonCode [ CodeableConcept ], ... ; # 0..* Coded Reason for request
  fhir:DeviceUseRequest.reasonReference [ Reference(Any) ], ... ; # 0..* Linked Reason for request
  fhir:DeviceUseRequest.supportingInfo [ Reference(Any) ], ... ; # 0..* Additional clinical information
  fhir:DeviceUseRequest.note [ Annotation ], ... ; # 0..* Notes or comments
  fhir:DeviceUseRequest.relevantHistory [ Reference(Provenance) ], ... ; # 0..* Request provenance
]

Changes since DSTU2

DeviceUseRequest
DeviceUseRequest.definition added Element
DeviceUseRequest.basedOn added Element
DeviceUseRequest.replaces added Element
DeviceUseRequest.requisition added Element
DeviceUseRequest.status Change value set from http://hl7.org/fhir/ValueSet/device-use-request-status to http://hl7.org/fhir/ValueSet/request-status
DeviceUseRequest.stage added Element
DeviceUseRequest.device[x] Renamed from device to device[x]
Add CodeableConcept
DeviceUseRequest.subject Add Reference(Group), Add Reference(Location), Add Reference(Device)
DeviceUseRequest.context Renamed from encounter to context
Add Reference(EpisodeOfCare)
DeviceUseRequest.occurrence[x] added Element
DeviceUseRequest.authored Renamed from orderedOn to authored
DeviceUseRequest.requester added Element
DeviceUseRequest.performerType added Element
DeviceUseRequest.performer added Element
DeviceUseRequest.reasonCode Renamed from indication to reasonCode
DeviceUseRequest.reasonReference added Element
DeviceUseRequest.supportingInfo added Element
DeviceUseRequest.note Renamed from notes to note
Type changed from string to Annotation
DeviceUseRequest.relevantHistory added Element
DeviceUseRequest.bodySite[x] deleted
DeviceUseRequest.prnReason deleted
DeviceUseRequest.recordedOn deleted
DeviceUseRequest.timing[x] deleted
DeviceUseRequest.priority deleted

See the Full Difference for further information

 

Alternate definitions: Master Definition (XML, JSON), XML Schema/Schematron (for ) + JSON Schema, ShEx (for Turtle), JSON-LD (for RDF as JSON-LD),

12.15.3.1 Terminology Bindings

PathDefinitionTypeReference
DeviceUseRequest.status Codes representing the status of the request.RequiredRequestStatus
DeviceUseRequest.stage The kind of diagnostic requestExtensibleRequestStage
DeviceUseRequest.device[x] Codes for devices that can be requestedExampleDevice Types
DeviceUseRequest.performerType Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.ExampleParticipant Roles
DeviceUseRequest.reasonCode Diagnosis or problem codes justifying the reason for requesting the device.ExampleCondition/Problem/Diagnosis Codes

Notes to reviewers:

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

12.15.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.

NameTypeDescriptionPathsIn Common
author-datedateWhen the request transitioned to being actionableDeviceUseRequest.authored
based-onreferencePlan/proposal/order fulfilled by this requestDeviceUseRequest.basedOn
(Any)
codetokenCode for what is being requested/orderedDeviceUseRequest.deviceCodeableConcept8 Resources
definitionreferenceProtocol or definition followed by this requestDeviceUseRequest.definition
(Any)
devicereferenceReference to resource that is being requested/orderedDeviceUseRequest.deviceReference
(Device)
encounterreferenceEncounter or Episode during which request was createdDeviceUseRequest.context
(EpisodeOfCare, Encounter)		12 Resources
event-datedateWhen service should occurDeviceUseRequest.occurrenceDateTime, DeviceUseRequest.occurrencePeriod
fillerreferenceDesired performer for serviceDeviceUseRequest.performer
(Practitioner, Organization, Device, Patient, RelatedPerson)
identifiertokenBusiness identifier for request/orderDeviceUseRequest.identifier26 Resources
patientreferenceIndividual the service is ordered forDeviceUseRequest.subject
(Patient)		31 Resources
replacesreferenceRequest takes the place of referenced completed or terminated requestsDeviceUseRequest.replaces
(Any)
requesterreferenceWho/what is requesting service DeviceUseRequest.requester
(Practitioner, Organization, Device)
requisitiontokenComposite request this is part ofDeviceUseRequest.requisition
stagetokenproposal | plan | original-order |reflex-orderDeviceUseRequest.stage
statustokenentered-in-error | draft | active |suspended | completed DeviceUseRequest.status
subjectreferenceIndividual the service is ordered forDeviceUseRequest.subject
(Group, Device, Patient, Location)