How daughters relate to EHR

The other night as I’m sitting on a hard bleacher watching my seven-year-olds baseball practice I noticed the mom sitting next to me looking a little forlorn. Being naturally inquisitive, I asked if everything was okay.

“I lost his glove,” she replied.

Noticing a glove on her son’s hand, she saw my look of confusion. “Not his. My husband’s. I had it with me last Thursday, and I left it here.”

“I don’t suppose this was a new glove. Judging by the look on your face I’d say this was his favorite glove; thirty years old, supple, broken in, fold flat as a sheet of paper.”

“Twenty-five years,” she corrected as she lowered her eyes.

“It’s rained the last three days,” I told her, which caused her to grimace even more. Having nothing better to do, I flayed her emotions. “I bet that glove meant the world to him. He probably planned on giving it to your son in a few years. The glove probably reminds him of some of the big events in his life, every scar, each stain on the leather, points to something important. You know, if it was outside for a few days, the field mice will have chewed on the leather.”

She brushed away a tear, and headed to the lost and found.

“Any luck?” She shook her head in despair. “In some countries, if a wife does something life that, the husband can sever the relationship, literally,” I said as I made a slashing motion with my hand. She made the briefest of smiles. At least she knew I was pulling her lariat. Reeling her in, I continued.

“You’re not thinking of spending the night at home, are you? If you are, you should at least call someone and let them know of your plans. He’ll heal over time,” I told her. “But he won’t forget it. Twenty years from now the two of you will be watching something on TV, and something will remind him of the glove YOU lost.”

Fast forward to last night. My daughter and I are getting out of the car so I can coach her and her softball team in the playoff game.

“Is your glove in the trunk?” I asked. This is after I spent several minutes grilling her at home about whether she had everything she needed for her game.

“I hope so,” she said shamelessly as I popped the trunk for her. “You hope so?” I repeated with an edge in my voice.

“It’s not here Daddy.”

I left her with her friends and drove home to look for it. Ten minutes. Nothing. For some reason, I looked in the trunk. There it was. Death by 1,000 cuts.

Does it all come down to baseball gloves?  “I hope so.”  What kind of a response is that?

Will these EHR expenditures help? I hope so.

Can you confirm for me that user satisfaction won’t fall any further? I hope so.

Are we ready for the changes coming to the business model?  I hope so.

Do you think we should continue to employ you? I hope so.

Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

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

My profiles: WordPressLinkedInTwitterMeetupBlog RSS

I got a little sidetracked today…

The nurse left work at five o’clock.  A twelve-hour shift—only lost one, better than some nights, worse than others.  Two hours before sunup, the icy wind gnawed at her ankles.  With her caffeine gauge on empty, she ducked into Starbucks, glancing waywardly at the plethora of coffees posted overhead on the menu board.

“Do you guys actually pay someone to think up all this stuff?”  She asked rhetorically.  The still groggy looking twenty-something barrista behind the counter ignored her, not a bright move.  His hair looked like it was cut with a mower; an errant flap of it skittered over his right eye with each movement of his head.  His right ear lobe was pierced in three places, although he only wore one earring.  The nurse noticed a barbed-wire tattoo around his left bicep.

Intent on continuing the conversation, even if it was to remain one-sided, the nurse inquired, “I suppose Starbucks has a marketing think-tank to invent the product names.  That word “Grande,” that’s Italian, right?”

Twenty-Something occupied himself by steaming a pot of skim milk.

“So, help me think this through,” she implored.  “Since Grande is the one in the middle, it must be Italian for medium.  And, “Venti,” that must mean large.  Right?  So, here’s where I’m confused.  The one labeled, “Tall.”  Something tells me that doesn’t translate to small in any language.  If you take a small cup of coffee, and make people order it as a tall cup of coffee, maybe they will actually think it’s larger than it really is.  QED.  Quod erat demonstrandum.  That’s Latin for cut the crap.”

The nurse knew she was jousting in soliloquies with an idiot.  Nonplussed, Twenty-Something merely rolled his eyes and asked her what she wanted.

The nurse was usually not a half-caff, double mocha, skimmed latte kind of person.  In fact, it troubled her that some people were—troubled her a lot.  The person she had hogtied and left in the trunk of her car was one of them; he hadn’t known when to shut up, so she had done it for him.  By the time she had checked on him during her break, he’d frozen solid.

“Any ideas?”  The Twenty-Something foolishly pressed the nurse.

“What do you recommend for somebody who just wants a cup of coffee?”

“Do you want regular or decaf?”

