Skip to Main Content

DSTU2 APIs (Millennium)

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.

signature_keys_unavailable error in non-prod FHIR app

John Howay5 days ago

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:

USC Keck Hospital

Application's Client ID and App ID, if relevant:

App ID: 550a3960-391c-43c7-b141-d161bdd2f8e2
Client ID: 2f4d465b-6b03-4edb-bbf3-a4034802c184

Expected Result:

On GET Patient call: https://fhir-ehr.sandboxcerner.com/dstu2/…/Patient/4618822

expected result is a 200 with payload.

Actual Result:

{ "code": 500, "message": "code=\"urn:cerner:error:oauth2:resource-access:signature-keys-unavailable\", error=\"signature_keys_unavailable\", subcode=\"unable_to_retrieve_credentials\"" }

opc-request-id: [/7719F41B209B4CFA8EE7ECFD78E0FC22/6EABBD91193744A68F5447D36EBD2FCE]
Date/time of the example: Tue, 27 Jan 2026 22:11:07 GMT

Thank you!

Comments
Post Details
Added 5 days ago
0 comments
8 views