Elation Health

Connecting Elation

You will need to contact Elation to access credentials (a “Client ID” and “Client Secret”) which can be used to connect Tellescope to Elation. You can get Sandbox (Test) credentials or Production (Real) credentials. When making the connection in Tellescope on the Integrations page, you will be able to select Production or Sandbox when providing your access credentials. You can initially provide a Sandbox connection to test things out. From there, you can remove the integration and switch to Production credentials.

Scope of Integration

Tellescope updates Elation when changes are made to patients and calendar events in Tellescope. If you have custom entity types (non-patients), these records will not sync with Elation.

When you provide the Elation credentials to Tellescope, we set up “webhooks” automatically, so that Tellescope can be notified of every change to patients and appointments that happen in Elation. We create or update existing patients and calendar events in Tellescope accordingly.

Patient Matching

💡 The remaining section goes into low-level technical details.

At a high level, we match patients by the following:

• [First Name + Last Name]

                AND one of the following:

• • [email address]

OR

• • [phone number]

OR

• • [date of birth] 

From there, a patient in Tellescope will store the Elation ID, so that future updates can be made more easily.

A patient created in Elation and pushed to Tellescope will have the source as "Elation" or "Elation Sandbox" and the externalId as the Elation Patient ID. Any enduser in Tellescope (created in Elation or not) which is mapped to an Elation patient has a "references" field. This is a list of values that look like { "type": "Elation", "id": "elation_patient_id_here" } or { "type": "Elation Sandbox", "id": "elation_patient_id_here" }

When a new patient is created (or an existing patient is updated in Tellescope)

• We check if the patient in Tellescope is already mapped to an existing Elation patient by
  • Seeing if the enduser "source" is "Elation" or "Elation Sandbox" and then using the enduser "externalId"
  • Searching the enduser "references" field for an item with the "type" "Elation" or "Elation Sandbox" and taking that "id"
  • Looking up a patient in Elation via API by matching against first name, last name, and one of [email, phone or date of birth]
    • If we find one here, we will push { "type" "Elation" | "Elation Sandbox", id: "elation_id_here" } to the enduser "references" field for future syncs
• If we find an elationId, we’ll PATCH Elation with the corresponding patient updates from Tellescope
• If we don’t find an elationId, we’ll create a new Patient in Elation, and then store the resulting patient id as part of the enduser’s "references" field

We’re currently syncing first_name, last_name, dob, sex, email, phone, and address details. We are now also able to set pronouns, gender identity, insurance, and insurance card images.

When a new patient is created (or an existing patient is updated in Elation)

• We get a webhook with the patient data
• We check if a Tellescope patient exists with this id, using the source/externalId and references fields
• We check if a Tellescope patient has the same fname/lname/dob or email or phone
• If we don’t find a match, we’ll insert a new Enduser with the source/externalId and references fields, alongside the Elation details
• If we do find a match, we’ll update that existing patient, and make sure that the elation id is included in the references field

Sync Form Responses

• After creating a form or internal note in Tellescope click the Integrations Tab on the form editor
• Toggle on Sync to Elation as Non-Visit Note
• Submissions for the specific form or internal note will then sync to Elation as a Non-Visit Note

Mapping Form Responses to Elation Profile

You can map form questions and answers to the History, Allergy, and Profile Note fields in Elation. 

• To map to Allergies, select the box Sync as Allergy to Elation
• To map to the Profile Note, select the box Append to Elation Profile Note; you can also define a note prefix to identify the line item within the profile note
  • The Elation Profile Note is limited to 500 characters, so we only pass answers, not questions

• To map to the patient's medical history (past, family, etc.), select the history type from the dropdown
  • Both the questions and answers will be passed to the History fields