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:
Are you an Oracle Partner Network Member? Yes / No
If you answer Yes to the above, please answer the below as well:
Partner/Company Name: Heidi Health Trading Pty Ltd
Is your company enrolled in the Industry Healthcare Path? Yes / 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? No. We are piloting with the American Hospital in Dubai but we are not developing on their behalf
If so, which client:
Application's Client ID and App ID, if relevant:
app ID: 6522cd9b-ea14-40d0-b3ff-8ce77f18e5b8
Client ID: 0dea21b6-8981-4200-94bb-2ed83e903ec0
We are working on Smart On FHIR EHR Launch at the moment. We are able to receive access_token, id_token etc. Once we prepare everything, we will redirect back to our FE page and set id_token in cookie. This solution works perfectly in Oracle Health Console test environment. However, when it comes to our client's real Cerner environment, seems like the cookie is blocked and our FE couldn't get the id_token from cookie (We guess, since we cannot get id_token on FE and we can see our BE works perfectly from logs). Any ideas on this? Thank you so much!