Tuesday, 9 November 2010

Provider Directories

Provider directories are a very hot national topic right now.  The HIT Policy Committee's HIE Workgroup created the Provider Dictionary Task Force to recommend strategies and policies.

Why are provider directories important?

When you think of the 3 necessary components to transport healthcare data from point A to point B, you need a routing method (REST, SOAP, SMTP),  a directory that tells you where to route, and certificate management to ensure the message is not read or modified during transmission.

The granularity of the directory(organization level or person level) has been a major part of the discussion.

If you want to route a message to John Halamka, do you route it to me as a person or BIDMC as my provider organization?   My EHR is hosted at the organizational level, so if you want to route it into my EHR, you should send it to my organization.   I may have  different preferences for communication depending on the urgency and the time of day/day of week.   Such detailed communication preferences are best implemented at the local organization level, so once the data arrives at the organization it can be further routed.

Another advantage of organization to organization communication is that fewer certificates are needed.   There are 70 hospitals in Massachusetts with 20,000 doctors.  It's much easier to manage 70 certificates than 20,000.

The details of how organization to organization directories should work is outlined in the Provider Directory task force materials.

In Massachusetts, we've implemented a slightly different approach.  The New England Healthcare Exchange Network (NEHEN) is a set of organization to organization gateways.  It works well for administrative data exchange and e-prescribing.   Although it is being used for clinical summary exchange, the challenge from a user's viewpoint is figuring out the right organization to receive data for a given clinician.   If I want to route a clinical summary to Dr. Bob, how do I know what organization hosts his EHR? What if he works at multiple organizations?

Here's what NEHEN has done per Greg Debor's testimony to the Provider Directory Workgroup.

'NEHEN administrative message handling and e-prescribing are based on preconfigured addressing schemes designed to deliver a message to a predetermined organization.  Program management staff maintain addressing tables and distribute them with NEHEN software.  This method easily supports routing an insurance eligibility request or claim to a payer, for example, or an electronic prescription to Surescripts for machine-to-machine processing.

Clinical health information exchange, however, is not nearly as straightforward.  There are multiple orders of magnitude more potential recipients, making centralized maintenance impractical and costly.  Many recipients may not be known to the sender, requiring a lookup capability akin to using an online Yellow Pages or White Pages directory.  In addition, not all processing by the recipient will be machine-to-machine, requiring some knowledge of the receiver’s preferences for fax, e-mail, human readable documents or EHR integration.  Recipients may delegate processing to certain staff, requiring knowledge of individuals rather than simply organizations.  Finally, the more sensitive nature of clinical information requires more complex access control to track and determine who at a recipient organization has been authorized to handle and view the information.

NEHEN has developed and deployed a Community Participant / Provider Directory  to support these aspects of clinical HIE, along with tools to allow delegated, self-managed registration and maintenance of directory entries.  The NEHEN directory supports both Yellow Page / White Page lookup and HIE routing.  Participants can use the NEHEN toolset to:

*Register and maintain organization, location, provider, clinical affiliation (practice hierarchies, etc.), receiving / message delivery preferences and other data using the NEHENExpress web-based user interface
*Delegate a person or destination specified by a provider to receive an electronic clinical message in addition to or instead of the provider (e.g., another covering physician, a practice assistant or practice e-mail inbox, a fax number an EHR URL, etc.)
*Upload provider, delegation and preference data in bulk (new and updates) via a NEHEN-specified web service
*Search for participating organizations, individual providers and delegates to add and maintain affiliations and delegate instructions
*NEHEN participants can now use the data in the directory in the course of data exchange to:
Determine whether another provider is eligible to participate in clinical data exchange via NEHEN
*Obtain routing information for a provider
*Select among multiple clinical affiliations to determine where an electronic message should be routed
*View provider data, clinical affiliation data, delivery preference and delegate data

These capabilities enable a number of functions critical to solving for the complexities inherent in clinical exchange such as allowing a patient or other person, such as a registration clerk, to accurately identify a patient’s provider of care to whom clinical messages should be routed.  For example, if two physicians named Smith practice in the same town, the practice name or address may be used to identify the Dr. Smith who provides care for the patient.

Allowing a receiving participant to route an incoming clinical message to the correct internal system for the provider to whom the message is addressed.  For example, if a participant’s providers use separate physical instances of an EMR, the location identified on an incoming message may be used to identify the EMR instance the message should be routed to.  If Dr. Smith is associated with Location A, a message for Dr. Smith can be routed to the EMR instance associated with Location A.

Discovering information about other participants’ availability for clinical HIE and their routing requirements.  This is equivalent to looking up a financial institution’s Bank Routing Number to determine how to accomplish a wire transfer, etc.

In designing the Community Participant / Provider Directory and functionality, NEHEN determined that no standards or comprehensive data sources are present today in the industry or cross-industry.  This led to the design of a simple data scheme, the elements of which are consistent with HL7 naming and data types.

NEHEN is now in discussion with leading providers of self-managed sources of provider data to pre-populate provider tables via web services for a richer data set for NEHEN users and to simplify database maintenance.  In pursuing this strategy, which NEHEN anticipates executing on in late-2010, NEHEN intends to provide its participants with provider, organization and routing data on a national level to enable data exchange across the NHIN."

Given the evolving national work on provider directories, heterogeneous state directory implementations, and emerging commercial products, it will be a very interesting year.  It's too early to tell if we'll have directory convergence or chaos.

Monday, 8 November 2010

The Cousin Jimmy Syndrome

I have great respect for my colleagues in the IT industry.   It's a challenging profession that requires a mixture of technical knowledge, people skills, and the emotional stability to deal with customer dissatisfaction when technology fails.

However, there's a downside to being an IT professional.  No matter how much expertise you have or what your reputation may be, many customers will not be able to distinguish between a polished industry expert and a self-promoting IT groupie.

I call this the "Cousin Jimmy Syndrome".

Here's how it happens.  You join a meeting to discuss a major IT project.  You talk about issues such as security, disaster recovery, change management, training, and support.

Then someone says, "Oh yeah, we've got 'Cousin Jimmy' doing that."   Or Bob who lives in his parents' basement.   Or Carol who knows how to use Excel and serves as the go to technology guru.

Unfortunately, when Jimmy, Bob, or Carol have an opinion, their colleagues trust them over you, since professional IT organizations may appear less nimble, less focused, and less accommodating than dedicated local experts.

Not to imply that IT professionals in large organizations are perfect, they have their flaws.  However, good management and oversight usually creates a culture in which there is division of labor, escalation, and few single points of human failure.    Cousin Jimmy does not know what he does not know.    His solutions may be fast or cheap but ultimately they are unsustainable, unmaintainable, and unsupportable.

How should the IT professional deal with Cousin Jimmy Syndrome?

1.   Let Cousin Jimmy fail - it may take a while, but eventually there will be a major outage, security breach, or data loss.   Although this may transiently feel like a win, it's really a loss for the customers.    It's a win the battle, lose the war tactic.

2.   Make Cousin Jimmy part of your team - this sometimes works and it's worth a try.   Success has a 1000 fathers, so if you can create a sense of team in which Jimmy gets all the credit but others do all the work, so be it.   The customers win.   Of course, it's hard to let Jimmy take the credit for what you've done, but I've learned over the years that anything is possible if you are willing to give others the credit for success.

3.   Offer a service so good, so inexpensive, and so reliable that eventually Jimmy moves on - this works much of the time.   I believe that hard work, innovation, and honesty eventually pay off and win the game.   True, sometimes politics triumph over expertise but you can outlast the naysayers.   By selflessly focusing on the customers, the technology, and your staff, you'll end up with a service that's really hard to beat at any price.   Jimmy may be omni-present, but he'll have a difficult time keeping up as technology evolves.

So, when the meetings are awkward, keep your composure, stick to your principles, and put the customers first.   Nine times out of ten, you'll eventually beat the Cousin Jimmy Syndrome.

If you need inspiration, you can always watch Verizon commercials in which the polished FIOS engineer wins over the meddlesome Cable Guy.  Next time you're debating technology with Cousin Jimmy, just think of him as the cable guy!

Friday, 5 November 2010

Cool Technology of the Week

As readers of my blog know, I'm passionate about mobile technology.

I believe that iPhone/Android smartphones, iPod Touch, and the Ipad, Playbook, Galaxy, Streak  will become the platform for healthcare   Desktops with complex operating systems, antivirus, and heavy "thick client" applications will disappear.  Ray Ozzie's farewell message to Microsoft describes a post PC world.

As we think about EHRs in the post PC world, I can envision an App Store for modular EHR components.   The Harvard SHARP grant SMArt team is working on this idea.

What about a healthcare App Store for patients that brings the PHR to the iPhone/iPod/iPad/Android etc.

Last week, Quest introduced Gazelle which brings powerful PHR functionality to smart phones.   It's my cool technology of the week.

