Skip to Main Content

R4 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.

GET Binary 400 Error

Joseph ChaplineMar 27 2024

My application is receiving the following 400 error from Cloudfront when making a GET Binary request. My application does make other successful FHIR requests before this specific request fails.
I have seen a few other posts with the same error on the old Google Cerner forums, so I was wondering if anyone has seen this error and can provide me with a concrete solution. The old posts did not provide solutions.

Workflow or API calls:

GET Binary https://fhir-ehr.cerner.com/r4/{cust-id}/Binary/XR-{document-id}

Expected Result:

200 Success with Binary data

Actual Result:

I'm not receiving an X-Request-Id because the request is failing before hitting the FHIR server

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">

<TITLE>ERROR: The request could not be satisfied</TITLE>

</HEAD><BODY>

<H1>400 ERROR</H1>

<H2>The request could not be satisfied.</H2>

<HR noshade size="1px">

Bad request.

We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.

<BR clear="all">

If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

<BR clear="all">

<HR noshade size="1px">

<PRE>

Generated by cloudfront (CloudFront)

Request ID: 2iOFGONUn0O0L_Ssh_JoG3_guvxtnbER4PbweNgw54rEfY399HMpHw==

</PRE>

<ADDRESS>

</ADDRESS>

</BODY></HTML>

Comments
Post Details
Added on Mar 27 2024
1 comment
484 views