Curbside Consult with Dr. Jayne 2/27/12

Over the past several years (and especially with Meaningful Use) there has been a fairly significant shift in the attitudes of ambulatory physicians who are making the leap to electronic health records. The hospital-based physicians (and ambulatory physicians who see patients in the hospital) are a different story. They’re a captive audience who has always been subject to hospital control and who has a long-standing history of adapting to things imposed by various Big Brother entities: the Joint Commission, the hospital’s formulary team, insurance and hospital case managers, etc.

Those physicians have done pretty well adapting to electronic documentation, computerized order entry, and the like while in the hospital. Hospitals have also tended to phase their implementations over the scope of years – deploying in a modular fashion with lab, nursing documentation, CPOE, and provider documentation all done as separate initiatives. Ambulatory docs who dislike the hospital’s conversion have been able to escape back to the relative safety of private practice and cling to their paper charts.

As ambulatory physicians transition to EHR, though, they tend to deploy more rapidly – wanting to get rid of all the paper immediately, but also with a strong drive to keep the revenue stream steady. When I started deploying EHRs some time ago, we worked with early adopters who believed in the promise of electronic recordkeeping and were more willing to staff up, reduce patient load, or work longer hours to realize their goals. These physicians are now mature users who are leveraging their EHRs to achieve advanced Patient Centered Medical Home designations, increase fee schedules through demonstrable quality, and improve patient satisfaction.

On the other hand, there are now thousands of physicians who previously found the idea of the EHR distasteful and feel forced to make the transition. Whether by peer pressure, payer requirements, or the threat of government-related penalties, they’re now implementing and with a significantly different strategy than may be prudent.

More often, I hear of physicians that want to implement a system fast, cheap, and easy. The rest of us who have done this for a while know that it’s very difficult (if not impossible) to do all three. Often these late adopters refuse to follow vendor advice, consultant advice, or frankly anyone’s advice. Convincing them to cut schedules or hire staff is a challenge. Ultimately, it’s the patients who suffer.

As the healthcare market consolidates, hospitals and health systems are looking to “align” (one of my least-favorite buzzwords) with community physicians to ensure profitable referral, ancillary, surgical, and inpatient revenue streams. Many are offering subsidies and other incentives to bring these providers onto EHR systems.

Often these practices don’t actually want to align, but are feeling cornered and desperate. Some have previously turned down acquisition offers from the same hospital and see taking a subsidized EHR as a way to be somewhat protected from burdensome federal requirements while maintaining at least some degree of autonomy. Others simply can’t afford an EHR without the subsidy. A last group is providers who’d like to be acquired but for various reasons aren’t suitable candidates, but hope that alignment (and sending a steady volume of referrals which of course cannot be spoken about) will result in being ultimately asked to the dance.

These physicians often deploy on an existing system-wide EHR. Since they’re late to the game, though, they haven’t been stakeholders in any of the decision-making that’s already occurred and often have less buy-in to the idea of group goals than those users who are actually part of the group.

Another angle is that even though subsidized, these physicians are paying customers with different expectations than employed physicians and different ideas about governance. Of course, this would have been true even if these subsidized physicians were early adopters, but the differences are magnified by them being late in the EHR game and feeling pressured to demonstrate Meaningful Use as quickly as possible.

I still go out on implementations and perform physician training on a regular basis. Until recently, most of the physicians I have worked with have treated me as a respected colleague who could assist them through the difficult transition. Some have even looked at me as some kind of EHR shaman, able to smooth their journey to the other side with mystical wisdom. Of course, there have always been a few docs who were borderline (or overtly) hostile, but they were few and far between and usually we could leverage their partners or peers to moderate their behaviors.

Lately I’ve run into more and more angry physicians who are completely resistant to the idea of the EHR transition even though they’ve agreed to go paperless. Some are passive-aggressive, but others are openly abusive. This manifests in a variety of ways – disruptive behavior, inappropriate comments during training (think middle school students with a substitute teacher), or refusing to be trained at all. I find the latter group the most frustrating because then they can’t figure out why the system is so hard to use and scream the loudest about lack of support.

Looking at the data on how many physicians are actually using EHRs in practice (let alone being robust users) we’re just approaching the midpoint. If what I’m seeing in the field is any indication, it’s only going to get tougher as the last-ditch adopters come through with increasingly unrealistic expectations and correspondingly difficult implementations.

I feel bad for the vendors and for the teams who have to support these folks (mine included.) I feel bad for the physicians who don’t want to transition to EHR and the staff members that have to work with them every day. But most of all, I feel bad for the patients who entrust them with their care. Regardless of what they think about the EHR, the IT team, or the government, I hope the angry docs remember that after all, it IS all about the patient.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 2/13/12

Care and Feeding of the CMIO

I frequently receive calls, e-mails, and LinkedIn messages from recruiters looking to fill CMIO positions. This might be a good thing – a sign that hospitals and health systems are figuring out that they really do need a CMIO after all and are looking to fill newly-created positions. A wise man once told me that it’s a good idea to spend 10% of your time looking for your next job, so I do read or listen to everything that comes my way. Who knows? Someone could be offering a CMIO position in a tropical location with excellent benefits and an assistant to deliver a slushy adult beverage every day at 5pm.

Unfortunately judging from many of the position postings I see, not all of them are new positions. In fact, some of them have been vacant for a long time and the postings have remained unchanged despite being unfilled. Some employers are just not understanding what CMIOs are looking for as far as scope of work, compensation, and job satisfaction. Let me give you a few examples.

Ability to continue practicing medicine. This is important for a variety of reasons. Credibility is often linked to actually using the systems that we’re advocating for our colleagues. Being an actual user of the system is important in understanding the reality and magnitude of issues raised by physicians. I’ve been able to shoot down the “it takes 17 clicks to do this” rhetoric spouted by some of my colleagues because I’m a user – and I know for a fact it’s a gross exaggeration or an example of a provider not following the best practice workflow.

Additionally, requiring a current active medical license of applicants can also screen out physicians with drug problems, failure to pay child support, failure to pay taxes, criminal records, and other undesirable employee attributes. I recommend that potential employers offer this as an option rather than a requirement, though. Keep in mind there are a lot of good candidates out there who don’t have licenses – many never thought they’d practice again and let their licenses lapse – so don’t use it as an absolute yes/no test. On the other hand, watch out for resumes that show people were in practice until recently and or have unexplained gaps in their work histories.

Travel and after-hours commitments, meetings, etc. One recent job description I saw stated that the job involved 50-75% travel – mostly regional, but some national. Considering that most employers are looking for people that have not only a medical degree but also either an advanced degree (MBA, MHA, etc.) or an informatics certificate, plus three to five years clinical experience and three to five years CMIO or medical director experience, this could be a problem. You’re talking about a potential applicant pool that will be in their late 30s to mid-40s age-wise at a minimum. These are going to generally be people who have families, often with small children, and your position may not be very attractive to them.

Continuing education and meetings. This should be part of the offer. It’s extremely helpful to be able to have not only the time (either on the clock or as dedicated continuing education time) but the budgetary resources to travel to a couple of meetings a year. Although we’re all increasingly good communicators in the virtual world, there is still value in face-to-face interaction with colleagues and peers, especially if your organization is in a town where there are only a handful of CMIO types. An offer I recently considered had not only less vacation than my current package, but I was explicitly told that as an IT employee (rather than a physician employee) I was not entitled to continuing education days or funding because “only the physicians get that.” I decided right away that they didn’t “get” what a CMIO was all about, and that was the end of my looking there.

Administrative support. With everything your CMIO is going to be tackling along the lines of Accountable Care, Meaningful Use, and the acronym soup that is our lives, he or she is going to need some help. Even if it’s just a shared administrative assistant, it can be a huge benefit to not have to spend time each day juggling calendars and handling daily office “stuff.” At a minimum, I’d expect some of the same things I’d expect from a good practice manager – opening / sorting / prioritizing mail and phone messages; ensuring regulatory compliance (completing license renewals and credentialing if those are required for practice); coordinating support resources, and handling other ad hoc requests. I would never consider a position without some kind of administrative support. The ability to tackle spreadsheets, flow chart software, project management software, and the ubiquitous slide shows is almost mandatory as well.

Benefits and salary. If you’re committed to finding an experienced CMIO who can hit the ground running, you’d better be willing to pay for it. Someone with ten years’ experience is not going to settle for an entry-level physician wage. The same group I mentioned above was offering a salary that was barely commensurate with the guaranteed salary they were paying new physician grads who were joining practices. When asked for the rationale, this was the answer: the CMIO doesn’t see as many patients or generate as much revenue. Again another indicator of an organization who doesn’t “get” the CMIO role. We may not be seeing 95% of the MGMA statistics for patient volume, but what we do can allow your physicians to reach that level in a much more efficient fashion as well as to assist in increasing the quality of care provided. Government and payer requirements are increasingly complex, and if you expect your CMIO to be able to bob and weave along with the myriad of changes, you better be willing to pay for it.

Culture and autonomy. CMIOs may report to a variety of people – CIO, CEO, or someone else entirely. Some organizations have complicated dual-reporting structures. Yet others have a clear chain of command but a parallel network of “informal” governance that makes it difficult to get things done. The best way to alienate a new (or potential) CMIO is for them to feel they’re in a place without clear direction or support for their initiatives. Making them obtain approval for every little thing is another good way to disenfranchise your CMIO. For those organizations that refuse to use the CMIO title, making your director of medical informatics (or whatever you want to call it) feel like a second-class member of the leadership team because they don’t have the title is another good way to encourage your CMIO to leave.

