Patient data and models do not mix. Unless you govern every call.
Hospitals, clinics and health-tech companies run agents for triage, documentation and clinical decision support. TapPass makes sure patient data never reaches a model unprotected, and shows the trail to your DPO without a reconstruction project.
✓Free for one person · No credit card needed
Agents already sit next to patients. In triage, notes and research.
Three agents hospitals and health-tech teams run, and what TapPass watches on each.
Names, MRNs, ICD codes and medications are removed or tokenised, so the model never sees the real data.
Free text is scanned for injected instructions before the agent acts on it, and clinical decisions stay with a clinician.
Session boundaries keep clinical and research context apart, so de-identified data stays de-identified.
Why healthcare AI needs a governance layer. Patient data has the highest protection.
Patient data is GDPR Art. 9 special category data. Agents in healthcare work in a regulatory minefield.
Clinical caution, as rules. Not as a policy document.
Your DPO, medical director and security team each say what must never happen. TapPass makes it a rule.
Runtime governance for healthcare AI. Every patient data touchpoint.
Detect, block and record every model call and every tool call that touches patient data.
Article 9, Article 17 and the AI Act. In one record.
What each rule asks of you, and the part of the answer TapPass gives you.
| Regulation | What it asks | What TapPass gives you |
|---|---|---|
| GDPR Art. 9Special category data | Explicit consent and strict safeguards when processing health data. | Patient identifiers removed or tokenised before any model, by rule, with the redacted text on the record. |
| GDPR Art. 17Right to erasure | Erase a patient’s data on request. | Cryptographic erasure with tombstones, a signed erasure receipt, and a hash chain that still verifies. |
| EU AI Act Art. 12Record keeping | Automatic logs for high-risk AI such as medical AI. | Every AI decision on a tamper-evident record: what went in, what came out, which rule applied. |
| EU AI Act Art. 14Human oversight | People who can oversee and stop the system. | Clinical recommendations held for the treating clinician, signed with a passkey. |
| MDRMedical Device Regulation | Safety and oversight for software used in clinical care. | TapPass is not a medical device. It keeps a person on clinical decisions and records what the agent contributed, which supports the evidence in your own MDR file. |
No feature guarantees a compliance outcome. TapPass gives you the controls and the evidence that make your own answer defensible.
Proof you can check. Not logos you have to trust.
We do not put customer names on a page unless we can show you the work. Here is what you can verify yourself, on your own agents.
Connect one agent in watching mode. TapPass records what it would have allowed, held, redacted or blocked, and nothing is blocked while you learn.
The same rule and the same call give the same verdict, every time. Replay a decision for your auditor, or a draft rule over last week’s traffic.
Security controls, subprocessors, and a DPA on request. Hosted in the EU, built in Belgium.
What we can show you today is the product on your own agents, the documentation behind every control in the Trust Center, and a team that answers your security questionnaire itself.
Does a model ever see patient names?
Not if your rules say so. Names, MRNs, ICD codes and medications are detected and removed or tokenised before the call leaves, and restored in the answer where needed.
Can we erase a patient’s data without breaking the audit trail?
Yes. TapPass uses cryptographic erasure with tombstones: the data is gone, you get a signed erasure receipt, and the hash chain is recomputed so the record still verifies.
Can an agent make a clinical decision on its own?
Only if you allow it. Clinical recommendations can be held for the treating physician, and outputs are scanned for unsupported medical claims.
Can TapPass run inside the hospital network?
Yes. On Enterprise, TapPass runs on your own servers, so no patient data leaves your network.
Patient data deserves more than a privacy policy. Govern every call that touches it.
Connect one agent and see every call TapPass would have held, stopped or routed elsewhere. Nothing is blocked while you learn.