178 lines
12 KiB
HTML
178 lines
12 KiB
HTML
<html>
|
|
<head></head>
|
|
<body>
|
|
|
|
|
|
<a href="/entrez/query.fcgi?db=gap">
|
|
<img style="margin-left:auto;margin-right:auto;display:block" src="/projects/gap/images/dbGaP_logo_final.jpg" alt="dbGaP" border="0" />
|
|
</a>
|
|
|
|
</br>
|
|
<!--
|
|
<h2>About dbGaP</h2>
|
|
-->
|
|
|
|
<h3><i>dbGaP Overview</i></h3>
|
|
|
|
<p>The <b>d</b>ata<b>b</b>ase of <b>G</b>enotypes <b>a</b>nd <b>P</b>henotypes (dbGaP) was developed to archive and distribute the results of studies that have investigated the interaction of genotype and phenotype. Such studies include genome-wide association studies, medical sequencing, molecular diagnostic assays, as well as association between genotype and non-clinical traits. The advent of high-throughput, cost-effective methods for genotyping and sequencing has provided powerful tools that allow for the generation of the massive amount of genotypic data required to make these analyses possible.</p>
|
|
|
|
<p>dbGaP provides two levels of access - <a href="#open">open</a> and <a href="#controlled">controlled</a> - in order to allow broad release of non-sensitive data, while providing oversight and investigator accountability for sensitive data sets involving personal health information. Summaries of studies and the contents of measured variables as well as original study document text are generally available to the public, while access to individual-level data including phenotypic data tables and genotypes require varying levels of authorization.
|
|
More complete descriptions of the dbGaP system are available in <a href="http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2031016/">Pub Med Central</a> and the <a href="http://www.ncbi.nlm.nih.gov/books/NBK154410/">NCBI Bookshelf</a>.
|
|
</p>
|
|
|
|
<p><a href="./GetPdf.cgi?document_name=ConfidentialityCertificate.pdf">View Certificate of Confidentiality</a></p>
|
|
|
|
<p>The data in dbGaP will be pre-competitive, and will not be protected by intellectual property patents. Investigators who agree to the terms of dbGaP data use may not restrict other investigators' use of primary dbGaP data by filing intellectual property patents on it. However, the use of primary data from dbGaP to develop commercial products and tests to meet public health needs is encouraged.</p>
|
|
|
|
|
|
<a name="subm"><h3><i>Submission Policy</i></h3>
|
|
|
|
<p>Submitters who are not Federally-funded and
|
|
affiliated with an NIH IC will need to work with an NIH <a href="#dac">DAC</a>
|
|
so that proposed submission can be reviewed for consistency with
|
|
appropriate policies to protect the privacy of research participants and
|
|
confidentiality of their data. Submissions to dbGaP will not be
|
|
accepted without assurance that the submitting institution approves the
|
|
submission and has verified that the data submission is consistent with
|
|
all applicable laws and regulations, as well as institutional policies.
|
|
Submitters must also identify any Data Use limitations that are specifically
|
|
set for each individual research participants, (e.g., through their informed
|
|
consent). Please see <a href="https://gds.nih.gov/">NIH data sharing policy</a>
|
|
website for more details.
|
|
</p>
|
|
|
|
|
|
|
|
<h3><i>Data Content and Organization</i></h3>
|
|
<p><b><a name="open">Open-Access Data</b></p>
|
|
|
|
<p>Open-access data can be browsed online or downloaded from dbGaP without prior permission or authorization. These data will include, but may not be limited to, the following:</p>
|
|
|
|
<table>
|
|
<tr>
|
|
<td><b><u>dbGaP Data Type</u></b></td>
|
|
<td><b><u>Where to Find It</u></b></td>
|
|
</tr>
|
|
<tr>
|
|
<td><i>Studies</i></td>
|
|
<td>'Study' column when browsing studies</td>
|
|
|
|
</tr>
|
|
<tr>
|
|
<td></td>
|
|
<td>Result of a search under the tab 'Studies'</td>
|
|
</tr>
|
|
<tr>
|
|
<td></td>
|
|
<td>Part of the breadcrumb path of a variable or document</td>
|
|
|
|
</tr>
|
|
<tr>
|
|
<td><i>Study Documents</i></td>
|
|
<td>Link from 'Browse Studies'</td>
|
|
</tr>
|
|
<tr>
|
|
<td></td>
|
|
|
|
<td>Link under 'Associated Documents' on study report</td>
|
|
</tr>
|
|
<tr>
|
|
<td></td>
|
|
<td>Result of a search under the tab 'Study Documents'</td>
|
|
</tr>
|
|
|
|
<tr>
|
|
<td><i>Phenotypic Variables</i></td>
|
|
<td>Link under 'Browse Studies'</td>
|
|
</tr>
|
|
<tr>
|
|
<td></td>
|
|
<td>Link under 'Associated Variables' on study report</td>
|
|
|
|
</tr>
|
|
<tr>
|
|
<td></td>
|
|
<td>Result of a search under the tab 'Variables'</td>
|
|
</tr>
|
|
<tr>
|
|
<td><i>Genotype-Phenotype Analyses</i></td>
|
|
|
|
<td>Link under 'Associated Analyses' on variable report</td>
|
|
</tr>
|
|
<tr>
|
|
<td></td>
|
|
<td>Link under 'Associated Analyses' on study report</td>
|
|
|
|
</tr>
|
|
</table>
|
|
|
|
<p>Please note that this is a general description of what is available to open- access users. Data available to open-access users may vary between studies and may also differ from what is described here without notice. You can find more details regarding data access policies for specific studies on the individual study report pages.</p>
|
|
|
|
<p><b><a name="controlled">Controlled-Access Data</b></p>
|
|
<p>Controlled-access data can only be obtained if a user has been authorized by the appropriate Data Access Committee (<a href="#dac">DAC</a>). Information on <a href="#request-controlled">requesting controlled data access</a>, is available below. Data available to authorized investigators may include the following:</p>
|
|
|
|
<ul>
|
|
|
|
<li>de-identified phenotypes and genotypes for individual study subjects</li>
|
|
<li>pedigrees</li>
|
|
<li>pre-computed univariate associations between genotype and phenotype (if not made available on the public site)</li>
|
|
</ul>
|
|
|
|
<p>Since data access policies are determined on a per-study basis, data available to users with controlled access authorization may vary between studies and may also change from what is described here without notice. You can find more details regarding data access policies for a specific study on the study report page along with a link to the appropriate authorizing body.</p>
|
|
|
|
<h3><a name="request-controlled"><i>Requesting Controlled-Access Data</i></a></h3>
|
|
<p>Access to controlled data in dbGaP will be granted by an NIH Data Access Committee or <a href="#dac">DAC</a>. Users wishing access to controlled data must submit a Data Use Certification, or <a href="#duc">DUC</a>, to the appropriate NIH DAC for approval. DAC
|
|
approval for controlled data access will be dependent upon completion of the DUC, and confirmation that the proposed research use is consistent with patient consent forms and any constraints identified by the institutions that submitted the dataset(s) to dbGaP.
|
|
Links to a study's DAC will be found on the study report page. Consult this instructional video to see <a href="https://www.youtube.com/watch?v=-3tUBeKbP5c&feature=iv&src_vid=ekFlMgLFZDE&annotation_id=annotation_2856830007">how to make a request<a>.</p>
|
|
|
|
<p>Submitters of controlled-access data housed in dbGaP may retain the exclusive right to publish an analysis of their submitted data for a specified period of time. Users of controlled-access data should consult the DUC or the study report page to determine the specific publishing exclusivity period for that study.</p>
|
|
|
|
<p>Access to individual-level data housed in dbGaP is under the jurisdiction of the sponsoring institute. Therefore, any questions regarding access to controlled data should be directed to the DAC for the study in question, and not to NCBI.</p>
|
|
|
|
<h3><i>Submitting Data to dbGaP</i></h3>
|
|
<p>Prior to submitting data to dbGaP a study must be registered by a NIH Genomic Program Administrator (GPA). Submitters should consult this high level overview of <a
|
|
href="http://www.ncbi.nlm.nih.gov/projects/gap/cgi-bin/GetPdf.cgi?document_name=HowToSubmit.pdf">the study registration and data submission process</a>. In addition to providing individual-level phenotype and genotype data to dbGaP, we also require the submission of sufficient metadata to enable NCBI to provide a browse-able interface for a study.</p>
|
|
|
|
<p>The following should be included in submissions to dbGaP:</p>
|
|
<ul>
|
|
<li>study documents (i.e. manual of procedures, protocols, questionnaires, consent forms, etc.)</li>
|
|
|
|
<li>data dictionary (a description of measured variables with pointers to those parts of study documents that describe how variables were measured)</li>
|
|
<li>any other supporting documentation</li>
|
|
<li>phenotype, exposure, genotype, and pedigree data without identifiable information, created using a random, unique code whose key will be held by the submitting institution</li>
|
|
<li>a guarantee that the identities of research participants will not be disclosed to dbGaP, or to secondary users of the coded data, without appropriate institutional approvals (due to this guarantee, research participants should not expect the return of individual research results derived from the analyses of submitted data)</li>
|
|
<li>a statement verifying that the data submitted to dbGaP for subsequent sharing and appropriate research is consistent with the initial informed consent process completed by study participants</li>
|
|
<li>a statement identifying any uses of the data that are specifically excluded by the informed consent process</li>
|
|
|
|
<li>a statement from the data's originating institution that submission of the data is in accord with all applicable laws and regulations</li>
|
|
</ul>
|
|
|
|
<p>Please note that these are general submission requirements. Since data submission policies are still being developed by participating studies/institutions, submission requirements may vary between studies and may also change from what is described here without notice.</p>
|
|
|
|
<p>As dbGaP is a NCBI data distribution service, the control and management of the data housed in dbGaP is under the jurisdiction of the sponsoring institute or study; therefore, any questions regarding submission requirements or other data issues should be directed to the <a href="#dac">DAC</a> for the study in question. </p>
|
|
|
|
<h3><i>Glossary</i></h3>
|
|
<p><a name="dac"><b>Data Access Committee (DAC)</b>: Data Access Committees are established based on programmatic areas of interest as well as technical and ethical expertise. All DACs will operate through common principles and under similar mechanisms to ensure the consistency and transparency of the controlled- data access process. </p>
|
|
|
|
<p><a name="duc"><b>Data Use Certification (DUC)</b>: A Data Use Certification is the application a user submits to a particular study's Data Access Committee (DAC) for consideration for authorized use of controlled dbGaP data. The Data Use Certification should include a list of the controlled data set(s) required by the user and a brief description of the proposed research use of the requested data. The user must also offer the following assurances in the Data Use Certification that:</p>
|
|
|
|
<ul>
|
|
<li>the data will only be used for approved research</li>
|
|
<li>data confidentiality will be protected</li>
|
|
<li>all applicable laws, local institutional policies, and terms and procedures specific to the study's data access policy for handling dbGaP data will be followed</li>
|
|
|
|
<li>no attempts will be made to identify individual study participants from whom data were obtained </li>
|
|
<li>controlled-access data from dbGaP will not be sold or shared with third parties</li>
|
|
<li>the contributing investigator(s) who conducted the original study and the funding organizations involved in supporting the original study will be acknowledged in publications resulting from the analysis of those data</li>
|
|
<li>all NIH supported genotype/phenotype data and conclusions derived directly from them will remain in the public domain, without licensing requirements</li>
|
|
<li>an annual research progress report will be submitted to the study's <a href="#dac">DAC</a></li>
|
|
|
|
</ul>
|
|
|
|
<p>Finally, the completed <a href="#duc">DUC</a> must be co-signed by a designated official representing the institution for which the applicant works.</p>
|
|
|
|
<p>Please note that this is a general description of the <a href="#duc">DUC</a>. Since data access policies are still being developed by participating studies/institutions, controlled access requirements, and hence, <a href="#duc">DUC</a> requirements may vary between studies and may also change from what is described here without notice. Additional details regarding controlled access requirements for a specific study will be provided on the study report page.</p>
|
|
|
|
</body>
|
|
|
|
</html>
|