Binary: 422 unprocessable entity

Skip to first unread message

Jay G

Jun 19, 2019, 9:44:42 AM6/19/19
to Cerner FHIR Developers

We are wondering if this site has a missing package similar to the other post about this error.

x-amzn-RequestId → d5724f64-8ed4-11e9-9184-b9971bf331cb   --- Accept: application/json+fhir
x-amzn-RequestId →9e15cacd-8ed4-11e9-8661-19cf06d63954  --- Accept: application/pdf

Thank you,

Yegor Hanov (Cerner)

Jun 19, 2019, 11:33:35 AM6/19/19
to Cerner FHIR Developers
Hi, Jay!

We have discussed this issue about a month ago over email in relation to the previous time you reported this problem [1].

Within the scope of MU3 requirements we certified the ability to generate CCD documents by virtue of operations on Binary [2] and DocumentReference [3].  Ability to retrieve general clinical documentation is not included within the scope of MU3 certified technology.  So, the issue you are running into now is that the client system is configured to meet the requirements of MU3 certified technology, but it is not configured to support the general document query.  This will likely occur at other client sites as well as you continue rolling out your app, so we would like to request that you disable the query for general clinical documentation.  

Feel free to use the operations on either Binary or DocumentReference to generate CCD if that is something that would be valuable for your end users.







-Yegor (Cerner)

Jay G

Jun 19, 2019, 1:11:39 PM6/19/19
Hello Yegor,

Thank you for the refresher. I'm going to put this info in the other threads as well.


You received this message because you are subscribed to a topic in the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this topic, visit
To unsubscribe from this group and all its topics, send an email to
To post to this group, send email to
To view this discussion on the web visit
For more options, visit
Reply all
Reply to author
0 new messages