Change Log 2025

Created by Enda Madden, Modified on Thu, 11 Dec at 4:24 PM by Enda Madden

We continue to welcome your input and are always available for a catch-up call to discuss these updates or any other aspects of OpenFIT, including your implementation of Feedback-Informed Treatment.


Schedule a Meeting


Customer Configuration – Company-specific Payor and Treatment Setting Values

We have added support for tenant-specific dropdown values for payor and treatment setting fields (for example, CareOregon). This allows us to configure organisation-specific options without affecting other customers.


Feature – CSRS Available for Group Cases

The Child Session Rating Scale (CSRS) can now be used with Group Cases. This brings Group case workflows into line with individual cases for organisations working with children and families.


Bug Fix – Reliable Session Updates

We resolved an issue where duplicate schedules could prevent sessions from updating correctly, which in turn affected reports and follow-up scheduling. Session updates are now applied reliably even when schedules have been changed multiple times.


Data Quality – Country Field Trimming for Phone Codes

We fixed an issue where extra spaces in the Country field could interfere with default country codes when entering phone numbers. The system now trims values to ensure consistent dialling code behaviour.


Reporting – Clearer Age Bands for Adolescents, Adults and Children

Age-based reporting has been refined so that adolescents, adults and children are categorised in a clearer and more consistent way (for example, < 18 is treated as adolescence). This helps align OpenFIT reports with common clinical and service definitions.


Administration – Local Admins Can See Deleted Users

Local Administrators can now view deleted users where appropriate. This makes it easier to troubleshoot access issues, audit historical activity and ensure that user management is aligned with local governance processes.


Branding – Consistent Use of “OpenFIT”

We standardised the product name to “OpenFIT” across the application to ensure consistent branding and avoid confusion caused by mixed capitalisation.


Reporting – Power BI Embedded Support

OpenFIT now supports embedding Power BI content directly within the application for eligible customers. This enables richer, interactive analytics experiences without requiring users to switch between systems.


Surveys – GAD-7 Translation Fallback

For the GAD-7 questionnaire, if a translation is not yet available in a given language, OpenFIT now falls back to English in a controlled way instead of displaying blank or inconsistent text. This ensures that the measure remains usable while translations are completed.


API – Status Endpoints Accept External Keys

The GetOrsStatus and GetSrsStatus API endpoints now accept client and episode external keys in addition to internal IDs. This simplifies integrations where the external system stores its own identifiers.


API – Incremental Data Pull Support

Several OpenFIT API GET endpoints have been extended to support incremental data pulls. Integrations can now request only recently changed records, reducing load and making scheduled synchronisations more efficient.


Email Infrastructure – Region-specific Azure Communication Services

We now use separate Azure Communication Services (ACS) resources for email in AU, EU and CA. This improves deliverability and supports regional data-handling and governance requirements.


Localisation – Additional Languages

New languages have been added to OpenFIT for both the user interface and, where available, outcome measures. This supports wider deployment in additional countries and language groups.


Reporting – User Report Source Column and Direct/Share Calculations

The User Report now includes a Source column and improved calculations to distinguish between “Direct” and “Shared” usage. This gives clearer insight into how surveys are being distributed (for example, via direct links versus shared channels) and aligns with requirements from large payors such as CareOregon.


Usability – Edit Client Button from Case

We added a clearer “Edit Client” option from the Case view so that clinicians and administrators can quickly update client details without having to navigate through multiple screens.


Accessibility – PHQ-9 Colour Adjustments

The colour palette used in PHQ-9 charts has been adjusted to be less saturated and more accessible, while still clearly differentiating severity levels. This supports better readability for users with visual sensitivities.


Scoring – ORS and SRS Scores to One Decimal Place

Displayed ORS and SRS scores are now rounded consistently to one decimal place. This makes charts and reports easier to read while preserving clinically meaningful precision.


Security – Improved 2FA Verification Code Delivery

We addressed issues where two-factor authentication verification codes could arrive late or not at all for some users. Code delivery via email/SMS has been made more reliable as part of our broader messaging infrastructure improvements.


Permissions – Data Entry User Type “Handle Cases” Behaviour

We clarified and corrected how the “Handle Cases” checkbox behaves for the Data Entry user type. This ensures that permissions match expectations for staff who enter data on behalf of clinicians without full case-management rights.


Reporting – Gender Added to Reports

Gender is now available as a filter and field in key reports. This addresses user requests to analyse outcomes by gender where appropriate and permitted by local governance.


Support – Activation Emails BCC to OpenFIT Support

Account activation emails can now BCC the OpenFIT support team. This helps us monitor activation flows and assist customers more quickly if new users encounter difficulties.


SPI – Enable SPI Beyond 50 Sessions

We removed a limitation where the Success Probability Index (SPI) could show “N/A” when a client exceeded 50 sessions (the original length of the model). SPI now continues to function for long-term treatment episodes.


Email Infrastructure – Move to Azure Communication Services

OpenFIT email communication is now powered by Azure Communication Services. This modernises our email stack, improves monitoring and aligns with the SMS infrastructure changes described below.


Data Management – Extended Batch Import CSV

The batch import CSV format has been extended to support additional fields and upsert behaviour across more entities. This makes it easier to perform bulk updates and migrations without manual data entry.


Messaging – Dedicated SMS Template

SMS messages now use a dedicated template that is optimised for the shorter format of text messages, rather than reusing the email template. This improves clarity for clients receiving survey invitations by SMS.


Support – Change of Support Email Address

We updated the primary support email address to support@openfit.care. This is now reflected across the application and in automated communications.


Measures – Removal of GCSRS from Survey List

The GCSRS measure has been deactivated and removed from the survey templates list in the standard OpenFIT configuration, reflecting current recommended practice and simplifying the survey selection options for clinicians.


Messaging – Alternative SMS Provider and Resilience

We have implemented an alternative SMS provider alongside Azure Communication Services to improve resilience and delivery rates across different countries and mobile networks. This underpins improvements in survey invitations and 2FA codes.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article