STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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

9.7 Resource ReferralRequest - Content

Patient Care Work GroupMaturity Level: 1Compartments: Patient, Practitioner

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.

9.7.1 Scope and Usage

This resource is used to share relevant information required to support a referral request or a transfer of care request from one practitioner or organization to another. It is intended for use when a patient is required to be referred to another provider for a consultation/second opinion and/or for short term or longer term management of one or more health issues or problems.

Examples include:

  • Request for a consult from a specialist
  • Referral for support from community services
  • District nursing services referral
  • Request for Aged care placement assessment
  • Request for a pharmacist medication review
  • Referral for physiotherapy or occupational therapy

ReferralRequest is also intended for use when there is a complete and more permanent transfer of care responsibility from one practitioner/organization to another (for example, as in the case of requesting the transfer of care for a patient from an acute care setting to rehabilitation, aged care, or a skilled nursing facility).

9.7.2 Boundaries and Relationships

ReferralRequest is closely related to other types of "request" resources, particularly DiagnosticRequest and ProcedureRequest. In fact, for some services, it may be appropriate to use any one of these resources to request that the service be performed. Which one is used may be driven by organizational practice and by context. When it is unclear which to use, the following principles may be helpful:

  • ProcedureRequest or DiagnosticRequest are typically used when the requesting clinician has and wishes to exercise the authority (and expertise) to decide exactly what action will be done.
  • A ReferralRequest is used when the requesting practitioner is seeking another practitioner or organization to use their own expertise and/or authority to determine the specific action to take.
  • Whether an activity is deemed to be a procedure or only a diagnostic request is typically driven by how invasive the diagnostic process is. More invasive processes are typically represented as procedures, though the dividing line may vary by organization.

Irrespective of the guidance above, systems should be prepared for some degree of overlap between these resources and should be prepared to execute searches against multiple resources in cases where differentiation cannot be guaranteed. As well, in some workflows more than one type of resource or even all three might exist; E.g., upon receiving a ReferralRequest a practitioner might initiate a DiagnosticRequest. The diagnostic service might then initiate a ProcedureRequest.

A "referral" is often thought of as a document that contains a great deal of information about the patient being referred. This resource does not actually contain the clinical background information for the patient. Instead, it supports references to the numerous other resources that define this information. For example, Condition, Family History, Allergy/Intolerance, Alerts, Medication, Diagnostic Reports, etc. Alternatively, some systems may choose to bundle up a ReferralRequest and this referenced information into a Document for delivery to the recipient. However, REST, Messaging and Services are also valid architectures for managing referrals and may be more appropriate where active workflow management is needed.

The details of the type of care desired as part of a referral may be conveyed using any of the "request" or "order" resources, likely with a status of "proposed". The CarePlan resource can be used to describe more sophisticated requests for combinations of services. Likewise, ReferralRequest may be referenced as part of a CarePlan.

A ReferralRequest may be targeted (identifying a specific Practitioner or Organization to perform the requested care) or untargeted (merely identifying the type of care desired). The Task resource may be used to help manage such workflows.

A ReferralRequest might be fulfilled by a DiagnosticReport, Encounter, Procedure, or other assessment-related resource.

A ReferralRequest should not be confused with an Appointment, as appointments are intended for booking/scheduling purposes.

PLANNED CHANGE:

ReferralRequest is one of the Request resources in the FHIR Workflow specification. As such, it is expected to be adjusted to align with the Request workflow pattern which will involve adding a number of additional data elements and potentially renaming a few elements. Any concerns about performing such alignment are welcome as ballot comments and/or tracker items.

This resource is referenced by CarePlan, Claim, ClinicalImpression, DiagnosticReport, Encounter, EpisodeOfCare, ExplanationOfBenefit, ImagingStudy, MedicationRequest, Procedure and QuestionnaireResponse