“What’s the strongest you have?”

“Ethiopian.”

“Give me your largest.”

“Shall I leave room for cream?” asked Twenty-Something.

She looked at the prices.  Two dollars for a cup of coffee.  Why would anyone pay that much and then hide the taste of the coffee with cream, she wondered?  “No cream.  Instead, give me a latte grande with skim milk.”

“One grande latte,” Twenty-Something replied, correcting her syntax.  “Is that all?”

“Better give me a large orange juice.  That’s what’s it’s called, isn’t it, or is that also a grande?”

Her wit was lost on Twenty-Something.  “Large,” she murmured through her teeth.  “And a bagel, plain.”

“Toasted?  Cream cheese?”  She knew he was toying with her.

She’s had enough, grabbed the coffee, and headed for the door.

He hollered for her to pay, but the look she gave him told him to let it go.

Too bad the trunk couldn’t hold two.  She’d come back tomorrow to visit the boy.

The RHIO Answer

It may be helpful as you read this to use your highlighter on the screen to accentuate the important parts or some white-out for the parts you don’t favor.

Do you ever kick an idea around, speaking about it, writing about it, until at some point you finally capture it in a way that makes sense to you?  That’s how I reason things through.  I write like I’m talking aloud and sometimes it lands in my lap.

That just happened to me as I was trying to get my arms around what it is about the concept of the RHIOs that has been bothering me.  Bear with me.  I was on LinkedIn emailing someone using the ‘send a message’ feature.  I was returning an email which she was returning which I had initiated.  The process works like this.  I get an email from LinkedIn telling me I have a message.  I go to LinkedInm read the message and send a reply via LinkedIn.  She receives an email indicating she has a message, goes to LinkedIn, and so forth and so on.

Do you see it?  In this scenario, what is the added value provided by LinkedIn?  Nothing.  It’s all hat and no cowboy.  LinkedIn serves simply as a pass through, contributing nothing.  I wrote in my message to her, “Send me your email address, I feel like I’m in my own RHIO.”

When is a RHIO not aRHIO?  When there’s no need for it.  Is there any functionality intended for the hundreds of RHIOs which couldn’t be dealt with at the N-HIN?  What do you think?

Which EHR mistake would you rather make?

Which EHR mistake would you rather make?–My first post as a contributor to @healthsystemCIO http://ow.ly/1xDx5

When Children Parent

It’s not easy being green—I think that is how the Grinch mat have felt when little Cindy-Lou-Who saw him stealing her Christmas tree.

Cindy Lou Who: “Santie Claus, why? Why are you taking our Christmas tree? Why?”
Narrator: But do you know, that old Grinch was so smart and so slick, that he thought up a lie and he thought it up quick.
Grinch: “Why my sweet little tot…”
Narrator: The fake Santie Claus lied…
Grinch: “…there’s a light on this tree that won’t light on one side. So I’m taking it home to my workshop, my dear. I’ll fix it up there, then I’ll bring it back here.”
Narrator: And his fib fooled the child. Then he patted her head, he got her a drink and he sent her to bed.

I’ve been a father for eleven years.  I have had heart disease for the last seven.  I was a smoker and stopped three and a half years ago.  My children knew the heart attack was a result of my smoking.  Those who have smoked know have difficult it is to stop.  I started again two months ago—sneaking around, burying the butts, washing clothes, gargling—doing whatever it took not to get caught.

My children had never seen me smoke—never until last night.  I snuck out on one of our decks to have a smoke.  One puff later, out pops my Cindy-Lou-Who.  She’s ten.

“Are you smoking Dad?  Why?”

I am not sure which one of us was more upset.  I stood there for a second wondering what to say, wondering if I had the where-with-all to create a Grinch-like fib—a lie.

A good lie may have made the situation disappear, at least temporarily.

One of our family rules is no lying.  I’ve told the children I will never lie to them, and they should never lie to me.  I had to decide which the greater wrong was, telling her a lie, or telling her that I was doing something she knew could kill me—something which would crush her.

I told her the truth.  Her face was expressionless.  She turned and walked away.

We talked.  It takes more than talking.  My wife told me my daughter told her she was upset and what upset her.

I previously tried hypnosis and acupuncture—both worked right up to the point when I got back in my car.  If anyone has any good ideas about how to attack this, please let me know.

My daughter is very smart, and pretty brave.  Now it is my turn.

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

“Who moved my cheese?”

