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, entity, and date, with CSV export.
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.
The log is append-only: rows are never updated or deleted, so even an admin cannot rewrite history. Export the whole thing to CSV whenever a reviewer asks.
| Tool | How it works there | How Sereniq does it |
|---|---|---|
| Most legacy IDD tools | Activity log exists, but lacks IP + UA capture or is mutable. | Every state change captured: userId, IP, UA, after-blob |
Yes. Sereniq includes Audit Log as part of its compliance workflow for Texas HCS Residential Support, HCBS Supervised Living, and Host Home / Companion Care 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, entity, and date, with CSV export.
The workflow keeps evidence close to the original shift, individual, 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, entity, 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.
A walkthrough built around your programs. We reply within one business day.
Have a quick question first? Ask it here