I worked for a group like that for a while. It was unpleasant, and each day I felt like I had just played 20 rounds of Whac-A-Mole. Because there was no real organizational culture, there was little room for strategy and great need for firefighting skills. Everything was a crisis that had to be dealt with and the leadership was constantly in transition. It seemed like I had five different bosses at any given time and everything was a priority. Initially I thought it was just me trying to adjust (I was a Padawan Learner then rather than the Jedi I am today) but it turned out it was a vacuum in leadership and culture.

If you have a handle on these things, you’ll probably do pretty well trying to hire your first CMIO. If you’re an organization where that role is well established, it might be worth taking a little time to see how your CMIO thinks you measure up in these areas. The CMIO is still a relatively new addition to the corporate team and it’s certainly OK for the position to change and evolve over time.

I’m pretty happy in my current role. But if you do happen to be located in a tropical or otherwise fabulous place and can provide the aforementioned fuzzy drinks, e-mail me.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 2/6/12

The past week has been crazy, and unfortunately the crazy spilled into the weekend as well. I had visions of the perfect thought-provoking topic for this week’s Curbside Consult, but every time I tried to flesh something out, it escaped me. Instead, I found myself musing on what I planned to do at HIMSS and which vendors I wanted to be sure to check out. Mr. H and Inga are hard at work on their “must see” vendor list and I’m working on my personal CMIO hit list.

For the CMIO (or anyone involved in evaluating new products or making purchasing decisions) it can be a great way to sort the proverbial wheat from the chaff. Many products look great in brochures or on the Internet but pale when you see them in person. Last year one of my “hot items” (sad that I think this is hot, isn’t it?) was wall-mount swing-arm brackets for monitors. The true test of quality and sturdiness is being able to check them out in person rather than trust a marketing slick.

You may ask, why does a CMIO care about brackets, and should she? The answer is yes. If I have to use it every day, I want to make sure it’s going to work for me and for the hundreds of physicians I represent. That’s not to say that the CMIO should be out personally investigating everything that needs to be purchased. Generally I prefer that the engineering and purchasing folks work their magic first, culling the herd down to their top choices, then allow a small group of providers to make the final call.

This year I have a laundry list of things to look at. Some are a bit gadgety (washable keyboards, COWs), others are more esoteric. I want to see how vendors are progressing with natural language processing and where they stand with clinical decision support. Are they going home-grown, or incorporating third-party solutions? How are the attendees responding to them? Who has incorporated Medicomp’s Quippe product that blew our minds at HIMSS11?

Like last year, I hope to have some time to cruise the exhibit hall with Inga, but I will also have some time to peruse the booths with a few other CMIOs and share their opinions and thoughts. One of my friends is a first-time attendee, so watching his expression as he sees some of the people out there will be interesting. A note to ChipSoft: I see you’re exhibiting again. If you’re giving away the clog slippers this year, please stash some for Inga and me because we’ll be looking for them and you ran out last year.

The marketing materials from exhibitors are arriving much more slowly than I remember from last year. So far, my favorite marketing piece is from CDW Healthcare, with their “What happens at HIMSS definitely won’t stay at HIMSS” tagline and accompanying poker chip. Although I like the idea of taking home things I learn, based on the potential for Inga and Jayne to have a good time, I’m sure some things will be staying well within the 89109 zip code.

Speaking of marketing, I received quite a response to my comment on why the soles of Christian Louboutin shoes are red. One reader shared his shame:

I must know. During a Battle of the Sexes trivia contest, I and my fellow male panel of knowledge brokers failed to identify the maker of the famed red sole shoe. It was the tipping point in a tight contest that found us falling to the gals. I now must know why the soles are red…

A certain savvy reader provides the answer:

Just a quick comment to say I thoroughly enjoy your commitment to giving your readers a well-balanced education. Not just what’s up in healthcare, but why CL shoes have their distinctive red sole! A mundane process turned into a brilliant marketing differentiator. I’ll be looking out for them!

In short, it’s all about branding. Louboutin trademarked the red-soled look in 2008, fighting to protect the distinctive look when Yves Saint Laurent came out with a red sole in 2011. YSL claimed in court documents that red soles existed long before Louboutin trademarked them:

Red outsoles are a commonly used ornamental design feature in footwear, dating as far back as the red shoes worn by King Louis XIV in the 1600s and the ruby red shoes that carried Dorothy home in The Wizard of Oz.

There’s your fashion moment of the day, and hopefully some of you can leverage this newfound knowledge to win the hearts of your lady-friends who might have a thing for shoes, not to mention to triumph in the next battle of the sexes trivia night.

Have a favorite HIMSS (or other show-related marketing piece) to share? Does it belong in the Hall of Fame or Hall of Shame? E-mail me.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 1/30/12

Don’t Take Me Out of Context

Depending on the size of the communities they live in, CMIOs can sometimes feel isolated. Some may work in cities with multiple hospitals and health systems and have easy access to peers (and getting together over drinks is certainly fun!) but many work in towns with only one hospital. For the latter, finding and collaborating with peers can be a challenge.

I belong to a virtual community of CMIOs that contains a mix of big-city and small-town CMIOs. There are a couple of former CMIOs and a couple of young pups just starting out in informatics thrown into the mix as well. It’s been a great resource for idea sharing over the last several years and has helped me preserve my sanity on numerous occasions.

We recently got into a discussion about single sign-on options. Even those hospitals with single-database systems often have legacy systems with which clinicians need to interact. They also need to access a variety of homegrown and interfaced applications in order to care for patients and manage clinical data. Many hospitals have tackled this with single sign-on, proximity badges, or other strategies to reduce the need for clinicians to manage multiple passwords.

I’ve used several of these solutions and they are undoubtedly cool. However, they lack the ability for clinicians to rapidly access a single patient across multiple systems. Providers end up searching for the patient in multiple applications while they try to mentally create a unified view of the patient. This is less than ideal. One of the young pups in the group mentioned that he was looking at context-sharing solutions in an effort to remediate this problem. Luckily we have a few CCOW aficionados in our group. For best-of-breed shops, this can be essential to efficient access by clinicians.

For those of you who don’t know where I’m going with this, let me introduce you to CCOW. CCOW stands for Clinical Context Object Workgroup, which is an HL7 standard that allows clinical applications to share information. Through this standard, applications can participate in both user context sharing and patient context sharing.

From a practical standpoint, this means that when the clinician accesses a patient chart, all other applications that the provider is accessing synchronize to that patient. When user context is also included, it may also facilitate reduced sign-on into applications which are subsequently accessed. CCOW can go deeper than just user and patient context – encounter context can also be included.

CCOW (thanks to Health Level Seven, Inc. for the graphic) is often misunderstood by clinical and IT people alike. Although many vendors create their applications to be CCOW compliant, this does not mean that just installing two of them will “automagically” link them together. Context management is required. When the systems lack a shared master patient index or a common patient identifier, an intermediary mapping agent may also be necessary. Dedicated context management software may also need to be installed locally or on servers to help synchronize client-server and Web-based applications.

CCOW also doesn’t magically move data from one application to another. It simply allows users to access information on a single patient across disparate applications with a minimum of fuss and bother. Depending on the setup of the environment, CCOW may not work the same for users accessing from home or from non-network devices.

The use of CCOW also creates additional testing requirements during application upgrades in order to ensure that functionality remains unchanged. I know of at least one major vendor whose CCOW functionality has been negatively impacted by an upgrade, causing much consternation to the numerous hospitals live on its product.

There are multiple context managers out there, including Microsoft’s Vergence product (formerly of Sentillion) and Carefx Fusionfx. The fate of the Vergence solution is one reason that the recent Microsoft / GE Healthcare joint venture (first reported by Mr. HIStalk back in December) makes a lot of people nervous. Customers were already twitchy after Microsoft acquired Vergence from Sentillion in 2009, with reports of a decline in customer service and support.

Quite a few significant players in the hospital industry are customers, so hopefully that will be incentive enough for the as-yet-unnamed entity to resist making a mess of it. (Any idea on that name? I’ve been keeping my eye out, but haven’t seen anything, and there’s nothing on the Microsoft Health Web page yet, either.)

Most of the big vendors are CCOW compliant, but there are still some who don’t understand the value proposition to clients. Far from a gimmick or a “nice to have” feature, for organizations such as Mayo Clinic, Johns Hopkins, and many more, it’s essential. Once again, I was grateful to my CMIO coffee klatsch for a good discussion and plenty of humorous anecdotes. I’m looking forward to catching up with y’all at HIMSS12 in just a few short weeks!

Have a question about virtual networking, best-of-breed systems, or what the new Microsoft/GE entity should be called? E-mail me.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 1/23/12

I was inspired by Ed Marx’s post last month, Transformation Through the Written Word. He talks about doing book studies with his direct reports, which then expanded throughout the workplace. The thing that most fascinated me about Ed’s piece was his book list. Having been the victim of a boss who tortured his team with 17 Irrefutable Laws of Teamwork, I was surprised (and quite pleased) to find books on his list which didn’t scream “teamwork!” or “leadership!” or “business!”

