AI and Machine Translation Quality Review for Patient Communications — Pashto, Dari, and 22 More Afghan Languages
Before a machine-translated discharge instruction, portal message or chatbot reply reaches an Afghan patient, a qualified human translator from Ariana Nexus reviews it, scores every error by severity, corrects it and signs the record.
For health programs covered by Section 1557, federal rules already require this review for critical patient text. We make it fast, measurable and specific to Afghan Pashto, Dari and every language Afghan patients speak.
At a glance
- What it is
- Qualified human review of Pashto, Dari and other Afghan-language text produced by machine translation or generative AI, before it reaches patients.
- Who it’s for
- Hospitals and health systems, language services and patient experience teams, digital health and EHR teams, health plans, and companies building patient-facing AI.
- What we review
- Discharge instructions, medication directions, portal messages, reminders, forms, patient education, and chatbot and virtual assistant replies.
- Languages
- Pashto, Dari and 22 more Afghan languages, with reviewers matched by dialect, region and gender.
- Method
- Every error typed and scored as critical, major or minor, aligned with ISO 5060:2024 and the MQM framework.
- Legal basis
- Section 1557 of the Affordable Care Act, 45 CFR 92.201(c)(3).
- You receive
- Corrected text, a findings log, a signed review record and an error profile of your tool.
- Delivery
- In-house reviewers only, with a business associate agreement signed before any patient text is shared.
Why AI translation fails Afghan patients
Translation engines learn from text that already exists online, and little of it is Afghan. Most Persian text online is Iranian, much of the Pashto online comes from Pakistan and is not medical, and several Afghan languages are rarely written at all. The output still reads fluently, which is the danger: a patient cannot tell a fluent error from a correct instruction.
Pashto with the wrong gender and region
Doses, numbers and negations
Words patients actually use
War, trauma and mental health
Right-to-left text that breaks
What we review
Any patient-facing text in an Afghan language that a machine or an AI model produced, reviewed against its English source and in the form the patient will actually see.
- Discharge instructions and after-visit summaries
- Medication directions and pharmacy labels
- Patient portal messages and secure chat
- Appointment reminders and text messages
- Consent, financial and registration forms
- Patient education and website pages
- Chatbot, virtual assistant and AI agent replies
- Scripts for AI voice and phone systems

Who uses this service
- Hospitals and health systems serving Afghan patients
- Language services and interpreter services departments
- Patient experience, digital health and portal teams
- EHR, patient messaging and health AI companies
- Health plans and public health departments
- Clinics and resettlement health programs serving the Afghan diaspora
What the evidence shows
What a review record holds
Every item leaves a record your auditors can read, tied to the reviewer who signed it.
- Item
- Discharge instruction
- Produced by
- The machine translation tool named at intake
- Language and variety
- Dari, Kabul
- Reviewer
- Qualified translator matched by variety and region
- Second check
- Second linguist, for the critical finding
- Findings
- 1 critical, 1 major, 2 minor
- Decision
- Blocked, corrected, released
- Signed
- Reviewer and second linguist, with date
What you receive
- Corrected text, ready to publish in the patient’s language and variety
- A findings log listing every error with its category, severity and correction
- A signed review record: reviewer, variety, date and decision for each item
- An error profile of the tool that produced the text, by language
- Glossary entries and style rules your team and your tool can reuse
- Back-translation into English on request
What a review finds
Two constructed examples of the errors we see most often. Pashto first, then Dari.
Pashto: a follow-up question and instruction for a woman patient from Kandahar
Dari: a discharge instruction for a patient from Kabul
How a review works
Six steps, the same for every item, so a result in Pashto can be compared with a result in Dari or Uzbeki.
- Stage 1
Intake and triage
We log the content type, the tool that produced it and the patient audience, then set the route: full review, sampled review or human translation. - Stage 2
Source check
We read the English first. Unclear abbreviations and instructions that are wrong in English are flagged before the translation is judged. - Stage 3
Matched review
A qualified translator matched to the language, variety, region and patient gender reviews the output line by line against the source. - Stage 4
Severity scoring
Each error is typed, such as accuracy, terminology or locale, and scored critical, major or minor, following ISO 5060:2024 and MQM. - Stage 5
Correction and second check
The reviewer corrects the text. Anything scored critical is checked again by a second linguist before release. - Stage 6
Signed record and feedback
You receive the signed record. Recurring errors become glossary entries and rules for your tool, so the next output starts better.
How we score errors
When machine translation is the right tool, and when it is not
Machine draft with our review
- Pashto or Dari text from a tool you already use
- Portal messages, reminders and general education
- Volume that would otherwise wait for translation
Human translation instead
- Medication directions and consent forms
- Machine drafts that need more than correction
- Uzbeki, Turkmeni and Balochi content
No machine translation
- Hazaragi and the 18 smaller Afghan languages, most with no reliable engine
- Patients who read little: use recorded audio or an interpreter
- Clinical answers no reviewer can check before a patient relies on them
The review federal rules already require
Section 1557 of the Affordable Care Act and its 2024 rule draw the line for AI translation in health care. When a covered entity uses machine translation for text that is critical to a patient’s rights, benefits or meaningful access, where accuracy is essential, or where the source is complex, non-literal or technical, a qualified human translator must review the translation. Discharge instructions, medication directions and consent forms meet at least one of those conditions.
Where no certification exists, we set the standard.
No U.S. certification exam tests translation from English into Pashto or Dari, so buyers are left to take a vendor’s word. Ariana Nexus answers with a written reviewer standard, reviewers who meet it and a signed record for every item.
Graduates, not bilinguals
A seven-part reviewer standard
From the communities we serve
In-house from intake to signature
Honest about what AI cannot do
Outside the de facto authorities’ channels
Machine translation alone, a bilingual check, or a qualified review
Matched to the patient, not only the language
Language and exact variety
City and region
Gender
Education close to medicine
The team that reviews your content
The program is overseen by Hassan Ukasha, Managing Partner, and delivered by partners and managers educated at Cornell, Brown, the University of Chicago and the University of British Columbia. The reviewers they lead are Afghan college graduates, not bilingual volunteers.

