All I want for Christmas

It’s Christmas time. [Well, okay, it’s not anymore. This was written before Christmas, but the one friend I do have reviews these posts first, and he disappeared on holiday beforehand, so I’m only getting to post it now].

It’s a hard time of year for everyone, especially if you have any sense of the ridiculous. After all, what’s the basis for Christmas? The Son of God came to the world, and told everyone that God was angry because of everyone’s injustice and greed. So naturally, we remember Jesus by giving gifts to anyone who’ll give us stuff back, and by eating and drinking far too much. We can’t even get the time of year right – though maybe it’s best that Christmas is just a pagan feast at heart.

Of course, when I’m stupid enough to say something like this to my friends, they tell me that the best part of Christmas – what it’s really all about – is spending time with my family. Well, they’re quite welcome to spend time with my family. Though if they think that’ll be fun, they don’t know my family as well as I do. So I’m back hiding in my hovel, thinking about healthcare and IT (and not before time too. Apologies for the long delay between posts – apparently our customers expected me to get some actual work done before they got to go on their family fun-time holidays).

And what I’m thinking about right now is, what will you and your loved ones – if you have any – what will you be talking about this Christmas once you’ve had too much to eat and drink, and all the presents are opened? Well, I can’t think of anything better than to talk about healthcare system reform. 

“Umm, yeah,” you’re saying, “right. What else would we talk about?”

Well, don’t blame me. Instead, you can blame Senator Tom Daschle:

Daschle wants Americans to host “holiday-season house parties to brainstorm over how best to overhaul the U.S. health-care system,” the WSJ reports.

Don’t believe me? Check out the WSJ for the whole outrage. And thanks to my spies in the USA who alerted me to this gem.

At first I laughed at this. I was pretty disappointed too. I was certainly hoping for more from the incoming administration. After eight years of the Bush power slide, we’re in desperate need of a responsible approach to prevent the inevitable, though a quick survey shows that the Democrats have quite happy competed with the Republicans to see who offers worse government (it’s a US thing: governments are bad, so we vote for bad governments). Nevertheless, I found myself hoping that “Change we can believe in” didn’t mean that kind of change the Health IT Nerd believes in, the kind that I usually see in the healthcare system – namely, just a different kind of stupid.

As I said, I thought, who’d be stupid enough to talk about healthcare policy over a Christmas meal? But the more I thought about it, the more I realized that we always talk about healthcare policy when my family gets together. It starts easily enough, talking about our family’s latest encounter with the healthcare system. What with the many little accidents of life – backyard, kitchen, and bedroom - and getting old (also accidental; at least, it certainly seems to happen while you’re looking the other way), the extended families of the Health IT Nerd and his suffering wife have regular encounters with the healthcare systems across the world, and whichever side of the family we have the “luck” to spend the festive season with, the subject is sure to come up.

And once the subject does come up, you can be sure of one thing: everyone is going to start complaining about how terrible the healthcare system is. After all, it’s never our fault that we needed healthcare. Actually, it’s not our fault. Since the only thing that’s sure in life is death and hospitals, it’s just because we were born. So the fact that we need healthcare is our parent’s fault – it’s important to know who to blame for all life’s ills. For this reason, the best time to talk about how to reform the healthcare system is when you get together with those whose fault it is. 

It doesn’t matter what country you’re in, either. You can be sure that everyone’s going to be complaining about the quality of the healthcare system. And also how much we have to pay for it. Again, it doesn’t matter how it gets paid for, directly, indirectly through insurance, or indirectly through taxation. We pay too much, and the quality of service sucks. 

So, this year, when you get together as families, do your patriotic duty, and brainstorm how to overhaul the U.S. health-care system, because, as Daschle points out:

There is no question that the economic health of this country is directly related to our ability to reform our health-care system

For a start, you can tell by looking at the way we celebrate Christmas, you can tell for sure that it would be a waste of time asking us to consider the healthcare system from some altruistic perspective about what would actually be good for our health. No, we definitely need to talk about money. And since there’s a war or two to fight, and the worst financial crisis this century, we need all the money we can get. 

