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.

Getting 422 Unprocessable Entity (WebDAV) (RFC 4918) while using DiagnosticReport to post a document

Anvit SinghAug 25 2025 — edited Aug 25 2025

Workflow or API calls:

Reminder: If this is referring to a client domain or EHR activity—not the public sandbox—do not include API request data or live patient data.

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
Are you a registered Code Program member? Yes
Does your App have a presence on the Oracle Healthcare App Marketplace? Yes

Are you developing on behalf of an Oracle Health client?
If so, which client:

Application's Client ID and App ID, if relevant:

Expected Result:

Actual Result:{

"resourceType": "OperationOutcome",

"issue": \[

    {

        "severity": "error",

        "code": "invalid",

        "details": {

            "text": "Unprocessable entity"

        }

    }

\]

}

X-Request-Id / Cerner-Correlation-Id / opc-request-id:
Date/time of the example: Mon, 25 Aug 2025 18:29:41 GMT

Here is the exact curl from Postman for your reference :-

curl --location 'https://fhir-ehr.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/DiagnosticReport' \
--header 'Accept: application/fhir+json' \
--header 'Authorization: Bearer <redacted> \
--header 'Content-Type: application/fhir+json' \
--data '{
"resourceType": "DiagnosticReport",
"category": [
{
"coding": [
{
"code": "LP29708-2",
"display": "Cardiology",
"isUserSelected": false,
"system": "http://loinc.org"
}
],
"text": "string"
}
],
"code": {
"coding": [
{
"code": "2820587",
"system": "https://fhir.cerner.com/ec2458f2-1e24-41c8-b71b-0e701af7583d/codeSet/72",
"userSelected": true,
"display": "Discharge Note-Nursing"
}
],
"text": "Cardiology"
},
"effectivePeriod": {
"start": "2025-06-28T12:49:16.209Z",
"end": "2025-06-28T12:49:16.209Z"
},
"identifier": [
{
"use": "usual",
"type": {
"coding": [
{
"code": "Coding",
"system": "http://snomed.info/sct",
"version": "4.0.1",
"display": "test",
"userSelected": true
}
],
"text": null
},
"system": "http://hl7.org/fhir/sid/us-ssn",
"value": "11182456"
}
],
"performer": [
{
"reference": "Practitioner/3332081"
}
],
"resultsInterpreter": [
{
"reference": "Practitioner/3332081"
}
],
"presentedForm": [
{
"contentType": "application/pdf;charset=utf-8",
"title": "Remote Pacemaker Device Check",
"url": "http://snomed.info/sct",
"data": "JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIF",
"creation": "2025-06-28T12:49:16.209Z"
}
],
"status": "final",
"subject": {
"reference": "Patient/14756524"
}
}'

Comments
Post Details
Added on Aug 25 2025
4 comments
51 views