LIS - Audit (field-level change history by module)
Use Audit to review a detailed, field‑level history of adds and changes within each audited area of the LIS. Every major module (e.g., Orders, Requisitions, Results) has its own dedicated Audit, tailored to that record type. Audits provide a granular view of who did what, when, and how a record changed across time.
What you can see (typical)
- User, date/time, and action (add, edit (update))
- Field‑level changes with old value → new value
- Record identifiers and context (order/requisition/results)
Common uses
- Compliance and accreditation documentation
- Root‑cause analysis for discrepancies
- Training and process improvement
- Security and access oversight
📘 Instructions: Use the Audit features
Open the module‑specific audit
- Click Audit from the menu and choose the record (order, requisition, patient).
Filter to the records of interest
- Use the Audit Search filters (use the advanced grid filters) to narrow results.
Open record details
- Select a row in the results grid and click the information icon.
Drill into the audited record
- In the pop‑out Details Audits window, select the record from the grid to view its audit trail.
Expand entry history
- Click the expand arrow on the left to view the user entry history; select the specific history row you want to analyze.
View change details
- Click the history information icon to open the Change Details pop‑out and review field‑level old/new values and timestamps.
Tips and best practices
- Start broad (date/user) then refine filters to isolate specific records or events.
- Use consistent identifiers (order number, requisition number) to jump directly to a target record.
- Capture rationale in user comments where available, these appear in audit review and speed investigations.
- Export or screenshot key audit views for accreditation binders or incident reviews, per your policy.
Note: Audit is read‑only and scoped per module. To correct data, use the appropriate form (e.g., Result Corrections) so changes are properly logged and visible in Audit.

For additional help, please contact our support team.