Technical Specifications > Central Intake Message Workflows
The Central Intake Hub (CI Hub) acts as a RMS-Source as well as a RMS-Target. The CI Hub is responsible for manage the referral queues for a regional Central Intake implementation. The CI Hub is integrated with the Ontario Provincial Care Coordination Gateway (PCCG) to:
- receive referrals into the queue
- route referrals to destinations
- receive routing recommendations
Routing, Splitting and Chaining Requests
In cases where a completion of a 'parent' ServiceRequest results in the creation of other 'children' ServiceRequests, multiple ServiceRequests MAY be triggered by an RMS that is performing the role of both RMS Source and RMS Target.
Message Flows
The diagram and corresponding table below illustrates message flows between Referral Management Systems, the PCCG, and the CI Hub in an electronic referral forwarding scenario.
| Business Event | Source System | Target System | Details |
|---|---|---|---|
| 1a. RMS Source sends ServiceRequest (SR1) to PCCG | RMS Source | PCCG |
|
| 1b. PCCG sends ServiceRequest (SR1) to CI Hub/RMS-T1 | PCCG | CI Hub/RMS Target 1 |
|
| 1c. CI Hub/RMS-T1 sends acknowledgement message to PCCG to track status | CI Hub/RMS Target 1 | PCCG |
|
| 1d. PCCG sends acknowledgement message to RMS-S to track status | PCCG | RMS Source |
|
| CI/RMS Target 1 routes/forwards referral to RMS Target 2 | |||
| 2a. CI Hub/RMS-T1 sends new ServiceRequest (SR2) to PCCG | CI Hub/RMS Target 1 | PCCG |
|
| 2a. PCCG sends new ServiceRequest (SR2) to RMS-T2 | PCCG | RMS Target 2 |
|
| 2b. CI Hub/RMS-T1 notifies RMS-S through PCCG that SR1 was routed/forwarded | CI Hub/RMS Target 1 | PCCG |
|
| 2b.PCCG notifies RMS-S that SR1 was routed/forwarded | PCCG | RMS Source |
|
| 2c.RMS-T2 sends acknowledgement message of referral acceptance to CI Hub/RMS-T1 and RMS-S through PCCG | RMS Target 2 | PCCG |
|
| 2c.PCCG sends acknowledgement message to CI Hub/RMS-T1 | PCCG | CI Hub/RMS Target 1 |
|
| 2d.CI Hub/RMS-T1 notifies RMS-S through PCCG that referral was updated | CI Hub/RMS Target 1 | PCCG |
|
| 2d.PCCG transmits message to notify RMS-S of referral update | PCCG | RMS Source |
|
| 3a.RMS T-2 requests further information for the patient, communication sent to RMS T1 | RMS Target 2 | PCCG |
|
| 3a.PCCG sends request for communication to CI Hub/RMS T1 | PCCG | CI Hub/RMS Target 1 |
|
| CI Hub/RMS-T1 assesses request and sends to RMS-S (Option 1) or answers (Option 2) | |||
| 3b. Option 1 CI Hub/RMS-T1 sends a new request to RMS-S through PCCG | CI Hub/RMS Target 1 | PCCG |
|
| 3b. Option 1 PCCG sends the new request to RMS-S | PCCG | RMS Source |
|
| 3b. Option 1 RMS Source sends answer of new request to CI Hub/RMS-T1 via PCCG | RMS Source | PCCG |
|
| 3b. Option 1 PCCG sends answer of new request to CI Hub/RMS-T1 | PCCG | CI Hub/RMS Target 1 |
|
| 3b. Option 1 CI Hub/RMS-T1 sends answer of new request to RMS-T2 | CI Hub/RMS Target 1 | PCCG |
|
| 3b. Option 1 PCCG sends answer of new request to RMS-T2 through PPCCG | PCCG | RMS Target 2 |
|
| 3b. Option 2 CI Hub/RMS-T1 sends answer to RMS-T2 through PCCG | CI Hub/RMS Target 1 | PCCG |
|
| 4a. RMS-T2 sends notification that referral has been accepted to CI Hub/RMS-T1 and RMS-S through PCCG | RMS Target 2 | PCCG |
|
| 4a. PCCG sends notification to CI Hub/RMS-T1 that referral has been accepted | PCCG | CI Hub/RMS Target 1 |
|
| 4b.CI Hub/RMS-T1 notifies RMS-S through PCCG that referral has been accepted | CI Hub/RMS Target 1 | PCCG |
|
| 4b.PCCG sends notification to RMS-S that referral has been accepted | PCCG | RMS Source |
|
| 5a.RMS-T2 sends notification that referral has been booked to CI Hub/RMS-T1 via PCCG | RMS Target 2 | PCCG |
|
| 5a.PCCG sends notification to CI-Hub / RMS-T1 that referral has been booked | PCCG | CI Hub/RMS Target 1 |
|
| 5a. CI-Hub/RMS-T1 notifies RMS-S through PCCG that referral has been booked | CI Hub/RMS Target 1 | PCCG |
|
| 5a. PCCG notifies RMS-S that referral has been booked | PCCG | RMS-Target 1 |
|
The diagram and corresponding table below illustrates message flows between Referral Management Systems, the PCCG, and the CI Hub in an electronic referral splitting scenario.
| Business Event | Source System | Target System | Details |
|---|---|---|---|
| 1a. RMS Source sends ServiceRequest (SR1) to PCCG | RMS Source | PCCG |
|
| 1b. PCCG sends ServiceRequest (SR1) to Central Intake | PCCG | Central Intake |
|
| 2a. Central Intake sends acknowledgement message to PCCG to indicate receipt | Central Intake | PCCG |
|
| 2b. PCCG sends acknowledgement message to RMS-S to indicate receipt | PCCG | RMS Source |
|
| Central Intake splits the ServiceRequest and creates two child ServiceRequests | NOTE: Official identifier SHALL be different for SR1, SR1.1 and SR1.2 SR1.1.replaces = nullSR1.1.identifier = newSR1.1.requsition = SR1 identifierSR1.1.requester = SR1.performerSR1.1.basedOn = SR1When the system splits the referral based on the downstream provider's preferences configured in PHSD, both split referrals are routed to the same RMS-T | ||
| SR1.1 Flow | |||
| 3.1a. Central Intake sends new ServiceRequest (SR1.1) to RMS Target 1 via PCCG | Central Intake | PCCG |
|
| 3.1b. PCCG sends new ServiceRequest (SR1.1) to RMS Target 1 | PCCG | RMS Target 1 |
|
| 3.1.c. Central Intake notifies RMS-S through PCCG that SR1 was split and two child referral (SR1.1 and SR1.2) were created | Central Intake | PCCG |
|
| 3.1.d.PCCG notifies RMS-S that SR1 was split and two child referral (SR1.1 and SR1.2) were created | PCCG | RMS Source |
|
| 4.1a. RMS-Target 1 sends acknowledgement message to PCCG to indicate receipt | RMS Target 1 | PCCG |
|
| 4.1.b. PCCG sends notification of receipt to Central Intake | PCCG | Central Intake |
|
| 4.1.c. Central Intake sends notice of receipt to RMS-S through PCCG | Central Intake | PCCG |
|
| 4.1.d.PCCG sends notification of receipt to RMS-S | PCCG | RMS Source |
|
| 5.1.a.RMS Target 1 sends notification that referral has accepted to Central Intake via PCCG | RMS Target 1 | PCCG |
|
| 5.1.b.PCCG sends notification that referral has accepted to Central Intake | PCCG | Central Intake |
|
| 5.1.c.Central Intake sends notification that referral has accepted to RMS Source via PCCG | Central Intake | PCCG |
|
| 5.1.c.PCCG sends notification that referral has accepted to RMS Source | PCCG | RMS Source |
|
| 6.1.a.RMS Target 1 sends appointment details for child ServiceRequest (SR1.1) | RMS Target 1 | PCCG |
|
| 6.1.b.PCCG sends appointment details for child ServiceRequest (SR1.1) | PCCG | Central Intake |
|
| 6.1.c.Central Intake sends appointment details for child ServiceRequest (SR1.1) | Central Intake | PCCG |
|
| 6.1.c.PCCG sends appointment details for child ServiceRequest (SR1.1) | PCCG | RMS Source |
|
| SR1.2 Flow | |||
| 3.2a. Central Intake sends new ServiceRequest (SR1.2) to RMS Target 2 via PCCG | Central Intake | PCCG |
|
| 3.2b. PCCG sends new ServiceRequest (SR1.2) to RMS Target 2 | PCCG | RMS Target 2 |
|
| 4.2.a. RMS-Target 2 sends acknowledgement message to PCCG to indicate receipt | RMS Target 2 | PCCG |
|
| 4.2.b. PCCG sends notification of receipt to Central Intake | PCCG | Central Intake |
|
| 4.2.c. Central Intake sends notice of receipt to RMS-S through PCCG | Central Intake | PCCG |
|
| 4.2.d.PCCG sends notification of receipt to RMS-S | PCCG | RMS Source |
|
| 5.2.a.RMS Target 2 sends notification that referral has accepted to Central Intake via PCCG | RMS Target 2 | PCCG |
|
| 5.2.b.PCCG sends notification that referral has accepted to Central Intake | PCCG | Central Intake |
|
| 5.2.c.Central Intake sends notification that referral has accepted to RMS Source via PCCG | Central Intake | PCCG |
|
| 5.2.c.PCCG sends notification that referral has accepted to RMS Source | PCCG | RMS Source |
|
| 6.2.a.RMS Target 2 sends appointment details for child ServiceRequest (SR1.1) | RMS Target 2 | PCCG |
|
| 6.2.b.PCCG sends appointment details for child ServiceRequest (SR1.1) | PCCG | Central Intake |
|
| 6.2.c.Central Intake sends appointment details for child ServiceRequest (SR1.1) | Central Intake | PCCG |
|
| 6.2.c.PCCG sends appointment details for child ServiceRequest (SR1.1) | PCCG | RMS Source |
|