I’m a voracious reader, although lately I’ve been reading some fairly insubstantial fluff in an attempt to reduce stress and achieve relaxation. One of my best friends keeps recommending things like The Mathematics of Life or The Omega Theory,  but I just can’t seem to get into the mode for deep thinking.

I liked the fact that Ed’s list is eclectic – it includes James and the Giant Peach and Disney psychology along with the classic management and leadership-themed works. One of my personal favorites is The Checklist Manifesto: How to Get Things Right  by Atul Gawande. This book should be required reading for everyone who does anything which remotely impacts patients or other living things. I’ve liked Atul Gawande since reading his first book, Complications: A Surgeon’s Notes on an Imperfect Science, years ago. It helped to make sense of the things I encountered during training and in understanding the psychological complexity of events physicians are exposed to.

Speaking of psychological complexity, I’m already tired of the run-up to the November elections. One of the hot topics is healthcare reform. I’m not convinced that any of the candidates is qualified to actually speak to the issues. The general public gets pulled into the rhetoric as well. I end up discussing healthcare politics with a patient at least a couple of times a day. I recently ran across a book that should be required reading for anyone who thinks they are educated regarding the delivery of healthcare in the United States.

I don’t want to turn into Oprah, but I’m throwing it out there as the first “Dr. Jayne’s Book Club Challenge.” Some talking points from my friend Doug Farrago (of Placebo Journal fame) really sum it up:

• Our society has warped our perception of true risk. We are taught to fear vaccinations, mold, shark attacks, airplanes, and breast implants when we really should worry about smoking, drug abuse, obesity, cars, and lack of basic hygiene.
• Somehow we have developed an expectation that our health should always be perfect.  We demand unnecessary diagnostic testing, antibiotics for our viruses, and narcotics for bruises and sprains. And due to time constraints on physicians, fear of lawsuits and the pressure to keep patients satisfied, we usually get them.
• The bottom line is that most conditions are self-limited. “Our best medicines are Tincture of Time and Elixir of Neglect.”
• There is tremendous financial pressure on physicians to keep patients happy. But unlike business, in medicine the customer isn’t always right. Sometimes a doctor needs to show tough love and deny patients the quick fix. A good physician needs to have the guts to stand up to people and tell them that their babies gets ear infections because they smoke cigarettes. That it’s time to admit they are alcoholics. That they need to suck it up and deal with discomfort because narcotics will just make everything worse. That what’s really wrong with them is that they are just too damned fat.  Unfortunately, this type of advice rarely leads to high patient satisfaction scores.

It’s available now from Amazon, although not yet in Kindle format, which I know will make some of you sad. If you’ve read it, let me know what you think. And if you know anyone in politics, feel free to leave copies on their desks.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 1/16/12

Jayne Gets Her Tweet On

During a recent e-mail exchange, a friend of mine repeatedly chastised me for not being on Twitter. He failed to see why someone who lives in the land of blogging and social media wouldn’t want to Tweet with the rest of the world. To be honest, I’ve been more than a little scared to take the plunge. Knowing all too well what an outrageous time suck Facebook can be, I didn’t want to get into something else that had the potential to further unmask certain addictive personality traits.

Nevertheless, I took the plunge. Signing up was deceptively easy, although I’m having a hard time deciding who to follow. I don’t want to overdo it with too much information. So far, I’m following HIStalk (of course), my BFF Inga, and my very public secret crush Farzad Mostashari (and his dashing bow tie.) You can follow my shame spiral @JayneHIStalkMD .

While I’m feeling social, I decided to share some reader correspondence. It goes back a bit, as you can imagine my inbox usually looks something like the hallways of a New Orleans emergency department during Mardi Gras (which incidentally is just a month away for those of you who plan to get your party on).

From Miami, My Amy: “I was at a physician office this week and they couldn’t get the right patient into the right room. They took me back twice and reseated me in the reception and did the same thing to another person. Made me wonder whose medical record they were viewing. I find I am becoming a “difficult” patient, bristling with all the paperwork to fill out time and time again… with the same provider.” I agree, this sounds pretty annoying and it’s also a significant patient safety issue. I do hope your physician apologized though. I that was happening in my office,I would expect my staff to make me aware so that I could say something to patients.

From Bama Bubba: “Your Curbside Consult today really charged up my growing OCD. Public restrooms never have commode lids, plus they often flush with a great torrent of surging water, not the home-based gentle swirl. This flushing surely raises huge clouds of nasty water droplets perfect for deep lung deposition. I had a remembrance of the huge toilet complex at McCormick Place in Chicago and literally dozens of commodes in narrowly separated stalls, used by folks from all over the world, being flushed at the same time. Whoa! Talk about a toxic cloud of international viruses. Excuse me, I have to go wash my hands again.”

From HealthNut: “Re: shift work food options. I worked 11-7 for a stretch and our food options consisted of coffee, colas, cigarettes, and vending machine staples of sandwiches with greenish mystery meat/cheese, lukewarm canned chili or Beanee Weenee, peanut butter crackers, candy bars, and gum. The only thing that kept us from morbid obesity was bring broke all the time because we were students.” Yeah, that and the fact that we had to run arterial blood gas samples to the lab in styrofoam cups of ice chips and run to radiology to look at actual x-ray films all night long. At my hospital, our vending machines were just updated with a new item: White Castles.

From Golfing Great: “Regarding your recent post on technology as the new scapegoat. It’s not only the users who operate the systems, but also the folks who create and maintain the systems, the training they receive, their proficiency, and their ability to anticipate — or at least understand — the needs of those users (which I try to do by subscribing to HIStalk, so thank you very much!) When problems occur, there is usually more than enough blame to go around. It’s a shame the time spent deflecting isn’t devoted to planning, training, and coordination instead. It is important to keep in mind that systems are comprised of technology, people, and processes, all of which must function properly for the system to succeed. I’m not sure that any system will ever be able to address the intentional ignorance demonstrated by people in some of the scenarios you quoted, certainly technology alone cannot. I couldn’t agree more that culture is key, particularly when, even in spite of best efforts, systems are inadequate.” Thanks for that feedback. If I could convince organizations of the need to do one thing prior to and during implementation of any health IT system, it would be this: change management.

From Mr. Clean: “What is the evidence base on best way to sanitize tablets and (especially) keyboards? Inquiring minds want to know!” There’s not a ton of data on this. Personally, I use the same wipes that we use in the emergency department, which are a healthcare-grade sanitizing wipe for hard surfaces. Low-level cleaning requires keeping the surface wet for at least thirty seconds; higher-level disinfection requires keeping the surface wet for at least three minutes, which is a little harder to do with a keyboard.

Just a few days ago, the FDA cleared a self-sanitizing hospital keyboard with the bargain price of $900. The solution uses UV light to eliminate bacteria. Another reader suggested the WetKeys Washable Keyboards, which actually look pretty cool and have much more accessible pricing. It would definitely be easier to keep those wet for three minutes than a traditional keyboard. I really like the looks of their washable flexible keyboard. Too bad Santa has already come and gone — he could have rolled one up and left it in my stocking.

Have questions about ICD-10, the most common injuries seen during Mardi Gras, or whether you should order your White Castles with double pickles? E-mail me.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 1/9/12

The New Year is ringing in slowly from a news perspective. Maybe everyone’s just a little saggy from the holidays. I did manage to find some thought-provoking tidbits for the week.

Almost 40,000 new laws have recently gone into effect, now that 2012 is here. The biggest changes involve immigration, civil rights, budget woes, abortion, and other hot-button issues. Some less-reported but no less interesting legislation:

• Georgia will require those who drive golf carts on the road to have brakes, back-up lights, and a horn.
• Illinois allows motorcyclists to run red lights if they don’t turn green (the lights, not the motorcyclists) in a reasonable amount of time.
• Nevada is requiring fire performers and their apprentices to register with the state fire marshal.
• Utah nixes happy hour.

Congressman Edward Markey has asked HHS Secretary Kathleen Sibelius to tackle the issue of alarm fatigue. Specifically, he requests that the Institute of Medicine look at the issue and recommend solutions.

The New York Times reports on a new Medicare study that claims hospital workers only recognize and report medical errors and accidents one out of seven times. Daniel R. Levinson, inspector general of the Department of Health and Human Services, also notes the following:

• More than 130,000 Medicare beneficiaries experienced at least one adverse event in a hospital during a one-month timeframe.
• Although hospitals have systems to report adverse events, staff failed to report most of the harmful incidents.
• Hospital administrators are aware of underreporting by staff.
• Hospitals fail to connect adverse events with systemic quality concerns, resulting in few changes to policies and procedures.

I’m trying something new this year. My goal is to complete all of my required Continuing Medical Education and Maintenance of Certification activities at the beginning of the year rather than waiting until December is halfway out the door. I’ve been doing pretty well so far, plowing through piles of journals and article links that people have sent.

The Journal of Hospital Infection publishes a study on the hazards of lidless toilets, especially in spreading pathogenic bacteria like Clostridium difficile, one of the nastiest hospital-acquired bugs. In my hospital, the only commodes with lids are those little space-shuttle style ones found in the ICU patient rooms. Now that I think of it, you don’t see too many staffers wearing full protective equipment when helping patients in that way. Something to think about. Kind of makes my kvetching about dirty keyboards less relevant.

