Building a Usable Healthcare API

I’ve long believed that a rock solid API is going to be required by healthcare IT software companies and EHR vendors in particular. If we want hospitals and doctors to be able to accomplish everything they need to accomplish, we need APIs to connect providers to services that will better serve the patients. EHR vendors aren’t going to do everything. With this in mind, we thought that it was time to start a discussion on how to build a usable healthcare API.

On Thursday, September 8th at 3:30 PM ET (12:30 PM PT), join us LIVE in our latest Healthcare Scene interview, as we discuss healthcare APIs with the following experts:

2016 September - Building a Usable Healthcare API-Headshots
There are a lot of people who talk generally about an API, but very few that have executed it well in healthcare. CareCloud and ManaHealth are two healthcare companies that are trying to implement a health care API in the right way, so we’re excited to sit down with them to talk about their experience building healthcare APIs.

If you’ve never watched one of our live video interviews, you can watch it live on this YouTube page (includes Live Chat room as well) or just visit this post on the day of the event and watch the video embedded below:

We look forward to shedding more light on what it takes to build a high quality, usable healthcare API.

Be sure to Subscribe to Healthcare Scene on YouTube to be updated on our future interviews or watch our archive of past Healthcare Scene Interviews.

About the author

John Lynn

John Lynn

John Lynn is the Founder of the HealthcareScene.com, a network of leading Healthcare IT resources. The flagship blog, Healthcare IT Today, contains over 13,000 articles with over half of the articles written by John. These EMR and Healthcare IT related articles have been viewed over 20 million times.

John manages Healthcare IT Central, the leading career Health IT job board. He also organizes the first of its kind conference and community focused on healthcare marketing, Healthcare and IT Marketing Conference, and a healthcare IT conference, EXPO.health, focused on practical healthcare IT innovation. John is an advisor to multiple healthcare IT companies. John is highly involved in social media, and in addition to his blogs can be found on Twitter: @techguy.

2 Comments

  • Good topic. The question is the API the critical factor. There are well established APIs (SMART) to allow add on features to existing EHRS, there are established APIs (FHIR) to facilitate data exchange. Not sure creating another API will change anything. It is not a problem of skill, it is a problem of will. I am a fan of establishing a new law that requires any health data to be shared to a public repository or a public block chain (ultimately managed by the patient or their representative) prior to issuing payment for such services. Use what ever API you choose but once the data is uncoupled from the system/vendor/org it can be used to improve and advance health care.

Click here to post a comment
   

Categories