Incidents

MAR refusals raise the alarm. Automatically.

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.

Capture
Mobile-first
Critical
Admin, supervisor, nurse
Close-out
Supervisor-signed
Incidents · critical follow-up
IncidentsBook a demo
01  /  How it works

Incidents, step by step.

1

A print with every follow-up field

The incident print captures every field your supervisor or QIDP needs for follow-up, with signatures and close-out history. The incident list and the open-incident deficiency file go in the survey-prep bundle.

2

A refusal raises the alarm the same shift

The link that operators love: a MAR refusal fires a critical alert to your supervisor and nurse, linked to the exact dose, so the incident gets filed the same shift instead of surfacing at survey. The escalation that used to depend on a DSP remembering now happens by default.

3

Close-out, signed and logged

Close-out is a supervisor-signed workflow: every state change written to the audit log with timestamp and user.

02  /  What ships

The things that actually ship.

  • Mobile-first capture from the floor
  • Critical incidents auto-fan-out to the right roles
  • MAR refusals alert supervisors and nurses as a critical event, automatically
  • Incident print + internal follow-up detail + CSV bundle
  • Supervisor close-out signature with full audit trail
03  /  Compared

What competitors don’t do here.

Full comparison
ToolHow it works thereHow Sereniq does it
Statewise (formerly TaskMaster Pro) / GIVIncidents exist as a module. The refusal-to-alert link does not.MAR refusals alert supervisors and nurses as a critical event, automatically
PaperLost forms, missed escalations, recoupment lines.Critical incidents auto-fan-out to the right roles
04  /  FAQ

What providers ask before switching.

Does Sereniq support Incidents for Texas IDD providers?

Yes. Sereniq includes Incidents as part of its compliance workflow for Texas HCS Residential Support, HCBS Supervised Living, and Host Home / Companion Care 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.

How does Incidents help during an HHSC look-back?

The workflow keeps evidence close to the original shift, individual, 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 refusals alert supervisors and nurses as a critical event, automatically.

What makes Sereniq different for Incidents?

Sereniq is built around Texas IDD operations instead of a generic form builder. Statewise (formerly TaskMaster Pro) / GIV: Incidents exist as a module. The refusal-to-alert link does not.

See incidents set up for your agency.

A walkthrough built around your programs. We reply within one business day.

Have a quick question first? Ask it here