PLoS Medicine publishes some interesting thoughts on a topic dear to most health care workers and an increasing number of IT workers: “Poor Diet in Shift Workers: A New Occupational Health Hazard?” It cites data (including some from the Nurses Health Study) linking shift work to type 2 diabetes in women. Potential underlying mechanisms include poor diet and exercise, poor sleep, and disruption of circadian rhythms. Knowing the differences between day-shift menus and night-shift menus in most hospital cafeterias, brown-bagging it is probably the safest option if you’re looking at interventions.

David Blumenthal penned the recent A Piece of My Mind column in the Journal of the American Medical Association. It’s titled, “A Physician Goes to Washington… and Safely Returns,” which actually encouraged me to read it, unlike most of the pieces in JAMA which sound like something to read with a glass of warm milk when you have insomnia. I was hoping for some juicy revelations or HITECH wisdom, but it’s mostly about what it’s like to spend time in government service.

I’ve finished my stack of mandatory reading for the day, so am heading to lounge with a bit of fluff – Explosive Eighteen by Janet Evanovich. I can’t believe they’re finally making a movie of her first book One for the Money – it’s due out the end of this month and I’m counting down.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 1/2/12

What Gets Measured Gets Managed

During the last five years, we have seen significant shifts in how healthcare is delivered and in the way in which different healthcare services are valued. Most of us have realized for quite some time that fee-for-service medicine is clinging to life. Pay-for-outcomes is going to be the order of things from here on out.

Hospitals are no longer going to be paid to ameliorate hospital-acquired conditions or to deliver care to patients who were impacted by preventable harms. Physicians are going to be judged on their patients’ lab data and biometric information rather than the number of visits they bill.

Care will be transformed regardless of how we feel about it, whether it’s by the name Accountable Care, Shared Savings, or Pay-for-Performance. It’s something we all need to get used to.

My colleagues were ringing in the New Year this morning in the time-honored tradition of complaining around the coffee pot. (Most of us were rounding a bit later than usual and I did see a couple of bloodshot eyes.) It seems that many independent physicians, particularly those in small practices, don’t know where to start. (Employed docs are generally confused too, although to a slightly lesser degree.)

I decided to introduce them to Peter Drucker, whose famous statement, “What gets measured gets managed,” should be well understood by now. But let’s just say I was more than surprised by the blank looks in front of me.

Several of the docs didn’t understand that Meaningful Use is going to get trickier as time goes on. Although there are some metrics for Stage 1, many of them are easily achievable with a minimum of work. (Apparently though not as easy as people might think – I’m still stumped by the phenomenon of people unsuccessfully attesting. If you don’t have the numbers, why would you attest? Still waiting for someone to shed light on this.)

Although we don’t have final metrics for Stage 2 and beyond, it’s virtually guaranteed that the bar will be higher and the hoops smaller. In talking with the docs in the lounge, though, many of them don’t have a clue how to approach care metrics – even those with sophisticated software. I’m seeing far too many physicians who are barely using their certified EHRs, who are confused by some of the terminology, or who are hung up on wanting flash and sizzle.

I felt like I was giving a Grand Rounds presentation because our friendly chatter turned into a lecture that I probably could have given CME credit for. Docs don’t seem to understand that you have to know what you’re looking at in order to drive change. It’s not going to drive itself. You have to figure out what you want to work on, then measure it, then work on it, then measure it and work on it some more. Lather, rinse, repeat.

It seems pretty straightforward, but maybe it’s not, so allow me to share some other “secrets” that your docs may not know.

First, don’t get hung up on the fact that your EHR vendor may or may not have a registry or dashboards. Maybe they do and it’s just called something else, or maybe they don’t. One doc I was chatting with was caught up in the fact that he didn’t have his vendor’s dashboard product live yet. He was either under the impression (or in denial – it’s debatable) that he couldn’t start managing care until he had the pretty charts to back up the data. He didn’t like it too much when I called baloney on that one.

Most certified EHRs have at least some minimally decent ability to do reporting. That’s really all you need to start. If you have discrete data, you can report on a wealth of conditions. Prostate cancer screening? Check. Blood pressures? Check. Documentation of advance directives? Check.

You don’t need pie charts to tell you how to care for patients. When your report has blanks on it because you haven’t documented an item for a particular patient – that, my friends, is an opportunity for care.

Second, don’t get baffled by the metrics. Looking at some of the NCQA or NQF or MU measures and how they’re calculated makes my head spin as much as yours does. If you’ve never tried to do quality improvement before, start with something basic.

If it’s important to you to make sure every patient over 50 has a documented cholesterol test, start there. Don’t get hung up in the numbers and managing everyone down to an LDL of 70 or figuring out complicated exclusions. Start with something manageable, such as actually testing everyone. Run reports, do outreach, give it a month or two, then run those reports again and see if you’re making a change.

Third (and this is one of those points where I’m glad I’m anonymous – my CIO is probably spitting his coffee as he reads this) you don’t even have to have an EHR to make a difference. (I think I heard a few vendor gasps out there, perhaps the hissing of the word “heresy,” but it’s true.) You can make tangible gains in patient care without even a single chart pull. If you have a practice management system (that’s a “billing system” to some of you docs) with even rudimentary reporting capabilities, you can find opportunities to deliver care.

How so, you ask? Take an all-too-common diagnosis like diabetes (250.xx in ICD-9 terms.) Run some claims reports. Run a report of patients seen in the last three years with that group of diagnoses codes on a claim (or pick a single one like 250.00 if you’re scared at what you might find) and the date of their last billable visit. Presto! Anyone who hasn’t been seen in the last six months is an opportunity for care. This, of course, assumes that you actually bill the codes you’re addressing at the visit and not just cloning the last visit’s codes, which may or may not have included the diabetes. Primary care physicians are notorious for under-documenting the work they do.

Calculate the percentage of diabetics who haven’t been seen in the last six months and you just created your first metric. (If you passed epidemiology and biostatistics, which you must have to have graduated, you can calculate this. Trust me.) Send some postcards and make some calls (HIPAA-appropriate of course) and get those patients to come to your office for an actual billable visit. Report again in two to three months and see how you did. If you need a graph to show you the results, allow me to introduce you to my friend, Microsoft Excel. But I’m betting the numbers will speak for themselves.

Finally, it’s not just enough to have the data. You have to make it visible to make it actionable. Post your goals and action plans in a visible place in the office. Post monthly outcomes numbers. Celebrate those victories. When the numbers aren’t in your favor, take some time to figure out why and how you can do things differently. Involve everyone in the office. Even if you’re only focusing on a single metric each month, you WILL make a difference in the lives of your patients.

If you don’t believe that what gets measured gets managed (especially if you’re posting it publicly for everyone and their cousins to see) think again. I used to think I was pretty decent with my exercise habits (although it truly is difficult to hit the treadmill with a martini, so I wouldn’t recommend it.) In 2010, I did about 870 miles, which wasn’t totally shabby.

However, a double-dog-dare by some of my staff led to the public posting of our activities, with technical validation courtesy of our friends Garmin and Nike+ to prohibit cheating. (I suppose I could have paid the neighbor kid to jog around with my Garmin on, but that wouldn’t have been very sporting.) We have some serious running junkies on our team, and although I wasn’t delusional about keeping up with them, I felt pretty strongly about being able to beat most of the 20-somethings that populate the cube farm we call home. (Yes, they’re young. Yes, many of them are liberal arts grads. No, we’re not an Epic shop.)

Everyone had to share his or her numbers Saturday night. I almost forgot, so I was frantically uploading with a glass of Bailey’s in hand. I finished respectably with over 1,200 miles, but there’s always 2012:

Just Measure It. Just Manage It. Just Do It.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 12/26/11

Technology: The New Scapegoat?

I’ve always been a bit of a tech junkie. If I wasn’t afraid of revealing my age, I could tell some pretty good stories. To me, technology is exciting and invigorating, but also something to be respected. Technology at any level can run amok – think about Lucy in the chocolate factory as a basic example of what can go wrong. And who wants the artificial intelligence to run amok like HAL 9000? 

In conversations with providers, hospital administrators, and end users, the problem is always “the EHR” or “the system” or “the computer.”

Having lived in an electronic practice for nearly a decade and having used computers in the hospital for almost a decade before that, I can say with a good level of confidence that it’s not always the technology that’s at issue. Systems are only as good as the users who operate them, in conjunction with the training they receive and the proficiency they demonstrate. A recent situation at UC Irvine Medical Center illustrates this.

Although the headline screams “drug pump issue,” a close reading of the Statement of Deficiencies document (it begins on Page Five) yields some interesting factoids:

• The hospital deployed new infusion pumps without hospital-wide training.
• No policy and procedure document was developed (let alone approved) for the safe use of the new pumps.
• A physician overrode a “soft stop” alert on the pump, leading to a patient receiving a high dose of medication. (I agree that the fact that there wasn’t a “hard stop” alert programmed in, but let’s remember a physician did override the alert.)
• The hospital was “unable to ensure that MD… was competent in accurately programming the medication infusion pump.” The pump didn’t have a drug library and was programmed with a dose over 30 times that of the prescribed dose.

After two patient-related incidents, the hospital took corrective action, including:

