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

Section Status: Electronic health records #967

Open
cgreene opened this issue Jul 23, 2019 · 6 comments
Open

Section Status: Electronic health records #967

cgreene opened this issue Jul 23, 2019 · 6 comments

Comments

@cgreene
Copy link
Member

cgreene commented Jul 23, 2019

We should consider between the options of:

  • Cut
  • Update
  • Expand
@spiros
Copy link

spiros commented Nov 21, 2019

Happy to work on this section, if there is still interest.

@agitter
Copy link
Collaborator

agitter commented Dec 2, 2019

Thanks for offering to help @spiros. It's unclear how active the manuscript update is right now. I added some thoughts in #810 (comment), and we'll see what the other project maintainers think.

@spiros
Copy link

spiros commented Dec 3, 2019

Sounds good!

@cgreene
Copy link
Member Author

cgreene commented Feb 10, 2020

I am excited to get this project rebooted and going. With #986 I'm adding infrastructure to handle authors from multiple versions. Could you describe what portions you think should be cut, updated, or expanded?

As the review is quite long, we probably won't want to expand sections without at least some cut in other areas. Fortunately, there may be recent reviews that we could cite if there are topics better dealt with by a more specialized review but that should still be covered.

@spiros
Copy link

spiros commented Apr 9, 2020

I think we could restructure the sections based on three main use cases

  1. Risk prediction - how can ML/AI used with EHR to enable risk prediction of adverse outcomes
  2. Phenotyping - high-throughput phenotyping approaches using semi-supervised learning to tackle the labelling problem
  3. Subtype discovery - identify, validate latent disease types (static or longitudinal)

We can then weave in some cross-cutting things like embeddings (which can be used for all three use cases etc). I would cut out any NLP-specific tasks (like extracting info from radiology reports or similar) and move them in their own section.

It might be a good idea to add a paragraph on challenges such as interpretability, noise, biases in EHR data etc.

@cgreene
Copy link
Member Author

cgreene commented Apr 12, 2020

@spiros : could you weigh in over at #1005 about positioning for this section? We're considering a reorganization and this is one of the trickier ones. Does it go with genetics, where many immediate applications are, or does it belong with text/images?

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

3 participants