http://suzukilab.uchicago.edu/research.htm
IIRC they were outperforming the average radiologist on some tasks 10 years ago.
* Following behind the expert to give a second opinion
* Going ahead of experts to screen cases that should be read by an expert
Humans are imperfect and have their sources of unwanted variability. Algorithms may be less variable and reach near-human performance in controlled settings, but are often not flexible enough, not good at incorporating multi-modal patient history, and sometimes fail in spectacularly bad ways.
As soon as AI manages to show that capabilities, it's the end. Algorithms are much more accurate in combining all the available biomedical information needed to decide for diagnosis and therapy.
Another is the existence of edge cases. While not quite as bad as self-driving cars, they still require human review.
One radiologist I spoke with was under the impression that his field was going to disappear in the next n years. I don't think that will be the case entirely, but it will change.
One reason why image detection is ripe for this kind of "disruption" is that some of the highest paid medical fields (dermatology, radiology) basically employ expert image recognizers.
On the other hand, I'm not sure what percentage of health care costs goes toward employing doctors directly, but I don't think it's huge compared with the rest of the facility and equipment and administration cost.
The real benefit will come when people don't have to go in to the doctor at all. Which makes the smartphone "take a picture" aspect pretty sweet.
If this interests you and you have developed the expertise, there is another startup opportunity to explore -- please email me at [email protected]. We are bunch of machine learning PhDs, developing/publishing and commercializing deep learning algorithms for disease/risk identification from retinal photography. We play with millions of retinal images, and it's a lot of fun!
What if we haven't but we do?
We (Cardiogram) in particular are hiring for: mobile engineers (building an Apple Watch app used by 100,000 active users), storage and data infrastructure engineering (how are you going to store 10 billion sensor measurements those users are producing?), and machine learning engineers (now that we have the data, what can we do with it?).
In practice, many people fit multiple categories. There's a tight relationship between data infrastructure and machine learning, for instance, since new infrastructure often enables new algorithms. Likewise, building a new feature in Cardiogram for Apple Watch may give us 10x more labeled data, and therefore make the deep learning algorithm perform better. Interdisciplinary is good.
So, how true or false is it?
If you've developed expertise in deep learning and want to apply your skills to healthcare in a startup... please email me: [email protected]. My co-founder and I are ex-Google machine learning engineers, and we've published work at a NIPS workshop showing you can detect abnormal heart rhythms, high blood pressure, and even diabetes from wearable data alone. We're working on medical journal publications now based on an N=10,000 study with UCSF Cardiology.
Your skills can really make a difference in people's lives. The time is now.