Monday, January 24, 2011

"All the World's a Stage"...Two

”All the world's a stage,
And all the men and women merely players:
They have their exits and their entrances;
And one man in his time plays many parts,
His acts being seven ages…”
[As You Like It, William Shakespeare]

Oh no, as if music analogies weren’t enough, now I’m quoting Shakespeare? Actually, I’ll confess that I’ve never read As You Like It but I thought of these lines in the context of Healthcare IT and Meaningful Use (MU) Stages. The monologue quoted above goes on to list seven “ages” (which we would call “stages”) of life: infancy, childhood, the lover, the soldier, the justice, old age, dementia/death. I think HIT has gotten beyond infancy, probably into “childhood” and wants to grow more mature with each Stage (stopping well before dementia and death, of course).

The eyes of the HIT world are watching the “players” from the HIT Policy Committee, who are proposing Stage 2 MU which will start in FY2013. When it’s defined, will it be “as we like it” and will we believe it is taking us on the right path? What’s the vision and strategy to which Stage Two is a stepping stone?

Most of us indeed play many parts (roles). For instance, with respect to HIT, I ‘m a public citizen commenting on regulations, standards developer, interoperability champion, product developer, PHR user, patient, and caregiver. The dedicated people on the HIT PC also play many parts  simultaneously, which may include clinician, developer, researcher, business executive, standards developer, and of course policy maker and patient.

Before submitting detailed comments, I want to share some themes and associated issues that I gleaned from my initial reading of the 19-page HIT Policy Committee Meaningful Use workgroup’s Stage 2 recommendations.
  • There’s more recognition of the need for evidence to support objectives. A little over three pages of references are given, though I wish that there were more explicit connections between each objective and the citations. Consider that regulations that affect thousands of providers, hundreds of vendors, and millions of patients have high stakes. So it’s reasonable to expect evidence not only of benefits but of associated costs including impacts upon workflows. The public comment period will undoubtedly cause more evidence to surface (and I encourage everyone who comments to include evidence as to why you agree or disagree, not just assertions or emotions).
  • There’s a broader view of the clinical team. I see progress towards a balanced perspective with the focus on medication administration, assessments, longitudinal care plan, and care team members, though there’s a lot of room for interpretation as to what the last two mean. There’s also more clarity of clinical/discharge instructions in Stage 2. It’s good to see the acknowledgement of other professionals such as nurses, pharmacists, and therapists, in addition to physicians.
  • Patients are increasingly considered part of the team. I’m all for “engaged” patients and consider myself one. The most challenging Stage 2 objective for patient engagement may be the patient download-upon-demand feature for all EHRs. What do patients want out of the data and how does it improve their health? I’d like to see this addressed in the Evidence Base/Rationale section.
  • More and more information will be exchanged. That’s no surprise, and can be a good thing for patients and providers, if…it’s usable and relevant, as I wrote in my three part December series starting with Information Liquidity. As stated by Dr. Lyle Berkowitz who gave testimony to the HIT Standards Committee: “Data sharing alone is never enough. Dr. Reid Coleman from Lifespan had the quote of the day when he said,   ‘Data is like salt water… you need a filter to drink it’. I’d also add that it helps to have good plumbing to connect it to the right facilities, and then also to have plenty of glasses available to make it easy for people to get it to the ‘final foot.’”
The Policy Committee has a tough tightrope to walk – on the one hand they’d like to wait for more early returns, evidence of how the industry is doing adopting Stage 1; they could then incorporate those experiences before finalizing Stage 2. On the other hand, they have heard that everyone need lots of lead time to work Stage 2 into their roadmaps, and needs its requirements finalized “yesterday” or at least 18 months beforehand. So they’re trying to send a “signal to the market” but they can’t guarantee that the signal won’t change. They’ll probably receive hundreds of comments. Interesting times lie ahead!

Monday, January 17, 2011

Philosophizing

Now that the HIT Policy Committee Meaningful Use workgroup’s Stage 2 recommendations have been released for public comment (due February 25th), I and probably hundreds of others will give it a careful review and offer public comments. I know that a lot of thought and balancing of considerations from public testimony has already gone into it. The “philosophical basis” – the “why” not just the “what” -- of MU is fundamental to what is included and how it is specified. I hope to look for what lies behind the objectives. Some of this comes out in the workgroup’s meetings (which, along with the HIT Policy Committee meetings, are open to the public, so I encourage you to participate). However, the “intent” behind proposals is not always evident in the documents themselves, and readers who didn’t listen to the meetings might not be able to read between the lines to understand what outcomes the workgroup is striving for. Presentations from prior meetings can help explain the guiding principles more than just reading the proposed objectives. I believe it really is about better health outcomes for all of us, including the currently disadvantaged. 

