Does it come in blue?

The store for audiophile wannabe’s. Denver, Colorado. The first store I hit after blowing an entire paycheck at REI when I moved to Colorado. 

The first thing I noticed was the lack of clutter, the lack of inventory. There were no amplifiers, because amplifiers were down market. There were a dozen or so each of the pre-amps, tuners, turntables, reel to reel tape decks, and these things called CD players. They also had dozens of speakers. At the back of the store was an enclosed 10 x 10 foot sound proof room with a leather chair positioned dead center.

When the ponytailed salesperson asked about my budget, like a rube I told him I didn’t have one. He beamed and took that to mean it was unlimited. It really meant I hadn’t thought of one. He asked me what I liked to listen to.

“Pink Floyd, Dark Side of the Moon.”

Within a few seconds I was seated in Captain Kirk’s chair, and Pink Floyd’s Brain Damage filled the room in pure digital quadraphonic sound. I was in love.

I lived a block and a half away. Since the equipment wouldn’t fit in my Triumph, I made several trips carrying home my new toys—gold plated monster cable, solid maple speakers that rested on nails so as to minimize distortion, a pre-amp, tuner, receiver, turntable, and stylus.

It wasn’t that I deliberately bought stuff I didn’t need. I walked in uneducated. I had never bought what I was looking at. I didn’t know how much to spend, nor what it would do for me. Looking back at that purchase decision, I bought specs I didn’t need. I didn’t realize it was possible to build audio technology that would meet performance specs beyond what I person could hear, heck beyond what anything could hear. Not understanding that possibility, I bought specs I couldn’t hear. I spent hundreds of dollars on features from which I would never receive value. You too?

It happens all the time. Stereos. Cars. Computers. Applications. Technology. Having bought it doesn’t mean it was needed, that it was the right thing to do, that it has an ROI, or that it meets the mission.

What must the ONC do to make EHR a success?

The following is my second reply to Brain Ahier’s interview of Dr. Blumenthal.  The purpose of this post was to outline some steps the ONC could take to retrofit its EHR strategy.  PLease let me know what you think.

Grab a soft-drink—this one is rather long. Please forgive any formatting mistakes–it looked good in Word.

I have never been one who thinks hit-and-run critiquing is fair. It is too easy to throw metaphorical tomatoes at an idea with which you disagree. As such, perhaps instead of just being critical of the national EHR rollout plan, here are a few ideas which may be worth exploring in more detail.

It just occurred to me that the ONC’s role, the Office of the National Coordinator, is just that—coordination. Who or what is the ONC supposed to be coordinating—among its various functions, or the providers? There are the coordinators, and its constituents—the uncoordinated. I know at least one provider who already spent $400 million on its EHR. They didn’t get coordinated. I asked one of their executives who played a major oversight role in the implementation, with whom they worked at the ONC. She was not even familiar with the acronym.

I don’t think providers are looking to be coordinated—they are looking to be led. I also think they are looking to be asked and to be heard. They are looking for answers to basic questions like; why should we do this, what is in it for me—this has nothing to do with incentive dollars?

It often seems like the ONC has developed many solutions seeking a problem, filling their tool bag in the hope they brought along the right one. This is where I think we see a good portion of the disconnect. It is better to say we know where we are going, but getting there slowly, instead of, we don’t know where we are going but we are making really good time.

People don’t buy drills because they need a drill—they buy them because they need—say it with me—holes. Providers need holes, not HIEs and RECs.

You understand the pressures you face much better than do I. Has anyone from the ONC asked you if they should reconsider their plan, their approach, their timing? Chances are good that you are not implementing EHR and CPOE because you have a vision or a business imperative of someday being able to connect your EHR to Our Lady of Perpetual Interoperability. CIOs and their peers are not spending eight or nine figures because you want a virtual national healthcare infrastructure. The C-team is investing its scarce resources to make its operation better, to reap the rewards of the promise of EHR.

The ONC is spending its resources towards a different goal, a virtual national healthcare infrastructure. The two goals do not necessarily overlap. I am reminded of the photo showing the driving of the Golden Spike—the connecting of the Union Pacific Railroad to the Central Pacific Railroad—the final link of the Transcontinental Railroad that in the 1870’s allowed Americans to cross the US by rail. What would have happened had the two railroads worked independently of each other? They would have built very nice railroads whose tracks would never have met, tracks dead ending in the middle of nowhere. Even if they almost met, say got within a few feet of each other, they would have failed.

