> For the complete documentation index, see [llms.txt](https://help.connected.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.connected.illumina.com/annotation/v3.27/data-sources/mitomap.md). # MITOMAP ### Overview MITOMAP provides a compendium of polymorphisms and mutations in human mitochondrial DNA. {% hint style="info" %} **Publication** Lott, M.T., Leipzig, J.N., Derbeneva, O., Xie, H.M., Chalkia, D., Sarmady, M., Procaccio, V., and Wallace, D.C. mtDNA variation and analysis using MITOMAP and MITOMASTER. *Current Protocols in Bioinformatics* 1(123):1.23.1-26 (2013). {% endhint %} ### Scraping HTML Pages #### Example MITOMAP is unique in that it doesn't offer the data in a downloadable format. As a result, the annotation content in Illumina Connected Annotations is scraped from the following MITOMAP pages: 1. [mtDNA Control Region Sequence Variants](https://mitomap.org/foswiki/bin/view/MITOMAP/PolymorphismsControl) 2. [mtDNA Coding Region & RNA Sequence Variants](https://mitomap.org/foswiki/bin/view/MITOMAP/PolymorphismsCoding) 3. [Reported Mitochondrial DNA Base Substitution Diseases: rRNA/tRNA mutations](https://mitomap.org/foswiki/bin/view/MITOMAP/MutationsRNA) 4. [Reported Mitochondrial DNA Base Substitution Diseases: Coding and Control Region Point Mutations](https://mitomap.org/foswiki/bin/view/MITOMAP/MutationsCodingControl) 5. [Reported mtDNA Deletions](https://mitomap.org/foswiki/bin/view/MITOMAP/DeletionsSingle) 6. [mtDNA Simple Insertions](https://mitomap.org/foswiki/bin/view/MITOMAP/InsertionsSimple) ![](/files/fT78ZCAXSGdljLndvqdg) #### Parsing Here's what the HTML code looks like: ```html ["582","MT-TF","Mitochondrial myopathy","T582C","tRNA Phe","-","+","Reported","72.90% ","0","2"], ["583","MT-TF","MELAS / MM & EXIT","G583A","tRNA Phe","-","+","Cfrm","93.10% ","0","3"], ``` We're mainly interested in the following columns (numbers indicate the HTML page above): * Position1,2,3,4 * Disease3,4 * Nucleotide Change1,2 * Allele3,4 * Homoplasmy3,4 * Heteroplasmy3,4 * Status3,4 * MitoTIP3,4 * GB Seqs FL(CR)1,2,3,4 * Deletion Junction5 * Insert (nt)6 * Insert Point (nt)6 * References/Curated References1,2,3,4 {% hint style="info" %} **MitoTIP** The MitoTIP information is used to populate the `clinicalSignificance` and `scorePercentile` JSON keys. The "frequency alert" entries are skipped since it's not directly relevant to clinical significance. {% endhint %} {% hint style="info" %} **Left alignment** Many of the variants in MITOMAP have not been normalized. As part of our import procedure, we left align all insertions and deletions. {% endhint %} {% hint style="info" %} **Variant Enumeration** Sometimes MITOMAP provides data that indicates that multiple values have been observed. Some examples of this are `C-C(2-8)` and `A-AC or ACC`. Alternate alleles containing IUPAC ambiguity codes are similarly enumerated. {% endhint %} {% hint style="info" %} **Inversions** MITOMAP inversions are currently treated as MNVs. {% endhint %} **Allele Parsing** The following MITOMAP allele parsing conventions are supported: * C123T * 16021\_16022del * 8042del2 * C9537insC * 3902\_3908invACCTTGC * A-AC or ACC * C-C(2-8) * 8042delAT ### PostgreSQL Dump File #### Example ```scss COPY mitomap.reference (id, authors, title, publication, editors, volume, number, pages, date, city, publisher, keywords, abstract, nlmid) FROM stdin; 1 Albring, M., Griffith, J. and Attardi, G. Association of a protein structure of probable membrane derivation with HeLa cell mitochondrial DNA near its origin of replication Proceedings of the National Academy of Sciences of the United States of America . 74 4 1348-1352 1977 . . Deoxyribonucleoproteins; DNA Replication; DNA, Mitochondrial; Hela Cells; Membrane Proteins; Microscopy, Electron; Molecular Weight; Neoplasm Proteins; Protein Binding Almost all (about 95 percent) of the mitochondrial DNA molecules released by Triton X-100 lysis of HeLa cell mitochondria in the presence of 0.15 M salt are associated with a single protein-containing structure varying in appearance between a 10-20 nm knob and a 100-500 nm membrane-like patch. Analysis by high resolution electron microscopy and by polyacrylamide gel electrophoresis after cleavage of mitochondrial DNA with the endonucleases EcoRI, HindIII, and Hpa II has shown that the protein structure is attached to the DNA in the region of the D-loop, and probably near the origin of mitochondrial DNA replication. The data strongly suggest that HeLa cell mitochondrial DNA is attached in vivo to the inner mitochondrial membrane at or near the origin of replication, and that a membrane fragment of variable size remains associated with the DNA during the isolation. After sodium dodecyl sulfate extraction of mitochondrial DNA, a small 5-10 nm protein is found at the same site on a fraction of the mitochondrial DNA molecules. 266177 2 Anderson, S., Bankier, A.T., Barrell, B.G., de Bruijn, M.H., Coulson, A.R., Drouin, J., Eperon, I.C., Nierlich, D.P., Roe, B.A., Sanger, F., Schreier, P.H., Smith, A.J., Staden, R., Young, I.G. Sequence and organization of the human mitochondrial genome Nature . 290 5806 457-465 1981 . . Base Sequence; Codon; DNA Replication; mtDNA; Evolution; Genes, Structural; Human; Nucleic Acid Precursors; Peptide Chain Initiation; Peptide Chain Termination; RNA, Ribosomal; RNA, Transfer; Transcription, Genetic The complete sequence of the 16,569-base pair human mitochondrial genome is presented. The genes for the 12S and 16S rRNAs, 22 tRNAs, cytochrome c oxidase subunits I, II and III, ATPase subunit 6, cytochrome b and eight other predicted protein coding genes have been located. The sequence shows extreme economy in that the genes have none or only a few noncoding bases between them, and in many cases the termination codons are not coded in the DNA but are created post- transcriptionally by polyadenylation of the mRNAs. 7219534 ``` #### Parsing From the PostgreSQL dump file, we're interested in parsing the mapping between reference IDs and the PubMed IDs: * id * nlmid {% hint style="info" %} **Why not use the PostgreSQL file for everything?** Ideally we would use this file for parsing all of our data, but the schema contains 80+ tables and we haven't invested the time yet to see how the tables are linked together to produce the 6 main HTML pages that we're interested in. {% endhint %} ### Known Issues {% hint style="warning" %} **Duplicated records** Multiple records describing the same nucleotide change are merged into the same record. If any conflicting information is found (homoplasmy, heteroplasmy, status, clinical significance, score percentile, end coordinate, variant type), an exception is thrown. * For diseases and PubMed IDs, we take the union of the values in the duplicated records. * For full length GenBank sequences, we take the largest number from each of the duplicated records since it provides the strongest evidence for this variant. {% endhint %} {% hint style="warning" %} **Skipped records** Records that represent an alternate notation of the original variant are skipped. Similarly some variants with confusing alleles (T961delT+ / -C(n)ins) are also skipped. {% endhint %} ### Download URLs * see [HTML Pages](#example) above * [PostgreSQL dump file](https://mitomap.org/downloads/mitomap.dump.sql.gz) ### JSON Output #### Small Variants ```json "mitomap":[ { "refAllele":"G", "altAllele":"A", "diseases":[ "Bipolar disorder", "Melanoma" ], "hasHomoplasmy":false, "hasHeteroplasmy":true, "status":"Reported", "clinicalSignificance":"confirmed pathogenic", "scorePercentile":83.30, "numGenBankFullLengthSeqs":2, "pubMedIds":["2316527","6299878","6301949"], "isAlleleSpecific":true } ] ``` | Field | Type | Notes | | ------------------------ | :----------: | ----------------------------------------------------------------------------------- | | refAllele | string | | | altAllele | string | | | diseases | string array | associated diseases | | hasHomoplasmy | boolean | | | hasHeteroplasmy | boolean | | | status | string | record status | | clinicalSignificance | string | predicted pathogenicity | | scorePercentile | float | MitoTIP score | | numGenBankFullLengthSeqs | integer | # of GenBank full-length sequences | | pubMedIds | string array | | | isAlleleSpecific | boolean | true when the current variant alternate allele matches the MITOMAP alternate allele | #### Structural Variants ```json "mitomap":[ { "chromosome":"MT", "begin":3166, "end":14152, "variantType":"deletion", "reciprocalOverlap":0.18068, "annotationOverlap":0.42405 } ] ``` | Field | Type | Notes | | ----------------- | :----------: | ---------------------------------------------- | | chromosome | string | | | begin | integer | | | end | integer | | | variantType | string array | | | reciprocalOverlap | float | Range: 0 - 1. Specified up to 5 decimal places | | annotationOverlap | float | Range: 0 - 1. Specified up to 5 decimal places | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.connected.illumina.com/annotation/v3.27/data-sources/mitomap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.