Healthcare
Less paperwork for clinicians, with rules around patient data.
Agents can take paperwork off clinicians and administrators: summaries, referrals, scheduling. Kyvvu makes sure they only touch patient data with consent, never run code, and never send records where they shouldn't go.
The problem
Patient data needs extra care.
- 01
Consent before access
Health data is special-category data. Accessing a record needs a valid basis, every time, not just when the agent was built.
health data
- 02
Security standards apply
NEN 7510 in the Netherlands, HIPAA in the US: information security rules that agents have to follow like any other system.
NEN 7510/HIPAA
- 03
Clinicians stay accountable
Whatever an agent drafts, a clinician signs. They need to trust that it didn't do anything on the way.
clinical accountability
In practice
Patient safety rules, enforced.
No record access without verified consent
A referral agent needs a patient's record to draft a referral letter. It tries to open the record before consent has been checked.
Illustrative scenarios. Each one is decided by a single policy from the open policy library, as the engine evaluates it. References to laws and regulations are our reading of them, to show how a policy maps to an obligation. Not legal advice.
How Kyvvu helps
Rules for patient data, ready to assign.
- 01
A healthcare policy pack
Consent before patient data access, approved healthcare domains only, no code execution for high-risk agents, mapped to NEN 7510 and HIPAA.
NEN 7510/HIPAA pack
- 02
Runs inside your environment
The engine sits in the agent's own process: so there's no proxy or extra network hop, and a check takes under a millisecond. Prompts and data stay with you.
in-process/no proxy
- 03
Hosted or yours
Use platform.kyvvu.com, or run the platform in your own infrastructure, on-prem or air-gapped, on Enterprise & Public.
hosted/self-hosted/air-gapped
- 04
A record of every step
Each task is recorded as an ordered trace of its steps with the verdict on each, hash-chained when it reaches the platform.
logs/traces
Questions
Common questions.
01Does patient data reach Kyvvu?
No. The engine decides inside the agent's process. Traces of steps go to the platform unless you keep them on your own machines, and on Enterprise & Public you can run the platform yourself.
02Can we restrict which systems an agent talks to?
Yes. The healthcare pack includes an allowlist of approved domains, such as your EHR and FHIR endpoints.
03Does Kyvvu make clinical decisions?
No. It controls what an agent may do, and records what it did. Clinical decisions stay with clinicians.
Get started
Every agent has to ASK before it acts.
Start with one agent
See it on your own agents
A 30-minute demo with someone who builds Kyvvu: your agent, your rules, and the policy that decides each step.
The policy pack
NEN 7510 and HIPAA, as policies
Read the healthcare pack: each policy, what it maps to, and the YAML.
Want to see other teams and sectors? All use cases.