Stream: IPA
Topic: SMART aspects of IPA
Mikael Rinnetmäki (Jan 11 2022 at 17:57):
@Michael van der Zel please choose one of the checkpoints scheduled for the IPA track to discuss the SMART stuff in more detail.
Isaac Vetter (Jan 11 2022 at 18:23):
Hey Michael! Mind sharing what you're thinking in terms of SMART & IPA?
Josh Mandel (Jan 11 2022 at 19:38):
If this is scheduled, maybe cross post a note in #smart ?
Josh Mandel (Jan 11 2022 at 19:39):
I just reviewed and submitted ballot comments yesterday -- such good work happening here in #IPA !
Michael van der Zel (Jan 12 2022 at 19:57):
In the Dutch IG they defined scopes that don't look like the SMART scopes here http://hl7.org/fhir/smart-app-launch/1.0.0/scopes-and-launch-context/index.html
They are like "medmij-medication-overview", instead of "patient/Medication.read, patient/MedicationStatement.read, ..."
Sometimes this is useful, but for implementations not so. The first is like a short version of the last. But how can we do this in a generic way?
Josh Mandel (Jan 12 2022 at 20:15):
This same theme came up in discussion with @Grahame Grieve earlier today in the SMARTv2 track, though it was a bit abstract -- Grahame, is this Dutch approach the kind of thing you were advocating?
John Moehrke (Jan 12 2022 at 20:29):
On a discussion yesterday it came up too... I was indicating that the Dutch model is similar to how IHE is approaching it. That is to say for example when IHE-MHD is grouped with IHE-IUA there is a defined set of scope strings specified for this grouping; when IHE-MHD is grouped with SMART then the SMART scopes are used. The IG specific scope strings can be informatively defined as equivalent (usually) to SMART scopes; but they do not need to be implemented exactly the same as SMART scopes.
Grahame Grieve (Jan 27 2022 at 05:04):
@Josh Mandel maybe. I suspect that it won't be as simple as a syntax expansion - I think there'll be deeper business rules that need to be dealt with
Last updated: Apr 12 2022 at 19:14 UTC
