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 OPN Member? Yes
Have you signed up to be in the Healthcare Developer Track? Yes
Are you a registered Code Program member? Yes / No (working to find the answer)
Does your App have a presence on the Oracle Healthcare App Marketplace? Yes
Are you developing on behalf of an Oracle Health client? Yes
If so, which client: UTMC
Application's Client ID and App ID, if relevant: Application ID e36e039a-9960-42f1-8310-5ff8cd8a5c0c, client ID 9b98ee47-31c6-4cbc-b5c9-3af65f6d4e7b
Expected Result:
X-request ID would be returned in the header, as per documentation https://build.fhir.org/http.html#custom
Actual Result:
X-Request-Id / Cerner-Correlation-Id / opc-request-id: Unknown, see information below
Date/time of the example: 2024-10-22 10:13 Central Daylight Time
Our engineering team is working on pulling the x-request from the header and was not able to pull it. We're not sure if the header is only present some of the time or whether we are not pulling from the right location.
As a reminder, we are trying to add the x-request in order to adhere to the new Oracle requirement to have x-request IDs for re-validation, and we need to re-validate to add coverage, consent, and observations for a customer commitment for a go-live that is expected in January, and needs to be testing by December, ideally.
Our test launch was using the Cerner Citrix simulator with the following details (no x-request ID to share, since we weren't able to pull it):
Could you please either provide us with details from this call, or provide us with an example call that includes the x-request and point out where specifically we need to look in order to pull the x-request detail.