Healthcare EHR API Q&A

A developer reached out to ask a few questions about our healthcare API, this is the email –

Here are the answers below!

1. The inclusion of the YouTube Video and the steps are a great help.

Thank you! We plan on making more videos and adding more documentation over the next several months. Be sure to join our Programmer Google Group for updates.

2. It appears that there are only 2 apps (AppVisit and BetterDoctor) are using the API. Its not clear how many apps actually use the API

We have several hundred of developers, doctors, medical billing companies and other EHRs building on the API.

Some of these partners want to announce and work together, we can list you here if you wanted to be a public partner (

There are other partners leveraging the API for private use, depending on what they are looking to do (e.g. if they wanted to import data into other reporting software.)

3. Are you working on additional SDKs?

Currently we have our API for medical scheduling, the EHR and medical billing platform, drchrono. We are looking into opening things up in the future to include another API specifically for patient facing apps that want to leverage onpatient.

4. The API currently is a very limited set. I am looking to develop a patient focused app. I understand that there are security implications and its not trivial to ensure unintended consequences. Are there any plans to expose a limited view of the patient chart? Can I get a least of meds? 

When the API is enabled for a partner, the API is turned on in sandbox mode initially until approved preventing security issues.

The API is ever evolving , so as you build you will see its limitations, but overtime is it becoming more and more robust. For example, one API partner wanted to have access to blood pressure stats, we just enabled blood pressure reading and writing of stats for them. We plan on opening up API access of med lists as well.

5. The redirect URL is mandatory. However, if I create a new mobile app, why do I need the URL?

This is one option currently available – You would open the authorize page in Safari, then after the user signs in then we would resides to that URL with the custom scheme which loads your app, you can use this tutorial on how to do that




<td align="left" width="65%">
  <em>Article by <a title="Daniel Kivatinos" href="" target="_blank" rel="noopener noreferrer">Daniel Kivatinos</a>, COO and cofounder, <a href="" target="_blank" rel="noopener noreferrer">drchrono</a></em><br /> Daniel drives direction, brand vision, and business strategy for drchrono. Daniel’s focus has been in the technology space since 2001, as a software engineer and entrepreneur. Daniel holds an M.S. in Computer Science and a B.S. in Computer Science & Psychology from Stony Brook University.