PracticeQ Release Notes

RESOLVED Invoice and Audit Trail Exports by Assistants

Development has resolved an issue that was preventing assistants from exporting the Lists → Invoices report and the Audit Trail.

RESOLVED Copay Calculation in Claim Payments

Development has resolved an issue where claim payments were not calculating client responsibility correctly based on copay amounts. Amounts will now match expected client responsibility moving forward.

IMPROVED INTEGRATION: Engage

Development has added a Mountain Time option in the Engage Timezone menu in Booking Settings.

RESOLVED Claims Export by Assistants

• Development has resolved an issue that was preventing assistants from exporting the Lists → Claims report.

IMPROVED INTEGRATION: Engage

• Development has resolved an issue where newly added clients were not able to access Engage despite being added correctly in PracticeQ.

IMPROVED INTEGRATION: eRX

• Development has improved the Generate Invitation URL button to guide Supporting Users to create a Full Administration role in ScriptSure.
• This will improve the workflow for solo practitioners who need to be approved to prescribe controlled substances.

IMPROVED PERFORMANCE: Invoicing Workflow

• Development has applied invoicing workflow limits to canceling invoices with payments:
  • Added safeguards and clearer rules around canceling invoices that already have payments applied.
  • Users cannot cancel an invoice that has an unrefunded payment attached.
  • This reduces the risk of accidentally disrupting financial histories, refunds, and reconciliations.

Income Report Improvements

• Development has resolved an issue where processed ACH payments were showing as
  Offline Payments
  in the Income Report.
• ACH payments with valid transaction IDs will now be correctly categorized as
  electronic/ACH payments
  .

IMPROVED INTEGRATION: eRX

• Development has fixed an issue where newly added assistants where not showing as available invitees in
  More → ePrescribe
  .
  • New assistant records now sync consistently so eRX invites can be sent in a timely fashion.
• Development resolved an issue where clients moved from one location to another were not being synced properly to a new eRX location.
• Development also addressed an issue where if a client's unit number field was blank/empty in PracticeQ, updates were not correctly reflected in ScriptSure, causing address discrepancies.

IMPROVED INTEGRATION: Engage

• Development has resolved an issue where newly added clients were not able to access Engage despite being added correctly in PracticeQ.

RESOLVED: Staff Comment Logs

• Development has addressed an issue where staff comment logs showed the author as "unknown" in the Audit Trail if the practitioner/assistant who entered the comment was later deleted.
• Comment histories now retain and display the original author's identity, even if the user account has been removed.

IMPROVED PERFORMANCE: Engage Appointment Sync

• Appointments scheduled in PracticeQ will now consistently appear in the Schedule and EasyFill sections of Engage after the 5-minute sync time has elapsed.
• Appointments canceled in PracticeQ will now consistently show as canceled in Engage after the 5-minute sync time has elapsed.

RESOLVED: GAD-7 Defaulting to Public

• Development has fixed an issue where the General Anxiety Disorder 7 questionnaire (GAD-7) was defaulting to an anonymous/public form by default.
• Moving forward, the English and Spanish versions of the GAD-7, when imported from the Standard Forms library, will have the Enable Anonymous Submissions option disabled by default.
• This improvement will ensure that each GAD-7 is tied to the correct client record.

RESOLVED: Developer API charges working as expected

• Development has resolved an issue where unchecking the Enable API access checkbox was not stopping developer API charges on an account.

RESOLVED: Rivia API calls

• Development has fixed an issue where Rivia API calls were not updating appointments in PracticeQ as expected.

NEW FEATURE: Export limit message

• PracticeQ will display a message when an export exceeds 20,000 line items.
• This message will alert your practice to batch your exports for more accurate record keeping.

RESOLVED: "Keep me logged in" setting consistent across browser tabs

• Development has resolved an issue where users who had PracticeQ open in multiple tabs would select Keep me logged in for 1 week in one tab, but would be logged out on other tabs.

RESOLVED: State formatting on Engage Account Setup Form

• Development has resolved an issue where Engage toll-free approval was being rejected due to the state abbreviation not consistently featuring two upper case characters (for example, Tx instead of TX).

• The state field will now feature a dropdown menu of two upper-case characters to select from, which will protect against rejections.

RESOLVED: PracticeQ Pay Accounts Closing

• Development has fixed an issue where removing a user from a PracticeQ Pay account caused the PracticeQ Pay account to close.

RESOLVED: Provider Appointment Approval Email not sending

• Development has resolved an issue where the Provider Appointment Approval email was sometimes not sending despite the appropriate box being checked in the appointment dialog window.

