Overview

Many customers will leverage Tellescope's off-the-shelf portal, Journeys, and communications channels to build their patient experience. Such an approach requires no custom code.

For customers who want to customize or extend Tellescope's patient-facing capabilities, this article provides an overview of 3 main approaches. 

1. API Usage

Every model in Tellescope's API is publicly documented. All of the endpoints used by Tellescope are available for your usage as well.

The Enduser (patient) model also offers endpoints for managing authentication. An authToken generated for an Enduser can then be used on the client-side to perform future API requests (authenticated as the patient). This means you should not need extensive backend middleware / proxying of the Tellescope API to build your patient experience.

2. TypeScript SDK / React Components

Our TypeScript SDK comes with authentication management and typed function calls to our API. For those familiar with TypeScript, the type suggestions provided by the SDK can be a very helpful way of learning our API.

For those developing React (web or native) applications, we offer React Components for authentication, state management, and common UI elements like Chat.

3. Portal Self-Hosting

Our Portal is a static React web application build on top of our API and React libraries. We are able to license the current source code for our portal to customers. It can be easily built and hosted as a static website on your preferred platform. 

The Portal Navigation is already wired to handle authenticated ("magic") links generated as part of Tellescope communications. E.g. links to fill out a form, book an appointment, finish an incomplete form, etc. 

This is a good option for customers who want more control over the look-and-feel of the portal, or who want to extend it with custom pages, but who don't want to build much from scratch.