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 HIPAA for FREE!!

Are We Chasing the Carrot or Afraid of the Stick?

Posted on May 29, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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.

The other day SGC asked in my hospital EHR adoption chart post: “If there were no penalties for non-EHR adoption, what would that chart look like?”

For those that are too lazy to click over to that post to see the chart, it basically shows hospital EHR adoption being massively accelerated thanks to the government EHR incentive program. In fact, we’re approaching full adoption of EHR in the hospital space (worth noting is that the ambulatory provider space is lagging far behind that adoption). SGC asks the question about whether that adoption would have occurred without the penalties.

My personal experience is that most organizations appreciate the EHR incentive money and plan that in as part of their budgeting for an EHR, but that they were really much more motivated by the EHR penalties that would accrue if they didn’t adopt an EHR. So, I’d say that people are more afraid of the stick than they are motivated by the carrot.

This is probably more so the case because the penalties are going to exist in perpetuity. I think most hospital organizations believe (and I think rightly so) that the EHR penalties for not using an EHR are not going to stop. In fact, they could get much worse. Not to mention, other payers might start implementing similar penalties for non-EHR use as well.

What’s been your experience? Are the carrot or the stick more motivating to healthcare organizations?

Another related question would be, “If there had been no EHR incentive or penalties, what would the EHR adoption chart look like today?” That’s a topic for another blog post.

My Overall Take on EHR in the Middle East

Posted on May 28, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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.

If you follow me on Twitter or on Facebook, then you’ve probably seen me posting pictures of my trip to Dubai. While I’ve been able to have a little fun and games on this trip, I spent most of my time teaching a 3 day EHR workshop to a group of amazing people from Saudia Arabia, Oman, and Pakistan. If you’ve never been out of the US and experience other countries, then I highly recommend it. It provides some amazing added perspective to your life.

Based on the surveys and feedback from attendees, I’d say the workshop was a success. I was surprised that I could talk about EHR for 3 days, but I didn’t have any problem. We’re going to shorten future EHR workshops I do to only 2 days, not because there isn’t enough content, but that after 2 days of talking about EHR you’re pretty well burnt out and can’t take in more information.

While I’m glad to hear that those who attended got value from the workshop, I must admit that I was grateful for the learning I took away from those in my class. It’s the truth of teaching. The students often teach the teacher as much as the teacher teaches the students. In fact, the last session of the workshop was an opportunity for the students to share their experiences and insights with EHR and to raise their challenges so we could collectively help each other. I love this type of community support. I’m hopeful it will continue well after the conference. Luckily with things like Twitter, LinkedIn, and WhatsApp, it’s easy for all of us from around the world to stay connected. Email’s not bad either.

While the middle east and each country in the middle east has some unique idiosyncrasies, I was most surprised by how similar it is in these countries when I compare it with my experience in the US. We like to think that it’s very different (and in a few cases it is), but there is more in common with implementing EHR than there is different when you look at EHR across the world.

For example, they still had doctors who didn’t want to train on the EHR and then complained that they didn’t know how to use it. The power of doctor peer pressure is just as strong internationally as it is in the US. EHR interfaces are as much a nightmare in the middle east as it is in the US. I could go on and on.

The thing I found most similar to the US was the people cared about the patients much like they do in the US. We generally have really amazing people working in healthcare and that appears to be true in the middle east as well. While we all understand the challenges we face in healthcare, the desire to provide great care to the patient is a universal desire.

I’m heading home tomorrow. I’ll be grateful to be home in my own bed and with my family. However, I’ve almost got a return trip planned for the end of August. Plus, my Saudi friends want me to come and share my insights in their country. Considering one of them has a jet ski on the ocean, that sounds pretty enticing. Not to mention my new friends in Oman offered to let me ride their camel if I visited them. I think we’ll stick to Dubai for now, but you never know where life will take me in the future. Maybe a future training I do will line up with HIMSS Middle East in December. Either way, I love that I’ve been able to learn about new EHR perspectives. It’s always enlightening.

Knotty Problems Surround Substance Abuse Data Sharing via EMRs

Posted on May 27, 2015 I Written By

Katherine Rourke is a healthcare journalist who has written about the industry for 30 years. Her work has appeared in all of the leading healthcare industry publications, and she's served as editor in chief of several healthcare B2B sites.

As I see it, rules giving mental health and substance abuse data extra protection are critical. Maybe someday, there will be little enough stigma around these illnesses that special privacy precautions aren’t necessary, but that day is far in the future.

