Hello,
We have a Cerner app that we've been using successfully for the last few months to allow patients to connect to various Cerner production instances and fetch their medical records. We fetch various resource types, including DocumentReference and the corresponding Binary.
However, we've run into a handful of situations where we try to fetch the Binary resource from the DocumentReference and we get a 404 / "Resource not found" response.
Here are a few x-request-id headers for sample requests:
- af85cb30-a323-4115-880c-f1636a252a0e+1942_AFYI
- cdec89be-eca7-4b14-a3eb-c9d84b7d7ad9+9419_JmvC
- 3629fff5-20ae-4cc6-9a9e-d6934b98783c+4663_k0sK
- 743d86fc-34a1-44cd-893d-612d033f67d3+1448_gWG1
- etc.
I noticed that a similar issue was reported a while ago, but it sounds like this affected the Cerner sanbox and that it was fixed:
I'd appreciate help to understand what's causing the 404's and whether there's anything I can do on our side to fetch these resources successfully.
Thanks,
--Shahaf