FHIR Chat · EHR Practitioner APP · inferno

Stream: inferno

Topic: EHR Practitioner APP


view this post on Zulip Suhas Patil (Jan 24 2022 at 06:30):

Inferno:. EHR Practitioner APP Test
Problem statement:
For EHR Practitioner APP testing, after providing required Launch Sequence from Different Browser doesn’t recognize actively running test.

Description:
Sample test was run for the SMART app hosted on Logica Sandbox.
During EHR Practitioner app testing after providing required FHIR end points and Client ID /Secret details it prompts and wait for LAUNCH Sequence to be initiated.
If this request is initiated from same browser type (say Inferno is running on Chrome and Launch URLI is imitated from Chrome) it proceeds for execution, whereas if Lunch URI is launched from different Browser (say Microsoft Edge) Inferno test doesn’t recognize the LAUNCH URI.
It gives the error: No actively running Launch sequence found for this ISS:<FHIR URL>. Please ensure that the EHR launch test is actively running before attempting to launch inferno from the EHR
So, it looks that it doesn’t recognize the session of running Launch URL from cross Browser.

Is there any way to handle this?

Eventually we need to call the LAUNCH URL from the in-build Browser of our EHR Application.
image.png

view this post on Zulip Stephen MacVicar (Jan 24 2022 at 13:12):

I can not reproduce this. I can start the EHR Practitioner App tests in Firefox, and then, when Inferno is waiting to receive the request, perform the EHR launch in Chrome and it works as intended. Does the ISS you're displaying exactly match the server url you're using for the tests?

view this post on Zulip Stephen MacVicar (Jan 24 2022 at 13:20):

Looking at your results further, the ISS does not match the server url. The iss ends in /data while the server url doesn't.

view this post on Zulip Suhas Patil (Jan 25 2022 at 15:38):

Stephen MacVicar said:

Looking at your results further, the ISS does not match the server url. The iss ends in /data while the server url doesn't.

Hi Stephen, Thanks... Great we realized what was wrong. Now with Updated URL its working. Many Thanks

view this post on Zulip Suhas Patil (Feb 02 2022 at 11:36):

Inferno:. EHR Practitioner APP Test
Problem statement:
For EHR Practitioner APP testing, after providing required Launch Sequence from Different Browser doesn’t recognize actively running test.
Description:
We are using Inferno SMART App having URI
Redirect.- https://inferno.healthit.gov/inferno/oauth2/static/redirect
Launch - https://inferno.healthit.gov/inferno/oauth2/static/Launch

During EHR Practitioner app testing after providing required FHIR end points and Client ID /Secret details it prompts and wait for LAUNCH Sequence to be initiated.
Launch Sequence https://<serverName>/SOFInferenoTest/launch.html?launch=<PatientGuid>&iss=https://<ServerName>/fhir-ClinAuth/
Issue:
If this request is initiated from same browser type (say Inferno is running on Chrome and Launch URLI is imitated from Chrome) it proceeds for execution, whereas if Lunch URI is launched from different Browser (say Microsoft Edge).
It gives the error:
Inferno has detected an issue with the SMART launch. No actively running launch sequences found with a state parameter of '0HGyNBkA2UcWgyui'. The authorization server is not returning the correct state variable and therefore Inferno cannot identify which server is currently under test
So, it looks that it doesn’t recognize the session of running Launch URL from cross Browser.
Is there any way to handle this?
Eventually we need to call the LAUNCH URL from the in-build Browser of our EHR Application.

image.png

We did some dig down and found the state parameter is managed by inferno itself and client do not have control over this parameter.
https://github.com/smart-on-fhir/client-js/issues/112

please suggest if any workaround available for this issue. Also if there is any wiki or documentation on state parameter how it is generated and managed by inferno server it will help.

view this post on Zulip Stephen MacVicar (Feb 02 2022 at 12:53):

That message indicates that the authorization server is returning an incorrect value for state. I can tell from the screenshot you provided that the authorization server is returning the wrong state because Inferno generates a UUID for state, and in that screenshot the authorization server is not providing a UUID.

While running the EHR launch sequence, after you initiate the launch, you will be informed that you are being redirected to the authorization server with the following modal:

Screen-Shot-2022-02-02-at-7.47.29-AM.png

If you inspect the url in that modal, you will see a value for state. You should be able to compare that value against what the authorization server returns and see that they are different.

view this post on Zulip Suhas Patil (Feb 22 2022 at 14:28):

Inferno: EHR Practitioner APP Test

We are using Inferno SMART App having URI
Redirect.- https://inferno.healthit.gov/inferno/oauth2/static/redirect
Launch - https://inferno.healthit.gov/inferno/oauth2/static/Launch

Scenario:
During EHR Practitioner app testing after providing required FHIR end points and Client ID /Secret details it prompts and wait for LAUNCH Sequence to be initiated.
Launch Sequence
While Providing below URL in another Browser window, it Doesn’t do the Authentication and redirects to Test Execution
https://inferno.healthit.gov/inferno/oauth2/static/Launch?launch=<PatientGuid>&iss=https://<ServerName>/fhir-ClinAuth/

Question: Is there any way to perform authentication before test execution

view this post on Zulip Yunwei Wang (Feb 22 2022 at 16:57):

any error messages?

view this post on Zulip Anshabapu Najan (Feb 24 2022 at 08:17):

can we use our own SMART On FHIR application with inferno to execute tests?

view this post on Zulip Yunwei Wang (Feb 24 2022 at 14:11):

@Anshabapu Najan Sorry, I don't quite understand. Can you clarify your question?

view this post on Zulip Cooper Thompson (Feb 24 2022 at 14:22):

Inferno IS a SMART on FHIR app. Are you asking if you can use your own SMART app instead of Inferno? For initial testing: sure. For actual certification: very likely not.


Last updated: Apr 12 2022 at 19:14 UTC