z-logo
Premium
Identical origin of adrenal cortex and gonad revealed by expression profiles of Ad4BP/SF‐1
Author(s) -
Hatano Osamu,
Takakusu Akira,
Nomura Masatoshi,
Morohashi Kenichirou
Publication year - 1996
Publication title -
genes to cells
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.912
H-Index - 115
eISSN - 1365-2443
pISSN - 1356-9597
DOI - 10.1046/j.1365-2443.1996.00254.x
Subject(s) - primordium , biology , gonad , adrenal cortex , population , anatomy , development of the gonads , sexual differentiation , cortex (anatomy) , microbiology and biotechnology , endocrinology , medicine , gene , genetics , neuroscience , demography , sociology
Background : Ad4BP/SF‐1 was originally identified as a steroidogenic tissue‐specific transcription factor. Recent gene disruption studies with the mammalian Ftz‐F1 gene encoding Ad4BP/SF‐1 clearly revealed the essential function of the factor for adrenal and gonadal differentiation. Results : In this study, we examined the early development of these tissues using Ad4BP/SF‐1 as the marker. In rat foetuses of 11.5 days post‐coitum (d.p.c.), a cell population designated adreno‐genital primordium was firstly observed on symmetrical lines extending from the dorsal aorta to the dorsal coelomic epithelia of the primitive urogenital ridges. From 12.5 d.p.c., the rostral half of the adreno‐genital primordium started to separate into two distinct cell populations. Judging from the distribution of primordial germ cells, the cell population on the dorsal aortal side is a primordium for the adrenal cortex whereas that on the coelomic epithelial side is for the gonads. At 13.5 d.p.c., these two primordia have separated completely. Conclusion : These observations clearly identified a novel adreno‐genital primordium from which both the adrenal cortex and the gonads originate. An RT‐PCR study conducted to detect adrenal‐ and gonad‐specific mRNAs supported the above observations.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here