Sometimes you find something that is too good to mess with.  The following comes from “Who Moved My Cheese” by Spenser Johnson.  It is the perfect allegory for healthcare.
Change Happens
They Keep Moving The Cheese
Anticipate Change
Get Ready For The Cheese To Move
Monitor Change
Smell The Cheese Often So You Know When It Is Getting Old
Adapt To Change Quickly
The Quicker You Let Go Of Old Cheese, The Sooner You Can Enjoy New Cheese
Change
Move With The Cheese
Enjoy Change!
Savor The Adventure And Enjoy The Taste Of New Cheese!
Be Ready To Change Quickly And Enjoy It Again & Again
They Keep Moving The Cheese.
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

We’re losing money, but making it up in volume.

I wrote this in response to an article in modernhealthcare.com titled New doc payment system needed
I posted this question on a dozen healthcare Linked in groups; How Can Doctors and Hospitals Make Money in a Post-Reform, Health 2.0 World?  The reason for the question was to probe for ideas for a speech I am giving in May at ICSI.
My takeaway of the responses is that every approach seems to be triage.  I see the business of healthcare, as juxtaposed to the healthcare business (the clinical side) as a 0.2 business model.  Plus or minus variants of IT, the business continues to run in much the same manner it has for the last fifty years.

Analyzing the model, it appears appears to me to be similar to the pattern created by dropping a pebble into a pond–ever expanding circles, but circles none-the-less.  Sort of a fractal business model, each fractal differing only by size.

The business of healthcare could not be facing more fundamental changes–most of which are external, most of which are unknown.  This is especially troubling for an industry whose P&Ls more closely resemble those of GM than of Apple.
It is time to stop relying on the adages, “We don’t know where we are going but we are making really good time,” and, “We’re losing money but we are making it up in volume.”
Rule number one for change–executives must admit they have a busted business model.  Rule number two–executives cannot change Rule number one.”
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 Easy Button

In Woody Allen’s movie Bananas, the dictator of the small country San Marcos declares that, “All the children under 16 years old are now 16 years old.” That was easy.

In the movie in my head, “The EHRs of Madison County,” I run customer service for a EHR vendor.  Customers kept calling to complain. I declared, “Tell the all the customers nothing’s wrong with our products.”

That was easy. Does that work for your implementation?

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

Microsoft EMR: It’s Not Just a Matter of When, It’s a Matter of Who

This guest post ties nicely to some of what I have been writing about regarding why I think firms like Apple, Microsoft, and Google will be the real N-HIN, why PHRs will become EMRs on super smart next gen devices.

Its author is Austin Merritt of softwareadvice.com, a web site that provides advice on selecting EHR software.  I think the strategic reason for Microsoft’s entry into EMR would not be because there are big bucks to be made from a limited number of physicians but because it gives them a foothold into two of the key stakeholders; doctors and patients, one via an EMR and the other through its PHR.  If that is where they intend to stop, they’ve wasted everyone’s time.  I think they have bigger plans, and those plans include having patients walk in to the doctor’s office, both having the same EMR on the same or compatible devices.  The rest of this post is Austin’s.

Microsoft Dynamics is largely present in just about every software market but medical. And they’re missing out big time. The United States healthcare IT market is growing at about 13% per year and is expected to reach $35 billion in 20111. The biggest opportunity for growth in the industry is among ambulatory care physician practices, partly due to the Stimulus Bill requiring the use of electronic health records (EHR) systems by 2015.

You would think Microsoft would be in such a promising industry, but you won’t find a Microsoft EHR available. The primary reason why is that EHRs are highly specialized, and Microsoft’s main products (Dynamics, CRM, and SharePoint) don’t come anywhere near the needs of physician practices. It would be very difficult for Microsoft to build an EHR from scratch and introduce it to the market. So what should Microsoft do to enter the industry? Acquire a current player.

Such an entry into the medical market would mimic the acquisition spree that Microsoft conducted between 2000 and 2002, when it acquired Great PlainsNavision, Damgaard, and several related vendors. These systems were re-branded and offered as Microsoft Dynamics. Before these acquisitions, Microsoft was not present in the enterprise resource planning (ERP) application market. Its only ERP presence was as an infrastructure vendor, licensing SQL Server databases and related platforms to support application rollouts. However, this lack of application presence gave competitors such as Oracle and SAP the opportunity to squeeze Microsoft out of the ERP infrastructure market by pushing Unix, Oracle databases and IBM DB2. By acquiring several applications, Microsoft was able to drive sales of its SQL Server and Windows Servers directly, in addition to the Dynamics applications themselves. This strategy proved effective in giving Microsoft a multi-billion dollar share of the lucrative ERP market.