There are those who see the work of the ONC as a real value-add. I dare say that most of those are not hospital CIOs or physicians. Both groups define value-add and success differently.

This is not to say that providers would not accept all the help they can get. However, providers want the help to be…what is the word I am searching for—helpful—to them, to their issues. The ONC’s mission will not work until the providers successfully deliver what the ONC needs from them. How many providers must be Stage 7, Meaningful Use, Certified compliant for the virtual national healthcare infrastructure to work? Fifty percent? Eighty? Who knows.

So, the providers own the critical path. It is all about the providers, bringing fully functional EHR systems to hospitals and physicians. The numbers I have seen do not paint a promising picture. The critical path is in critical condition. Ten percent hospital acceptance and a sixty percent failure rate. Let’s say those numbers are wrong by a factor of three—thirty percent acceptance, and a twenty percent failure rate. Even those numbers do not bode well for ever achieving a virtual national healthcare infrastructure under the current plan. Subtract from those figures—supply your own if you would like—the churn figures—those hospitals that are on their second or third installation of EHR. Something is amiss.

In a more perfect world the ONC might consider shifting course to something aligned with the following:

• Segment its mission into two parts; one to build a virtual national healthcare infrastructure, and two, provide hands-on support individual hospitals’ and providers’ EHR initiatives.
• Standards
• Standards—I wrote that twice because it is important to both missions
o Let us be honest, the largest EHR vendors do not want standards. Why? Because if all else fails, their standards become the standards. They don’t phrase it this way, but one can assume, their business model calls for them to do what is best for them.
o The vendors do not want to open their APIs to the HIEs
• Do not set dates for providers which to be met require meeting rules which do not yet exist. If the government wants providers to meet its dates, the government must first meet some of its critical success factors—standards, for example.
• Mandate vendor standards for however many vendors make up ninety percent of the EHR install base for hospitals. Give vendors 18-24 months to agree to a set of standards and have them retrofit their applications.
• Use a garrote and stick approach on the vendors. Create a standards incentive program, heck, underwrite it. Pay the vendors to develop and get on a single set of standards—this will have a much more positive impact than REC and PR money. Many will say, especially those who have an incentive for this not to happen, this cannot be done. Of course it can.
• Processes. EHRs are failing in part due to not enough user involvement, not enough user authority and governance. There is no usable decompositionable process map of how a hospital functions. No Level Zero through Level Whatever You Need. No industry standard, mega-diagram, boxes and arrows, which can be laid on a table or hung on a wall that shows, “This is what we do. This is how it all ties together.”
• I am building this process map, along with a colleague. Why isn’t the ONC? It will not match you hospital. It may not match anyone’s hospital. What it will do is give someone a great base from which they can edit it. Why is this important? Because it will enable the users, IT, and the vendor to overlay the EHR application to show:

o which business and clinical areas are impacted
o the process interfaces
o duplicated processes
o processes with no value-add
o which other facilities have similar and differing processes
o where change management resources must be focused
o what needs to happen if an acquisition is made

The ONC must move from coordinating to leading. To do that they need the authority to mandate the execution of some of the items listed above.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

My remarks to Brian Ahier’s insightful interview of Dr. Blumenthal

I encourage those who have not read Brian’s interview of Dr. Blumenthal on HealthSystemCIO.com to make time to read it.  http://healthsystemcio.com/2010/03/27/chatting-with-the-national-coordinator-for-health-it/#comments

Brian also has a link to the audio.

Brian asked me to comment, and I was pleased to do so.  Here is what I wrote.

I enjoyed reading your interview with Dr. Blumenthal. Clearly he and the members of his team are working very hard on a number of difficult and rather diverse issues.

I have been wondering, how does one tell the story of EHR to someone who has no understanding of EHR? Not the story about the EHR system in a physician’s office, or the ungainly one in a hospital. The story to which I refer is the story of the national rollout of EHR and the drive for interoperability.

For me, the question of how to tell the story in a way to make it understandable raises a number of other questions. Is there a story, or is it a collection of short stories written by different people, guided by different principles and goals? Is there a plot? Does the story come together in a natural manner?

