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

Pattern Discovery / Categorize #167

Merged
merged 14 commits into from
Dec 28, 2016
Merged

Conversation

cgreene
Copy link
Member

@cgreene cgreene commented Dec 22, 2016

Motivation: We need to start filling in the sections with relevant literature.

Progress: This includes some thoughts on unsupervised EHR analysis and some extraction work via NLP. I have stubbed in portions for @sw1 and potentially @traversc. If you guys want to contribute you can either work of of this PR and make a pull request into this branch of my repo, or you can start writing now and create a PR against the repo once this goes through. My impression is that @sw1 is the lead on this portion given his previous volunteering.

Timing: I estimate that I'll get to wrap up the text around EHRs tomorrow. I just got a paper that I was struggling to get that seems relevant. I need some time to review it. I will also aim to talk some about the imaging work, but that may be a separate PR.

@cgreene
Copy link
Member Author

cgreene commented Dec 22, 2016

No reviewers directly named at this time - will name reviewers after I get to make some changes tomorrow.

researcher time and cost required to develop specific solutions, but it may not
lead to performance increases.

TODO: survival analysis/readmission prediction methods from EHR/EMR style data
Copy link
Contributor

@sw1 sw1 Dec 23, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any preference for how long? How detailed? For now:

Nevertheless, recent work has revealed one domain in which deep networks have proven superior to traditional methods. Survival analysis models the time leading to an event of interest from a shared starting point, and in the context of EHR data, often associates these events to subject covariates. Exploring this relationship is difficult, however, given that EHR data types are heterogeneous, covariates are often missing, and conventional approaches require the covariate-event relationship be linear and aligned to a specific starting point (@arXiv:1608.02158). Early approaches, such as the Faraggi-Simon feed-forward network, aimed to relax the linearity assumption, but performance gains were lacking (@doi:10.1016/S0167-9473(99)00098-5). Katzman et al. in turn developed a deep implementation of the Faraggi-Simon network that, in addition to outperforming Cox regression, was capable of comparing the risk between a given pair of treatments, thus potentially acting as recommender system (@arXiv:1606.00931). To overcome the remaining difficulties, researchers have turned to deep exponential families, a class of latent generative models that are constructed from any type of exponential family distribution (@arXiv:1411.2581v1). This resulted in a deep survival analysis model capable of overcoming challenges posed by missing data and heterogeneous data types, while uncovering nonlinear relationships between covariates and failure time. They showed their model more accurately stratified patients as a function of disease risk score compared the current clinical implementation (@arXiv:1608.02158).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sounds good, I have nothing more to add, except for possibly mentioning other non-linear methods. I can think of Random Forest used in survival analysis (@arxivL0811.1645)

@cgreene
Copy link
Member Author

cgreene commented Dec 23, 2016

Ok - given that @sw1 has some content to contribute this is probably a good time to remove the [WIP] tag and aim to merge. This is a bit more of a laundry list than I like, but once we get the pieces in place we should return for some deeper analysis. This has some placeholders for expected contributions.

@cgreene cgreene changed the title [WIP] Pattern Discovery / Categorize Pattern Discovery / Categorize Dec 23, 2016
@agitter
Copy link
Collaborator

agitter commented Dec 27, 2016

Acknowledging the review request, I should be able to do it within 24 hours

Copy link
Collaborator

@agitter agitter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no major comments, the general direction looks good to me. I left some minor questions, but feel free to keep things as they are.

@@ -137,3 +137,7 @@ interpretability problems, how can we best ensure reproducible models? What
might a clinician, or policy maker, need to see in a deep model in order to
influence healthcare decisions? Or, is deep learning a hypothesis generation
machine that requires manual validation?*

### Transfer learning/transferability of features
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you point out, transfer learning and multi-task learning has come up as a theme in many papers and domains. Do you suggest we defer most of that discussion in the domain-specific sections and coalesce it here? Or introduce it in the specific sections and have a cross-domain recap here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I prefer to introduce in specific sections and cross-domain recap here. I think it's going to be key in bio for many near-future advances.

@@ -19,7 +19,7 @@ tackle any of them? Are there example approaches whereby deep learning is
already having a transformational impact? I (Casey) have added some sections
below where I think we could contribute to the field with our discussion.*

### Major challenges
### Major Areas of Existing Contributions
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we settle on title case or lower case for section and sub-section headings?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should settle on one. I don't have a preference either way. What do you prefer? I suggest we make one quick PR to go through and match case as soon as we decide.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Went with sentence case.

all of this work, the researchers must work around a specific challenge - the
limited number of well annotated training images. To expand the number and
diversity of images, the researchers have employed approaches where they employ
adversarial examples [@doi:10.1101/095786] or first train towards human-created
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we haven't introduced adversarial networks earlier in the manuscript, it may deserve more attention.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely. These are adversarial examples though. They take the same base image and apply perturbations to it. I think you're probably thinking of something more like this - which is an adversarial network generated training example:
https://arxiv.org/pdf/1612.07828v1.pdf

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. You're right, my mind jumped to Generative Adversarial Networks when I saw adversarial.

limited number of well annotated training images. To expand the number and
diversity of images, the researchers have employed approaches where they employ
adversarial examples [@doi:10.1101/095786] or first train towards human-created
features before subsequent fine tuning [@doi:10.1007/978-3-319-46723-8_13]. The
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does "train towards human-created features" mean? It sounds interesting. Is this initializing weights using prior knowledge? Training a network with manually-defined features first and then using those weights to initialize a different network?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some features that have been developed in the past for this task. They first perform supervised learning where the task is to regress output nodes (if I recall correctly) towards those features. Then, after that process, they fine tune specifically on their supervised examples. This is perhaps a more efficient way (in terms of # of examples) to build the network by pushing it towards intermediate features that are thought to be useful.

with deep learning approaches. In recent work, Wang et al.[@arxiv:1606.05718]
analyzed stained slides to identify cancers within slides of lymph node slices.
The approach provided a probability map for each slide. On this task a
pathologist has about a 3% error rate. Their algorithm had about a 7% error
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to be more precise or is this the terminology used in the paper? Does their error rate include false positives and false negatives?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the language in the paper was pretty loose. The pathologist had no false positives, so theirs are all false negatives. For the algorithm it had the normal FP/FN tradeoff. I think we may want to be less precise here. I'll make that revision now.

evaluated were unigrams and bigrams. These are the counts for single words and
two-word combinations in a free text document. They subset the full set of words
and word combinations to the 400 most commonly used ones. The machine learning
algorithms that they employed (naive bayes, logistic regression, and deep neural
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Naive Bayes" or "naive Bayes"?


##### Opportunities

However, significant work needs to be done to move these from conceptual
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cgreene are you planing to write these placeholder sections or are you looking for help here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this point, bullets are probably good. Still have some more work to do on this but wanted to give @sw1 a chance to integrate his new text.

Additionally, unique barriers exist in this space that may hinder progress in
this field.

###### Data sharing and privacy?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@XieConnect are you planning to write something about this topic?

@cgreene
Copy link
Member Author

cgreene commented Dec 28, 2016

Based on @agitter I'm going to go ahead and merge this. This will allow @sw1 to have the token. @sw1 - please open a quick PR to add in your paragraph. Thanks!

@cgreene cgreene merged commit f878276 into greenelab:master Dec 28, 2016
@cgreene cgreene deleted the ehr-pattern-discovery branch December 28, 2016 18:23
dhimmel pushed a commit to dhimmel/deep-review that referenced this pull request Nov 3, 2017
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

Successfully merging this pull request may close these issues.

4 participants