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. Single RMS Model

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

Single RMS Model

In the Single RMS Model, a single referral management system supports the exchange of Service requests, Appointments and Secure Communications between Requester HCPs and Performer HCPs. This could be a multi-tenant cloud environment supporting multiple independent subscribers or a shared enterprise or jurisdictional system.

Example workflow:

  • A Requester HCP (also performing the role of Case Assigner) initiates the referral in an RMS, selects a Performer HCP to provide the service, completes the required paperwork and sends the referral
  • The Performer HCP receives the referral, triages the request for completeness & appropriateness, accepts and completes the referral in the same, shared RMS as the Requester HCP
  • The RMS enable transmission of the referral to the Performer HCP as well as transmission of status updates, appointments, etc. to the Requester HCP
  • A shared Service Record is created and maintained within the RMS as a result of information entered by the Requester HCP and Performer HCP

BusModel-SingleRMS

Connecting POS Systems

Within a Single RMS Model, system integrations with local point of service systems (POS) may be used to improve workflow, to support creation and management of referral record and/or to retain a copy of a referral Service Record in the patient's chart.

Referral record copied to POS

Where a POS system does not have built in support for referral management, HCPs may create and/or manage referrals in an RMS and then receive a copy of the Service Record in their POS system through a system integration.

BusModel-SingleRMSwConnected

Referral initiated and/or managed in POS

In other cases, a POS system may provide HCPs with the ability to:

  • Initiate a referral in the POS system and then send a request to the RMS to create the Service Record through a system integration, and/or
  • Receive and manage referral information in the POS system and then communicate updates to the referral's status (e.g.: acceptance, completion), and appointment information to the RMS's copy of the Service Record through a system integration

BusModel-SingleRMSwConnectedSourceTarget

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