Healthie offers infrastructure for next generation digital health organizations that provide virtual-first care. Healthie’s API-first and fully brandable suite of solutions (Scheduling, EMR, Client Engagement) enables healthcare builders to launch and scale best-in-class experiences for their members. Healthie also offers a built-in marketplace of business and clinical integrations used by our organizations.
To learn more, visit www.gethealthie.com.
With this extension, organizations are able to build clinical workflows in Awell’s low-code platform and easily integrate them into Healthie. By doing so, Healthie’s customers can automate routine clinical tasks, synchronize data between systems and drive seamless coordination between care team and patients.
By combining Healthie’s web and mobile platform with our clinical workflows, clinicians will be able to provide the right care, at the right time for the right patient.
In order to set up this extension, you will need to provide a Healthie API key and Api url. You can obtain an API key via the Healthie portal (
Settings > Developer > API keys). You can obtain API url in the DOCUMENTATION in
Please note that the extension automatically prefixes the API key with
Basic so please provide your raw API key without
Basic in front.
Sends a chat message to a patient in name of the provided provider ID. Will create a new conversation if no active conversation between patient and provider exists or sends a message in an existing conversation if there is an active conversation between the two.
Creates a new patient according to the passed fields. After completion the
healthiePatientId will be exposed as a data point in the care flow.
Updates a specific patient (defined by the provided
id) according to the passed fields.
Adds a tag (existing one, identified by an
id) to a patient. Although the Healthie API call allows assigning multiple tags per API call, for simplicity of the logic this action can only take one tag as input. Assigning multiple tags is possible by adding multiple actions.
Removes a tag (identified by an
id) from a patient.
Creates a charting note with the provided
Prerequisites and set-up:
form_id exists in Healthie.
form_id is a charting form (click "Convert to charting form" in the form options).
textarea (long text answer). The action will write the content of the charting note in the first question of that type it finds in the form.
Send a form completion request to the patient. You will need the Healthie patient ID and the ID of the form you would like the patient to complete.
Although the Healthie API call allows sending form completion requests to multiple users per API call (see recipient_ids in their docs), we decided that every action only sends one form completion request. This heavily simplifies the logic and better fits our domain model (1-to-1 relationship between patient and pathway). If a user would like to send multiple form completion requests, they you can just add multiple actions.
Archives a patient with a given
Creates a location. ID of the created location is stored as
locationId data point.
Closes chat conversation with a given
id as a provider with the given
Deletes an appointment with a given
Cancels an appointment with a given
Retrieve the most recent metric entry from a given
Create a metric entry for a patient in Healthie. The category of the metric is the literal name of the metric in Healthie. So if you have a metric in Healthie called "Weight", you should use "Weight" as the category.
Checks that a patient has an active tag with given
Checks that a patient has active scheduled appointment with given