That’s why a new bill filed by Reps. Tim Murphy (R-PA.) and Paul Tonko (D-N.Y.), aimed at simplifying sharing of substance misuse data between EMRs, deserves a close look by those of us who track EMR data privacy. Tonko and Murphy propose to loosen federal rules on such data sharing  such that a single filled-out consent form from a patient would allow data sharing throughout a hospital or health system.

As things currently stand, federal law requires that in the majority of cases, federally-assisted substance abuse programs are barred from sharing personally-identifiable patient information with other entities if the programs don’t have a disclosure consent. What’s more, each other entity must itself obtain another consent from a patient before the data gets shared again.

At a recent hearing on the 21st Century Cures Act, Rep. Tonko argued that the federal requirements, which became law before EMRs were in wide use, were making it more difficult for individuals fighting a substance abuse problem to get the coordinated care that they needed.  While they might have been effective privacy protections at one point, today the need for patients to repeatedly approve data sharing merely interferes with the providers’ ability to offer value-based care, he suggested. (It’s hard to argue that it can’t be too great for ACOs to hit such walls.)

Clearly, Tonko’s goals can be met in some form.  In fact, other areas of the clinical world are making great progress in sharing mental health data while avoiding data privacy entanglements. For example, a couple of months ago the National Institute of Mental Health announced that its NIMH Limited Datasets project, including data from 23 large NIMH-supported clinical trials, just sent out its 300th dataset.

Rather than offer broader access to data and protect individual identifiers stringently, the datasets contain private human study participant information but are shared only with qualified researchers. Those researchers must win approval for a Data Use Certification agreement which specifies how the data may be used, including what data confidentiality and security measures must be taken.

Of course, practicing clinicians don’t have time to get special approval to see the data for every patient they treat, so this NIMH model doesn’t resolve the issues hospitals and providers face in providing coordinated substance abuse care on the fly.

But until a more flexible system is put in place, perhaps some middle ground exists in which clinicians outside of the originating institution can grant temporary, role-based “passes” offering limited use to patient-identifiable substance abuse data. That is something EMRs should be well equipped to support. And if they’re not, this would be a great time to ask why!

Documentation by Exception is the Dredge of EHR Documentation

Posted on May 26, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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.

There was a very bad practice that was started thanks in large part to EHR software implementations. That practice is called documentation by exception and it’s employed by many (most?) EHR vendors. For those not familiar with documentation by exception, here’s a definition:

Charting by exception (CBE) is a shorthand method of documenting normal findings, based on clearly defined normals, standards of practice, and predetermined criteria for assessments and interventions. Significant findings or exceptions to the predefined norms are documented in detail.

In the US, we all know why this type of documentation was implemented. By documenting all of the normal finding along with the exceptions, then the doctor is able to bill the insurance company at a higher level. I totally understand why doctors want to bill at a higher level. In fact, it was the argument that most EHR vendors would make when they were selling their product to doctors. The EHR was able to help doctors bill at a higher level and get paid more.

While this is going to be hard to change for this reason, there are so many unintended consequences associated with using documentation by exception in these practices. I know so many doctors that are literally embarrassed to share their chart notes with their colleagues because their chart notes are these long, cumbersome notes that are filled with normal findings that provide no value to anyone. Many of these doctors have resorted to creating a separate “short” note that only has the relevant “exceptions” detailed when they send their chart notes to another doctor.

Every doctor knows what I’m talking about, because they’ve found these long lengthy notes that are totally unusable. Plus, in many ways it puts a doctor at some risk if they documented a long list of “normal” items when in fact they didn’t actually check to see if everything was normal or not. However, more important than this is that the doctor can’t even read their own historical notes because they’re so cluttered with all these “normal” findings that it takes real work and effort (Translation: Wasted physician time) trying to search through these awful notes.

If somehow all of these normal findings that were being documented could add some value down the road, then I might change my mind about documentation by exception. However, I can’t imagine any useful clinical benefit to documenting a bunch of normal findings that weren’t actually checked or that were only casually observed. If you didn’t document something was wrong, then we can assume that everything else was normal or at least the patient didn’t complain of anything else. Why do we need to document it clinically? The answer is we don’t and we shouldn’t (except for the getting paid comments above).

We need to find a way to abolish these documentation by exception notes from healthcare. In the US this will be hard since it’s so tied to the payment system, but I’m sure smart minds can figure out a way to fix it. Every doctors I’ve ever talked to wants this solved. It almost makes the EHR notes useless to document this way. This is one more driver in the US system towards concierge and direct primary care models. In these cases, the doctors aren’t worried about reimbursement and so I can’t imaging they’d even consider documenting a patient visit in such an awful manner.

