This page is part of the FHIR Specification (v1.1.0: STU 3 Ballot 1). 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
This is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.

Detailed Descriptions for the elements in the ReferralRequest resource.
| ReferralRequest | |
| Definition | Used to record and send details about a request for referral service or transfer of a patient to the care of another provider or provider organization. |
| Control | 1..1 |
| Alternate Names | ReferralRequest TransferOfCare Request |
| ReferralRequest.status | |
| Definition | The workflow status of the referral or transfer of care request. |
| Control | 1..1 |
| Binding | ReferralStatus: The status of the referral. (Required) |
| Type | code |
| Is Modifier | true |
| Summary | true |
| ReferralRequest.identifier | |
| Definition | Business identifier that uniquely identifies the referral/care transfer request instance. |
| Note | This is a business identifer, not a resource identifier (see discussion) |
| Control | 0..* |
| Type | Identifier |
| ReferralRequest.date | |
| Definition | Date/DateTime of creation for draft requests and date of activation for active requests. |
| Control | 0..1 |
| Type | dateTime |
| Summary | true |
| ReferralRequest.type | |
| Definition | An indication of the type of referral (or where applicable the type of transfer of care) request. |
| Control | 0..1 |
| Binding | ReferralType: Codes for types of referral; e.g. consult, transfer, temporary transfer. |
| Type | CodeableConcept |
| Summary | true |
| Comments | Examples of referral type: - consultation; second opinion; third opinion - Assume management - Request for procedure(s) HL7 v2.8 Example - Table 0336: S = second opinion p = patient preference o = provider ordered w = work load. |
| ReferralRequest.specialty | |
| Definition | Indication of the clinical domain or discipline to which the referral or transfer of care request is sent. For example: Cardiology Gastroenterology Diabetology. |
| Control | 0..1 |
| Binding | PractitionerSpecialty: Codes indicating the types of capability the referred to service provider must have. (Example) |
| Type | CodeableConcept |
| ReferralRequest.priority | |
| Definition | An indication of the urgency of referral (or where applicable the type of transfer of care) request. |
| Control | 0..1 |
| Binding | DiagnosticOrderPriority: Codes indicating the relative priority of the referral. (Example) |
| Type | CodeableConcept |
| Summary | true |
| ReferralRequest.patient | |
| Definition | The patient who is the subject of a referral or transfer of care request. |
| Control | 0..1 |
| Type | Reference(Patient) |
| Summary | true |
| Comments | Referral of family, group or community is to be catered for by profiles. |
| ReferralRequest.requester | |
| Definition | The healthcare provider or provider organization who/which initiated the referral/transfer of care request. Can also be Patient (a self referral). |
| Control | 0..1 |
| Type | Reference(Practitioner | Organization | Patient) |
| Summary | true |
| ReferralRequest.recipient | |
| Definition | The healthcare provider(s) or provider organization(s) who/which is to receive the referral/transfer of care request. |
| Control | 0..* |
| Type | Reference(Practitioner | Organization) |
| Summary | true |
| Comments | There will be a primary receiver. But the request can be received by any number of "copied to" providers or organizations. |
| ReferralRequest.encounter | |
| Definition | The encounter at which the request for referral or transfer of care is initiated. |
| Control | 0..1 |
| Type | Reference(Encounter) |
| ReferralRequest.dateSent | |
| Definition | Date/DateTime the request for referral or transfer of care is sent by the author. |
| Control | 0..1 |
| Type | dateTime |
| Summary | true |
| ReferralRequest.reason | |
| Definition | Description of clinical condition indicating why referral/transfer of care is requested. For example: Pathological Anomalies, Disabled (physical or mental), Behavioral Management. |
| Control | 0..1 |
| Binding | ReferralReason: Codes indicating why the referral is being requested. |
| Type | CodeableConcept |
| Summary | true |
| ReferralRequest.description | |
| Definition | The reason element gives a short description of why the referral is being made, the description expands on this to support a more complete clinical summary. |
| Control | 0..1 |
| Type | string |
| To Do | This would be a good candidate for a 'markdown' data type. |
| ReferralRequest.serviceRequested | |
| Definition | The service(s) that is/are requested to be provided to the patient. For example: cardiac pacemaker insertion. |
| Control | 0..* |
| Binding | Practice Setting Code Value Set: Codes indicating the types of services that might be requested as part of a referral. (Example) |
| Type | CodeableConcept |
| Summary | true |
| ReferralRequest.supportingInformation | |
| Definition | Any additional (administrative, financial or clinical) information required to support request for referral or transfer of care. For example: Presenting problems/chief complaints Medical History Family History Alerts Allergy/Intolerance and Adverse Reactions Medications Observations/Assessments (may include cognitive and fundtional assessments) Diagnostic Reports Care Plan. |
| Control | 0..* |
| Type | Reference(Any) |
| Summary | true |
| ReferralRequest.fulfillmentTime | |
| Definition | The period of time within which the services identified in the referral/transfer of care is specified or required to occur. |
| Control | 0..1 |
| Type | Period |
| Requirements | Use cases: (1) to indicate that the requested service is not to happen before a specified date, and saving the start date in Period.start; (2) to indicate that the requested service must happen before a specified date, and saving the end date in Period.end; (3) to indicate that the requested service must happen during the specified dates ("start" and "end" values). |
| Alternate Names | EffectiveTime |
| Summary | true |