This guide focuses on the selection of messaging standards to support the in scope use cases.
Messaging
The following standards were considered to communicate Vaccination Events and to Query Immunization Repositories.
...
Due to differences in business requirements, the standards evaluation is broken into two sets of standardization requirements:
- Consumer messaging
- Source messaging
Consumer messaging
A primary role of the Provider Registry is to enable provider identification within consumer systems contributing data to or consuming data from provincial EHR solutions. The predominant means for exchanging data with the EHR is HL7 version 3 messaging.
Standard | Fit for Purpose | Stewardship | Quality | ||||||||||||||
Fits | Implementation | Vendor Support | Canadian | SDO | Complexity | Standard | Training, Support and Tooling | ||||||||||
Immunization HL7 V3.0AB MR2009 (HL7 v3) | Production | Yes (AB)Yes | Localized |
| MedHigh | ||||||||||||
CeRx 4.4 HL7 V3.0pan-Canadian MR2009 (HL7 v3) | Production in Canada | YesYes | Localized | High | |||||||||||||
HLv2 PRS XML Messaging | ProductionNot used | Yes | NoYes | High | |||||||||||||
Architectural Constraints and Considerations | Secondary Benefits | ||||||||||||||||
HL7 V3 Immunizations specification was designed to support the immunization use cases in a manner consistent with the design principles Use of HL7v3 conforms with the architectural design of Canada's digital health blueprint. AB MR2009 extends the Canadian specification with the ability to merge and logically delete providers. HL7v3 messaging does not provide the means to transmit a the history of changes to a provider records. The CeRx specification has been superseded by the Immunizations Specification for vaccine event messaging.PRS XML Messaging specification is proprietary to the registry solution but is shared across several provinces. | Standardizing on MR2009 across EHR applications reduces complexity within the infostructure and for implementers by minimizing variability in models and vocabularyVersion 3 uses rigorous analytic and message building techniques and eliminates areas of optionality that could negatively impact semantic interoperability. | ||||||||||||||||
| Recommendation | Supporting Rationale | ||||||||||||||||
| AB MR2009 (HL7 v3) | The AB MR2009 | It is recommended that new implementations adopt Immunization HL7 V3.0 for immunization. | The specification was designed to meet the in-scope use cases for PRS consumers and conforms with the architectural design of Canada's digital health blueprint. It extends the Canadian specification with the ability to merge and logically delete providers. | ||||||||||||||
Source messaging
Source messaging provides the means to transmit information from systems used at various licensing agencies, professional colleges, etc. to the Provider Registry.
Standard | Fit for Purpose | Stewardship | Quality | |||||
Fits | Implementation | Vendor Support | Canadian | SDO | Complexity | Standard | Training, Support and Tooling | |
PRS XML Messaging | Production | Yes | No |
| High | |||
| AB MR2009 (HL7 v3) | Production in Canada | Yes (AB) | Localized | High | ||||
pan-Canadian MR2009 (HL7 v3) | Production in Canada | Yes | Localized | High | ||||
Architectural Constraints and Considerations | Secondary Benefits | |||||||
Source systems are not typically EHR consumer systems. HL7v3 messaging does not provide the means to transmit a the history of changes to a provider records. (UC-6) The PRS XML Messaging specification is proprietary to the registry solution but is shared across several provinces. |
| |||||||
| Recommendation | Supporting Rationale | |||||||
| PRS XML Messaging | The PRS XML specification was designed to meet the in-scope use cases for PRS source systems. Although the specification is proprietary to the specific provider registry solution used in Alberta it is relatively straightforward to implement. | |||||||