FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 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 . Page versions: R5 R4B R4 R3

12.22 Resource DeviceRequest - Content

Orders and Observations Work GroupMaturity Level: 0 DraftCompartments: 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.22.1 Scope and Usage

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

This resource deals with the allocation of a device to a patient and while it may contain instructions on how to use the device, the data about getting the device to the patient is addressed in other resources. For example, Certain devices must be implanted via a surgical or other procedure and the implantation or explantation is represented in the [Procedure](procedure.html) or [ProcedureRequest](procedurerequest.html) resource.

The SupplyRequest resource is similar in that it deals with requesting a particular item for a specific patient. However, DeviceRequest is concerned with items where there is a patient focus, or instructions regarding their use, whereas SupplyRequest is concerned with inventory management.

This resource is referenced by CarePlan and Observation

12.22.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceRequest DomainResourceMedical device request
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierExternal Request identifier
... definition Σ0..*Reference(ActivityDefinition | PlanDefinition)Protocol or definition
... basedOn Σ0..*Reference(Any)What request fulfills
... priorRequest Σ0..*Reference(Any)What request replaces
... groupIdentifier Σ0..1IdentifierIdentifier of composite request
... status ?!Σ0..1codedraft | active | suspended | completed | entered-in-error | cancelled
RequestStatus (Required)
... intent ?!Σ1..1CodeableConceptproposal | plan | original-order | encoded | reflex-order
RequestIntent (Required)
... priority Σ0..1codeIndicates how quickly the {{title}} should be addressed with respect to other requests
RequestPriority (Required)
... code[x] Σ1..1Device requested
FHIR Device Types (Example)
.... codeReferenceReference(Device)
.... codeCodeableConceptCodeableConcept
... 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
... authoredOn Σ0..1dateTimeWhen recorded
... requester Σ0..1BackboneElementWho/what is requesting diagnostics
.... agent Σ1..1Reference(Device | Practitioner | Organization)Individual making the request
.... onBehalfOf Σ0..1Reference(Organization)Organization agent is acting for
... performerType Σ0..1CodeableConceptFille role
Participant Roles (Example)
... performer Σ0..1Reference(Practitioner | Organization | Patient | Device | RelatedPerson | HealthcareService)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)

DeviceRequest (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..*] ActivityDefinition|PlanDefinition Plan/proposal/order fulfilled by this requestbasedOn : Reference [0..*] Any The request takes the place of the referenced completed or terminated request(s)priorRequest : Reference [0..*] Any Composite request this is part ofgroupIdentifier : 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)intent : CodeableConcept [1..1] The kind of diagnostic request (Strength=Required)RequestIntent! Indicates how quickly the {{title}} should be addressed with respect to other requestspriority : code [0..1] Identifies the level of importance to be assigned to actioning the request (Strength=Required)RequestPriority! The details of the device to be usedcode[x] : Type [1..1] Reference(Device)|CodeableConcept; Codes for devices that can be requested (Strength=Example)FHIR 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 actionableauthoredOn : dateTime [0..1]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|HealthcareService 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 RequesterThe device, practitioner, etc. who initiated the requestagent : Reference [1..1] Device|Practitioner|Organization The organization the device or practitioner was acting on behalf ofonBehalfOf : Reference [0..1] Organization The individual who initiated the request and has responsibility for its activationrequester[0..1]

XML Template

<DeviceRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Request identifier --></identifier>
 <definition><!-- 0..* Reference(ActivityDefinition|PlanDefinition) Protocol or definition --></definition>
 <basedOn><!-- 0..* Reference(Any) What request fulfills --></basedOn>
 <priorRequest><!-- 0..* Reference(Any) What request replaces --></priorRequest>
 <groupIdentifier><!-- 0..1 Identifier Identifier of composite request --></groupIdentifier>
 <status value="[code]"/><!-- 0..1 draft | active | suspended | completed | entered-in-error | cancelled -->
 <intent><!-- 1..1 CodeableConcept proposal | plan | original-order | encoded | reflex-order  --></intent>
 <priority value="[code]"/><!-- 0..1 Indicates how quickly the {{title}} should be addressed with respect to other requests -->
 <code[x]><!-- 1..1 Reference(Device)|CodeableConcept Device requested --></code[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]>
 <authoredOn value="[dateTime]"/><!-- 0..1 When recorded -->
 <requester>  <!-- 0..1 Who/what is requesting diagnostics -->
  <agent><!-- 1..1 Reference(Device|Practitioner|Organization) Individual making the request --></agent>
  <onBehalfOf><!-- 0..1 Reference(Organization) Organization agent is acting for --></onBehalfOf>
 </requester>
 <performerType><!-- 0..1 CodeableConcept Fille role --></performerType>
 <performer><!-- 0..1 Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson|HealthcareService) 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>
</DeviceRequest>

JSON Template

{doco
  "resourceType" : "DeviceRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Request identifier
  "definition" : [{ Reference(ActivityDefinition|PlanDefinition) }], // Protocol or definition
  "basedOn" : [{ Reference(Any) }], // What request fulfills
  "priorRequest" : [{ Reference(Any) }], // What request replaces
  "groupIdentifier" : { Identifier }, // Identifier of composite request
  "status" : "<code>", // draft | active | suspended | completed | entered-in-error | cancelled
  "intent" : { CodeableConcept }, // R!  proposal | plan | original-order | encoded | reflex-order 
  "priority" : "<code>", // Indicates how quickly the {{title}} should be addressed with respect to other requests
  // code[x]: Device requested. One of these 2:
  "codeReference" : { Reference(Device) },
  "codeCodeableConcept" : { 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 },
  "authoredOn" : "<dateTime>", // When recorded
  "requester" : { // Who/what is requesting diagnostics
    "agent" : { Reference(Device|Practitioner|Organization) }, // R!  Individual making the request
    "onBehalfOf" : { Reference(Organization) } // Organization agent is acting for
  },
  "performerType" : { CodeableConcept }, // Fille role
  "performer" : { Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson|HealthcareService) }, // 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:DeviceRequest;
  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:DeviceRequest.identifier [ Identifier ], ... ; # 0..* External Request identifier
  fhir:DeviceRequest.definition [ Reference(ActivityDefinition|PlanDefinition) ], ... ; # 0..* Protocol or definition
  fhir:DeviceRequest.basedOn [ Reference(Any) ], ... ; # 0..* What request fulfills
  fhir:DeviceRequest.priorRequest [ Reference(Any) ], ... ; # 0..* What request replaces
  fhir:DeviceRequest.groupIdentifier [ Identifier ]; # 0..1 Identifier of composite request
  fhir:DeviceRequest.status [ code ]; # 0..1 draft | active | suspended | completed | entered-in-error | cancelled
  fhir:DeviceRequest.intent [ CodeableConcept ]; # 1..1 proposal | plan | original-order | encoded | reflex-order
  fhir:DeviceRequest.priority [ code ]; # 0..1 Indicates how quickly the {{title}} should be addressed with respect to other requests
  # DeviceRequest.code[x] : 1..1 Device requested. One of these 2
    fhir:DeviceRequest.codeReference [ Reference(Device) ]
    fhir:DeviceRequest.codeCodeableConcept [ CodeableConcept ]
  fhir:DeviceRequest.subject [ Reference(Patient|Group|Location|Device) ]; # 1..1 Focus of request
  fhir:DeviceRequest.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter or Episode motivating request
  # DeviceRequest.occurrence[x] : 0..1 Desired time or schedule for use. One of these 3
    fhir:DeviceRequest.occurrenceDateTime [ dateTime ]
    fhir:DeviceRequest.occurrencePeriod [ Period ]
    fhir:DeviceRequest.occurrenceTiming [ Timing ]
  fhir:DeviceRequest.authoredOn [ dateTime ]; # 0..1 When recorded
  fhir:DeviceRequest.requester [ # 0..1 Who/what is requesting diagnostics
    fhir:DeviceRequest.requester.agent [ Reference(Device|Practitioner|Organization) ]; # 1..1 Individual making the request
    fhir:DeviceRequest.requester.onBehalfOf [ Reference(Organization) ]; # 0..1 Organization agent is acting for
  ];
  fhir:DeviceRequest.performerType [ CodeableConcept ]; # 0..1 Fille role
  fhir:DeviceRequest.performer [ Reference(Practitioner|Organization|Patient|Device|RelatedPerson|HealthcareService) ]; # 0..1 Requested Filler
  fhir:DeviceRequest.reasonCode [ CodeableConcept ], ... ; # 0..* Coded Reason for request
  fhir:DeviceRequest.reasonReference [ Reference(Any) ], ... ; # 0..* Linked Reason for request
  fhir:DeviceRequest.supportingInfo [ Reference(Any) ], ... ; # 0..* Additional clinical information
  fhir:DeviceRequest.note [ Annotation ], ... ; # 0..* Notes or comments
  fhir:DeviceRequest.relevantHistory [ Reference(Provenance) ], ... ; # 0..* Request provenance
]