Setting its sights on the medical market, Microsoft is starting to squeeze its way in with a few smaller acquisitions and developments of its own, mainly Amalga and HealthVault. However, these current medical offerings are on the periphery of the market and do not really target the sweet spot: electronic health records for physician practices. An intelligent acquisition of a large EHR player would provide a key piece of the puzzle for Microsoft’s entry into the medical market.

Acquired by Microsoft in 2006, Amalga provides information connectivity and interoperability to large healthcare networks. It is the primary Microsoft healthcare offering in the industry at this point, although it is not available in the United States. Microsoft may be planning to offer it domestically, as it did with Navision Damgaard, or may be looking to acquire a domestic vendor to complement it. Regardless of Microsoft’s strategy, Amalga still would not address the physician practice EHR market.

On the other end of the spectrum, HealthVault is a patient-managed, centralized health records solution. It is essentially designed to be a reference point for consumers, not a substitute for medical records. If Microsoft were able to introduce an EHR to the market and enable its users to make records accessible to patients, labs, specialists and pharmacies via HealthVault, then they would really be on to something. This synergy with its other products would just be an added bonus to having its own EHR.

So what would Microsoft prioritize as its key acquisition criteria when evaluating EHR targets? They would certainly want target vendors who possess the following:

  1. Large market share and name brand recognition. Microsoft usually likes to be the largest name in the business, so they would definitely want to sell a “big-name” system with which most buyers are already familiar.
  2. A scalable product for small and large practices. Microsoft would need to be able to cover a wide range of medical customers. While its bread and butter is always in the small and mid-size market, they would want scalability into the largest organizations.
  3. A .Net architecture to drag along infrastructure sales. Reinforcing the position of .Net in the medical software marketplace would be important because it would drive further sales of Microsoft infrastructure while squeezing out Unix, Oracle and IBM.
  4. An established, indirect sales channel. Microsoft historically favors selling through partners, including the existing Dynamics dealer network. An EHR vendor with a large dealer network would provide Microsoft an easily transferable sales channel and process.

So which EHR vendor should Microsoft acquire? This is where it starts to get interesting. We decided to examine Microsoft’s ten most logical targets in detail. Two very popular products, GE Healthcare’s Centricity and McKesson’s Practice Partner, did not make the top ten list. While these systems meet many criteria, the parent companies – General Electric and McKesson – are not really acquirable by Microsoft. The remaining ten are outlined below.

MARKET SHARE SCALABLE PRODUCT .NET ARCHITECTURE INDIRECT CHANNEL
NextGen
Greenway
Pulse
Aprima
Allscripts/Misys
eClinicalWorks
Eclipsys
athenaHealth
Epic
Cerner
  • NextGen – One of the “biggest names” in EHRs, NextGen focuses on medium to large enterprises. However, its system is certainly able to scale down to smaller practices. While it is often too expensive for groups with less than ten physicians, it has a strong position in the sweet spot of the market. Its .Net-based system is sold both directly and through a channel network, so NextGen is a good fit for Microsoft.
  • GreenWay – GreenWay has a nice product, but is toward the smaller end of the companies on this list. It sells primarily directly and has some channel partners. PrimeSuite 2008, its EHR and practice management sytem, is .Net-based and is popular among small and mid-sized groups. Microsoft could leverage its resources and Greenway’s technology to become a major force in the industry. Moreover, Greenway doesn’t come with any legacy of old architecture or acquired customers.
  • Pulse – Pulse has quickly climbed its way into the ranks of bigger EHR vendors and will likely stay here for some time. They were one of the first vendors to achieve 2011 CCHIT certification and are receiving a lot of buzz as a result. While the system is scalable and .Net based, Microsoft would likely want to pursue bigger fish for now.
  • Aprima – Aprima (formerly known as iMedica) has focused on its .Net framework and N-tier architecture from the beginning. As a result, its modern platform and interface make it widely received among physicians across a broad range of specialties. While Microsoft would likely focus on larger companies first, Aprima could be a nice additional partner to champion .Net.
  • AllScripts/Misys – A large brand and a publicly-traded company, it is a logical first place to look. After all, the company claims to have 160,000 physicians using its products. However, the 2008 merger between AllScripts and Misys presents the usual integration challenge, which might keep this firm busy for quite a while. Although we think the future of AllScripts/Misys is very promising, Microsoft probably wouldn’t get involved at this point.
  • eClinicalWorks – This system is probably the most ubiquitous of the list, especially among smaller practices. The recent deal to sell eClinicalWorks through WalMart will definitely increase its brand recognition and share of the market. However, the system is built in Java, an open programming language that is the traditional enterprise alternative to Microsoft .Net. Microsoft would most likely rather acquire a pure .Net system or one that is at least close to it, especially with Oracle, IBM and SAP all embracing Java.
  • Eclipsys – Eclipsys acquired MediNotes in 2009 in an attempt to move users to its Peak Practice EHR. While Eclipsys is fairly popular among hospitals, Peak Practice has not achieved similar success among small to mid-size outpatient practices. Existing MediNotes users are not thrilled about being forced to purchase Peak Practice and we’ve seen quite a few seeking a new solution from a new vendor. We think the success of the MediNotes deal is unclear and Microsoft would steer clear for now.
  • Athena – The youngest company on this list, Athena’s product offering is slightly different from the others. Its system is offered via software as a service (SaaS) and is combined with outsourced billing and revenue cycle management services. This offering is indeed unique, but not a suitable target for Microsoft due to its SaaS offering and labor-intensive service component.
  • Epic – This company possesses an interesting niche in the market. It has only 190 clients, but 150,000 physicians using its products. This is due to its focus on only the largest healthcare organizations in the United States. While this focus is great for Epic, it wouldn’t be effective for Microsoft. Epic will never be able to achieve the ubiquity in the small to mid-sized market where Microsoft dominates. It also sells direct, contrary to Microsoft’s traditional indirect sales mode.
  • Cerner – Cerner’s cash cow is Millenium, a product designed primarily for hospitals. PowerWorks, its outpatient EHR, does not possess the market share among physician practices that Millenium enjoys among hospitals. While Cerner is a recognized name, few practices consider PowerWorks. It is also an older system. Cerner would need to improve its PowerWorks offering before becoming a suitable target for Microsoft.

