Mendelian Inheritance in Man (OMIM) - omim

The grade for the resource as automatically determined by the criteria violations.
A full description of the resource from the resource itself, if possible.
OMIM is a comprehensive, authoritative compendium of human genes and genetic phenotypes with full-text, referenced overviews that contains information on all known mendelian disorders and over 12,000 genes. OMIM focuses on the relationship between phenotype and genotype.
Last curated
(Optional) The ISO 8601 date of when the resource was last curated.
URL for the resource.
Source type
(Optional) How the resource relates to the data it contains. Current allowable entries are: "unknown", "repository", "source", "integrator", and "warehouse".
Curation status
Whether or not annotation is complete on this resource. Current allowable entries are: "complete", "incomplete", and "nonpublic".
The area of research for the resource.
The type of data the resource contains.
(Optional) Tags to describe the resource and its data.
disease-phenotype association
gene-disease association
variant-disease association
(Optional) Links to the resource's data.
The license that is used by the resource. We use SPDX where we can or: "inconsistent", "public domain", "unlicensed", "all rights reserved", or "custom".
License type
The type of license that is being used. This will be to define compatible data pools in the future; we only use the grossest terms now. If it is not known "unknown" is used. Current possible values are: "unknown", "unlicensed", "copyleft", "permissive", "public domain", "copyright", "restrictive", or "private pool".
License location
(Optional) The link to the resource license.
Focused curation
(Optional) Setting this flag to true indicates that the licensing was combinatorially complicated enough (as is the case in some commercial licenses) that the curator chose to wear a single "hat" during the process. From the site text: "While we try to cover as much of the licensing possibilities of a data resource that we can, in a few cases we may choose a particular "hat" to wear while evaluating to prevent a combinatorial explosion, which may also reduce the clarity of our curations for the community. In these cases, we may take on the role of a (1) non-commercial (2) academic (3) group that is (4) based in the US and trying to (5) create an aggregating resource, noting that other entities may have different results in the license commentary."
(Optional) Structured issues with the license. For every issue discovered with a resource, there should be a corresponding item in the license-issues field that marks the /exact/ violation, along with any comments. This field can be used by resources as the first step to improvement, as well as clarify any surrounding circumstances. Any issues or thoughts about a resource that do not slot into one of the criteria violations can go into the license-commentary field.
Criteria A.2.2: The license at link is custom.
Criteria B.1: Agreement section 13 requires downloads to be updated by downstream; section 14 discussion arbitrary API key revocation.
Criteria C.2: Downloads and access are provided post-registration; as the API key is used for access control, it violates the C.2 example.
Criteria D.1.2: Sections 8, 9, and 10 of the agreement make it seems that while a non-profit reasearcher may access the data, there is no reuse (pass-through) possible.
Criteria E.1.2: Sections 8, 9, and 10 of the agreement make it seems that while a non-profit reasearcher may access the data, there is no reuse (pass-through) possible.
(Optional) Further commentary on the license, possibly including the though process of the curations and things like locations of additional licenses.
• Assuming that one registered, it seems that data access would be relatively pain-free; so no C.1 violation.
• See also: and for additional access information.
• It is worth reading through the linked agreement; there are many sections that are restrictive or would be best interpreted with legal advice.
(Optional) Marker noting that there was some extended internal discussion or controversy about the evaluation of the licensing terms. If this is marked at "true", the controversy, or a link to a permanent archive of the controversy, must be sufficiently contained in the "license-commentary" to reconstruct the issues.
(Optional) Resource contact information, link, email, or whatever is public.
(Optional) Semi-structured list of supporting grants.
\"OMIM curation and updating is funded by a grant from the National Human Genome Research Institute (NHGRI) [1U41HG006627]. Initial development of the website was supported by Johns Hopkins Medicine and a grant from the Maryland Department of Health and Mental Hygiene. OMIM is hosted at University of California Santa Cruz (UCSC) Genome Bioinformatics.\"

All copyrightable materials on this site are © 2019 the (Re)usable Data Project under the CC-BY 4.0 license.
The (Re)usable Data Project is funded by the National Center for Advancing Translational Sciences (NCATS) OT3 TR002019 as part of the Biomedical Data Translator project and U24TR002306 as part of the CTSA Program National Center for Data to Health (CD2H).
The (Re)usable Data Project would like to acknowledge the assistance of many more people than can be listed here. Please visit the about page for the full list.