Admin only — Only administrators can view audit logs.
What gets logged
The platform automatically logs every significant action in the system. You do not need to enable logging — it runs by default and cannot be turned off. Logged actions include:- Record creation — New patients, appointments, invoices, clinical notes, and other records
- Record updates — Changes to existing records, including which fields were modified
- Status changes — Appointment status transitions, invoice payment updates, claim status changes
- Document views — When a user opens a patient record, clinical note, or financial document
- Login events — Successful and failed login attempts
- Permission changes — Role or permission modifications for staff members
- Data exports — When reports or records are downloaded or exported
Anatomy of a log entry
Each audit log entry captures:| Field | Description |
|---|---|
| Who | The user who performed the action (name and role) |
| What | A description of the action and what was changed |
| When | Exact timestamp of the action |
| IP address | The IP address from which the action originated |
| Device | Browser and device information (user agent) |
Querying audit logs
The audit log viewer provides powerful filtering to help you find specific events quickly.Filter options
Date range
Select a start and end date to narrow results to a specific time window. Useful for investigating incidents that occurred on a known date.
Action type
Filter by the type of action — creation, update, deletion, view, login, etc. Helpful when you are looking for a specific kind of event.
User
Show only actions performed by a specific staff member. Use this to review an individual’s activity history.
Patient
Filter by patient to see every action taken on or related to a specific patient record. Critical for patient-specific audits.
Apply filters
Use the filter bar to select your criteria — date range, action type, user, patient, or any combination.
HIPAA compliance
Our audit logging is designed with healthcare compliance in mind. The system follows a principle of access logging without content exposure:- When a user views protected health information (PHI), the log records that the record was accessed and by whom
- The log never captures the actual medical content — no clinical note text, diagnosis details, or treatment information appears in log entries
- This approach satisfies HIPAA’s audit trail requirements while ensuring that the logs themselves do not become a secondary PHI repository
What HIPAA flagging looks like
When a user accesses protected health information, the log entry includes a PHI access flag. This flag indicates that the action involved health data without revealing the data itself. For example:- “Dr. Ahmed viewed clinical notes for patient DN6K-M9P2” — flagged as PHI access
- “Reception updated phone number for patient DN6K-M9P2” — not flagged (contact info update, not clinical data)
Common audit scenarios
Investigating a data access concern
Investigating a data access concern
If a patient or staff member raises a concern about unauthorized data access, filter audit logs by the patient’s name and review all access events. The log shows exactly who viewed their records, when, and from what device.
Reviewing staff activity after departure
Reviewing staff activity after departure
When a staff member leaves your clinic, review their recent activity in audit logs before deactivating their account. This helps identify any unusual last-minute access patterns.
Compliance audit preparation
Compliance audit preparation
Before an external audit, filter logs by PHI access events over the relevant period. Export or screenshot the results to have documentation ready for auditors.
Tracking record modifications
Tracking record modifications
If a patient’s record appears to have incorrect information, use audit logs to trace every modification back to its source. The log shows what was changed and by whom.
Retention
Audit logs are retained for the lifetime of your clinic’s account. There is no automatic purging or rotation. Historical logs remain accessible regardless of how long ago the events occurred.Best practices
Review logs regularly
Review logs regularly
Do not wait for an incident to check audit logs. A monthly review of access patterns helps you spot unusual behavior early.
Use patient-specific filters for access requests
Use patient-specific filters for access requests
When a patient exercises their right to know who accessed their records, the patient filter gives you a complete access history in seconds.
Document your audit review process
Document your audit review process
Keep a record of when and why you reviewed audit logs. This demonstrates proactive compliance management during external audits.
Related articles
- Security Settings — Configure 2FA, passkeys, and login policies
- Staff Management — Manage access and deactivate departing staff
- Roles & Permissions — Understand who can access what

