QICoreDeviceNotRequested

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.

= Must Support, = Is Modifier, = QiCore defined extension

Field	Card.	Type	Description
doNotPerform	1..1	Extension	If true indicates that the request is asking for the specified action to not occur.
doNotPerformReason	1..1	Extension	An Extension
identifier	0..*	List<Identifier>	Identifiers assigned to this order by the orderer or by the receiver.
instantiatesCanonical	0..*	List<canonical>	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.
instantiatesUri	0..*	List<String>	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.
basedOn	0..*	List<Resource>	Plan/proposal/order fulfilled by this request.
priorRequest	0..*	List<Resource>	The request takes the place of the referenced completed or terminated request(s).
groupIdentifier	0..1	Identifier	Composite request this is part of.
status	1..1	String	The status of the request. Binding: Codes representing the status of the request. (required)
intent	1..1	String	Whether the request is a proposal, plan, an original order or a reflex order. Binding: The kind of diagnostic request. (required)
priority	0..1	String	Indicates how quickly the {{title}} should be addressed with respect to other requests. Binding: Identifies the level of importance to be assigned to actioning the request. (required)
code[x]	1..1	Concept	The details of the device to be used. Binding: Codes for devices that can be requested. (example)
doNotPerformValueSet	1..1	Extension	Specifies the value set that characterizes the events or activities that did not occur or were not performed.
parameter	0..*	List<parameter>	Specific parameters for the ordered item. For example, the prism value for lenses.
subject	1..1	QICorePatient	The patient who will use the device.
encounter	0..1	QICoreEncounter	An encounter that provides additional context in which this request is made.
occurrence[x]	0..1	DateTime | Interval<DateTime> | Timing	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	1..1	DateTime	When the request transitioned to being actionable.
requester	0..1	QICoreDevice | QICorePractitioner | QICorePractitionerRole | QICoreOrganization	The individual who initiated the request and has responsibility for its activation.
performerType	0..1	Concept	Desired type of performer for doing the diagnostic testing. Binding: Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (example)
performer	0..1	QICorePractitioner | QICorePractitionerRole | QICoreOrganization | QICoreCareTeam | HealthcareService | QICorePatient | QICoreDevice | QICoreRelatedPerson	The desired performer for doing the diagnostic testing.
reasonCode	0..*	List<Concept>	Reason or justification for the use of this device. Binding: Diagnosis or problem codes justifying the reason for requesting the device. (example)
reasonReference	0..*	List<QICoreCondition | QICoreObservation | QICoreDiagnosticReportLab | DocumentReference>	Reason or justification for the use of this device.
insurance	0..*	List<QICoreCoverage | ClaimResponse>	Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.
supportingInfo	0..*	List<Resource>	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	0..*	List<Annotation>	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	0..*	List<Provenance>	Key events in the history of the request.