Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On patient selection screen, search breaks #23

Open
jmandel opened this issue Oct 18, 2019 · 3 comments
Open

On patient selection screen, search breaks #23

jmandel opened this issue Oct 18, 2019 · 3 comments

Comments

@jmandel
Copy link
Member

jmandel commented Oct 18, 2019

Search fails during the authorization process, with a "please try again later" error.

@vlad-ignatov
Copy link
Contributor

I haven't been able to reproduce this so far.

  • Is it in the patient browser (the popup before launch) or in the built-in patient picker that is rendered after launch?
  • Are there any specific search parameters that I should try with (if it is the popup)?
  • Or maybe you can share the page URL if it is the built-in picker?

The messages you were seeing are rendered from ajax error callback. It means that the client could not connect to the backend (FHIR server) for some reason. My guess is that it probably was some network-related issue that does not exist any more?

@jmandel
Copy link
Member Author

jmandel commented Oct 28, 2019

@GinoCanessa FYI. This was in the built-in patient browser that's rendered mid-launch (i.e., the one that allows the user to select a single patient for patient/ scopes). Here's a URL to reproduce:

  1. Navigate to http://launch.smarthealthit.org/v/r4/sim/eyJoIjoiMSJ9/auth/authorize?redirect_uri=http://test&client_id=test&state=test&aud=http://launch.smarthealthit.org/v/r4/sim/eyJoIjoiMSJ9/fhir&scope=launch launch/patient patient/*.read&response_type=code

  2. Type "smith" into search box

  3. Click "Search"


Expected behavior: filter the patient list based on the query
Observed behavior: " An error occurred loading patients, please try again later."
image

@vlad-ignatov
Copy link
Contributor

Got it, thank you! The reason for this was that the ":contains" operator wasn't enabled on our r4 server. I have enabled it now and should stop producing these errors. However, the search doesn't seem to work. I guess I'll have to wait about 60 min for HAPI to re-build its search index...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants