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:
I am trying to pull the EHR from Cerner for my app (XYZ provider) and we were able to connect to sandbox successfully. and here are some follow up questions.
Developer questions:
-
What is relative frequency that authorization metadata will change and need to be dynamically discovered? What is relative risk of not using dynamic discovery ahead of user authorization? What would cause this data to change?
-
What is difference between application privacy "confidential" and "public". For our confidential app, we do not see it honoring scopes properly.
-
What is correct API scope for an individual logging in to authorize view of their own records? User or Patient
-
What additional steps (if any) are needed for production config? We can get data from Cerner Sandbox, but want to understand what other steps may be needed for prod readiness.
Are you an OPN Member? Yes / 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? Yes / No
Are you developing on behalf of an Oracle Health client? No
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: