Archive for February, 2009

A Vision for Open Healthcare (v0.1)

Yesterday, I used the term “Open Systems” when trying to understand Haque’s four pillars, but I didn’t really explore why I find open systems so interesting.  The topic, and whole purpose, of this blog is to figure out how to hack the modern healthcare system so that creative users can find ways to improve healthcare for themselves and for everyone.  Open Systems are one way to achieve this goal by making the system hackable.

When we make a system hackable, uses emerge that the designers and administrators never intended.  Sometimes those uses exploit the system (think email spam), and we must actively manage against them.  However, these novel emergent uses often add considerable value.  My hope is that open healthcare can save more lives at lower cost because it can recruit and deploy so many more participants than a closed, top-down system would even consider.

There is a lot of effort going into standardizing healthcare in every way from electronic medical records to treatment protocols.  What these standards have in common though is top-down specification and increasingly complex implementations.  Not only do these forces generally inhibit mass creativity, they actively discourage it.  Mass creativity is a threat to traditional hierarchies.

Healthcare is the epitome of complexity.  Not only is it a very hard problem requiring extreme amounts of talent to carry out even the most basic functions, there is so much money involved that the politics and red tape put every action under the microscope, thus regimenting the whole practice.  There is not an open system in sight.

The problem, though, is that bureaucracy doesn’t scale and it doesn’t adapt.  Past a certain point, it takes more effort to maintain the bureaucracy than it does to do the actual job.  To make matters worse, the bureaucracy is too slow to adapt to change.  It can’t evolve and improvise.  But how do we ensure quality of care while at the same time harnessing mass creativity?  The answer is in a little slight of hand.  What we really want is complex behavior, not complex systems.

Dee Hock, founder of Visa observed that:

Simple, clear purpose and principles give rise to complex and intelligent behavior. Complex rules and regulations give rise to simple and stupid behavior.

~ Dee Hock Quotes

The problem is in finding the right set of simple rules.

Coming from the technology world, I have a lot of faith in the lessons that the web has taught us.  In this realm, simple, open architectures and a philosophy of information sharing have lead to a vast ecosystem that simply didn’t exist 20 years ago.  While I have no illusions about silver bullets and quick fixes, applying some of the lessons of the web should get us a long way towards the goal of a fair and effective healthcare system.

There are two important lessons from the web that I want to address in the near future: Open Source and Standards Based APIs (call it Open Data?).  Individually and taken together, these areas of the web have made contributions on the same scale as many multi-billion dollar companies.  And they’ve done it on a shoestring.  Of course, I doubt that such a thing as an open source surgeon will ever exist, but adding billions of dollars of value (without billions in costs) on top of the existing healthcare infrastructure would be simply revolutionary.

Reblog this post [with Zemanta]

, ,

No Comments

Hacking Third-World Healthcare with Mobile Phones

Via Change.org, I discovered this story about Mobile Healthcare.  Briefly, a Stanford undergrad and co-founder of FrontlineSMS:Medic is training Malawians to use cell phones to coordinate community health activities.  What I find interesting is how they’re able to use relatively inexpensive and donated cell phones as a stand in for the sophisticated emergency response systems we have here.

Obviously, public health systems in the US can’t to coordinate their activities, but this looks like its an early stage disruptive innovation.  It’s cheap, it’s “good enough” where it’s deployed, and it’s sufficiently ad-hoc that it could start popping up unexpectedly in scenarios that normally call for more sophisticated solutions.  That’s the classic pattern of disruptive innovation.

More info:

Reblog this post [with Zemanta]

, ,

No Comments

Health Care and Haque’s Four Pillars of Smart Growth

Umair Haque always raises some interesting questions.  At least since I’ve started reading his blog, he’s focused on reconcieving business to be more sustainable, and in his post from Jan. 30th, he proposes four more pillars for smart growth:

  1. Outcomes, not income
  2. Connections, not transactions
  3. People, not product
  4. Creativity, not productivity

I find them intriguing, but as a recovering libertarian, a little alien. Well, since this blog is all about learning (for me in particular), I’m going to dive right in anyway and try to make sense of them in terms of health care and open systems.

Open systems really dovetail well with Haque’s four pillars.  The goal of open system is really about creating value by giving the user’s control.  That by itself satisfies 1, 3, and 4.  Number 2 actually enables the openness by making it possible to achieve a critical mass and make the system self sustaining.

Health care, on the other hand, is mired in closed, top down systems.  Insurance companies (or governments) are worried about income (or costs).  The focus is on proceedures, not outcomes.  And I don’t see how creativity can exist in such a system.

Of course, the system exists this way for a reason.  It’s not malice.  It’s just that high assurance requires some amount of bureaucracy.  On the other hand, anyone that can figure out how to build openness into, on top of, or around the system and apply Haque’s four pillars probably will stand to do a lot of good and maybe make some money in the process.

Reblog this post [with Zemanta]

, ,

No Comments

There is a point to this… really!

I’m not a healthcare expert.  I don’t have any training in the field, and I don’t work in the field.  I suppose some people could call me a hacker.  I’m a hacker in the sense that I build software systems for a living, and some of them might be worth mentioning.

(Just to clarify, hackers make cool things, they don’t break into computers.  Those are crackers)

So, I have no expertise to share with this blog.  Instead, I’m using it to learn.  The state of healthcare in this country hits pretty close to home, and coming from the software field, I think its strange that there are so few hackers tackling this problem.  

What I’m looking for are the grassroots innovators that are building cool things in their garages with off the shelf parts.  Obviously, no one is going to be building anything like a CT scanner in their garage, but that’s actually the fun part.  There’s no way to know what’s cool and important (disruptive in MBA speak) until it sneaks into people’s hands and we all exclaim how obvious it was.

No Comments