Schema: ProcedureRequest

Introduction

The headings below list the elements of the ProcedureRequest resource and describe how to populate and consume them.

Tip: You’ll find it helpful to read it in conjunction with the underlying ProcedureRequest profile definition.

ProcedureRequest Resource Elements

id

The logical identifier of the DiagnosticReport resource.

meta.profile

The DiagnosticReport profile URL.

Fixed value https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-DiagnostocReport-1

identifier

This will be populated with a globally unique and persistent identifier (that is, it doesn’t change between requests and therefore stored with the source data).

status

The status of the ProcedureRequest. Set value of active.

This is mandatory in the base FHIR resource. However as this resource in our model is not being used as a request but to hold data that would have been in a request submitted in a different format we have chosen to use the default value stated.

intent

The status of the ProcedureRequest. Set value of order.

This is mandatory in the base FHIR resource.

code

The tests requested by the requesting HCP. Where no code is available then Medicus will populate the code.text field with the text ‘No code available’.

subject

A reference to the Patient that the ProcedureRequest is about.

performer

Reference to the resource for the practitioner or organization that is requested to perform this request the ProcedureRequest.

requester

Reference to the resource for the practitioner or organization that created the ProcedureRequest.

reasonCode

An explanation or justification for why this diagnostic investigation is being requested in coded or textual form.

reasonReference

A reference to any conditions the patient has that are supplied by the requesting HCP due to their relevance to the test request.

note

A human readable explanation from the requesting HCP containing an explanation on why the test has been requested and any contextual information they considered relevant.