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:
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?
If so, which client:
Application's Client ID and App ID, if relevant:
can add our FHIR client ID if needed.
Expected Result:
We can call the DocumentReference fhir route and receive data.
Actual Result:
X-Request-Id / Cerner-Correlation-Id / opc-request-id:
Date/time of the example:
X-Request-Id: /7EA70BBCA07950E64A7A404EB8D65782+Vdj2_Sele
Time: 2026-03-25T13:00:25Z
URL:
https://fhir-myrecord.cerner.com/r4/0e5efebe-b60c-458e-971a-ee39e08a2178/DocumentReference?_count=50&patient={patient}
Error response:
500 internal server error
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "fatal",
"code": "exception",
"details": {
"text": "Internal service error from resource store"
}
}
]
}
Various endpoints and resource types are throwing errors like the one documented above.