Access and communication

The patient who cannot describe the problem in your language

In a country where a waiting room holds Hebrew, Russian, Arabic and English in the same hour, the language question arrives before the clinical one. Most of it is administrative and safe to answer in whatever language it was asked. The part that is not safe is the part clinics most often improvise, usually by asking whoever came along to translate.

The language of the conversation is not the language of the record

A patient can ask about parking in Russian and be answered in Russian without anything following them into the chart. The distinction worth drawing before any software is switched on is between information the clinic publishes, which may be rendered in any language freely, and clinical content, which may not. An assistant that translates a symptom description into the clinician's language has done something nobody asked it to do and nobody can check. Let it carry the question verbatim, in the language it was typed, and let a person decide what that means.

A family member is not an interpreter, and the clinic should say so

The adult son who comes along to translate is doing a kindness and creating a problem: he edits, he softens, he answers on his mother's behalf, and he is present for a conversation she might have had differently alone. A child doing the same is worse. Clinics rarely state a position on this because stating it feels unwelcoming, so the position gets improvised at the desk. Publish it instead, in plain words, in every language you serve: when the clinic arranges an interpreter, when a relative may help, and which conversations require neither.

What translates safely, and what needs a person

Opening hours, directions, what to bring, which insurers are accepted, how to cancel, whether a referral is needed - all of it is publishable text and all of it can be answered in four languages without risk. A symptom, a medication name, a dosage, a result, an instruction after a procedure: none of these belong to an assistant in any language, and the reason is not translation quality. It is that the patient will act on the answer. The line is the same line as everywhere else in the practice, and language does not move it.

Record the need before the appointment, not at the door

An interpreter has to be booked, and the clinic finds out it needs one when the patient is already standing there. The cheapest fix has nothing to do with language technology: ask the question at the point of booking, in the patient's own language, and write the answer where the clinician will see it. One field, filled in days earlier, removes the appointment that gets rebooked because nobody could conduct it.

Frequently asked questions

Can an AI assistant act as our interpreter?
No, and that is not a limitation to work around. It can answer administrative questions in the patient's language, which is most of the traffic, and it can record that an interpreter is needed. Interpreting a clinical conversation is a role with professional standards attached, and software holding a conversation in two languages is not the same thing as meeting them.
Which languages should a clinic in Israel actually cover?
Hebrew, Russian, Arabic and English cover most of what a general practice sees, and the right answer for your clinic is in your own enquiry log rather than in a national statistic. Read the questions that arrived in a language you do not publish in - that list is short, specific and more useful than any assumption about your catchment.
Does the assistant detect the language, or does the patient choose?
Both, and it matters that the patient can override. Detection from the first message is right most of the time and wrong in the case that matters: someone typing in a second language because they assume the clinic has no other. A visible language control costs nothing and removes that assumption.
What happens to a question we cannot answer in that language?
It should be handed to a person with the original wording intact, not a translated summary of it. A summary is a second author's account of what the patient said, and the clinic cannot tell which parts are the patient's. Keep the original, note the language, and let whoever picks it up read what was written.
Is a translated website enough on its own?
It covers the reading and not the asking. A patient who can read your Russian page still has a question that page did not anticipate, and at that point their options are to phone a desk that answers in Hebrew or to leave. The assistant is useful precisely at that gap, and useful in proportion to how honestly it refuses the clinical half of it.

Get in touch

Leave your details and we will reply. You do not need a sales call to get an answer.