RESOLVED: CMS-1500 signature dates showing next day's date

• Development has fixed a timezone bug where CMS‑1500 signature dates could roll to the next day after 7pm EST due to UTC conversion.
• Dates will now display consistently regardless of submission time.

RESOLVED: Account Verification emails

• Development has resolved an issue where account verification emails links were not directing clients to the verification page.

RESOLVED: Day-Before Reminder Emails Not Sending to Contacts

• Development has resolved an issue where the Reminder Emails set to send the day before an appointment were not sending to client contacts.

RESOLVED: Note Exports Issue

• Development has resolved an issue where treatment note exports were not generating properly.

RESOLVED: Auto-Invoicing Behavior

• Development has resolved an issue where automatically created invoices were sometimes creating duplicate invoices and/or duplicate charges for a single appointment.

Reassign client location in eRX!

• Previously, PracticeQ Support changed client eRX locations at your request.
• Now, you have the power to update a client's eRX Practice Location in their client profile!
• Read more here.
• To use this tool, your user profile must have access to the necessary eRX locations.

Updated Invoice Cancellation Settings

• When you cancel an invoice in PracticeQ, the invoice will now unlink from its original appointment!
• Auto-charge settings will also be disabled when the invoice is canceled.
• You will see the following popup when you select Action → Cancel for the invoice in question:

Rich-Text Notes: You Spoke Up, and We Listened!

• After hearing your feedback, development has rolled back the change made in December 2025 that preserved rich-text formatting after a note was locked.
• Rich-Text question types will once again default to bold blue type once locked.

RESOLVED: Heidi Widget Not Launching

• Development has resolved an issue where Heidi was not launching in a client note when expected.

RESOLVED: Account Exports Unsuccessful

• Development has resolved an issue where account exports were failing.

Trizetto Account Lock Settings

• Development reduced PracticeQ's account lock duration from 180 minutes to 60 minutes to match Trizetto's policy, allowing users to regain access without unnecessary delay.

Saving Questionnaires

• Development resolved an issue where questionnaires saved within a folder displayed outside of the folder on the My Forms page.

Rich Text Formatting in Notes

• Our team addressed an issue where a note containing Rich Text formatting changed when locked.

• Moving forward, Rich Text formatting will stay intact after the note is locked.

Client Profile Permissions Update

• Development has resolved an issue where users with the Can View Client Profiles permission were able to edit client profiles even when the Can edit client profiles permission was not selected.

• They also resolved an issue where users with the Can create diagnosis permission were able to set diagnosis end dates, even when the Can edit diagnosis on main list/on notes permissions were not selected.

Audit Trail Updates

• Creating a comment and deleting a comment will now generate entries in the Audit Trail.

• The system will now log an Invoice Created event in the Audit Trail when ANY invoice is created, regardless of where the action originates (in the client profile, appointment window, or elsewhere).

Pending Invitations for New Assistants

• Previously, if new assistants bypassed the initial invite to PracticeQ, their status would continue to display as Invitation Pending, even after they create their account and reset their password.

• Development has resolved the issue; moving forward, if the user goes through the reset password flow, their status will correctly update to Active.

Uninvoiced Sessions and Copay

• Development has addressed an issue where uninvoiced appointments added to statements were not taking insurance billing, such as copay, into account.

• Moving forward, statements will correctly display copay instead of full amount for uninvoiced appointments.

Time/Timezone in Appointment Confirmation Emails

• Development has resolved an issue where confirmation emails were displaying the practitioner's timezone instead of the client's.
• Confirmation emails will now reflect the client's timezone, as intended.

Elation Integration

• We have resolved an issue where the Group ID and Member ID fields were not syncing with PracticeQ unless a Carrier Name was provided. These fields will not sync correctly even when the carrier's name is left blank.

Form Restoration

• When users deleted a Form and Form Folder and then later selected the Form to be restored, the form was not being restored correctly and placed back in the correct Active Questionnaire, Consent Form, or Note Template list.
• This has been addressed and forms should restore correctly moving forward.

Locking notes issue resolved

Development has resolved an issue that was causing notes to lock before all signatures were completed. Moving forward, the following logic will apply for notes requiring signatures:

• If a note with a required and non-required signature field has a signature applied to the non-required signature field, the note will not lock.
• If a note with a required and non-required signature field has a signature applied to the required signature field, the note will lock.
• If a note with a single non-required signature field is signed, the note will lock.
• If a note with a single required signature field is signed, the note will lock.