Retrieve clinical information

Retrieve referral request (versioned) (A005, FHIR STU3)

Overview

Use this endpoint to retrieve a specific version of ReferralRequest.

Supported security patterns

  • Application-restricted access
  • Healthcare worker, user-restricted access

Pre-requisites

The pre-requisites for this endpoint are the same as for endpoint [[HYPERLINK_A005]].

Note: e-RS only supports the retrieval of the most recent version of ReferralRequest. You cannot retrieve earlier versions.

Important notes

Attachment availability

In order to retrieve an attachment using the [[HYPERLINK_A042]] (or deprecated [[HYPERLINK_A006]]) endpoint, the attachment must be available for download. Attachments are only made available once an uploaded file has been validated and successfully malware scanned. A request to retrieve an attachment that is not available for download will result in an error being returned. See [[HYPERLINK_A042]] for more information.

The availability status of an attachment can be retrieved via any endpoint that returns an eRS-AvailabilityStatus-1 code in the success response, including [[HYPERLINK_A005]]. The eRS-AvailabilityStatus-1 code can return one of four possible values, as detailed below.

eRS-AvailabilityStatus-1 codeDescription / Guidance
AVAILABLEThe file is available for download.
PENDINGThe file is being scanned and cannot be retrieved. Wait at least 5 minutes before checking its availability again
THREATS FOUNDThe file has been quarantined after detecting a threat and cannot be retrieved.<br> Contact the organisation that uploaded the file to resolve the issue and get the information you need. Use the extensions returned via this endpoint: Extension-eRS-AttachedBy-1 and Extension-eRS-AttachedByOrganisation-1.
VALIDATION_FAILEDThe file has failed validation and cannot be retrieved.<br> Contact the organisation that uploaded the file to resolve the issue and get the information you need. Use the extensions returned via this endpoint: Extension-eRS-AttachedBy-1 and Extension-eRS-AttachedByOrganisation-1. Validation can fail because the: <ul><li>content type of the file is not supported</li><li>content type of the file does not correlate with the file extension</li><li>file provided is too large and is not supported by e-RS.</li></ul>

Receiving an e-Referral Pathway Start Date

The e-Referral Pathway Start Date is a derived value of when the Referral To Treatment (RTT) clock starts. Find out how e-RS derives the pathway start date [[HYPERLINK_PATHWAY_START]].

If a referral was created with an alternate pathway start date, then this will be available in the referral request response.

Service providers must always ensure the correct start date is recorded in line with [[HYPERLINK_RTT_RULES]].

Use case

See [[HYPERLINK_A005]].

Related endpoints

See [[HYPERLINK_A005]].

Sandbox test scenarios

You can test the following scenarios in our sandbox environment

ScenarioRequest
Unbooked ReferralRequestubrn=000000070000, version=5
ReferralRequest booked to directly-bookable serviceubrn=000000070001, version=5
ReferralRequest booked to indirectly-bookable serviceubrn=000000070002, version=5
ReferralRequest deferred to service provider for bookingubrn=000000070003, version=5
ReferralRequest that was converted from an Advice and Guidance Requestubrn=000000070004, version=5
ReferralRequest with related ReferralRequestubrn=000000070005, version=5
ReferralRequest with additional requirements listedubrn=000000070011, version=5
ReferralRequest with attachments unavailable to downloadubrn=000000070012, version=5
get/STU3/ReferralRequest/{ubrn}/_history/{version}

Request

  • Base URL
    https://sandbox.api.service.nhs.uk/referrals/FHIR
  • URL
    https://sandbox.api.service.nhs.uk/referrals/FHIR/STU3/ReferralRequest/{ubrn}/_history/{version}
  • Auth
    HTTP bearer

Parameters

#/paths/~1STU3~1ReferralRequest~1%7Bubrn%7D/get/parameters/0 (unresolved $ref)
#/paths/~1STU3~1Appointment~1%7Bid%7D~1_history~1%7Bversion%7D/get/parameters/6 (unresolved $ref)
#/paths/~1STU3~1Task/get/parameters/0 (unresolved $ref)
#/paths/~1STU3~1Communication/get/parameters/3 (unresolved $ref)
#/paths/~1STU3~1Communication/get/parameters/4 (unresolved $ref)
#/paths/~1STU3~1Communication/get/parameters/5 (unresolved $ref)
#/paths/~1STU3~1Task/get/parameters/4 (unresolved $ref)

Response

(unresolved $ref)

Changes

No recorded changes to this operation across all 1 revision of this API.