Sticking with the story theme for a moment—who are the main characters, do they relate to one another? Does it come to a meaningful conclusion, in fact, does it conclude?

Look at the various antagonists—EMR, EHR, PRH, Meaningful Use, Certification, HIEs, RECs, the N-HIN, interoperability, the ONC, CMS, ARRA, standards, vendors, and PR. I am sure I missed several.

Imagine if Random House allocated millions of dollars to publish and market a book which had yet to be put to paper. No plot, no outline. What if they hired a dozen writers, each with their own areas of expertise—and lack of expertise—and crossed their fingers.

Would they be more successful if they offered penalties and incentives to the writers—a garrote and stick approach? What if they changed the rules after the writers started? What if they left undefined numerous areas of rules, rules which will impact the story, and told the writers to keep pushing ahead?

I do not see how the national EHR rollout story comes together. Now or some distant tomorrow—at least not under this approach. Is the approach viable? Having a few disparate successes does not make me a believer. Call me a cock-eyed nihilist.
Once every so often, an announcement is made that another single hospital reached Stage 7. One among thousands. Why do I view this from the vantage point of a glass half-empty? For me, the existing approach is one of guidance and facilitation. There are no long lines of providers trying to beat the others to the front of the EHR line. There have been several hundred million dollar do-overs.

If we circle back to the providers for a second, three of the largest causes of failure include the arbitrary setting of go-live dates without knowing what needs to be done or can be done in that time frame; second, letting IT and the vendor drive and manage the project; third, not getting users to define what they need and then having IT replicate those needs. IT does not need an EHR.

As I look at the government’s national rollout of EHR I see the same three problems. Who are the government’s users? Doctors, clinicians, and hospitals. There are fixed dates, many having undefined requirements. These are causing some providers to dash for the cash. Who is driving the rollout—the government’s users, or the government. They way the rollout is structured, the users have all of the responsibility and little of the authority. This is a government led IT project. Where are their users? They are running their practices and hospitals. They have one ear open towards, reform, another to the garrote and stick project rollout approach, another to EHR, and yet another to their business model. They have run out of ears.

Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942

My profiles: WordPressLinkedInTwitterMeetupBlog RSS

EHR-the 40 chicken crocodile

Got a couple hundred million burning a hole in your pocket?  Why not buy an EHR?  Indeed.

Riddle me this Batman, “What is a 40 chicken crocodile?”

It is the number of chickens you have to feed it each day to keep it from eating you. What is the crocodile at your hospital?  Is it your EHR?

Let me recount to you a true story about the details of one of the EHR “success” stories.  A major hospital who selected their EHR from among one of what I like to call the oligopoly EHR Flavor of the Month Club.  You know the suspects.

Permit me to throw a wrench to those clairvoyants who think they know where this is going before I’ve even written it.  Admittedly, I have a tendency to throw metaphorical tomatoes in one direction—that of the vendors.  That’s because, they are often easy targets.  Slow down Pepito.

This hospital, and from what I was told, the vendor, did it right.  I am not sure I would have differed from the approach of either.  The hospital spent a few years in its vendor selection process, and they were very thorough.  They spent two years building their process maps, ensuring the vendor implemented the EHR to meet their needs, not the other way around.  Operations led the nine-figure project.

They implemented many of the support functions and a few of the specialty functions.  Here come the chickens.  After implementation, cash flow dropped by 80 percent for several months due to significant issues they encountered cleaning up the revenue side.  Doctors were instructed to cut their hours by fifty percent to allow them to learn to use the system.  Hours are still down by twenty percent, well more than a year later.  Users use about one-third of the functionality, even after a rigorous training program.

The hospital held off doing most of the clinical implementations for two years.

I asked for some recommendations.  What would you have done differently?  Here’s what I learned.  If you have a research organization you need to spend extra special attention to their workflows.  Managing post-go-live was a big issue to begin to offset productivity losses. Without a continuous process improvement program the EHR would not have been accepted. Do not pick a go-live date at the outset of the project as it causes the organization to be paralyzed simply to hit the date.  Testing was compromised to meet the go-live date. The post go-live issues are still being fought.  Do not let the design or build teams skimp on either reporting or testing, they are still playing catch-up.

