Integration Profiles Overview

Integration Profiles in HALO describe reusable technical patterns—based on IHE-style specifications—that define how systems and actors exchange information to meet specific interoperability needs. Each profile specifies roles, transactions, and conformance requirements that together enable consistent, secure integration within HALO.

Purpose and Role in HALO

Integration Profiles provide the technical building blocks that connect HALO’s high-level use cases to real-world, testable implementations. By defining clear actor responsibilities and transaction flows, they ensure reliable interoperability, support conformance testing, and maintain alignment with evolving pan-Canadian interoperability standards. These profiles form the foundational layer that translates conceptual workflows into concrete, standards-based system behaviour.

Profiles in HALO

This section currently includes four core Integration Profiles within the HALO framework:

• CA:AC – pan-Canadian App Catalog – Defines how systems discover and retrieve metadata about jurisdictionally approved SMART on FHIR applications, enabling consistent app selection and launch integration.
• CA:SoF – pan-Canadian SMART on FHIR – Specifies the pan-Canadian use of SMART App Launch v2.1.0 for secure, standards-based app launches, including discovery of authorization endpoints, token exchange, and access to contextual FHIR resources.
• CA:SoFA – pan-Canadian SMART on FHIR Accelerator – Adds HALO-specific context management capabilities to SMART on FHIR, allowing systems to securely package, transmit, and manage clinical launch context using $set-context and $clear-context.
• CA:FSub – pan-Canadian FHIR Subscription – Defines an event-driven FHIR Subscription mechanism for keeping Point of Care systems synchronized with SoFA updates, supporting both REST-hook and WebSocket channels.

Future Considerations

While designed for HALO, these Integration Profiles are intentionally specified for potential re-use. As pan-Canadian specifications evolve, and if other initiatives require these capabilities, the profiles may be adopted more broadly or transitioned into standalone specifications outside of the HALO project.