Archive for August, 2007

Key Health IT opportunity: Medicare Says It Won’t Cover Hospital Errors

Last week the NY Times and others reported that Medicare will stop covering expenses incurred by hospitals for what the agency considers as errors:

In a significant policy change, Bush administration officials say that Medicare will no longer pay the extra costs of treating preventable errors, injuries and infections that occur in hospitals, a move they say could save lives and millions of dollars.

Assuming the rules get enacted as expected, this is a major opportunity for health IT firms to jump in with solutions. For example, firms that do any of the following will be in demand very soon:

  • Track medical errors and liabilities (this used to matter for legal cases, not it’ll be useful for reiumbursing)
  • Analyze billing patterns and CPT charges that would likely be for “cleaning up a mistake” rather than an orginating a procedure. Billing software vendors can start to add functionality into their applications to do better reporting.
  • Insurance company bill processing software will need better filters
  • Tracking hospital acquired infections (HAI) and tying them to specific bills at the hospital. Companies are doing this today but not really tying their reports to specific patients or into the financial side.

According to the NY Times article, the Medicare rule changes could save significant money:

The new policy — one of several federal initiatives to improve care purchased by Medicare, at a cost of more than $400 billion a year — is sending ripples through the health industry.

With this much money at stake and the government now ready to put new rules into effect, health IT firms should start their engines…and fast. This is a brave new world and we’ll need new software to make all this work efficiently for both the government and providers.

Microsoft Health Common User Interface (CUI) Guidance and Controls

Microsoft’s been tying to make some major inroads into healthcare IT (some impressive, others that are a little “me too”). They are strong in the office automation and general computing space in hospitals but weak in the healthcare-specific vertical and clinical areas. One of the areas that Microsoft’s always been strong is supporting the development community and they’re starting to make some good progress in health IT (specifically health not the just IT part). I’m a Microsoft Solutions Architect MVP and believe me they know how to take care of developers.

Microsoft recently released their Common User Interface (CUI) documents which provides developers, users, and UI specialists with healthcare-specific guidance.

I’ve gone through many of the documents and for people that have been in the business for a while (or like me who have actually built about dozen healthcare systems) much of the information is obvious. However, if you’re new to healthcare IT and design, I definitely recommend taking a look. Even if you already know the material, it’s great to base new development on something like this so that your engineers and UI specialists don’t reinvent the wheel. All development teams need guidelines like these and if you lead a team creating healthcare software you owe it to yourself to take a look and use the guidelines directly or adapt them to your liking.

In addition to the guidelines there are also .NET (ASP.NET and desktop) controls that put into practice much of the guidance. Just be careful that once you start using the controls you may no longer be platform-independent. Before jumping straight into the code, try to adapt the documents and build your own UI standards around it and then see if the controls make sense to use.

Here are the common user interface guidance areas they’ve implemented so far:

Health IT Blogs Visualized

Ryan Byrd over at healthTech.accordingtome.com has a great picture of the HIT blogosphere.

HIT Blogsphere Visualized

Here’s how he described what he did:

What does the healthcare blogosphere look like? That is, how are all the healthcare IT blogs interconnected?

I wrote a quick program that extracted the blogs listed there and for each of them, I spidered the first page for links and checked to see if those links linked back to the original 50. Then my program created a network graph that displayed the connections while scaling the size of each site’s node proportional to the number of other sites linking to it.

Looks like a great picture, Ryan. Nice job.