Skip to Main Content

Clinical APIs (EHR)

Announcement

For information related to the Oracle Partner Network (OPN) Industry Healthcare Track please visit our OPN Industry Healthcare Program page.

For specific questions related to Oracle Partner Network (OPN), please contact Partner Assistance.

Millennium FHIR and non-FHIR API Specifications and Supporting Documents can be found HERE on docs.oracle.com
Soarian FHIR API Specifications and Supporting Documents can be found HERE on docs.oracle.com.

Error 404 'Default Backend' on Previously Working URL

Luis OjedaApr 6 2026

Workflow or API calls:

METHOD: GET

URL: https://api.sandboxcernermillennium.com/<tenant>/message/20241001/patientMessages/inboxItems?createDateTimeGreaterThanOrEqualTo=2020-01-01T00:00:00Z&createDateTimeLessThanOrEqualTo=2025-11-04T11:31:03Z&patientId=9859041

Hello everyone,

I'm experiencing an issue with an integration that suddenly stopped working, and I would appreciate your help.

I have an Oracle Health EHR URL/endpoints that was working perfectly until a few days ago. However, when making the same request today, I'm receiving the following error:

**Error:** Default backend - 404 not found

This behavior is affecting all the existing endpoints for EHR that i'm consuming. Please let me know if you need a specific information that I can share.

1. Are there any known changes to Oracle Health EHR infrastructure or endpoints that could cause this behavior?

2. Does the "default backend" message suggest a load balancer or routing configuration issue?

3. Is there any communication about maintenance or API changes? Any guidance would be greatly appreciated.

Thank you in advance.

Expected Result:

HTTP 200 Success

{

"items": [

{ “DATA” }

]

Actual Result:

X-Request-Id / Cerner-Correlation-Id: /EA54595A8F614B85854E7F267401C66B+4388 / opc-request-id: /EA54595A8F614B85854E7F267401C66B/31655F6E30A245008850C172D4AD660F
Date/time of the example:Mon, 06 Apr 2026 18:10:09 GMT

Comments
Post Details
Added on Apr 6 2026
0 comments
57 views