Hassan Ukasha
- B.S.Cornell University
- M.P.H.Cornell University
Oversees the firm’s operations and the AI translation review program, including engagement governance, the reviewer standard and data protection. Grew up in Herat.

Tamana Ghaznawi
- B.S.Cornell University
- M.P.H.Cornell University

Zeba Haqbani
- B.Sc.University of British Columbia

Diana Ayubi
- B.A.Cornell University
- Psy.D.West Chester University

Shukria Sakhi
- B.S.Brown University
- M.P.H.Brown University

Hussain Ahmad
- M.Eng.Cornell University
- Ph.D.University of Chicago

All 24 Afghan languages we review
We review written output in all 24 languages and say plainly when machine translation is not a sound option. Several of these languages are rarely written, so the right answer may be a human translation or a recorded message rather than an engine. For Hazaragi speakers, we review Afghan Dari for Hazaragi readers or record the message in Hazaragi.
- پښتوPashtoIranian. South and east; spoken nationwideMachine translation: widely offered
- دریDariIranian. Nationwide; Kabul, Herat, Mazar-i-SharifMachine translation: often returned as iranian persian
- هزارگیHazaragi (a variety of Dari)Iranian. Central highlandsMachine translation: not offered as its own variety
- ایماقیAimaqIranian. West: Ghor, Badghis, HeratMachine translation: no reliable engine
- بلوچیBalochiIranian. Southwest: Nimroz, HelmandMachine translation: limited
- اورمړیOrmuriIranian. LogarMachine translation: no reliable engine
- پراچیParachiIranian. Panjshir and Kapisa valleysMachine translation: no reliable engine
- وخیWakhiIranian. Wakhan, BadakhshanMachine translation: no reliable engine
- شغنیShughniIranian. Shughnan, BadakhshanMachine translation: no reliable engine
- سنگلیچیSanglechiIranian. Sanglech valley, BadakhshanMachine translation: no reliable engine
- اشکاشمیIshkashimiIranian. Ishkashim, BadakhshanMachine translation: no reliable engine
- منجیMunjiIranian. Munjan valley, BadakhshanMachine translation: no reliable engine
- یدغهYidghaIranian. Munjan border regionMachine translation: no reliable engine
- ازبکیUzbekiTurkic. North: Balkh, Jowzjan, FaryabMachine translation: offered in another script
- ترکمنیTurkmeniTurkic. Northwest: Jowzjan, FaryabMachine translation: offered in another script
- قرغزیKyrgyzTurkic. Little Pamir, WakhanMachine translation: offered in another script
- پشهییPashayiIndo-Aryan. Laghman, Kunar, NangarharMachine translation: no reliable engine
- گواربتیGawarbatiIndo-Aryan. Lower Kunar valleyMachine translation: no reliable engine
- تیراهیTirahiIndo-Aryan. Nangarhar, a few villagesMachine translation: no reliable engine
- اشکونNuristani (Ashkun)Nuristani. Southwest NuristanMachine translation: no reliable engine
- کتیKatiNuristani. Nuristan, Bashgal valleyMachine translation: no reliable engine
- پارونPrasunNuristani. Nuristan, Parun valleyMachine translation: no reliable engine
- وایگلیWaigaliNuristani. Nuristan, Waigal valleyMachine translation: no reliable engine
- براهوییBrahuiDravidian. South: Helmand, Nimroz, KandaharMachine translation: no reliable engine
Regions are indicative and used for matching; they are not a census. Names are shown in Arabic script as commonly written; several smaller languages have no standardized spelling. Engine coverage changes often. We check the specific tool you use at intake.
In Pashto and Dari
The words engines get wrong
Everyday health words, as Afghan patients read them and as engines often return them.
Pashto
Dari
Ways to engage
Spot audit
Full review before release
Ongoing assurance
Human translation
How patient data stays protected
- A business associate agreement is signed before any patient text is shared.
- Reviewers never paste patient text into public AI tools.
- We ask only for the text the review needs.
- We do not use your content to train AI models.
Terms used on this page
- Machine translation
- Automated, text-based translation produced without a qualified human translator. The Section 1557 rule defines it at 45 CFR 92.4.
- Qualified human translator
- A translator who follows translator ethics, including confidentiality, has shown written proficiency in English and the other language, and translates accurately with the terms the text needs.
- Machine translation post-editing (MTPE)
- Correcting machine output until it reads correctly. A quality review adds scoring and a signed record.
- Linguistic quality assurance (LQA)
- A structured check of translated content against defined error types and severity levels.
- MQM
- Multidimensional Quality Metrics, a shared typology of translation error types used to score quality.
- Severity level
- The weight of an error, critical, major or minor, based on its effect on the reader.
- Afghan Dari
- The variety of Persian spoken and written in Afghanistan, distinct in everyday vocabulary from Iranian Persian (Farsi).
- Hazaragi
- A variety of Dari spoken by Hazara communities, treated as its own language for matching.
Questions health systems ask
Is Google Translate accurate enough for Dari or Pashto patient instructions?
Not on its own. In a 2021 study of emergency department instructions, Google Translate was 94% accurate for Spanish but 67.5% for Persian (Farsi), the closest published measure for Dari. Afghan Dari differs from Iranian Persian in everyday health words, so the output needs review by a qualified human translator before a patient relies on it.
Does Section 1557 allow machine translation of patient documents?
It allows the tool, not unreviewed output. Under 45 CFR 92.201(c)(3), if a covered entity uses machine translation for text that is critical to a patient’s rights, benefits or meaningful access, where accuracy is essential, or where the language is complex, non-literal or technical, a qualified human translator must review the translation.
Who counts as a qualified human translator?
The Section 1557 rule, at 45 CFR 92.4, describes a qualified translator as someone who follows translator ethics, including confidentiality, has shown proficiency in written English and the other language, and translates accurately and impartially with the specialized terms the text needs. Our reviewers are assessed in the exact variety they review and trained in medical terminology.
Can we use ChatGPT or another AI model to translate discharge instructions into Pashto or Dari?
You can use it to draft. We treat translation by AI models as machine translation, because it is automated, text-based translation, so critical patient text still needs review by a qualified human translator. AI models also write fluent text that hides errors and can change meaning between runs, so each output needs its own review.
Is Dari the same as Farsi?
They are closely related varieties of Persian, but not the same in daily use. Afghan Dari uses different words for many health terms, such as شفاخانه for hospital and داکتر for doctor, where Iranian Persian uses بیمارستان and پزشک. Tools trained mostly on Iranian text tend to produce the Iranian forms.
What is machine translation post-editing, and how is a quality review different?
Post-editing (MTPE) corrects machine output until it reads well. A quality review also measures it: every error is categorized and scored by severity, and the result is signed and recorded. You learn how good the tool is, not only what the corrected text says.
How do you score translation quality?
We follow ISO 5060:2024, the international guidance for evaluating translation output, and the MQM error typology. Each error is typed, such as accuracy, terminology or locale, and weighted as critical, major or minor. Critical errors block release until they are corrected and checked again.
Which Afghan languages can machine translation handle?
Pashto is widely offered. Dari is offered by some tools but often returned as Iranian Persian. Uzbeki, Turkmeni and Kyrgyz are usually produced in another script, while Afghan communities write them in Arabic script. Most other Afghan languages have no reliable engine, and several are rarely written; for those we recommend human translation or recorded audio.
Do you match reviewers by dialect and gender?
Yes. We match the language, the exact variety, the city or region your patients come from, and the reviewer’s gender where the subject calls for it. Clinical content goes to reviewers with degrees close to medicine.
How do you protect patient information during a review?
A business associate agreement is signed before any patient text is shared. Reviewers work only in approved systems, never paste patient text into public AI tools, and handle only the text the review needs.
Does the executive order making English the official language change our obligations?
Executive Order 14224, signed in March 2025, designates English as the official language but does not require agencies or health programs to stop offering services in other languages. Section 1557 and its language access rule, including the machine translation review requirement, remain in effect.
Does California’s AB 3030 apply to AI-translated patient messages?
AB 3030 requires California health facilities, clinics and physician offices that use generative AI for communications about a patient’s clinical information to include a disclaimer and instructions for reaching a person, unless a licensed or certified health care provider reads and reviews the message. Our language review does not replace that clinical review, but it makes sure the message and the disclaimer are right in Pashto or Dari.
Is there a U.S. certification for Pashto or Dari translators?
No U.S. certification exam tests translation from English into Pashto or Dari. That is why we publish our own reviewer standard: a degree, an assessment in the exact variety, medical training, ethics and HIPAA training, supervised entry and periodic review.
Related healthcare services
- Medical interpreters for hospitals and clinics
- Telehealth and video remote interpreting
- Mental health and trauma-informed interpreting
- Patient document translation
- Health plan member materials translation
- Clinical trial consent and recruitment translation
- Linguistic validation of patient questionnaires
- Afghan patient cultural competency training
- Medicaid eligibility and benefits navigation
- Section 1557 language access compliance consulting
Put a qualified reviewer between the machine and your patient.
Scope and handling are agreed under NDA, with a business associate agreement in place before any patient text is shared.