FHIR Chat · SMART Backend Services and SMART App Launch

Stream: smart

Topic: SMART Backend Services and SMART App Launch

Josh Mandel (Jun 03 2021 at 16:44):

We've got a ballot reconciliation window open right now for SMARTv2 and for Bulk Data -- one question is whether we should take this opportunity to move the "Backend Services Authorization" page from Bulk Data --> SMARTv2.

This would help by:

Consolidating authorization profiles in one place (SMARTv2)
Clarifying that backend services authorization is useful beyond Bulk Data

Anybody think this is a bad idea?

Josh Mandel (Jun 03 2021 at 16:47):

@Lloyd McKenzie is this a "transfer" of a page that we can do during reconciliation of these two STU specs?

Lloyd McKenzie (Jun 03 2021 at 18:30):

From an HL7 perspective, it's not really a transfer, it's adding rules to one spec and removing rules from another spec. Formally, there'd be no transfer of 'ballot experience' from the original page to the new page, but from an FMG you could finesse that if it ever became an issue

Josh Mandel (Jun 03 2021 at 20:48):

Thanks @Lloyd McKenzie! I guess I want to figure out is... should I try this? I think it'd be the right thing outcome-wise, but if there are deep procedural concerns I'd just skip it.

Gino Canessa (Jun 03 2021 at 20:56):

FWIW, +1 to moving it. It feels odd to link to the Bulk Data IG in order to talk about SMART Backend Auth, and it's harder to discover.

Lloyd McKenzie (Jun 04 2021 at 03:07):

Is the spec the content being removed from normative? If it were, you might have to deprecate it rather than remove it. Other than that, I can't think of any procedural issues.