Integrating with other apps

How to integrate with other health IT solutions

Schuyler Welch avatar
Written by Schuyler Welch
Updated over a week ago

It is easy to integrate with other apps. Below is a list of other possible types of integration:

  • Patient Identifier

  • Auto Check-In

  • Single Sign On

  • Just In Time Provisioning

  • Launch EHR

  • Session Webhooks

Patient Identifier

This feature allows you to associate a call record with a patient ID in your system.

You can add ?pid= to the end of your patient invite link to attach a patient identifier (usually hashed) that only your system can recognize. When a patient clicks this room link, the unique identifier will be stored in meeting history records. This unique identifier can only be retrieved through the meeting history API.

For example: For, “123456” will be stored.

Auto Check-In

To improve accessibility, or to reduce redundancy between systems so that patients aren't required to type in their name upon check-in after they have left a system where they have already been identified (for example, a patient portal to, you may find it useful to automatically check in a patient. Adding this feature to the end of your invite link lets the patient check in with one click.

To enable this capability, add these two attributes to the end of your waiting room link:


  • Instead of patientName in the URL, you’ll put the patient's name.

  • You can add %20 in between the first and last name to make a space. Adding an actual space to the URL will not work.

  • You can combine Auto Check-In and Patient Identifier by adding &pid=123456 to the end of the above example.

The final result will look similar this:

When a patient clicks on this link, they will immediately appear in the provider's patient queue, without the need to enter their name manually.

Single Sign On

SSO is only available on the Clinic and Enterprise subscriptions. There is a one time $250 setup fee. You can reach out to for more information.

Just In Time Provisioning

JIT can be used with SSO. When your users log in for the first time, their account and license will be added automatically. You can reach out to for more information.

Launch EHR

If you have a web-based EHR application, you can get beta access to launch the patient's profile. There are two main components to make this work:

  1. You need to request beta access for emrUrl to be turned on.

  2. Each link sent to patients needs to have the pid (explained above) included. You need a system that can pair the provider's room link to the patient's pid and send that link to the patient.

Once we give you beta access, we need your EHRs web link. This would be something like The next part would be setting up the pid. Each patient should have a unique identifier to their EHR profile. It would be like “A58gR84S”

For the next part to work a scheduler can help create the invites with the pid. You just have to pair the provider's room link with the pid.

When the patient checks in, you will see the EHR button. This button will combine the EHR web link you gave us with the pid the patient checked in with and will launch their profile.

As mentioned above, with the meeting history API you can export the history with the pid and see when that specific patient had sessions.

Session Webhooks

With webhooks you can get session data when a patient checks in, call starts and call ends. This can be useful for setting up additional workflows. For example, if you receive a webhook that a patient checked in but it's been 10 minutes and no corresponding call start webhook, this could trigger alerts on your side to notify the team.

You can reach out to for more API information or requests.

If you have any questions, please contact our support team.

Did this answer your question?