New features
Bed-availability widget on the CE pipeline (CE) A 5-tile bed-availability widget now sits above the Community Engagement pipeline board so intake staff can see capacity without leaving the board. Tiles cover Available, Reserved (derived from active CE leads), Authorization risk, Upcoming discharges (14 days), and total Occupied. The Authorization-risk tile is org-configurable from CE Settings — toggle it on or off based on whether your team triages by payer risk. See Leads. Edit lead urgency and see it on the pipeline (CE) Lead urgency is now a first-class signal on the pipeline board. Edit urgency directly from the lead profile, and high or critical leads show a name-adjacent urgency badge plus a colored tile outline so the board scans at a glance. A new stage-header Leads popover lists each stage’s leads, color-coded by urgency, and click-through opens the lead detail. See Leads. Pick a pipeline track when creating a lead (CE) The lead intake wizard and the Add Lead dialog now include a pipeline-track picker, so a new lead can land on the correct service-line track without an extra hop. The picker honors org-configured tracks and respects existing assignment permissions. See Leads. Auto-create follow-up tasks from scheduled meetings (CE) When you schedule a meeting from a lead, contact, or partner, Community Engagement can now auto-create a follow-up task assigned to the meeting owner. Toggle the behavior and set a default lead time (1–14 days after the meeting end) in CE Settings → Calendar follow-ups. The task shows up in My Tasks and notifies the assignee. See the Calendar scheduling user guide and admin guide. Push follow-up tasks to Microsoft 365 calendars (CE) Follow-up tasks can now be pushed to a Microsoft 365 calendar as a PHI-safe event so they show up in Outlook alongside meetings. Configure the push and the recipient resolution order (override → coordinator → default) in CE Settings. Due-date notifications also now sweep on their own schedule so an assignee gets an in-app and email reminder when a task comes due, with idempotency so you don’t get repeat pings. Automated corrective actions from audit findings (GR) Critical and high-severity audit findings linked to a regulatory requirement now automatically open a Corrective Action Plan (CAP) against the active accreditation. The CAP is created with a derived target date, linked back to the source audit finding, and stays idempotent if the finding is re-emitted. Low-severity and unlinked findings continue to flow through manual remediation. See the audit admin guide and compliance admin guide. Evidence trails on regulatory reports (GR) Regulatory reports now carry an evidence trail. When a report is submitted, the platform fans the event out to every mapped accreditation body and records evidence on each linked standard, with a Source event badge on the report detail and a click-through to the originating event. A new Regulation mapping settings area lets governance admins manage which standards a report satisfies. See the compliance admin guide and the compliance dashboard.Updates
Evidence Coverage and Evidence Gaps on the compliance dashboard (GR) The Compliance dashboard gains two new cards. Evidence Coverage shows a per-category breakdown of requirements with at least one linked piece of evidence; Evidence Gaps lists the highest-priority requirements with no evidence linked yet, so you can close the most important gaps first. Type-to-confirm on irreversible actions Destructive actions across the platform — permanent deletes, voids, revokes, terminates, and irreversible bulk operations — now require you to type a confirmation word (DELETE, VOID, REVOKE, TERMINATE) before the action runs. The new affordance is consistent across HR, FA, FW, LO, PM, Clinical, and the platform admin surfaces, replacing inconsistent legacy confirm dialogs.
Built-in security and backend health alerts documented (PF)
Every organization ships with a set of platform-managed alert rules. Security defaults fire on permission violations, account lockouts, session hijack, suspicious activity, IP blocks, bulk operations, config changes, and data exports. Three backend-health alerts watch DLQ depth, domain-event lag, and edge-function errors. See Alert configuration and Security alert configuration for the full list.
Wizard integrity hardening (FW)
The wizard audit and live-stack checks no longer silently pass when the backing stack is unreachable. Generated and identity columns no longer produce false “required field” findings. The create-wizard submit gate now requires a real read-back of the persisted row before reporting a wizard as proven. Net effect: wizards that look green really are green.
Bug fixes
- GR-08 evidence fan-out now correctly emits one evidence record per mapped accreditation body when a regulatory report is submitted, instead of only the first match.
- Consistent destructive-dialog UX — destructive confirmation dialogs across platform, HR, FA, FW, LO, PM, and Clinical now share a single visual treatment, replacing long-standing inconsistencies.
- Token and opacity consistency — sporadic color and opacity drift across the app is now aligned to the design-system tokens, so destructive, warning, and muted surfaces render consistently across modules and themes.