Clinical Groupware: Platforms, Not Software

DAVID C. KIBBE and BRIAN KLEPPER

First Published on THCB

Clinical Groupware is rapidly gaining acceptance as a term describing a new class of affordable, ergonomic, and Web-based care management tools.

Since David first articulated Clinical Groupware's conceptual framework on this blog early last year -- see here and here -- we've been discussing Clinical Groupware with a growing number of people and organizations who want to know what it is, where it's going, and what problems it may solve, particularly for small and medium size medical practices, their patients and their institutional/corporate sponsors and networks.

2009: A Year of Surprises and Change for the EHR Technology Market

DAVID C. KIBBE and BRIAN KLEPPER

2009 began with a bang for legacy Electronic Health Record (EHR) vendors, promising strong sales and windfall profits on the heels of stimulus package incentive bonuses initially worth more than $19 billion to doctors and hospitals. But things changed dramatically along the way.

Here ten surprises and notable events that have impacted the EHR market:

Why Standards Matter (2): Health IT Enters a New Era of Regulatory Control

DAVID C. KIBBE and BRIAN KLEPPER
 
The recent history of electronic medical records in ambulatory care, or what we now call EHR (electronic health record) technology, can be divided roughly into three phases. Phase I, which lasted approximately 20 years, from about 1980 to the early 2000's, was an era of exploration and early adaptation of computers to outpatient medicine. It coincided with the availability of PCs that were cheap enough to be owned by many doctors, and with the increased capacity of off-the-shelf software programs, mainly spreadsheet and database management systems such as Lotus, Excel, Access, and Microsoft's SQL, to lend themselves to computerized capture of health data and information.

Why Standards Matter (1): The True Meaning of Interoperability

DAVID C. KIBBE and BRIAN KLEPPER

Americans are generally skeptical of words that otherwise intelligent and articulate people can't pronounce.  "Interoperability," like nu-cu-lar, is one of these. After a while, these words can take on a mystique all their own.

But interoperability is a hugely important word in the context of today's ongoing debate about the use of EHR technology by physicians, hospitals, and patients too. The federal government is going to provide billions of dollars to encourage today's fragmented health care providers to convert from mostly paper to mostly computerized information systems. It is critically important for these systems to talk with one another. We want health data to flow between and among these systems and to be, well, interoperable.  And it isn't now.

Finally, A Reasonable Plan For Certification of EHR Technologies

A caution to readers: This post is about methods for certifying Electronic Health Record (EHR) technologies used by physicians, medical practices, and hospitals who hope to qualify for federal incentive payments under the so-called HITECH portion of the American Recovery and Reinvestment Act (ARRA). It may not be as critical as the larger health care reform effort or as entertaining as Sarah Palin, but it WILL matter to hundreds of thousands of physicians, influencing how difficult or easily those in small and medium size practices acquire health IT. And indirectly for the foreseeable future, it could affect millions of American patients, their ability to securely access their medical records, and the safety, quality, and the cost of  medical care.

Three weeks ago, on July 14-15, 2009, the ONC's Health IT Policy Committee held hearings in DC to review and consider changes to CCHIT's current certification process. The Policy Committee is one of two panels formed to advise the new National Coordinator for Health IT, David Blumenthal. In a session that was a model of open-mindedness and balance, the Committee heard from all perspectives: vendors, standards organizations, physician groups, and many others. 

An Open Letter (3) to the New National Coordinator for Health IT - The Elephant in Health IT's Living Room

DAVID C. KIBBE and BRIAN KLEPPER

In the first and second parts of this series we talked about how and why there is no universal definition for the term "EHR." Instead there is a legitimate, growing debate about the features and functions that "EHR technologies" should offer physicians seeking to qualify for HITECH incentive payments. We explored the layers of network technology, suggesting that federal regulators should "separate the data from the applications."

An Open Letter (2) to the New National Coordinator for Health IT - Opening the Aperture of Innovation

DAVID C. KIBBE and BRIAN KLEPPER

One of the important decisions before Dr. Blumenthal and his colleagues at ONC and HHS is whether the national health information network will be one of closed appliances that bundle together proprietary hardware, software, and networking technology, or one of open data exchange and management platforms in which the component parts required to do medical computing can be assembled from different sources. If the former direction is chosen, power and control will be concentrated in the hands of a very few companies. If the latter, we could see an unprecedented burst of disruptive innovation as new products and services are developed to create the next generation of e-health services in this country.