Workflow or API calls:
Accessing FHIR R4 resources (Patient, Encounter, Condition, Procedure) via the patient-specific endpoint.
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:
- Using
fhir-myrecord.cerner.com as the base URL
- Access token issued with
persona: patient
- Patient ID (from fhirUser): 12724069
- All requests return 502 Bad Gateway
- We confirmed that the token is valid and not expired
Accept: application/fhir+json and Authorization headers are included
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
Are you an OPN Member? No
Have you signed up to be in the Healthcare Developer Track? No
Are you a registered Code Program member? No
Does your App have a presence on the Oracle Healthcare App Marketplace? No
Are you developing on behalf of an Oracle Health client?
If so, which client:
Application's Client ID and App ID, if relevant:
Expected Result:
Actual Result:
X-Request-Id / Cerner-Correlation-Id / opc-request-id:
Date/time of the example: