Versions Compared

Old Version 3

changes.mady.by.user Russ Buchanan

Saved on

compared with

New Version Current

changes.mady.by.user Russ Buchanan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This guide focuses on the selection of messaging standards to support the in scope use cases.  Due to differences in business requirements, the standards evaluation is broken into two sets of standardization requirements:

  • Consumer messaging
  • Source messaging

Consumer messaging

The A primary role of the PRS system Provider Registry is to enable provider identification to 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
Requirements

Implementation
Type 

Vendor Support

Canadian
Steward

SDO
Maintained

Complexity

Standard
Maturity

Training,
Support
and Tooling

AB MR2009 (HL7 v3)

CloselyImage Modified

Production
in Canada 

High

Yes (AB)

Localized by Alberta

High

 

High

AvailableImage Modified

pan-Canadian MR2009 (HL7 v3)

PartiallyImage ModifiedProduction
in Canada 		HighYesLocalized by InfowayHighHighAvailableImage Modified

PRS XML Messaging

PartiallyImage Modified

Production
in Canada 

Medium

Yes

No

LowImage Modified

High

LimitedImage Modified

Architectural Constraints and Considerations

Secondary Benefits

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 full version of the provider record including a history of changes to a provider records.

The PRS XML Messaging specification is proprietary to the WHIC PRS solutionregistry 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 vocabulary.

Recommendation

Supporting Rationale

AB MR2009 (HL7 v3)The AB MR2009 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
Requirements

Implementation
Type 

Vendor Support

Canadian
Steward

SDO
Maintained

Complexity

Standard
Maturity

Training,
Support
and Tooling

PRS XML Messaging

CloselyImage Added

Production
in Canada 

HighImage Added

Yes

No

LowImage Added

 

High

LimitedImage Added
AB MR2009 (HL7 v3)PartiallyImage AddedProduction
in Canada 		None (Source)Image AddedYes (AB)LocalizedHighImage AddedHighAvailableImage Added

pan-Canadian MR2009 (HL7 v3)

LimitedImage AddedProduction
in Canada 		None (Source)Image AddedYesLocalizedHighImage AddedHighAvailableImage Added

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 MessagingThe 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.