Although NextGen is not currently dominant amongst small practices, Microsoft could bring them downmarket. NextGen is unable to serve these smaller buyers for two reasons: 1) small practices cannot afford an enterprise expenditure; and, 2) NextGen does not want to (and maybe cannot) devote resources to chasing smaller deals. If Microsoft owned NextGen, they could double down on pursuing smaller practices, perhaps through their channel partners. They may even lower prices to buy market share and make up the difference with revenue from services, SQL licenses, and maintenance.

Which EHR do you think Microsoft should acquire?

Paul M. Roemer
Chief Imaginist, Healthcare IT Strategy

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

My profiles: WordPressLinkedInTwitterMeetupBlog RSS

The McDonald’s healthcare business model

Sarah Palin continues to receive national media coverage.  Many hospitals continue to implement EHR without any measurable goals.  (One of those is bad.)

The year is 2014.  I had this dream the other night of having dropped my IQ when I was at the hospital, but I couldn’t remember which hospital, so off I went, hospital by hospital looking for my IQ—I realize there are those of you who believe this isn’t a great loss.

In the first hospital I visited, a photo of the new president hung behind the registration desk.  Next to her photo—surprised some of you with that I bet—hung the photo of the Secretary of Hospital Sameness.  For a while I wondered what someone in that position did day to day.  The more hospitals I visited, the more apparent it became.  The hospitals all looked very much alike, right down to dust on the fake Fichus tree next to the water fountain.  For a while I thought that maybe I was driving in circles until I noticed that even though receptionists were all named Gladys, they wore different clothes.  It was almost like visiting Stepford.

Does anyone have the sense that what reform will really accomplish is to reform away healthcare competition?  There appears to be a move afoot towards the efficiency that is created by sameness—what I call the McDonalds healthcare model.  Put one on every corner.  Make them identical.  Limit the options.  Everyone gets a burger.  Nobody gets a steak.

Eliminate waste.  Does that mean eliminate ways of operating that differ from how the government permits them to operate?  There is talk of pulling costs out of the system thereby making it more efficient.  You tell me.  Is the argument that there is so much inefficiency that by becoming efficient not only will we be able to cover everyone, but we will be able to do it at a cost below what it costs to care for far fewer people?

How do you understand it?  Are costs being removed, or simply moved?  If someone with no access to healthcare suddenly has healthcare—a good thing by almost anyone’s standards—the reasoned person knows costs have just increased.  (Healthcare theorem 1:  The cost to provide healthcare to 2 people is greater than or equal to the cost to provide it to one person.)  If costs have increased, how does one make a believable argument that the basis for reform is cost reduction?

I try hard not to be too cynical, but sometimes I think, why bother.  By the way, I found my IQ.  Thanks for asking.

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