livaz
Thanks so much to you, @CaitlinV39 and @SteveWohl for putting together the CMS guidance for configuring Azure FHIR.
While technically correct, I'm afraid this statement will be misleading to business stakeholders new to FHIR.
The Azure API for FHIR has a https://docs.microsoft.com/azure/healthcare-apis/fhir/use-smart-on-fhir-proxy built in that can be enabled for basic SMART on FHIR scenarios. In addition, our health architects have developed a more robust https://github.com/microsoft/fhir-proxy that can be extended for more complex scenarios.
The CMS patient access API requires the use of the SMART on FHIR stand alone launch sequence.
* "Tutorial: Azure Active Directory SMART on FHIR proxy"only supports the EHR launch sequence.
* For fhir-proxy, the SMART capability statement isn't listed in the README.md so I cannot tell at a glance whether stand-alone launch (launch-standalone) is supported (along with the other capabilities required for Patient Access). I already opened a ticket [https://github.com/microsoft/fhir-proxy/issues/4].
Without a tutorial on SMART as it applies to the CMS rule (Patient Access API), the CMS tutorial is incomplete (even for an MVP).
Secondarily, it may be unclear from this announcement that Azure FHIR is not an "out of the box" solution for CMS rule FHIR compliance; but rather, CMS compliant APIs can be built on-top of Azure FHIR. The tutorials lower the knowledge barrier of understanding the details of the IGs, but are by themselves insufficient.
Microsoft