• Only allowing trained RNs who have documented competency to program the pumps.
• Ensuring that dose, concentration, and flow rates are chosen from a current drug library appropriate to the care area.
• Restricting the ability for users to enter dose/rate for non-library medications unless a second user verifies the programming.
• Requiring re-verification of orders and programming when soft limits are overridden.
• Instituting hard stops which cannot be overridden for certain medication doses.
• Instituting independent double check for programming of pumps that deliver certain high-risk medications

These seem like no-brainer fixes to me. I’m glad the hospital put policies in place that should have been there all along (regardless of the newness of the brand of pump, model, etc., these are just good patient safety procedures).

The document goes on to list several other fairly horrifying behaviors, including a director of pharmacy who admitted knowing that no policies were in place and that no one was overseeing pump safety. “We will in the future, but the pharmacy department needs to be trained first.” He/she also stated that the vendor provided inadequate training for monitoring of pump-related events. Blaming the vendor is always easy – it takes a steadfast leader to halt a go-live when adequate training has not yet taken place.

Other scenarios mentioned in the document:

• A resident physician involved in a pump-related incident that involved infusing a medication over one hour instead of the recommended six hours was “unaware or unwilling to accept the hospital pharmacy directive to infuse the medication over six hours.” The resident’s anesthesia record stated that he was aware that he dosed the medication to infuse over one hour. The resident also violated Department of Anesthesia rules by not paging his attending physician to be present for the end of anesthesia as was required. Oh yeah – he also “overlooked” the patient’s low oxygen level and didn’t take corrective action. When the attending arrived after the resident finally paged, the attending called a Code Blue because the patient “had poor color and was not breathing.”
• Residents examining patients but not writing progress notes (even after a nursing supervisor notified the attending physician) on several occasions.
• An oncology staff nurse (whose job duties included validating chemotherapy doses) who was unable to calculate the dose when given a patient’s weight in pounds and a dose in milligrams per kilogram.
• Contract nurses allowed to operate infusion pumps without training (one with an ungraded proficiency exam in the personnel file — if you made him take it, why not grade it?)

I had to quit reading after a while because I’m extremely compulsive about patient safety and it was just making me increasingly agitated.

Despite the potential harm involved in the pump-related incidents, I’m actually glad they happened. Why? Because the incidents acted as a trigger to expose some significant issues and deficits in patient safety. Patient safety is a culture that requires education and support. It doesn’t happen in a vacuum.

I wouldn’t let an adolescent operate a lawn mower independently without appropriate training, safety gear, and close supervision. We don’t allow teenagers to drive cars (aka operate deadly weapons) without proving a minimum level of proficiency. Yet in this situation, users were allowed to operate equally dangerous machinery without training. The documentation doesn’t mention whether the nurses were forced to operate the pumps over their objections, but the point is they shouldn’t have been asked to use potentially lethal equipment they weren’t qualified (by training and demonstrated competency) to use.

I hope this case serves as a wake-up call for some institutions. I hope end users continue to speak up when they’re asked to do things that are unsafe and that someone listens. Lives depend on it.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 12/19/11

I really struggled with what to write about for this week’s Curbside Consult. I thought about being witty or trying to come up with some clever HIStalk version of “Twas the Night Before Christmas,” but the things I saw today top anything I could ever come up with. So listen, dear readers, to the cautionary tale of why each and every one of you who work in health IT can never forget the importance of your role, whether large or small.

As you may have picked up from my columns, when I’m not in the CMIO trenches, I work in various clinical environments. I don’t have to (it’s not part of my contract,) but I discovered during a year-long sabbatical from patient care that I really did miss taking care of people. I missed the simple joys of being able to make a new parent confident that their baby will eventually sleep through the night or helping patients come up with a plan to manage chronic health conditions. I missed the patients who came to me with lacerations because they knew I could patch them up faster than the local emergency room.

I did not, however, miss dealing with insurance companies, RVU compensation models, and administrators who didn’t know beans about running a medical practice.

When I was ready to see patients again, I had to find opportunities that wouldn’t interfere with my CMIO duties and that were flexible enough for me to still have plenty of time to cultivate my hobbies (can one really consider martini drinking a hobby?) I chose to be a non-employed physician. Sometimes I work for a staffing company, covering urgent and emergent care facilities. Sometimes I work as a locum tenens to cover docs who are on medical or family leave. Today was a little of both and to compound the “perfect storm” that was brewing, it was a place I hadn’t worked before.

You know you’re in trouble when you pull up to the designated employee parking garage and it’s essentially a chain link cage with a badge-swipe entry portal that looks like a sally port. As a last-minute fill-in for a physician out on leave, I didn’t have a badge, so I had to phone a security guard, who had to find my name on a list. Of course they didn’t have me on said list, but I must have looked fairly non-scary, so they buzzed me in.

I parked (next to a Corvette and a Jaguar, safe in their cage – go figure) and headed in. The staff was friendly and I had enough time to get fully caffeinated before the patients started rolling in, both of which are usually good signs.

The Emergency Department Information System (EDIS) was one I had worked with before, so I was pretty confident that I was going to be able to roll along without incident. Boy, was I wrong. Today was a veritable textbook of “lessons learned” on what can go totally wrong with software, hardware, and workflow. As I mentioned, this is why it’s so important for everyone who works in health IT to take their jobs seriously. Information Services leadership take note and hold on tight, because here we go:

1. I was given a stock password and told to change my password the first time I logged in. Unfortunately, my security classification doesn’t permit password changes, requiring me to call the help desk, which told me I could tell them what I wanted and they’d load it on their end. Really?
2. Better yet, the PACS system has a generic login and password left on a sticky note taped to the monitor. When I asked about this, I was told they had gone to a generic login because the doctors couldn’t remember their passwords. I can’t imagine what their HIPAA audit policy looks like for figuring out who viewed what data with generic logins.
3. To make things more exciting, the IT team scheduled a planned upgrade of the financial and registration system during the day shift. There were no printed downtime procedures available for staff and no clear communication plans. We were alerted to upgrade status by random people who would walk through the ED shouting “it’s back up” or “it’s down again.” Eventually we figured out that the patients whose names appeared in mixed case were registered using the integrated system, and patients whose names were all lower case were manually registered in the EDIS. That might have been nice to know since those manually registered patients had no outbound orders stemming from their accounts. We figured this out after radiology never showed up to do films on our patients – apparently we were supposed to call radiology to schedule those manually registered patients.
4. I’m usually obsessive about hand hygiene before and after touching patients. Today I actually felt an uncontrollable urge to wear gloves to touch the keyboard. You may have noticed I said “keyboard,” as in singular. There was one computer for me to use in a 10-bed emergency unit and it was a fixed desktop. That means no documenting in a patient-facing manner, thereby leading to rework, possible memory errors, and potential transcription errors. The nurse also had a single fixed workstation. Interestingly, the registrar had a really nice new computer on wheels (wireless) to go with their spanking new financial and registration system. So much for enabling patient care.
5. The software had not been updated to a Meaningful Use-compliant version. Not that being MU certified has anything to do with usability or efficiency, but it has become at least a minimum standard for software to meet. Basic demographic information is required to meet MU and this system had some major holes. I know the vendor has a MU compliant version (I’ve used it before,) but this was not it. The users were unaware of any planned upgrades.
6. I’m fairly certain the EDIS was not JCAHO compliant or remotely adherent to the precepts of the Institute for Safe Medication Practices, either. For prescribing, it was almost entirely hard-coded with physician “favorites.” Unfortunately, many of these favorites included “do not use” abbreviations as well as medications that have been off the market for several years. Users told me the prescribing system was hand-built and doesn’t import data from any of the respected formulary vendors. It was pretty clear no one was updating it, either. There was no appropriate way to prescribe current weight-based pediatric prescriptions. In order to get a non-ambiguous medication order for the pharmacy, I had to find the closest “canned” medication I could then print it on safety paper, finally crossing out the confusing parts and handwriting a traditional script below to clarify the confusing computer-ese. To the pharmacists on the receiving end – mea culpa, I didn’t know what else to do.
7. There was no ability to save any kinds of defaults or templates when documenting patients. I had the choice of either a “brief” history/ROS/exam, which was basically a canned jumble of findings (which I’m sure some committee somewhere worked really hard to agree on, rendering it individually useless) or the ability to check each individual finding box individually. After a full complement of ED patients, I’m seeing individual checkboxes when I close my eyes.
8. Customizations had been placed into the system without logic, resulting in duplicates and user brain fatigue. Most of the follow up clinics were listed as “Clinic – Specialty” but every now and then I’d see a rogue like “Derm Clinic” (even though Clinic – Dermatology was in there) but there was no consistency.
9. Clicking for Spanish patient education materials occasionally printed documents in a language which was distinctly not Spanish. Thank you, Señor B for gently educating the gringa that the discharge instructions were muy mal, because you’re right, I didn’t look at them before I handed them to you or I would have known. Shame on me and my apologies to those who taught me during eight years of Spanish classes.
10. Printers were non-configurable. I could print the discharge summary for the patient, but when I wanted to print additional information (such as sources of free medication for uninsured patients), my only choice was “print to file.”

I could keep going but I won’t. Hopefully you get the point.

