ProcedureRequest

Key: = Must support, = QICore-defined extension, = Is-Modifier

Field	Card.	Type and Description
approachBodySite	`0..*`	`List<Extension>` An Extension
appropriatenessScore	`0..1`	`Extension` An Extension
asNeeded[x]	`0..1`	`Boolean \| Concept` If a CodeableConcept is present, it indicates the pre-condition for performing the procedure. For example "pain", "on flare-up", etc. Binding: SNOMED CT Medication As Needed Reason Codes (Example)
authoredOn	`0..1`	`DateTime` When the request transitioned to being actionable.
basedOn	`0..*`	`List<Reference>` Plan/proposal/order fulfilled by this request.
bodySite	`0..*`	`List<Concept>` Anatomic location where the procedure should be performed. This is the target site. Binding: SNOMED CT Body Structures (Example)
category	`0..*`	`List<Concept>` A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). Binding: Procedure Category Codes (SNOMED CT) (Example)
code	`1..1`	`Concept` A code that identifies a particular procedure, diagnostic investigation, or panel of investigations, that have been requested. Binding: value set (Preferred)
context	`0..1`	`Reference` An encounter or episode of care that provides additional information about the healthcare context in which this request is made.
definition	`0..*`	`List<Reference>` Protocol or definition followed by this request.
doNotPerform	`0..1`	`Boolean` Set this to true if the record is saying that the procedure should NOT be performed.
identifier	`0..*`	`List<Identifier>` Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller.
intent	`1..1`	`String` Whether the request is a proposal, plan, an original order or a reflex order. Binding: RequestIntent (Required)
note	`0..*`	`List<Annotation>` Any other notes and comments made about the service request. For example, letting provider know that "patient hates needles" or other provider instructions.
occurrence[x]	`0..1`	`Interval<DateTime \| Interval<DateTime> \| Timing` The date/time at which the diagnostic testing should occur.
performer	`0..1`	`Reference` The desired perfomer for doing the diagnostic testing. For example, the surgeon, dermatopathologist, endoscopist, etc.
performerType	`0..1`	`Concept` Desired type of performer for doing the diagnostic testing. Binding: Participant Roles (Example)
priority	`0..1`	`String` Indicates how quickly the ProcedureRequest should be addressed with respect to other requests. Binding: RequestPriority (Required)
reasonCode	`0..*`	`List<Concept>` An explanation or justification for why this diagnostic investigation is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in supportingInformation. Binding: Procedure Reason Codes (Example)
reasonReference	`0..*`	`List<Reference>` Indicates another resource that provides a justification for why this diagnostic investigation is being requested. May relate to the resources referred to in supportingInformation.
reasonRefused	`0..1`	`Extension` The reason the request was refused. Applies only if the status is refused.
relevantHistory	`0..*`	`List<Reference>` Key events in the history of the request.
replaces	`0..*`	`List<Reference>` The request takes the place of the referenced completed or terminated request(s).
requester	`0..1`	`Requester` The individual who initiated the request and has responsibility for its activation.
requisition	`0..1`	`Identifier` A shared identifier common to all procedure or diagnostic requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier.
specimen	`0..*`	`List<Reference>` One or more specimens that the laboratory procedure will use.
status	`1..1`	`String` The status of the order. Binding: RequestStatus (Required)
subject	`1..1`	`Reference` On whom or what the procedure or diagnostic 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).
supportingInfo	`0..*`	`List<Reference>` Additional clinical information about the patient or specimen that may influence the procedure or diagnostics 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.

Key: = Must support, = QICore-defined extension, = Is-Modifier