Error when adding a new appointment to the Cerner R4 sandbox

[Yu Xu]

Hello,

I'm adding an appointment to the sandbox for my project tests.

I copied the example JSON request data from https://fhir.cerner.com/millennium/r4/scheduling/appointment/#create

and updated a few of fields for testing. Please refer to the attached file.

The patient and location IDs I put into the request are both valid.

I always get the error:

{"resourceType":"OperationOutcome","issue":[{"severity":"error","code":"invalid","details":{"text":"Unprocessable entity"}}]}

Please help.

Thank you very much,

Yu Xu

[Benjamin Eichhorn (Cerner)]

Hi, 

Per our group guidelines, could you please post the X-Request-Id associated with your request? This is located in the headers of the response.

Thanks,

Ben (Cerner)

[Yu Xu]

Hello Ben,

All the headers pulled from the HTTP response message are copied below:

---------------- Headers in Response ----------------
Connection: keep-alive
Date: Wed, 28 Oct 2020 15:31:14 GMT
Cache-Control: no-cache
Server-Response-Time: 35.870321
Vary: Origin
X-Request-ID: a70aafaf-61ad-4da4-869f-668f1dcd3caf
X-Runtime: 0.035803
X-Cache: Error from cloudfront
Via: 1.1 7bae3892a4b9b7cb601b5d663d98de74.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ORD51-C2
X-Amz-Cf-Id: KibA6Sv-i3q9YltaSQKP1Bt7_Sj47S8yRlwXE8sVq_n2vdRK6hk33g==
Content-Type: application/fhir+json; charset=utf-8
Content-Length: 133

Thank you very much,

Yu

[Aaron McGinn (Cerner)]

The X-Request-ID you provided was for a Patient create, not Appointment. You will need to provide the X-Request-ID for the Appointment create failure.

-Aaron (Cerner)

[Sharon Wang]

Hello Aaron,

I'm sorry that I switched to adding patient before copying the headers.

I ran the adding appointment request again and headers are shown below:

---------------- Headers in Response ----------------
Connection: keep-alive

Date: Wed, 28 Oct 2020 18:34:09 GMT
Cache-Control: no-cache
Server-Response-Time: 272.191046
Vary: Origin
X-Request-ID: ab484d53-289a-43a1-8d44-9a1d0b685c3b
X-Runtime: 0.272095

X-Cache: Error from cloudfront
Via: 1.1 7bae3892a4b9b7cb601b5d663d98de74.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ORD51-C2

X-Amz-Cf-Id: vWjsUUFmjkt_MDi6kjmcL7A7AWIjxISaOTbE0Hx8HbIB1LMOM1i3eQ==
Content-Type: application/fhir+json; charset=utf-8
Content-Length: 125

The URL is https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/Appointment

Sorry again and THANK YOU,

Yu

On Wed, Oct 28, 2020 at 12:45 PM 'Aaron McGinn (Cerner)' via Cerner FHIR Developers <cerner-fhir...@googlegroups.com> wrote:

The X-Request-ID you provided was for a Patient create, not Appointment. You will need to provide the X-Request-ID for the Appointment create failure.

-Aaron (Cerner)

--
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 https://groups.google.com/d/topic/cerner-fhir-developers/FWvGjXXUq_o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/dd92160b-797c-4b93-8ce5-ddb56efa9d3ao%40googlegroups.com.

--

Sharon Wang

[Aaron McGinn (Cerner)]

It looks like a mapping does not exist in the domain for that Appointment.serviceType. You may consider passing in a proprietary code instead [1]. This would remove the necessity of having the appropriate mappings in place.

[1] https://fhir.cerner.com/millennium/r4/proprietary-codes-and-systems/#code-set-14249-scheduling-appointment-type-synonyms

-Aaron (Cerner)

[Sharon Wang]

Hi Aaron,

I used following service type (complete JSON data is attached), and got the same error:

             "serviceType": [
                {
                  "coding": [
                    {
                      "code": "5038369",
                      "system": "https://fhir.cerner.com/ec2458f2-1e24-41c8-b71b-0e701af7583d/codeSet/14249",
                      "display": "Office Visit -Return",
                      "userSelected": true
                    }
                  ]
                }
              ],

The headers are shown below:

