You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

In Development

Please note the state of this interoperability specifications workspace is 'In Development'.  Most pages will have no text.  As we work with our partners, we will identify the pages that have draft content and should be reviewed.


The pan-Canadian eReferral / eConsult (CA-eReC) Interoperability Specification is an implementable and testable specification. It defines building blocks to create electronic referrals and electronic consults that will support communication between healthcare practitioners and service providers performing electronic patient referrals and / or electronic consultations.  CA-eReC building blocks are configurable to address necessary Canadian jurisdictions variances. 

An eReferral is an electronic request for a patient to receive care from a specialist or other services (e.g., home or community care, diagnostic exam). It aims to streamline and improve the referral process compared to traditional paper-based methods.  Overall, eReferrals aim to enhance the quality of patient care, reduce delays in treatment, and improve the overall efficiency of the healthcare system.

An eConsult is an electronic request from a physician to receive advice from a specialist (i.e., provider-to-provider consultation)?, enabling asynchronous communication between the requesting physician and specialist. 

The CA-eReC specifications, written in line with international best practices, contain the information necessary for an implementer to consume and develop the components necessary for creating, and consuming an electronic referral or consult.

Intended Audience

The intended audience of this document is participants of the eReferral Working Group who are collaborating with Infoway to develop the pan-Canadian CA-eReC interoperability specification.  The current state of these pages is 'In Development'.  Most content one would expect from these types of specifications will be missing.  These pages should be taken as work-in-progress.

Purpose

The purpose of this document is to propose and work through the use cases in scope for eReC-CA,

Once we have a defined scope, the goal will be to collaborate with the working group participants to define:

  • Detailed set of requirements (including Actors, Transactions and References to specific profiles and standards),
  • Describe the implementation patterns that enable the exchange of the eReC-CA, and
  • Describe the set of requirements that complement the set of IHE Profiles, pan-Canadian Interoperability Specifications (e.g. CA:FeX), and HL7 FHIR® Profiles required by the eReC-CA specifications with Canadian-specific constraints.
  • No labels