(Resending) Creating Communication reminder fails with Invalid Request - what's wrong with it?

[Dmitry Lipin]

Hi Team,

We are trying to create new Communication of reminder category in public FHIR sandbox (secured) environment.


$ cat /tmp/create_communication_minimal

{
  "resourceType": "Communication",
  "status": "completed",
  "category": [
    {
      "coding": [
        {
          "system": "http://terminology.hl7.org/CodeSystem/communication-category",
          "code": "reminder"
        }
      ]
    }
  ],
  "priority": "urgent",
  "topic": {
    "text": "CDI Query"
  },
  "recipient": [
    {
      "reference": "Practitioner/12742069"
    }
  ],
  "sender": {
    "reference": "Practitioner/12753114"
  },
  "subject": {
    "reference": "Patient/12724071"
  },
  "payload": [
    {
      "contentAttachment": {
        "contentType": "text/plain",
        "data": "Q29tbXVuaWNhdGlvbg=="
      }
    }
  ]
}

$ curl -v -H Content-Type:application/fhir+json -H 'Authorization: Bearer ...' https://fhir-ehr.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Communication -X POST --data @/tmp/create_communication_minimal


We are getting 400 Bad Request with only details "Invalid request" provided.

< HTTP/1.1 400 Bad Request
< Content-Type: application/fhir+json; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Date: Thu, 20 Apr 2023 05:59:24 GMT
< Cache-Control: no-cache
< Referrer-Policy: strict-origin-when-cross-origin
< Server-Response-Time: 711.744601
< Strict-Transport-Security: max-age=631152000
< Vary: Accept, Origin
< X-Content-Type-Options: nosniff
< X-Download-Options: noopen
< X-Frame-Options: SAMEORIGIN
< X-Permitted-Cross-Domain-Policies: none
< X-Request-Id: d452ef62-240a-4e7c-a285-fade73a221da+0492_IpPM
< X-Runtime: 0.711706
< X-Xss-Protection: 1; mode=block
< X-Cache: Error from cloudfront
< Via: 1.1 4a1ea8b67dc2325b2469ed51d3e186ac.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: JFK50-P2
< X-Amz-Cf-Id: 3BsK_3RA07SZD2j4MKOEUyGloXYfCVLiVdFYsMPUFVxZufLRjnQwcg==
<
* Connection #0 to host fhir-ehr.cerner.com left intact
{"resourceType":"OperationOutcome","issue":[{"severity":"error","code":"invalid","details":{"text":"Invalid request"}}]}

What is the actual reason of the failure? How we can debug it ?

Thanks,
Dmitry