Protocols & Audit

Every decision logged.
Every protocol versioned.

AfterHours Ally was designed from day one around defensible records — not as an afterthought. The protocol engine and audit layer are the product, not a compliance checkbox.

Protocol Engine

Clinic-configurable protocol trees

Each clinic maintains its own species × age × symptom decision tree. Protocols are edited in the dashboard, previewed, and published with a version stamp. The live triage engine always runs the latest published version — draft changes never reach owners.

Board-reviewed defaults included

AfterHours Ally ships with a baseline protocol set covering the most common small-animal after-hours presentations: GI, respiratory, trauma, toxin exposure, neurological, and obstetric. Your DVMs review, edit, and sign off before going live.

Deterministic urgency scoring

Urgency is produced by a rule engine — not a language model. Weights and threshold criteria are version-controlled alongside the protocol. Red-flag triggers (e.g., suspected toxin, respiratory distress, open fracture) always escalate, regardless of any other factor.

Versioned protocol history

Every protocol revision is stored with author, timestamp, and diff. If a question arises about what protocol was in effect during a specific interaction, you can pull the exact version that ran — down to the branch logic.

Audit Record Schema

Every triage session writes an immutable record. Fields are append-only — no record can be edited or deleted after creation.

FieldDescription
session_tokenUnique, immutable identifier for each triage session
started_at / completed_atISO-8601 timestamps for session open and close
consent_versionDisclaimer version acknowledged (e.g., v2.0-tcpa-2025)
ip_hashSHA-256 of the owner's IP — stored but never re-identified
species / age_groupPatient classification from first protocol branch
urgencyFinal score: immediate / urgent / routine / self-care
protocol_domainTop-level symptom category matched (e.g., respiratory)
step_countNumber of protocol steps traversed
escalation_idForeign key to escalation record if a DVM was paged
ack_atTimestamp of on-call DVM acknowledgement (if applicable)
channelDelivery channel: web, sms-relay, email-link

Export Formats

📊

CSV — Audit events

All escalation, consent, and system events in chronological order. Ideal for incident review.

📋

CSV — Interactions

Session-level log with urgency, protocol, step count, owner contact. Import into spreadsheet or BI.

⚙️

JSON — Full export

Complete structured dump of all interactions, escalations, and audit events. Use with your PMS or data warehouse.

📄

PDF — Report bundle

Formatted audit summary for insurance submissions, AVMA reviews, or board meetings.

All exports are available from the Audit dashboard. Exports are scoped to your clinic and require an authenticated session. No export is available to the public or to owners.

Live Dashboard

Real-time audit access — no lag, no exports required for daily review.

The Audit dashboard shows every interaction in reverse-chronological order with urgency badges, escalation flags, and consent versions. Filter by date range, urgency level, or DVM. Flag individual sessions for follow-up. Access is gated to authenticated clinic users only.

Access your dashboard →

See it live in your browser.

The demo runs a real protocol — no sign-up required.