How to Provide Feedback:
If you have feedback on the CA:eReC v1.0.3 DFT, to be considered for a future release, you can now submit your feedback via Jira as defined below;
- To submit feedback, you must register as a user on Infoway’s InfoCentral, be an active member of a working group, and be granted access to the JIRA projects.
- To register on the InfoCentral website, go to: https://infocentral.infoway-inforoute.ca. Click on the Register link and follow the instructions to create an account.
- Once registered in InfoCentral, and a working group, you can request access to Jira directly in a working group meeting, or by emailing [email protected].
- To access the eReferral Jira Project, go to: https://informs.infoway-inforoute.ca/projects/ER (Note: this link will only work if you have been granted access to JIRA).
- Submit your feedback on Jira. You will receive automatic notifications when your submissions receive comments or reach milestones during the review process.
- All collaborators are encouraged to browse through previously submitted feedback to see if a topic has already been discussed.
Please find more information on specification feedback by clicking on this link: pan-Canadian Interoperability Specifications Feedback
If you have any questions, issues, or comments related to specification feedback, please reach out to [email protected]
Release Notes
12/06/2024 -v1.0.3 release - Technical Errata
- Removed package dependency on ca.on.oh-eReferral-eConsult 0.11.1-alpha1.0.12.
- Fixed links pointing to previous ON eServices extensions, codesystems, and valuesets.
10/30/2024 -v1.0.2 release - Technical Errata
- Modified Bundle slicing discriminator from resource type to profile to improve validation capabilities.
- Fix typos on Messaging Compliance Table (in the Actors and Transactions section) for the following transactions:
- Notify data correction [eReCm-4] - Maturity Level should be L2 for eReC Requester
- Send communication from requester [eReCm-9] - Maturity Level should be L3 for eReC Performer
- Send communication from performer [eReCm-10] - Maturity Level should be L3 for eReC Performer
10/09/2024 - v1.0.1 release - Technical Errata
- Update to the canonical url for task-code.
- Updated the profile pages to reflect the correct canonicals for each profile
- Added linkage and description to the existing BusinessStatusReason extension in the extension table.
10/01/2024 - Initial v1.0.0 release of the CA:eReC Specifications including ballot feedback from the community.
- Updated overall page hierarchy from ballot feedback
- Business Context
- Added Business Models page to describe the people and systems that contribute to a service record in different eReferral and eConsult models supported by the specification.
- Updated Use Cases page - Added a use case for Central Access and Triage in addition to Central Intake. Updated flow diagrams for simplicity and consistency with sequence diagrams.
- Added Business Events page to describe events supporting eReferral/eConsult workflow associated with different levels of system maturity.
- Technical Context
- Updated MustSupport definition from ballot feedback - highlighted 'use case support' guidance on resource profiles.
- Added Integration Patterns page to highlight the real-world architectures that support the business models to provide implementable technical specifications. Updated technical actors, actor options and grouping - Note: addition of eReC Informer and eReC Recipient technical actors with updated
eReC-m2: Notify new service record
, and neweReC-m11: Notify update service record transactions
- Updated Messaging page with new actor definitions and transactions, re-framing transactions in context of maturity levels. Added requirements for reducing message size within a message bundle.
- Updated Sequence diagrams with new/updated actors and transactions. Added a diagram to support the Central Access and Triage use case.
- Updated Conformance Requirements tables with new/updated actors and transactions. Added a table to support Central Access and Triage use case.
- FHIR Artifacts
- HealthcareService profile added from ballot feedback
- Questionnaire profile removed from ballot feedback
Updated Appointment, Bundle, Communication, DocumentReference, Location, MessageHeader, Organization, Patient, Practitioner, PractitionerRole, QuestionnaireResponse, ServiceRequest, and Task profiles and version numbers based on ballot feedback
Removed mustSupport on CommunicationBarrier, CopiedParticipants, DARC, DART, HCNV Code, PatientPresentLocation, PerformerIdentifier, ReasonForNoHCN, ReferralIdentifier, and RoutingOptions extensions and updated their version numbers
All ValueSets were refined to include correct canonicals, with Canada Health Infoway owned codesystems created for each valueSet (with exception of human-language valueSet). Version numbers were removed
- Added example message bundles
- Added capability statements for technical actors