Workflow or API calls:
When a Millennium user launches our embedded application from a patient chart, we use the Encounter resource ID returned as part of the launch context to make a request to the Encounter endpoint for the provided resource ID.
This is a very rare occurrence.
Background Information:
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
Are you an OPN Member? Yes
Have you signed up to be in the Healthcare Developer Track? Yes
Are you a registered Code Program member? Yes
Does your App have a presence on the Oracle Healthcare App Marketplace? Yes
Are you developing on behalf of an Oracle Health client?
If so, which client:
Application's Client ID and App ID, if relevant:
Client ID: 7f0d0b79-8c30-43ae-a149-9e0c2340daac
App ID: 4f3237fc-83ac-4326-a306-be961b29d9fe
Expected Result:
The request for an Encounter resource using the resource ID provided by the system the request is destined for returns the resource successfully.
Actual Result:
The request for an Encounter resource using the resource ID provided by the system the request is destined for returned a 404 error with the following OperationOutcome as the response body:
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "not-found",
"details": {
"text": "Resource not found"
}
}
]
}
X-Request-Id : /BA994362C916BAC81F18E161F97E84D0+xlin_loXK
Date/time of the example: 7/28/2025 9:02:11 AM Central Time
What scenario(s) would cause Oracle to provide an Encounter resource ID as part of an embedded application launch that does not exist when a request is made for that ID to the Encounter FHIR endpoint within moments of the application launch?