Your obligations under Section 1557 and Title VI
Federally funded health programs must provide qualified interpreters at no cost to patients with limited English proficiency, and may not rely on family members or untrained staff. About 8 percent of U.S. residents — roughly 25.7 million people — are limited English proficient (U.S. Census Bureau, census.gov), and each is entitled to meaningful access. Document how you identify language need, how you source qualified interpreters, and how you handle the highest-demand languages in your service area.
- Offer qualified interpreters at no cost, in a timely manner
- Avoid minors and family members except in emergencies
- Post taglines and notices in your community's most-requested languages
Verify qualification, not just language
In Minnesota, ask every interpreter source to confirm MDH Spoken Language Health Care Interpreter Roster registration and, where it exists, national certification such as CCHI or NBCMI. More than one in nine Minnesotans speaks a language other than English at home (U.S. Census Bureau via Minnesota Compass, mncompass.org), and that demand concentrates in a handful of languages. For the highest-demand languages — Somali, Spanish, Hmong, Karen, Oromo — also confirm dialect screening and specialty experience, because demand routinely outpaces narrow sub-specialties.
- Confirm MDH roster registration for each interpreter
- Require CCHI or NBCMI where the credential exists for that language
- Confirm dialect and specialty match for complex care
Protect PHI: the interpreter is a Business Associate
Interpreters handling protected health information should operate under a Business Associate Agreement and clear PHI-handling rules. HIPAA civil penalties can reach roughly $1.5 million per violation category per year (U.S. Department of Health & Human Services, hhs.gov), so an interpreter touching PHI without a BAA is a real exposure. Your interpreter source should sign a BAA, scrub patient identifiers from any scheduling notes, and provide documented session records of who interpreted what, when.
- Require a signed BAA before any PHI is shared
- Keep patient identifiers out of booking notes
- Expect documented records of each encounter
Plan for demand, not just incidents
Treat language access as capacity planning. An estimated one in twenty Minnesotans is limited English proficient (U.S. Census Bureau, census.gov), so demand is a standing condition, not an occasional incident. Use your own encounter data plus statewide demand patterns to forecast which languages you will need most, and give your interpreter partner enough lead time to recruit and vet for the languages where supply is thin.
Key takeaways
- Document your end-to-end language-access process before an audit asks for it
- Verify roster registration and certification for every interpreter
- Sign a BAA and enforce PHI hygiene in scheduling
- Forecast demand for thin-supply languages and plan lead time