404 Not found when trying to read Condition resource after creation

62 views
Skip to first unread message

Venkata Boddeti

unread,
May 9, 2018, 8:23:09 AM5/9/18
to Cerner FHIR Developers
If this is a question about an error or issue you are seeing, please fill out the following fields:

I have created a Condition resource and trying to read the created resource with the location header returned from the response. I received 404 Not found error.

X-Request-Id: 2a101768895ae6a88b74802c8c14f2e9

Issue Summary: (include links to documentation, and describe what you've tried so far. Do NOT include request or response bodies unless this is from our public sandbox)
X-Request-Id or CorrelationId: 2a101768895ae6a88b74802c8c14f2e9

Max Philips (Cerner)

unread,
May 9, 2018, 11:34:16 AM5/9/18
to Cerner FHIR Developers
Hi Venkata,

I can see in our logs that the correlation id you provided is a 404, but that was just the search, so it doesn't indicate anything about how that URL was returned in the Location header.  Looks like that Condition id does not exist, so it is returning a 404 as expected.

I just tried POSTing a Condition (diagnosis) and the location header I received was a valid URL that returned 200 for me.

Do you happen to have the correlation id from your POST? Or could you give any more information about the workflow that ended with that specific Location header?

Thanks,
Max (Cerner)

Venkata Boddeti

unread,
May 9, 2018, 12:52:38 PM5/9/18
to Cerner FHIR Developers
Hi Max,

Thanks.

There are 2 service calls in this flow.

1st Service call: Send post request to create a condition. Condition resource was created and I got the following response.

HttpResponseProxy{HTTP/1.1 201 Created [Date: Wed, 09 May 2018 16:43:37 GMT, Cache-Control: no-cache, Vary: Origin,User-Agent, Strict-Transport-Security: max-age=631152000, Server-Response-Time: 287.178812, X-XSS-Protection: 1; mode=block, Pragma: no-cache, X-Request-Id: cbeb4c9f6ca33286fdeaef2fa9782b7d, ETag: W/"38186593", X-Frame-Options: SAMEORIGIN, X-Content-Type-Options: nosniff, Expires: Fri, 01 Jan 1990 00:00:00 GMT, Last-Modified: Wed, 09 May 2018 16:43:37 GMT, Location: https://fhir-ehr.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Condition/d38186593, Status: 201 Created, Content-Length: 0, Content-Type: application/json+fhir] [Content-Type: application/json+fhir,Content-Length: 0,Chunked: false]}

2nd service call: Send Get request to read the condition resource created in the first call. The url that I used is https://fhir-ehr.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Condition/d38186593.  I got this url from Location in  HttpResponse from previous call.

I got the following response from this call: But I have created the resource in the previous call.

HttpResponseProxy{HTTP/1.1 404 Not Found [Date: Wed, 09 May 2018 16:43:38 GMT, Cache-Control: no-cache, Vary: Origin,User-Agent,Accept-Encoding, Strict-Transport-Security: max-age=631152000, Server-Response-Time: 198.073, X-XSS-Protection: 1; mode=block, Pragma: no-cache, X-Request-Id: 31fc8a4b77d036bbd5c97648deb24a75, X-Frame-Options: SAMEORIGIN, X-Content-Type-Options: nosniff, Expires: Fri, 01 Jan 1990 00:00:00 GMT, Status: 404 Not Found, Transfer-Encoding: chunked, Content-Type: text/plain; charset=utf-8] ResponseEntityProxy{[Content-Type: text/plain; charset=utf-8,Chunked: true]}}

I have used same access-code for both these calls. Please let me know what is the issue with this call. Condition should exist as per the response in the first call.

Thanks, Venkata

Max Philips (Cerner)

unread,
May 9, 2018, 1:05:07 PM5/9/18
to Cerner FHIR Developers
Hi Venkata,

Thanks for the additional info!

I have logged a ticket internally for us to investigate what is going on. We'll update this thread with further information.

Thanks,
Max (Cerner)

Max Philips (Cerner)

unread,
Aug 8, 2018, 5:07:21 PM8/8/18
to Cerner FHIR Developers
We've identified the root cause and have started work on a fix.

Thanks,
Max (Cerner)
Reply all
Reply to author
Forward
0 new messages