So this year, instead of simply complaining about how poor the system is, instead, try and figure out how to pay less, either by defrauding someone, or perhaps by setting up some kind of ponzi scheme to raise enough money to pay for it (as if any kind of savings plan isn’t a ponzi scheme in the end). If that doesn’t work out for you, see if you can figure out how to overhaul the US healthcare system. And the best kind of overhaul is one that saves money – in other words, one that makes the system poorer. 

It’s kind of a game, see. Basic level, you get to plan a healthcare system assuming no constraints, like worrying about how much it costs. But anyone can design a pretty good healthcare system that way. At the intermediate level, factor in real world constraints like costs, staffing levels, and inefficiencies like organizational dysfunction. There’s a special advanced level where you also get to make allowances for things like liability funding, and on-going educational resourcing. If your family wins at that level, then you move onto wizard level, where you get to figure out how to overhaul the US healthcare system to make it better, while factoring in unreal world constraints like eating long lunches with friendly lobbyists.

No one wins the wizard level. Ever.

But it’s Christmas, so there’s no harm in hoping for the best. After all, wishes can come true. So what does the Health IT Nerd wish for?

Of course, I wish for world peace, justice for all, the end of famine, an end to bad governments, and that people would stop sponging off their richer neighbors. And in healthcare, I wish that people would stop getting sick, and that everybody would be happy to let their poor sick neighbors sponge off them.

Hmm. This isn’t going well. Though at least Bush the Second is going to be gone. I guess that’s not much a Christmas present though, since it was all organized years ago. 

No, other than a bit more of that river of gold, what I really want for Christmas is that everyone would finally come to really understand: Interoperability – it’s all about the people.