Changes since DSTU2

DeviceRequest
DeviceRequest.definition
  • Added Element
DeviceRequest.basedOn
  • Added Element
DeviceRequest.priorRequest
  • Added Element
DeviceRequest.groupIdentifier
  • Added Element
DeviceRequest.status
  • Change value set from http://hl7.org/fhir/ValueSet/device-use-request-status to http://hl7.org/fhir/ValueSet/request-status
DeviceRequest.intent
  • Added Element
DeviceRequest.priority
  • Change value set from http://hl7.org/fhir/ValueSet/device-use-request-priority to http://hl7.org/fhir/ValueSet/request-priority
  • Default Value "If missing, normal priority" added
DeviceRequest.code[x]
  • Added Element
DeviceRequest.subject
  • Add Reference(Group), Add Reference(Location), Add Reference(Device)
DeviceRequest.context
  • Renamed from encounter to context
  • Add Reference(EpisodeOfCare)
DeviceRequest.occurrence[x]
  • Added Element
DeviceRequest.authoredOn
  • Added Element
DeviceRequest.requester
  • Added Element
DeviceRequest.requester.agent
  • Added Element
DeviceRequest.requester.onBehalfOf
  • Added Element
DeviceRequest.performerType
  • Added Element
DeviceRequest.performer
  • Added Element
DeviceRequest.reasonCode
  • Renamed from indication to reasonCode
DeviceRequest.reasonReference
  • Added Element
DeviceRequest.supportingInfo
  • Added Element
DeviceRequest.note
  • Renamed from notes to note
  • Type changed from string to Annotation
DeviceRequest.relevantHistory
  • Added Element
DeviceRequest.bodySite[x]
  • deleted
DeviceRequest.device
  • deleted
DeviceRequest.prnReason
  • deleted
DeviceRequest.orderedOn
  • deleted
DeviceRequest.recordedOn
  • deleted
DeviceRequest.timing[x]
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON.

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. DeviceRequest DomainResourceMedical device request
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierExternal Request identifier
... definition Σ0..*Reference(ActivityDefinition | PlanDefinition)Protocol or definition
... basedOn Σ0..*Reference(Any)What request fulfills
... priorRequest Σ0..*Reference(Any)What request replaces
... groupIdentifier Σ0..1IdentifierIdentifier of composite request
... status ?!Σ0..1codedraft | active | suspended | completed | entered-in-error | cancelled
RequestStatus (Required)
... intent ?!Σ1..1CodeableConceptproposal | plan | original-order | encoded | reflex-order
RequestIntent (Required)
... priority Σ0..1codeIndicates how quickly the {{title}} should be addressed with respect to other requests
RequestPriority (Required)
... code[x] Σ1..1Device requested
FHIR Device Types (Example)
.... codeReferenceReference(Device)
.... codeCodeableConceptCodeableConcept
... 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
... authoredOn Σ0..1dateTimeWhen recorded
... requester Σ0..1BackboneElementWho/what is requesting diagnostics
.... agent Σ1..1Reference(Device | Practitioner | Organization)Individual making the request
.... onBehalfOf Σ0..1Reference(Organization)Organization agent is acting for
... performerType Σ0..1CodeableConceptFille role
Participant Roles (Example)
... performer Σ0..1Reference(Practitioner | Organization | Patient | Device | RelatedPerson | HealthcareService)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)

