CHW Intake Program: How to Launch in 5 Languages

What a CHW intake program actually does

A community health worker (CHW) is the first person a patient meets in a refugee clinic, a Federally Qualified Health Center (FQHC), or a street-outreach program. They sit next to the patient, hand them a phone or tablet, and walk them through an intake form. That intake form has to work in the patient's language, on the CHW's phone, and produce a record the supervising provider can read in English ten minutes later. When all three of those things happen, the program runs. When any one of them breaks, the CHW is doing paperwork instead of care.

This guide walks through the five pieces you need in place to launch a multilingual CHW intake program, drawing on what works in real FQHC and refugee-clinic deployments. It assumes you have (or can stand up) a CHW supervisor, a mobile-friendly intake tool, and a target patient demographic.

Piece 1: Pick your first five languages from real data

Don't pick languages from a national demographics dashboard. Pull the language preferences of every patient your clinic saw in the last 12 months. That list — usually 3 to 8 languages — is the language set your intake program has to support. If your city has a refugee resettlement office, ask them which cohorts are arriving this quarter; those are the languages you need before the patients walk in, not after.

A common pattern in the US: Spanish is always #1. After that, the order varies by metro — Somali and Amharic in some cities, Vietnamese and Mandarin in others, Haitian Creole in Florida, Arabic and Dari in refugee-heavy states. Aim for the top five. Adding a sixth language is a separate decision and usually deserves its own pilot.

Piece 2: Choose a robust intake tool that supports your languages

Ideally the CHW intake form is completed in the native language of the patient. The form has to render correctly in right-to-left scripts (Arabic, Dari, Pashto), it has to keep working on spotty hospital Wi-Fi, and it has to handle the patient tapping the wrong answer and needing to back up without losing the rest of the form. Brella's multilingual form builder was designed for exactly this — build once in English, translate into the languages you serve, and have the CHW hand the phone to the patient with a language picker on the first screen.

Before you commit to a tool, run a one-week pilot with one CHW in your busiest language. Pilot data should answer three questions: (1) Did patients finish the form? (2) Did the CHW have to translate on the fly, or did the form do it? (3) Did the supervising provider get an English-language summary that was actually readable? If any answer is "no," that language isn't ready. Brella's form builder has built in analytics to answer these questions immediately.

Piece 3: Don't build your form from scratch

Every hour a clinic administrator spends laying out form fields is an hour not spent training CHWs or reviewing data. You don't need that hour. The Brella dashboard ships with an AI form builder — describe the intake you need in a sentence ("a PRAPARE social needs screening for a refugee clinic") and it generates the full question set, ready to edit, in under a minute. It'll build and ship PRAPARE (Protocol for Responding to & Assessing Patient Assets, Risks, and Experiences) and AHC HRSN (Health-Related Social Needs) screening templates with one easy prompt, and translate those templates into 100+ languages with the click of a button.

Already have an intake packet in hand — a scanned PRAPARE PDF, a state-mandated screening form, a paper form your clinic has used for years? Upload the PDF and Brella converts it directly into a digital form, with the question types and logic already mapped, so you're not retyping a 20-question packet by hand. From there it's the same one-click translation into 100+ languages, RTL scripts included.

Starting from a pre-validated template — whether generated by AI, converted from a PDF, or picked from Brella's library — gets you three things for free: regulatory alignment, peer-reviewed translation, and a defensible record when an audit asks where the questions came from.

If your clinic needs a custom intake beyond PRAPARE — and most do — start with PRAPARE as the first 12 questions and add your clinic-specific block after. Mixing a validated instrument with a custom block is the standard pattern.

Piece 4: Train CHWs on the workflow, not the software

The most common reason CHW programs stall is that the training focused on the tool instead of the workflow. The CHW doesn't need to know how to add a question to a form. The CHW needs to know: when do I hand the phone over (after the patient consents and selects their language), and what do I do if the patient stops answering halfway through (let them — partial intake is still useful).

Build a one-page laminated card with the workflow. Keep it under ten steps. Put it in the CHW's pocket. The Brella mobile app takes care of the rest — the CHW selects the patient's language, hands over the device, and the patient does the rest.

Piece 5: Loop the supervising provider in within an hour

A CHW intake that doesn't reach a clinician within an hour is a CHW intake that won't be used. The supervising provider has to see the patient's responses — translated into English — in the EHR or in the dashboard, with the patient's preferred language flagged so the provider knows to bring a qualified medical interpreter for the visit itself. Brella's dashboard exports structured JSON that maps to most EHR intake forms, and the English translation is visible the moment the patient submits.

Schedule a monthly review of the first ten completed intakes with the CHW, the supervising provider, and an interpreter. Watch for: mistranslations, questions that consistently confuse patients, and answers that flag acute needs the intake should have caught earlier. Update the form monthly. The first version of a CHW intake program is never the version that scales — the third or fourth version is.

What to measure in the first 90 days

• Completion rate by language. Track every intake from "patient opens form" to "patient submits." If one language is below 70%, the translation or the layout for that language needs work, not the CHW.
• Time-to-provider. Median minutes between form submission and the provider seeing the English summary. Target is under 60 minutes for in-clinic visits.
• Language mismatch errors. Any time a CHW has to re-do an intake because the wrong language was selected. Should drop to near-zero after the first month.
• Patient satisfaction. A two-question verbal survey after the visit: "Did the form ask the right questions?" and "Were you comfortable answering in your language?" Track trends, not absolutes.

Ready to launch your multilingual CHW intake program? Start a free Brella trial.