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!!

Need Point of Care EMR Documentation to Meet Future EMR Documentation Requirements

Posted on April 12, 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.

As part of my ongoing writing about what people are starting to call the EHR Backlash, I started to think about the shifting tides of EMR documentation. One of the strongest parts of the EHR backlash from doctors surrounds the convoluted documentation that an EMR creates. There is no end to the doctors who are tired of getting a stack of EMR documentation where 2 lines in the middle mean anything to them.

Related to this is the physician backlash to “having to do SOOOO many clicks.” (emphasis theirs) I still love the analogy of EHR clicks compared to playing a piano, but unfortunately EHR vendors haven’t done a good job solving the two things described in that article: fast predictable response and training.

With so many doctors dissatisfied with all the clicking, I predict we’re going to see a shift of documentation requirements that are going to need a full keyboard as many doctors do away with the point and click craziness that makes up many doctors lives. Sure, transcription and voice recognition can play a role for many doctors and scribes or similar documentation methods will have their place, but I don’t see them taking over the documentation. The next generation of doctors type quickly and won’t have any problem typing their notes just like I don’t have any issue typing this blog post.

As I think about the need for the keyboard, it makes me think about the various point of care computing options out there. I really don’t see a virtual keyboard on a tablet ever becoming a regular typing instrument. At CES I saw a projected keyboard screen that was pretty cool, but still had a lot of development to go. This makes sense why the COWs that I saw demoed at HIMSS are so popular and likely will be for a long time to come.

Even if you subscribe to the scribe or other data input method, I still think most of that documentation is going to need to be available at the point of care. I’ve seen first hand the difference of having a full keyboard documentation tool in the room with you versus charting in some other location. There’s just so much efficiency lost when you’re not able to document in the EMR at the point of care.

I expect that as EMR documentation options change, the need to have EMR documentation at the point of care is going to become even more important.

FitBit API and Other Healthcare APIs

Posted on 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 long been a big fan of APIs in technology. It’s really powerful to open up your software so that outside developers can create really cool applications on top of your software. Think where Twitter would be today if it weren’t for their API. Most of the best Twitter clients were not built by Twitter. That’s just one simple example.

With that in mind, I was interested to see how the FitBit API was doing in its development. It’s been around for a couple years, so my hope was that I’d find a mature API with some good documentation and most importantly a strong developer community around it.

It seems like Fitbit has made it really easy to sign up and start using their API. That’s a good thing. Far too many in healthcare have an API, but they put up these enormous barriers for developers to start using it. When you’re dealing with PHI, you do have to take a serious approach to access, but the intent should be to create as many of those trusted API relationships as possible.

Next, I took a look at the Fitbit API documentation. Most of you won’t want to look at the API documentation since you’re not a developer. However, if you look at this Fitbit API Explorer page, you’ll get a good view of what functions are possible with the Fitbit API. They have a set of Ruby, PHP, and .Net Client libraries which is great (Although they’re not directly developed or supported by Fitbit). I do wish they had a really good sample app that uses their API. I’ve found a great sample application is incredibly valuable to developers that want to start using that API.

Finally, I took a look at the Fitbit discussion group. I was a little disappointed that there wasn’t more activity here. It does seem that the questions in the group do get eventually answered, but I’d have like to see a bigger Fitbit presence in the forum. The most active threads are the feature requests and announcements threads which isn’t too much of a surprise. There were only 15-20 active threads in April.

All in all, it looks like Fitbit has created a pretty solid API. I could see myself using it for a future project.

I’m interested to know what other APIs you’ve found in healthcare. What other healthcare companies are putting out really good APIs? Have you used the Fitbit API? What was your experience? Is it reliable? What are the best apps in healthcare that leverage someone’s API?