Guideline answers must be auditable. Here are the controls we run in the CliniSearch proxy before any answer reaches the clinician interface.

See how this translates to practice: Explore our Clinical governance features, visit the Patient Safety Hub, or review Clinical Safety & Assurance for enterprise rollout.

Audit trail by default

Every search from user2 and user4 pages is logged with the query, response snippet, full payload, user email, IP, user agent, and correlation ID. This happens asynchronously so clinicians are never blocked by logging.

Version-aware responses

We track which guideline version a recommendation came from. If a source updates, CliniSearch refreshes embeddings and clearly marks the new publication date in responses.

Proxy controls

  • Normalises specialty codes to prevent malformed requests to the backend.
  • Injects requested_by from the authenticated user so every query has an owner.
  • Sets a default synthesis_type to keep response shape predictable.

Why this matters for governance

Governance teams need to know who saw what, when, and from which guideline version. With audit logs, pinned versions, and proxy validation, CliniSearch provides that trace without slowing down the clinician path.

If you want to see the audit model in your environment—or need custom fields added to the log—reach out. We are happy to adapt it to your governance requirements.