Twistle Releases
This is your go-to place for the latest updates and release notes about Twistle.
You’ll find the most recent release notes below. For earlier versions, please see the archive by year.
Current releases
Twistle - May 2026
New Features and Enhancements
Allow Teams to display point of contact details
A Twistle message to a patient is usually sent on behalf of a Care Team. If a patient has questions about that message (e.g., how to fill in a particular form), there was previously no easy way to contact their Care Team. Care Teams now have the option of including point of contact information to share with the patient. Both the label and contact details are configurable. This information is displayed in the Contacts section of the web application.
Display all submissions for a Form
A patient form can have multiple versions. Users managing workflows previously could only see submissions for a specific version. Now, all submissions across all versions can be viewed on a single page, providing better visibility.
Enforce mandatory capture of patient ID for an Enterprise
When a patient is provisioned, a unique patient ID (e.g., MRN from the EHR) can be assigned. It is now possible to make this field mandatory for a specific Enterprise.
Display additional message when a caregiver needs to verify multiple patients
A caregiver may be assigned to receive messages on behalf of a patient. Upon logging in, caregivers must verify the patient’s date of birth to protect data. If a caregiver is linked to multiple patients, they must verify each patient whenever they access their account.
Allow caregiver numbers to be removed via the API
The wipe_test_phone_numbers API endpoint previously allowed removal of numbers from patient records only. This has now been extended to support removal of caregiver phone numbers as well.
Allow external outbound data API to be utilized at a workflow level
Previously, external_outbound_data_api hooks could only be configured at the organization level, leading to unnecessary data volume. It is now possible to configure these at the workflow level, improving efficiency and data control.
Include additional medication code field in the Xealth integration
An additional field has been introduced in the Xealth integration, enabling the use of medication codes in standard data mappings.
Fixes
- Ensure a patient only has one active number: Fixed edge cases where multiple SMS numbers could become active.
- Ensure workflow steps are correctly displayed: Resolved issue where empty workflow steps appeared in some scenarios.
- Caregiver matching validation: Added name validation when matching caregivers to avoid incorrect assignments.
- Workflow execution efficiency: Improved performance in how workflow executions are stored.
- Eligibility updates: Users can now be updated from eligible to ineligible to receive messages.
Twistle - April 2026
New Features and Enhancements
Display workflow steps for all workflow versions
You can now select a specific workflow version and view the complete set of steps for that version.
Improved loading time for patient forms
Forms with conditional questions now load significantly faster.
Add support for active medications via the Xealth integration
Active medications data is now available through the Xealth integration.
Improved SMS delivery status sharing with external systems
SMS delivery status updates can now be shared more reliably with external systems.
Fixes
- Hide dependent conditional fields when initial responses change: Conditional fields now correctly disappear.
- Ensure supported languages are set: Fix applied for Xealth API-provisioned patients.