Today was a big day - the end of Standards Summer Camp. We presented the HIT Standards Committee work of the past 6 months and then attended a celebratory reception at the White House.
Judy Sparrow, the ONC "national coordinator" who orchestrated all our HITSC meetings, announced her retirement last month. Jon Perlin and I presented her with a silver bowl, engraved with the words "The Standard Bearer". Thanks for all you've done, Judy.
As we discussed our Summer Camp work during the meeting, we were guided by a few basic principles:
While it might not be perfect, does it represent the best we have at this point in history?
Does it point us in the right direction?
Is it the next step in an incremental approach to refining the standards and implementation guides?
Does it support our policy objectives?
Can we update it as needed going forward through the SDO community?
Doug Fridsma presented an overview of our Summer Camp activities to date:
The Metadata Analysis Power Team lea by Stan Huff completed the standards for patient identification, provenance (which organization generated the data), and security flags. Simple XML constructs from CDA R2 and standard X.509 certificates were chosen for these requirements.
The Patient Matching Power Team led by Marc Overhage completed its analysis of best practices for patient matching, noting the types of demographics that should be captured in systems to optimize the sensitivity and specificity of patient matching applications.
The Surveillance Implementation Guide Power Team led by Chris Chute chose one implementation guide for each of the public health transactions - surveillance, reportable lab, and immunizations. We had a spirited discussion about the optional fields in the implementation guides and made it clear that we want the core elements to be the certification criteria. We do not want each state public health department to mandate different "optional" fields. Our transmittal letter will note that EHRs that send the core set should meet the certification criteria. Public health departments should accept this core set. Optional fields are just that - optional items for future reporting needs.
Farzad Mostashari, National Coordinator, framed the important discussion of transport standards by noting that we must move forward, boldly specifying what is good enough. If we specify nothing, the silos of data we have today in hospitals, clinician offices, pharmacies, and labs will persist. There's a sense of urgency to act.
The NwHIN Power Team led by Dixie Baker presented its thoughtful analysis of the 10 standards guides included in NwHIN Exchange and the 2 standards guides included in NwHIN Direct. This analysis was not a comparison of the two, but was an objective look at the suitability of each standards guide for its intended purpose to support aspects of transport functionality at a national scale. The team did not discuss their suitability for use at the local, state, or regional scale. The team did not declare "push or "pull" as a superior architecture. Their thoughtful analysis led to a very robust discussion. I'd summarize it as:
*Direct is low risk for the purpose intended, pushing data from point A to point B using SMTP/SMIME with an optional XDR (SOAP) connector. Additional work needs to be done on certificate discovery, but that will use DNS and LDAP, two well adopted technologies.
*Exchange needs additional work to ensure it scales at a national level for pull and push transactions. The S&I Framework teams are working on modular specifications that should enable a subset of Exchange components to be used, simplifying implementation and support. The Standards Committee will seek additional testimony from Exchange implementers to learn more about their experience.
*It's worthwhile to think about additional transport standards that do not yet have well specified implementation guides, such as a combination of REST, oAuth and TLS - something that Facebook, Amazon, or Google would use to create a highly scalable transport architecture.
The ePrescribing of Discharge Meds Power Team led by Jamie Ferguson presented the use of HL7 2.2-2.51 transactions to support hospital information system workflows in a manner that is compatible with Medicare Part D. We clarified that newer versions of HL7 2.x which are backward compatible should also be allowed.
The Clinical Quality Workgroup and Vocabulary Task Force led by Jamie Ferguson presented their transition plans for vocabularies, identifying the cross maps between vocabularies that need to be created and supported as we evolve from our current use of vocabularies to a future state in which there is one structured vocabulary per domain of medicine (problems, medications, labs, allergies etc).
Doug Fridsma then presented an overview of the Standards and Interoperability Framework activities and next steps:
Transitions of Care - Doug described a brilliant approach that incorporates simple XML, such as has been used in the CCR, with the expandability of the CCD. He calls this next evolution of clinical summaries "Consolidated CDA templates". It's likely that the clinical summary certification criteria will evolve to a single XML format that is easy to use, fast to implement, expandable, based on a reference model, and human readable. Well done!
Reportable Labs - In the past, standards harmonizers struggled to balance simple, easy to implement lab specifications such as ELINCS with the comprehensive and full featured lab specifications from HITSP. The S&I group created a foundation based on ELINCS that is expandable to include all the features of the HITSP specifications using a single HL7 2.51 implementation guide. Amazing work.
Provider Directories - The S&I Framework team had the courage to admit that directory standards are still evolving and need more testing/piloting before selection. DNS/LDAP approaches are likely to work well for certificate discovery. Other aspects of directories such as provider routing addresses and electronic service capabilities may be stored in web pages (microdata), LDAP (HPD), or X12 274 directory structures.
Doug also described new works in progress - Query Health for distributed data mining, Data Segmentation to manage disclosures of protected health information, and Electronic Submission of Medical Documentation for transmission to Medicare review contractors.
Finally and very importantly, the Implementation Workgroup led by Liz Johnson and Judy Murphy presented the Implementation Workgroup certification criteria analysis. We had a thoughtful discussion of each open issue and suggested a path forward for each certification item.
Truly an inspiring meeting - the most work we've ever done in a single day.
The delivery of Meaningful Use Stage 2 Standards and Certification criteria was recognized at a White House celebration by Aneesh Chopra, Chief Technology Officer and numerous members of the Obama administration senior staff. Thanks so much to Aneesh and others for celebrating our work.
As I told the Standards Committee today, I am honored to serve with this team, the hardest working Federal Advisory Committee in government. A milestone day for the country.
Wednesday, September 28, 2011
Tuesday, September 27, 2011
Preparing for a New CEO
On October 17, 2011, Dr. Kevin Tabb MD joins Beth Israel Deaconess as the new CEO.
As part of his briefing packet, I needed to summarize all the key IS issues for the next 3 months, 6 months and 1 year. Here's what I said:
Introduction
Information Systems at BIDMC has a 30 year tradition of industry firsts:
First web-based Healthcare Information Exchange, CareWeb - 1997
First web-based Enterprise-wide Personal Health Record, Patientsite - 1999
First web-based Enterprise-wide Provider Order Entry system - 2001
First web-based Enterprise-wide electronic medication reconciliation system - 2007
First "Magic button" for health information exchange invented at BIDMC - 2008
Pilot hospital to exchange data with Google Health, Healthvault, and CDC - 2008
Pilot hospital to exchange data with the Social Security Administration (Megahit) - 2009
First hospital to implement clinical iPads - 2010
First hospital to achieve federal certification of its EHR systems - 2011
First hospital to achieve meaningful use and receive Federal IT stimulus funding - 2011
The Information Week 500 Awards ranked BIDMC the #1 healthcare IT organization in the country for 2011. By the end of 2011, we'll have eliminated handwritten orders and the emergency department will be paperless.
We've done this with an operating budget that is less than 2% of BIDMC's operating expenses and a capital budget that has been increasingly constrained.
Scope of responsibilities
Information Systems at BIDMC is responsible for all clinical, financial, research, education, and administrative applications. Telecom, Media Services, Knowledge Services, and Health Information Management (medical records) are part of IS. Our scope includes comprehensive IT support for 83 locations including the Main Campus in the Longwood Medical Area, Needham Hospital, APG (owned practices), HMFP (academic affiliates), BIDPO (physician organization that includes many private clinicians), and Community Health Centers. Our infrastructure includes a primary and disaster recovery data center. We support 18,626 user accounts (of which 17,410 have email boxes), 10,600 desktops, 2000 laptops/tablets, 3000 network printers. 600 iPads, 1600 iPhones, 403 servers (152 physical, 2501 virtual) and 1.5 petabytes of storage.
Key challenges
90 Days
Laboratory Information System - On January 21, 2012, BIDMC will replace all laboratory automation in a single day, retiring 30 years of home-built lab systems with a commercial system from Soft Computer. Additional functionality will be added after the go live via planned additional phases. The Laboratory Information Systems Steering Committee will prioritize ongoing future work.
5010 go live - On January 1, 2012, all private and public payers in the US will implement a new revenue cycle transmission and content format called 5010. All BIDMC systems and interfaces are complete. The challenge is testing with all our payers, many of which are not yet ready. We will be able to transmit old (4010) and new (5010) formats, so we are prepared for any payer contingency plans.
Malware control - Harvard networks are attacked every 7 seconds, 24x7x365. The sophistication of the attacks has increased dramatically since identity theft has become a profitable business for organized crime. We have an expert team of security professionals and a multi-layered defense of firewalls, intrusion detection, and anti-virus tools.
Compliance - over the past three years, the number of government and plaintiff attorney requests for information has skyrocketed. The impact on IS is that an increasing percentage of our staff time is spent on e-discovery, file sequestration, and applications that support compliance efforts.
Hospital integration - Milton hospital will join the BIDMC family in the next few months. The clinical system integration includes bi-directional viewing of BIDMC webOMR and Milton Meditech via the web, as well as bidirectional viewing of Atrius Epic and Milton Meditech via the web. This is the same integration we offer all affiliated hospitals and clinician offices. Here's an overview of the Massachusetts state-wide health information exchange effort
180 days
Analytics- Although the precise future of Accountable Care Organizations is unknown, their formation requires a combination of health information exchange and analytics. Here's an overview of BIDMC's strategy.
Community IT - As BIDMC expands its footprint to Anna Jaques, Milton, Lawrence General, more primary care offices, and potentially new affiliations, we must have a scalable community IT function that can respond to changing needs with agility.
365 days
ICD10- Despite our efforts to convince CMS and HHS to delay ICD10, reducing the burden on organizations which are trying to implement Meaningful Use, 5010, and healthcare reform simultaneously, it is clear that ICD10 will go forward with an October 1, 2013 deadline. Here's an overview of the challenges it creates. Although the project is burdensome, has no ROI, and will distract resources from other strategic imperatives, ICD10 will be a top hospital priority in FY12. We have a steering committee compromised of all the right stakeholders. ICD10 is not an IS project, but requires the unified collaboration of all operational areas.
eMAR - Medication safety has been a strength of BIDMC, with its innovative provider order entry, medication reconciliation and e-prescribing systems. In FY12, BIDMC will leverage the work done in FY11 on idealized medication workflow redesign to implement bedside medication verification and electronic medication administration record pilots. Hospitals which have adopted these technologies early have been limited by available technology (computers on wheels) and have low user satisfaction. Our aim is to use mobile devices such as the iPhone/iPod/iPad to create a better workflow and user experience.
Clinical documentation - although BIDMC’s ambulatory documentation is fully automated, inpatient progress notes are still handwritten, then scanned. A multi-disciplinary stakeholder group will devise a unified care team documentation workflow which will then automate and pilot. Our hope is to create “wiki-like” team charting.
Learning Management System - As noted above, compliance requirements are increasing in the short term and long term. To address the staff education aspects of compliance, BIDMC will be implementing a learning management system over the next year.
Healthcare Reform
As discussed above, healthcare reform will require additional health information exchange and analytics. The blog postings noted above outline the details. Additionally, BIDMC has been been an IT pilot site for numerous state and federal efforts. We expect to be the IT learning laboratory for healthcare reform.
Key opportunities
We’re experts in mobile, wireless, disaster recovery, security, and data standards. We lead national and statewide efforts to share data for population health, quality measurement, public health, electronic disability adjudication and payer/provider collaboration. We're experts at interoperability and analytics. We host EHRs for every affiliated clinician and provide quality/outcome/process analytics. We’ve achieved meaningful use for our hospitals and 90% of our physicians will attest by 12/31/11.
We look forward to the opportunities ahead.
As part of his briefing packet, I needed to summarize all the key IS issues for the next 3 months, 6 months and 1 year. Here's what I said:
Introduction
Information Systems at BIDMC has a 30 year tradition of industry firsts:
First web-based Healthcare Information Exchange, CareWeb - 1997
First web-based Enterprise-wide Personal Health Record, Patientsite - 1999
First web-based Enterprise-wide Provider Order Entry system - 2001
First web-based Enterprise-wide electronic medication reconciliation system - 2007
First "Magic button" for health information exchange invented at BIDMC - 2008
Pilot hospital to exchange data with Google Health, Healthvault, and CDC - 2008
Pilot hospital to exchange data with the Social Security Administration (Megahit) - 2009
First hospital to implement clinical iPads - 2010
First hospital to achieve federal certification of its EHR systems - 2011
First hospital to achieve meaningful use and receive Federal IT stimulus funding - 2011
The Information Week 500 Awards ranked BIDMC the #1 healthcare IT organization in the country for 2011. By the end of 2011, we'll have eliminated handwritten orders and the emergency department will be paperless.
We've done this with an operating budget that is less than 2% of BIDMC's operating expenses and a capital budget that has been increasingly constrained.
Scope of responsibilities
Information Systems at BIDMC is responsible for all clinical, financial, research, education, and administrative applications. Telecom, Media Services, Knowledge Services, and Health Information Management (medical records) are part of IS. Our scope includes comprehensive IT support for 83 locations including the Main Campus in the Longwood Medical Area, Needham Hospital, APG (owned practices), HMFP (academic affiliates), BIDPO (physician organization that includes many private clinicians), and Community Health Centers. Our infrastructure includes a primary and disaster recovery data center. We support 18,626 user accounts (of which 17,410 have email boxes), 10,600 desktops, 2000 laptops/tablets, 3000 network printers. 600 iPads, 1600 iPhones, 403 servers (152 physical, 2501 virtual) and 1.5 petabytes of storage.
Key challenges
90 Days
Laboratory Information System - On January 21, 2012, BIDMC will replace all laboratory automation in a single day, retiring 30 years of home-built lab systems with a commercial system from Soft Computer. Additional functionality will be added after the go live via planned additional phases. The Laboratory Information Systems Steering Committee will prioritize ongoing future work.
5010 go live - On January 1, 2012, all private and public payers in the US will implement a new revenue cycle transmission and content format called 5010. All BIDMC systems and interfaces are complete. The challenge is testing with all our payers, many of which are not yet ready. We will be able to transmit old (4010) and new (5010) formats, so we are prepared for any payer contingency plans.
Malware control - Harvard networks are attacked every 7 seconds, 24x7x365. The sophistication of the attacks has increased dramatically since identity theft has become a profitable business for organized crime. We have an expert team of security professionals and a multi-layered defense of firewalls, intrusion detection, and anti-virus tools.
Compliance - over the past three years, the number of government and plaintiff attorney requests for information has skyrocketed. The impact on IS is that an increasing percentage of our staff time is spent on e-discovery, file sequestration, and applications that support compliance efforts.
Hospital integration - Milton hospital will join the BIDMC family in the next few months. The clinical system integration includes bi-directional viewing of BIDMC webOMR and Milton Meditech via the web, as well as bidirectional viewing of Atrius Epic and Milton Meditech via the web. This is the same integration we offer all affiliated hospitals and clinician offices. Here's an overview of the Massachusetts state-wide health information exchange effort
180 days
Analytics- Although the precise future of Accountable Care Organizations is unknown, their formation requires a combination of health information exchange and analytics. Here's an overview of BIDMC's strategy.
Community IT - As BIDMC expands its footprint to Anna Jaques, Milton, Lawrence General, more primary care offices, and potentially new affiliations, we must have a scalable community IT function that can respond to changing needs with agility.
365 days
ICD10- Despite our efforts to convince CMS and HHS to delay ICD10, reducing the burden on organizations which are trying to implement Meaningful Use, 5010, and healthcare reform simultaneously, it is clear that ICD10 will go forward with an October 1, 2013 deadline. Here's an overview of the challenges it creates. Although the project is burdensome, has no ROI, and will distract resources from other strategic imperatives, ICD10 will be a top hospital priority in FY12. We have a steering committee compromised of all the right stakeholders. ICD10 is not an IS project, but requires the unified collaboration of all operational areas.
eMAR - Medication safety has been a strength of BIDMC, with its innovative provider order entry, medication reconciliation and e-prescribing systems. In FY12, BIDMC will leverage the work done in FY11 on idealized medication workflow redesign to implement bedside medication verification and electronic medication administration record pilots. Hospitals which have adopted these technologies early have been limited by available technology (computers on wheels) and have low user satisfaction. Our aim is to use mobile devices such as the iPhone/iPod/iPad to create a better workflow and user experience.
Clinical documentation - although BIDMC’s ambulatory documentation is fully automated, inpatient progress notes are still handwritten, then scanned. A multi-disciplinary stakeholder group will devise a unified care team documentation workflow which will then automate and pilot. Our hope is to create “wiki-like” team charting.
Learning Management System - As noted above, compliance requirements are increasing in the short term and long term. To address the staff education aspects of compliance, BIDMC will be implementing a learning management system over the next year.
Healthcare Reform
As discussed above, healthcare reform will require additional health information exchange and analytics. The blog postings noted above outline the details. Additionally, BIDMC has been been an IT pilot site for numerous state and federal efforts. We expect to be the IT learning laboratory for healthcare reform.
Key opportunities
We’re experts in mobile, wireless, disaster recovery, security, and data standards. We lead national and statewide efforts to share data for population health, quality measurement, public health, electronic disability adjudication and payer/provider collaboration. We're experts at interoperability and analytics. We host EHRs for every affiliated clinician and provide quality/outcome/process analytics. We’ve achieved meaningful use for our hospitals and 90% of our physicians will attest by 12/31/11.
We look forward to the opportunities ahead.
Monday, September 26, 2011
Protecting the Legacy of Bill and Dave
When I was an undergraduate at Stanford, my wife to be and I lived with Dr. Fred Terman, the Stanford Provost who first brought together William Hewlett and David Packard. In early 1980's I had the opportunity to meet Hewlett and Packard. Since then, I've had a special affection for the company.
HP has just hired its fifth CEO in six years, Meg Whitman, the former CEO of eBay. Carly Fiorina, Mark Hurd and Leo Apotheker are gone, each with a checkered history and a large severance check.
Now the future of the iconic company rests with a new leader who is expected to turn it all around.
Can one person do that? It seemed to work for Steve Jobs.
But, being a CEO is not very fun. There's a lot of risk and CEOs can only hope that overly optimistic Board expectations are tempered by twists of fate or alignment of historic market forces at the right time in the right place. The CEO can take credit and be a hero.
It's been a bad year for tech CEOs. Yahoo CEO Carol Bartz was fired over the phone. Rumors are flying about tech CEOs who may be on the way out.
I think of HP as a great printer, server, and storage company which leads the world in PC manufacturing. Their software has always been less than perfect in my experience, since software development is not a core competency of the company.
HP may be shedding its PC business to focus on higher margin software and services. At a time when mobile technologies such as smartphones and tablets are at the peak of consumer demand, HP has exited that business.
Every company has its lifecycle - early innovation, hypergrowth, the burden of maintaining an installed base, displacement by new early stage companies, and decline.
In the late 90's Microsoft could not be stopped. In the late 2000's Google was invincible. Now Apple is the most valuable company in the US and HP has lost $60 billion of shareholder value in the past year.
I truly hope that HP can be transformed by focusing the $120 billion dollar company on those businesses which are profitable and growing. Like IBM in the 1990's, it may need to radically change its focus.
It will take more than Meg to do it. The devoted employees of HP should be able to explain the company's core competencies to Meg and the Board. Hopefully, they will listen.
There's a 72 year tradition at stake.
Note to Meg - Bill, Dave, and Dr. Terman are counting on you. May you rise to the occasion.
HP has just hired its fifth CEO in six years, Meg Whitman, the former CEO of eBay. Carly Fiorina, Mark Hurd and Leo Apotheker are gone, each with a checkered history and a large severance check.
Now the future of the iconic company rests with a new leader who is expected to turn it all around.
Can one person do that? It seemed to work for Steve Jobs.
But, being a CEO is not very fun. There's a lot of risk and CEOs can only hope that overly optimistic Board expectations are tempered by twists of fate or alignment of historic market forces at the right time in the right place. The CEO can take credit and be a hero.
It's been a bad year for tech CEOs. Yahoo CEO Carol Bartz was fired over the phone. Rumors are flying about tech CEOs who may be on the way out.
I think of HP as a great printer, server, and storage company which leads the world in PC manufacturing. Their software has always been less than perfect in my experience, since software development is not a core competency of the company.
HP may be shedding its PC business to focus on higher margin software and services. At a time when mobile technologies such as smartphones and tablets are at the peak of consumer demand, HP has exited that business.
Every company has its lifecycle - early innovation, hypergrowth, the burden of maintaining an installed base, displacement by new early stage companies, and decline.
In the late 90's Microsoft could not be stopped. In the late 2000's Google was invincible. Now Apple is the most valuable company in the US and HP has lost $60 billion of shareholder value in the past year.
I truly hope that HP can be transformed by focusing the $120 billion dollar company on those businesses which are profitable and growing. Like IBM in the 1990's, it may need to radically change its focus.
It will take more than Meg to do it. The devoted employees of HP should be able to explain the company's core competencies to Meg and the Board. Hopefully, they will listen.
There's a 72 year tradition at stake.
Note to Meg - Bill, Dave, and Dr. Terman are counting on you. May you rise to the occasion.
Friday, September 23, 2011
Cool Technology of the Week
I've written that Accountable Care Organizations will require increasing amounts of health information exchange and analytics/business intelligence in order to be successful.
As we explore various tools and techniques, I've talked to people in industries outside of healthcare.
Palantir Technologies provides tools for analyzing, integrating, and visualizing data of all kinds, including structured, unstructured, relational, temporal, and geospatial. It has traditionally has focused on government, providing such functions as
Intelligence
Defense
Regulation and Oversight
Cyber Security
and financial data exploration/visualization for analysts and traders.
Here's a cool example of its use to analyze subprime mortgages.
Here's another example of its use with the Medicare cost data sets.
Edward Tufte has emphasized the need for creative visualizations to turn data into information, knowledge and wisdom.
Palantir's histogram and mapping tools do that nicely.
A business intelligence application that assembles disparate data sources and presents unique visualizations that empower analytic exploration. That's cool!
As we explore various tools and techniques, I've talked to people in industries outside of healthcare.
Palantir Technologies provides tools for analyzing, integrating, and visualizing data of all kinds, including structured, unstructured, relational, temporal, and geospatial. It has traditionally has focused on government, providing such functions as
Intelligence
Defense
Regulation and Oversight
Cyber Security
and financial data exploration/visualization for analysts and traders.
Here's a cool example of its use to analyze subprime mortgages.
Here's another example of its use with the Medicare cost data sets.
Edward Tufte has emphasized the need for creative visualizations to turn data into information, knowledge and wisdom.
Palantir's histogram and mapping tools do that nicely.
A business intelligence application that assembles disparate data sources and presents unique visualizations that empower analytic exploration. That's cool!
Thursday, September 22, 2011
My Atlantic City Memories
Today I'm in Atlantic City, New Jersey presenting at the HIMSS Mid-Atlantic Symposium.
In 1965, I lived in Wilingboro, NJ near Trenton and visited Atlantic City one weekend with my parents.
What does a 3 year old remember?
Walking the Boardwalk
Touring the attractions of the Steel Pier
Eating Saltwater Taffy
For some reason, I remember a Planter's Peanuts man. Per Wikipedia there was a Peanut Man statue on a bench in Atlantic City, so there's some association with Planter's and the area.
My parents recall the area as a bit run down in the 1960's but I can only remember the wondrous sights, sounds, smells, and tastes that I had never experienced before. It was sensory overload for a 3 year old.
Above is a postcard from that era.
Today's Atlantic City has hotels, casinos, restaurants, outlet stores, and convention space, but the souvenir shops, the taffy, and the roasted peanuts are still the same. It's amazing how much can change in a lifetime, but today I was able to relive a childhood experience on an early foggy morning in New Jersey.
In 1965, I lived in Wilingboro, NJ near Trenton and visited Atlantic City one weekend with my parents.
What does a 3 year old remember?
Walking the Boardwalk
Touring the attractions of the Steel Pier
Eating Saltwater Taffy
For some reason, I remember a Planter's Peanuts man. Per Wikipedia there was a Peanut Man statue on a bench in Atlantic City, so there's some association with Planter's and the area.
My parents recall the area as a bit run down in the 1960's but I can only remember the wondrous sights, sounds, smells, and tastes that I had never experienced before. It was sensory overload for a 3 year old.
Above is a postcard from that era.
Today's Atlantic City has hotels, casinos, restaurants, outlet stores, and convention space, but the souvenir shops, the taffy, and the roasted peanuts are still the same. It's amazing how much can change in a lifetime, but today I was able to relive a childhood experience on an early foggy morning in New Jersey.
Wednesday, September 21, 2011
The Challenges of ICD10 Implementation
On October 1, 2013, the entire US healthcare system will shift from ICD9 to ICD10. It will be one of the largest, most expensive and riskiest transitions that healthcare CIOs will experience in their careers, affecting every clinical and financial system. It's a kind of Y2k for healthcare.
Most large provider and payer organizations, have a ICD10 project budget of $50-100 million, which is interesting because the ICD10 final rule estimated the cost as .03% of revenue. For BIDMC, that would be about $450,000. Our project budget estimates are about ten times that.
CMS and HHS have significant reasons for wanting to move forward with ICD10 including
1) easier detection of fraud and abuse given the granularity of ICD10 i.e. having 3 comminuted distal radius fractures of your right arm within 3 weeks would be unlikely
2) more detailed quality reporting
3) administrative data will contain more clinical detail enabling more refined reimbursement
Large healthcare organizations have already been working hard on ICD10, so they have sunk costs and a fixed run rate for their project management office. At this point, any extension of the deadline would cost them more.
Most small to medium healthcare organizations are desperate. They are consumed with meaningful use, 5010, e-prescribing, healthcare reform, and compliance. They have no bandwidth or resources to execute a massive ICD10 project over the next 2 years.
Vendors have told me such things as "I have been amazed at how much we (and our third-party partners) are spending on getting prepared for ICD10 – and it's not what you would expect (extending data tables, new code lookup tools, etc.) It's a whole host of clinician assistance tools, new documentation workflows, new kinds of provider-facing decision support to maximize coding revenue while guarding against RAC audits - all simply for billing!"
In my CIO role, not any state or federal role, I will continue to listen to concerns about ICD10, sharing them broadly on my blog and with government leaders who will listen.
The Wall Street Journal recently published an article about the granularity of ICD10.
One of my staff posted this response, which is very thoughtful:
While nice-to-have, ICD-10 comes at a time when substantial cuts await providers. The "super committee" is deliberating on these now for Medicare and Medicaid. Adding more administrative overhead to the U.S. healthcare system is untimely and will ultimately impact clinical care. Our health care system already has twice the administrative overhead of other advanced nations. We arguably have the most complex medical reimbursement system in the world. ICD-10 makes it worse.
When HHS published the requirement for ICD-10 in the January 16, 2009 Federal Register, they estimated transition costs for health care providers to be 0.03% of patient revenues. For a $1B medical center, this would be $300,000. Based on experience at our hospital and that of my colleagues at other hospitals, they missed it by a factor of 10 or more.
When a regulation of this magnitude is published, various laws and executive orders require a Regulatory Impact Analysis. Some requirements are intended to protect small businesses and non-profits from burdensome, unfunded federal mandates. The marginal cost estimate published in the Federal Register for ICD-10 was $2.966 billion over the period 2011 to 2025. Two-thirds of this was transitional cost. The benefits were estimated at $4.540 billion.
HHS has a tradition of low-balling cost estimates. Further evidence can be seen with recent estimates of HITECH privacy regulations.
If Congress was doing its job of regulatory oversight, they would sponsor hearings to learn what payers and providers are actually spending on ICD-10 conversion. Costs for consulting services alone run into the millions. This does not count the application software conversion, training and education, and other "in-house" costs. At our medical center, we would be paying $380,000 according to HHS estimates. Instead, the marginal cost of ICD-10 will be in excess of $5m. For multi-hospital systems, the costs may exceed $100m.
A Congressional review of transition costs would turn the regulatory impact assessment on its head. Costs could easily become double the estimated benefit savings.
With ICD-10, the government is perpetuating a reimbursement system that is far too complex. We spend more than any other country on healthcare administrative overhead. The Medicare Claims Processing Manual, for example, is over 4,000 pages in length. The reimbursement system needs simplification to bring the cost of this function in line with other industries.
Recently, HHS began promoting a "global payment" initiative. This had the potential for simplifying reimbursement, but they over-laid it on top of the existing system. Instead of substitution, it was additive. You bill as usual and then have a settlement process that adds one more layer of administrative overhead.
Unfortunately, there are too many activities within and outside the government whose livelihood depends on perpetuating this complex system. It is akin to the Internal Revenue Code. There are also groups who promote ICD-10 for its more granular health care research potential. This is laudable, but not affordable. There is no "free lunch". Every dollar spent on administrative overhead is one less dollar spent on clinical care.
What's needed is a fresh look at the reimbursement system. While ICD is used in other countries, it is not used for reimbursement purposes. Rather, it is used for health statistics and reporting. Using it for reimbursement adds an entirely different dimension. Because it is used for reimbursement, the U.S. version requires numerous extensions. Read this as more codes and more complexity.
Our health care system needs to change. If we are going to cut cost, let it be overhead, not clinical care.
Most large provider and payer organizations, have a ICD10 project budget of $50-100 million, which is interesting because the ICD10 final rule estimated the cost as .03% of revenue. For BIDMC, that would be about $450,000. Our project budget estimates are about ten times that.
CMS and HHS have significant reasons for wanting to move forward with ICD10 including
1) easier detection of fraud and abuse given the granularity of ICD10 i.e. having 3 comminuted distal radius fractures of your right arm within 3 weeks would be unlikely
2) more detailed quality reporting
3) administrative data will contain more clinical detail enabling more refined reimbursement
Large healthcare organizations have already been working hard on ICD10, so they have sunk costs and a fixed run rate for their project management office. At this point, any extension of the deadline would cost them more.
Most small to medium healthcare organizations are desperate. They are consumed with meaningful use, 5010, e-prescribing, healthcare reform, and compliance. They have no bandwidth or resources to execute a massive ICD10 project over the next 2 years.
Vendors have told me such things as "I have been amazed at how much we (and our third-party partners) are spending on getting prepared for ICD10 – and it's not what you would expect (extending data tables, new code lookup tools, etc.) It's a whole host of clinician assistance tools, new documentation workflows, new kinds of provider-facing decision support to maximize coding revenue while guarding against RAC audits - all simply for billing!"
In my CIO role, not any state or federal role, I will continue to listen to concerns about ICD10, sharing them broadly on my blog and with government leaders who will listen.
The Wall Street Journal recently published an article about the granularity of ICD10.
One of my staff posted this response, which is very thoughtful:
While nice-to-have, ICD-10 comes at a time when substantial cuts await providers. The "super committee" is deliberating on these now for Medicare and Medicaid. Adding more administrative overhead to the U.S. healthcare system is untimely and will ultimately impact clinical care. Our health care system already has twice the administrative overhead of other advanced nations. We arguably have the most complex medical reimbursement system in the world. ICD-10 makes it worse.
When HHS published the requirement for ICD-10 in the January 16, 2009 Federal Register, they estimated transition costs for health care providers to be 0.03% of patient revenues. For a $1B medical center, this would be $300,000. Based on experience at our hospital and that of my colleagues at other hospitals, they missed it by a factor of 10 or more.
When a regulation of this magnitude is published, various laws and executive orders require a Regulatory Impact Analysis. Some requirements are intended to protect small businesses and non-profits from burdensome, unfunded federal mandates. The marginal cost estimate published in the Federal Register for ICD-10 was $2.966 billion over the period 2011 to 2025. Two-thirds of this was transitional cost. The benefits were estimated at $4.540 billion.
HHS has a tradition of low-balling cost estimates. Further evidence can be seen with recent estimates of HITECH privacy regulations.
If Congress was doing its job of regulatory oversight, they would sponsor hearings to learn what payers and providers are actually spending on ICD-10 conversion. Costs for consulting services alone run into the millions. This does not count the application software conversion, training and education, and other "in-house" costs. At our medical center, we would be paying $380,000 according to HHS estimates. Instead, the marginal cost of ICD-10 will be in excess of $5m. For multi-hospital systems, the costs may exceed $100m.
A Congressional review of transition costs would turn the regulatory impact assessment on its head. Costs could easily become double the estimated benefit savings.
With ICD-10, the government is perpetuating a reimbursement system that is far too complex. We spend more than any other country on healthcare administrative overhead. The Medicare Claims Processing Manual, for example, is over 4,000 pages in length. The reimbursement system needs simplification to bring the cost of this function in line with other industries.
Recently, HHS began promoting a "global payment" initiative. This had the potential for simplifying reimbursement, but they over-laid it on top of the existing system. Instead of substitution, it was additive. You bill as usual and then have a settlement process that adds one more layer of administrative overhead.
Unfortunately, there are too many activities within and outside the government whose livelihood depends on perpetuating this complex system. It is akin to the Internal Revenue Code. There are also groups who promote ICD-10 for its more granular health care research potential. This is laudable, but not affordable. There is no "free lunch". Every dollar spent on administrative overhead is one less dollar spent on clinical care.
What's needed is a fresh look at the reimbursement system. While ICD is used in other countries, it is not used for reimbursement purposes. Rather, it is used for health statistics and reporting. Using it for reimbursement adds an entirely different dimension. Because it is used for reimbursement, the U.S. version requires numerous extensions. Read this as more codes and more complexity.
Our health care system needs to change. If we are going to cut cost, let it be overhead, not clinical care.
Tuesday, September 20, 2011
Next Steps for Health Information Exchange in Massachusetts
Health Information Exchange (HIE) is challenging. As I've written about previously, several state HIEs have failed or are failing.
There are Federal HIE goals, State Medicaid goals, private sector goals, and many varied sources of funding. Each stakeholder has their own self interest.
The Harvard Program for Health Care Negotiation and Conflict Resolution teaches about the "Walk in Woods", moving from self interest, to enlarged interests, to enlightened interests, to aligned interests.
On September 19, the HIT Council and the HIT/HIE Advisory Committee of Massachusetts stakeholders took such a walk to review a straw man plan that aligns all the interests and optimizes available budgets.
Here's the idea.
There's an ONC-approved State Health Information Exchange plan. There's a State Medicaid plan. There are many existing regional health information exchanges in Massachusetts.
We created a Venn diagram of all these projects and identified their points of intersection.
Then, we developed objective criteria for what could be done now, what needs minor policy/technical work and what needs substantial additional work.
The end result was a phased plan making 2012 the year of connectivity to support push transactions, 2013 the year of databases to support analytics/population health and 2014 the year of the pull transaction.
We then worked on reconciling sources of funds.
There are two state programs with substantial federal matching grants - the Medicaid Management Information System (MMIS) and HITECH funds for State Medicaid Health Plans. Every dollar from state resources that is invested in these programs yields $10 of spending. A very wise use of state funds would be to leverage every dollar using federal matching programs. Since 100% of hospitals in Massachusetts receive Medicaid funds, Federal matching programs for Medicaid improvements are ideal for building the "information highway" to connect stakeholders as well as for state public health gateways to receive syndromic surveillance, reportable lab, and immunization data required by meaningful use.
However, what if we build the highway, but no one uses it? It's important to connect EHRs by overcoming technical and resource barriers. Our workgroups will devise a plan to create a grant or procurement program that leverages ONC HIE funds to accelerate EHR to HIE connectivity.
With senders, receivers, and a pipe connecting the stakeholders, we have a clear HIE plan.
With aligned federal, state and private resources, we can define the timelines and we've developed Gantt charts for all our FY12 projects.
To guide the projects, we'll have 3 "functionality" workgroups
Finance and Sustainability Workgroup,
Technology and Implementation Workgroup
Legal & Policy Workgroup
and 2 "engagement" workgroups
Provider engagement & Adoption Workgroup
Consumer and Public Engagement Workgroup
With clear goals that align the interests of all parties, a budget that optimizes every source of funds, and a multi-stakeholder Advisory Committee with community-wide participation in workgroups, we have the foundation to move forward.
As we proceed with a sense of urgency, our rallying cry to all stakeholders is "focus on making the HIE happen, not on the impediments and barriers that we'll encounter along the way."
I look forward to the work ahead and numerous go lives in FY12.
There are Federal HIE goals, State Medicaid goals, private sector goals, and many varied sources of funding. Each stakeholder has their own self interest.
The Harvard Program for Health Care Negotiation and Conflict Resolution teaches about the "Walk in Woods", moving from self interest, to enlarged interests, to enlightened interests, to aligned interests.
On September 19, the HIT Council and the HIT/HIE Advisory Committee of Massachusetts stakeholders took such a walk to review a straw man plan that aligns all the interests and optimizes available budgets.
Here's the idea.
There's an ONC-approved State Health Information Exchange plan. There's a State Medicaid plan. There are many existing regional health information exchanges in Massachusetts.
We created a Venn diagram of all these projects and identified their points of intersection.
Then, we developed objective criteria for what could be done now, what needs minor policy/technical work and what needs substantial additional work.
The end result was a phased plan making 2012 the year of connectivity to support push transactions, 2013 the year of databases to support analytics/population health and 2014 the year of the pull transaction.
We then worked on reconciling sources of funds.
There are two state programs with substantial federal matching grants - the Medicaid Management Information System (MMIS) and HITECH funds for State Medicaid Health Plans. Every dollar from state resources that is invested in these programs yields $10 of spending. A very wise use of state funds would be to leverage every dollar using federal matching programs. Since 100% of hospitals in Massachusetts receive Medicaid funds, Federal matching programs for Medicaid improvements are ideal for building the "information highway" to connect stakeholders as well as for state public health gateways to receive syndromic surveillance, reportable lab, and immunization data required by meaningful use.
However, what if we build the highway, but no one uses it? It's important to connect EHRs by overcoming technical and resource barriers. Our workgroups will devise a plan to create a grant or procurement program that leverages ONC HIE funds to accelerate EHR to HIE connectivity.
With senders, receivers, and a pipe connecting the stakeholders, we have a clear HIE plan.
With aligned federal, state and private resources, we can define the timelines and we've developed Gantt charts for all our FY12 projects.
To guide the projects, we'll have 3 "functionality" workgroups
Finance and Sustainability Workgroup,
Technology and Implementation Workgroup
Legal & Policy Workgroup
and 2 "engagement" workgroups
Provider engagement & Adoption Workgroup
Consumer and Public Engagement Workgroup
With clear goals that align the interests of all parties, a budget that optimizes every source of funds, and a multi-stakeholder Advisory Committee with community-wide participation in workgroups, we have the foundation to move forward.
As we proceed with a sense of urgency, our rallying cry to all stakeholders is "focus on making the HIE happen, not on the impediments and barriers that we'll encounter along the way."
I look forward to the work ahead and numerous go lives in FY12.
Subscribe to:
Posts (Atom)


