Who changed this med order on Tuesday? From which device? Answered.
Every state-changing action writes to the audit log: userId, IP, user-agent, and a non-PHI after-blob describing what changed. Immutable. Admin-viewable. Filterable by user, action, and date.
When a state auditor or your own QIDP asks "who changed this med order on Tuesday from which device," you answer in one query, not a multi-day forensic exercise.
Destructive admin actions are mirrored to a separate ops bucket: even if someone with admin access tries to cover tracks, the parallel record survives.
For Texas IDD agencies, Audit Log 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 audit log · immutable · ip + ua. 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: Every state change captured: userId, IP, UA, after-blob, Immutable storage, Filterable by user, action, date. 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 Audit Log as part of its compliance workflow for Texas HCS, TxHmL, HCBS Supervised Living, and Host Home providers. Every state-changing action writes to the audit log: userId, IP, user-agent, and a non-PHI after-blob describing what changed. Immutable. Admin-viewable. Filterable by user, action, and date.
The workflow keeps evidence close to the original shift, client, home, staff member, and approval trail. The pieces that matter most are: Every state change captured: userId, IP, UA, after-blob; Immutable storage; Filterable by user, action, date.
Sereniq is built around Texas IDD operations instead of a generic form builder. Most legacy IDD tools: Activity log exists, but lacks IP + UA capture or is mutable.