So, after doing a pretty bang up job, at least from where I sit, there are still a lot of chickens being fed to the crocodile.  Wonder how many chickens it would have taken had the users not been as involved as they were.  How many had the users not spent two years pre-build defining processes?  A lot.  Now comes the rest of the clinical effort.  See you at the poultry counter.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

What if hospital business models weren’t so tribal?

I tend to look at it from the perspective of the business model of many hospitals.  How does one transform a 0.2 business model to function in today’s let alone tomorrow’s changing healthcare model?

The clinical side of healthcare, the healthcare business, in juxtaposition to the business of healthcare, would never quarter to the idea of buying millions of dollars of technology without first knowing how they were going to use it.

Plenty can be gained by applying what other industries have done to become more effective.  In some respects the inherent structure, cost duplication, and rigid departmental silos remind me a lot of how the various agencies under Homeland Security function, operating in isolation, performing much of the same work, and not sharing information.

Other industries operate with a much less tribal model than healthcare.  Hospitals have created tribes and tribal chiefs.  In some hospitals the tribes have names like radiology, general surgery, psychiatry, and OBG/YN.  Other hospitals have redundant tribes named admissions, human resources, IT, and payroll.  Each tribe is run by the tribe’s chief.  The chief’s dominant weapon is his or her budget which is lorded over its individual tribe, and a dispute vehicle of the other tribes.

The tribal organization is more a reflection of how the hospital evolved over the years, not a result of an inept business strategy.  Nobody set out to build an ineffective and internally competitive model, or one that duplicated support functions.  Acquisitions have reinforced and exacerbated the problem, duplicating and increasing costs without yielding a resultant increase in value.

Before the business of healthcare is prepared to cope with the unknowns of the myriad of external influences it will face in the next few years, it must first change how it functions under its current structure.  It might begin by revisiting its present structure and making sure that its performance and quality precede the application of technology.

I frown on using the term efficient.  To me, efficiency implies speed, and doing bad things faster is no solution.  Let us work at improving effectiveness and good things will happen.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

What if our EMRs were portable?

I am wondering how much of the cost of a hospital’s EHR system includes building in the functionality of individuals’ EMRs and making them transportable.

What if EMR’s were made portable and they could be carried around by patients on super smart devices?

Any thoughts?

saint       Paul M. Roemer
       Chief Imaginist, Healthcare IT Strategy
      
       1475 Luna Drive, Downingtown, PA 19335
       +1 (484) 885-6942
       paulroemer@healthcareitstrategy.com 

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

The change keeps changing

Hello to those whom I’ve yet to meet.  This is rather long, so you may wish to grab a sandwich.

I write to share a few thoughts.  I reside in the small place where those who refuse to drink the Kool Aid reside. For those who haven’t been there, it’s where those who place principle over fees dare to tread.

Where to begin? How to build your provider executive team? (Those who wish to throw cabbages should move closer to their laptops so as not to be denied a decent launching point.)

I comment on behalf of those in the majority who have either not started or hopefully have not reached the EHR points of no return—those are points at which you realize that without a major infusion of dollars and additional time your project will not succeed. Those who have completed their implementation, I dare say for many no amount of team building will help. Without being intentionally Clintonian—well, maybe a little—I guess it depends on what your definition of completed is.

If I were staffing a healthcare organization, to be of the most value to the hospital, I’d staff to overcome whatever is lying in wait on the horizon, external influences—the implications of reform and Stages 2 and 3 of Meaningful Use, and a national roll out of EHR with no viable plan to get there.  Staffing only to execute today’s perceived demands will get people shot and will fail to meet the needs of hospital. To succeed we need to exercise an understanding of what is about to happen to healthcare and to build a staff to meet those implications.

Several CEOs have shared that they are at a total loss when it comes to understanding the healthcare implications of reform and IT.  They’ve also indicated—don’t yell at me for this—they don’t think their IT executives understand the business issues surrounding EHR and reform.  I somewhat disagree with that perspective.

Here’s a simplified version of the targets I think most of today’s hospital CIOs are trying to hit.

1. Certification
2. Meaningful use
3. Interoperability—perhaps
4. Budget
5. Timing
6. Vendor management
7. Training
8. User acceptance
9. Change management
10. Work flow improvement
11. Managing upwards

