Workflow or API calls:
Reminder: If this is referring to a client domain or EHR activity—not the public sandbox—do not include API request data or live patient data.
Background Information:
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
We are setting up a SMART on FHIR integration for Banner Health in their Pre‑Production Cerner environment.
Our SMART on FHIR application is already registered in the Oracle Health Code Console, and we are able to successfully launch the app using the “Test Sandbox” feature. This confirms that the app itself is functioning correctly.
Issue Encountered
When Banner Health launches our SMART on FHIR app from their Cerner instance, the required SMART on FHIR query parameters are not being included.
Cerner is currently launching the app using the following URI without the required query parameters:
https://smartonfhir-preprod.nextplanesolutions.com/pgsmartlaunch
However, a proper SMART on FHIR launch must include both the iss and launch parameters:
https://smartonfhir-preprod.nextplanesolutions.com/pgsmartlaunch?iss={THEIR_ISS}&launch={LAUNCH_TOKEN}
Are you an Oracle Partner Network Member? Yes
If you answer Yes to the above, please answer the below as well:
Partner/Company Name: Press Ganey
Is your company enrolled in the Industry Healthcare Path? No
Does your company have the Oracle Health Millennium Platform (OHMP) Environment Access Technical Accelerator? Yes / No
Are you developing on behalf of an Oracle Health client?
If so, which client:
Yes Banner Health
Application's Client ID and App ID, if relevant:
Application ID
e1b410fe-0f54-4075-a208-28d4afa9737c
Client ID
9858ebbd-c9b8-468c-81ea-7887c4bff68d
Expected Result:
SMART on FHIR launch should include:
- iss (the EHR’s FHIR base URL)
- launch (the EHR-provided launch context)
Example:
https://smartonfhir-preprod.nextplanesolutions.com/pgsmartlaunch?iss={THEIR_ISS}&launch={LAUNCH_TOKEN}
Actual Result:
Cerner launches the following without any query parameters, causing the SMART on FHIR launch to fail:
https://smartonfhir-preprod.nextplanesolutions.com/pgsmartlaunch