DSTU2 STU 3 Ballot
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is

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

5.13 12.8 Resource DeviceUseRequest - Content Resource DeviceUseRequest - Content This resource is marked as a draft

This resource is marked as a draft .

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.
Clinical Decision Support Orders and Observations Work Group Work Group Maturity Level : 0 Maturity Level : 0 Compartments : : 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.

5.13.1 Scope and Usage 12.8.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

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

5.13.2 Boundaries and Relationships 12.8.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

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 and ClinicalImpression

5.13.3 Resource Content 12.8.3 Resource Content

Structure

CodeableConcept CodeableConcept 0..* Notes or comments 0..1
Name Flags Card. Type Description & Constraints Description & Constraints doco
. . DeviceUseRequest DomainResource Medical device request
. . . identifier Σ 0..* DomainResource Identifier A request for a patient to use or be given a medical device Request identifier
. . bodySite[x] . definition Σ 0..1 0..* Reference ( Any ) Target body site Protocol or definition
. . . basedOn bodySiteCodeableConcept Σ 0..* Reference ( Any ) What request fulfills
. . . replaces bodySiteReference Σ 0..* Reference ( BodySite Any ) What request replaces
. . status . requisition Σ 0..1 Identifier Identifier of composite request
. . . status ?! Σ 0..1 code proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted draft | active | suspended | completed | entered-in-error | cancelled
DeviceUseRequestStatus ( RequestStatus ( Required )
. . device . stage ?! Σ 1..1 CodeableConcept proposal | plan | original-order | encoded | reflex-order
RequestStage ( Extensible )
... device[x] Σ 1..1 Device requested
Device Types ( Example )
.... deviceReference Reference ( Device )
. . . . deviceCodeableConcept Device requested CodeableConcept
. . encounter . subject Σ 0..1 1..1 Reference ( Encounter Patient | Group | Location | Device ) Encounter motivating request Focus of request
. . identifier . context Σ 0..* 0..1 Identifier Reference ( Encounter | EpisodeOfCare ) Request identifier Encounter or Episode motivating request
. . indication . occurrence[x] Σ 0..* 0..1 Desired time or schedule for use
. . . . occurrenceDateTime Reason for request dateTime
. notes . . . occurrencePeriod Σ Period
. . . . occurrenceTiming string Timing
. . prnReason . authored Σ 0..* 0..1 CodeableConcept dateTime PRN When recorded
. . orderedOn . requester Σ 0..1 dateTime Reference ( Device | Practitioner | Organization ) When ordered Who/what is requesting diagnostics
. . recordedOn . performerType Σ 0..1 dateTime CodeableConcept When recorded Fille role
Participant Roles ( Example )
. . subject . performer Σ 1..1 0..1 Reference ( Practitioner | Organization | Patient | Device | RelatedPerson ) Focus of request Requested Filler
. . timing[x] . reasonCode Σ 0..1 0..* CodeableConcept Schedule for use Coded Reason for request
Condition/Problem/Diagnosis Codes ( Example )
. . . reasonReference timingTiming Σ 0..* Timing Reference ( Any ) Linked Reason for request
. . . supportingInfo timingPeriod 0..* Period Reference ( Any ) Additional clinical information
. . . note timingDateTime 0..* dateTime Annotation Notes or comments
. priority . . relevantHistory Σ code 0..* routine | urgent | stat | asap DeviceUseRequestPriority Reference ( Required Provenance ) Request provenance

Documentation for this format doco Documentation for this format

UML Diagram UML Diagram ( Legend )

DeviceUseRequest ( ( DomainResource ) Indicates the site on the subject's body where the device should be used ( i.e. the target site) Identifiers assigned to this order by the orderer or by the receiver bodySite[x] : Type [0..1] « CodeableConcept | identifier : 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 ( BodySite ) » [0..*] « Any » Plan/proposal/order fulfilled by this request basedOn : 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 of requisition : Identifier [0..1] The status of the request (this element modifies the meaning of other elements) The status of the request (this element modifies the meaning of other elements) status : : code [0..1] « [0..1] « Codes representing the status of the request. (Strength=Required) Codes representing the status of the request. (Strength=Required) DeviceUseRequestStatus ! » RequestStatus ! » The details of the device to be used Whether the request is a proposal, plan, an original order or a reflex order (this element modifies the meaning of other elements) device stage : CodeableConcept [1..1] « The kind of diagnostic request (Strength=Extensible) RequestStage : + » The details of the device to be used device[x] : Type [1..1] « Reference [1..1] « ( Device » )| CodeableConcept ; Codes for devices that can be requested (Strength=Example) Device Types ?? » An encounter that provides additional context in which this request is made The patient who will use the device encounter : subject : Reference [1..1] « Patient [0..1] « Encounter | Group » | Location | Device » Identifiers assigned to this order by the orderer or by the receiver An encounter that provides additional context in which this request is made identifier : Identifier context : Reference [0..1] « Encounter [0..*] | EpisodeOfCare » Reason or justification for the use of this device 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" indication occurrence[x] : Type [0..1] « dateTime : CodeableConcept | Period [0..*] | Timing » 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 When the request transitioned to being actionable notes authored : dateTime [0..1] Who/what is requesting diagnostics. The practitioner that holds legal responsibility for ordering the investigation requester : Reference [0..1] « Device : string | Practitioner [0..*] | Organization » The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x% Desired type of performer for doing the diagnostic testing prnReason : performerType : 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 [0..*] ?? » The time when the request was made The desired perfomer for doing the diagnostic testing orderedOn performer : Reference [0..1] « Practitioner : dateTime | Organization [0..1] | Patient | Device | RelatedPerson » The time at which the request was made/recorded Reason or justification for the use of this device recordedOn : dateTime [0..1] reasonCode : CodeableConcept [0..*] « Diagnosis or problem codes justifying the reason for requesting the device. (Strength=Example) Condition/Problem/Diagnosis ?? » The patient who will use the device Reason or justification for the use of this device subject : reasonReference : Reference [1..1] « Patient » [0..*] « Any » 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" 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) timing[x] : Type [0..1] « Timing | Period | dateTime » supportingInfo : Reference [0..*] « Any » Characterizes how quickly the use of device must be initiated. Includes concepts such as stat, urgent, routine 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 priority : code [0..1] « note : Annotation [0..*] Codes representing the priority of the request. (Strength=Required) Key events in the history of the request DeviceUseRequestPriority ! » relevantHistory : Reference [0..*] « Provenance »

XML Template 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]>
 <
 <</device>
 <</encounter>
 <</identifier>
 <</indication>
 <
 <</prnReason>
 <
 <
 <</subject>
 <</timing[x]>
 <

 <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 JSON Template { "resourceType" : "", 

{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
DeviceUseRequest.basedOn added
DeviceUseRequest.replaces added
DeviceUseRequest.requisition added
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
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
DeviceUseRequest.authored Renamed from orderedOn to authored
DeviceUseRequest.requester added
DeviceUseRequest.performerType added
DeviceUseRequest.performer added
DeviceUseRequest.reasonCode Renamed from indication to reasonCode
DeviceUseRequest.reasonReference added
DeviceUseRequest.supportingInfo added
DeviceUseRequest.note Renamed from notes to note
Type changed from string to Annotation
DeviceUseRequest.relevantHistory added
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

CodeableConcept 0..* Notes or comments Timing 0..1
Name Flags Card. Type Description & Constraints Description & Constraints doco
. . DeviceUseRequest DomainResource Medical device request
. . . identifier Σ 0..* DomainResource Identifier A request for a patient to use or be given a medical device Request identifier
. . bodySite[x] . definition Σ 0..1 0..* Reference ( Any ) Target body site Protocol or definition
. . . basedOn bodySiteCodeableConcept Σ 0..* CodeableConcept Reference ( Any ) What request fulfills
. . . replaces bodySiteReference Σ 0..* Reference ( BodySite Any ) What request replaces
. . status . requisition Σ 0..1 Identifier Identifier of composite request
. . . status ?! Σ 0..1 code proposed | planned | requested | received | accepted | in-progress | completed | suspended | rejected | aborted draft | active | suspended | completed | entered-in-error | cancelled
DeviceUseRequestStatus ( RequestStatus ( Required )
. . device . stage ?! Σ 1..1 CodeableConcept proposal | plan | original-order | encoded | reflex-order
RequestStage ( Extensible )
... device[x] Σ 1..1 Device requested
Device Types ( Example )
.... deviceReference Reference ( Device )
. . . . deviceCodeableConcept Device requested CodeableConcept
. . encounter . subject Σ 0..1 1..1 Reference ( Encounter Patient | Group | Location | Device ) Encounter motivating request Focus of request
. . identifier . context Σ 0..* 0..1 Identifier Reference ( Encounter | EpisodeOfCare ) Request identifier Encounter or Episode motivating request
. . indication . occurrence[x] Σ 0..* 0..1 Desired time or schedule for use
. . . . occurrenceDateTime Reason for request dateTime
. notes . . . occurrencePeriod Σ Period
. . . . occurrenceTiming string Timing
. . prnReason . authored Σ 0..* 0..1 CodeableConcept dateTime PRN When recorded
. . orderedOn . requester Σ 0..1 dateTime Reference ( Device | Practitioner | Organization ) When ordered Who/what is requesting diagnostics
. . recordedOn . performerType Σ 0..1 dateTime CodeableConcept When recorded Fille role
Participant Roles ( Example )
. . subject . performer Σ 1..1 0..1 Reference ( Practitioner | Organization | Patient | Device | RelatedPerson ) Focus of request Requested Filler
. . timing[x] . reasonCode Σ 0..1 0..* CodeableConcept Schedule for use Coded Reason for request
Condition/Problem/Diagnosis Codes ( Example )
. . . reasonReference timingTiming Σ 0..* Reference ( Any ) Linked Reason for request
. . . supportingInfo timingPeriod 0..* Period Reference ( Any ) Additional clinical information
. . . note timingDateTime 0..* dateTime Annotation Notes or comments
. priority . . relevantHistory Σ code 0..* routine | urgent | stat | asap DeviceUseRequestPriority Reference ( Required Provenance ) Request provenance

Documentation for this format doco Documentation for this format

UML Diagram UML Diagram ( Legend )

DeviceUseRequest ( ( DomainResource ) Indicates the site on the subject's body where the device should be used ( i.e. the target site) Identifiers assigned to this order by the orderer or by the receiver bodySite[x] : Type [0..1] « CodeableConcept | identifier : 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 ( BodySite ) » [0..*] « Any » Plan/proposal/order fulfilled by this request basedOn : 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 of requisition : Identifier [0..1] The status of the request (this element modifies the meaning of other elements) The status of the request (this element modifies the meaning of other elements) status : : code [0..1] « [0..1] « Codes representing the status of the request. (Strength=Required) Codes representing the status of the request. (Strength=Required) DeviceUseRequestStatus ! » RequestStatus ! » The details of the device to be used Whether the request is a proposal, plan, an original order or a reflex order (this element modifies the meaning of other elements) device stage : CodeableConcept [1..1] « The kind of diagnostic request (Strength=Extensible) RequestStage : + » The details of the device to be used device[x] : Type [1..1] « Reference [1..1] « ( Device » )| CodeableConcept ; Codes for devices that can be requested (Strength=Example) Device Types ?? » An encounter that provides additional context in which this request is made The patient who will use the device encounter : subject : Reference [1..1] « Patient [0..1] « Encounter | Group » | Location | Device » Identifiers assigned to this order by the orderer or by the receiver An encounter that provides additional context in which this request is made identifier : Identifier context : Reference [0..1] « Encounter [0..*] | EpisodeOfCare » Reason or justification for the use of this device 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" indication occurrence[x] : Type [0..1] « dateTime : CodeableConcept | Period [0..*] | Timing » 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 When the request transitioned to being actionable notes authored : dateTime [0..1] Who/what is requesting diagnostics. The practitioner that holds legal responsibility for ordering the investigation requester : Reference [0..1] « Device : string | Practitioner [0..*] | Organization » The proposed act must be performed if the indicated conditions occur, e.g.., shortness of breath, SpO2 less than x% Desired type of performer for doing the diagnostic testing prnReason : performerType : 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 [0..*] ?? » The time when the request was made The desired perfomer for doing the diagnostic testing orderedOn performer : Reference [0..1] « Practitioner : dateTime | Organization [0..1] | Patient | Device | RelatedPerson » The time at which the request was made/recorded Reason or justification for the use of this device recordedOn : dateTime [0..1] reasonCode : CodeableConcept [0..*] « Diagnosis or problem codes justifying the reason for requesting the device. (Strength=Example) Condition/Problem/Diagnosis ?? » The patient who will use the device Reason or justification for the use of this device subject : reasonReference : Reference [1..1] « Patient » [0..*] « Any » 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" 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) timing[x] : Type [0..1] « Timing | Period | dateTime » supportingInfo : Reference [0..*] « Any » Characterizes how quickly the use of device must be initiated. Includes concepts such as stat, urgent, routine 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 priority : code [0..1] « note : Annotation [0..*] Codes representing the priority of the request. (Strength=Required) Key events in the history of the request DeviceUseRequestPriority ! » relevantHistory : Reference [0..*] « Provenance »

XML Template 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]>
 <
 <</device>
 <</encounter>
 <</identifier>
 <</indication>
 <
 <</prnReason>
 <
 <
 <</subject>
 <</timing[x]>
 <

 <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 JSON Template { "resourceType" : "", 

{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

}
 
Alternate
definitions:

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
DeviceUseRequest.basedOn added
DeviceUseRequest.replaces added
DeviceUseRequest.requisition added
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
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
DeviceUseRequest.authored Renamed from orderedOn to authored
DeviceUseRequest.requester added
DeviceUseRequest.performerType added
DeviceUseRequest.performer added
DeviceUseRequest.reasonCode Renamed from indication to reasonCode
DeviceUseRequest.reasonReference added
DeviceUseRequest.supportingInfo added
DeviceUseRequest.note Renamed from notes to note
Type changed from string to Annotation
DeviceUseRequest.relevantHistory added
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 , Resource Profile ( XML , (for ) + JSON Schema , ShEx (for Turtle ), Questionnaire )

5.13.3.1 Terminology Bindings 12.8.3.1 Terminology Bindings

DeviceUseRequest.status DeviceUseRequest.priority Notes to reviewers: At this time, the code bindings are placeholders to be fleshed out upon further review by the community.
Path Definition Type Reference
DeviceUseRequest.status Codes representing the status of the request. Codes representing the status of the request. Required DeviceUseRequestStatus RequestStatus
DeviceUseRequest.stage The kind of diagnostic request Extensible Codes representing the priority of the request. RequestStage
DeviceUseRequest.device[x] Codes for devices that can be requested Required Example DeviceUseRequestPriority Device Types
DeviceUseRequest.performerType Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. Example Participant Roles
DeviceUseRequest.reasonCode Diagnosis or problem codes justifying the reason for requesting the device. Example Condition/Problem/Diagnosis Codes

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 12.8.4 Search Parameters Search parameters for this resource. The common parameters also apply. See

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

© HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:43+1100.
Name Type Description Paths
author-date date When the request transitioned to being actionable DeviceUseRequest.authored
based-on reference Plan/proposal/order fulfilled by this request DeviceUseRequest.basedOn
(Any)
code token Code for what is being requested/ordered DeviceUseRequest.deviceCodeableConcept
definition reference Protocol or definition followed by this request DeviceUseRequest.definition
(Any)
device reference Device requested Reference to resource that is being requested/ordered DeviceUseRequest.device DeviceUseRequest.deviceReference
( Device )
patient encounter reference Search by subject - a patient Encounter or Episode during which request was created DeviceUseRequest.subject DeviceUseRequest.context
( EpisodeOfCare , Encounter )
event-date date When service should occur DeviceUseRequest.occurrenceDateTime, DeviceUseRequest.occurrencePeriod
filler reference Desired performer for service DeviceUseRequest.performer
( Practitioner , Organization , Device , Patient , RelatedPerson )
subject identifier token Business identifier for request/order DeviceUseRequest.identifier
patient reference Search by subject Individual the service is ordered for DeviceUseRequest.subject
( Patient )
replaces reference Request takes the place of referenced completed or terminated requests DeviceUseRequest.replaces
Links: Search (Any)
requester reference | Version History Who/what is requesting service  DeviceUseRequest.requester
( Practitioner , Organization , Device | Table of Contents )
requisition token | Compare to DSTU1 Composite request this is part of DeviceUseRequest.requisition
stage token proposal | plan | original-order |reflex-order DeviceUseRequest.stage
status token | entered-in-error | draft | active |suspended | completed  DeviceUseRequest.status
subject reference | Propose a change Individual the service is ordered for DeviceUseRequest.subject
( Group , Device , Patient , Location try { var currentTabIndex = sessionStorage.getItem('fhir-resource-tab-index'); } catch(exception){ } if (!currentTabIndex) currentTabIndex = '0'; $( '#tabs' ).tabs({ active: currentTabIndex, activate: function( event, ui ) { var active = $('.selector').tabs('option', 'active'); currentTabIndex = ui.newTab.index(); document.activeElement.blur(); try { sessionStorage.setItem('fhir-resource-tab-index', currentTabIndex); } catch(exception){ } } });