✍️ Signature Requests Follow the Assigned Signer
When you change a client's assigned signer, the open signature request moves with that change instead of leaving a duplicate behind. 💙
✨
What's new:
- 🔁 The request moves:Assign or change a user in a client information field — Caregiver, BCBA, school representative — while a signature request is pending, and the request moves to the new person.
- 🔔 The new signer is told:A comment is added to the session thread and the new signer gets a notification. The previous signer's notification is removed.
🛠️
Fixed:
Signing after the assignment changed used to leave the original request open, so the field appeared twice on the note — once signed, once pending — and every new attempt added another signature.💡
Why it matters:
Caseloads change while notes wait for signatures. The person who needs to sign hears about it, and the note closes when they do.One thing to know:
Notes already affected are not repaired by this change. If a note is waiting on that signature, clear and reset the client's signer field. If it was signed and an open request was left behind, cancel that request.---
📋 Find and Fix Gaps in Your Client Data
Available for organizations with the Outcomes subscription
Record health shows how complete your client data is, and Update client data lets you fill gaps in place. Both pages are open to your organization, with privileges you control. 💙
✨
What's new:
- 📊 Record health:An overall score and a percentage for each field, across the clients you can access.
- ✏️ Fill gaps inline:On Update client data, edit a cell with the same input the client profile uses — dropdown, date picker, or text box. The change saves immediately and appears on the client's profile.
- 👤 Only your clients:Both pages show the clients you have access to and say how many. If you can access every client, you see the whole organization.
- 🔐 Two privileges:Record health: Manageadds choosing which fields count.Record health: Access and updatecovers viewing and editing. Managers haveManageby default; Administrators and Supervisors can be givenAccess and update.

💡
Why it matters:
Gaps used to be found by an admin and sent around by hand, usually when a report was due. Now the person with the information can see and fix it on their own clients.Two things to know:
- Editing follows the rights you have. If you can't edit a field on the client profile, the cell is read-only, and Lumary-managed fields stay read-only.
- A row's gap count updates as soon as you save. The Record health score updates on its next refresh.
---
🎚️ Control Who Can Mix Measurement Types in a Program
A new privilege lets a Manager decide which roles can create a program with targets of multiple measurement types. 💙
✨
What's new:
- 🔐 New privilege:"Create Programs with Targets with Mixed Measurement Types," under Settings > Organization > User Privileges > User Abilities > Programs.
- ✅ Nothing changes unless you change it:At release, the privilege is on for every role that could do this. You can't give it to Behavior Technicians and Parents.
- 🚫 When it's off for a role:Only targets that match the program's measurement type can be selected.

💡
Why it matters:
Mixing measurement types within a program can make graphs harder to read. This privilege lets organizations require matching measurement types for specific roles or keep their existing setup.One thing to know:
Programs you have keep working. But if the privilege is off for a role, someone in that role can't save changes to a program that mixes measurement types — including edits on other tabs — until the mismatched targets are changed or removed.---
✍️ Map an Additional Signature Field to Lumary
✨
What's new:
Lumary-integrated clinics can send an additional, separate signature URL to Lumary.
The section on the Integrations page is now called
Signature Mapping
(previously Guardian Signature Mapping), with a link to the setup article next to it.
💡
Why it matters:
Sending a signature URL to Lumary enables more robust tracking of note signatures and lets you pull actual signatures into reports, such as signature logs required by some payers. Previously, Lumary-integrated organizations could map a caregiver signature field and an alternate caregiver field to Lumary, using the same field on the Lumary side.
Now, you can send an additional, separate signature type to Lumary, allowing different signature types to pull into signature logs or other reporting.
One thing to know:
Nothing changes for the caregiver and alternate caregiver mappings you already have.👉
Learn more about how to set up and utilize signature mapping:
Signature Mapping to Lumary---
📑 See Missing Data in the Care Model Export
For organizations using Care Model, the Excel export's report info tab has a Missing data section. 💙
✨
What's new:
One row for each field used in your grouping or filters with clients missing a value, showing how many clients are missing it, what that means for the numbers, and completeness across all active clients. If nothing is missing, the section says so.
💡
Why it matters:
The export goes into payer conversations. You can answer "how complete is this?" before anyone asks.---
➕ Also in This Release
📅
Lumary appointments
: Deleting a scheduled session in Hi Rasmus no longer hides the Lumary appointments linked to it. They stay on the schedule and link to another session with the same name when one exists.▶️
Starting a session
: Opening the same session on a second device joins the session already running instead of starting a second one, and a note that has gone to your integration can't be sent again. Both could leave a note stuck as not rendered, which blocked starting the next session.📄
Report templates
: Reordering sections in a report template no longer unlinks them from their section templates on save. Sections unlinked before this release stay unlinked — re-add the section or rebuild the template to restore the link.