FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R3 R2

Orders and Observations Work GroupMaturity Level: 3 Trial UseCompartments: Device, Encounter, Patient, Practitioner, RelatedPerson

Detailed Descriptions for the elements in the ProcedureRequest resource.

ProcedureRequest
Definition

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

Control1..1
Alternate Namesdiagnostic request
ProcedureRequest.identifier
Definition

Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Summarytrue
Comments

The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below.

ProcedureRequest.definition
Definition

Protocol or definition followed by this request.

Control0..*
TypeReference(ActivityDefinition | PlanDefinition)
Alternate Namesprotocol
Summarytrue
ProcedureRequest.basedOn
Definition

Plan/proposal/order fulfilled by this request.

Control0..*
TypeReference(Any)
Alternate Namesfulfills
Summarytrue
ProcedureRequest.replaces
Definition

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

Control0..*
TypeReference(Any)
Summarytrue
ProcedureRequest.requisition
Definition

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.

Control0..1
TypeIdentifier
Requirements

Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes.

Alternate NamesgrouperId; groupIdentifier
Summarytrue
Comments

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

ProcedureRequest.status
Definition

The status of the order.

Control1..1
Terminology BindingRequestStatus (Required)
Typecode
Is Modifiertrue
Summarytrue
Comments

The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see Event Pattern for general discussion) or using the Task resource.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

ProcedureRequest.intent
Definition

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

Control1..1
Terminology BindingRequestIntent (Required)
Typecode
Is Modifiertrue
Summarytrue
Comments

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

ProcedureRequest.priority
Definition

Indicates how quickly the ProcedureRequest should be addressed with respect to other requests.

Control0..1
Terminology BindingRequestPriority (Required)
Typecode
Meaning if MissingIf missing, this task should be performed with normal priority
Summarytrue
ProcedureRequest.doNotPerform
Definition

Set this to true if the record is saying that the procedure should NOT be performed.

Control0..1
Typeboolean
Is Modifiertrue
Default Valuefalse
Requirements

Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc.

Summarytrue
Comments

This element is labeled as a modifier because it indicates that a procedure shouldn't happen, instead of a request for it to happen. In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ProcedureRequest.code and ProcedureRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation.

ProcedureRequest.category
Definition

A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").

Control0..*
Terminology BindingProcedure Category Codes (SNOMED CT) (Example)
TypeCodeableConcept
Requirements

Used for filtering what procedure request are retrieved and displayed.

Summarytrue
Comments

There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set.

ProcedureRequest.code
Definition

A code that identifies a particular procedure, diagnostic investigation, or panel of investigations, that have been requested.

Control1..1
Terminology BindingProcedure Codes (SNOMED CT) (Example)
TypeCodeableConcept
Summarytrue
Comments

Many laboratory and radiology procedure codes embed the specimen/organ system in the test ordeer name, for example, serum or serum/plasma glucose, or a chest xray. The specimen may not be recorded separately from the test code.

ProcedureRequest.subject
Definition

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).

Control1..1
TypeReference(Patient | Group | Location | Device)
Summarytrue
ProcedureRequest.context
Definition

An encounter or episode of care that provides additional information about the healthcare context in which this request is made.

Control0..1
TypeReference(Encounter | EpisodeOfCare)
Alternate Namesencounter
Summarytrue
ProcedureRequest.occurrence[x]
Definition

The date/time at which the diagnostic testing should occur.

Control0..1
TypedateTime|Period|Timing
[x] NoteSee Choice of Data Types for further information about how to use [x]
Alternate Namesschedule
Summarytrue
ProcedureRequest.asNeeded[x]
Definition

If a CodeableConcept is present, it indicates the pre-condition for performing the procedure. For example "pain", "on flare-up", etc.

Control0..1
Terminology BindingSNOMED CT Medication As Needed Reason Codes (Example)
Typeboolean|CodeableConcept
[x] NoteSee Choice of Data Types for further information about how to use [x]
Summarytrue
ProcedureRequest.authoredOn
Definition

When the request transitioned to being actionable.

Control0..1
TypedateTime
Alternate NamesorderedOn
Summarytrue
ProcedureRequest.requester
Definition

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

Control0..1
Alternate Namesauthor; orderer
Summarytrue
Comments

This not the dispatcher, but rather who is the authorizer.

ProcedureRequest.requester.agent
Definition

The device, practitioner or organization who initiated the request.

Control1..1
TypeReference(Device | Practitioner | Organization)
Summarytrue
ProcedureRequest.requester.onBehalfOf
Definition

The organization the device or practitioner was acting on behalf of.

Control0..1
TypeReference(Organization)
Requirements

Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request.

Summarytrue
ProcedureRequest.performerType
Definition

Desired type of performer for doing the diagnostic testing.

Control0..1
Terminology BindingParticipant Roles (Example)
TypeCodeableConcept
Summarytrue
Comments

this is a role, not a participation type. I.e. does not describe the task, but describes the capacity. For example, “compounding pharmacy” or “psychiatrist” or “internal referral”.

ProcedureRequest.performer
Definition

The desired perfomer for doing the diagnostic testing. For example, the surgeon, dermatopathologist, endoscopist, etc.

Control0..1
TypeReference(Practitioner | Organization | Patient | Device | RelatedPerson | HealthcareService)
Summarytrue
Comments

If needed, use an extension for listing alternative performers and/or roles and/or preference.

ProcedureRequest.reasonCode
Definition

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.

Control0..*
Terminology BindingProcedure Reason Codes (Example)
TypeCodeableConcept
Summarytrue
Comments

This may be used to decide how the diagnostic investigation will be performed, or even if it will be performed at all. Use CodeableConcept text element if the data is free (uncoded) text as shown in the CT Scan example.

ProcedureRequest.reasonReference
Definition

Indicates another resource that provides a justification for why this diagnostic investigation is being requested. May relate to the resources referred to in supportingInformation.

Control0..*
TypeReference(Condition | Observation)
Summarytrue
Comments

This may be used to decide how the diagnostic investigation will be performed, or even if it will be performed at all. Use CodeableConcept text element if the data is free (uncoded) text as shown in the CT Scan example.

ProcedureRequest.supportingInfo
Definition

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.

Control0..*
TypeReference(Any)
Alternate NamesAsk at order entry question; AOE
ProcedureRequest.specimen
Definition

One or more specimens that the laboratory procedure will use.

Control0..*
TypeReference(Specimen)
Summarytrue
Comments

Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, If the request is entered first with an unknown specimen, The Specimen resource references to the ProcedureRequest.

ProcedureRequest.bodySite
Definition

Anatomic location where the procedure should be performed. This is the target site.

Control0..*
Terminology BindingSNOMED CT Body Structures (Example)
TypeCodeableConcept
Requirements

Knowing where the procedure is performed is important for tracking if multiple sites are possible.

Alternate Nameslocation
Summarytrue
Comments

Only used if not implicit in the code found in ProcedureRequest.type. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension procedurerequest-targetBodySite.

ProcedureRequest.note
Definition

Any other notes and comments made about the service request. For example, letting provider know that "patient hates needles" or other provider instructions.

Control0..*
TypeAnnotation
ProcedureRequest.relevantHistory
Definition

Key events in the history of the request.

Control0..*
TypeReference(Provenance)
Comments

This may 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.