9.7.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. ReferralRequest DomainResourceA request for referral or transfer of care
... identifier 0..*IdentifierBusiness identifier
... basedOn 0..*Reference(ReferralRequest | CarePlan | DiagnosticRequest | ProcedureRequest)Request fulfilled by this request
... parent Σ0..1IdentifierComposite request this is part of
... status ?!Σ1..1codedraft | active | cancelled | completed | entered-in-error
ReferralStatus (Required)
... category ?!Σ1..1codeproposal | plan | request
ReferralCategory (Required)
... type Σ0..1CodeableConceptReferral/Transition of care request type
... priority Σ0..1CodeableConceptUrgency of referral / transfer of care request
RequestPriority (Example)
... patient Σ0..1Reference(Patient)Patient referred to care or transfer
... context 0..1Reference(Encounter | EpisodeOfCare)Originating encounter
... fulfillmentTime Σ0..1PeriodRequested service(s) fulfillment time
... authored Σ0..1dateTimeDate of creation/activation
... requester Σ0..1Reference(Practitioner | Organization | Patient)Requester of referral / transfer of care
... specialty 0..1CodeableConceptThe clinical specialty (discipline) that the referral is requested for
PractitionerSpecialty (Example)
... recipient Σ0..*Reference(Practitioner | Organization)Receiver of referral / transfer of care request
... reason Σ0..1CodeableConceptReason for referral / transfer of care request
... description 0..1stringA textual description of the referral
... serviceRequested Σ0..*CodeableConceptActions requested as part of the referral
Practice Setting Code Value Set (Example)
... supportingInformation Σ0..*Reference(Any)Additonal information to support referral or transfer of care request

doco Documentation for this format

UML Diagram (Legend)

ReferralRequest (DomainResource)Business identifier that uniquely identifies the referral/care transfer request instanceidentifier : Identifier [0..*]Indicates any plans, proposals or orders that this request is intended to satisfy - in whole or in partbasedOn : Reference [0..*] « ReferralRequest|CarePlan| DiagnosticRequest|ProcedureRequest »The business identifier of the logical "grouping" request/order that this referral is a part ofparent : Identifier [0..1]The status of the authorization/intention reflected by the referral request record (this element modifies the meaning of other elements)status : code [1..1] « The status of the referral. (Strength=Required)ReferralStatus! »Distinguishes the "level" of authorization/demand implicit in this request (this element modifies the meaning of other elements)category : code [1..1] « Identifies the degree of intention/authorization associated with the request (Strength=Required)ReferralCategory! »An indication of the type of referral (or where applicable the type of transfer of care) requesttype : CodeableConcept [0..1]An indication of the urgency of referral (or where applicable the type of transfer of care) requestpriority : CodeableConcept [0..1] « Codes indicating the relative priority of the referral. (Strength=Example)RequestPriority?? »The patient who is the subject of a referral or transfer of care requestpatient : Reference [0..1] « Patient »The encounter at which the request for referral or transfer of care is initiatedcontext : Reference [0..1] « Encounter|EpisodeOfCare »The period of time within which the services identified in the referral/transfer of care is specified or required to occurfulfillmentTime : Period [0..1]Date/DateTime of creation for draft requests and date of activation for active requestsauthored : dateTime [0..1]The healthcare provider or provider organization who/which initiated the referral/transfer of care request. Can also be Patient (a self referral)requester : Reference [0..1] « Practitioner|Organization|Patient »Indication of the clinical domain or discipline to which the referral or transfer of care request is sent. For example: Cardiology Gastroenterology Diabetologyspecialty : CodeableConcept [0..1] « Codes indicating the types of capability the referred to service provider must have. (Strength=Example)PractitionerSpecialty?? »The healthcare provider(s) or provider organization(s) who/which is to receive the referral/transfer of care requestrecipient : Reference [0..*] « Practitioner|Organization »Description of clinical condition indicating why referral/transfer of care is requested. For example: Pathological Anomalies, Disabled (physical or mental), Behavioral Managementreason : CodeableConcept [0..1]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 summarydescription : string [0..1]The service(s) that is/are requested to be provided to the patient. For example: cardiac pacemaker insertionserviceRequested : CodeableConcept [0..*] « Codes indicating the types of services that might be requested as part of a referral. (Strength=Example)Practice Setting Code Value S...?? »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 PlansupportingInformation : Reference [0..*] « Any »

XML Template

<ReferralRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Business identifier --></identifier>
 <basedOn><!-- 0..* Reference(ReferralRequest|CarePlan|DiagnosticRequest|
   ProcedureRequest) Request fulfilled by this request --></basedOn>
 <parent><!-- 0..1 Identifier Composite request this is part of --></parent>
 <status value="[code]"/><!-- 1..1 draft | active | cancelled | completed | entered-in-error -->
 <category value="[code]"/><!-- 1..1 proposal | plan | request -->
 <type><!-- 0..1 CodeableConcept Referral/Transition of care request type --></type>
 <priority><!-- 0..1 CodeableConcept Urgency of referral / transfer of care request --></priority>
 <patient><!-- 0..1 Reference(Patient) Patient referred to care or transfer --></patient>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Originating encounter --></context>
 <fulfillmentTime><!-- 0..1 Period Requested service(s) fulfillment time --></fulfillmentTime>
 <authored value="[dateTime]"/><!-- 0..1 Date of creation/activation -->
 <requester><!-- 0..1 Reference(Practitioner|Organization|Patient) Requester of referral / transfer of care --></requester>
 <specialty><!-- 0..1 CodeableConcept The clinical specialty (discipline) that the referral is requested for --></specialty>
 <recipient><!-- 0..* Reference(Practitioner|Organization) Receiver of referral / transfer of care request --></recipient>
 <reason><!-- 0..1 CodeableConcept Reason for referral / transfer of care request --></reason>
 <description value="[string]"/><!-- 0..1 A textual description of the referral -->
 <serviceRequested><!-- 0..* CodeableConcept Actions requested as part of the referral --></serviceRequested>
 <supportingInformation><!-- 0..* Reference(Any) Additonal information to support referral or transfer of care request --></supportingInformation>
</ReferralRequest>

JSON Template

{doco
  "resourceType" : "ReferralRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Business identifier
  "basedOn" : [{ Reference(ReferralRequest|CarePlan|DiagnosticRequest|
   ProcedureRequest) }], // Request fulfilled by this request
  "parent" : { Identifier }, // Composite request this is part of
  "status" : "<code>", // R!  draft | active | cancelled | completed | entered-in-error
  "category" : "<code>", // R!  proposal | plan | request
  "type" : { CodeableConcept }, // Referral/Transition of care request type
  "priority" : { CodeableConcept }, // Urgency of referral / transfer of care request
  "patient" : { Reference(Patient) }, // Patient referred to care or transfer
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Originating encounter
  "fulfillmentTime" : { Period }, // Requested service(s) fulfillment time
  "authored" : "<dateTime>", // Date of creation/activation
  "requester" : { Reference(Practitioner|Organization|Patient) }, // Requester of referral / transfer of care
  "specialty" : { CodeableConcept }, // The clinical specialty (discipline) that the referral is requested for
  "recipient" : [{ Reference(Practitioner|Organization) }], // Receiver of referral / transfer of care request
  "reason" : { CodeableConcept }, // Reason for referral / transfer of care request
  "description" : "<string>", // A textual description of the referral
  "serviceRequested" : [{ CodeableConcept }], // Actions requested as part of the referral
  "supportingInformation" : [{ Reference(Any) }] // Additonal information to support referral or transfer of care request
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:ReferralRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:ReferralRequest.identifier [ Identifier ], ... ; # 0..* Business identifier
  fhir:ReferralRequest.basedOn [ Reference(ReferralRequest|CarePlan|DiagnosticRequest|ProcedureRequest) ], ... ; # 0..* Request fulfilled by this request
  fhir:ReferralRequest.parent [ Identifier ]; # 0..1 Composite request this is part of
  fhir:ReferralRequest.status [ code ]; # 1..1 draft | active | cancelled | completed | entered-in-error
  fhir:ReferralRequest.category [ code ]; # 1..1 proposal | plan | request
  fhir:ReferralRequest.type [ CodeableConcept ]; # 0..1 Referral/Transition of care request type
  fhir:ReferralRequest.priority [ CodeableConcept ]; # 0..1 Urgency of referral / transfer of care request
  fhir:ReferralRequest.patient [ Reference(Patient) ]; # 0..1 Patient referred to care or transfer
  fhir:ReferralRequest.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Originating encounter
  fhir:ReferralRequest.fulfillmentTime [ Period ]; # 0..1 Requested service(s) fulfillment time
  fhir:ReferralRequest.authored [ dateTime ]; # 0..1 Date of creation/activation
  fhir:ReferralRequest.requester [ Reference(Practitioner|Organization|Patient) ]; # 0..1 Requester of referral / transfer of care
  fhir:ReferralRequest.specialty [ CodeableConcept ]; # 0..1 The clinical specialty (discipline) that the referral is requested for
  fhir:ReferralRequest.recipient [ Reference(Practitioner|Organization) ], ... ; # 0..* Receiver of referral / transfer of care request
  fhir:ReferralRequest.reason [ CodeableConcept ]; # 0..1 Reason for referral / transfer of care request
  fhir:ReferralRequest.description [ string ]; # 0..1 A textual description of the referral
  fhir:ReferralRequest.serviceRequested [ CodeableConcept ], ... ; # 0..* Actions requested as part of the referral
  fhir:ReferralRequest.supportingInformation [ Reference(Any) ], ... ; # 0..* Additonal information to support referral or transfer of care request
]

