3.31 — New Features , Fixes & Improvements | Release Notes

New Features 🚀


  • Web - Sort Ready-for-Billing Patients by Number of Eligible Billable Codes - Added Patient Prioritization Sorting: Billing teams can now sort “Ready for Billing” patients by the number of eligible RTM billable codes and optionally view the count, making it easier to prioritize higher-value billing opportunities.

Improvements 🔧


  • Prompt Integration - Improved RTM Status Synchronization - Engage now retrieves RTM status directly from Prompt to ensure a patient’s RTM enabled/disabled state remains accurate, even when multiple cases exist. Current RTM statuses remain unchanged, and the updated synchronization logic applies only to new updates moving forward.


  • Web - Updated Text Color - Improved Theme Readability - Text color in the yellow design theme has been updated from white to black to improve readability and accessibility across the interface.

Bug Fixes 🐞 


  • Web - Corrected Reply Handling for OTP Emails - One-time passcode emails sent to patients now use a no-reply address to prevent responses from being routed to administrative inboxes and reduce confusion about support channels.


  • Web - Fixed Missing SMS Setup Links - Patients now correctly receive their account setup link via SMS when a new account is created through Prompt.


  • RTM - Fixed Incorrect RTM Code Generation - Code 98977 will no longer generate unless the required minimum number of monitoring data points has been met during the billing period.


  • Mobile Web App + Mobile App - Resolved Secure Connection Warning - Links in system-generated emails now open without browser security warnings, allowing patients to safely access Engage pages from email links.


  • Web - Fixed Email Sender Configuration - The system now consistently uses the designated no-reply address instead of reverting to the administrative email.


  • RTM - Corrected RTM Reporting Totals - The RTM Billed Codes dashboard now counts only codes that are actually billed, preventing inflated totals and ensuring consistency across reports.


  • Web - Fixed Missing Activation Emails - Patients now receive activation emails when a provider assigns a HEP via Prompt, and the patient status properly reflects that a HEP has been created.


  • Web - Resolved Duplicate Account Creation - The system now prevents multiple patient accounts from being created using the same email address and phone number combination.


  • RTM Reports - Fixed Missing Codes in Reports - Billed RTM codes 98985 and 98979 now appear correctly in provider billing reports, filters, and dashboard charts.


  • RTM - Fixed Missing Billing Documentation - Eligible 98980 codes now correctly display billing details instead of showing “Billing: Null” and associated clinical monitoring logs.


  • Web - Fixed RTM Dashboard Display Issue - Providers will now correctly see their RTM patients without needing to manually adjust filter settings each session.


  • Web - Fixed Invalid Patient Entries - Deleted or discharged patients no longer appear in the RTM dashboard, preventing “User not found” errors when opening profiles.


  • Web + Mobile App - Resolved Missing HEP Across Accounts - Patients with multiple group associations will now retain access to their HEP when one associated account is deleted.


  • Web - Fixed HEP Assignment Error - Providers can now successfully assign HEPs without encountering prescription update errors, and patient activity status updates correctly.


  • Web - Fixed HEP Status Sync Issue - Patients assigned a HEP through Prompt now correctly show that a program exists instead of displaying “No HEP.”


  • Web - Fixed Premature Session Timeouts - Providers will no longer be logged out after short idle periods, reducing the risk of lost work during active sessions.


  • RTM - Resolved Inconsistent Code Documentation Display - Providers and internal teams now see consistent documentation data for RTM code 98985 during the billing period.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.