Gazelle includes automated lab results and educational materials, medication list, immunization list, allergy list, medical contacts, in case of emergency information - everything you need to share your medical records in an emergency.

CLIA rules complicated that delivery of lab data directly to patients, but new revisions to regulations have made this easier.

A lifetime medical record with educational materials on smartphones - that's cool.

Thursday, 4 November 2010

What Makes Me Happy?

I was recently in a meeting with senior managers who commented on my generally even temperament.  I rarely express extremes of emotion (joy, sadness, anger, despair) in the workplace.   They asked me what makes me happy.

Here's my own version of "Raindrops on roses and whiskers on kittens".

What makes me happy

1.  Innovation - Operations is really important, but if I can spend dedicated time each week creating something new,  I feel invigorated and inspired.

2.  Focusing on one thing and doing it really well - In our multitasking world, it's hard to meet everyone's expectations for real time response if you are focused on a single task at a time.

3.  Teaching a willing student - Sharing the lessons I've learned with my family, friends, and colleagues is very fulfilling for me.   Teaching my daughter has been one of my life's great joys.

4.  Experiencing the world with a friend - I enjoy exploring exotic locales from museums to mountaintops with my best friend - my wife.

5.   Time in the wilderness and outdoors in general - Every week I try to spend time hiking, biking, skiing, kayaking or climbing.

6.  A breakfast of rice, tsukemono, vegan miso soup and big cup of Gyokuro green tea from Uji  - It's healthy, low calorie, and satisfying.

7.   Vegan Pot Pie or Split Pea Soup after a day working outside - These are definitely my comfort foods.

8.   A Saturday morning at home with a coil of  blue incense from the Kungyokudo Incense shop  (near the Kyoto train station)

9.  A glass of red wine on a cold winter's night.

10.  Growing Japanese cucumbers, eggplant and shiso.  The taste of cucumber salad (sunomono), grilled eggplant with miso (nasu dengaku),  or shiso on soft tofu reminds me of summer nights in Japan.

What makes me unhappy

1.  Unplanned work that increases scope without a change in resources or timeline

2.  Needless administrative or bureaucratic processes imposed by those who are not actually doing the work

3.  The guy behind you who honks 2 milliseconds after the light turns green

4.  Flights that are delayed or cancelled due to equipment failure when the airlines run so lean that no spare aircraft or parts are available.

5.  Cold callers from organizations you do not support

6.  Your neighbor whose dog barks continuously and whose children play loud musical instruments, but who objects to the sounds created by garden maintenance at noon on a Saturday.

7.  Staff at home improvement stores who have never done home improvement

8.  Monday morning quarterbacks who lack the expertise to do work but are happy to criticize others' work.

9.  People who believe that the louder they yell the faster those around them will work

10. Machiavellian people who use politics, relationships, and manipulation rather than hard work to get ahead.

There you have it.

Last night it was 25F and I enjoyed a glass of Syrah with a vegan pot pie, spent the evening with my family, and then focused on writing a book preface.  That makes me happy.

Wednesday, 3 November 2010

Losing the Battle but Winning the War

Over the past 2 months since Labor Day, I've been given hundreds of challenging controversies to resolve.   I'm not sure if it's the economy, healthcare reform, or the uncertainties of an election year, but in general, the Fall of 2010 has had more emotion, discontent, and chaos than most years.

Whenever I'm asked to play Solomon, I always ask myself - do I want to win the battle or win the war?

I could use formal authority to force a short term outcome.

I could raise my voice, leverage my reputation,  or utilize negative commentary (think political advertising) to win the day.

All such victories are temporary and I would never use such tactics.

Imagine that I forced customers to use a technology solution without gaining their buy in.  I'd win the battle.   Inevitably, the users would try as hard as they could to make the project fail, blaming all negative consequences on the products I mandated.   I'd lose the war.

It is far better to take the long view, devising a solution that stakeholders will embrace as their own and feel motivated to make successful.

The day to day battles rarely matter.  The trajectory over years is the best measure of success.

Similarly, in the world of technology, if you go live a few months late because you focused on user acceptance, no one will ever remember.  If you go live too early to meet an arbitrary deadline, no one will every forget.

Thus, pick your battles.   Ignore most of them.   Keep your eye on your long term vision and work toward it incrementally, focusing on change management and stakeholder alignment.

It's the war, not the battle, that people will remember long after you're gone.

Tuesday, 2 November 2010

The Electronic Medical Home