Changes since DSTU2

ReferralRequest
ReferralRequest.basedOn added Element
ReferralRequest.parent added Element
ReferralRequest.category added Element
ReferralRequest.context Renamed from encounter to context
Add Reference(EpisodeOfCare)
ReferralRequest.authored Renamed from date to authored
ReferralRequest.dateSent deleted

See the Full Difference for further information

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. ReferralRequest DomainResourceA request for referral or transfer of care
... identifier 0..*IdentifierBusiness identifier
... basedOn 0..*Reference(ReferralRequest | CarePlan | DiagnosticRequest | ProcedureRequest)Request fulfilled by this request
... parent Σ0..1IdentifierComposite request this is part of
... status ?!Σ1..1codedraft | active | cancelled | completed | entered-in-error
ReferralStatus (Required)
... category ?!Σ1..1codeproposal | plan | request
ReferralCategory (Required)
... type Σ0..1CodeableConceptReferral/Transition of care request type
... priority Σ0..1CodeableConceptUrgency of referral / transfer of care request
RequestPriority (Example)
... patient Σ0..1Reference(Patient)Patient referred to care or transfer
... context 0..1Reference(Encounter | EpisodeOfCare)Originating encounter
... fulfillmentTime Σ0..1PeriodRequested service(s) fulfillment time
... authored Σ0..1dateTimeDate of creation/activation
... requester Σ0..1Reference(Practitioner | Organization | Patient)Requester of referral / transfer of care
... specialty 0..1CodeableConceptThe clinical specialty (discipline) that the referral is requested for
PractitionerSpecialty (Example)
... recipient Σ0..*Reference(Practitioner | Organization)Receiver of referral / transfer of care request
... reason Σ0..1CodeableConceptReason for referral / transfer of care request
... description 0..1stringA textual description of the referral
... serviceRequested Σ0..*CodeableConceptActions requested as part of the referral
Practice Setting Code Value Set (Example)
... supportingInformation Σ0..*Reference(Any)Additonal information to support referral or transfer of care request

doco Documentation for this format

UML Diagram (Legend)

ReferralRequest (DomainResource)Business identifier that uniquely identifies the referral/care transfer request instanceidentifier : Identifier [0..*]Indicates any plans, proposals or orders that this request is intended to satisfy - in whole or in partbasedOn : Reference [0..*] « ReferralRequest|CarePlan| DiagnosticRequest|ProcedureRequest »The business identifier of the logical "grouping" request/order that this referral is a part ofparent : Identifier [0..1]The status of the authorization/intention reflected by the referral request record (this element modifies the meaning of other elements)status : code [1..1] « The status of the referral. (Strength=Required)ReferralStatus! »Distinguishes the "level" of authorization/demand implicit in this request (this element modifies the meaning of other elements)category : code [1..1] « Identifies the degree of intention/authorization associated with the request (Strength=Required)ReferralCategory! »An indication of the type of referral (or where applicable the type of transfer of care) requesttype : CodeableConcept [0..1]An indication of the urgency of referral (or where applicable the type of transfer of care) requestpriority : CodeableConcept [0..1] « Codes indicating the relative priority of the referral. (Strength=Example)RequestPriority?? »The patient who is the subject of a referral or transfer of care requestpatient : Reference [0..1] « Patient »The encounter at which the request for referral or transfer of care is initiatedcontext : Reference [0..1] « Encounter|EpisodeOfCare »The period of time within which the services identified in the referral/transfer of care is specified or required to occurfulfillmentTime : Period [0..1]Date/DateTime of creation for draft requests and date of activation for active requestsauthored : dateTime [0..1]The healthcare provider or provider organization who/which initiated the referral/transfer of care request. Can also be Patient (a self referral)requester : Reference [0..1] « Practitioner|Organization|Patient »Indication of the clinical domain or discipline to which the referral or transfer of care request is sent. For example: Cardiology Gastroenterology Diabetologyspecialty : CodeableConcept [0..1] « Codes indicating the types of capability the referred to service provider must have. (Strength=Example)PractitionerSpecialty?? »The healthcare provider(s) or provider organization(s) who/which is to receive the referral/transfer of care requestrecipient : Reference [0..*] « Practitioner|Organization »Description of clinical condition indicating why referral/transfer of care is requested. For example: Pathological Anomalies, Disabled (physical or mental), Behavioral Managementreason : CodeableConcept [0..1]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 summarydescription : string [0..1]The service(s) that is/are requested to be provided to the patient. For example: cardiac pacemaker insertionserviceRequested : CodeableConcept [0..*] « Codes indicating the types of services that might be requested as part of a referral. (Strength=Example)Practice Setting Code Value S...?? »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 PlansupportingInformation : Reference [0..*] « Any »

