Procedure Request

Examples & Testing

The Procedure Request resource represents information about a request for a diagnostic test, treatment, or other procedure to be performed.

See the FHIR documentation for more information about Procedure Request resources.

Procedure Request resources support the following interactions.

When searching for Procedure Request resources, the following search parameters are supported.

Name	Type	Prefixes Modifiers	Can be Chained?	Description
_id	Token			Resource id.
_lastUpdated	Date	lt le gt ge		When the resource last changed.
_source	Uri	:missing		Where the resource comes from.
authored	Date	ne lt le gt ge sa eb ap :missing		Date request signed.
body-site	Token	:not :in :notin :missing		Where procedure is going to be done.
code	Token	:not :in :notin :missing		What is being requested/ordered.
context	Reference	:missing	yes	Encounter or Episode during which request was created.
encounter	Reference	:missing	yes	An encounter in which this request is made.
identifier	Token	:missing		Identifiers assigned to this order.
intent	Token	:missing		proposal \| plan \| order +.
occurrence	Date	ne lt le gt ge sa eb ap :missing		When procedure should occur.
patient	Reference	:missing	yes	Search by subject - a patient.
priority	Token	:missing		routine \| urgent \| asap \| stat.
provenance-agent	Reference	:missing	yes	Search by provenance, specified by its author (aka originator) Organization.
requester	Reference	:missing	yes	Individual making the request.
status	Token	:missing		draft \| active \| suspended \| completed \| entered-in-error \| cancelled.
subject	Reference	:missing	yes	Search by subject.

When searching Procedure Request resources, it is possible to sort the returned values by the following search parameters.

Only one sort parameter may be specified.

When searching Procedure Request resources, it is possible to include the resources referenced by the following field names.