As an outsider, the confluence of all the various decision streams at work here created a veritable maelstrom in which we tried to deliver care. It would be tempting to refuse to go back if I’m ever asked to staff that facility again. What’s interesting, though, is that I probably won’t refuse if I’m called. Why? Because the patients were genuinely needy, the care provided was solid despite the challenges, and the staff worked their tails off as a team to get through the shift. Everyone did his or her part and then some.

By the end of the day, it was like we had worked together forever. Hugs were exchanged (as well as recipes for Christmas cookies and empanadas – thanks for introducing me to things I never thought possible with chocolate and coconut) and high-fives given. I learned a nice trick for removing the proverbial rusty nail from the bottom of a foot, courtesy of a provider who shoes his own horses in his spare time. I did a little bit of education on Meaningful Use and information security.

Last, but most important, I helped some people. And that, my friends, is what it’s all about.

Feliz Navidad, próspero año y felicidad.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 12/12/11

This is always a busy time of year, so I’m a little late reporting on something that could have a profound impact on health care. Last month, the United States Supreme Court agreed to hear challenges to the 2010 Patient Protection and Affordable Care Act (PPACA).

The briefing schedule was just released last week. It looks like briefs are due throughout January, February, and March. We can anticipate oral arguments before the Court shortly thereafter.

Although there is no way to predict when the Court will hand down any given decision, all cases argued during a particular term are decided prior to the summer recess, so we should have a decision by the end of June. The timing of this is interesting because it means there will be a decision right around the time the 2012 presidential campaign heads into its final months.

In announcing its review of the case, the Court is consolidating two pending lawsuits. Both seek to overturn the Act, with the primary question being whether the law is constitutional – in particular, the mandate for individuals to obtain health coverage.

Specifically, an appeal from the United States Court of Appeals for the Eleventh Circuit in Atlanta is aimed at reversing the decision that a three-judge panel made to strike down the mandate. The panel felt that Congress did not have the authority to do this despite their constitutional power to regulate commerce and levy taxes. This particular appeal dealt only with the mandate, however, and left the rest of the Act intact.

The other appeal attempts to overturn a decision in the Eleventh Circuit that ruled against Florida and other states on a challenge to the law’s expansion of Medicaid. The states also argued that Congress exceeded its reach by expanding Medicaid eligibility and coverage thresholds that states must adopt. Under the Act, states must meet new conditions or lose all federal Medicaid funds.

There are several different actions the Court could choose: upholding the law, striking down only that provision, striking down other elements, or striking down the entire law. In a bit of a twist, they are also considering another issue coming out of the Fourth Circuit (Virginia) which could delay a final ruling until 2015 when penalties take effect and the ability of individuals to challenge the individual mandate becomes timely.

There are a total of 26 states challenging the law. Given the polarization the law has caused, this is sure to be one of the more electrifying cases heard this year. In anticipation of the significance of the issue, the Court scheduled more than five hours of oral arguments instead of the usual one-hour argument. They will hear two hours of argument on the issue of overstepping constitutional authority, an hour and a half on whether the mandate can be separated from the rest of the act, an hour on the Medicaid issue, and an hour on the issue of whether it is premature to decide the case.

Regardless of the outcome, it will be interesting to see how the presidential candidates react, not to mention how those battling on both sides of the aisle of Congress will react. For those of you who have a hankering for primary source material, briefs and orders are posted on the Docket page of the Supreme Court website.

Have a question on the branches of government, touring Washington DC, or where Associate Justice Ruth Bader Ginsburg gets her kicky jabots? E-mail me.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 12/5/11

For those of you who are my Facebook friends, you may have noticed that I’m at the National Finals Rodeo this week. (And if you’re not my friend on Facebook… well, you know what you need to do to keep up with all my travels and adventures.) Despite my love of all things technology, I really am a cowgirl at heart.

For those of you who are not rodeo fans, NFR is in Las Vegas. I’m amazed at how the city transforms itself for different constituencies. The casinos of the headquarters hotels are filled with the sounds of country music. Shopping areas are featuring cowboy boots in the window instead of rhinestone stilettos (although there are plenty of rhinestones on the boots.) The cocktail waitresses at one bar I’ve been to several times in the past have given up their leather bustiers and miniskirts in favor of tight jeans and white cotton shirts. If there’s any place on earth that’s a triumph of marketing, it’s Las Vegas.

So what does this have to do with healthcare and technology? A couple of things.

First, let’s talk about marketing. We always think about vendors when we think of marketing. Nearly every vendor’s ad campaigns these days prominently feature the twin terrors of Meaningful Use and Accountable Care. If those aren’t mentioned, then it’s revenue cycle or other financial aspects of health care.

I think we forget about the sheer amount of hospital marketing that goes on, however. Just like the casinos marketing to the cowboys (many of whom have wallets the size of their belt buckles – and trust me, Jayne and her crew have been checking out some jeans pockets on this trip) the hospitals, surgery centers, and physicians are heavily marketing towards whatever demographic they feel has the fattest wallets or deepest pockets.

Driving around most cities, you see plenty of healthcare-related billboards. One hospital I passed recently boasts a Heart Hospital. What does that mean? Do they do more heart cases than anyone else? Are their outcomes better than others? Or do they just want the perception of being specialized to try to garner business when their volumes are the same as the hospital across town?

Everyone is tweeting their emergency department wait times. I’d like to see them tweeting their nurse-to-patient ratios or their infection rates instead. That would really create some interesting discussion in the community about which facility is the best.

Physicians and other providers aren’t much different. Going after high-paying patients is an art form. Medical buildings (and some physician offices, too) are installing complimentary coffee kiosks to go with their waiting room check-in kiosks. Ancillary services including cosmetic and convenience offerings are proliferating faster than Medicare Wellness exams. Availability of after-hours physician access at premium prices is becoming more commonplace. Concierge-type practice models such as MD VIP are going mainstream. My travel companion noticed a special advertising section in the Southwest Airlines Spirit magazine this month that featured not only concierge medicine, but other specialty and alternative practices.

Hospitals and physicians have their own internal marketing campaigns as well. It may be as simple as signs in a primary care office reminding diabetic patients to take off their shoes prior to seeing the physician or as complex as a multi-hospital multimedia hand washing campaign (complete with Big Brother surveillance, as we’ve seen recently) or promoting desired behaviors such as vaccine compliance through viral videos.

The medical establishment is increasingly marketing technology to patients. Not only emergency wait times, but also patient portals, secure messaging with providers, lab results online, bill pay, and a host of other services. Many of these offerings not only add value to patients and families, but also have the potential to significantly increase the bottom line for healthcare organizations. Payers are in the game as well as employers, with many offering health promotion and disease prevention as well as online enrollment, updating, and claims management features.

Many agree there are health benefits to increased patient education and empowerment. But the jury is still out on some of these marketing efforts. I’m interested to hear what HIStalk readers think about marketing – on the vendor, client, and patient sides. Have an opinion? I promise to read your comments just as soon as I’m finished watching the action. Tonight is “Tough Enough to Wear Pink Night.” I’ll let you guess what color my boots are.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 11/28/11

Now that Thanksgiving has come and gone, we’re officially in that nebulous zone called “The Holidays.” For many, this includes hectic family gatherings, school programs, and travel to see relatives. College students return home to agitate parents and siblings.

For physician offices, it marks the beginning of cold and flu season. For IT teams, it often it signals a lull in the implementation of projects because no one wants to deploy new technology when physicians and staff are alternating time out of the office with packed schedules (usually required to accommodate said time out of the office.)

I officially boycotted Black Friday by purchasing nearly nothing, despite needing to pick up a new external hard drive. I was happy to see my municipality issuing tickets to big box retailers that opened at midnight, citing laws preventing 24-hour operation of retail enterprises. I’m not the neighborhood Grinch by any means, but I am glad to see someone countering the steady pressure of rampant consumerism. I did buy some coffee (a delightful peppermint mocha) while visiting with a friend, but I’m sure that didn’t make a blip on the Black Friday cash register.

One good thing about The Holidays is that travel often brings people to town that I don’t get to see too often. I had the rare chance to sit down with my longest-standing friend. We started our healthcare careers together at the tender age of 13 as hospital volunteers, aka Candy Stripers. Cecilia always wanted to be a nurse and I always wanted to be a doctor, so it was a friendship forged of common interests with a sprinkling of adventure.

We started volunteering on the mother/baby ward (yes, they were called wards back in the Cretaceous period,) refilling plastic pitchers with ice chips and answering the nurse call light system. My favorite part was using the Addressograph machine to stamp paperwork when new patients arrived, assembling charts in large plastic three-ring binders. I guess that means my interest in health information goes back to the very beginning (or maybe I just liked the smell of mimeograph ink).

After a while, I tired of being the ice chip police and transferred to being the “checkout girl” at the gift shop. The computerized cash register made the job fun. I enjoyed the tally reports that it created for the end-of-day close. Maybe that’s where my interest in technology comes from.

Being Candy Stripers gave us unlimited access to the hospital (in the pre-HIPAA era, things were very different.) I still can’t believe they let teenage girls do the “pharmacy run,” driving a cartful of drugs to every ward including the locked psychiatric ward (at my hospital, robots now do that work). We saw the hospital from the ground up – from central stores to sterilization to food prep to pharmacy to nursing and beyond. It gave you a solid understanding of all the different people needed to make patient care possible. It allowed you to be close to the action, but not too close (thankfully, we weren’t on duty the night that a baby was delivered in the lobby bathroom.)

