Issue while testing Patient Standalone App - Full Access

[HitakshiDobariya99]

I'm following this document for the implementation of SMART on FHIR: https://github.com/Azure-Samples/azure-health-data-services-samples/blob/main/samples/patientandpopulationservices-smartonfhir-oncg10/docs/deployment.md

I have diligently completed each step of the deployment process. However, while testing the Standalone App for Patients, I encountered an error.

I have verified the roles and permissions settings thoroughly and assigned permissions for my application. Also, I gave the Administrator rights to Auth function app for modifying signed user permissions.

Kindly seek your expertise to resolve this issue. Your assistance will be highly appreciated. Thank you.

[VirajKheni]

I'm facing the same issue. If is there anyone who knows then will be very appreciative.

https://github.com/Azure-Samples/azure-health-data-services-samples/issues/105

[nimesh13]

Hey can you guys let me know how you are testing this? I probably missed this in the docs but I can only find the extensive postman APIs and the inferno tool only.

[HitakshiDobariya99]

Hello, I'm testing Standalone Patient App - Full Access from the Inferno test suite. In this testing, I'm giving APIM smart baseUrl, client app id, and secret which has the patient's scope. https://inferno.healthit.gov/suites/g10_certification/dfCEkR56ZIC#1

[EXPEkesheth]

Thanks for reporting the issue, we will investigate and report back

[nimesh13]

@HitakshiDobariya99 oh the inferno tool, okay. I tried with the APIM gateway URL, standalone client app id and secret but it returns a 404 resource not found. I added the standalone app to the fhir service IAM roles too.

Any idea?

[VirajKheni]

Hello @nimesh13

I think it's a base URL mistake. You need to give APIM gateway URL/smart as a base Url.

[nimesh13]

@VirajKheni oh yes this worked!! Thanks! But is this documented anywhere?

[nimesh13]

So I am also stuck on a similar issue:

[EXPEkesheth]

@erikhoward - can you please check on the documentation issue mentioned by Viral above?

@nimesh13 - is this a different issue mentioned from original one ? If yes, can you please share more details and create new issue?

[nimesh13]

@EXPEkesheth - yes I have moved the discussion to a new issue.

[EXPEkesheth]

Documentation updated and hence closing the issue

[HitakshiDobariya99]

This issue is resolved now. You can close the issue.