In the meantime before I’ve analyzed the recommendations, what should I blog about? I’m humbled by the consistency with which other bloggers manage to write daily (I wish…!) since it’s hard for me to find time, let alone good ideas, to share daily. In that regard, my son Dan sets a high bar for consistency as he writes his blog, The Philosopher Developer, almost daily. Similar to my combining thoughts on HIT and music, he combines his vocation (programming) and his avocation (philosophy/thinking). While it’s tempting for me to say “like father, like son,” Dan started his blog a year before I did, so I should say “like son, like father!” His January 15th post on “Resolution: the need for a terminating condition” is sound advice to us all as we engage in discussion and debate about the right path forward in HIT, health reform, family issues, or anything else, such as the Arizona Tragedy. Hopefully, there can be a harmonious environment and humble attitude framing our discussions, even when we disagree.

Back to Health IT. It’s clear that increasing patient engagement in health is one of the main drivers for Stage 2 and 3. I look forward to the day, not too far away, when I’ll ask each of my healthcare providers, as meaningful users, to share information with me as a patient or possibly a caregiver, per the regulations (electronic copy, access, download, secure messaging) or beyond that if they can. My HIT work won’t be a compartment that I leave behind at the office, but a reality every time my family or I interact with the healthcare system. Like it not, that’s likely to be more and more often for me for the rest of my life.

Monday, January 10, 2011

An Aid to Survey the River of Clinical Information

Recently, I’ve had discussions with many people in the HIT industry about the future direction for Meaningful Use (MU), especially about exchanging clinical information. It’s clear that Stage 1 is only the start of a journey, and that increasingly robust sets of clinical information will need to be exchanged. However, such exchanges need to be helpful rather than burdensome, and much work needs to occur to figure out how to display what’s significant, accurate, reconciled, and usable for clinicians and patients (see my recent blog series Part 1, Part 2, Finale).

I’m sharing a spreadsheet (a work in progress) showing a library of standardized reusable data sections and comparing many types of electronic clinical documents/records, including the two most “famous” that are required in Meaningful Use Stage 1, CCD and CCR. This spreadsheet may eventually be published in a more final form from an organization, but even now it may be useful to you if you have any of these questions:
  • What must be shared in Stage 1 as a clinical summary with providers and/or patients? (See spreadsheet columns B and D green cells)
  • Are certification and MU clinical summaries the same? There are some interesting differences that can be found between the standards for certification and the language for meaningful use (See column A and the CMS FR – Clinical Summary tab).
  • What’s the difference between a full C32 and what’s required in Stage 1 certification? Quite a bit, actually! (See column D, white check marks)
  • What data are not included in CCR and CCD but might be desirable to share in the future? (See all rows and columns). Stage 1 requires only the most commonly requested clinical summary data (meds, allergies, problems, results, etc.).
  • How much reusability exists among today’s electronic clinical documents? (See column Q, which also indicates which sections are most often used). There are worthy efforts afoot to improve commonality and reduce divergence, such as the ONC sponsored CDA Consolidation Project. 
Here’s my compulsory “liquid” or “music” analogy of the day. A mighty rushing river is growing, of clinical information and the standards thereof. I hope my high-level spreadsheet serves as an aid, a “Bridge Over Troubled Water” where you can safely survey the river before you plunge in. Although I created this spreadsheet, with plenty of review from Health Story and EHRA members, I’m far from being the authority on clinical documents. Robin Raiford did wonderful work on a similar spreadsheet in 2009, which was actually more detailed, but was limited to HITSP CDA documents and preceded the ONC Final Rules. I recommend that you read the original specs, and follow Keith Boone’s blog and his upcoming CDA book.

The Arizona Tragedy and Harmonious HIT

I was shocked, saddened, and angered by the news of the recent assassination attempt on Arizona congresswoman Gabrielle Giffords and the killing or wounding of 18 other innocent bystanders.

What does this have to do with healthcare IT? A little. I am very grateful that it looks as though Representative Giffords will survive. Undoubtedly, an amazing amount of medical technology as well as skilled and compassionate healthcare professionals were involved in the surgery. Without both the technology and the  people, she certainly would not have survived. And both will be needed continuously if, as expected, she faces a lengthy and arduous recovery, long after the headlines have faded from our memories.

What does this have to do with "harmonious?" A lot, actually. Jared Loughner is not talking at present, and it's too soon to know what really motivated him to commit such a horrendous crime. Still, I'm reminded that words as well as bullets can wound deeply. It's ironic and sad that a subject such as Healthcare Reform, and to some extent Healthcare IT -- both intended to improve people's lives -- are sometimes debated with such rancor and acrimony in public forums, e.g., on the Internet.

