Agile Diagnosis (YC S11) Launches: Helping Doctors With Diagnosis
techcrunch.com
techcrunch.com
Of course I guess I shouldn't be too surprised since medical records keeping is still 30 years out of date. The fact that it's still common practice to share medical records by filling out a consent form and having one office fax paper forms to other is ridiculous.
I really hope we start to see disruption in this industry, so much potential for not only cost savings but improved care.
I don't think it is that ridiculous really. Assuming that the policy to require a signature from the patient stands, fax seems like a pretty natural choice for sending a paper form. Alternatively, they could take the time to scan the form then email it.
Ideally, both you and I would probably prefer something completely digital (both forms and health records). Towards that goal, I think the biggest problem would be interoperability. Someone like Kaiser could (and maybe they do) use all digital things between themselves, because they can enforce a uniform software platform.
One nice thing that I've seen about some digital medical record systems is that they print out nice reports. That is a good fallback system, so that you can still fax or email simple documents around.
But there are a LOT of smaller practices without an EMR or that don't want to go through the work of initial integration.
I believe there is a fine line between a good "decision aid" and "annoyance" and getting this right for an expert working in a chaotic, collaborative, time-sensitive, law-suit-attracting environment is extremely challenging.
2. http://en.wikipedia.org/wiki/Randomized_controlled_trial
3. http://www.informatics-review.com/wiki/index.php/Alert_fatig...
http://lingpipe-blog.com/2008/11/17/accident-involving-space...
3 days and 4 teams working on one guy's stomach ache? Was this guy a Saudi prince? Seriously, I think we've already established that the richest of the rich will always be able to get great health care; for myself, I just don't want to have to convince a doctor that a 103 degree fever and occlusion on a chest x-ray aren't caused by my asthma acting up. I don't want to go into the doctor after vomiting constantly for three days, just to be told "that happens". Personal care from a team (or a few teams) of doctors probably can't be beat, but machine diagnosis can probably beat any health care I've ever received.
There are certain kinds of diagnosis which are hard for humans and easy for computers, relatively, and some which are hard for computers and easy for people. (well, more likely hard for one and impossible for the other).
Truly novel things, where you aggregate data across multiple sites, are IMO the most amazing. Or, really rare but well defined conditions; doctors, especially busy ones, have a much smaller in-memory working set than computers.
I am very excited by machine diagnosis to augment humans. I don't think it will replace humans for a long time, but making humans even 1% better saves many lives and improves quality of life (and saves money).
All of that data entry would take time that physicians don't have. It would only be potentially worth doing for complex cases. Unless you can find a way to pay providers for doing the extra coding and data entry. Insurance generally won't pay extra for data entry beyond what they need for billing, and billing data isn't sufficiently detailed for diagnosis.
ML also doesn't account for human intuition and tacit knowledge. There are many subtle cues which experienced physicians can pick up on to make a diagnosis. It's impossible to codify them all; some are probably only noticed subconsciously.
If this flow chart was on the door of the patient room, my quality of care would have been MUCH better.
I don't think anyone can touch YC for the core value proposition, but domain-specific programs (for medical, enterprise, government, ...) might make some sense, and I could see the value in something like StartX as a pre-YC while-still-in-college thing.
Pretty excited to see someone is executing on this
This is the mindset that any disruptive enterprise must face. It's not like in the coding community, where spending a substantial amount of time writing seemingly trivial and boring tests -- i.e. an automated checklist -- is considered to be a necessary step in writing software.