There are plenty of facts that could allow one to conclude that these targets have a Gossamer quality to them.  Here’s what I think. You don’t have to accept this, and you can argue this from a technology viewpoint—and you will win the argument. I recently started to raise the following ideas, and they seem to be finding purchase—I like that word, and since this is my piece, I used it.

Before we go there, may I share my reasoning? From a business perspective, many would say the business of healthcare must move from a 0.2 to a 2.0 business model. (This is not the same as the healthcare business—the clinical side.)  The carrot?  The ARRA incentives—an amount that for many providers will prove to be more of a rounding error than a substantive rebate.

Large healthcare providers are being asked to hit complex, undefined, and moving targets, and they are planning on adapting to reform and reforming their own business model while they implement systems which will change how everyone works.  Hospitals are making eight and nine figure purchase decisions based in part on solving business problems they have not articulated. If success is measured as being on-time, in-budget, and fully functional and accepted, for any project in excess of $10,000,000, the chances of failure are far greater than the chances of success.

Their overriding business driver seems to be that the government told them to do this. Providers are making purchasing decisions without defining their requirements. Some will spend more on an EHR system than they would to build a new hospital wing.  Many don’t know what the EHR should cost, yet they have a budget. Many don’t know if they need a blue one or a green one, if it comes in a box, or if they need to water it.

So, where would I staff to help ensure my success—this is sort of like Dr. Seuss’, “If I ran the Circus”—the one with Sneelock in the old vacant lot.  I’d staff with a heavy emphasis on the following subject matter experts:

• PMO
• Planning & Innovation
• Flexibility
• Change Management
• PR & Marketing

Contrary to popular belief, not all of these high-level people need to have great understanding of healthcare or IT. You probably already have enough medical and IT expertise to last a lifetime.

Here’s why I think this is important. Here’s what I believe will happen. Three to five years for now the government would like us to believe there will be a network of articulated EHRs with different standards, comprised of hundreds of vendor products, connected to hundred of RHIOs, and mapped to a N-HIN.  Under the proposed model, standardization will not occur if only for the fact that there is no monetary value to those vendors whose standards are not standard.

Interoperability, cost, and the lack of standardization will force a different solution—one which is portable.  I think the solution will have to be something along the lines of a single, national, open, browser-based EHR.  It will be driven by consumers.  Consumers will purchase the next generation of super-smart portable devices that offer a combination of iPad/iPhone functionality.

The Personal Health (PRH) will have evolved to become the EMR.  How is this possible?  What do smart devices do?  They do one thing, billions of times each day, and they do it perfectly—they send and receive ones and zeros.  That is what today’s EMR are—ones and zeroes.  Those next-gen devices will be EMR-capable.  Why?  Because there are more than a hundred million customers who will keep buying these devices.

The so-called N-HIN will be the new Super Internet—not some cobbled together network of RHIOs.

Firms like Apple, Google, and Microsoft will drive this change.  We already buy everything they offer, in fact, we line up at midnight to do so.  By then, those firms will care less about selling the devices than they will about transporting the ones and zeroes that comprise the data.  Their current PHRs are their way of introducing themselves to consumers as players in healthcare.

The point I am trying to drive home is that from being able to adapt to change and reform, lean towards staffing the unknown.  Staff with leaders, innovators, and people who can turn on a dime. Build your organization like turning on a dime is your number one requirement. Don’t waste time and money worrying about Certification or Meaningful Use. If anyone asks you why, you can blame me.

If you want a real reason, I have two. First, they won’t mean a thing five years from now. Second, if I am the person writing an incentive check, I want to know one and only one thing—will your system connect with the other system for which I am also writing a check?  That is the government’s home run.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

The Wildebeest Postulate

The Kalahari; vast, silent, deadly. The end of the rainy season, the mid-day heat surpasses a hundred and twenty. One of the varieties of waterfowl, most notably the flame red flamingo that nested in the great salt pans in Botswana, has begun its annual migration. In the muck of one of the fresh-water pools that had almost completely evaporated, writhes a squirming black mass of underdeveloped tadpoles. A lone Baobab tree pokes skyward from the middle of the barren savanna. In its shade, standing shoulder to shoulder and facing out, a herd of wildebeest surveys the landscape for predators.  Sir David Attenborough and PBS can’t be far away.

