Spanish and multilingual access: website, phone and forms
Patients who prefer Spanish or another language should be able to find your practice, book, complete intake and reach a person in that language, or be told clearly how to get free help. If your practice is covered by Section 1557, federal rules call for qualified interpreters and human review of machine translation for important content, so a translate button alone is not a plan.
Try booking in Spanish
Ask a fluent Spanish speaker, a staff member or a friend, to try reaching your practice entirely in Spanish while you watch.
- Search in Spanish for your specialty and town, the way a patient would.
- Land on your site and look for Spanish content without using a browser translate button.
- Book online or submit a request in Spanish.
- Call the main line and ask for an appointment in Spanish.
- Read the confirmation text or email. Which language is it in?
Mark every point where they hit English only, a dead end or a voicemail. A typical pattern is a Spanish homepage that leads into an English only booking tool, or a phone menu option for Spanish that ends at the same English voicemail.
If your community includes other large language groups, such as Vietnamese, Chinese, Arabic or Haitian Creole, repeat the test with what help you can find.
What Section 1557 asks of covered practices
Section 1557 of the Affordable Care Act applies to health programs that receive federal financial assistance from HHS, directly or indirectly. Many practices do. Whether yours is covered is a question for counsel, and this page is general information, not legal advice.
For covered practices, the HHS rules say:
- You must take reasonable steps to provide meaningful access to each individual with limited English proficiency, free of charge, accurately and in a timely way
- When interpretation is needed you must offer a qualified interpreter, and when translation is needed, a qualified translator
- If you use machine translation for text that is critical to a patient's rights, benefits or access, where accuracy is essential, or that contains complex or technical language, a qualified human translator must review it
- You may not require patients to bring their own interpreter, and may not rely on a minor child to interpret except as a temporary measure in an emergency
- You may not rely on staff who are not qualified interpreters, translators or qualified bilingual staff
- You must post a notice that free language help is available, in English and at least the 15 languages most commonly spoken by people with limited English proficiency in your state, in a conspicuous place on your website and on documents such as intake forms
Does ChatGPT recommend your practice?
The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.
What to translate first
You do not need to translate every page at once. Start where a patient decides and acts:
- The booking flow, confirmations and reminders
- Intake forms and consents, with a qualified translator, because these are exactly the documents where accuracy matters
- Visit preparation instructions
- Hours, locations, accepted insurance and how to reach a person
- Your new patient page and your most visited service pages
Publish translations as real pages with their own addresses, not only through a translate widget. Real pages can be found by search engines, and AI assistants answering a question in Spanish can only repeat what your pages actually say. A browser translate button is fine for casual reading, but machine output on consent forms or prep instructions is the case the rules single out for human review.
Write simply in both languages; see plain language patients and AI both prefer. Then assign someone to update the translation whenever the English page changes, or the two drift apart within months.
The phone is where language access breaks
Most patients with limited English will still call, and the phone is where well meaning practices fail them.
- The menu option to nowhere. "Para español, oprima dos" should reach a person who speaks Spanish, or an interpreter, not the same English voicemail.
- Unqualified helpers. Being conversational in a language is not the same as being able to explain a prep instruction accurately. Decide which staff are qualified bilingual staff and what they may handle.
- No interpreter line. For languages you do not staff, contract a telephone interpreter service, and train the front desk to bring an interpreter onto a call within the first minute.
- English only voicemail. Record the greeting in each language you serve, with the same callback promise.
AI phone and chat assistants that work in several languages can help with scheduling around the clock. Test them with native speakers before launch, and keep clinical conversations with qualified interpreters. More on choosing coverage in AI receptionists versus answering services.
Record the language and use it
Language access fails quietly when the preferred language is captured once and then ignored. Ask about it at the first contact and carry it through:
- Add a preferred language question to request and booking forms
- Store it in the EHR where the front desk and clinicians see it
- Route callbacks to bilingual staff, or start the callback with an interpreter already on the line
- Send reminders, intake links and instructions in that language
- Book an interpreter for the visit automatically, so nobody has to remember
Intake forms also need the language assistance notice, and the form itself should work for screen reader users too; see online intake forms that patients finish and accessible forms and chat.
Finally, say what is true, and only that. "Hablamos español" on your site is a promise. If it holds only on Tuesdays when one staff member is in, patients will find out on a Thursday.
Checklist
- A fluent speaker has tried booking in Spanish from search to confirmation
- Booking, confirmations, intake and prep instructions exist in your main patient languages
- Consents and instructions were translated or reviewed by a qualified human translator
- The website shows a notice that free language help is available
- The phone menu's language option reaches a person or an interpreter
- Preferred language is recorded in the EHR and drives callbacks and reminders
- Children are never used as interpreters outside a true emergency
Frequently asked
Can we use a website translate button instead of translated pages?
For casual browsing it helps, but it should not be your plan for important content. Section 1557 rules require human review of machine translation for critical, technical or accuracy sensitive material, such as consents and prep instructions, and translated pages are easier for patients and search engines to find.
Can a patient's family member interpret?
Under Section 1557, covered practices may not require patients to bring their own interpreter and may not rely on a minor child except briefly in an emergency. An adult companion may help only in narrow circumstances the rule describes, such as when the patient specifically asks in private with a qualified interpreter present. Offer a qualified interpreter first.
Which languages should we support?
Start with the languages your patients and your community actually speak. Your EHR's preferred language field, your phone logs and local census data will show where demand is. The language assistance notice itself must cover the most common languages in your state.
Do AI receptionists handle Spanish well enough for scheduling?
Some do, and quality varies by product and by accent. Test with several native speakers using real scheduling requests before you rely on one, and keep anything clinical with qualified human interpreters.
Sources
- 45 CFR 92.201, Meaningful access for individuals with limited English proficiency, Electronic Code of Federal Regulations
- 45 CFR 92.11, Notice of availability of language assistance services and auxiliary aids and services, Electronic Code of Federal Regulations
- 45 CFR 92.2, Application, Electronic Code of Federal Regulations
Book a strategy call with the team.
Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.