DeviceRequest (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..*] ActivityDefinition|PlanDefinition Plan/proposal/order fulfilled by this requestbasedOn : Reference [0..*] Any The request takes the place of the referenced completed or terminated request(s)priorRequest : Reference [0..*] Any Composite request this is part ofgroupIdentifier : 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)intent : CodeableConcept [1..1] The kind of diagnostic request (Strength=Required)RequestIntent! Indicates how quickly the {{title}} should be addressed with respect to other requestspriority : code [0..1] Identifies the level of importance to be assigned to actioning the request (Strength=Required)RequestPriority! The details of the device to be usedcode[x] : Type [1..1] Reference(Device)|CodeableConcept; Codes for devices that can be requested (Strength=Example)FHIR 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 actionableauthoredOn : dateTime [0..1]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|HealthcareService 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 RequesterThe device, practitioner, etc. who initiated the requestagent : Reference [1..1] Device|Practitioner|Organization The organization the device or practitioner was acting on behalf ofonBehalfOf : Reference [0..1] Organization The individual who initiated the request and has responsibility for its activationrequester[0..1]

XML Template

<DeviceRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Request identifier --></identifier>
 <definition><!-- 0..* Reference(ActivityDefinition|PlanDefinition) Protocol or definition --></definition>
 <basedOn><!-- 0..* Reference(Any) What request fulfills --></basedOn>
 <priorRequest><!-- 0..* Reference(Any) What request replaces --></priorRequest>
 <groupIdentifier><!-- 0..1 Identifier Identifier of composite request --></groupIdentifier>
 <status value="[code]"/><!-- 0..1 draft | active | suspended | completed | entered-in-error | cancelled -->
 <intent><!-- 1..1 CodeableConcept proposal | plan | original-order | encoded | reflex-order  --></intent>
 <priority value="[code]"/><!-- 0..1 Indicates how quickly the {{title}} should be addressed with respect to other requests -->
 <code[x]><!-- 1..1 Reference(Device)|CodeableConcept Device requested --></code[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]>
 <authoredOn value="[dateTime]"/><!-- 0..1 When recorded -->
 <requester>  <!-- 0..1 Who/what is requesting diagnostics -->
  <agent><!-- 1..1 Reference(Device|Practitioner|Organization) Individual making the request --></agent>
  <onBehalfOf><!-- 0..1 Reference(Organization) Organization agent is acting for --></onBehalfOf>
 </requester>
 <performerType><!-- 0..1 CodeableConcept Fille role --></performerType>
 <performer><!-- 0..1 Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson|HealthcareService) 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>
</DeviceRequest>

JSON Template