XML Template

<ReferralRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Business identifier --></identifier>
 <basedOn><!-- 0..* Reference(ReferralRequest|CarePlan|DiagnosticRequest|
   ProcedureRequest) Request fulfilled by this request --></basedOn>
 <parent><!-- 0..1 Identifier Composite request this is part of --></parent>
 <status value="[code]"/><!-- 1..1 draft | active | cancelled | completed | entered-in-error -->
 <category value="[code]"/><!-- 1..1 proposal | plan | request -->
 <type><!-- 0..1 CodeableConcept Referral/Transition of care request type --></type>
 <priority><!-- 0..1 CodeableConcept Urgency of referral / transfer of care request --></priority>
 <patient><!-- 0..1 Reference(Patient) Patient referred to care or transfer --></patient>
 <context><!-- 0..1 Reference(Encounter|EpisodeOfCare) Originating encounter --></context>
 <fulfillmentTime><!-- 0..1 Period Requested service(s) fulfillment time --></fulfillmentTime>
 <authored value="[dateTime]"/><!-- 0..1 Date of creation/activation -->
 <requester><!-- 0..1 Reference(Practitioner|Organization|Patient) Requester of referral / transfer of care --></requester>
 <specialty><!-- 0..1 CodeableConcept The clinical specialty (discipline) that the referral is requested for --></specialty>
 <recipient><!-- 0..* Reference(Practitioner|Organization) Receiver of referral / transfer of care request --></recipient>
 <reason><!-- 0..1 CodeableConcept Reason for referral / transfer of care request --></reason>
 <description value="[string]"/><!-- 0..1 A textual description of the referral -->
 <serviceRequested><!-- 0..* CodeableConcept Actions requested as part of the referral --></serviceRequested>
 <supportingInformation><!-- 0..* Reference(Any) Additonal information to support referral or transfer of care request --></supportingInformation>
</ReferralRequest>

JSON Template

