z-logo
open-access-imgOpen Access
Heterogeneity of p53 Mutational Status in Esophageal Squamous Cell Carcinoma
Author(s) -
Kuwabara Shirou,
Ajioka Yoichi,
Watanabe Hidenobu,
Hitomi Jiro,
Nishikura Ken,
Hatakeyama Katsuyoshi
Publication year - 1998
Publication title -
japanese journal of cancer research
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.035
H-Index - 141
eISSN - 1349-7006
pISSN - 0910-5050
DOI - 10.1111/j.1349-7006.1998.tb00578.x
Subject(s) - biology , cancer research , carcinoma , genetic heterogeneity , mutation , esophagus , gene , esophageal cancer , lymph node , polymerase chain reaction , tumor suppressor gene , esophageal disease , gene mutation , pathology , cancer , phenotype , carcinogenesis , medicine , genetics , immunology , anatomy
In esophageal squamous cell carcinoma, p53 gene mutations have been analyzed for inter‐ or intra‐patient heterogeneity but only a few studies have investigated intratumoral heterogeneity. We investigated this question within individual esophageal cancers, and also in their lymph‐node metastases in 8 cases. Analyzing the p53 gene sequence by direct sequencing of polymerase chain reaction products, we found heterogeneity for p53 mutations in the pre‐invasive area in 3 esophageal cancers. In all areas sampled in the invasive portion of each cancer, the p53 mutational status was identical in a given tumor. In heterogeneous tumors, the invasive area showed one of the p53 mutations found in the pre‐invasive area. In nodal metastases, the p53 mutation was identical to that in the invasive area of each primary tumor. These data suggest that the timing of p53 alteration is not as early as might have been expected, indicating that, in regard to p53 gene alteration, some esophageal cancers are composed of various subclones in the pre‐invasive stage with invasiveness developing in one of them, which becomes predominant through clonal selection.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here