Path | Short | Definition | Comments |
---|---|---|---|
Medical device request | 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. | ||
identifier | External Request identifier | Identifiers assigned to this order by the orderer or by the receiver. | |
instantiatesCanonical | Instantiates FHIR protocol or definition | The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. | Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. |
instantiatesUri | Instantiates external protocol or definition | The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest. | This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. |
basedOn | What request fulfills | Plan/proposal/order fulfilled by this request. | |
priorRequest | What request replaces | The request takes the place of the referenced completed or terminated request(s). | |
groupIdentifier | Identifier of composite request | Composite request this is part of. | |
status | draft | active | suspended | completed | entered-in-error | cancelled | The status of the request. | This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid. |
intent | proposal | plan | original-order | encoded | reflex-order | Whether the request is a proposal, plan, an original order or a reflex order. | |
priority | Indicates how quickly the {{title}} should be addressed with respect to other requests | Indicates how quickly the {{title}} should be addressed with respect to other requests. | |
code[x] | Device requested | The details of the device to be used. | |
parameter | Device details | Specific parameters for the ordered item. For example, the prism value for lenses. | |
parameter.id | Unique id for inter-element referencing | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | |
parameter.extension | Additional content defined by implementations | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
parameter.modifierExtension | Extensions that cannot be ignored even if unrecognized | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
parameter.code | Device detail | A code or string that identifies the device detail being asserted. | |
parameter.value[x] | Value of detail | The value of the device detail. | Range means device should have a value that falls somewhere within the specified range. |
subject | Focus of request | The patient who will use the device. | |
encounter | Encounter motivating request | An encounter that provides additional context in which this request is made. | |
occurrence[x] | Desired time or schedule for use | 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". | |
authoredOn | When recorded | When the request transitioned to being actionable. | |
requester | Who/what is requesting diagnostics | The individual who initiated the request and has responsibility for its activation. | |
performerType | Filler role | Desired type of performer for doing the diagnostic testing. | |
performer | Requested Filler | The desired performer for doing the diagnostic testing. | |
reasonCode | Coded Reason for request | Reason or justification for the use of this device. | |
reasonReference | Linked Reason for request | Reason or justification for the use of this device. | |
insurance | Associated insurance coverage | Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. | |
supportingInfo | Additional clinical information | Additional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject's body the device will be used (i.e. the target site). | |
note | Notes or comments | 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. | |
relevantHistory | Request provenance | Key events in the history of the request. | This might not include provenances for all versions of the request - only those deemed "relevant" or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a "relevant" change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject. |
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.
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 [ServiceRequest](servicerequest.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.
Notes to reviewers:
At this time, the code bindings are placeholders to be fleshed out upon further review by the community.
authored-on | When the request transitioned to being actionable | DeviceRequest.authoredOn |
based-on | Plan/proposal/order fulfilled by this request | DeviceRequest.basedOn |
device | Reference to resource that is being requested/ordered | (DeviceRequest.code as Reference) |
event-date | When service should occur | (DeviceRequest.occurrence as dateTime) | (DeviceRequest.occurrence as Period) |
group-identifier | Composite request this is part of | DeviceRequest.groupIdentifier |
instantiates-canonical | Instantiates FHIR protocol or definition | DeviceRequest.instantiatesCanonical |
instantiates-uri | Instantiates external protocol or definition | DeviceRequest.instantiatesUri |
insurance | Associated insurance coverage | DeviceRequest.insurance |
intent | proposal | plan | original-order |reflex-order | DeviceRequest.intent |
performer | Desired performer for service | DeviceRequest.performer |
prior-request | Request takes the place of referenced completed or terminated requests | DeviceRequest.priorRequest |
requester | Who/what is requesting service | DeviceRequest.requester |
status | entered-in-error | draft | active |suspended | completed | DeviceRequest.status |
subject | Individual the service is ordered for | DeviceRequest.subject |