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

Define Search scenario #3

Open
1 task
HodGreeley opened this issue Aug 7, 2017 · 1 comment
Open
1 task

Define Search scenario #3

HodGreeley opened this issue Aug 7, 2017 · 1 comment

Comments

@HodGreeley
Copy link
Contributor

  • Sachin to discuss with Steve Yen
@HodGreeley HodGreeley changed the title Add Search Define Search scenario Aug 7, 2017
@HodGreeley
Copy link
Contributor Author

Quick follow up. I spoke with Marty in more detail. This plan seems good, with some possible additions to the data model to give more fields to search/rank for FTS.

Rob, I think this impacts the UI quite a bit on a couple of pages. Take a look and let’s sync up.

Thanks,
Hod

On 9/25/17, 7:29 AM, "Marty Schoch" [email protected] wrote:

(sending again as I intended to reply-all)

This sounds good to me, with one addition that the search can find matches in multiple fields (this was something Ravi mentioned wanting to highlight as well).

marty

On Sun, Sep 24, 2017 at 9:56 AM, Mike Carey [email protected] wrote:
For Analytics, let’s have a form that takes parameters (diagnosis name and some patient range attributes like age, weight, height, gender and also a date range) and plots the numbers of diagnoses with the given name (e.g., Mongoitis) for patients falling in the specified ranges (age, height) in the specified date range. Y is count and X is yr/mo. Under the hood is a SQL++ join/group/agg query on patient id (which is not the CB k/v key). This is what we talked about after the meeting on Thursday; I still like it. THEN – if you click on a point on the graph – let’s bring up a scrollable list of the patients and their attributes. (So later we can drill down and see the latest patients and new attributes, etc.)

For Search, let’s have a form that takes keyword parameters – multiple of them – and searches the encounter’s text field. One could look, e.g., for encounters with keywords “vomiting”, “nausea”, “fever”, “joining”, “scaling” – to look for patients who are having trouble scaling and joining and who are getting sick over it. ☺ The differentiator between Analytics and Search is that presumably the terms will be stemmed (so “join”, “joins”, “joining”, … all match) and we can relevance-rank the results by the degree of match (a record that matches more terms ranges higher, e.g., “Patient presents with a cluster that can’t seem to scale or do joins well, and has been experiencing daily fever, chills, nausea, and headaches”.)

Cheers,

Mike

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

No branches or pull requests

1 participant