Release Date -
Overview
notea46e7d86-bf3f-4b21-ac5c-b9f5b21ab4ccFeatures included in this release
-
Program Defects Fixed
Progress Notes
Features included in this release
-
Program Defects Fixed
Progress Notes
New features + Program Improvements + Defects
The new Progress Notes workflow has been optimized so the signature device check runs immediately after “Add New Note” is clicked, instead of when a blank note or template is selected. This moves the delay upfront (as in the old workflow) and avoids lag when loading templates, significantly reducing perceived slowness for users without Topaz/ePad installed.
Yes
Ledger
The new Edit Treatment modal has been updated to match the legacy screen’s behaviour: after the close‑out date, users can again change billing order only (without recalculating estimates), as before. This restores parity between the old and new UIs so offices can adjust billing order on closed‑month procedures when needed.
Yes
Progress Notes
The Progress Note UI has been updated to correctly handle attachments with long file names. Long names now truncate with an ellipsis (…) instead of breaking the layout, keeping the Add/Edit Progress Note modal visually consistent across supported screens.
Yes
Progress Notes
The “Load My Signature” logic on the Unsigned Progress Note screen has been aligned with the standard Progress Note behaviour. The button now correctly respects the currently authenticated user and no longer allows another user’s signature to be loaded via “Load My Signature,” ensuring consistent and secure signature loading across Progress Note and Unsigned Progress Note.
Yes
Progress Notes
The Progress Note screen has been updated so that ePad signatures can now be successfully captured and saved when using the new Progress Note UI. Offices with ePad enabled can again add ePad signatures directly in Progress Notes.
Yes
Progress Notes
The Progress Note confirmation modal has been updated so that the “OK” button now works correctly even when no ePad device/software is installed and ePad is enabled.
Yes
Progress Notes
Notes Macro changes now save successfully without redirecting users to the Denticon Page Unavailable page, and the Notes Macro list updates as expected.
Yes
RCM |
||||
Module |
JIRA# |
Description |
Beta/GA |
Release Notes [Yes/No] |
No User facing changes | ||||
Defects
Module |
JIRA # |
Release Notes [Yes/No] |
DPC |
||||
Module |
JIRA# |
Description |
Beta/GA |
Release Notes [Yes/No] |
Defects
Module |
JIRA # |
Description |
Denticon Patient Experience [Integration] |
||||
Module |
JIRA# |
Description |
Beta/GA |
Release Notes [Yes/No] |
Treatment Plan Presentation - Decline & Sign |
[DENT-18839] [Q1][PI2] Treatment Plan Presentation - SAGE QR Code and Decline and Sign - JIRA |
Within Treatment Plan Presentation, in Step 1 (Review Treatment Plans):
Post‑decline:
Value: Provides a documented, auditable way to record that a patient declined treatment, with proper acknowledgement and a copy of the declined plan. |
BETA |
No |
Treatment Plan Presentation - QR Code for Launch |
[DENT-18839] [Q1][PI2] Treatment Plan Presentation - SAGE QR Code and Decline and Sign - JIRA |
From the Treatment Presentation modal:
Security highlights:
Value: Makes it faster for staff to move the Accept & Pay experience to a mobile device without logging in separately or re‑selecting plans. |
BETA |
No |
Treatment Plan Presentation - Do not update Treatment Plans to Unaccepted |
[DENT-19576] Enhancement: Do not update Treatment Plans to Unaccepted - JIRA |
Revert from previous implementation, Treatment Plans will only be updated to Unaccepted (U) status where the Decline Treatment flow has been followed. Else, Treatment Plans accepted will be marked as accepted (A) where acceptance has been completed, and blank where the plan has not been updated. |
BETA |
No |
AutoEligibility site feature GA enablement |
[DENT-20240] AutoEligibility site feature GA enablement - JIRA |
Removal of site feature flags to ensure AutoEligibility is available to all clients. |
GA |
No |
Defects
Module |
JIRA # |
Description |
Integrations |
[DENT-19681] DCA - Dosespot not updating on RX screen - JIRA |
A potential root cause was identified from DataDog logs, and a fix has been prepared in a pull request. The issue was reported as occurring with testing limited to a specific patient, and not reproducible across other patients. Analysis suggested the problem was due to incomplete or incorrect responses from the DoseSpot API. |
Integrations |
Reduction of patient information that is shared with the DoseSpot endpoint to only pass the PatientID. |
|
DCORE2 New Features |
|||
JIRA# |
Description |
Beta/GA |
Release Notes [Yes/No] |
DENT-20842 |
Denticon now displays a non-blocking notification to users whose sessions are flagged as exhibiting bot-like or automated activity on key pages (Patient Search, Insurance, Claims, and Notes). Users can dismiss the alert and continue working. Whitelisted RPA integration accounts are excluded from detection. This is an early-warning observation step ahead of enforcement; no users are blocked at this time. |
GA |
No |
DENT-20248 |
Denticon now automatically strips trailing slashes from Cloud 9 URLs when they are entered or saved in configuration. This prevents launch failures caused by malformed URLs stored in the database. No configuration changes are required. |
GA |
No |
DENT-20741 |
Added PGID 5430 to the Denticon SSO allowlist to enable Apteryx bridging for that group, following the established SSO enablement pattern. Change applied across DenticonCore and PoWSolution. |
GA |
No |
Defect Fixes
JIRA # |
Description |
Release Notes [Yes/No] |
DENT-19981 |
Fixed an issue where contract charges were posting to the ledger but the associated credit card payment was not being processed or recorded when using CC Pay. Affected offices running periodic contract billing via Utilities > Review Contract. Payment posting and ledger entries now align correctly for contract billing workflows. |
No |
DENT-19965 |
Fixed an issue where users could create a password containing the character combination |
TBD for final |
Defect Fixes
JIRA # |
Description |
Release Notes [Yes/No] |
DENT-20941 |
As per the latest implementation, PN availability (both toolbar icon and Patient dropdown menu item) is now aligned with the following logic:
This behavior has been validated across legacy, hybrid, and fully core flows, ensuring consistency with the existing legacy application behavior. |
Yes |
DENT-2118 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-20844 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-21183 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-20743 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-21170 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-21240 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-21276 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-21368 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-21369 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
DENT-21371 |
Advanced Charting bug as per Advanced Charting Fully Core Beta Feedbacks |
No |
Technical Enhancements
Module |
Jira # |
Description |