Awell Health Developer Hub
Dev Hub
← Back to the Marketplace


Elation is a clinical-first EHR and patient engagement tool. It's designed for the craft of primary care medicine.
EHR Integrations

title: Elation

description: Elation is a cloud-based health record system designed for healthcare providers, clinics, and medical practices.


Elation is a cloud-based health record system designed for healthcare providers, clinics, and medical practices. It offers a range of features including patient scheduling, charting, e-prescribing, billing, and telemedicine. Overall, Elation is designed to streamline the workflow of medical practices, improve patient care, and increase efficiency.



The integration of webhooks with Elation presents unique challenges and considerations:

  • Non-Discriminative Triggers: Elation does not differentiate between the creation or update of a resource. Both actions will set off webhook with action saved, which might not provide enough discriminative information for some use cases.
  • Programmatic Setup: Elation webhooks can only be configured programmatically, as there's no dedicated user interface in Elation to set up webhooks. View this demo video for a step-by-step guide on how to set up your webhooks in Elation.
  • Limitation on user-triggered actions: Elation has a concept called "Preventing echo". This means that that any action carried out by the user affiliated with the API credentials that created the subscription doesn't trigger a webhook. You can read more about this behaviour here. If you are not receiving any webhooks from Elation after setting up your subscription, then this is the reason. A feasible workaround to the above limitation is creating a dedicated user not meant for human interactions but serves the sole purpose of facilitating M2M communication.

If you need help setting up your webhooks in Elation, reach out! We are happy to help you.

Extension settings

In order to use this extension you will need to provide the extension with the following settings:

  • Base URL / endpoint URL of the API
  • Authorization URL
  • Client ID for OAuth2 Password authentication
  • Client Secret for OAuth2 Password authentication
  • API Username for OAuth2 Password authentication
  • API Password for OAuth2 Password authentication

Not sure where you can find all of this information? Click here to have a look at Elation's Developer documentation.


The following actions are supported with Elation today:

Create Patient

This action creates a patient in Elation.

When creating a patient, you will have to specifiy the primary physician and caregiver practice ID:

  • Primary physician ID: you can retrieve this ID by using the Find Physicians API call, or by using the Find Physician action
  • Caregiver Practice ID: similar to the primary physician ID, you can find this ID by using the same API call or action

Get Patient

Using a patient identifier, retrieve a patient object from Elation.

Note that when retrieve the mobile phone number, we are tranforming the number to an international format. We apply a heuristic and assume all mobile numbers in Elation are in US national format so we prepend the number with the +1 country code. Having the number in international format unlocks more powerful functionality like sending text messages with 3rd party services like Twilio and MessageBird.

Update Patient

Update a patient in Elation using any fields available in create patient. We use Elation's PATCH method to apply partial modifications to a the patient resource (i.e. update only what is needed).

Create Appointment

Easily create a patient appointment in Elation.

Creating an appointment requires a few strings to be well-formulated:

  • Scheduled date must be a datetime string (ISO-8601). For example, January 1, 2023 at noon, Pacific Time (-8 hours) would be shown as such: 2023-01-01T12:00:00.000-08:00
  • Reason must not be free text. This value comes from the following list of appointment types (Follow-Up, Office Visit, Physical Exam, etc.): Appointment types
  • Patient is the patient ID.
  • Physician is the physician ID (see Find Physician)
  • Practice is the practice ID (again, see Find Physician)

You can also include a duration (default to 15 minutes, or whatever has been set in your EHR)

Get Appointment

Retrieve appointment details using an appointment ID.

Create Non-Visit Note

The non-visit note is a special kind of note that, as the name suggests, is not associated with a visit. These notes, in their simplest form, provide a chronological account of information about the patient.

Additional documentation for some of the action fields:

  1. Category: The default category is "Problem" but you can choose any of "Past", "Family", "Social", "Instr", "PE", "ROS", "Med", "Data", "Assessment", "Test", "Tx", "Narrative", "Followup", "Reason", "Plan", "Objective", "Hpi", "Allergies", "Habits", "Assessplan", "Consultant", "Attending", "Dateprocedure", "Surgical", "Orders", "Referenced", "Procedure".
  2. Chart and document date automatically get set to the current date, i.e. the date when the action is orchestrated.

Delete Non-Visit Note

Deletes the non-visit note identified by an ID.

Get Non-Visit Note

Retrieve the details of a non-visit note identified by an ID.

Get physician

Using a physician identifier, retrieve a physician object from Elation.

Find physicians

Search a physician based on a set of parameters. The ID of the physician matching the search parameters will be returned. To retrieve the details of the physician, you can use the the "Get physician" action.

Note that this action can only support finding one physician so if your search criteria match multiple physicians the action will throw an error.

Custom Actions
Get Patient
Create Patient
Update Patient
Create Appointment
Get Appointment
Find Appointment
Get Physician
Find Physician
Create Non-Visit Note
Update Non-Visit Note
Get Non-Visit Note
Delete Non-Visit Note
Post letter
Create lab order

Other extensions