{doco
  "resourceType" : "DeviceRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Request identifier
  "definition" : [{ Reference(ActivityDefinition|PlanDefinition) }], // Protocol or definition
  "basedOn" : [{ Reference(Any) }], // What request fulfills
  "priorRequest" : [{ Reference(Any) }], // What request replaces
  "groupIdentifier" : { Identifier }, // Identifier of composite request
  "status" : "<code>", // draft | active | suspended | completed | entered-in-error | cancelled
  "intent" : { CodeableConcept }, // R!  proposal | plan | original-order | encoded | reflex-order 
  "priority" : "<code>", // Indicates how quickly the {{title}} should be addressed with respect to other requests
  // code[x]: Device requested. One of these 2:
  "codeReference" : { Reference(Device) },
  "codeCodeableConcept" : { 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 },
  "authoredOn" : "<dateTime>", // When recorded
  "requester" : { // Who/what is requesting diagnostics
    "agent" : { Reference(Device|Practitioner|Organization) }, // R!  Individual making the request
    "onBehalfOf" : { Reference(Organization) } // Organization agent is acting for
  },
  "performerType" : { CodeableConcept }, // Fille role
  "performer" : { Reference(Practitioner|Organization|Patient|Device|
   RelatedPerson|HealthcareService) }, // 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:DeviceRequest;
  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:DeviceRequest.identifier [ Identifier ], ... ; # 0..* External Request identifier
  fhir:DeviceRequest.definition [ Reference(ActivityDefinition|PlanDefinition) ], ... ; # 0..* Protocol or definition
  fhir:DeviceRequest.basedOn [ Reference(Any) ], ... ; # 0..* What request fulfills
  fhir:DeviceRequest.priorRequest [ Reference(Any) ], ... ; # 0..* What request replaces
  fhir:DeviceRequest.groupIdentifier [ Identifier ]; # 0..1 Identifier of composite request
  fhir:DeviceRequest.status [ code ]; # 0..1 draft | active | suspended | completed | entered-in-error | cancelled
  fhir:DeviceRequest.intent [ CodeableConcept ]; # 1..1 proposal | plan | original-order | encoded | reflex-order
  fhir:DeviceRequest.priority [ code ]; # 0..1 Indicates how quickly the {{title}} should be addressed with respect to other requests
  # DeviceRequest.code[x] : 1..1 Device requested. One of these 2
    fhir:DeviceRequest.codeReference [ Reference(Device) ]
    fhir:DeviceRequest.codeCodeableConcept [ CodeableConcept ]
  fhir:DeviceRequest.subject [ Reference(Patient|Group|Location|Device) ]; # 1..1 Focus of request
  fhir:DeviceRequest.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Encounter or Episode motivating request
  # DeviceRequest.occurrence[x] : 0..1 Desired time or schedule for use. One of these 3
    fhir:DeviceRequest.occurrenceDateTime [ dateTime ]
    fhir:DeviceRequest.occurrencePeriod [ Period ]
    fhir:DeviceRequest.occurrenceTiming [ Timing ]
  fhir:DeviceRequest.authoredOn [ dateTime ]; # 0..1 When recorded
  fhir:DeviceRequest.requester [ # 0..1 Who/what is requesting diagnostics
    fhir:DeviceRequest.requester.agent [ Reference(Device|Practitioner|Organization) ]; # 1..1 Individual making the request
    fhir:DeviceRequest.requester.onBehalfOf [ Reference(Organization) ]; # 0..1 Organization agent is acting for
  ];
  fhir:DeviceRequest.performerType [ CodeableConcept ]; # 0..1 Fille role
  fhir:DeviceRequest.performer [ Reference(Practitioner|Organization|Patient|Device|RelatedPerson|HealthcareService) ]; # 0..1 Requested Filler
  fhir:DeviceRequest.reasonCode [ CodeableConcept ], ... ; # 0..* Coded Reason for request
  fhir:DeviceRequest.reasonReference [ Reference(Any) ], ... ; # 0..* Linked Reason for request
  fhir:DeviceRequest.supportingInfo [ Reference(Any) ], ... ; # 0..* Additional clinical information
  fhir:DeviceRequest.note [ Annotation ], ... ; # 0..* Notes or comments
  fhir:DeviceRequest.relevantHistory [ Reference(Provenance) ], ... ; # 0..* Request provenance
]

Changes since DSTU2

DeviceRequest
DeviceRequest.definition
  • Added Element
DeviceRequest.basedOn
  • Added Element
DeviceRequest.priorRequest
  • Added Element
DeviceRequest.groupIdentifier
  • Added Element
