## Overview

The following diagram forms the basis for all eReferral pathways in the architecture. The diagram shows the most complex flow possible, but components of it can be removed to build variations. 

Each column represents a system component, each box represents an action, the dotted arrow represent the direction of API calls, and the coloured star icon represents advanced business logic interactions that can be enabled by SMART on FHIR.

The following [video](https://www.screencast.com/t/8vTZX9OMU) (11min) provides an overview of the diagram:


![alt text][eReferral Diagram]

[eReferral Diagram]: https://content.screencast.com/users/jdoleweerd/folders/Snagit/media/9c0fe487-f934-4052-a181-d6dd0991f08f/2017-10-02_16-35-11.png "eReferral Process Flow Map"


The eReferral process contains 4 main flows
1. **Choose Destination** - The requester chooses the destination to send an eReferral
2. **Submit eReferral** - The requester submits the eReferral to its chosen destination
3. **Update Requester** - The provider sends an eReferral update to the requester
4. **Update Provider** - The requester sends an eReferral update tot he Provider.

Other data flows are are variations of one of these 4 data flows. e.g.,
* **1b**. Selecting a referral destination at a central intake services is the same as "1 - Choose Destination", but performed at a different location
* **2b**. Sending a referral package from an eReferral solution to an EMR is the same as "2 - Submit eReferral", except that it is relayed through the eReferral solutaion (where modifications may be made) before arriving at the EMR
* **2b / 2c**. Forwarding a referral on to another service that may be useful to a client from an eReferral solution or provider system is the same process as "2 - Submit eReferral". 
* **3** The processes of "Update Request", "Notify Requester of Outcome", "Request for update" are all the same processes with slightly different payload contents. 
* **1** When the requester sends a referral to a central intake destination to choose the final referral destination on their behalf, the requester is still choosing the destination *Central Intake*, after which Central Intake chooses a new destination to route the referral to.

Recognizing that all eReferral processes are a variation of 4 core processes, this specification will focus these 4 processes, and note exceptions and variations when appropriate.