How to Provide Feedback: 

The ballot release of the pan-Canadian eReferral / eConsult v1.1.0 DFT-Ballot will be available on April 15

The timeline for ballot submissions is April 15 - May 16, 2025

You may review the CA:eReC Specifications in the following formats:

• Review the CA:eReC Specifications in Simplifier.net, from the corresponding link in the table above or on the Release page.

How to submit your ballot submission:

• All Collaborators are invited to document their ballot comments using the CA:eReC v1.1.0 DFT Submission spreadsheet, available here. 
• Send an email to [email protected], with Subject Line "CA:eReC", including the CA:eReC v1.1.0 DFT Submission spreadsheet as an attachment.
• We kindly ask that each organization submit all comments within one spreadsheet submission. 
• Upon submission, you will receive an acknowledgment email with a reference number. Feedback will be triaged by the Infoway Lead to support the eReferral/eConsult Working Group with decisioning/voting blocks.

For questions, please contact us at [email protected]

To learn more about the balloting cycle process, please visit the IO Specifications Publication Model page.

Release Notes

Implementation Guide

• Using pan-Canadian Enterprise Template

FHIR Profiles

• HealthcareService can be a reference Task.owner, Communication.sender. MessageHeader.author has optional cardinality (ER-48)

• ServiceRequest.identifier shall have a single official business identifier (ER-75)

• Patient.identifier is an optional, must support element (aligning with CA Core+ modelling) (ER-85)

• Task.output can use String and Code as allowable data-types (ER-35)

• Changed BindingStrength for ServiceRequest.category to preferred (ER-56)

Extensions

• Added ServiceProviderPreference extension to ServiceRequest to indicate preference for provider or location (ER-43)

• Added ServiceRequesterDelegate extension to ServiceRequest to identify person or provider that is the delegate (ER-49)

• Added back RoutingOptions and ReferralIdentifier extensions to MessageHeader and ServiceRequest (ER-58)

• Added back PerformerIdentifier extension to ServiceRequest.performer (ER-71)

Terminology

• Added MessageChangeReasonCode valueset to MessageHeader.reason to provide context on the trigger for ‘notify-update’ messages (ER-44)

Technical Context

• Fixes to certain transactions in UC-4 Central Access and Triage (CAT), Select Alternate Flows Sequence Diagrams (ER-51, ER-52, ER-54, ER-63, ER-64)

• Updated guidance for how Target Systems shall reference ServiceRequest received from Source systems (ER-67)
• MessageTransaction Details: Indicating where focus is variable and appropriate changeReasonCode to use (ER-84)