Visit the HL7 website
Visit the FHIR website

Pan-Canadian eReferral-eConsult (CA:eReC) v1.1.0-DFT-Ballot

1.1.0-DFT-Ballot   Canada flag
  • Index
  • Home
  • Business Context
    • Business Models
    • Use Cases
    • Business Events
    • Business Rules
    • Privacy and Security Guidance
    • Provincial Considerations
  • Technical Context
    • Technical Foundation
    • Integration Patterns
    • Messaging
    • Sequence Diagrams
    • Conformance Requirements
  • FHIR Artifacts
    • Messaging Events
    • Resource Profiles
    • Extensions
    • Terminology
    • Examples
    • Capability Statements
    • Downloads
    • ---
    • Appointment (CA:eReC)
    • Bundle (CA:eReC)
    • Communication (CA:eReC)
    • DocumentReference (CA:eReC)
    • Location (CA:eReC)
    • MessageHeader (CA:eReC)
    • Organization (CA:eReC)
    • Patient (CA:eReC)
    • Practitioner (CA:eReC)
    • PractitionerRole (CA:eReC)
    • HealthcareService (CA:eReC)
    • QuestionnaireResponse (CA:eReC)
    • ServiceRequest (CA:eReC)
    • Task (CA:eReC)
  • Change Log
    1. Index
    2. Business Context
    3. Business Models
    4. Example: Central Intake in Point to Point

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

Example: Central Intake in Point to Point

In Ontario, Central Intake services have been introduced to provide single points of access to high demand services within specific geographical areas within the province.

Organizations operating Central Intake services have a choice of RMS solutions to support their requirements and these have been introduced to an existing network of Point to Point integrations with existing Source Systems and Target Systems.

In this model the RMS used by Central Intake is a Target for requests from Requester HCPs and can be seen as a Source of Referrals to Performer HCPs.

To support this, an integrated RMS used by Central Intake (in role of Case Assigner) will employ separate messaging approaches to:

  1. Enable the Case Assigner to receive the service request from the Requester HCP / Source System, communicate acceptance (etc.)
  2. Enable the Case Assigner to transmit the service request to the Performer HCP / Target System and receive, acceptance, (etc.)
  3. Enable the Case Assigner to notify the Requester HCP / Source System of its interactions with the Performer HCP as the service request is assigned, accepted, completed (etc.)

BusModel-CentralIntakeMultipleRMS

Table of Contents | IG © based on FHIR R4 | Package package:ca.infoway.io.erec@1.1.1-dft-ballot | Version History
HL7® and FHIR® are the registered trademarks of Health Level Seven International