Practice Vine Enables API for Any EHR

Posted on October 1, 2013 I Written By

John Lynn is the Founder of the 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 and 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 was recently introduced to a new company that is working to take traditional client server based EMR software and connecting them to the cloud. The company is called PracticeVine. I think they have an interesting approach to consider.

While many people love to proclaim the future of cloud based EHR, they underestimate the install base of client server based EMR and some of the advantages of a locally hosted EHR. PracticeVine provides a way for client server based EMR to have some cloud based functionality. Their first implementation is a Patient Forms tool for MacPractice EHR.

When you dig into a PracticeVine implementation, you see that if they’re successful, they’re essentially building a powerful API to an EHR software. With MacPractice they started with forms, but over time I could see PracticeVine building out other features which continue to expand the API like functionality that they need to provide cloud based functionality to client server based EHR software. Could PracticeVine become the ultimate EHR API provider?

Obviously, that’s an ambitious goal and far more than what they’re trying to chew off now. However, it’s really interesting to think about what the ultimate EHR API provider would look like. It’s even more exciting to think about what could be possible if we had deep EHR APIs for all the EHR vendors.

The real challenge that PracticeVine faces is resistance from EHR vendors to let them build this out. It’s not like most EHR vendors are even thinking about an API for their EHR. In fact, most of them can’t see past meaningful use stage 2. I’ll be interested to see where PracticeVine takes this. I really hope they’re successful at getting EHR vendors to interface with them.