Telehealth patient identity

The job

A remote appointment happens without a reception desk. The clinic or the telehealth service wants to know that the person who booked is the person who connects, before the appointment goes ahead.

The flow

1. Booking. When the appointment is booked, your system creates a session and sends the patient the link.
2. Document. The patient photographs an identity document. See document verification.
3. Selfie and face match. The selfie is matched to the document portrait. See face verification.
4. Liveness. The patient moves the face through two ovals, a challenge that helps detect presentation attacks. See liveness.
5. Before the call. Your system reads the status. When the session is complete and successful, it opens the appointment. Otherwise it holds the appointment for a person to look at.

Keeping personal data out of callbacks

If your appointment system does not need names or images in the callback, set the callback to leave them out. The callback then carries the session identifier, and your system fetches the result by that identifier. Retrieving and storing the result are controlled separately, with your own access rules and with the retention and erasure settings. See data controls and webhooks.

Scenario setup

In the scenario editor you choose the documents and countries you accept, the steps, and the callback and retention settings.

What your system receives

A session status and a list of results for each step. See session statuses.

Next

Try the interactive tour, or talk to us about your appointment flow.