Sunwave 8.18

Sunwave 8.18

Date

Oct 8, 2025

Issues

 

10 Tickets

 


CRM Enhancements

Collection Warning Removal Reasons

What's New
Users with the Manage Collections Warning permission can now document a required removal reason and optional removal note when deactivating a Collections Warning. The system also now logs full removal metadata—including who removed it, when, and why—across both parent and child realms. A new "Resolved" option has been added to all realms under Collections Warning Closed Reasons.

Why This Matters
This closes a long-standing audit gap by enabling traceability and accountability around Collections Warning removals. It also supports clearer operational communication between clinical, billing, and administrative teams across multi-realm environments.

Who It's For
Billing teams, Compliance Officers, and anyone with Collections Management permissions working within CRM → Accounts, Opportunities, Patient Chart, and Intake workflows.

How it works

image-20251002-185127.png
  • Trigger Points: The new removal workflow is triggered when a user with Manage Collections Warning permission clicks the red COLLECTIONS text or selects Menu → Collections Warning / Manage Collections from:

    • Patient Chart

    • CRM → Accounts

    • CRM → New Opportunity

    • CRM → Opportunities

  • New Required Field: Upon disabling a Collections Warning, a Removal Reason dropdown appears. This is:

    • Required to save the warning removal

    • Populated from: Parent Realm → List Values → CRM → Collections Warning Removal Reason

image-20251002-185237.png

MARA Enhancements

Change MARA TX Plan to 3 Problems/Objectives/Goals

What’s New

Expanded Problem Generation
Mara can now generate three problems/objectives/goals in a Master Treatment Plan if supported by the assessment.
Assessment‑Driven Output
The number of generated items is determined by the client’s assessment data.

Regulatory Compliance Support
This enhancement helps providers satisfy requirements mandating that treatment plans address all identified problems, needs, and strengths.

Why This Matters

  • Better Regulatory Compliance — Some states require treatment plans to address all identified problems, needs, and strengths. This update helps meet mandates that fixed‑limit plans cannot satisfy.

  • Improved Clinical Accuracy & Completeness — Treatment plans will more fully reflect the real complexity of a client’s situation, alleviating the need for manual addition after auto‑generation.

  • Workflow Efficiency — By automatically capturing more problems when warranted, providers save time and reduce the risk of omissions or manual errors.

Who’s It For

  • Clinicians, therapists, case managers, and care coordinators who use Mara to author or review treatment plans.

  • Billing, QA, and compliance teams who validate that treatment plans satisfy documentation requirements.

How It Works

  1. Mara reviews the structured assessment data to detect all clinically relevant problems, needs, or areas for intervention.

  2. Based on that, Mara generates a treatment plan with N problems/objectives/goals (where N ≥ 1, up to 3), rather than stopping at two.

  3. Users can regenerate the plan (if the initial output doesn’t suit them) or manually add, remove, or edit any problem/goal.


RCM Enhancements

Give Billing Admin Users access to CLI File (Export File to Clearinghouse)

What’s New

  • New permission level created specifically for Billing Admin users to allow access to the CLI export file / clearinghouse export.

  • Billing Admins can now generate or download the CLI export / clearinghouse file directly, without requiring higher‑level or engineering access.

  • UI changes: the export option is now visible only to users with the new permission.

image-20251002-190541.png

Why This Matters

  • Operational efficiency: Billing Admins can self‑serve file exports, reducing delays and dependence on support or engineers.

  • Security & principle of least privilege: The new permission restricts access narrowly to the CLI export file, instead of granting full or broad access to systems.

  • Auditability & role separation: Organizations can better maintain separation of duties — billing tasks vs system-level access — while still empowering roles that need it.

Who It’s For

  • Billing Admin users who need to access and transmit files to the clearinghouse.

  • Finance / billing teams managing clearinghouse exports.

  • Admins / compliance officers who want to control and audit access to export functionality.

  • Operational Efficiency: Billing Admins can now self-serve export operations, reducing friction and support requests.

How It Works

  1. Any user with ADMIN BILLING in their user profile in practice setup>users will now be able to see the Download button in the Billing>Claims Submission screen.


Ticket List

Qs - Q's Report - "Completed" Queue's Display in Q Report -> Incomplete

Prevent Decimals in Order Duration Field

SSN Field does not save when entered from the "New Opportunity Pop Up" 

MARA - Change MARA TX Plan to 3 Problems/Objectives/Goals 

Give Billing Admin Users access to CLI File (Export File to Clearinghouse)

Realm Set-Up - Is Inventory may not be used with Med Count

Remediate Tables with Empty Rows in Patient Engagement

Q's Report - Last Modified Not Updating On Initial Update

Blank app when “Waves” from Menu disabled

Collections Warning - add Closing Reason & Comment