Workflow or API calls:
PDF Binary reads returning NotFound due to misconfigured persona templates
Background Information:
Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:
Are you an OPN Member? Yes
Have you signed up to be in the Healthcare Developer Track? Yes (I believe so)
Are you a registered Code Program member? Yes / No
Does your App have a presence on the Oracle Healthcare App Marketplace? Yes
Our application currently connects successfully to numerous Oracle/Cerner tenants but we have one tenant that is unable to configure their Document concept/B2B persona template to successfully permit us access to some types of progress notes. The client has raised an SR but has not had it resolved yet. One thing that is not clear is whether there is any configuration of the user/persona that would allow more than one Document/B2B template for the API (i.e. one per application accessing the API or one for a manual user at a GUI and a different one for the API) or if there is only one global version.
If the template is global to the API as a whole would it need to be a superset of all the document types that all applications require? Presumably this is all configured solely within Bedrock and not in Clinical Document Viewer?
I've been given different answers depending on who was asked in the past. and I was hoping for something definitive.
Many thanks!
Are you developing on behalf of an Oracle Health client?
If so, which client:
Application's Client ID and App ID, if relevant:
Application ID
847065ab-9b41-4b54-9084-d1a11c79c5e0
Client ID
d68da736-2824-4ebb-a452-701af4ccce39
Expected Result:
Successful return of a binary PDF document.
Actual Result:
StatusCode: NotFound
{"resourceType":"OperationOutcome","issue":[{"severity":"error","code":"not-found","details":{"text":"Resource not found"}}]}
X-Request-Id / Cerner-Correlation-Id / opc-request-id:
{X-Request-ID=/1E93B2115697291A0C0804D30821C4DB+gBQ5_LdsT}
{opc-request-id=/1E93B2115697291A0C0804D30821C4DB/29559F09E3606E913156881BB40EA4B2}
Date/time of the example:
{Date=Mon, 09 Jun 2025 18:27:28 GMT}