Binary 422 Error

[Jay G]

Hello,

We are getting this error when requesting a Binary : 422 Unprocessable Entity (WebDAV) (RFC 4918) 

This happens when using both 'application/json+fhir' and the 'application/pdf' content-type from the DocumentReference entry.

Thanks,

Jay

[Max Philips (Cerner)]

Hi Jay,

Per group guidelines, can you provide an X-Request-Id response header to help us investigate?

Thanks,

Max (Cerner)

[Jay G]

This one is the most recent:  X-Request-Id →c2e52535-6ab6-11e9-8580-f198e3c55e86

[Max Philips (Cerner)]

Hi Jay,

Thanks for the information. I see you are working in a different domain than our public sandbox. We will confirm that onboarding has been fully completed for this domain.

I may reach out to you privately past this message.

Thanks,

Max (Cerner)

[Jay G]

For posterity's sake:

Within the scope of MU3 requirements we certified the ability to generate CCD documents by virtue of operations on Binary [1] and DocumentReference [2].  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.

[1] https://fhir.cerner.com/millennium/dstu2/infrastructure/binary/#autogen-ccd-if

[2] https://fhir.cerner.com/millennium/dstu2/infrastructure/document-reference/#operation-docref