In previous blog posts, I've mentioned an idea deserves its own dedicated post.

Over the weekend, I keynoted the eClinicalWorks National User's Conference in Florida.    One of the attendees emailed me the following question:

"I have a number of questions regarding certain types of patient-level data that might cause us problems in the future of HIE.  No one, to date, has been able to answer these and I thought I might ask you.

The first, and easiest, is how we we going to handle the following situation:

1) I am seen in Boston as a child and my mother says that I am allergic to Penicillin (or pick your drug of choice).  The nurse-practitioner asks a few questions of my mother, who isn't terribly forthcoming with information but insists that I am allergic.   While he/she has reservations, they record it as an allergy in their eclinicalworks EMR.  It goes to the Massachusetts HIE.

2) I move to Washington DC to go to college and the family practitioner hears my allergy story.  He asks more detailed questions and decides that I DON'T have an allergy.  He records it in his Epic system and it goes to the DC HIE.

3) I get my first job in Dallas.  Unfortunately, I wind up unconscious in the Dallas Ed and the doctor queries my records - in our future super-connected world, he/she sees that I am both allergic and not allergic to Penicillin.

How do I, as a patient, protect myself from this happening?"

The best way to accomplish this is for each patient in the country to choose an Electronic Medical Home (EMH) which stores a copy of their electronic data as gathered by clinicians, pharmacies, labs, payers, and other data generators.

The concept is simple.    An Electronic Medical Home vendor would create a URL or secure email address for each participating patient.

The patient would provide this URL or secure email address to every caregiver.

At the end of each visit, test or hospitalization the data would be sent securely to the Electronic Medical Home of the patient's choice.

These Electronic Medical Homes could be offered by primary care givers, EHR vendors (such as eClinicalWorks' 100millionpatients.com), or non-tethered EHR vendors such as Google Heath, Microsoft Healthvault, or Dossia.

Over the next few weeks, I predict that even telecoms like AT&T and Verizon will announce eHealth offerings.

All we need to get started is for one of these groups to create simple software capable of receiving clinical data via a RESTful URL or via SMTP/TLS Secure email/XDR as suggested by NHIN Direct.

Electronic Medical Homes nicely solve the problem of consolidating multiple disparate records in one place.   They solve the Meaningful Use requirement to deliver summaries and educational materials to patients.    The make the patient the steward of their own lifetime records, simplifying consent issues for data sharing.

But what if a patient does not want to be the steward of their Electronic Medical Home?   That's ok.  It will give rise to a new professional service, the healthcare knowledge navigator,  an expert who manages your Electronic Medical Home on your behalf.   This could be a primary care clinician, a midlevel (Nurse Practitioner/Physician Assistant) or a trusted vendor.

Here's my challenge to the industry.

Create an Electronic Medical Home using a RESTful URL or the NHIN Direct specification.

As long as you protect privacy, ensure technical security, and obtain patient consent, I will send data to you on behalf of the patient.

Monday, 1 November 2010

The FY11 HMS Operating Plan

Every year I work with all the stakeholders at Harvard Medical School to develop an operating plan.

This year, we have additional governance input http://geekdoctor.blogspot.com/2010/10/year-of-governance.html as well as additional funding from Stimulus grants

Although budgets are still constrained, the limits imposed by the 2008-2009 economic downturn are relaxing a bit.  We're hiring more staff, moving to new space, and expanding our infrastructure capacity.

My current direct reports include experts overseeing education, administration, research, innovation, infrastructure, and customer service.   They work closely with governance groups to develop yearly priorities.

It's a year of reaccreditation by the Liaison Committee on Medical Education (LCME), so we've supported applications and infrastructure in preparation for our March visit.

Harvard is planning it's 5 year capital expenditures and we're forecasting IT capital needs as part of that process.

A much greater focus on enterprise security has resulted in policies for data protection and oversight.   We've completed this with new infrastructure tools to monitor data flows and isolate confidential information.

Major priorities for this year include

*developing a Harvard-wide strategy for reporting and analyzing conflicts of interest
*further expanding our innovative research social networking and data mining technologies
*piloting new procurement and funding strategies
*expanding our support for the administrative workflows that support students and faculty in the educational process
*implementing new firewalls, antivirus, intrusion detection and prevent technologies
*expanding our high performance computing facility to 6000 CPU cores and a petabyte of storage

Here's the initial version of the FY11 HMS IT Operating Plan. I look forward to a great year ahead.
Girls Generation - Korean