An application programing interface (API) is a set of standards that govern how software applications talk to each other. APIs play an increasingly important role in healthcare data exchange, whether for data analytics, medical research, or creating innovate ways to access the EHR.
What are APIs and why do they matter for healthcare? This article offers a basic explanation of APIs for physicians and other healthcare professionals who don’t have a technical computing background.
What are APIs?
APIs show up anywhere two software components interact, whether in an operating system or on the web. Have you cut and pasted text between applications on your laptop recently? Maybe you found a restaurant using Yelp’s map interface? Or searched itineraries on Google Flights?
That’s right, in each case you were relying on APIs to structure how those applications interacted with other websites and softwares. APIs facilitate the incredible connectivity we’ve come to expect in the digital era.
An easy way to think about APIs is as a way to request information from a system and return a response. A popular analogy explains the API as a waiter at your restaurant. You have a menu of meal options and a kitchen designed to fulfill your request. But you need a messenger to deliver your request and return the response. An API is like the waiter who takes your order, delivers it to the kitchen and brings back what you asked for.
If you’re still confused about APIs, this 3-minute video from MuleSoft is worth you’re time. It’s one of the simplest explanations of APIs out there.
Why do APIs matter for healthcare?
In the era of digital health, one of the biggest challenges facing the industry is interoperability. APIs have emerged as the most popular solution for managing the flow of information between a healthcare organization’s internal applications, EHRs and other data exchange tools.
As Geisinger Health’s Chief Data Offcer Dr. Nicholas Marko told HealthITAnalytics, “There’s no such thing as one set of data that gives you everything you need in one single format. There will always be information coming from a number of different places, and there will always be a need to work with systems that handle that.”
“There’s no such thing as one set of data that gives you everything you need in one single format.”
APIs show up anywhere there’s a need to communicate data between systems. For example, researchers accessing a population health database might rely on an API to pull real-time data and analytics from various sources. APIs also make it easier to grant patients access to their medical records online.
As with other industries, APIs are critical for health IT development. One way to think about APIs is that they make everything more efficient. APIs serve as a sort of standardized gateway for healthcare data, which helps:
- Decrease software development time.
- Save storage space on endpoint devices.
- Overcome differences in standards or programming languages used to create the data that lives at either end of the bridge.
Basically, APIs make it easier for people building healthcare software to access data faster while reducing duplication or security errors.
The rise of EHR app stores
As a physician, you’ve likely used an app that connects in some way to patient data form your EHR. Many of the big EHR vendors have open APIs that allow third-party software developers to create apps that access their data. These apps facilitate functions like:
- Education and training
- Decisions support
- Inter-organizational workflow
- Data management
- Clinician-patient communication
- Clinician-clinician communication
- Much more
The largest EHR app store is the athenahealth marketplace, which allows providers and health systems to shop for apps and services that integrate with athenahealth. The marketplace emerged from More Disruption Please (MDP) – athenahealth’s 2011 response to calls for more disruptive innovation in health care technology.
Allscripts, Cerner, and Epic now have app stores similar to athenahealth’s. As of 2019, the leading EHRs have all enabled some API integration.
While you use software that relies on APIs daily, most physicians don’t need to understand how APIs work or how they are evolving in healthcare.
But if you’re curious about the future of health IT – or just tired of not understanding the technical jargon like HL7 and FHIR – the following resources are a good place to start for further reading.
“Why Application Programming Interfaces Are Key for Healthcare” (Feature from HITinfrastrucutre.com)
“APIs in healthcare: what healthcare providers should now about APIs” (Whitepaper from Corepoint Health)
“Sate of the Healthcare API Economy” (HIMSS19 Session 217)