Language Access: Five Myths That Keep Clinics Improvising
Few clinics set out to neglect language access. Where it breaks down, the cause is usually a set of comfortable assumptions that let the organization improvise from day to day. Each one sounds reasonable. Each one leaves a gap that patients with limited English proficiency end up filling on their own.
The U.S. Department of Health and Human Services treats language assistance as necessary for equal access to HHS-funded programs for people with limited English proficiency. The National CLAS Standards place language assistance within a wider framework of governance, workforce, and quality improvement. Measured against those expectations, here are five myths worth retiring.
Myth 1: “Our bilingual staff can interpret.”
Reality: Speaking two languages and interpreting are different skills. Interpreting health information accurately means handling medical terms, keeping the speaker’s meaning without adding or dropping anything, and staying neutral in a conversation where the interpreter may know the patient. CLAS Standard 7 calls for ensuring the competence of people who provide language assistance.
Bilingual employees are a real asset, and many enjoy using their language skills at work. The fix is to define the role:
- Decide which tasks bilingual staff may do in another language, such as scheduling or reminders, and which require a qualified interpreter.
- Set a way to assess competence for staff who do interpret, and recognize that work in job descriptions.
- Avoid pulling someone off their own duties to interpret by default, which strains both jobs.
Myth 2: “We rarely get requests, so the need is small.”
Reality: A low request count often measures how the question is asked, not how many people need help. If no one asks about language at scheduling, or if patients don’t know an interpreter is available, many will simply manage, bring someone along, or stop coming.
Better signals include:
- The share of records with a preferred language recorded at all.
- Whether preferred spoken language, preferred written language, and interpreter need are captured as separate fields.
- Whether missed appointments or incomplete referrals differ by preferred language.
- Community data about the languages spoken in the service area.
If those numbers don’t match the request count, the gap is the finding.
Myth 3: “We translated the forms, so we’re covered.”
Reality: Translating high-volume documents is a sensible start, but a patient’s path includes far more than forms. A consent form may be translated while the text message linking to it is in English only. Portal education may be translated while the password reset screen is not. Billing statements, referral letters, and after-hours phone menus are easy to forget.
A practical approach is to map one common pathway, such as new-patient intake, from first contact to follow-up, and list every message along the way. Then ask which of them determine whether a person can get in, stay in, and finish. Those come first.
Myth 4: “Family members can help.”
Reality: Family members bring comfort and context, and patients may want them present. They are a different thing from an interpreter. A relative may soften bad news, skip a question they find embarrassing, or add their own opinion. Children placed in that role carry a burden they shouldn’t. The CLAS Standards specifically discourage using untrained individuals or minors as interpreters.
What works better:
- Offer a qualified interpreter every time, in the patient’s language, and explain what the interpreter’s role is.
- Let family stay as support, not as the channel of communication.
- Document what was offered and what the patient chose.
- Set a clear rule for emergencies, when waiting is not possible, and follow up with a qualified interpreter as soon as one is available.
Myth 5: “We’ll figure it out when the patient arrives.”
Reality: Arranging support on the spot means the patient waits, the schedule slips, and staff improvise under pressure. It also leaves no plan for the predictable bad days: a scheduled interpreter who doesn’t arrive, a video connection that fails, or a language the usual vendor doesn’t cover.
Preparing ahead looks like this:
- Record the language need in a structured field that travels with the appointment, so no one rediscovers it.
- Show whether an interpreter has been requested, confirmed, or delayed, so staff don’t duplicate requests or assume someone else made one.
- Write down a fallback, such as phone interpretation, with the access number posted where front-desk and clinical staff can reach it.
- Check the setup periodically by testing the steps the way a patient would encounter them.
From improvising to a system
Each myth rests on the same idea: that language access is a favor arranged case by case. Treating it as an ordinary part of operations, with defined roles, recorded needs, translated pathways, and tested fallbacks, takes some setup. After that, it makes the daily work easier for staff as well as for patients.
Sources
- HHS Office for Civil Rights: Limited English Proficiency
- HHS Office of Minority Health: National CLAS Standards
- HHS Office for Civil Rights: Effective Communication in Health Care
About the author
Sherry Sayari, MPH, is an Operational Standards Evaluator who has led population health, community outreach, and social services programs. More on the About page.