DeviceRequest.status
  • Change value set from http://hl7.org/fhir/ValueSet/device-use-request-status to http://hl7.org/fhir/ValueSet/request-status
DeviceRequest.intent
  • Added Element
DeviceRequest.priority
  • Change value set from http://hl7.org/fhir/ValueSet/device-use-request-priority to http://hl7.org/fhir/ValueSet/request-priority
  • Default Value "If missing, normal priority" added
DeviceRequest.code[x]
  • Added Element
DeviceRequest.subject
  • Add Reference(Group), Add Reference(Location), Add Reference(Device)
DeviceRequest.context
  • Renamed from encounter to context
  • Add Reference(EpisodeOfCare)
DeviceRequest.occurrence[x]
  • Added Element
DeviceRequest.authoredOn
  • Added Element
DeviceRequest.requester
  • Added Element
DeviceRequest.requester.agent
  • Added Element
DeviceRequest.requester.onBehalfOf
  • Added Element
DeviceRequest.performerType
  • Added Element
DeviceRequest.performer
  • Added Element
DeviceRequest.reasonCode
  • Renamed from indication to reasonCode
DeviceRequest.reasonReference
  • Added Element
DeviceRequest.supportingInfo
  • Added Element
DeviceRequest.note
  • Renamed from notes to note
  • Type changed from string to Annotation
DeviceRequest.relevantHistory
  • Added Element
DeviceRequest.bodySite[x]
  • deleted
DeviceRequest.device
  • deleted
DeviceRequest.prnReason
  • deleted
DeviceRequest.orderedOn
  • deleted
DeviceRequest.recordedOn
  • deleted
DeviceRequest.timing[x]
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON.

 

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

12.22.3.1 Terminology Bindings

PathDefinitionTypeReference
DeviceRequest.status Codes representing the status of the request.RequiredRequestStatus
DeviceRequest.intent The kind of diagnostic requestRequiredvalueset-request-intent.html
DeviceRequest.priority Identifies the level of importance to be assigned to actioning the requestRequiredRequestPriority
DeviceRequest.code[x] Codes for devices that can be requestedExampleFHIR Device Types
DeviceRequest.performerType Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.ExampleParticipant Roles
DeviceRequest.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.22.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.

NameTypeDescriptionExpressionIn Common
authored-ondateWhen the request transitioned to being actionableDeviceRequest.authoredOn
based-onreferencePlan/proposal/order fulfilled by this requestDeviceRequest.basedOn
(Any)
codetokenCode for what is being requested/orderedDeviceRequest.code.as(CodeableConcept)8 Resources
definitionreferenceProtocol or definition followed by this requestDeviceRequest.definition
(PlanDefinition, ActivityDefinition)
devicereferenceReference to resource that is being requested/orderedDeviceRequest.code.as(Reference)
(Device)
encounterreferenceEncounter or Episode during which request was createdDeviceRequest.context
(EpisodeOfCare, Encounter)		12 Resources
event-datedateWhen service should occurDeviceRequest.occurrence.as(DateTime) | DeviceRequest.occurrence.as(Period)
group-identifiertokenComposite request this is part ofDeviceRequest.groupIdentifier
identifiertokenBusiness identifier for request/orderDeviceRequest.identifier26 Resources
intenttokenproposal | plan | original-order |reflex-orderDeviceRequest.intent
patientreferenceIndividual the service is ordered forDeviceRequest.subject
(Patient)		31 Resources
performerreferenceDesired performer for serviceDeviceRequest.performer
(Practitioner, Organization, Device, Patient, HealthcareService, RelatedPerson)
priorrequestreferenceRequest takes the place of referenced completed or terminated requestsDeviceRequest.priorRequest
(Any)
requesterreferenceWho/what is requesting service DeviceRequest.requester.agent
(Practitioner, Organization, Device)
statustokenentered-in-error | draft | active |suspended | completed DeviceRequest.status
subjectreferenceIndividual the service is ordered forDeviceRequest.subject
(Group, Device, Patient, Location)