{doco
  "resourceType" : "ReferralRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Business identifier
  "basedOn" : [{ Reference(ReferralRequest|CarePlan|DiagnosticRequest|
   ProcedureRequest) }], // Request fulfilled by this request
  "parent" : { Identifier }, // Composite request this is part of
  "status" : "<code>", // R!  draft | active | cancelled | completed | entered-in-error
  "category" : "<code>", // R!  proposal | plan | request
  "type" : { CodeableConcept }, // Referral/Transition of care request type
  "priority" : { CodeableConcept }, // Urgency of referral / transfer of care request
  "patient" : { Reference(Patient) }, // Patient referred to care or transfer
  "context" : { Reference(Encounter|EpisodeOfCare) }, // Originating encounter
  "fulfillmentTime" : { Period }, // Requested service(s) fulfillment time
  "authored" : "<dateTime>", // Date of creation/activation
  "requester" : { Reference(Practitioner|Organization|Patient) }, // Requester of referral / transfer of care
  "specialty" : { CodeableConcept }, // The clinical specialty (discipline) that the referral is requested for
  "recipient" : [{ Reference(Practitioner|Organization) }], // Receiver of referral / transfer of care request
  "reason" : { CodeableConcept }, // Reason for referral / transfer of care request
  "description" : "<string>", // A textual description of the referral
  "serviceRequested" : [{ CodeableConcept }], // Actions requested as part of the referral
  "supportingInformation" : [{ Reference(Any) }] // Additonal information to support referral or transfer of care request
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:ReferralRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:ReferralRequest.identifier [ Identifier ], ... ; # 0..* Business identifier
  fhir:ReferralRequest.basedOn [ Reference(ReferralRequest|CarePlan|DiagnosticRequest|ProcedureRequest) ], ... ; # 0..* Request fulfilled by this request
  fhir:ReferralRequest.parent [ Identifier ]; # 0..1 Composite request this is part of
  fhir:ReferralRequest.status [ code ]; # 1..1 draft | active | cancelled | completed | entered-in-error
  fhir:ReferralRequest.category [ code ]; # 1..1 proposal | plan | request
  fhir:ReferralRequest.type [ CodeableConcept ]; # 0..1 Referral/Transition of care request type
  fhir:ReferralRequest.priority [ CodeableConcept ]; # 0..1 Urgency of referral / transfer of care request
  fhir:ReferralRequest.patient [ Reference(Patient) ]; # 0..1 Patient referred to care or transfer
  fhir:ReferralRequest.context [ Reference(Encounter|EpisodeOfCare) ]; # 0..1 Originating encounter
  fhir:ReferralRequest.fulfillmentTime [ Period ]; # 0..1 Requested service(s) fulfillment time
  fhir:ReferralRequest.authored [ dateTime ]; # 0..1 Date of creation/activation
  fhir:ReferralRequest.requester [ Reference(Practitioner|Organization|Patient) ]; # 0..1 Requester of referral / transfer of care
  fhir:ReferralRequest.specialty [ CodeableConcept ]; # 0..1 The clinical specialty (discipline) that the referral is requested for
  fhir:ReferralRequest.recipient [ Reference(Practitioner|Organization) ], ... ; # 0..* Receiver of referral / transfer of care request
  fhir:ReferralRequest.reason [ CodeableConcept ]; # 0..1 Reason for referral / transfer of care request
  fhir:ReferralRequest.description [ string ]; # 0..1 A textual description of the referral
  fhir:ReferralRequest.serviceRequested [ CodeableConcept ], ... ; # 0..* Actions requested as part of the referral
  fhir:ReferralRequest.supportingInformation [ Reference(Any) ], ... ; # 0..* Additonal information to support referral or transfer of care request
]

Changes since DSTU2

ReferralRequest
ReferralRequest.basedOn added Element
ReferralRequest.parent added Element
ReferralRequest.category added Element
ReferralRequest.context Renamed from encounter to context
Add Reference(EpisodeOfCare)
ReferralRequest.authored Renamed from date to authored
ReferralRequest.dateSent deleted

See the Full Difference for further information

 

Alternate definitions: Master Definition (XML, JSON), XML Schema/Schematron (for ) + JSON Schema, ShEx (for Turtle), JSON-LD (for RDF as JSON-LD),

9.7.3.1 Terminology Bindings

PathDefinitionTypeReference
ReferralRequest.status The status of the referral.RequiredReferralStatus
ReferralRequest.category Identifies the degree of intention/authorization associated with the requestRequiredReferralCategory
ReferralRequest.type Codes for types of referral; e.g. consult, transfer, temporary transfer.UnknownNo details provided yet
ReferralRequest.priority Codes indicating the relative priority of the referral.ExampleRequestPriority
ReferralRequest.specialty Codes indicating the types of capability the referred to service provider must have.ExamplePractitionerSpecialty
ReferralRequest.reason Codes indicating why the referral is being requested.UnknownNo details provided yet
ReferralRequest.serviceRequested Codes indicating the types of services that might be requested as part of a referral.ExamplePractice Setting Code Value Set

9.7.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPathsIn Common
basedonreferenceRequest being fulfilledReferralRequest.basedOn
(ReferralRequest, CarePlan, ProcedureRequest, DiagnosticRequest)
categorytokenProposal, plan or requestReferralRequest.category
contextreferencePart of encounter or episode of careReferralRequest.context
(EpisodeOfCare, Encounter)
datedateCreation or activation dateReferralRequest.authored18 Resources
parenttokenPart of common requestReferralRequest.parent
patientreferenceWho the referral is aboutReferralRequest.patient
(Patient)		31 Resources
prioritytokenThe priority assigned to the referralReferralRequest.priority
recipientreferenceThe person that the referral was sent toReferralRequest.recipient
(Practitioner, Organization)
requesterreferenceRequester of referral / transfer of careReferralRequest.requester
(Practitioner, Organization, Patient)
specialtytokenThe specialty that the referral is forReferralRequest.specialty
statustokenThe status of the referralReferralRequest.status
typetokenThe type of the referralReferralRequest.type6 Resources