Cecilia and I thought it would be cool to work together when we grew up. I could have a private practice and she could be the office nurse. Although I did ultimately end up with that practice (at least for a while,) she specialized in cardiac nursing and prowled the telemetry and post-surgical step-down units. The hospital where we started faced a declining census and was torn down to make room for outpatient offices. I still have a brick from the demolition. Ironically, a decade later they’re thinking about building a bed tower there due to rising hospitalizations among the increasingly aged population of our home town.

Being a nurse on the front lines, Cecilia really has seen the transformation of healthcare delivery first hand. She has nearly a decade more experience than I do, working in the trenches while I was still slogging through medical school and residency. She has worked through every buzzword you can think of. We always commiserate about having to deal with patient-focused care that’s actually profit-focused, centers of excellence that really aren’t that excellent (but the administrators think that if you call it that, it makes it automatically great,) and goofy regulations and policies.

Spending time in major hospitals throughout the country, we’ve both found that the more hospitals think they’re unique, they more they really are the same. Clinical care has been commoditized. 

It’s a bit humorous, but we both wound up in the same situation for clinical work. Although she works for a major health system just a few miles from her home, they don’t employ her – she’s staffed by an agency hundreds of miles away because the hospital doesn’t want to spend the money to employ full-time nurses. I’m in the same boat because my hospital doesn’t actually employ any of the hospital-based physicians either, relying on a staffing company to insure us and administer our schedules. It’s a long way from what we thought we were getting into way back when.

I can’t complain, though. Being a mercenary doc from the clinical perspective allows me to indulge my IT passions and still see patients. It does make one wonder, though,what’s next in healthcare. When the majority of workers at a hospital aren’t actually employed by the hospital, what’s that going to mean? How do you ensure training and consistency? How do you handle an ever-changing and increasingly complex environment? How does it impact patients? We’ll just have to wait and see.

So here’s to The Holidays. I hope you have the chance to connect with friends and colleagues old and new. Stay safe, stay sane, and take some time to recharge. If what we’ve seen this year is true, it’s only going to get busier in 2012.

Have a question about eggnog recipes, call light systems, or making the perfect ice pack out of a rubber glove and paper towels? E-mail me.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 11/21/11

As the newest member of the HIStalk team, I’m continually amazed at how Mr. H and Inga keep up with the constant barrage of press releases, announcements, news, information, and gossip that circulates around everything related to health information technology. I try not to feel bad when I realize an interesting tidbit has slipped past. Hopefully at HIMSS I can meet with Inga for a mind-meld to learn how she does it (and also to absorb some of her sartorial style.)

The issue at hand is relatively small potatoes in the overall federal funding bonanza – a $1.24 million contract awarded by ONC to APP Design, Inc. The goal of this contract is to help patients better understand choices regarding sharing of health data.

Specifying, building, and deploying a health information exchange have been a major part of my career for nearly half a decade. As a physician, the concept of HIE solves a myriad of problems. Consult letters don’t get lost in the mail; labs don’t wind up being double-ordered because the results aren’t in the chart; and medical misadventures can be prevented through timely sharing of pertinent clinical data.

As those of you who have been down this road know, it’s often unpaved and riddled with pot holes, poor lane markings, and uneven shoulders. For many of us, the road trip has been halted by the barrel monster called “Consent.” This is ironic because our patients think that simply by virtue of the fact that we’re documenting using computers, that all their providers are already fully sharing patient information. I’ve had patients yell at me in the exam room because I don’t have a particular piece of data on my screen.

As long as data sharing is within a physician group (especially if they are all under the same tax ID and within a single state) it seems relatively uncomplicated. But add non-employed physicians, independent providers, multiple health systems, and (heaven forbid) multiple states and you have a real mess on your hands.

When we sought to add providers outside our large employed physician group, the recommended consent language created by outside counsel was over five pages long and was totally unintelligible to the average person. Remember all those carefully crafted patient education handouts that have to be at the fifth-grade reading level so that patients can hopefully understand them? Think again. I have multiple graduate degrees and couldn’t follow this one.

Days of revising turned to weeks and then months as we struggled to get the consent document to even a single page. What felt like years of my life were sucked away on endless conference calls with our in-house attorneys and outside counsel. I jokingly proposed the following:

Check one below:

a) I want my physicians to share all information available so they can treat me the best way possible

b) I don’t want my physicians to share information and am aware this could possibly hurt or maybe even kill me

c) I don’t want to share my information because I am a drug seeker and am afraid you will no longer treat me if you find out

Not surprisingly, the attorneys didn’t find it funny. Most of my physician colleagues however found it hilarious.

Regardless, I’m looking forward to the outcomes of this exercise. The E-Consent trial being funded by ONC has several goals, including finding new ways to educate patients about data sharing as well as finding ways to move from paper consent to electronic consent.

The trial will take place at four sites in western New York that use the HEALTHeLINK exchange system. APP Design plans to create a new user interface to inform patients about data sharing and their choices, and also to document the patient’s permission. Looking at the timeline for deliverables, by now the project kickoff meeting should have occurred as well as creation of the project approach and work plan. APP Design will have 48 weeks to deploy a pilot, then an additional 32 weeks to evaluate patient understanding and satisfaction. Biweekly status meetings with ONC and monthly progress and financial reports will occur throughout the project.

Let’s hope they do well and avoid the potholes. May the construction barrels steer them to smooth pavement, slow gradual turns, and well-lighted parking.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 11/14/11

Dear Dr. Jayne,

Is our current EHR paradigm dated? Docs practiced for years with paper. Pencil evolved to ink, both inscribed on compressed wood. Housed in manila folders, stickers provided the index and retrieval involved sight-based interpretation based on patient names. Then, we introduced computers. Initially similar to the paper paradigm, full summaries in ANSII or images are stored in a paradigm that still resembles folder-based paper storage.  From the images and full ANSII summaries came discrete data points. Ink on paper had now evolved to data capture as unique field based database storage. Over time, these discrete data points will become much more comprehensive.   

With all the technical advances where is the industry going? Will the paradigm shift from practicing medicine on discrete data points to something else, and when? Will medicine be able to shift? Is multimedia the next frontier? Just like the initial paper to electronic chart paradigm shift, when will computer science convert images and video to discrete data points? We all know the value of discrete data.

Fan of Dr. Jayne from the Deep South

Dear Southern Fan,

You pose some interesting questions. Given the fact that physician recordkeeping didn’t change much for hundreds of years, the relative pace of records evolution at present is staggering. We’re already becoming fairly adept at converting spoken language into discrete data, allowing physicians to document patients’ stories not only with codified data points, but with the rich narrative that frames individual patient circumstances and situations.

In my opinion, the biggest barrier to the kind of documentation that can be envisioned is unfortunately the proverbial hand that feeds us. The regulations, policies, and requirements of CMS are still stuck in the paper paradigm. And as we all know, as CMS goes, so go the rest of the payers. Despite federal mandates to take the technology forward — such as HIPAA and HITECH — healthcare providers are still being scored based on documentation standards that have not evolved in more than a decade.

Physicians can’t get “bullet point” credit for documenting a cancerous skin lesion with a photograph. They say a picture is worth a thousand words, but in an audit, a picture is worth nothing.

I remember sitting in medical school watching a video of a child with whooping cough. No written description could ever take the place of that. When you see and hear that kind of pathology, it’s etched in your brain forever. Nevertheless, embedding a video clip of a patient isn’t worth anything, either. I can look at a photograph of a diabetic foot and tell you a lot more about a patient’s illness and status than I can glean from a multi-page nonsense note generated from a poorly-implemented EHR.

I once heard someone say that our thinking is constrained by the technology of today. I don’t think that’s the entire problem; our vision is also constrained. And it’s not the technology that locks us in, but also the auditing and payment paradigm that hobbles us.

I was initially hopeful that the rise of Accountable Care Organizations with their risk-sharing and outcomes orientation would help us move to a more modern way of thinking and documenting. It doesn’t look like the fact that providers and payers are sharing risk is going to move us away from the incessant and costly paradigm of documentation for documentation’s sake.

The promise of telemedicine and other technology ventures such as real-time electronic patient communication was exciting. However, lack of payment and increased regulatory burden continue to keep it from realizing its potential. I’d like to think the future’s so bright we’ll have to wear shades, but I’m not sure CMS agrees.

Dr. Jayne

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 11/7/11

You all know how much I love things from South Carolina, so it’s with an extra smile that I congratulate Pink Glove Dance winner Lexington Medical Center of West Columbia, SC. Their entry really does have it all – from the early morning cleaning crew to pink glow sticks at the end of the day. I’m particularly impressed because they captured parts of the hospital that some of us forget about – like the engineering department (the guys with the umbrellas) and the child care center – with plenty of other clever bits in between. In honor of the win, $10,000 will be donated to the Vera Bradley Foundation for Breast Cancer. BTW, don’t miss the biohazard ninjas at 2:23.