A part of me wonders if EHR vendors will work to solve this problem as well. They could have the beautiful note and the crappy, mess of a note. They’ll use less vulgar terms like the “clinical note” and the “billing note” or something like that, but maybe that’s a small step in the right direction to satisfying the clinical needs (short, concise, relevant notes) together with meeting the billing requirements note. It’s sad that EHR vendors need to do something like this, but it would be better than the current state of EHR notes.

EHR Partner Programs

Posted on May 22, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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.

Amazing Charts just announced a new EHR partner program. This isn’t something that’s particularly new for EHR vendors. They all have lots of partners. Some have formalized them into a program like athenahealth has done with their More Disruption Please (MDP) program. Others are much more quiet about the partners they work with and how they work with them.

What’s clear to me in the EHR industry is that an EHR vendor won’t be able to do everything. There are some that like to try (See Epic), but even the largest EHR vendor isn’t going to be able to provide all the services that are needed by a healthcare organization. This is true for ambulatory and hospitals.

Since an EHR vendor won’t be able to do everything, it makes a lot of sense for an EHR vendor to have some sort of partners program. The challenge for an EHR vendor is that a partner program comes with two major expectations. First, the partner has a high quality integration with the EHR software. Second, that the partner is something that the EHR vendor has vetted.

The first challenge is mostly a challenge because most EHR vendors aren’t great at integrating with outside companies. This is a major culture shift for many EHR vendors and it will take time for them to get up to speed on these types of integrations. Plus, these integrations do take some time and investment on the part of the EHR vendor. When there’s time and investment involved, the EHR vendor starts to be much more selective about which companies they want to be working with long term. They don’t want to spend their time and money integrating with a company which none of its users will actually use.

The second challenge is that EHR users assume that an EHR partner is one that’s been vetted by the EHR vendor. Even if the EHR vendor puts all sorts of disclaimers on their partner page, the EHR vendor is still associated with their partners. The written disclaimers might help you avoid legal issues, but working with shady partners can do a lot of damage to your reputation and credibility in the marketplace. I actually think this is probably the biggest reason that EHR vendors have been reluctant to implement partner programs.

I think over time we’ll see the first problem solved as EHR vendors work to standardize their APIs for partner companies. As those APIs become more mature, we’ll see much deeper EHR integrations and the costs to an EHR vendor will drop dramatically when it comes to new partner integrations.

The second problem is much harder to solve. My best suggestion for EHR vendors is to create a platform which allows your users to help you vet potential partners. Not only can they participate in the vetting process, but it can also help you know which partners would be useful to your users. Is there anything more valuable than user driven partnerships? It also puts you in a good position with potential partners if you already have users interested in the integration.

However, an EHR vendor shouldn’t just leave potential partnership requests to their users. Many of their users don’t know of all the potential partner companies. Users are so busy dealing with their day jobs that they often don’t know of all the potential companies that could benefit their practice or hospital. Certainly you should accept user input on potential partnerships, but an EHR vendor should also seed the potential partner feedback platform with a list of potential partners as well. The mix of an EHR vendor created list together with user generated partner lists is much more powerful than one or the other.

We’re just at the beginning of companies partnering and integrating with EHR vendors. I expect that over the next 5 years an EHR vendor will be defined as much by the organizations it chooses to partner with as the features and functions it chooses to develop itself.

What’s the Story on 21st Century Cures Legislation?

Posted on May 21, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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 just saw that the 21st Century Cures legislation passed the house committee process. Word on the street is that Congress probably won’t take this up even if the house passes it this summer. The legislation looks pretty interesting for those of us in healthcare IT. Blair Childs, Premier’s senior vice president of public affairs, offered the following statement on the legislation:

Members of Premier wish to thank House Energy and Commerce Chairman Fred Upton (R-MI) and Representative Diana Degette (D-CO) for their leadership to advance interoperability standards as part of the landmark 21st Century Cures legislation. With today’s vote, the vision for a fully interoperable health information technology ecosystem is one step closer to becoming a reality.

We also wish to thank Committee members Joe Pitts (R-PA), Frank Pallone (D-NJ), Gene Green (D- TX), Michael Burgess (R-TX) and Doris Matsui (D-CA) for their support of interoperability standards in the legislation, and for their efforts to ensure that the technology systems of the future will be built using open source codes that enable applications to seamlessly exchange data/information across disparate systems in healthcare.

