Plenty of US clinics see Spanish-speaking patients every day, and many of those visits run through a qualified interpreter. So a fair question about any ambient scribe is: what does it do when the encounter is not all in English? Short version: Patient Square listens to the visit and drafts a structured English note about two minutes after you finish, including encounters that crossed languages or used an interpreter. It does not interpret between you and the patient, and it does not replace a medical interpreter. The note is a draft you review and sign, with names and medications worth an extra look.
Key takeaways
- Many US visits involve Spanish-speaking patients or a qualified interpreter; the scribe documents them.
- The scribe does not interpret the clinical conversation and does not replace a medical interpreter.
- The note comes back in English for you to review and sign.
- Verify patient names, medication names, and dosages carefully, especially in bilingual encounters.
- We do not publish an accuracy percentage; treat every draft as a draft.
From visit end to draft English note
Audio recordings retained after the note drafts
Language the clinical note returns in
Source: audio handling described on the security page.
What a bilingual US visit actually looks like
There is no single shape. Sometimes you speak Spanish yourself and the whole visit runs in Spanish. Sometimes a family member is present and switching between languages. Often a qualified interpreter joins in person, by phone, or by video, and the conversation moves patient, interpreter, clinician, and back again. Language access is a legal and safety obligation in many US settings, not a nicety, so these visits are common and they are not going away.
That mix is the hard part for documentation. The clinical facts live across two languages and sometimes three voices. A note has to pull the medically relevant content out of all that and land it in English, accurately, for the record.
An ambient scribe helps with the documentation half of that problem. It does not help, and should not try to help, with the interpretation half. Those are different jobs.
How an ambient scribe handles interpreter-mediated encounters
Patient Square listens to the encounter and drafts a structured SOAP note, ICD-10 suggestions, and a prescription draft about two minutes after you finish. That includes visits where an interpreter is present. The scribe is documenting what happened; it is not the channel through which you and the patient understand each other.
Keep the roles clean. The interpreter carries the clinical conversation in real time. You practice medicine. The scribe drafts the note afterward. If you drop the interpreter and lean on the scribe to bridge the language gap during the visit, you have misused the tool and created a safety problem. The scribe is downstream of the conversation, not part of it.
The finished note comes back in English, which is what your chart and your colleagues need. A human scribe documenting an interpreted visit would do the same: the conversation crosses languages, the record is in English.
The honest limits
This is the part vendors skip, so here it is plainly.
The note is in English. If the visit happened partly in Spanish, the scribe is producing an English clinical note from a multilingual conversation, and that is a harder task than a single-language visit. Read the draft against what you remember of the encounter.
Names and medications need verification. In any note, patient names and drug names are the most error-prone fields, because they are proper nouns and they sound alike. Across languages, that risk goes up. Confirm the patient’s name, every medication name, and every dose before you sign. Do not skim those fields.
We do not publish an accuracy number. Be wary of any scribe that quotes one language-accuracy figure as if it settles the question, because accuracy depends on audio quality, accents, crosstalk, and the specific vocabulary of the visit. The safer posture is the correct one anyway: it is a draft, you review it, you own the signed record.
What to check in a bilingual-visit note
A quick review discipline catches most of what matters.
| Field to check | Why it is higher-risk in a bilingual visit | What to do |
|---|---|---|
| Patient name | Proper nouns transcribe poorly, more so across languages | Confirm spelling against the chart |
| Medication names | Drug names sound alike and cross languages badly | Verify each against your own order |
| Dosages and units | Numbers and units are easy to mishear | Read every dose before signing |
| History details | Content moved through an interpreter | Check the draft against your recollection |
| Plan and follow-up | Instructions may have been relayed, not stated directly | Confirm the plan reflects what you decided |
This is not busywork specific to Patient Square. It is the review any signing clinician owes any draft, tightened a notch for encounters that crossed languages. The reading stays yours.
Where the scribe fits, and where it does not
It fits the documentation load. A clinic that sees Spanish-speaking patients all day still has to chart every one of those visits in English, and doing that from memory after a long interpreted encounter is slow and lossy. The scribe drafts it in about two minutes so you review instead of reconstruct.
It does not fit the interpretation need. If your clinic’s language access plan requires a qualified interpreter, that requirement stands. The scribe changes nothing about it. Anyone selling an ambient scribe as an interpreter replacement is selling you a compliance and safety risk.
Because Patient Square is EHR-agnostic, none of this depends on your system. You copy or paste the English note into Epic, athenahealth, eClinicalWorks, or whatever your clinic runs. Related reading: primary care documentation with an ambient scribe, SOAP note quality, and the HIPAA, BAA, and consent page for how consent works when you are recording a visit.
Try it on a real bilingual encounter
The best test is your own hardest visit.