Before switching on any AI voice assistant, from any vendor, a hospital should get written answers to these questions: where is patient data processed and stored, and does it leave the country; is the caller informed at the start of the call; how is the ID number collected; who can see call content, and is every access logged; and how long are recordings kept. This guide gathers a checklist you can apply to any vendor, why each question matters and how Dorsera Health answers each one in a single table, then explains how to verify the answers.
KVKK is Türkiye’s personal data protection law; the checklist is written for hospitals in Türkiye.
This guide is not legal advice; the final assessment belongs to your hospital’s data protection adviser or legal team.
Why does an AI voice assistant need its own KVKK review?
Because a single phone call collects voice, an ID number and health information at the same time, and health data is a special category of personal data under KVKK. Unlike a web form, this data arrives as speech, is turned into text and is processed by an AI model.
A voice assistant is usually made of several parts: speech recognition that turns speech into text, a language model that produces the answer, speech synthesis that voices it, and storage where records are kept. These parts can run on different services in different countries. That is why “where is the data?” needs an answer for every link in the chain, not just one.
Which questions should you ask the vendor?
The table below collects the questions to put to any AI voice assistant vendor. The last column is Dorsera Health’s answer; hold us to the same standard.
| # | Ask the vendor | Why it matters | Dorsera Health’s answer |
|---|---|---|---|
| 1 | Where are voice, transcripts and identity data processed and stored? | Health data is a special category; speech recognition, the language model and storage may sit in different places | All three are processed and stored in Türkiye |
| 2 | Is data transferred abroad? | Transfers abroad are subject to separate conditions under KVKK | It is not transferred abroad |
| 3 | Is the caller informed at the start of the call? | People must be informed when their data is collected; the caller should know they are talking to an AI | The caller hears they are speaking with an AI assistant; the KVKK privacy notice can be heard with one key press |
| 4 | How is the national ID number collected? | A spoken number ends up in the recording and transcript, and can be misheard | The national ID (TC) number is typed on the phone keypad and never spoken |
| 5 | Who on the hospital side can see call content? | Only people who need it for their work should access the data | Role-based access: only authorised people can see it |
| 6 | Is every access to call content logged? | Who saw what and when must be answerable in a review or a complaint | Yes, every access is recorded in an audit log |
| 7 | How long are recordings and transcripts kept, and what happens when the period ends? | Data should not be kept longer than its purpose requires | Set in the contract |
| 8 | For what purposes is call data used? | Data should be processed only for the stated purpose | Set in the contract |
| 9 | How are the data controller and data processor roles split, and are there sub-processors? | Who is responsible for what in a breach must be clear from the start | Set in the contract |
| 10 | How and when is the hospital told about a data breach? | The hospital’s own notification duty depends on it | Set in the contract |
| 11 | What does the assistant read from the HBYS? | The assistant should not access more than its job needs | It reads for identity verification, free slots and the consultation fee, and writes appointment actions |
| 12 | Can a record be written without the caller’s confirmation? | A misheard “yes” means wrong data in the patient’s record | Nothing is booked, cancelled or moved until the caller presses 1 |
| 13 | Does the assistant give medical advice? | Patient safety; an AI making a diagnosis is not acceptable | It gives no medical advice and makes no diagnosis; when needed, it hands the call to the team |
| 14 | When is the caller passed to a person? | Complaints and special cases must reach a human | When the caller asks, has a complaint, or the assistant cannot resolve the request, the call is transferred with its context or a call-back request with a note is opened |
HBYS is the hospital information system, the Turkish term for a hospital’s patient and appointment system. Rows marked “set in the contract” are matters that vary by hospital or must be fixed in writing. Do not close them on a vendor’s verbal answer.
No single department should fill the list in alone. Data location and access logs concern IT, the privacy notice and retention concern the legal team, and hand-off rules and medical limits concern patient services. When all three read the same table together, gaps in a vendor’s answers show up sooner. To the caller, the assistant is the hospital’s voice; when something goes wrong, the patient remembers the hospital, not the vendor.
How do you verify the answers?
Do not settle for verbal answers: call the demo line, ask for the data flow in writing, see the panel, and put the rest in the contract.
- Call the demo line. Are you told you are speaking with an AI, can you hear the privacy notice, is the ID number requested on the keypad? You will hear all of this in one call.
- Ask for the data flow in writing. For speech recognition, the language model, speech synthesis and storage, ask in which country data is processed and stored.
- See the panel. Ask for a live look at role definitions and the access log; check whether you can see who opened which call.
- Put the open items in the contract. Retention period, purposes of use, roles, sub-processors and breach notification should be in writing.
- Update your own side. Review your hospital’s privacy notice and data inventory with your legal team so they cover the new channel.
Which answers are warning signs?
Ask more questions when you hear any of these:
- “The data is in the cloud,” with no country named.
- A separate location is named for speech recognition or the language model, and it is abroad.
- The assistant asks for the ID number out loud.
- The caller is not told they are speaking with an AI.
- The retention period is not put in writing.
- Access to call content is not logged.
- The assistant listens to symptoms and comments on them medically or hints at a diagnosis.
Where does Dorsera Health stand on this list?
With Dorsera Health, voice, transcripts and identity data are processed and stored in Türkiye; the caller is informed at the start of the call, the ID number is typed on the keypad, and every access to call content is logged. The assistant is live-connected to the HBYS and writes the appointment during the call, only after the caller confirms on the keypad; how it works is covered step by step in our guide to the HBYS-integrated AI phone assistant. That is why we describe Dorsera Health as the only AI phone assistant in Türkiye that is KVKK compliant and live-connected to the HBYS. Items that vary by hospital, such as the retention period, we set in writing in each hospital’s contract.
Try it yourself
You can test the first four items of the list in one phone call. Call the Dorsera Demo Hospital line: +90 312 203 68 00. For the rest, book a demo at health.dorsera.com and bring your questions in this table.