Skip to main content

What's New -March 25, 2026

Explore updates and new features in Caresmartz360

K
Written by Kate Lewis
Updated over a month ago

Release Notes – R106 –March 25, 2026

n.b. while the in-app chat and voice bot features were demonstrated during this webinar, it is not currently slated for global release. Once the internal beta is complete, we will communicate a release date for this much-anticipated feature. Details are subject to change.

Mobile App Versions

There will be an update to the Agency app with this release. The version of the Caregiver app will remain the same 2.56 (Code Push 1.0). The Version for agency app will be 2.23 (Code Push 1.0).

The minimum operating system requirements are as below:

Platform

Minimum Version

Notes

iOS

15.1+

Older devices (iPhone 6/6 Plus, some iPad models) cannot run RN 0.78 apps.

Android

7.0+ (API 24)

React Native officially bumped minSdkVersion to 24, so Lollipop (21) and Marshmallow (23) are dropped. Covers ~99% of active devices in 2025.

Schedule Maintenance Window

Please note that regular maintenance is scheduled for March 25th, 2026, from 12:30 AM - 4:30 AM Eastern Time, to perform necessary tool updates and deploy improvement patches. Thank you for your continued partnership!

Pay whiz - Payroll CSV Export

CareSmartz360 now supports generation of Paywhiz-compatible payroll CSV export, allowing agencies to export payroll data in a format ready for direct upload into Paywhiz.

Following are the fields available in the file:

1. Key: This field is mapped the employee’s SSN.

2. PayItem: This field begins with E followed by earning code. Eg: EREG

The Earning Codes are as follows:

· Regular: REG

· Overtime: OT

· Holiday: HOL

· Expenses: EXP,

· Mileage: MIL

· Double OT: DOT

· Weekly OT:WOT

· Travel:TRV

3. Legal: This field mapping is not required.

4. PayGroup: This field mapping is not required.

5. Block: This field mapping is not required. As we are not to block payment for any employee.

6. Hours: This field displays the hourly units.

7. Dollars: We don't need to send values in Dollars if the hours are defined in column G (Hours) and vice- versa.

8. OverrideRate: This field displays the OT Rate (Incase of Overtime)/ Base rate (Reg)/Holiday Rate (incase of Holiday). (This would be inclusive of Multipliers when applicable)

9. LaborValue#: The field is mapped to the CS360 ClientId.

10. LaborDescription#: This field displays the Client’s Name (First Name Last Name)

11. OverridePremium: This field mapping is not required.

12. WeekNumber: This field mapping is not required.

13. OverrideBaseRate : This field mapping is not required.

14. ORWorkersCompCode : This field mapping is not required.

15. ORWorkersCompState : This field mapping is not required.

Paychex - Big Beautifull Bill Enhancement - Delayed - March 31

With this release, Caresmartz360 enhances its overtime (OT) handling to align with the principles of the “Big Beautiful Bill (BBB)” compliance requirements, ensuring a clear distinction between FLSA (weekly overtime) and Non-FLSA (non-weekly overtime) pay classifications.

With the updated logic:

· Overtime is now explicitly classified based on its origin:

· Weekly overtime is treated as FLSA OT

· Daily, 7th consecutive day, and other non-weekly overtime types are treated as Non-FLSA OT

· Pay components are now generated using a combination of OT Type and Multiplier, rather than multiplier alone.

· If the agency chooses to adopt BBB, they can use the newly added FLSA OT and map it with pay component added by Paychex. Otherwise, they may ignore FLSA and continue using the existing approach.

Overall, this update brings Paychex integration in line with payroll compliance expectations under BBB by introducing clear classification, structured pay component creation, and improved payroll integrity.

Enhancement in Report to fetch the actual Client Length of Stay (LOS):

We have enhanced the Client Length of Stay report to provide accurate and reliable stay calculations based on real client status.

What’s New:

· Accurate LOS Calculation: The report now calculates actual Length of Stay using Admission Date and current client status (Active or Inactive/Hold).

· Status-Based Logic:

o Active Clients: LOS = Current Date – Admission Date