Today’s vote is an essential step to optimize HIT investments, improve the quality of care across settings and avoid the cost burdens associated with the work around solutions that are needed today for systems to “talk” to one another. We strongly urge the full House of Representatives to support these interoperability standards and to vote in favor of moving the legislation forward as it stands today.

Many of the comments he offers about ensuring interoperability is open source and support for standards of healthcare interoperability are great things. Although, as I think we learned with the meaningful use regulations, the devil is in the details and the 21st Centure Cures legislation is not simple. I’d love to hear from people who are following the legislation. Is this a good piece of legislation? Should it be passed? Are their hidden land mines? What are the unknowns or uncertain outcomes of the legislation?

When I saw this legislation hit my email inbox it has me asking how people keep up with legislation. Not to mention, what’s the process for creating this legislation? Just thinking of the process makes me tired and overwhelmed. Is it any wonder that lobbyists are so powerful? It really takes someone whose full time job it is to track and influence legislation to really get something done. The process and legislation is so complex that a casual follower just can’t keep up. I think that’s really unfortunate. I’m not sure the solution though either.

HIMSS15: Adoption Still a Problem for Organizations Swapping EHRs – Breakaway Thinking

Posted on May 20, 2015 I Written By

The following is a guest blog post by Todd Stansfield, Instructional Writer from The Breakaway Group (A Xerox Company). Check out all of the blog posts in the Breakaway Thinking series.
Todd Stansfield

Each year the Health Information and Management Systems Society’s (HIMSS) annual conference is the Super Bowl of health IT. No other conference boasts more attendees ranging from health IT innovators and collaborators to pioneers. This year 40,000 plus participants descended on Chicago, all eager to learn about the new direction, trends, and solutions of the industry.

As always, buzzwords were aplenty—interoperability, care coordination, patient experience, and value-based care, to mention a few. During her keynote address on April 16, Karen DeSalvo, National Coordinator for the ONC, called the current state of health IT the “tipping point.” In 2011 the ONC released its four-year strategic plan focused on implementing and adopting electronic health records (EHRs). Now, DeSalvo says the industry is changed and ready to move beyond EHRs to technologies that will create “true interoperability.”

Enlightening conversations were happening among the crowded booths, hallways, and meeting rooms between organizations looking to ‘rip and replace’ their current EHR for a new one. While some organizations are struggling to unlock data across disparate systems, others are looking to upgrade their current system for one compatible with ICD-10, Meaningful Use, analytics solutions, or a combination of these. Still others are looking to replace systems they dislike for lack of functionality, vendor relationships, etc. In many cases, replacing an EHR is needed to ensure interoperability is at the very least viable. This buzz at HIMSS is a strong indicator that EHRs are still an important and essential part of health IT, and perhaps some organizations have not reached the tipping point.

In addition to the many challenges these organizations are facing—from data portability, an issue John Lynn wrote about in August 2012, to the cost of replacing the system—leaders are agonizing over the resistance they are facing from clinician end users. How can these organizations force clinicians to give up systems they once resisted, then embraced and worked so hard to adopt? How can leadership inspire the same level of engagement needed for adoption? The challenge is similar to transitioning from paper to an EHR, only more significant. Whereas the reasons for switching from paper were straightforward—patient safety, efficiency, interoperability, etc.—they are not so clear when switching applications.

Clinicians are also making harsher comparisons between applications—from every drop-down list, to icon, to keyboard shortcut. These comparisons are occurring at drastically different phases in the adoption lifecycle. Consider the example of an end user needing to document a progress note. In the old EHR, this user knew how to copy forward previous documentation, but in the new system she doesn’t know if this functionality even exists. Already the end user is viewing the new system as cumbersome and inefficient compared to the old application. Multiply this comparison by each of the various tasks she completes throughout her day, and the end user is strongly questioning her organization’s decision to make the change.

This highlights an important point: Swapping one EHR for another will take more planning, effort, and strategy than a first-ever implementation. The methods for achieving adoption are the same, but the degree to which they are employed is not. Leadership will not only have to re-engage end users and facilitate buy-in, they will have to address the loss of efficiency and optimization by replacing the old application.

Leadership should start by clearly outlining the reasons for change, a long-term strategy, as well frustrations end users can expect. They should establish a strong governance and support structure to ensure end users adhere to policies, procedures, and best practices for using the application. The organizations that will succeed will provide end users with role-based education complete with hands-on experience completing best practice workflows in the application. Education should include competency tests that assess end users’ ability to complete key components of their workflow. Additionally, organizations must capture and track performance measurements to ensure optimized use of the system and identify areas of need. And because adoption recedes after application upgrades and workflow enhancements, all efforts should be sustained and modified as needed.

