Immunization use cases cover three main areas requiring standardization:
- Messaging
- TerminologySecurity
- Single Sign On (SSO)
Listed below are the available standards considered for each standardization category, the chosen alternative being highlighted.
Messaging
The following messaging standards were evaluated to support the exchange of information between front end applications and Panorama.
...
Standard | Fit for Purpose | Stewardship | Quality | |||||
Fits | Implementation | Vendor | Canadian | SDO | Complexity | Standard | Training, | |
Production | Yes | Localized | Normative | |||||
iTerm ValueSet | Custom | Yes | No | N/A | ||||
Architectural Constraints and Considerations | Secondary Benefits | |||||||
Both options were designed to support Panaroma's data model. | Using pan-Canadian terminology subsets supports inter-jurisdictional interoperability. SNOMED CT’s terminology model can be leveraged to support aggregation and analysis of the information captured within vaccination records. | |||||||
Recommendation | Supporting Rationale | |||||||
It is recommended that new implementations adopt the custom reference value sets developed by Ontario. | The pan-Canadian Public Health Immunization Subsets reflect Canadian requirements (e.g. Canadian vaccine lists), and is aligned with the PHAC Canadian Immunization Guide. It is being adopted in additional projects across Canada (including AB, SK, MB, Canadian Forces, CIHI), so additional implementations that adopt the Ontario standard will be well positioned for interoperability with these groups or organizations. | |||||||
...
Single Sign On (SSO)
The following security frameworks were considered to manage provide SSO access to protected data through via FHIR resources.
Standard | Fit for Purpose | Stewardship | Quality | |||||||||
Fits | Implementation | Vendor | Canadian | SDO | Complexity | Standard | Training, | |||||
| Production | | No | Yes | Normative | | ||||||
| Production | | No | Yes | Normative | | ||||||
Architectural Constraints and Considerations | Secondary Benefits | |||||||||||
oAuth 2.0 provides better support for mobile applications. |
| |||||||||||
Recommendation | Supporting Rationale |
| ||||||||||
It is recommended that oAuth 2.0 be used to provide SSO access to protected data through FHIR resources. | Better support for mobile applications. | |||||||||||