QICoreServiceRequest

A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.

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

Field	Card.	Type	Description
statusReason	0..1	Extension	Captures the reason for the current state of the resource.
approachBodyStructure	0..*	List<Extension>	The approach body site used for this procedure. Multiple locations are allowed.
appropriatenessScore	0..1	Extension	The RAND appropriateness score for the requested procedure.
isElective	0..1	Extension	An Extension
identifier	0..*	List<Identifier>	Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller.
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 ServiceRequest.
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 ServiceRequest.
basedOn	0..*	List<QICoreCarePlan | QICoreServiceNotRequested | QICoreMedicationNotRequested>	Plan/proposal/order fulfilled by this request.
replaces	0..*	List<QICoreServiceNotRequested>	The request takes the place of the referenced completed or terminated request(s).
requisition	0..1	Identifier	A shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier.
status	1..1	String	The status of the order. Binding: The status of a service order. (required)
intent	1..1	String	Whether the request is a proposal, plan, an original order or a reflex order. Binding: The kind of service request. (required)
category	0..*	List<Concept>	A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). Binding: Classification of the requested service. (example)
priority	0..1	String	Indicates how quickly the ServiceRequest should be addressed with respect to other requests. Binding: Identifies the level of importance to be assigned to actioning the request. (required)
doNotPerform	0..1	Boolean	Set this to true if the record is saying that the service/procedure should NOT be performed.
code	0..1	Concept	A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. Binding: Codes describing the Procedure Type (preferred)
orderDetail	0..*	List<Concept>	Additional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. Binding: Codified order entry details which are based on order context. (example)
quantity[x]	0..1	Quantity | Ratio | Interval<Quantity>	An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction).
subject	1..1	QICorePatient	On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans).
encounter	0..1	QICoreEncounter	An encounter that provides additional information about the healthcare context in which this request is made.
occurrence[x]	0..1	DateTime | Interval<DateTime> | Timing	The date/time at which the requested service should occur.
asNeeded[x]	0..1	Boolean | Concept	If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. Binding: A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc. (example)
authoredOn	0..1	DateTime	When the request transitioned to being actionable.
requester	0..1	QICorePractitioner | QICorePractitionerRole | QICoreOrganization | QICorePatient | QICoreRelatedPerson | QICoreDevice	The individual who initiated the request and has responsibility for its activation.
performerType	0..1	Concept	Desired type of performer for doing the requested service. Binding: Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. (example)
performer	0..*	List<QICorePractitioner | QICoreOrganization | QICorePatient | QICoreDevice | QICoreRelatedPerson | HealthcareService>	The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc.
locationCode	0..*	List<Concept>	The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center. Binding: A location type where services are delivered. (example)
locationReference	0..*	List<QICoreLocation>	A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center.
reasonCode	0..*	List<Concept>	An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in `supportingInfo`. Binding: Diagnosis or problem codes justifying the reason for requesting the service investigation. (example)
reasonReference	0..*	List<QICoreCondition | QICoreObservation | QICoreDiagnosticReportLab | DocumentReference>	Indicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in `supportingInfo`.
insurance	0..*	List<QICoreCoverage | ClaimResponse>	Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service.
supportingInfo	0..*	List<Resource>	Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements.
specimen	0..*	List<QICoreSpecimen>	One or more specimens that the laboratory procedure will use.
bodySite	0..*	List<Concept>	Anatomic location where the procedure should be performed. This is the target site. Binding: Codes describing anatomical locations. May include laterality. (example)
note	0..*	List<Annotation>	Any other notes and comments made about the service request. For example, internal billing notes.
patientInstruction	0..1	String	Instructions in terms that are understood by the patient or consumer.
relevantHistory	0..*	List<Provenance>	Key events in the history of the request.