While HIMSS15 brought to the stage a wealth of new ideas, solutions, and visions for the future of health IT, the struggle to adopt an EHR has not completely gone away. Many organizations are grappling with their current EHR and choosing to replace it in hopes of meeting the triple aim of improving care, costs, and population health. For these organizations to be prepared for true interoperability, they must overcome challenges unseen in paper to electronic implementations. And if done successfully, only then will our industry uniformly reach the tipping point, a point where we can begin to put buzzwords into practice.

Xerox is a sponsor of the Breakaway Thinking series of blog posts.

Emerging Health Apps Pose Major Security Risk

Posted on May 18, 2015 I Written By

Katherine Rourke is a healthcare journalist who has written about the industry for 30 years. Her work has appeared in all of the leading healthcare industry publications, and she's served as editor in chief of several healthcare B2B sites.

As new technologies like fitness bands, telemedicine and smartphone apps have become more important to healthcare, the issue of how to protect the privacy of the data they generate has become more important, too.

After all, all of these devices use the public Internet to broadcast data, at least at some point in the transmission. Typically, telemedicine involves a direct connection via an unsecured Internet connection with a remote server (Although, they are offering doing some sort of encryption of the data that’s being sent on the unsecured connection).  If they’re being used clinically, monitoring technologies such as fitness bands use hop from the band across wireless spectrum to a smartphone, which also uses the public Internet to communicate data to clinicians. Plus, using the public internet is just the pathway that leads to a myriad of ways that hackers could get access to this health data.

My hunch is that this exposure of data to potential thieves hasn’t generated a lot of discussion because the technology isn’t mature. And what’s more, few doctors actually work with wearables data or offer telemedicine services as a routine part of their practice.

But it won’t be long before these emerging channels for tracking and caring for patients become a standard part of medical practice.  For example, the use of wearable fitness bands is exploding, and middleware like Apple’s HealthKit is increasingly making it possible to collect and mine the data that they produce. (And the fact that Apple is working with Epic on HealthKit has lured a hefty percentage of the nation’s leading hospitals to give it a try.)

Telemedicine is growing at a monster pace as well.  One study from last year by Deloitte concluded that the market for virtual consults in 2014 would hit 70 million, and that the market for overall telemedical visits could climb to 300 million over time.

Given that the data generated by these technologies is medical, private and presumably protected by HIPAA, where’s the hue and cry over protecting this form of patient data?

After all, though a patient’s HIV or mental health status won’t be revealed by a health band’s activity status, telemedicine consults certainly can betray those concerns. And while a telemedicine consult won’t provide data on a patient’s current cardiovascular health, wearables can, and that data that might be of interest to payers or even life insurers.

I admit that when the data being broadcast isn’t clear text summaries of a patient’s condition, possibly with their personal identity, credit card and health plan information, it doesn’t seem as likely that patients’ well-being can be compromised by medical data theft.

But all you have to do is look at human nature to see the flaw in this logic. I’d argue that if medical information can be intercepted and stolen, someone can find a way to make money at it. It’d be a good idea to prepare for this eventuality before a patient’s privacy is betrayed.

Hospital EHR Adoption Chart

Posted on May 15, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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 always love a good chart and this one illustrates what those of us in the industry have know for a while. EHR incentive money absolutely increased EHR adoption in hospitals. I think it also did in ambulatory environments as well, but not quite to the extent of hospitals.

Can we just put the discussion of whether HITECH helped EHR adoption to rest? It increased EHR adoption.

To me that’s not the question that really matters. What really matters is whether the EHR incentive money has incented adoption of the right EHR software. It’s great that we’ve adopted EHR software, but have we just locked ourselves in to the wrong software for the next 5+ years? Or have we implemented a great EHR foundation that will prove to be extremely beneficial to healthcare for decades to come?

I look forward to a deep discussion in the comments.

Video Demonstration of End-to-End ICD-10 Testing

Posted on May 14, 2015 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 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’ve heard a lot of people suggest that an organization needed to do end-to-end ICD-10 testing in order to prepare for the switchover to ICD-10 on October 1, 2015 (we think). I came across this video demonstration of Qualitest doing an end-to-end test of ICD-10:

What do you think of the demo? Is this a valuable thing to do? Should this be done with every EHR and PM vendor and with every vendor that connects to that software?