solutions · healthcare
Wytness for healthcare
Audit agent activity touching patient data, without sending the patient data to your audit vendor.
the question every regulator asks
Can you produce the evidence?
HIPAA §164.312(b) demands audit controls over every system touching electronic PHI; GDPR Article 9 makes patient data special-category; the EU AI Act puts healthcare triage in Annex III high-risk. The structural problem is that traditional audit logging ships the data being audited to the place it's audited from — and when the auditable event is a prompt carrying a patient's name, condition, and history, shipping it to a third-party SaaS is a HIPAA-disclosure event of its own. Wytness tokenises PHI in your runtime; the audit trail reaches us already sealed.
a scenario
A privacy-counsel review, with and without
A Melbourne digital-health startup triages six hundred GP referrals a day with an AI agent — reading free-text letters, extracting Medicare numbers and conditions, routing to specialists. Two clinic groups it sells into have a HIPAA-covered US parent. Counsel asks: prove no Medicare identifier ever left Australia readable, show which referrals were auto-routed without a clinician, and produce the chain of custody on one referral a patient is disputing.
Without Wytness that's Datadog traces, OpenAI logs they can't export, and a Postgres table — each containing the very PHI the question is about. With it, it's one signed export: pseudonymised patient tokens, tool calls, model versions, clinician approval flags, and the policy fingerprint each routing was evaluated against. The Medicare numbers never appear because they never left the runtime. One meeting, closed.
// Event identity:
// What the agent did:
// Parameters (PHI tokenised before this row was sealed):
// Integrity proof (3-layer):
one referral fetch from the scenario — PHI arrives as tokens we cannot reverse
the deliverable
What you can prove
- ✓Which agent accessed which patient record, with what tool, and on whose authority, to the granularity §164.312(b) calls for.
- ✓That PHI never left your environment in plain form: pseudonymisation happens in your runtime, before any event reaches Wytness.
- ✓That clinical-decision-support agents stayed inside their scope and did not retrieve records belonging to patients outside the current encounter.
- ✓That a tool destination never received a PHI field unless an approved tool path required it.
- ✓That a breach investigation can reconstruct, for a specific patient, every agent interaction touching their record in the last seven years.
how the surfaces map
Three surfaces, one product.
/product/ledger
Ledger
Every action signed with your browser-generated key; PHI pseudonymised in your code before egress. Re-identification runs in your runtime on demand — Wytness holds tamper-evident metadata, never the patient data behind it.
/product/registry
Registry
Inventory of every clinical agent and PHI-touching tool call. Anomaly rules flag cross-encounter contamination, off-hours retrieval, destinations outside the BAA list, and behaviour shifts after a model upgrade that need clinical safety re-review.
/product/shield
Shield
High-risk actions — releasing PHI externally, suggesting medication changes, generating billing codes — gated behind the approval workflows your clinical governance team already runs.
for your auditor
Frameworks that matter here
SOC 2 Type II
Trust services criteria for the audit pipeline itself.
ISO 27001:2022
Pairs with ISO 27799 for the health-sector profile.
EU AI Act
Annex III §5(a) covers AI used in healthcare access and triage.
GDPR
Article 9 special-category data underpins all EU health-AI work.
HIPAA Security Rule
§164.312(b) audit controls — control matrix in progress.
NIST AI RMF 1.0
MEASURE and MANAGE support via the signed trail — in progress.
HITRUST CSF v11
Framework alignment available on request.
the boundary
What Wytness does not do
- —We are not an Electronic Health Record. We log what your agents did against your EHR (Epic, Cerner, AthenaHealth, or your own); we do not replace it.
- —We do not sign Business Associate Agreements at launch. BAA readiness is gated on the vendor-side controls a HIPAA-covered customer requires from sub-processors; we are honest about this with every healthcare prospect and will revisit as the customer-controlled-key model and pen test close the relevant gaps.
- —We do not provide clinical content review. A Wytness audit trail evidences what happened; whether it was clinically correct remains your clinical governance team's call.