Some things never change. I make my way across the freshly laid macadam to meet the school bus. Fifty feet in front of me is a young silver maple tree, the buds of its green leaves yielding only the slightest hint of spring hidden deep within. The late afternoon sun casts a slender shadow across the sodded common area. One by one they come—soccer moms; big moms, little moms, moms who climb on rocks; fat moms, skinny moms, even moms with chicken pox—sorry, I couldn’t stop myself—as they will every day at this same time, seeking protection in its shade. My neighbors.  It’s only sixty-five today, yet they seek protection from the nonexistent heat, a habit born no doubt from bygone sweltering summer days. A ritual. An inability to change. In a few weeks the leaves will be in their full glory, and the moms will remain in the shadow of what once was, standing shoulder to shoulder facing outward, scanning the horizon for the bus. A herd. Just like wildebeest.

The children debus–I invented the word.  Mine hand me their backpacks, lunch boxes, and musical instruments.  I look like a Sherpa making my way home from K-2.

I shared this analogy with the neighborhood moms—the bruises will fade gradually. I can state with some degree of certainty they were not impressed with being compared to wildebeest. So here we go, buckle up. By now you’re thinking, “There must be a pony in here somewhere.”

Some things never change; it’s not for lack of interest, but for lack of a changer.  For real change to occur someone needs to be the changer, otherwise it’s just a bunch of people standing shoulder to shoulder looking busy. How are you addressing the change that must occur for EHR to be of any value?  EHR is not about the EHR.  It’s not about ARRA money, and it is not about IT.  It is about moving from a 0.2 business model to 2.0.  You need someone who sees the vision of what is is—sorry, too Clintonian—must lead.  Be change.

One of the great traits of wildebeest is that they are great followers.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

Abnormal


I remember the first time I entered their home I was taken aback by the clutter. Spent and wet leaves and small branches were strewn across the floors and furniture. Black Hefty trash bags stood against the walls filled with last year’s leaves. Dozens of bright orange buckets from Home Depot sat beneath the windows. The house always felt cold, very cold. After a while I learned to act normally around the clutter.

There came a time however when I simply had to ask, “Why all the buckets? What’s the deal with the leaves?”

“We try hard to keep the place neat,” she replied.

“Where does it all come from?” I asked.

“The windows.”

I looked at her somewhat askance. “I’m not sure I follow,” I replied as I began to feel uneasy.

“It’s not like we like living this way; the water, the cold, the mess. It costs a fortune to heat this place.

And, the constant bother of emptying the buckets, and the sweeping of the leaves.”

“Why don’t you shut your windows? It seems like that would solve a lot of your problems.”

She looked like I had just tossed her cat in a blender.

When you see something abnormal often enough it becomes normal. Sort of like in the movie The Stepford Wives.  Sort of like Patient Relationship Management (PRM). The normal has been subsumed by the abnormal, and in doing so is slowing devouring the resources of the hospital.

Are you kidding me? I wish. It’s much easier to see this as a consultant than it is if you are drinking the Kool Aid daily. When I talk to people about a statistic that indicates that 500 people called yesterday about their bill, and everyone looks calm and collected, it makes me feel like I must be the only one in the room who doesn’t get it—again with The Stepford Wives.

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer

If I ask about it they always have an answer.  “Billing calls are usually around 500 a day.”  They say that with a straight face as though they are waiting to see if I will drink the Kool Aid. It’s gotten to the point where no matter how bad things get, as long as they are consistently bad, there not bad at all.

This is the mindset that enables the PRM manager (I know you don’t have one—I am being facetious) to be fooled by their own metrics. When is someone going to understand that repeatedly having thousands of people calling to tell your organization you have a problem, means you have a problem?

It would probably take less than a week to pop something on your web site, and post a YouTube video explaining how to read the bill.  Next week, do the same thing and help patients understand how to file claims and disputes—granted, you may need more than a week for this one.

What is the future of the EHR/N-HIN landscape?