[Belated Christmas note: I sure hope you got what you wanted for Christmas. Because I didn't)

What we have here is a failure to communicate

IT is the great white hope for healthcare, the healthcare administrator’s wet dream: we’ll be able to reduce the cost of this monster using IT and improve service at the same time. And like all fantasies of this type, what you get in the cold light of day just isn’t quite the same – that sensuous young woman turns out to be a withered old hag with a sour disposition (or, for my female readers – if I still have any: that buff young man turns out to be a crotchety old jerk with a hairy back).

One of the principles is easy to grasp. Anywhere between 50% and 80% of healthcare professionals’ time is spent tracking down information so they can provide proper healthcare. That’s right – that doctor who’s getting paid a million smackers a year: he spends most his time finding the right pieces of paper. That's not all - almost all of the preventable deaths that occur relate to missing information one way or another.

So, if you stick all that information on computers, and they can talk to each other, then the information will just be right there, exactly when and where the healthcare professional needs it. Magic! And we could get twice as much work for the same amount of money, and with less “totally negative health outcomes”. So you can see how seductive this idea is – up there with the supermodels. Also, see the Turkey I had for thanksgiving.

Actually, it would be magic if it worked that way, but the real magic is in the innocuous words “they can talk to each other”. In the healthcare IT industry, this is called “interoperability”, and it’s the Holy Grail. It bears startling resemblance to the Holy Grail too. Not only has no one ever seen it, we don’t even know what it actually is.

In order for computers to be able to talk to each other, they need to understand each other in a deep and meaningful way. At least that’s what the experts say.

I’m not so sure. I’m married, and I know that once you understand each other, you no longer need to talk anymore. Yeah, yeah, everyone laughs when I say that, and pities Mrs. Health IT Nerd. And I mean, I understand their pity, because I know me even better than they do, but they’ve missed the point: Mrs. Health IT Nerd and I are never going to understand each other (any of you that are married will know exactly what I mean). So our lives are full of interesting times, and we are forced to keep talking to each other.

So this is what makes interoperability so much fun: we’re never going to understand each other fully, but we have to get along anyway. I think this is one of the craziest things that happens in health IT, that the industry so seriously misunderstands what will enable interoperability, and what the results might be.

Classic interoperability theory says that in order for two computers to talk to each other, you need the following things:

• A transmission channel between the two (usually, but not always, bidirectional)
  
• A common set of terms (words) with meanings that both parties understand
  
• A common set of information models (grammar/story plotlines) to allow the pieces of meaning in terms to be assembled into a coherent larger structure
  
• An agreed process (who says what when, and what happens next)
  

This is called the “interoperability stack” (I presume “stack” like as in “Dad, I totally stacked your car”).

It’s the same requirements for humans to talk together, on any scale, from my two small kids arguing about who gets to be the doctor and who is the patient, to diplomats from two large countries resolving which side of the border their soldiers will get to acquire their need for emergency healthcare on.

Actually, that stack above is incomplete. There’s something else that most interoperability wonks don’t stress, but I can’t stress enough:

• The two parties need to share an agreed context of operations
  

Like Mrs Health IT Nerd and I, no one knows how to even agree on what this “context of operations” thing is, how wide and deep it is.

Take a simple case: in Isaac Asimov’s Foundation, one of the characters says: “Violence is the last refuge of the incompetent”, by which he means, only the incompetent will use violence because it doesn’t solve anything.

Well, I have a friend (Yes, I *do* have one), and he’s a wingnut, so he says that this means that competent people would have resorted to violence long before it’s time for the last refuge. While that interpretation is the polar opposite of the one that was intended, the actual words and the grammar are understood the same way. It’s the different background values people use when evaluating the meaning of the phrase that make the difference here. (Which interpretation is correct? It’s not like it matters for this column, but I figure that what happened in Iraq - or any other war - shows the statement is wrong and stupid however you want to read it.)

This is why interoperability is so hard: there are so many layers to understanding. A whole industry exists to define interoperability based on standards that provide meaning for that stack, a whole alphabet soup of them, such as HL7, CEN, ISO, IHTSDO, ASTM, ANSI, WHO, W3C, OASIS, WS-I…. a never-ending profusion of standards bodies. You know what? These standards bodies, these definers of interoperability, they can’t even interoperate amongst themselves, so it’s the proven-blind leading the probably-blind.

These standards are all going to fail. Well, not so much fail (though it might be best if, umm, if we all don’t actually look too closely at them when we say that), as not quite deliver all the things people are demanding from them – just small things, like life, the universe, everything, and also world peace as well. These things won't happen, but there will be some outcomes: life will get better, healthcare will improve. But you know should know by now what happens when healthcare improves: costs go up; so even if these interoperability standards deliver everything anyone dreams of, the outcomes won’t be what they desired in terms of cost-cutting.

Even if the healthcare administrators and those who pay for healthcare (i.e. you!) scale back the expectations of what interoperability can achieve to something reasonable, these standards are not going to deliver, because they’re all based on the expectation that if you solve the technical problems, interoperability will just happen.

It’s people who insist on doing things differently, calling the same thing by different names or vice versa. It’s people, who, given the same patients, the same healthcare problems, and the same computer systems, find completely different ways to achieve roughly the same outcomes. And for all these people – both healthcare professionals, and healthcare informaticians (horrible word!): there’s my way of doing things, and all the wrong ways to do it. There’s even a step beyond that, people for whom there’s my way of doing something, and all the other ways that I am dedicated to destroying. These people are methodological terrorists, and they are attracted to standards. This is part of why the healthcare standards wars are such fun.

So the fundamental problem of interoperability, of getting the information to the right person at the right time, is the first and last steps – getting it out of the first person who has it, and into the other person who needs to understand it in the appropriate context, how it relates to all the other information they have. Compared to these two problems, everything else is just plumbing, though we can’t even get that right. Interoperability is about people, not technologies.

Perhaps the healthcare industry isn’t so stupid to spend below average amounts on IT after all.

However we’re clearly going to spend what we do have on chasing the chimera of getting computers to fully understand healthcare – that is, us. Well, that will never happen.

So I think that we need to start focusing on enabling interoperability without trying to understand each other. See, if we all focus together on trying to achieve something perfectly useless, there’s a reasonable chance that we might actually succeed, especially since we've already achieved one of the desired outcomes – we’ll never understand each other.