1568 results for "Sweden+NDA+enforceability+one+party+signed"

in 10.29 milliseconds.

• Whole-exome sequencing of 20 samples of actinic keratosis (10s) and cutaneous squamous cell carcinoma (10s)

  Whole-exome sequencing of 20 samples of actinic keratosis (10) and cutaneous squamous cell carcinoma (10) was performed to investigate a potential relationship between DNA methylation-based subtypes and genetic mutation patterns. 7 samples were shown to belong to the stem cell-like subclass (4 AK and 2 SCC), 12 - to the keratinocyte-like subtype (6 AK and 6 SCC) and one SCC sample is unclassified (was not included in the methylation analysis). Exome regions were captured using Agilent Low Input Exome-Seq Human v5 kit and sequenced on Illumina Hiseq4000 with paired-end 100-nucleotide reads.

  Dataset EGAD00001003765

• Native American Ancient DNA sequencing

  The morphology of the first humans in the Americas (Paleoamericans) differs from that of Native Americans, and has raised the question of whether or not there are also differences in origin or genetics. A few populations who survived until relatively recently have been suggested to retain Paleoamerican morphology. One of these populations is from La Jolla. Here, we have generated genome sequence data from four La Jolla individuals in order to investigate these questions This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/

  Dataset EGAD00001002144

• Submitter Portal API

  Submitter Portal API The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have an ega-box (submission account), you can skip this step.  Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal-api