One may argue it is possible to build the real Brooklyn Bridge with nothing but toothpicks, and a lake filled with Elmer’s Glue.  Difficult yes; prudent, no.   Urban legend is when the United States first started sending astronauts into space, they quickly discovered that ballpoint pens would not work in zero gravity.  To combat the problem, NASA scientists spent a decade and $12 million to develop a pen that writes in zero gravity, upside down, underwater, on almost any surface including glass and at temperatures ranging from below freezing to 300C.

The Russians used a pencil.

The ability to do something is not justification for doing it.  Nor is that fact that someone has put it forth as an idea.  The willingness to do something merely because everyone is doing it or because someone instructed it be done probably has nothing to do with a business strategy, or if it does, it shouldn’t.

In the next five to seven years the business of healthcare at the provider level will have the opportunity to change markedly—the unanswered question is, will it have the ability?  To answer that at the provider level—primarily hospitals and clinics—I believe one must distinguish between the business of healthcare (how the business is run) and the healthcare business (how the care is delivered).

In many respects, the business of healthcare and the strategy surrounding it is pinned to a 0.2 business model.  Certainly there are exceptions to any aphorism, but taken as a whole, there is plenty of room for improvement.  As one hospital CEO told me, “What we really lack is adult supervision.”

So, how exactly does the toothpick bridge apply to healthcare?   Here’s my take on the situation.

  1. It may be possible to build and roll out a national network of EMRs through EHRs connected by HIEs to an N-HIN—I don’t think will happen in the next five to seven years, especially if to be effective the network requires a minimal participation of somewhere between 70 to 80 percent of healthcare providers.
  2. Even if I am wrong, why would anyone build a national EHR network out of toothpicks?  Could they possibly have devised a more complex and costly approach?
  3. The government arrived late for the party, has only limited authority, and chose to provide cash incentives instead of direction or leadership.  They passed the responsibility of the success of the national EHR roll out to hundreds of thousands of healthcare providers.
  4. The providers are burdened by having no experience in the sector, hundreds of EHR systems from which to select, no standards, hundreds of HIEs, no viable plan, no one with singular authority, a timeline that cannot be meet, and an unwritten set of Meaningful Use requirements.

The plan sounds like something designed by Rube Goldberg.  Could it be done this way?  I do not think we will ever know.  Not necessarily because it will fail, but because I think the plan will be supplanted by a more realistic one from the private sector.

The government’s plan relies on a top-down approach—albeit with a missing top; from the government, to the providers, to the patients.

The private sector plan will come from firms like Apple, Google, and Microsoft.  It will work because it will be built from the bottom up; from the patients, to the providers, and back.  Personal Health Records (PHRs) will become EMRs.  This approach will allow them to flip their PHR users to EMR users, and will be adopted quickly by millions of customers (patients).  Their approach will have a small handful of decision makers calling the shots instead of hundreds.

This model’s other component will be driven from another direction, by large hospitals and clinics that connect to small hospitals, small practices, and ambulatory physicians via a SAAS model.  Something like this is underway today at the Cleveland Clinic using their offering, DrConnect.

I believe the approach will be refined even further as the distinction between PHRs and EMRs erodes.  Instead of requiring remote care providers to have their own mini-EHR integrated with their practice management system, they will be able to use the EHR of a large hospital.  I anticipate that they will be able to log on to the system to access their patients’ EMRs as though they were actually resident in the large hospital.  This will all but eliminate the role of Health Information Exchanges (HIEs).  It will also extend the reach of those large hospitals, and aid in the retention and recruiting of physicians.

Why is this important?  Because the federal plan, which won’t be viable for several years, is designed to use software solutions which address a current business issue.  By the time their networked solution is fully functional it will be well on its way to obsolescence.  The government is forcing the expenditure of more than a hundred billion dollars on a static offering to address a non-static issue.  Their approach will not be able to keep pace with the changes demanded by market forces.  It reminds me off building a plan to go to the moon based on where the moon was instead of where it will be.  
[
digg=http://digg.com/business_finance/What_is_the_future_of_the_EHR_N_HIN_landscape]

saint Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy1475 Luna Drive, Downingtown, PA 19335
+1 (484) 885-6942
paulroemer@healthcareitstrategy.com

My profiles: LinkedInWordPressTwitterMeetupBlog RSS
Contact me: Google Talk/paulroemer Skype/paulroemer Google Wave/paulroemer