DRAFT - The specification is currently in development and subject to significant change. It is not ready for limited roll-out or production level use.
Updates
Terminology Updates
| VALUE SET/CODE SYSTEM | VERSION No. | DATE | SUMMARY OF CHANGE |
|---|---|---|---|
| CommunicationBarrier | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes codes from https://ehealthontario.ca/fhir/CodeSystem/communication-barrier until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems |
| CommunicationCategory | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes codes from https://ehealthontario.ca/fhir/CodeSystem/communication-category until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems |
| DARC and DART Reasons | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes codes from https://ehealthontario.ca/fhir/CodeSystem/darc-dart-reason until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems |
| eReferralIdentifierType | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes the code from http://ehealthontario.ca/fhir/CodeSystem/ereferral-identifier-type until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems |
| HumanLanguage | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention |
| MessageEventCode | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes codes from https://ehealthontario.ca/fhir/CodeSystem/message-event-code until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems |
| PatientContactRelationships | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes codes from http://ehealthontario.ca/fhir/CodeSystem/patient-contact-relationship until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems. Note that these codes in particular may also evolve as part of the requirements for emergency contact relationship codes in the pan-Canadian Health Data Content Framework |
| TaskBusinessStatus | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes codes from https://ehealthontario.ca/fhir/CodeSystem/task-business-status until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems |
| TaskCode | 0.1 | 11/28/2023 | Replaced eHealthOntario ValueSet Canonical with IGuide Canonical convention, still includes codes from https://ehealthontario.ca/fhir/CodeSystem/task-code until further feedback from the eReferral Interoperability Working Group is collected to address the impact of changing the code system on production systems |
Constraint Updates
CA:eReC cross iguide changes
.meta
The MustSupport flag on this element has been relaxed in this version until further confirmation of the use of meta.profile (outside of use for certain validation suites) and impact can be assessed by the working group. Please note that this relaxation is based on the IG Best Practices highlighted here of avoiding forcing the mustSupport constraint on .meta in profiles unless absolutely necessary.
.coding
Elements .coding.system and .coding.display have been relaxed, while the elements .coding and .coding.code will maintain their constraints as discussed within the eReferral interoperability working group, pending further discussion based on the mustSupport definition (TBC).
Known Issues
- Introduced virtualService extension derived from an R5 element within the Appointment profile. A separate extension will be created for it after balloting is completed. For now, please focus attention on the patterning and use of the Appointment resource and how virtualService fits into it.
Any known issues found within the guide will be documented in the section provided here in future iterations of this guide. To provide your questions or concerns please message Canada Health Infoway on: interoperability@infoway-inforoute.ca.