Blog · · 7 min read
Privacy in Medical Phone Calls: Handling Health Data with Voice AI
Clinic callers mention symptoms and history. What Japan's APPI and official guidance say about health data, outsourcing and overseas processing, and how to collect less.
Key points
- Under Japan's APPI, medical history and clinical information are "special care-required personal information," and acquiring it generally requires the person's prior consent (Articles 2(3) and 20(2)).
- A clinic phone agent should collect only what booking needs, hand medical questions to staff, and keep diagnoses out of calendar titles and notifications.
- When audio goes to an outside AI platform, the clinic has to check its supervision duties toward contractors (Article 25) and, if processing happens abroad, the rules on providing data to third parties in foreign countries (Article 28).
Put a voice agent on a clinic's phone line and health details will come up whether you ask for them or not: "I've had a fever since Tuesday," "I'm already a patient for my back." In Japan, that kind of information is "special care-required personal information" under the Act on the Protection of Personal Information (APPI), and it carries stricter rules than a name or phone number, starting with a general requirement for prior consent to acquire it. The practical starting point is to design the agent to collect only what booking needs, and to map exactly where call audio goes, including any processing outside Japan.
This post summarizes what the official sources say; it isn't legal advice. Whether a particular clinic's setup complies is for the clinic to determine against the original texts, with professional advice where needed. Sources were checked on 2026-10-03. If you serve patients in the US, HIPAA applies instead and is out of scope here (HHS).
What counts as sensitive on a clinic call
The APPI defines special care-required personal information as personal information containing a person's race, creed, social status, medical history, criminal record, the fact of having been a victim of crime, or other descriptions specified by Cabinet Order that require special care so as not to cause unfair discrimination or prejudice (APPI, Article 2(3), official English translation). Guidance for medical and care providers from Japan's Ministry of Health, Labour and Welfare (MHLW) and the Personal Information Protection Commission (PPC) lists, as typical examples in a medical setting, medical history recorded in clinical records, clinical information learned during treatment, and health checkup results (MHLW guidance page, in Japanese, last amended April 1, 2026).
Sorted by sensitivity, the information on a typical booking call looks like this:
| Comes up on the call | Category |
|---|---|
| Name, phone number, preferred date and time | Personal information |
| Patient ID number (for identity checks) | Personal information |
| Symptoms, diagnoses, visit history, medications, checkup results | Can be special care-required |
Booking rarely needs anything beyond the first two rows. The third row will still come up because callers volunteer it, so decide in advance what happens when it does.
What the official sources require
Consent to acquire sensitive data
Except in cases such as those based on law, acquiring special care-required personal information requires the person's prior consent (APPI Article 20(2); PPC general guidelines, section 3-3-2, in Japanese).
For clinic reception desks, the MHLW guidance takes the view that a patient who fills in a medical questionnaire and asks to be seen is presuming the clinic will acquire that sensitive information, so when the clinic acquires it properly and directly from the patient, in writing or orally, consent can be read from the patient's own action. Whether a phone agent falls within that reasoning, and how far it should ask, is a judgment for the clinic based on the original text.
Supervising contractors
When a business outsources handling of personal data, it must supervise the contractor appropriately (APPI Article 25). The MHLW guidance spells this out: choose contractors that handle personal information properly, put handling rules in the contract (including what happens after the contract ends), and decide how subcontracting is handled. A phone agent can create several layers, from clinic to telephony vendor to voice AI platform to speech and LLM APIs, so drawing the data flow on one page makes the review much easier.
Processing outside Japan
Providing personal data to a third party in a foreign country generally requires prior consent, unless the recipient is in a country the PPC recognizes as having an equivalent system or has a qualifying data protection framework in place (APPI Article 28; PPC guidelines on overseas transfers, in Japanese). On cloud services, the PPC's official Q&A (in Japanese) says the test is whether the cloud provider is set up to handle the personal data (Q7-53), and that storing data on a foreign server isn't a foreign transfer if the provider is not set up to handle it (Q12-3). A voice AI necessarily processes conversation content to transcribe and answer, so you need to know which countries the platform and its upstream APIs run in.
Breaches
A leak, or possible leak, of personal data that includes special care-required information must be reported to the PPC and notified to the people affected (APPI Enforcement Rules, Article 7(1); restated in the MHLW guidance). Limiting where transcripts and summaries are stored, and who can read them, is the first line of defence.
For medical information systems, the MHLW guidance also points to MHLW's security guidelines for medical information systems (in Japanese; version 7.0 as of October 2026). Vendors have their own guideline from the Ministry of Economy, Trade and Industry and the Ministry of Internal Affairs and Communications (METI, in Japanese).
Design choices that collect less
Independent of the legal analysis, you can design the agent so sensitive data is less likely to be collected or spread.
- Collect only what booking needs. Name, callback number, preferred time, new or returning patient. Don't add a "what's the problem?" field.
- Hand medical questions to staff. "Can I take this with my medication?" belongs in the handoff conditions, not in the FAQ (designing AI-to-human handoff).
- Keep diagnoses out of visible places. Calendar titles show up on front-desk screens; use something like "Appointment (Yamada)". Keep symptoms out of Slack or Teams notifications too.
- Verify identity in the booking system. Let the booking system check the patient ID the caller gives and return only a yes or no to the model. A matching caller number doesn't prove who is calling, so use it only to find the patient.
- Tell callers up front that an AI is answering and the call is recorded (telling callers they're talking to an AI).
- Decide where transcripts live and when they're deleted, in line with the clinic's own rules.
Doing this with voicast
In voicast you define the fields to collect (fields) and the handoff conditions (handoff_when) in the agent config. Booking systems and calendars are connected through in-call tools (config.tools) that call a server on the provider's side, so that server decides event titles and what gets stored. Keep titles to something like "Appointment (Mr. Yamada)" and put the reason for the call only in the notes. Have the identity-check tool return only the result, never the date of birth or patient ID number. The AI does not say anything that isn't in a tool result, so the fewer fields you return, the less information enters the conversation. When you forward post-call webhooks to Slack or similar, your receiver chooses which fields to send. Before anything is sent to error monitoring, transcripts, collected fields and phone numbers are stripped.
voicast also combines speech recognition, LLM and speech synthesis APIs from providers in and outside Japan, so call audio and conversation content may be processed outside Japan. If you deploy it for a clinic, review that against the Article 28 materials above and decide what notice or consent is needed. Contact us if you need more detail for that review.
FAQ
Can a phone agent ask callers about their symptoms?
The APPI doesn't forbid acquiring sensitive data, but it generally requires prior consent (Article 20(2)). Booking usually works without symptoms, so the safest default is not to ask, and let the clinic decide against the MHLW guidance if it truly needs them.
What if a caller volunteers a diagnosis anyway?
You can't stop people from saying it, so assume it will end up in the transcript or summary. Decide where those are stored, who can read them and when they're deleted, and keep that information out of widely visible places like calendar titles and chat notifications.
Does overseas processing rule out using AI for clinic calls?
The sources don't say that. Article 28 requires prior consent for a foreign transfer unless the recipient is in a recognized country or has a qualifying framework, and the Q&A explains when cloud use isn't a "transfer" at all. Which case applies is for the clinic to check using information from the vendor.