Connection: keep-alive
Date: Thu, 29 Oct 2020 02:38:53 GMT
Cache-Control: no-cache
Server-Response-Time: 464.237118
Vary: Origin
X-Request-ID: 29d3802f-77c5-4cff-8fb3-9d6484b8342c
X-Runtime: 0.464154
X-Cache: Error from cloudfront
Via: 1.1 e01091b7c39d5f291f684f22eebc396f.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ORD51-C2
X-Amz-Cf-Id: rJlElYX2j3D7qSAEzZETJAUYQGyE9X-FzdBASGfjo2Cf6K-9jZQt4Q==

Content-Type: application/fhir+json; charset=utf-8
Content-Length: 125

Thank you very much,

Yu

--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/5a5a2dde-42f3-43b8-832e-a1abe4b609f9o%40googlegroups.com.

--

Sharon Wang

[Keifer Laverty (Cerner)]

Hello Yu,

It doesn't look like that the service type you are using exists in the domain you are working in. We were able to find this service type in the domain that you can use for testing:

"serviceType": [
  {
    "coding": [
      {
        "system": "https://fhir.cerner.com/ec2458f2-1e24-41c8-b71b-0e701af7583d/codeSet/14249",
        "code": "31732041",
        "display": "Same Day",
        "userSelected": true
      }
    ],
    "text": "Same Day"
  }
]

We will also work to update the documentation on fhir.cerner.com to reflect this.

-Keifer (Cerner)

[Yu Xu]

Hi Keifer ,

I modified my service type as copied below, per your suggestion:

              "serviceType": [
                {
                  "coding": [
                    {
                      "system": "https://fhir.cerner.com/ec2458f2-1e24-41c8-b71b-0e701af7583d/codeSet/14249",
                      "code": "31732041",
                      "display": "Same Day",
                      "userSelected": true
                    }
                  ],
                  "text": "Same Day"
                }

              ],

I also modified the start/end datetime to reflect "Same Day" visit but still got "Unprocessable entity" error.

Not sure if it's related to the same issue or other issue.

X-Request-ID: e37767b8-a63b-4742-a3bc-804ece56496e

Much Appreciate your supports.

Thanks,

Yu

[Madhur Rajendran (Cerner)]

Hi Yu,

I apologize, we're currently having issues with the mappings for serviceType. We're currently working on getting that fixed, but until then you won't be able to create appointments in a 'proposed' status.

I'll post back on this thread when we've fixed the issue, until then the workflow for creating an appointment with a 'booked' status should still work correctly.

Thanks,
Madhur (Cerner)

[Yu Xu]

Hi Madhur ,

Thanks for the update,

Yu

[Marcus Nilsson]

Hi Madhur,

I'm experiencing same problem today (422 unprocessable entity) when trying to create Appointments, both with 'proposed' and 'booked' status which you suggested as workaround.

Copied body straight from example: https://fhir.cerner.com/millennium/r4/scheduling/appointment/#example---booked-appointment

Any updates?

(My x-request-id if you need it)
X-Request-Id: 5f21a03c-c2c9-41ed-916d-3973af58c23e)

Best regards,

Marcus Nilsson

[Sydne Anschutz (Cerner)]

Hello Marcus, 

Thank you for reaching out to us with the correlation id, the issue you're seeing isn't the same as the one originally posted in this thread. Your error is occurring because the slot is already used. 

The examples on fhir.cerner.com are are non-normative and replaying them in the public sandbox is not guaranteed to yield the same results as explained under the notes section of the response here: https://fhir.cerner.com/millennium/r4/scheduling/appointment/#example---booked-appointment

To work around this issue please refer to this post: https://groups.google.com/g/cerner-fhir-developers/c/yqEmJYcCAWs/m/xUvYZYgYAwAJ 

Regards,

Sydne (Cerner)

[Marcus Nilsson]

Thank you very much for your response!

Would i be possible to get that kind of error information (slot already used) in response to POST, in the operation outcome, instead of just "Unprocessable entity" ?

And also, how is the original issue, not being able to create as "proposed", going ?

Regards,

Marcus Nilsson

[Sydne Anschutz (Cerner)]

Hi Marcus,

We will take your suggestion into consideration, but we can't comment on if and when we'll be making that enhancement. As for the original issue, it is still being worked on and I will post back on this thread when the issue is resolved.

Thanks,

Sydne (Cerner)