thank you to the presenters and to Russ for sharing the video links.
With regards to HALO, the conceptual architecture flow has a step 4b "App Authz" to goes from the SMART app to the IDP/AS. Is the intention that all SMART apps will need to authorize with a PT IDP/AS when they are launched (rather than or on top of the 'local' auth flow between the SMART launcher and the SMART app)? I ask because I presume that for step 2 (between the EMR and the IDP/AS) that is a jurisdictional identity mechanism.
As always, we are interested in hearing about your projects, learning about SMART on FHIR capabilities of your products and lessons learned. Please reply to this thread or the meeting invite with suggestions for future topics.
In the meantime, we’ll work with the Infoway team to tee up a conversations about:
- Vendor engagement on HALO requirements
- Deeper dive into technical topics like expected capabilities of the FHIR endpoint
Next meeting is scheduled for October 18th. Have a wonderful month!
Our regular cadence of SMART North meetings will resume on Sept 20th with:
- an update on the HALO project from the team at Canada Health Infoway, and
- a demonstration of a low-code FHIR development platform that the CANImmunize team have been working on.
For those who need a reminder, HALO is the Infoway project that stemmed from projects at Ontario Health, BC Provincial Health Services Authority (PHSA) to support launch of apps from EMRs with context and EHR access mentioned at a couple meetings in the spring.
Improving the quality of patient care through the effective sharing of clinical information among health care organizations, clinicians and their patients.