Audit Log

What is recorded

Changes to tracked records are stored in the background. Every line holds:

• The action — record created, updated or deleted
• Which record — its type and id (patient, quote, consultation, user…)
• Who — the user who did it; the link survives even if that user is later removed
• What changed — the previous and new values of the fields
• From where — the address the request came from

Keeping the link to a deleted user is a small but important detail: what someone did in their last weeks does not vanish when their account is removed.

Why it matters

• Staff turnover — What a departing consultant did in their final weeks becomes something you can check — which records they reassigned, which statuses they changed.
• Disputes — "I never sent that quote" and "that patient was assigned to me" end at the log.
• Tracing data loss — Why a record looks empty — deleted or overwritten — can be traced afterwards.
• Compliance — Health data is a special category; being able to trace access and changes is one of the technical measures expected under GDPR and KVKK.

Which records are tracked

Auditing is not tied to one screen: patients, quotes, consultation rooms, users and other core record types are covered. Once a record type is tracked, every change to it is logged regardless of where it came from — the interface, the mobile app or the API.

The AI side is no exception: writes made through the MCP gateway keep their own access log as well, recording which key changed which record, with old and new values.

Who can see it

The audit log sits behind a permission, and it should: it holds previous states of records, which in the wrong hands is a way to read back deleted information. Who gets access is decided when the team is set up; in practice it stays with management and whoever administers the system.

Related pages