go-v.orgdoi

Role of the mitochondrial genome in preimplantation development and assisted reproductive technologies

Lawrence Charles Smith, Jacob C. Thundathil, France Filion · Reproduction Fertility and Development · 2004

  • DOI 10.1071/rd04084
  • Publisher CSIRO Publishing
  • Type article
  • Issued 2004

Not cached yet. This record was fetched live for this request and is stored after the lookup. Reopening the page should serve the cached copy.

Reproduction Fertility and Development · CSIRO Publishing · article · 2004

Abstract

Our fascination for mitochondria relates to their origin as symbiotic, semi-independent organisms on which we, as eukaryotic beings, rely nearly exclusively to produce energy for every cell function. Therefore, it is not surprising that these organelles play an essential role in many events during early development and in artificial reproductive technologies (ARTs) applied to humans and domestic animals. However, much needs to be learned about the interactions between the nucleus and the mitochondrial genome (mtDNA), particularly with respect to the control of transcription, replication and segregation during preimplantation.

Nuclear-encoded factors that control transcription and replication are expressed during preimplantation development in mice and are followed by mtDNA transcription, but these result in no change in mtDNA copy number. However, in cattle, mtDNA copy number increases during blastocyst expansion and hatching. Nuclear genes influence the mtDNA segregation patterns in heteroplasmic animals. Because many ARTs markedly modify the mtDNA content in embryos, it is essential that their application is preceded by careful experimental scrutiny, using suitable animal models.

Open the resolved locator · 10.1071/rd04084

Metadata licence: OpenAlex metadata (CC0)

Registry
OpenAlex DOI index + API
Fetched
2026-11-20 01:45 UTC
Cache state
not cached yet (bulk-index+openalex)
Locator
https://doi.org/10.1071/rd04084
Metadata licence
OpenAlex metadata (CC0)
Scope
Metadata as returned by the resolver; abstracts are never generated here.