z-logo
Premium
Fetal development of the retrohepatic inferior vena cava and accessory hepatic veins: Re‐evaluation of the Alexander Barry's hypothesis
Author(s) -
Jin Zhe Wu,
Cho Baik Hwan,
Murakami Gen,
Fujimiya Mineko,
Kimura Wataru,
Yu Hee Chul
Publication year - 2010
Publication title -
clinical anatomy
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.667
H-Index - 71
eISSN - 1098-2353
pISSN - 0897-3806
DOI - 10.1002/ca.20930
Subject(s) - medicine , inferior vena cava , hepatic veins , anatomy , vein , fetus , caudate lobe , hepatectomy , surgery , pregnancy , biology , resection , genetics
The retrohepatic inferior vena cava (IVC) is commonly considered to originate from the right vitelline or omphalomesenteric vein. In contrast, Alexander Barry hypothesized that one of the hepatic veins grows to merge with the subcardinal vein and develops into the retrohepatic IVC. We re‐examined fetal development of the retrohepatic IVC and other related veins using serial histological sections of 20 human fetuses between 6 and 16 weeks of gestation. At 6–7 weeks, when a basic configuration of the portal‐hepatic vein systems had just been established, one of hepatic veins (i.e., the posterocaudal vein in the present study) had grown caudally to reach the posterocaudal surface of the liver, and notably, extended into the primitive right adrenal gland (five of the eight early‐staged fetuses). Because the inferior right hepatic vein (IRHV) and retrohepatic IVC appeared at the same developmental stage, it is likely that any peripheral remnants of the posterocaudal vein would continue to function as primary drainage territory for the IRHV. The caudate vein developed rapidly in accordance with marked caudal and leftward extension of Spiegel's lobe at 12–16 weeks. Thin accessory hepatic veins developed later than the caudate vein and IRHV. The present results supported Barry's hypothesis. Clin. Anat. 23:297–303, 2010. © 2010 Wiley‐Liss, Inc.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here