o Inactive/Hold Clients LOS = Discharge Date – Admission Date

· New Columns & Filters:

o Added Client Status column for clear visibility

o Introduced Client Name filter for easier navigation

o UI Validation: Deactivation date cannot be set earlier than Admission Date, ensuring data accuracy.

o Additionally, the discharge date column has also been renamed to Discharge Date (Historical / Upcoming) for better reference.

Improved Data Handling: Wrong or Incorrect discharge & reactivation scenarios are handled as continuous stays, preventing negative or incorrect values.

Impact: Eliminates negative/incorrect LOS values and provides a more accurate view of client stay duration.

Consistency: All other report functionalities (filters, paging, behavior) remain unchanged.

This update significantly improves data accuracy for client stay calculations, ensures that erroneous discharges no longer distort LOS, and gives agencies a more reliable and meaningful view of their Active and Inactive/Hold clients’ actual length of stay, while keeping existing reporting workflows intact.

Introduction of Voice Bot for Pending Shift Confirmation

***The new VoiceBot feature is not globally available and is currently in internal beta testing. Stay tuned for the global release. Thank you for your patience.


In-App Chat

***The new In-App Chat feature is not globally available and is currently in internal beta testing. Stay tuned for the global release. Thank you for your patience.

New UI of Weekly Care Summary

The Weekly Care Summary report is now available with improved access, filtering, and export options. Users can refresh the report, apply or reset collapsible filters from the left panel, and view data with default filters applied on first access.\

The report is grouped by Client, with expandable and collapsible rows to view associated caregivers and their weekly work durations. Client and caregiver names are clickable, enabling quick navigation to their respective profiles. Users can view, download, or print individual reports directly from the Actions column.

Flexible download options are supported:

· Download all clients’ reports at once, compiled into a single master folder containing one ZIP per client.

· Download all reports for a specific client as a ZIP directly from the client row.

The display supports weekly date ranges (up to 31 days), service and status-based filtering, role-based staff signature selection, sorting on key columns, and standard pagination consistent with other reports.

New UI of DMAS-90 Weekly Summary

The DMAS-90 Weekly Summary display is now available with enhanced filtering, viewing, and download capabilities. Users can refresh the display, apply or reset collapsible filters, and view data with default filters applied on first access. Reports are grouped by client, with expandable rows showing associated caregivers, quick view options, and individual report downloads.

Users can download DMAS-90 reports at multiple levels:

· All visible clients can be downloaded at once, generating a single master folder containing one ZIP per client, named with the selected date range.

· Per client, all reports for the selected week can be downloaded as a ZIP named with the client’s name and date range.

The display supports weekly date ranges, role-based RN signature selection, client and caregiver status–driven filters, hyperlinks to client and caregiver profiles, and standard pagination with a default of 50 records per page.

EVV updates:

Sandata – Trimming carriage returns in reason code description

We updated the Sandata integration to automatically trim extra spaces and null characters from the Reason Code description. This prevents unintended carriage returns and formatting issues in the payload sent to Sandata.

Impact / Benefit:

· Eliminates errors caused by malformed Reason Code descriptions

· Ensures cleaner, consistent data in Sandata Post Reports for both bulk and single updates

Sandata – Handling exceptions after visit is posted and manually edited

Change:
Improved how Sandata exceptions are handled when a visit has already been posted and the agency performs manual updates (e.g., manual clock-in/out). The system now correctly manages exceptions such as “Visit Without In-Call”, “Visit Without Out-Call”, and “No Show” after posting.

Impact / Benefit:

· Ensures exceptions are applied and resolved correctly even for visits created directly in Approved status

· Reduces scenarios where a “No Show” or similar exception remains incorrectly applied and cannot be fixed once the visit is in Posted view

Authenticare – Download request/response JSON

Added the ability to download full request and response JSON for Authenticare from the EVV interface.

Impact / Benefit:

· Gives agencies and support teams direct access to Authenticare request/response payloads

· Simplifies troubleshooting and audit of EVV data exchanges with Authenticare

Did this answer your question?