Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and EHR for FREE!

ICD-10 Ebola Infographic

Posted on October 21, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

In my post on funny ICD-10 codes ruining the ICD-10 brand, I briefly commented how there’s no ICD-9 code for Ebola, but that there is one for ICD-10.

Beth Friedman from Agency Ten22 shared a link to this ICD-10 Ebola Infographic that I thought readers would find really interesting.

Ebola ICD-10 Infographic

One more reason to finally implement ICD-10 in the US.

Are Researchers Ready to Use Patient Health Records?

Posted on October 20, 2014 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site (http://radar.oreilly.com/) and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

There’s a groundswell of opinion throughout health care that to improve outcomes, we need to share clinical data from patients’ health records with researchers who are working on cures or just better population health measures. One recommendation in the much-studied JASON report–an object of scrutiny at the Office of the National Coordinator and throughout the field of health IT–called on the ONC to convene a conference of biomedical researchers.

At this conference, presumably, the health care industry will find out what researchers could accomplish once they had access to patient data and how EHRs would have to change to meet researchers’ needs. I decided to contact some researchers in medicine and ask them these very questions–along with the equally critical question of how research itself would have to evolve to make use of the new flood of data.
Read more..

Meaningful Use #HITsm Twitter Chat

Posted on October 17, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I had the honor today to host the #HITsm Twitter chat. For those not familiar with the #HITsm chat, you just join every Friday at Noon ET and watch the tweets that are sent using the #HITsm hashtag. There are usually 4-5 questions that are discussed over the hour chat. Since I was the host, I created the questions this week. I chose to focus the chat on the latest happenings with meaningful use. The transcript of the chat is found here.

I just took a look at the stats for the chat on Symplur and saw that the chat had 68 participants that sent out 474 tweets which had 3,196,079 impressions. You have to be a little careful looking at impressions since that’s potential impressions, but it’s still interesting to consider the possible reach of a chat.

There were some really interesting tweets during the chat, so here are the questions and a few (ok, more than a few since I got carried away) of my favorite tweets: Read more..

Insights from Dr. Eric Topol at #SHSMD14

Posted on October 16, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.


Patient care will eventually win, but sacred cows still have a lot of fight in them.


I’m still chewing on this one. I definitely love the idea of remote visits. Not sure it’s the smartest patient room.


This trend is definitely happening. Although, if you sound out Iwwiwwiwi, it sounds a lot like whining. I’m not sure that’s a good thing. Either way, I think the market is going to push towards on demand medicine.


I’d love to hear more about this topic. I think the first step is identifying the real cost problem. Seems like these top drugs could provide a really good start.

Are We Moving from Passive Patients to Active Consumers?

Posted on October 15, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.


This were the questions I was asking myself when I sat in on a presentation by Intermountain’s revenue cycle manager at the Craneware Summit in Las Vegas. I think the clear answer to the first question is that patients are becoming more active. Patients are shouldering a larger portion of the cost of their healthcare and so now they’re move involved in the care they receive. Plus, the internet and mobile applications have made it much easier for a patient to be informed on their health.

The later question is much harder. What impact will this change have on healthcare?

I certainly don’t have all the answers, but it’s going to take a dramatic shift by the current healthcare system to adapt to this changing consumer. The days of the omniscient doctor (at least perceived) are gone and there’s now a shift to a more collaborative care model.

Of course, many doctors fear that this shift is going too far. They usually point to the overbearing patient who thinks they know better than the doctor. Certainly these patients exist, but they are the minority and aren’t a huge shift from the patients who didn’t listen to their doctor before the shift happened. The problem is that 1 rotten apple spoils the bunch.

Overall, I think this change will be a good thing for the healthcare system. There are a lot of things you can’t change in healthcare if you don’t have an active patient that’s engaged and cares about their health. Hopefully this will be the start of that movement to helping patients care more about their health.

If you want proof that things are changing, Intermountain has changed their mission statement. First, it’s not very often that an organization as large as Intermountain makes a major change to their mission statement. Second, think about whether this mission statement would work for your hospital or healthcare organization:

Change is in the air. What are you doing to prepare for the change?

Will EHR Vendors Become Service and Consulting Companies?

Posted on October 14, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This is the topic of a really interesting LinkedIn discussion: Will EHR Vendors Become Service and Consulting Companies?

I think this is a really great question and one that’s worthy of serious consideration. I think we’ve seen this happen time and time again in the IT industry. Some of the best examples are IBM, HP, and Dell. As their IT hardware and software becomes a “commodity” then they leverage their relationships and domain expertise to change into a service and consulting company. Usually this also involves them spending their extra cash to acquire the leading consulting company (or companies) in the industry as well.

In some ways we’re already seeing this happen. Epic announced a consulting division of their company in order to retain their senior staff. Cerner’s always made a good chunk of their money from consulting services.

Of course, thanks to meaningful use incentive money and some still massive upgrade costs, EHR vendors haven’t needed to shift their business model to a service and consulting model yet. There’s still plenty of money to be made just selling the software, training, etc.

What will also be interesting to watch is whether the large service and consulting companies like Accenture, IBM, HP, Dell, etc. will eat up the market share so that the EHR companies don’t have as much of an opportunity to grow a service and consulting business. No doubt it will be a big dog fight. Not to mention many of the current EHR consulting companies (although, you could see many of these getting acquired by the EHR vendors).

I guess my short answer to this question is: In the short term, we’re not likely to see a massive shift towards services and consulting, but long term it’s very likely to happen. What are your thoughts?

Open Standards Advance in Health Care Through the Appeal of FHIR and SMART

Posted on October 13, 2014 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site (http://radar.oreilly.com/) and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

The poor state of interoperability between EHRs–target of fulminations and curses from health care activists over the years–is starting to grind its way forward. Dr. Kenneth Mandl, a leader of the SMART Platform and professor at the Boston Children’s Hospital Informatics Program, found that out when his team, including lead architect Josh Mandel, went to HIMSS this year to support Cerner’s implementation of his standard, and discovered three other vendors running it.

That’s the beauty of open source and standards. Put them out there and anyone can use them without a by-your-leave. Standards can diffuse in ways the original developers never anticipated.

A bit of background. The SMART platform, which I covered a few years ago, was developed by Mandl’s team at Harvard Medical School and Children’s Hospital to solve the festering problem of inaccessibility in EHRs and other health care software. SMART fulfilled the long-time vision of open source advocates to provide a common platform for every vendor that chose to support it, and that would allow third-party developers to create useful applications.

Without a standard, third-party developers were in limbo. They had to write special code to support each EHR they want to run on. Worse still, they may have to ask the EHR vendor for permission to connect. This has been stunting the market for apps expanding the use of patient data by clinicians as well as the patients themselves.

SMART’s prospects have been energized by the creation of a modern interoperability resource called FHIR. It breaks with the traditional health care standards by being lean, extendible in controllable ways, and in tune with modern development standards such as REST and JSON.

It helps that SMART was supported by funds from the ONC, and that FHIR was adopted by the leading health care standards group, HL7. HL7’s backing of FHIR in particular lent these standards authority among the vendor and health care provider community. Now the chocolate and peanut butter favored by health IT advocates have come together in the SMART on FHIR project, which I wrote about earlier this year.

Mandl explains that SMART allows innovators to get access to the point of care. As more organizations and products adopt the SMART on FHIR, API, a SMART app written once will run anywhere.

Vendors have been coming to FHIR meetings and expressing approval in the abstract for these standards. But it was still a pleasant surprise for Mandl to hear of SMART implementations demo’d at HIMSS by Intermountain, Hewlett-Packard, and Harris as well as Cerner.

The SMART project has just released guidlines for health care providers who want to issue RFPs soliciting vendors for SMART implementations. This will help ensure that providers get what they ask and pay for: an API that reliably runs any app written for SMART.

It’s wise to be cautious and very specific when soliciting products based on standards. The notion of “openness” is often misunderstood and taken to places it wasn’t meant to go. In health care, one major vendor can trumpet its “openness” while picking and choosing which vendors to allow use of its API, and charging money for every document transferred.

The slipperiness of the “open” concept is not limited to health IT. For years, Microsoft promulgated an “open source” initiative while keeping to the old proprietary practices of exerting patent rights and restricting who had access to code. Currently they have made great progress and are a major contributor to Linux and other projects, including tools used with their HealthVault PHR.

Google, too, although a major supporter of open source projects, plays games with its Android platform. The code is nominally under an open license–and is being exploited by numerous embedded systems developers that way–but is developed in anything but an open manner at Google, and is hedged by so many requirements that it’s hard to release a product with the Android moniker unless one partners closely with Google.

After talking to Mandl, I had a phone interview with Stan Huff, Chief Informatics Officer for Intermountain. Huff is an expert in interoperability and active in HL7. About a year ago he led an effort at Intermountain to improve interoperability. The motivation was not some ethereal vision of openness but the realization that Intermountain couldn’t do everything it needed to be competitive on its own–it would have to seek out the contributions of outsiders.

When Intermountain partnered with Cerner, senior management had by that time received a good education in the value of a standard API. Cerner was also committed to it, luckily, and the two companies collaborated on FHIR and SMART. Cerner’s task was to wrap their services in a FHIR-compliant API and to make sure to use standard technology, such as in codes for lab data.

Intermountain also participated in launching a not-for-profit corporation, the Healthcare Services Platform Consortium, that promotes SMART-on-FHIR and other standards. A lot of vendors have joined up, and Huff encourages other vendors to give up their fears that standardization is a catheter siphoning away business and to try the consortium out.

Intermountain currently is offering several applications that run in web browsers (and therefore should be widely usable on different platforms). Although currently in the prototype stage, the applications should be available later this year. Besides an application developed by Intermountain to monitor hemolytic disease among neonates and suggest paths for doctors to take, they support several demonstration apps produced by the SMART project, including a growth chart app, a blood pressure management app, and a cardiovascular app.

Huff reports that apps are easy to build on SMART. In at least one case, it took just two weeks for the coding.

Attendees at HIMSS were very excited about Intermountain’s support for SMART. The health care providers want more flexible and innovative software with good user interfaces, and see SMART providing that. Many vendors look to replicate what Intermountain has done (although some hold back). Understanding that progress is possible can empower doctors and advocates to call for more.

Is EHR on Life Support? Short Answer…No

Posted on October 10, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Today, David Swink sent me a link to an article from the Washington Examiner and this quote from the article:

“A revolt is brewing among doctors and hospital administrators over electronic medical records systems mandated by one of President Obama’s early health care reforms.”

“The American Medical Association called for a “design overhaul” of the entire electronic health records system in September because, said AMA president-elect Steven Stack, electronic records “fail to support efficient and effective clinical work.”

It seems like there have been a wave of articles similar to this coming out in the national media. For some reason the national media only likes to report on things when “the sky is falling.” It’s kind of a ridiculous report though.

What’s not ridiculous is that many doctors are dissatisfied with their EHR software. That is something that is real and many are extremely frustrated with it and many of the EHR regulations that require a lot of extra work by them. Does that mean that we’re going to see an EHR “design overhaul” or that the doctors are going to revolt against EHRs and stop using them?

My answer (as the headline alludes) is that it’s not going to happen. Certainly we’re going to see some EHR switching over the next few years. In fact, we might see a lot of EHR switching. However, we’re not going to see a mass of people revolting against EHR and going back to paper. That would be a true revolt and it’s just not going to happen. Like it or not, EHR is the go forward technology that will be used by healthcare to document healthcare.

Meaningful use on the other hand is a different story. I do think that meaningful use is on life support. If the congress can somehow get the Flex-IT Act to pass, then we can take meaningful use off life support, but I’m still not planning to discharge MU from the hospital. The program has some serious health issues.

On a more optimistic note, I’m really excited to see what doctors and hospitals start doing with the data stored in EHR. Is it everything we want it to be? No, but I believe we’re still going to see a lot of good come from EHR software now that EHR’s are implemented and we’ve largely got MU behind us.

How Quick Can We Analyze Health IT Data?

Posted on October 9, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

While at the AHIMA Annual convention, I had a chance to sit down with Dr. Jon Elion, President and CEO of ChartWise, where we had a really interesting discussion about healthcare data. You might remember this video interview of Dr. Elion that I did a few years back. He’s a smart man with some interesting insights.

In our discussion, Dr. Elion led me on an oft repeated data warehouse discussion that most data warehouses have data that’s a day (or more) old since most data warehouses batch their data load function nightly. While I think this is beginning to evolve, it’s still true for many data warehouses. There’s good reason why the export to a data warehouse needs to occur. An EHR system (or other IT system) is a transactional system that’s build on a transactional database. This makes it difficult to do really good data analysis. Thus the need to move the data from a transactional system to a data store designed for crunching data. Plus, most hospitals also combine data from a wide variety of systems into their data warehouse.

Dr. Elion then told me about how they’d worked hard to change this model and that their ChartWise system had been able to update a hospital’s data warehouse (I think they may call it something different) every 5 minutes. Think about how much more you can do with 5 minute old data than you can do with day old data. It makes a huge difference.

Data that’s this fresh becomes actionable data. A hospital’s risk management department could leverage this data to identify at risk patients that need a little extra attention. Unfortunately, if that data is a day old, it might be too late for you to be able to act and prevent the issue from getting worse. That’s just one simple example of how the fresh data can be analyzed and improve the care a patient receives. I’m sure you can come up with many others.

No doubt there are a bunch of other companies that are working to solve this problem as well. Certainly, day old healthcare data is valuable as well, but fresh data in your data warehouse is so much more actionable than day old data. I’m excited to see what really smart people will be able to do with all this fresh data in their data warehouse.

Ebola Lapse in Dallas Offers Few Lessons, Except About Our Over-reliance on Technology

Posted on October 8, 2014 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site (http://radar.oreilly.com/) and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

Of all the EHR problems encountered daily across the country, the only one to hit the major news outlets was a non-story about a missed Ebola diagnosis in Dallas, Texas. Before being retracted, the hospital’s claim of an Epic failure launched a slew of commentary in the health IT field. These swirled through my head last night as I tried to find a lesson in the incident.

The facts seem to be as follows. A 42-year-old man named Thomas Eric Duncan arrived from Liberia and checked in to the emergency room at Texas Health Presbyterian Hospital Dallas complaining of symptoms consistent with an Ebola diagnosis. He told the admitting nurse he had come from Liberia, and the nurse entered the data into the Epic EHR.

The purpose of recording the patient’s travel history, however, seemed to be simply to determine the need for immunizations, so the EHR kept it within a nurse’s section of the data (which the hospital called a “workflow”) and did not display it to the doctor. The doctor sent Duncan home, where he came into contact with about 100 people who were potentially infected. His symptoms worsened and he returned to the hospital two days later, where he was finally diagnosed correctly and admitted.

Late night musing #1: If Texas Health Presbyterian Hospital Dallas can’t diagnose a case of Ebola, why do they think they can treat one? The hospital has won numerous awards, including one for patient safety–I guess you’re safe once you’re admitted.

Meanwhile, the city of Dallas waited several extra days to clean up infected sheets and other belongings from the Duncan home. In Africa, such detritis are recognized as a major source of new Ebola infections.

Late night musing #2: Does this reflect the competence of public health officials in this country? Maybe we should turn the job over to the Secret Service.

It’s really a shame that the national press jumped on the hospital’s announcement that the EHR was the source of the problem. Commenters criticized the hospital right away, asking why the nurse didn’t simply tell the doctor, and why the doctor didn’t ask on his own.

Finally, the hospital backed off from blaming Epic, thus making the hospital look even stupider and more guilty than it already appeared. Nevertheless, EHRs at some hospitals may be designed to flag warning signals.

Clearly, there are many layers to this health care failure. I don’t blame the nurse, or even the doctor. ERs are always busy, and the nurse might never have known who would see the patient or even be in the ER when the doctor finally saw him.

But I do find a small lesson in the brief appearance of the EHR as a pivotal character in the story. The nurse thought he or she was doing their job just by entering the data into the EHR, and the doctor thought he was doing his job by reading it. The EHR had loomed as a magical solution to health care workflow–in the minds of hospital administrators, if not the ER staff.

Maybe if the nurse knew that the travel history was for the purpose of immunizations, he or she would not have relied on the EHR to use that information for diagnosis. Besides showing the need for training, some of my colleagues suggest that this problem calls for FDA regulation of EHR interfaces. They also suggest that systems use good user interface design to highlight important information (which would require a definition of what’s “important”) or at least allow searches for critical elements of the record.

Late night musing #3: Behind this also lies the mindlessness of much data collected by EHRs. I’m sure the nurse knew whether the unfortunate Mr. Duncan was a smoker and whether he suffered from depression, because regulations require these things to be recorded. Travel history became just another one of these automatic requirements to be tossed into the EHR and forgotten.

My story also concerns the musings of other health IT commentators, who suggested that EHRs be better integrated into “workflows”–as if every clinician follows a mechanical path of treatment and the EHR can figure out what it is.

Another thoughtful posting calls for integrating infectious diseaess into clinical decision support. But as my colleague Sandra Raup (R.D., J.D., M.P.H.) points out, CDS depends on a long history of clinical data collection. One can’t instantly add a new disease.

It might have been useful for some international health organization to realize, when the Ebola outbreak began to spread, that it would eventually break out of central Africa, and then to provide an app to hospitals around the world for checking symptoms and travel history. There is certainly a creative role for health IT to play.

I think the messiness of the Texas Health Presbyterian Hospital Dallas story shows why EHR failures, numerous as they are, don’t get reported in the press. There are just too many complicating factors. The EHR is partly configured by the clinic’s staff, who thereby become responsible for some of its decisions. The EHR failure usually comes when the staff is under stress, when they have communication problems, when the patient’s condition is rare. Ascribing blame becomes a tangled mess; one must start designing systems with multiple, redundant points to catch failures that can fall through the cracks.

So one level, this is just another sad story of humanity’s tendency to trust too much in its technology, a story that ranges from the flight of Icarus to the sail of the Titanic and the failure of the Fukushima Daiichi nuclear power plant. On other, it’s a familiar story of a systemic problem leading to what’s sometimes called a “normal failure.” Not much new to learn, but lots of work to do. Clinicians have to evaluate EHRs and know how the data is used, a more open system in all directions.