DFT - The specification is currently in development and subject to change. For a full list of available versions, see the Directory of published versions

UC-03: Referral to a Central Intake

Scenario: Requester Health Care Provider sends a referral request to a Central Intake, which forwards to most appropriate downstream Performer Health Care Provider

Please see:

• UC-03: Referral to Central Intake for the full description of the use case corresponding to the diagrams, and
• Single Entry Models for additional information about why there is multiple service requests (SRs) referenced in these flows.

Related Route/Split/Chain Content:

1. For details on Routing, Splitting, and Chaining system requirements, see the L3: Advanced Workflows and Business Rules pages.
2. For details on Routing, Splitting, and Chaining within messaging workflows, see the messaging page.

The section below provides guidance on how to read the sequence diagrams:

• The green swim lane provides a simplified view of the actors and transactions that are not explicitly illustrated on the diagram. The Foundational Profiles defined in the Reference Architecture are referenced as required. See the Reference Architecture Release Information page for more information about released versions. These integration profiles are informative options to satisfy pre-requisite business requirements suggested for the particular use case.
• The blue swim lanes group sequence of processes (along with their required actors and transactions) that are needed to occur to satisfy this particular use case. These are to be read from left to right and top to bottom. Note that the sequence diagrams are not explicitly calling out whether the processes are synchronous or asynchronous, and in certain cases it may depend on the specific implementations.
• The actors and corresponding transactions in red, represent the technical actors and transactions that are the bases to achieve interoperability between the different clinical systems.
• For more information on core IHE Profiles and specific Canadian implementation guidance, refer to the Reference Architecture.

Routing and Splitting Referral Requests

Routing: The referral request is forwarded to a new downstream service from Central Intake.

Splitting: The referral request gets split into multiple parts/services that logically make up the original request at Central Intake, to be fulfilled by different downstream services.

Chaining Referral Requests

Chaining: A new, distinct referral is created to a downstream service based on the original referral after a service is performed at central intake.