Archive for March, 2009
Healthcare Hacks on Twitter and Friendfeed
Posted by matt in Cool Hacks on March 10th, 2009
I rediscovered this quote a few days ago, and it got me thinking about that piece of software I mentioned in my previous post.
Q. Why is the software so dang simplistic?
A. In the early days of the Joel on Software forum, achieving a critical mass to get the conversation off the ground was important to prevent the empty restaurant phenomenon (nobody goes into an empty restaurant, they’ll always go into the full one next door even if it’s totally rubbish.) Thus a design goal was to eliminate impediments to posting. That’s why there’s no registration and there are literally no features, so there’s nothing to learn.
- Joel Spolksy in Building Communities with Software
I have a few skeleton pieces of that software sitting on my hard drive right now. While trying to figure out how to make it work like Joel’s message board, I remembered one of the other axioms of software development: The Best Code is No Code. It doesn’t make sense to write a new piece of software and waste others time learning a new piece of software when there are very good free alternatives already out there. They don’t even require me to futz around with servers and hosting. So instead I’m going to put my effort into building connections on Twitter and Friendfeed.
For the time being, anything cool and healthcare related that I find online is going into one of those two places. If I outgrow it I’ll move on, but I don’t think that’ll be an issue. Incidentally, I think that choosing to use these services instead of rolling my own is an example of what I’m trying to learn with this blog.
Great Healthcare Hacks will Empower the Real Problem Solvers
My attention tends to be drawn to Open Data because I want to write code to make sense of it. I love the thought of building a Googlesque system to crunch terabytes of data and somehow magically defeat the healthcare problem with elegant algorithms and raw computing power. I’m not the kind of person that can really solve this problem though.
The people that are going to solve the healthcare problem are doctors and policy makers and probably even a few quants (I hear that some of them aren’t too busy right now). Some of them are very good at what they do, but they don’t necessarily have the means (well, the quants might) to harness Open Data and really deploy the smart, data driven, solutions that I think are necessary. So where does this leave me?
Both the promise and the problem of an Open Source solution is that it relies wholly on collaboration. A brilliant spark by itself will flame out almost immediately, but many sparks connected by a combustible fuel can burn hot and bright. To switch metaphors, open healthcare does not necessarily need a Google, it instead needs its Facebook.
I’m writing this blog because I’m hoping it will help me discover what I can contribute to the solution. I like to think I can write really cool software, but I’m fully aware that even the greatest software is useless without a market or a community to exploit it. I’m not one of the primary solution providers I listed above so what I can build won’t solve the problem directly. My best hope is not to be the spark, but the fuel. If someone like me wants to hack the healthcare system, I need to do it by building an open network of people that can actually solve the problem.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=695f0e13-4cd9-4cd3-ae9c-1ea5879c40b3)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=634b2fbf-6fc6-44f1-8480-18d085af8dce)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=855177c4-db73-49e1-ab0d-7b7c37bd5b48)