The TheraDriver and Aloha integration allows organizations to manage schedules and schedule changes in TheraDriver while sending session activity into Aloha.
With this integration, organizations can create recurring schedules for clients and staff, manage daily schedule changes in TheraDriver, and have session updates reflected in Aloha.
Session activity sent from TheraDriver to Aloha includes:
TheraDriver should
be used as the source of truth for scheduling once the integration is live.
Sync Direction
Session data flows in one direction:
TheraDriver → Aloha → Motivity / Hi Rasmus
There is no bidirectional session sync between TheraDriver and Aloha.
This means:
TheraDriver syncs the following session activity into Aloha:
During onboarding, TheraDriver manages the initial setup of the integration.
The onboarding process includes:
Recurring Schedule Setup
If recurring schedules already exist in Aloha, TheraDriver can download those schedules from Aloha and upload them into TheraDriver.
If schedules are not recurring in Aloha, TheraDriver can upload schedules into TheraDriver using a spreadsheet provided by the organization.
Other Session Types
The organization is responsible for managing other recurring sessions in TheraDriver, such as:
After onboarding is complete, the organization is responsible for maintaining client and staff information in both systems.
Clients and staff are not automatically synced into TheraDriver when they are added, edited, or disabled in Aloha.
Organizations should manage all schedule updates in TheraDriver, including:
Organizations using TheraDriver may have access to:
Feature availability may depend on the organization’s TheraDriver setup.
Client and Staff EHR IDs
Client and staff profiles in TheraDriver must include the correct Aloha client or staff ID in the EHR ID field.
This allows TheraDriver to match the client or staff member to the corresponding profile in Aloha.
If the EHR ID is missing or incorrect, sessions may fail to sync into Aloha.
Code Mapping
The TheraDriver team must map billable and non-billable codes using the appropriate Aloha APPT_TYPE value.
If appointment types are not mapped correctly, sessions may fail to write into Aloha.
Cancellation Reason Mapping
TheraDriver must also map cancellation reasons between TheraDriver and Aloha.
At this time, session status is only mapped when it is tied to a cancellation reason in TheraDriver.
Sessions may fail to write from TheraDriver into Aloha for several reasons.
Common causes include:
|
Issue |
What to Check |
|
Expired client authorization |
Confirm the client has an active authorization in Aloha. |
|
Missing EHR ID |
Confirm the client and staff profiles in TheraDriver include the correct Aloha ID. |
|
Incorrect EHR ID |
Confirm the EHR ID matches the correct Aloha client or staff profile. |
|
Staff missing required qualification |
Confirm the staff member has the required qualifications in Aloha. |
|
Incorrect or unmapped appointment type |
Confirm the code is mapped to the correct Aloha APPT_TYPE value. |
|
Cancellation reason not mapped |
Confirm cancellation reasons are mapped between TheraDriver and Aloha. |
Failed sessions can be retried. TheraDriver can assist with troubleshooting failed syncs.