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.

Identifiers assigned to this order by the orderer or by the receiver.

Plan/proposal/order fulfilled by this request.

The request takes the place of the referenced completed or terminated request(s).

Composite A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request this is part of. ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.

The status of the request.

This element is labeled as a modifier because the status contains the codes cancelled revoked and entered-in-error that mark the request as not currently valid.

Whether the request is a proposal, plan, an original order or a reflex order.

This element is immutable. It cannot be changed for the same resource instance.

Indicates how quickly the {{title}} request should be addressed with respect to other requests.

If true, indicates that the provider is asking for the patient to either stop using or to not start using the specified device or category of devices. For example, the patient has undergone surgery and the provider is indicating that the patient should not wear contact lenses.

If do not perform is not specified, the request is a positive request e.g. "do perform". DeviceRequest.reason includes the reason for marking the DeviceRequest as 'do not perform'.

The details of the device to be used.

The number of devices to be provided.

Specific parameters for the ordered item. For example, the prism value for lenses.

A code or string that identifies the device detail being asserted.

The value of the device detail.

Range means device should have a value that falls somewhere within the specified range.

The patient who will use the device.

An encounter that provides additional context in which this request is made.

The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. "Every "Every 8 hours"; "Three hours"; "Three times a day"; "1/2 day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". 2013".

When the request transitioned to being actionable.

The individual or entity who initiated the request and has responsibility for its activation.

The device, practitioner, etc. who initiated desired individual or entity to provide the request. device to the subject of the request (e.g., patient, location).

The organization preferred location(s) where the device should actually be used in coded or practitioner was acting on behalf of. free text form. E.g. at home or nursing day care center.

Desired type of performer Reason or justification for doing the diagnostic testing. use of this device.

When doNotPerform is true, this is the reason for requesting not to provide the device.

The desired perfomer for doing This status is to indicate whether the diagnostic testing. request is a PRN or may be given as needed.

Reason or justification The reason for using the use of this device.

Reason or justification Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the use of this device. requested service.

Additional clinical information about the patient that may influence the request fulfilment. For example, this may includes body include where on the subject's body the device will be used ( i.e. (i.e. the target site).

Knowing where the device is targeted is important for tracking if multiple sites are possible.

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.

Key events in the history of the request.

This may might not include provenances for all versions of the request – - only those deemed “relevant” "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” "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.