Patient Search Name Issue

116 views
Skip to first unread message

Kimberly Berger

unread,
Feb 12, 2018, 8:56:10 AM2/12/18
to Cerner FHIR Developers
Hello. 

I have a question regarding the Patient Search functionality. I am doing a search on name and I have come up with some interesting results.

For instance doing a request with name=smith works fine:

The subsqeuent calls to get the rest of the results using the next link work fine as well.

However, I have found that various letters and letter combinations don't work. For instance if I want all patients who have a 'D' in their name I end up with an error on the 7th next link call. I am getting an error of:
{"Operation was unsuccessful, and returned status InternalServerError. OperationOutcome: Overall result: FAILURE (1 errors and 0 warnings)\r\n\r\n[ERROR] 
(no details)(further diagnostics: Endpoint returned a body with contentType 'text/html', while a valid FHIR xml/json body type was expected. Is this a FHIR endpoint?)."}

I have found this to be the case with letters: A, D, I, O, P, R, S and T.  When you add other letters most combinations work just fine, but for instance 'DOR' doesn't.  With these specifics, and also, the results when I change to a _count=1, it seems like there are specific patient(s) who have these letters in their name that have a bad data or formatting, which cause a bad response. 

One of the X-Request-Id: 1abd9f04803378b204816382e86d5a15

There was a previous message regarding a similar issue here: 

Is this something that someone could look into?

Eric Sornson (Cerner)

unread,
Feb 12, 2018, 10:26:26 AM2/12/18
to Cerner FHIR Developers
Kimberly thank you for notifying us.  We did find an issue with one of the patients being returned resulting in the error you're seeing.  We're looking into the issue.

- Eric (Cerner)

Avery Allen (Cerner)

unread,
Feb 12, 2018, 3:27:47 PM2/12/18
to Cerner FHIR Developers
Kimberly,

The issue should be resolved now.  Thanks again for letting us know about it.

- Avery (Cerner)


On Monday, February 12, 2018 at 7:56:10 AM UTC-6, Kimberly Berger wrote:

Kimberly Berger

unread,
Feb 13, 2018, 6:57:38 AM2/13/18
to Cerner FHIR Developers
Great thank you so much!

Kimberly Berger

unread,
Feb 13, 2018, 7:09:11 AM2/13/18
to Cerner FHIR Developers
This did work for most of the patients, however, I'm still getting an issue when I do P.  It is a different error though..

X-Request-Id: c3d599aecb54625895395f7d133ba0f7

I'm receiving: 422 Unprocessable Entity

Jenni Syed (Cerner)

unread,
Feb 13, 2018, 11:43:38 AM2/13/18
to Cerner FHIR Developers
Hi Kimberly,

It looks like too many patients qualified for that query. We do want to improve that message by returning an OperationOutcome that explains the call was too costly, but for now, you may want to try doing a more specific query to limit the number of results.

Regards,
~ Jenni

Kimberly Berger

unread,
Feb 14, 2018, 7:51:11 AM2/14/18
to Cerner FHIR Developers
Great, thank you for the explanation.
Reply all
Reply to author
Forward
0 new messages