• Submission FAQ

  Submission FAQ Before Submission Is the EGA the right archive for my data? The most suitable archive for your data is dependent on the type of data you are wishing to submit and whether the data require public or controlled access. Public access is defined as complete and open access to all submitted data. On the contrary, controlled access, exerted by the EGA, requires formal applications to be made to access the submitted data files and metadata. EGA only accepts human-derived data subject to controlled access. If your submission contains other types of data, please choose the appropriate repository for it (see image below): ENA, EVA, ArrayExpress, BioSD and GWAS catalog.  Should your submission be subjected to controlled access? Data access conditions are normally defined in the original informed consent agreements signed by the participants involved in your study. All data submitted to the EGA is subject to controlled access. These consents prevent the derived data files, potentially identifiable, from being dispersed by open and public access. Controlled access data often refers to human data derived from medical research and consortium projects. If in doubt, consult the informed consent agreements that apply to your study The EGA enables you to hold a submission before publication. What data types can be submitted to the EGA? Data types accepted by the EGA can be split into three categories: Sequences: both in generic and platform-specific formats. Array-based: from raw signal files to processed matrices. Phenotypes: all possible phenotype formats are accepted. All manufacturer-specific raw data formats derived from major next generation sequencing platforms are accepted. Also generic sequence formats: flat reads in a FASTQ file, aligned sequences (BAM or CRAM files) as well as sequence variation files in VCF format. All array-based technologies are accepted, including raw data, intensity and analysis files, without any restriction on data formats accepted. We also accept and distribute phenotype data (associated to the samples) in almost any format: from an image to a README file. How long does a submission take? Submissions to EGA come in a variety of formats and sizes, thus it is difficult for us to exactly predict how long a submission will take. We, therefore, advise all of our submitters to allow as much time as possible to make a submission. Based on previous records, we anticipate that the submission process may take at least one month. The submitter’s familiarity with the procedures, possible technical issues that may arise during submission and the amount of data that is being submitted are the main factors that will affect the length of the submission process. However, each step of a regular submission should be considered when estimating the time it would take: Encryption of the files Upload of the files Metadata submission Archival of the files Release of the study and datasets to EGA webpage For example, the upload of the files depends on the submission size, while metadata submission mainly relies on each submitter’s expertise. Further, some steps (e.g. answering to inquiries) depend on the EGA Helpdesk team, which may take some days to be processed during busy times Is data deposited in the EGA secure? The EGA set-up consists of a secure computing facility for data processing, a shared EBI set-up for data submissions and distribution of data via data requests made through the EGA website. Data is also copied in the Barcelona Supercomputing Center (BSC) infrastructure, where all stored and distributed data is encrypted Data is encrypted along the submission process and stored securely, granting its access to authorised users exclusively. During the download process, through our Python Client or Aspera, all requested data is downloaded over secure https connections. All data at the EGA is encrypted, and only accessible (for log-in and download) through secure protocols. For further information please, visit our security overview. What documentation do I need to provide? All submissions require policy’s documentation: 'Data Access Agreement (DAA)', 'Data Processing Agreement (DPA)' and 'Authorized Submitters Formulary'. The data processors (EGA) and the data owners will also sign the DPA. Will all metadata be public? Among the submitted metadata we need to make the distinction between identifiable and unidentifiable metadata: (1) the former may allow the identification of the human the sample derived from (e.g. detailed geographical providence, personal name, family ancestry…); (2) while the latter can be used to interpret the data without compromising the anonymity of the patients. The majority of the metadata submitted to the EGA corresponds to the unidentifiable category (e.g. sequencer's model). This type of metadata is publicly available on the EGA website and other EBI resources/partners’ websites. On the other hand, some parts samples’ metadata are subject to being identifiable, and thus only accessible by authorized data requesters, with the exception of: 5 submitter-defined attributes of the sample: alias, title, subject_id, gender and phenotype. It is the submitter’s responsibility not to submit sensitive metadata in these public fields. 3 anonymised fields that pinpoint the sample record in archivals: sample’s EGA stable ID (EGAN…), BioSample ID (SAMEA…) and submitter’s center name. During Submission Are there any sample specific requirements for EGA? All samples submitted to the EGA must include the attributes of biological sex, subject ID (anonymised individual identifier) and phenotype information. These are critical for data findability and its analysis, and we highly recommend using controlled ontology terms where applicable. For example: defining tumour and non-tumour samples and/or defining disease state. The EGA recommends using the Experimental Factor Ontology Database to find ontologized terms that describe your sample phenotypes. How do I get an accession number to use in my publication? You will receive your study accession number (EGAS…) upon complete your submission, either: Programmatically. As soon as the metadata is submitted and validated your study will be assigned an accession number that will be given in the submission’s response. Manually registering your study and relevant metadata using the online metadata submission tool: the EGA submitter Portal. How are files uploaded to the EGA? Data files are uploaded into private submission drop boxes (i.e. environments to which you are granted access and where you can transfer your files) using INBOX or FTP. These spaces are provided as part of the submission procedure. Before uploading any file, you must encrypt your files, . Only encrypted files shall be uploaded to the drop boxes. Why does data need to to encrypted for my submitted files? It is one of the security steps the EGA has implemented. In case of a security breach, people without the proper encryption key will not be able to read or use the information that could have been leaked. This measure is essential when working with sensitive data, such as controlled access human data. All submitters must use crypt4gh to create EGA compliant files prior to uploading them. This encryption is GPG-based, using EGA’s public key. Why are my files not available if I see them in the INBOX? There exists a time window between the data upload and the availability of such files via the Submitter Portal. For this reason, some metadata (run and analysis objects) cannot be registered until at least 24 hours after the files have been uploaded to your box. Why are MD5 sum values generated for my submitted files? We require pre- and post- encryption MD5 (message-digest) checksum values to be provided for all submitted files. These 128-bit values are computed using the content of each file, creating unique sequences that allow us to ensure that file integrity has been maintained during the transfer process. In other words, if the MD5 checksums we generate and those you generated match, we infer that the content of the transferred files is correct (i.e. files are not corrupted or truncated). MD5 checksums are computed automatically using the crypt4gh tool provided. Your submission will not be accepted and may be significantly delayed if you do not provide MD5 checksum values for all data files in the required format. How can I check if my files are correctly uploaded to the inbox? It is important to check the status pf your file so you know whether your files are in the inbox, being processed, or if there is any issue with one of them. In order to check this, you should: Look for the file locally. Drag and drop it to the file table. Then bars will appear on the table, which means that we are processing it. Green: The files checksum are correct and your file will move to “ingested files”. No further actions are needed from your end.. Red: The files checksum does not match and your file needs to be re-uploaded. Please re-upload relevant files to your inbox using the same path. After Submission How do I use my accession number in my publication? We suggest the use of the below template, using your study accession ID (EGAS…) : Data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found at https://ega-archive.org and "The European Genome-phenome Archive of human data consented for biomedical research" Your study ID will be the one that groups your whole submission, and thus its usage is recommended as such. Nevertheless, all metadata submitted to EGA hold a unique and persistent identifier (starting with EGA…) that can be used to identify specific records. For example, you could reference a specific dataset (EGAD…) or sample (EGAN…) in your publications (see full list of identifiers). How do I make my data searchable? Once you have finalized your submission, you can schedule the data release. Please take into account that the release process needs time for the files to be archived in our system, and for the Helpdesk team to validate your submission. Can I withdraw (meta)data from the EGA? We have methods in place for the secure removal of deposited (meta)data. Contact EGA-helpdesk for further details. EGA complies with FAIRness of (meta)data, and thus, even when the data is removed we keep an entry for their identifiers in our system. In other words, we execute a soft delete on canceled objects (e.g. a study): metadata is still stored in our systems, but it loses all links, cannot be queried and data files cannot be retrieved anymore. The reason behind this behaviour is so that queries using withdrawn data properly respond back (see example of a canceled study). What happens to the data once it has been submitted to the EGA? When the data is submitted, the submitter can choose either keep their data private or schedule the release of their data.

  Documentation submission/metadata/submission/FAQ

• Cross-Sectional Characterization of Idiopathic Bronchiectasis

  This GDMCC protocol will study adult patients with non-CF, idiopathic bronchiectasis, whose genetic etiologies are not known. Idiopathic bronchiectasis is reportedly more common in females with certain tall, thin body types and associated with environmental organisms, such as nontuberculous mycobacterium (NTM). The other susceptibility factors predisposing to bronchiectasis or acquisition of NTM are unclear. The study will attempt to broaden the understanding of this disease by comparing gender-associated factors and NTM status. A relatively equal number of both females/males and NTM/non-NTM infected subjects will be enrolled. Approximately 300 people may be screened to find 260 eligible subjects, since a small number (e.g., 40 patients) may be diagnosed with PCD, vCF, or other known etiology as an explanation for the bronchiectasis. This single-visit protocol will use a systematic approach to characterize the physical features, radiographic patterns, and associated lower airway microbial flora. There is no natural history of disease course follow-up component to this protocol. Participants will have one outpatient clinic visit for evaluation with a physical examination including detailed body size measurements, medical history, collection of blood samples for routine lab tests and genetic analyses, and a chest X-ray if no recent one is available. Participants will also have tests of lung function, and measurement of a gas called nitric oxide in the nose. Participants whose initial tests show abnormal results may also be asked to have a nasal scrape to collect cell samples and/or a skin sweat test to measure salt concentrations. Participants will also have a sputum specimen collected during the visit and will be asked to collect two additional early morning sputum samples and a mouth rinse at home within 2 weeks of the clinic visit, and mail the sample collection materials to the research team. Careful evaluation and characterization of the physical and clinical characteristics will guide the genetic characterization of idiopathic bronchiectasis, and likely lead to an improved diagnostic approach. Identification of disease causing genes may provide new therapeutic targets.

  Study phs001279

• Metagenomics-Guided Pathogen Discovery in Travelers' Diarrhea

  Traveler's diarrhea (TD) is caused by enterotoxigenic Escherichia coli (ETEC), other pathogenic gram-negative pathogens, norovirus and some parasites. Nevertheless, standard diagnostic methods fail to identify pathogens in more than 30% of TD patients, so it is predicted that new pathogens or groups of pathogens may be causative agents of disease. A comprehensive metagenomic study of the fecal microbiomes from 23 TD patients and seven healthy travelers was performed, all of which tested negative for the known etiologic agents of TD in standard tests. Metagenomic reads were assembled and the resulting contigs were subjected to semi-manual binning to assemble independent genomes from metagenomic pools. Taxonomic and functional annotations were conducted to assist identification of putative pathogens. We extracted 560 draft genomes, 320 of which were complete enough to be enough characterized as cellular genomes and 160 of which were bacteriophage genomes. We made predictions of the etiology of disease in individual subjects based on the properties and features of the recovered cellular genomes. Three subtypes of samples were observed. First were four patients with low diversity metagenomes that were predominated by one or more pathogenic E. coli strains. Annotation allowed prediction of pathogenic type in most cases. Second, five patients were co-infected with E. coli and other members of the Enterobacteriaceae, including antibiotic resistant Enterobacter, Klebsiella, and Citrobacter. Finally, several samples contained genomes that represented dark matter. In one of these samples we identified a TM7 genome that phylogenetically clustered with a strain isolated from wastewater and carries genes encoding potential virulence factors. We also observed a very high proportion of bacteriophage reads in some samples. The relative abundance of phage was significantly higher in healthy travelers when compared to TD patients. Our results highlight that assembly-based analysis revealed that diarrhea is often polymicrobial and includes members of the Enterobacteriaceae not normally associated with TD and have implicated a new member of the TM7 phylum as a potential player in diarrheal disease.

  Study phs001352

• NHLBI GO-ESP: Family Studies (Mendelian Lipid Disorders)

  The NHLBI "Grand Opportunity" Exome Sequencing Project (GO-ESP), a signature project of the NHLBI Recovery Act investment, was designed to identify genetic variants in coding regions (exons) of the human genome (the "exome") that are associated with heart, lung and blood diseases. These and related diseases that are of high impact to public health and individuals from diverse racial and ethnic groups will be studied. These data may help researchers understand the causes of disease, contributing to better ways to prevent, diagnose, and treat diseases, as well as determine whether to tailor prevention and treatments to specific populations. This could lead to more effective treatments and reduce the likelihood of side effects. GO-ESP is comprised of five collaborative components: 3 cohort consortia - HeartGO, LungGO, and WHISP - and 2 sequencing centers - BroadGO and SeattleGO. In this study, we seek to identify the genetic cause of two monogenic lipid disorders-severe hypercholesterolemia and familial hypoalphalipoproteinemia. Monogenic severe hypercholesterolemia is clinically characterized by elevated total and low-density lipoprotein (LDL) cholesterol levels in plasma. Elevated LDL-cholesterol levels lead to excessive deposition of cholesterol in arterial walls, which eventually results in accelerated atherosclerosis and premature cardiovascular disease (CVD). Monogenic hypercholesterolemia has a prevalence of approximately one in 500 individuals, making it one of the most common inherited disorders. To date, mutations in the LDL receptor (LDLR) ligand-binding domains of APOB and PCSK9 have been shown to cause hypercholesterolemia. While mutations in these genes can explain a large percentage of clinically diagnosed patients, the underlying molecular determinant in a substantial fraction of patients remains unknown. Familial hypoalphalipoproteinemia (low HDL-C) is defined by an HDL-C below the age- and sex- specific 10th percentile. ABCA1, LCAT, and APOA1 are known to cause familial hypoalphalipoproteinemia. We hypothesize that: (1) additional novel genes responsible for Mendelian forms of low HDL-C exist; and (2) the causal gene and mutation(s) in each family may be discovered with exome analysis of just a few affected individuals in each pedigree.

  Study phs000587

• NIDDK IBD Genetics Consortium Crohn's Disease Genome-Wide Association Study

  This dataset contains data from a genome-wide association study performed with 968 Inflammatory Bowel Disease (IBD) affected cases and 995 unrelated controls using the Illumina HumanHap300 Genotyping BeadChip. Cases were selected to have Crohn's disease with ileal involvement, and controls were matched to cases based on sex and year of birth. Subjects were drawn from two cohorts: (1) persons with non-Jewish, European ancestry (561 cases and 563 controls), and (2) persons with Jewish ancestry (407 cases and 432 controls). Genotyping was performed at the Feinstein Institute for Medical Research. Seven-hundred fifty-four of the samples (468 cases and 286 controls) were taken from the NIDDK IBD Genetics Consortium cell line repository. These samples are identified in the IBD_Sample file. The subject IDs for these individuals may be used to request corresponding samples for follow-up research through the repository. In addition, complete phenotype data for these individuals are available, together with the Consortium's phenotyping manual and the forms used to collect the data. The remaining 1,209 samples were obtained from pre-existing collections ascertained through Cedars-Sinai Medical Center, Johns Hopkins University, University of Chicago, University of Montreal, University of Pittsburgh, University of Toronto, and the New York Health project (controls only). For these samples, only sex, cohort (Jewish vs. non-Jewish), and age at diagnosis (cases only) are available. Two-hundred three individuals from among the pre-existing samples did not provide consent to release their genotype data (designated as consent group 2 in the file IBD_Subject). Thus, individual genotype data are only provided for 1,760 samples. To compensate for this, we have provided summary results for each SNP. These are based on a stratified analysis testing case/control association. Fifty-one samples had a call rate less than 93% and were therefore excluded from this analysis, leaving an overall sample size of 1,963 - 51 = 1,912. X Chromosome Heterozygosity Nine samples have X chromosome heterozygosity that is neither consistent nor inconsistent with their phenotypic sex. One of these samples was found to have Turner Syndrome. The remaining 8 samples have heterozygosity ranging from 35-76%.

  Study phs000130

• CTN - 0051: Extended-Release Naltrexone vs. Buprenorphine for Opioid Treatment (X:BOT)

  The overarching goal of CTN-0051 is to foster adoption of new relapse-prevention pharmacotherapies in community-based treatment programs (CTPs) where these could have a substantial public health impact. To this end CTN-0051 will assess the comparative effectiveness of extended-release injectable naltrexone (XR-NTX, Vivitrol®), an opioid antagonist recently approved and indicated for the prevention of relapse to opioid dependence, versus buprenorphine-naloxone (BUP-NX, Suboxone®), a high affinity partial agonist indicated for maintenance treatment of opioid dependence, as pharmacotherapeutic aids to recovery. The study is conducted in 8 CTN-affiliated CTPs that provide or partner with detoxification services (inpatient/residential) which have the capacity to maintain participants opioid-free for approximately 3-7 days, have the capacity to provide medication-assisted therapy, and can provide a minimum of one group or individual counseling session per week during the 24-week treatment period. Up to 600 eligible participants will be randomized to treatment with XR-NTX or BUP-NX for 24 weeks (sufficient to include 350 participants who are randomized more than 72 hours after their last opioid). To maximize generalizability, the point of randomization is flexible, from shortly after program admission until just prior to program discharge. The primary goal of the study is to estimate the difference, if one exists, between XR-NTX and BUP-NX in the distribution of the time to relapse (i.e., loss of persistent abstinence) during the 6-month trial. The primary outcome measure is the time to the event, with the event called relapse. Secondary objectives are to: (1) compare outcome on XR-NTX versus BUP-NX across a range of clinical safety and secondary efficacy domains, (2) explore demographic, clinical, and genetic predictors of successful treatment and moderators of differential effectiveness (i.e., what variables may help clinicians choose which of these treatments is best for a given patient), and (3) collect a limited dataset to permit analyses of economic costs and benefits of the two treatments.

  Study phs002876

• UK10K NEURO GURLING

  In the UK10K project we propose a series of complementary genetic approaches to find new low frequency/rare variants contributing to disease phenotypes. These will be based on obtaining the genome wide sequence of 4000 samples from the TwinsUK and ALSPAC cohorts (at 6x sequence coverage), and the exome sequence (protein coding regions and related conserved sequence) of 6000 samples selected for extreme phenotypes. Our studies will focus primarily on cardiovascular-related quantitative traits, obesity and related metabolic traits, neurodevelopmental disorders and a limited number of extreme clinical phenotypes that will provide proof-of-concept for future familial trait sequencing. We will analyse directly quantitative traits in the cohorts and the selected traits in the extreme samples, and also use imputation down to 0.1% allele frequency to extend the analyses to further sample sets with genome wide genotype data. In each case we will investigate indels and larger structural variants as well as SNPs, and use statistical methods that combine rare variants in a locus or pathway as well as single-variant approaches. This sample set consists of DNA from multiply affected schizophrenia families. The families have been diagnosed using the SADS-L clinical instrument which gives diagnoses at the probable level of the research diagnostic criteria (RDC). In addition all diagnoses are available using DSMIIIR criteria. These criteria are widely accepted as being valid and reliable for the diagnosis of schizophrenia. All families have been collected to ensure that they are uni-lineal for transmission of schizophrenia, i.e. they have only one affected parent with schizophrenia, or a relative of only one transmitting or obligate carrier parent with schizophrenia. Families with bi-lineal transmission of schizophrenia (i.e. with both parents being affected) were not sampled for this study. All families have multiple cases of schizophrenia and related disorders. The families have been selected to ensure there are no cases of bipolar disorder within them and that they do not contain bipolar disorder in any relatives on either side of the family.For further information on this cohort please contact Hugh Gurling (h.gurling@ucl.ac.uk).

  Study EGAS00001000225