I hope that the discussion of legislation, meaningful use, certification, standards, and all other subjects related to healthcare, and HIT, will be conducted in a rational civil manner. When we feel strongly about the rightness of our cause, that's great: we should exercise our privilege of free speech. But with privilege come responsibility, and we don't need to fire off verbal bullets or grenades with shrapnel, as if others are merely "targets" and not real people. Rep. Giffords, the other victims, and all of us deserve no less as we try to work together, harmoniously rather than dissonantly, to improve the health of our nation and our people.

This may be too "preachy" a blog post, but the Arizona tragedy affected me and made me think again about the reasons I got into the HIT industry in the first place. How can I and each of us contribute to making things better?

Tuesday, December 28, 2010

Finale: Drinking Safely and Healthily from Liquid Information

Happy New Year! If you must drink, do it responsibly and safely. Which brings us to the subject of this Finale to a blog series that started here. How can Health IT systems help clinicians to consume/drink the liquid information that will increasingly flow to them? How can these systems help users protect both patient safety and clinician productivity?

The faucet has been opened. It’s fairly easy to tell developers to send clinical information to others. It’s harder to know what to tell providers to do with what they receive. The trickle of information exchange hasn’t become a flood yet, but let’s be prepared! Clinicians want the information to be usable, not a hindrance. They want to do the right thing, but they can’t afford to reduce their capacity to see patients, and they don’t want to be liable for negligence if they can’t read every word of every available electronic record for the patient. Policies and guidelines for realistic expectations and duties of clinicians to retrieve and read electronic information would be very helpful coming from medical, legal, and health information management professional associations.

Patient safety is impacted both if there’s inadequate information flow but also if there’s too much. We’ve heard of “alert fatigue” in clinical systems, and could face “information overload fatigue” too, where important information is obscured by “noise” that could lead to errors or duplication as occur in the absence of information flow. While the PCAST report on health information technology proposes applying search technology (good idea), that may be helpful but insufficient. I can “Google” anything, but how often do you or I look beyond the first page of results, even when there are thousands of hits? I implicitly rely upon the search engine to display the most relevant links first, since my time is limited. While a patient’s medical records are much less voluminous than data in web searches, even dealing with only 24 clinical documents per my personal health example requires indicators of relevance to aid decision making. If I don’t look at Google search results page 2, it’s probably not a big deal, but the stakes are much higher for patient care: who can decide what’s most important to show for a clinical encounter, especially since that varies depending on the encounter’s purpose?

Thankfully, healthcare and academic organizations realize the need to tackle this challenge. I was fascinated by the findings from this medication reconciliation project at Partners Healthcare: “design of a novel application and the associated services that aggregate medication data from EMR and CPOE systems so that clinicians can efficiently generate an accurate pre-admission medication list.” It was pioneering work at the time, and was a springboard for further research, such as refined aggregation algorithms based on more standardized data, and clinician-vetted UI techniques to reduce cognitive burden and add value.

In 2008 when I helped interoperability and ambulatory workgroups (including physicians, nurses, pharmacists, engineers, and others) write the CCHIT certification criteria and roadmap through 2011, we proposed 2009 as a first step in consumption of discrete data such as medications and allergies from C32 CCDs, but concluded that we shouldn’t be prescriptive about EHR functionality or workflow to handle such data.

Medications are just one example of data that needs to be reconciled after being exchanged. A new clinical data Reconciliation project at IHE offers promise to advance the cause of clinical decision support for reconciling problems, allergies, medications, and more. It’s humbling to acknowledge that HIT isn’t so sophisticated or trusted to make clinical decisions, any more than web search can buy your next car automatically. Instead, we should share the results of research to inform and stimulate innovations that are then tested in multiple care settings, before even thinking about regulating and standardizing functionality. But I’m all for specifying how standardized information exchanges can be inputs to these innovative algorithms and UIs.

To return to my musical analogy, music isn’t just playing the notes in a score: but rather how the score is brought to life to touch the heart through the genius of great performers. We shouldn’t try to turn musicians into robots where every nuance is pre-programmed. Similarly, in HIT MUsic, there’s room for the art as well as the science!

If anyone reading this can point to interesting research and experiences regarding consuming health information that’s exchanged, I’d love to hear about them. The results would benefit providers and developers EHRs and HIEs as well.

Monday, December 27, 2010

Intermezzo: ONC Standards and Interoperability Framework Initiatives

Before the 3rd movement of my blog series -- on information liquidity, the trickle becoming a flood, and final post yet to be named -- I was busy just before Christmas writing responses to a call for comments on the ONC Standards and Interoperability Framework initiatives. I posted my responses on the ONC FACA blog (I had multiple responses, all on December 22nd around 2pm).

