Mobile-first capture: type, severity, witnesses, immediate action, follow-up. Critical incidents auto-fan-out to admin, supervisor, and nurse the second the form is submitted.
The incident print captures every field your supervisor or QIDP needs for follow-up. Incident records, supporting notes, MAR context, signatures, and close-out history all go in the survey-prep bundle.
The integration that operators love: a MAR refusal silently opens an Incident draft. Your nurse opens it, completes it, signs it. The escalation that used to depend on a DSP remembering now happens by default.
Close-out is a supervisor-signed workflow: every state change written to the audit log with timestamp and user.
For Texas IDD agencies, Incidents is not an isolated screen. It touches the client record, staff permissions, home assignments, supervisor review, and the evidence packet you may need during an HHSC look-back. Sereniq keeps those pieces in one workflow so the record reads cleanly months after the shift is over.
The page is tuned for incidents · critical follow-up. In practice, that means the product has to work for the DSP on a phone, the supervisor approving work, the nurse or program lead checking exceptions, and the administrator who needs a defensible export without rebuilding the story from paper binders.
The core controls are specific: Mobile-first capture from the floor, Critical incidents auto-fan-out to the right roles, MAR refusal silently opens an Incident: no manual escalation. Those details are what turn daily documentation into evidence that can support HCS Residential Support, TxHmL documentation workflows, HCBS Supervised Living, and Host Home / Companion Care operations.
Yes. Sereniq includes Incidents as part of its compliance workflow for Texas HCS, TxHmL, HCBS Supervised Living, and Host Home providers. Mobile-first capture: type, severity, witnesses, immediate action, follow-up. Critical incidents auto-fan-out to admin, supervisor, and nurse the second the form is submitted.
The workflow keeps evidence close to the original shift, client, home, staff member, and approval trail. The pieces that matter most are: Mobile-first capture from the floor; Critical incidents auto-fan-out to the right roles; MAR refusal silently opens an Incident: no manual escalation.
Sereniq is built around Texas IDD operations instead of a generic form builder. Statewise (formerly TaskMaster Pro) / GIV: Incidents exist as a module. The MAR-to-incident auto-link does not.