From my comments on shoes and finding the best martini, some of you might think Dr. Jayne’s idea of the great outdoors involves poolside cocktails at the Ritz Carlton. Big surprise though — I spent the weekend camping. Good, old-fashioned sleeping bag on the ground in tent-style camping. No electricity, no running water. The weather was chilly, but fantastic. It was great to be away from technology for at least a little bit (except for the guy in our group who was texting in his tent – I believe that’s a camping faux pas, but I wasn’t going to wriggle out of my mummy bag to tell him to quit.)

Camping can be a great equalizer. It’s hard to know whether you’re a Suit, a Doc, or IT staffer when you’re all wearing jeans and either a ponytail or a ball cap. (I didn’t go camping with work people, but I did go camping with an IT staffer, a postal carrier, and a project manager as well as other assorted folks, so it was an interesting mix.)

Watching people set up camp definitely reminded me recent IT adventures in the “you get what you pay for” category. The inexpensive vendor with the iffy support that you contracted with because you only needed them as a bridge technology? Very similar to the budget tent with the iffy instructions that took entirely too long to assemble and will never, ever go back into its stuff sack. (And a shout out to my tent provider – yes, you are correct, your tent IS the bomb, I’m sorry I ever made fun of how much you paid for it, and BTW you’re never getting it back.)

Being away from the constant electronic and political spin cycle was good and allowed for some time to think about where our tech-enabled lifestyle has gotten us and how far apart we are from the vast majority of people in the world. One of the women in my group mentioned that she had never eaten a breakfast that had been cooked over an actual fire. Considering that’s how many people in the world today still live on a daily basis, it seemed kind of sad that we’re so out of touch from what many consider true basic needs. Our near-worship of technology and making things easier and more efficient has also made us more prone to heart disease, diabetes, obesity, depression, anxiety, and stress-related illnesses, which add to the high cost of health care.

We’re spending billions on expanding, enhancing, upgrading, and turbo-charging health information technology when there are people in the world (and even in our own country) who have no access to health care. We forget that there are people who have to walk miles to access clean drinking water. Things like that kind of put some of our daily IT trials and tribulations in perspective when you’re considering that level of resource disparity in our world.

While contemplating all of this under a cloudless starry sky (after having confiscated my tent-mate’s iPhone and its fascinating but atmosphere-spoiling astronomy app) I started thinking about what it really is that I do for a living. When I left solo practice to begin my journey at the Big Hospital and in academia, I was motivated by how many patients I’d be able to impact by moving to the next level. Moving next to the Large Health System and now to my current position, the potential for impacting patients’ health should be even greater. It’s a long way from three thousand patients in a private practice to several million patients across a multi-state organization, but some days it doesn’t feel very impactful.

I know from the numbers (which I crunch daily thanks to software, reports, registries, and endless dashboards) that we are moving the needle. On a month-to-month basis however it is agonizingly slow. We’re building a better mousetrap, but is a mousetrap what we really need? Where is the true innovation? Do we instead need an ultrasonic way to repel the mice from the area, obviating the need for a mousetrap? Or maybe we’ve over engineered, missing entirely the fact that if we’re living on a farm, we’re going to have mice, and we need to be focusing on something else entirely?

The people who deal with the mice on a daily basis feel like they’re no longer stakeholders in the process. Putting it in healthcare terms, insurers, large health systems, and federal entitlement programs are driving legislation that pushes us away from individually focused care and into a widget-making mentality. Patients aren’t the same and neither are providers. Among large health systems, there are great differences (and for some, differences even within their own organizations.)

We’re exactly a year from the next presidential election and I think it will be interesting to see where we are when the big day rolls around. By November 2012, we’ll know who’s been naughty and who’s been nice in the game of Meaningful Use attestation. We’ll watch some vendors bomb and some victors emerge. The big question: will we actually be making more of a difference in the lives of the patients we serve? Or will we ourselves be mice reaching for cheese and hoping to avoid the snap of the trap? Only time will tell.

Have a question about healthcare expenditures, CPOE, or which knot to use to hang your bear bag? E-mail me.

E-mail Dr. Jayne.

Curbside Consult with Dr. Jayne 10/31/11

Today is Halloween, which is without a doubt my favorite day of the year. It’s one of those days where even adults can act like kids and playing dress-up is OK. People love to mark the occasion by visiting haunted houses, watching scary movies, and telling ghost stories.

So everyone grab a popcorn ball and some of those little peanut-buttery candies in the orange and black wrappers and turn the lights down low, because it’s time for Dr. Jayne’s Top Ten List of Horrifying and Frightening Things.

10. HIPAA compliance zombies. You know the type — those that cite HIPAA as the reason for everything, regardless of relevancy. I had a run-in with one of these who told me (as the referring physician) that she couldn’t fax me a copy of a consultation note (which was addressed to me, but had only arrived with one of three pages present) unless I sent a release signed by the patient. Reason: HIPAA. (I bet in her head it was spelled HIPPA.)

9. Physicians who demand that allergy checking and other EHR decision support be completely disabled because they “know all that stuff already.” I understand (and loathe) alert fatigue as much as the next gal, but seriously, I can’t imagine that there’s a physician who has never accidentally prescribed a medication to someone who was allergic to said medication. I know I’ve done it and you know you’ve done it at least once in your career, too. If that doesn’t scare you into leaving the allergy checking active, it should.

8. Shortages of common medications, including vaccines and chemotherapy drugs. Often these are low-profit margin generics and are made by only a handful of manufacturers. If one of them experiences production issues, the entire supply is threatened. Something to think about the next time you read about all drug makers being branded as greedy.

7. Celebrities and politicians dabbling in the public health sphere by adding to vaccine hysteria. Want to see something really scary? Pictures of vaccine-preventable diseases. I wish they’d spend their time advocating anti-drug and anti-obesity propaganda instead.

6. Patient-facing software vendors who do not have licensed physicians on staff (or at least as consultants.) I’m not sure how they evaluate usability, let alone suitability for patient care. The only thing scarier is the hospitals and health systems that actually purchase this software.

5. Hospitals and ambulatory organizations that implement patient-facing software without physician leadership or oversight. I recently moonlighted at a JCAHO-accredited facility that had an allegedly certified system. However, for some reason, the prescriptions printed without a medication route. The system also had “never use” abbreviations on the prescribing screen. I’m not sure why they were printing on paper in the first place, but with obvious patient safety and regulatory issues to address, I didn’t pick the eRx battle that day.

4. Congressional rule-making that increases health care costs in the name of balancing the budget. I’m talking about the ridiculous change that made patients obtain prescriptions in order to use flexible spending accounts to reimburse over-the-counter drugs. Let’s see, the reason they’re over-the-counter is because they don’t require a prescription. But now, to save money, I have to get a prescription for my OTC med (after paying a co-pay), take it to the pharmacy, waste their time submitting it to my insurance to get the denial because it’s OTC, then pay cash for it and submit it to my FSA overseer. If they thought this process was going to deter patients, they were wrong (I’m not sure they thought it that far through the process, though) because patients are coming in droves for these scripts and some offices are charging fees for preparing these extra prescriptions. There’s a whole lot of spending going on here and it’s your fault, Congress. Next time you’re going to do this kind of thing, can you please ask a primary care doc his or her opinion first? I’d rather be counseling the obese, hyperlipidemic, hypertensive diabetic about his cardiac risk than writing another prescription for little Johnny’s diaper cream.

3. The fact that the item above is only a teeny, tiny, microscopic piece of what Congress has done or is trying to do with healthcare. I’ve got an idea: Let’s form a Congressional HMO, enroll all the legislators and their families in it, and use it as a pilot site for health care reform proposals. Once they prove efficacy on a captive population, only then should it be allowed to see the light of day. Muahahaha!

2. The emergency department at almost any urban hospital and quite a few suburban and rural ones, too. Overcrowding is often the norm, and due to fright-inducing Acts of Congress such as EMTALA, everyone is treated regardless of the ridiculousness of their chief complaint or its appropriateness for the emergency department. I know some hospitals were (and still are) guilty of patient dumping, and that is indeed a crime, but having to perform a medical screening examination on a patient who presents with “wants to know if I’m dyslexic” at 11 a.m. on a Saturday is a waste of resources. And yes, I really did see this patient, but only after the nurse had to spend his time assessing the patient’s pain score and asking him if he had an advance directive. This was in an ED that sees about the same patient volume as that of Massachusetts General Hospital, so it’s not like we were just sitting around shoe shopping on the Internet.

1. Watching providers adapt to ICD-10. I’m hearing lots about ICD-10 readiness and how software and billing systems will handle it, but am hearing very little about how organizations are actually going to train their providers to identify the appropriate new codes for old diseases. Word in the Doctor’s Lounge is that providers think EHR vendors will just automagically map the codes for them. They apparently missed the fact that it’s not a 1:1 conversion. If your vendor is telling you they’ll do this, you should be as frightened as if you just ran into Jason Voorhees and Freddy Krueger chatting at the coffee machine.

I hope after all this you’re not too scared to open the door to trick-or-treaters tonight or to do some candy hunting of your own. Maybe you’ll stop by Casa Jayne and not even know it. I’m one of the “good candy” houses and my office at work is also well provisioned. I stocked up on Sweet Tarts and Sprees should a certain sassy sales exec decide to stop by. I’ll be in costume (of course!) but I’ll give you a clue — you’ll be able to figure me out by my shoes. I’ll bet Inga doesn’t have a pair of these!

E-mail Dr. Jayne.