Administration
Audit logs
ArkCloud keeps three records: an activity log of sign-in and other application events, a hash-chained log of administrative and financial actions whose integrity an administrator can check, and a PHI access log of who opened which patient record. The first two are viewed from ArkCloud RCM; the PHI access log is reached from the ArkCloud launcher.
Written for: Organisation administrators · Compliance officers · Security reviewers
Where to look
| Field or control | What it means |
|---|---|
| Administration → Audit Logs | Immutable Audit Logs (the hash-chained log): filter by category, event type and date; open an event to see actor, resource and payload; Verify Integrity runs the check over the chain; Export Logs downloads a JSON file and needs a start and end date. |
| Compliance → Audit Log | The activity log (sign-ins, failed sign-ins, lockouts and other application events), filterable by event type and date, with export. Supervisor or Admin; other roles see "Only supervisors and administrators can view the audit log". |
| PHI access log | Footer of the ArkCloud launcher (/access-log). Every opening of a patient record screen: when, who, which screen, which patient record (by record id, not name) and from which address. Choose 7 days, 30 days, 90 days or 1 year; click a person or a record id to filter by it. 100 entries per page; there is no export. Admin only. |
ArkCloud RCM → Administration → Audit Logs
Examples of what is recorded
- Successful and failed sign-ins, account locks and unlocks.
- User created, updated, deactivated and reactivated; password resets; forced sign-outs; MFA disabled by an administrator.
- Changes in Access (referrals, registrations, consents, signatures), Rehab and RCM records, written by the actions that make them.
- Openings of patient record screens, in the PHI access log. Lists and search results are not all logged row by row, and a CSV built in the browser is not logged.
Integrity and tamper resistance
| Field or control | What it means |
|---|---|
| No edits from the application | The application's database role cannot delete entries in the activity log, the hash-chained log or the PHI access log, or change their contents. The one thing it may set is an archive date on hash-chained entries. |
| Verify Integrity | Checks that every entry links to the one before it and, for entries written from 2 October 2026 on, recomputes each entry's hash so an edited entry is detected. Older entries are checked for linkage only, which detects a deleted or reordered entry but not an edited one. |