Cures Act - current level of compliancy based on specifications

[erikglimpse-crystalpm]

Based on the ONC's final rule for how a certified software's FHIR API should work...

https://www.healthit.gov/cures/sites/default/files/cures/2020-03/APICertificationCriterion.pdf

... how currently compliant is the Microsoft FHIR server with the Cures Act - G.10 out of the box?

What would need to be added or modified?

The Microsoft FHIR server appears to support the R4 standard (4.0.1), SMART on FHIR, TLS 1.2, and Bulk Data Access.

Does the Microsoft FHIR server also support the OpenID Connect standard, USCDI v1, and US Core?

[CaitlinV39]

@erikglimpse-crystalpm We do not attest to supporting this today. For SMART on FHIR, you will need to leverage additional capabilities to meet this today. We typically point people to look at our FHIR Proxy which has additional SMART support: https://github.com/microsoft/fhir-proxy/tree/main/docs

[erikglimpse-crystalpm]

@CaitlinV39 That answers our questions about SMART on FHIR, but not everything else mentioned.

If you're not supporting the Cures Act or these pieces individually, what could you say that the Microsoft FHIR server does have or even partially supports out of these:

R4 standard (4.0.1)
TLS 1.2
Bulk Data Access
OpenID Connect standard
USCDI v1
US Core FHIR standard

[CaitlinV39]

@erikglimpse-crystalpm sorry for the delay on this. Here are some details.

1. The open-source and both versions of our managed service support R4
2. We leverage Azure AD as the identity provider. The Azure AD Device Registration Service currently supports using Transport Layer Security (TLS) 1.2 for communications with Azure.
3. We have support for $export. The bulk data access IG is still definitely influx but we are monitoring and continuing to look at how we support Bulk Data Access. We have $import available in the open-source backed by SQL. We also support patient-$everything in open-source and both versions of the managed service.
4. We don't have anything out of the bok on OpenID connect right now. We are investigating.
5. I'd need a bit more detail on what you are looking for from the FHIR service for USCDI v1.
6. We allow you to load profiles and search parameters. The only gap I'm aware of on the US Core IG right now is that we don't support $docref.
   Let me know if that helps!

@CraigP68