Industry
Healthcare
Health data is a special category under KVKK art. 6 and carries a stricter regime. Here the default may be block rather than mask.
What is at stake here.
Special category means a different threshold
Masking is enough in most contexts; for a special category, stopping the request outright may be preferable.
Identity fields are dense to begin with
A patient record holds national ID, phone, address and date of birth together.
Nothing may be allowed to leave
In local-model mode no request leaves the machine; verification degrades to the lexical fallback rather than switching off.
Why it is not optional
Patient data leaves no margin for error.
Where a legal duty is the reason, the article is named. No penalty figures and no circular numbers — those change, and a marketing page is the wrong place to be wrong about them.
Health data is special-category
KVKK art. 6 treats health data as special-category; processing and transferring it is bound by narrower conditions than ordinary personal data.
A fabricated answer costs differently here
In another sector a wrong answer is a mistake. In a clinical context it is text that supports a decision. That is why failing closed has to be the default.
It has to work without reaching the internet
In local-model mode no request leaves the machine; a deployment that never moves data off the hospital network is possible.
Use cases
What actually happens in the day's work.
These are mechanisms, not case studies. Each one is a concrete thing somebody does, and what the chain does about it.
Summarising a patient note
Situation
A clinician pastes a discharge summary or patient note and asks for a summary or a rewrite.
What happens
Identity and contact fields are masked; the clinical content is preserved, because that is the part that makes the summary useful.
A patient lookup at the call centre
Situation
An operator looks a patient up by identity number and asks about their appointment.
What happens
The identity number becomes a token; the answer is resolved for an entitled user and stays masked for one who is not.
A clinical question with no source
Situation
Someone asks a treatment question the knowledge base has no source for. The model would still produce a fluent answer.
What happens
The grounding step closes here: with no source, the model is not let loose. In a clinical setting a quiet invention is worse than no answer.
The answer
Which part of the product responds.
Configuration
Recommended starting posture.
These are starting recommendations; the final policy is written with you during setup.
- Priority entity types
- TR_TCKNDATE_TRADDRESS_TRPHONE_TR
- If the policy cannot be read
- stop
- Deployment
- On-premise or air-gapped
The rules get written together
The rules for this sector are written with you during onboarding: blocked phrases, the competitor list and the entity rules are set against your own processes. Instead of adapting someone else's template, you start with a policy that is genuinely yours — and it goes live only after being tried in the simulation that runs without saving.
Other industries
Let's talk through your own scenario.
In a 30-minute technical session we run your prompts and your policy through it live.