Pan-cancer prevalence of microsatellite instability and Lynch syndrome in India
This pan-cancer study of 519 Indian patients reveals a 25.6% prevalence of microsatellite instability/mismatch repair deficiency, identifying a high burden of Lynch syndrome (49.6% of MSI-high/MMRd cases) driven largely by specific *MLH1* founder variants, thereby validating a tumor-first screening approach to improve detection and management across diverse cancer types in India.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
The Big Picture: Finding a Hidden "Glitch" in Cancer
Imagine your body's cells are like a massive library of books (your DNA). Every time a cell divides to make a new cell, it has to photocopy these books. Usually, the library has a very strict proofreading team (called the Mismatch Repair system) that checks the photocopies for typos.
Lynch Syndrome is like a genetic glitch where a person is born with a broken proofreader. Because the proofreader is broken, typos pile up in the books. These typos are called Microsatellite Instability (MSI). When too many typos accumulate, the cells get confused and start growing out of control, leading to cancer.
This study is the first big "census" in India to see how many people have this broken proofreader across many different types of cancer, not just the usual suspects like colon cancer.
The Mission: A "Tumor-First" Detective Hunt
In the past, doctors often waited for a patient to have a very specific family history of cancer before they checked for this glitch. It was like waiting for a fire to burn down a whole house before checking the smoke alarm.
This study flipped the script. They used a "Tumor-First" approach.
- The Analogy: Imagine a detective who doesn't wait for a report of a crime. Instead, they walk into any building (any cancer patient) and immediately check the smoke alarm (the tumor) to see if it's broken. If the smoke alarm is broken (MSI-High), then they go back to check the building's blueprints (the patient's blood) to see if the owner was born with a broken alarm system (Lynch Syndrome).
What They Did
- The Team: Researchers from 17 different hospitals across India worked together.
- The Group: They looked at 519 patients with various cancers (colon, stomach, ovary, uterus, etc.).
- The Process:
- They tested the tumor tissue to see if it had "typos" (MSI testing).
- If the tumor had typos, they checked the patient's blood to see if the "broken proofreader" was a genetic inheritance (Germline testing).
- They also looked for specific "signature" mutations to rule out random, non-inherited causes.
The Big Discoveries
1. The Glitch is More Common Than Thought
They found that 25.6% of the tumors they tested had the "typo" signature (MSI-High). This is a surprisingly high number, meaning this genetic glitch is a frequent visitor in Indian cancer patients.
2. Half of the "Glitch" Cases are Inherited
Out of the tumors with the "typo" signature, they checked the patients' blood. They found that nearly half (49.6%) of these patients actually had Lynch Syndrome. This means almost 1 in 2 people with this specific tumor glitch inherited the broken proofreader from their parents.
3. It's Not Just About the Colon
While Colon Cancer had the highest number of cases, they found Lynch Syndrome in many other places too, including:
- Endometrial (Uterus) Cancer
- Ovarian Cancer
- Stomach Cancer
- Others: Oesophagus, pancreas, and small intestine.
- The Lesson: You can't just look for this in colon cancer; you have to check all types of tumors.
4. The "Gujarat" Connection (Founder Variants)
This is a very specific and important finding for India. The researchers found that many of the patients with Lynch Syndrome shared the exact same broken gene mutation.
- The Analogy: Imagine a village where everyone has the same unique scar on their hand. You realize they all descend from one great-grandparent who had that scar.
- The Finding: They found two specific "scars" (mutations) in the MLH1 gene that were very common. One of them, called c.156delA, appears to be a "Founder Variant" that originated in the Gujarat region of India about 70 generations ago (roughly 1,750 years ago).
- Because of this, a huge chunk of the Lynch Syndrome cases in their study came from this specific region and shared this specific genetic history.
5. Two Tests Agree on the Answer
The study compared two different ways of testing the tumor:
- PCR-FLA: A lab test that counts the "typos" directly.
- IHC: A test that looks for the missing "proofreader" proteins under a microscope.
- The Result: In non-colon cancers, these two tests agreed with each other 93.8% of the time. This is great news because it means doctors can use either method and trust the result.
Why This Matters (According to the Paper)
The paper concludes that this "Tumor-First" strategy works very well in India. By testing the tumor first, they can catch people with Lynch Syndrome who would have otherwise been missed because they didn't have a "classic" family history.
Finding these patients is crucial because:
- It tells the patient they have a hereditary condition.
- It allows their family members to get tested (Cascade testing) so they can catch cancer early or prevent it.
- It identifies patients who might respond well to specific immunotherapies (drugs that help the immune system fight the cancer).
Summary
Think of this study as a massive safety inspection across India. The researchers found that a significant number of cancer patients have a broken "proofreading" system. They discovered that in India, this is often caused by a specific genetic "family heirloom" (founder variant) that has been passed down for centuries, particularly in Gujarat. By checking the tumor first, doctors can now find these hidden genetic risks much faster and help families stay safe.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.