I'm also working with others on responses to the recent 108-page PCAST report on "realizing the full potential of health information technology to improve healthcare for Americans." More on that later...

So now, back to the post-holiday catchup and to the 3rd movement!

David

Wednesday, December 22, 2010

Andante: What Happens When the Trickle Becomes a Flood?

This is the second part of a “Symphony in Three Movements” blog. The second movement of a symphony is often the slow movement: Andante literally means “a moderately slow tempo (a walking pace).” The first movement (information liquidity) is Allegro (fast, lively) because there’s a national momentum around Meaningful Use (MU). But using/consuming/”drinking” the information has moved slowly for reasons that I’ll discuss now.

All of us have experienced information overload (too much paper mail, e-mail, so many web sites and so little time). Many messages compete for our attention and go unread. So when we advocate health information liquidity, and it comes, we need to be careful what we wish for!

As a patient, father and grandfather, I want clinicians to be helped, not burdened, by availability of my family’s information. So I’d like to know: what do they consider helpful? To starting think through this question, let’s consider a real world scenario rather than abstractions: myself as a patient (I consent to this disclosure of my health information).

Over the past year, as a relatively healthy person who took four sick days from work, I had the following medical encounters:
  • one ER visit followed by an additional day of hospital care for a “transient global amnesia” attack, which hopefully won’t recur
  • Two PCP visits: one routine annual physical, plus one following up the hospitalization
  • One Neurologist office visit following up the hospitalization
  • Two dermatology visits with minor procedures performed
  • One GI visit, related to a procedure performed in 2008
  • I also had dental and chiropractic visits

That’s 7 medical visits. The hospital has an EHR, and my PCP is starting to use one, but I don’t know about the others. Let’s hypothesize that they all are meaningful users of EHRs. Then they would have produced at least 16 electronic clinical documents: 7 clinical summaries and one discharge summary for the next provider, 7 electronic copies of health information and one discharge instructions document for me. I’m not counting other MU information exchanges such as e-prescriptions, immunization registry updates (one flu shot), nor reportable labs or surveillance. Here I’ll just focus on the clinical documents, realizing that much more information can also be exchanged (results for lab, EEG, EKG, CT, Echo; consult notes, etc.). If 2011 and 2012 are like 2010, then by 2013 I’d have 24 or more electronic clinical documents available to other providers. People with serious or chronic illnesses could have far more. So what should my providers in 2013 look at? All 24 documents? How would they decide what’s important and relevant? Most of these documents will be partly duplicative but may not list exactly the same problems, procedures, allergies, etc. To what extent does this additional information (and the effort to digest it) save time or work elsewhere? As far as I know, these aren’t simple questions with simple answers, but I’d be interested in your thoughts.

At a minimum in 2013 I’d expect the hospital to send (push) electronically a discharge summary and/or a CCD to my PCP and the Neurologist, who will then read them. The Direct Project has received a lot of attention because it has clear applicability to common scenarios like discharges, referrals, and consults. But that’s a drop in the bucket compared to all patient’s electronic health information, so there remains a big challenge about what to do with the rest of it.

As reported in the recent PCAST report, p.15, lack of liquidity and interoperability produces this problem: “In effect, the patient has fragmented into disconnected facts and clusters of symptoms. To prevent the most basic medical errors, some facts are elicited over and over again, to the frustration of patients and healthcare providers alike: ‘Do you have any drug allergies? Have you had any surgeries? Are you taking aspirin or blood thinners?’ This frustrating repetition works, albeit inefficiently, if the patient is cognitively intact and well informed, but not all patients fit that description, especially in the event of a serious or acute illness. Health providers need views of the patient that are less fragmented than at present.” And so along comes information liquidity to remedy the fragmentation – or does it? PCAST report p. 23 says: "A first point to convey is that in virtually all of our use cases, the “user” of the data does not need to be, and indeed should not be, scanning through the entire health record. Instead, the user needs to be looking at an application layer that accesses and presents a limited amount of information from a given health record or set of records."

That “application layer” has slowly been emerging in pockets of HIT, perhaps because the information exchange is still a trickle, not a flood yet. Do clinicians trust a layer to limit the information they see? What’s the right balance between too much and too little? Though I’m a standards advocate, I’m not sure we’re ready for standards in this area, but we do need research, innovation, real-world implementation testing, evidence of what works and what doesn’t, sharing of experiences, policies, and guidance. In my third and final movement of this series, I’ll talk about some promising research and projects underway to improve the usability and benefits of the information that flows. Despite what I said about the challenges, I’m optimistic that we (collectively) will figure this out.

In the meantime, while you await the finale of this symphony, Happy Holidays and Merry Christmas to you!