A lab report arrives as a PDF full of abbreviations, reference ranges, and a number circled in red. That's the first barrier. For most people in India, there's a second one right behind it: whatever explanation exists for what the report means usually arrives only in English.
The second barrier, after the report itself
Most people don't think exclusively in English, and plenty don't think in a single language at all — a conversation might move between English, Hindi, and a regional language within the same sentence. Health apps that answer only in English, or that translate a canned English answer afterward, are solving the wrong half of the problem: the words change, but the way the explanation is built doesn't.
Reasoning in English and translating the sentence afterward is not the same as reasoning in the language someone actually thinks in.
Why 'translated afterward' isn't enough
Medical explanation depends on nuance — confidence, caveats, the difference between “this is likely” and “this is certain.” That nuance is exactly what gets lost in a literal, after-the-fact translation. And translation alone still doesn't account for code-switching: someone who asks a question half in Hindi and half in English expects an answer in the same register, not a formally translated paragraph.
How Sol actually handles this
Sol reasons natively in nine languages, including Hinglish, rather than reasoning once in English and translating the output. That means the chain of reasoning itself — not just the final sentence — is built in the language you asked in. You can also ask by voice, in whichever of those languages you're most comfortable speaking rather than typing.
This matters most for the people the health system already serves worst: people for whom English medical jargon was always going to be a barrier, on top of everything else in an already stressful moment.
