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!

A List of Key Insights for EHR Data Conversion

Posted on December 17, 2013 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.

Healthcare Scene sat down with Sean West, VP of Data Conversion at HealthPort, to discuss EHR data conversion. EHR data conversion is quickly becoming a hot topic for many organizations that rushed their initial EHR selection and implementation. In our video discussion embedded below, Sean West offers a number of key insights including the following:

  • Convert the Data Close to the EHR Conversion
  • Ensure You Have Enough Time to Make the Conversion
  • Consider How Much Data Needs to Be Converted
  • Look at the Impact on Performance of Converting All EHR Data
  • Evaluate Your Legacy EHR Vendors Willingness to Work with You on Data Conversion

Check out the following video for all the details:

We also asked Sean West about when an organization would want to consider a vendor neutral archive for their EHR. While the vendor neutral archive is incredibly popular with PACS systems, we’re just now starting to see the idea crop up with EHR data. In the following video, Sean West provides some good insight into when an organization might want to consider a vendor neutral archive for their EHR data.

A Private HIE is a Vendor Neutral Archive Applied to EHR

Posted on June 17, 2013 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 been really fascinated by the work many hospital systems are doing to create a private HIE in their organization. As I wrote, I think that private HIE could lead to a nationwide HIE. It’s still a bit of a long shot, but I think it has more promise than the other HIE initiatives I’ve seen in action.

Along with my interest in private HIEs, I’ve also been fascinated by the switch to Vendor Neutral Archives (VNA) in the radiology space. In a VNA, you can store any medical image in the archive and it doesn’t matter what device you use to capture or view the image. Think about the flexibility that this provides. You’re no longer locked into a certain piece of imaging equipment or to a certain viewing application. Instead, you can switch as needed.

As I consider these two areas, it seems that a private HIE is the first step to having a vendor neutral archive. In fact, I’m not sure why more people haven’t applied the principles of vendor neutral archives to the EHR world. I imagine the challenge is in the complexity of the data. Sure, DICOM isn’t a simple piece of data either, but at least there are some DICOM standards that most medical imaging companies follow. The same can’t be said in the EHR world.

The problem now is that the term HIE has so much failure associated with it. I imagine that’s why we moved from RHIO to HIE as well. However, I think that the change from creating an HIE to a vendor neutral archive for EHR data would be a dramatic shift in thinking. This could be an important decision for a large hospital system. Instead of just trying to share data from EHR to EHR, what if they created a vendor neutral archive of all their EHR data such that your future EHR was built around that VNA instead of around a specific piece of software. I’m not sure there are many hospital CIOs brave enough to look this far out.

What do you think of the VNA concept applied to EHR? Is a private HIE the start of a VNA for EHR?