14136 results for "Buy fc coins Buyfc26coins.com is EA Sports official for FC 26 coins Their customer service is very responsive..7ZgM"

in 24.64 milliseconds.

• Genomic Characterization CS-MATCH-0007 Arm C1

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm C1 is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with MET amplification are treated with Crizotinib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002177

• Genomic Characterization CS-MATCH-0007 Arm P

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm P is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with PTEN loss by IHC are treated with the drug GSK2636771. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002152

• Genomic Characterization CS-MATCH-0007 Arm Z1B

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm Z1B is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with CCND1, CCND2, and/or CCND3 amplifications are treated with Palbociclib. This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including DNA from tumor tissue and whole blood.

  Study phs002180

• Genomic Characterization CS-MATCH-0007 Arm Q

  The CS-MATCH-0007 protocol is part of a collaboration between the Center for Cancer Genomics (CCG) and the Division of Cancer Treatment and Diagnosis (DCTD) to perform whole-exome sequencing and RNA sequencing using pre-and post-treatment tumor biopsy specimens from patients enrolled on a treatment arm of the NCI-MATCH Clinical Trial (EAY131). The goal of this study is to identify the molecular basis for response and resistance to targeted therapies that are matched to specific genomic alterations found in their cancers. Arm Q is one of the treatment sub-protocols within the NCI-MATCH Clinical Trial (EAY131) where patients with HER2 amplification are treated with Kadcyla® (ado-trastuzumab emtansine). This subprotocol is one of the treatment arms included in the CS-MATCH-0007 protocol and will provide specimens for the program including tumor tissue and whole blood.

  Study phs001926

• About

  About What's the EGA? The European Genome-phenome Archive (EGA) is a global network for permanent archiving and sharing of personally identifiable genetic, phenotypic, and clinical data generated for the purposes of biomedical research projects or in the context of research-focused healthcare systems. Jointly managed by the European Bioinformatics Institute (EMBL-EBI) in Cambridge (UK) and the Centre for Genomic Regulation (CRG) in Barcelona, we aim to advance biomedical research and promote personalised medicine worldwide by enabling discovery of and access to human genomic and health research data. The EGA contains data collected from individuals whose consent agreements authorise data release for specific research use to bona fide researchers. We ensure strict security measures to control access to the data and maintain patient confidentiality. With expertise in data management and technical infrastructure, we promote FAIR data reuse and enable researchers to share their data securely. By leveraging public funding and our strategic partnerships, the EGA provides a free service for permanent data storage, data discovery, and secure data access. In addition, we foster a federated network to provide transnational access to human research data in compliance with legal frameworks. For additional information about the EGA, please contact: Helen Parkinson and Mallory Freeberg EMBL European Bioinformatics Institute Arcadi Navarro, Roderic Guigó, and Jordi Rambla Center for Genomic Regulation History The European Genome-phenome Archive was launched in 2008 at the European Bioinformatics Institute (EMBL-EBI), an outstation of the European Molecular Biology Laboratory (EMBL), to address an identified need for archiving and sharing the results of genome-wide association studies from the Wellcome Trust Case Control Consortium. With the signing of a memorandum of understanding in 2013 and a formal agreement in 2016, the EGA became a joint project of EMBL-EBI and the Centre for Genomic Regulation (CRG). The two institutes work together to support the EGA services, including supporting submissions, website, strategic leadership, and data infrastructure developments. In 2022, the Federated EGA was officially launched with the signature of the first five countries: Finland, Germany, Norway, Spain, and Sweden. With more than 20 additional nodes worldwide preparing to join, the Federated EGA aims to become the largest human omics data sharing initiative towards understanding human health and disease. EGA overview If you're a researcher you may need to deposit, manage, or access genomic data in a secure and regulated way. The European Genome-phenome Archive (EGA) is a platform that facilitates these processes, ensuring that sensitive data is stored and shared in accordance with legal and ethical regulations. Submission process To start a submission, you need to become an EGA submitter. For that, you’ll need to sign a Data Processing Agreement (DPA) with us, that defines the terms and conditions under which your data will be processed and shared within the EGA system. The access to each study is controlled by its Data Access Committee (DAC). The DAC is responsible for managing data access requests and ensuring that the release of data is in accordance with the General Data Protection Regulation (GDPR). Please, note that once your data is released, all public metadata related to your study and dataset(s) will be searchable on the EGA website. However, the files are only accessible under controlled access, which means that a DAC has to agree to a previous data access request. Request process It is possible to submit an access request to data stored at the EGA. The DAC assigned to the study will assess the request and, if approved, grant access to the data. Requesters must provide sufficient justification for your request and comply with the intended data usage in order to get access to it. Each dataset is covered by a Data Access Agreement (DAA) that defines the terms and conditions of use for the specified dataset/s. The DAA is created and provided by the DAC, and must be signed by the individual requesting access to the given dataset/s. Download process Once the request for access is approved, the data and metadata can be downloaded. The EGA offers various download options to fit the needs: it is possible to preview files without downloading them, download specific files of interest, or even download terabytes of data. Overall, the EGA provides a secure and regulated environment for depositing, managing, and accessing human data. Regardless of the role - submitter, DAC member, or requester - the EGA provides assistance for each while ensuring that sensitive data is managed in an ethical and responsible manner. More information on how EGA handles data is available in the EGA dataflow.

  Documentation about/ega

• Immuno-genomic Profiling of Biopsy Specimens Predicts Neoadjuvant Chemotherapy Response in Esophageal Squamous Cell Carcinoma

  Esophageal squamous cell carcinoma (ESCC) is one of the most aggressive cancers and is primarily treated with platinum-based neoadjuvant chemotherapy (NAC). Some ESCCs respond well to NAC. However, biomarkers to predict NAC sensitivity and their response mechanism in ESCC remain unclear. We introduce a model by machine learning and validated its potential to predict the NAC response in ESCC. To create this model, we performed whole genome sequencing and RNA-seq analysis on totally 141 ESCC biopsy specimens before NAC treatment and analyzed their immuno-genomic features and association with NAC response. Neutrophils infiltration could play an important role in ESCC response to NAC. We also demonstrated that specific copy number alterations and copy number signatures in the ESCC genome were significantly associated with NAC response. The interactions between the tumor genome and immune features of ESCC are likely to be a new indicator of therapeutic capability and a new therapeutic target for ESCC, and machine learning prediction for NAC response is useful.

  Study JGAS000535

• What is a DAC?

  What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions.  You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks.  Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, the EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

  Documentation access/data-access-committee/what-is-dac

• 16S-based fecal microbiota composition of the Milieu Intérieur Cohort

  The Milieu Intérieur project is a population-based study coordinated by the Institut Pasteur, Paris. The objective is to dissect the interplay between genetics and environment and their impact on the immune system. One of the primary goals of the project is to ascertain the role of the microbiota in regulating immune programs.

  Study EGAS00001003419

• PyEGA3 download client

  PyEGA3 Checks prior to download - Is the dataset available for download? Most datasets are available using the PyEGA3 Download client, except for specific legacy datasets. For these ones, refer to Live Outbox distribution, an alternative way to download these datasets.If the dataset you've been granted access to begins with the ID EGAD5XXXXXXX, please refer to the Live Outbox distribution. If the dataset you have been granted access to contains encrypted data (filename ending in .gpg), contact EGA Helpdesk for detailed information on how to download these files.General Information The PyEGA3 download client is available at its GitHub repository. In its README you will find a step by step guide on how to use it to download files you have been granted access to. PyEGA3 implements the GA4GH-compliant HTSGET protocol supporting requests over genomic ranges. This enables the download of specific regions of interest rather than the entire file. HTSGET is not possible for all the files held by EGA: if the dataset does not contain index files (e.g. filename ending in *.crai), then genomic range requests cannot be performed. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Check out our video tutorial! Frequently Asked Questions General questions How do I download the datasets to which I have been granted access? After setting up your EGA download account, you can proceed to download using the EGA download client – PyEGA3. The pyEGA3 download client is a python-based tool for viewing and downloading files from authorised EGA datasets. This download client is continuously being developed for more user-friendly download experiences. Can I download the dataset’s metadata via the download client? No, the download client cannot be used to download metadata. Registered EGA users can download metadata of an authorised dataset by logging into the EGA webpage and navigating to the dataset of choice. Approximately two thirds down the page you will find the option to download the metadata as a zip file. How do I download large datasets as quickly as possible? The main EGA download client is pyEGA3 download client, a python-based tool for viewing and downloading files from authorised EGA datasets.We could exceptionally consider the option of an Aspera download for users experiencing very slow download rates or facing particular issues.Contact the EGA Helpdesk for further information. Pre-requirement and Installation What are the major requirements for the PyEGA3 download client installation and usage? The PyEGA3 client is compatible with any OS with Python 3.6+ installed. The client requires a connection to the internet, sufficient space on the destination drive, and the EGA download account credentials. Where can I find the PyEGA3 download client installation and download instructions? We strongly recommend checking our video tutorial demonstrating the usage of PyEGA3 from installation to file download. More detailed information is available at PyEGA3 GitHub. What ports are required for the PyEGA3 download client to function? PyEGA3 makes HTTPS calls to the EGA Data API (https://ega.ebi.ac.uk:8443). This port 8443 must be reachable from the location where PyEGA3 is executed to avoid timeouts. PyEGA3 download client How to update the PyEGA3 download client to be on the latest version? Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 --upgrade I do not have an active EGA account. Can I test the download with the PyEGA3 download client? An EGA download test account (ega-test-data@ebi.ac.uk) has been created for troubleshooting and training purposes. The test account does not require an EGA username and password because it contains publicly accessible files from the 1000 Genomes Project. More information about the use of this account and log in details are available at pyEGA3. I lost my connection while the download was in progress. Does this mean that I have to download the file again from the start? The PyEGA3 download client supports automatic resumption of downloads. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the resume feature, downloads will automatically resume if you encounter any errors or if the connection is interrupted. How can I improve the overall download speed of the PyEGA3 download client? Download speeds can be optimised using the --connections parameter which will parallelise download at the file level. If the --connections parameter is provided, all files >100Mb will be downloaded using the specified number of parallel connections. It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Why is my file taking a long time to be saved? Please note that when a file is being saved, it goes through two processes. First, the downloaded file "chunks" are pieced back together to reconstruct the original file. Secondly, PyEGA3 calculates the checksum of the file to confirm that the file was downloaded successfully. Larger files will take more time to reconstruct and validate the checksum. Why is the HTSGET protocol not working with my dataset of interest? PyEGA3 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file, saving both time and storage space. Please note that in order for the genomic range requests to work for a BAM, CRAM or VCF file there must be an associated BAI, CRAI or TBI file, respectively. If the dataset does not contain these index files then genomic range requests cannot be performed. After download Do I need to decrypt data files downloaded through the pyEGA3 download client? Files are transferred over secure HTTPS connections and received unencrypted, thus there is no need for decryption after data download. What is the purpose of an MD5 file? After the download completes, file integrity is verified using checksums. The PyEGA3 download client automatically verifies each file’s unencrypted md5 after download to ensure that the file was downloaded correctly from the EGA. Errors Why do I get a “400 Client Error” while trying to access the download client? Ensure that your credentials are formatted correctly. Please contact the EGA Helpdesk if you are unsure about your account’s username (i.e. your email address). Why do I get a “500 Server Error”? It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Otherwise, 500 server errors are internal server errors from EGA’s end. Retry after some time and, if the 500 error persists: check our homepage or Twitter for any outage information or report it to EGA Helpdesk. Why do I get a “slice error”? This type of error occurs when one slice download was prematurely interrupted. Please re-start the same download. The download client will pick up any partial download and download any missing slices. Why do I get the error “Dataset' EGADXXXXXXXXXXX' is not in the list of your authorised datasets”? Please note that the data access was given to the email (username) provided to the Data Access Committee (DAC) in your official request. Therefore, you shall check that the account that you are using is the same one that you sent to the DAC. Why do I get “ERROR:root:Failed to obtain IP address”? This might mean that the connection ports are blocked. Check that the port 8443 is reachable.In case the port is reachable and the error persists, please try to modify the file pyega3.py on line 44 in the python module installation: Replace endpoint = 'https://ipinfo.io/json' with endpoint = 'https://api.myip.com' Why do I get the error “Invalid username, password or secret key - please check and retry”? Make sure that you are using the correct credentials (username and password) and there is no typo. Contact EGA Helpdesk if the problem persists.

  Documentation access/download/files/pyega3

• The Primary Open-Angle Glaucoma Genes and Environment (GLAUGEN) Study

  Background Information: Primary open-angle glaucoma (POAG) is an age-related, intraocular pressure (IOP)-dependent progressive optic neuropathy that ultimately leads to irreversible blindness. Vision loss from POAG is a condition of public health significance. Current evidence suggests that POAG is a polygenetic disease modified by environmental influences. Despite the fact that a positive family history of disease is an important risk factor for POAG, conventional linkage and candidate gene approaches have revealed less than 5% of the genetic component of the disease. Furthermore, there is no consensus on environment risk factors for POAG. Elevated IOP is the only modifiable risk factor for POAG; yet, lowering IOP slows, but does not halt the disease process. Study Objectives: The overall goal of our research is to elucidate the pathogenesis of POAG so that cost-effective disease detection and primary prevention strategies can be implemented. The primary aim of the Glaucoma Gene Environment Initiative (GLAUGEN), funded by the Human Genome Research Institute (NHGRI), is to discover genetic loci associated with POAG. The secondary aim of GLAUGEN, funded by NHGRI and the National Eye Institute, is to discover gene environment interactions in POAG. Methods and study populations: For this study, we have assembled cases and controls from three studies: the Nurses&#39; Health Study (NHS), the Health Professionals Follow-up Study (HPFS) and the Genetic Etiologies of POAG (GEP) project based at Massachusetts Eye and Ear Infirmary (MEEI). This case-control group includes 1057 unrelated cases and 1272 controls. Members of the NHS and HPFS also have repeated environmental exposure data collected prior to a diagnosis of POAG. NHS - The Nurses Health Study started in 1976 under the direction of Dr. Frank E. Speizer. With funding from the NIH, registered nurses from 11 US states were invited to complete a detailed questionnaire regarding lifestyle and health biennially. Initially, 121,000 women responded to the baseline questionnaire. Currently, Dr. Susan Hankinson serves as the program director for the NHS. HPFS - The Health Professionals Follow-up Study began in 1986 under the direction of Drs. Walter Willett and Meir Stampfer. Under the auspices of the NIH, they enlisted 51,529 male health professionals from throughout the US to complete similarly designed biennial questionnaires. Beginning in 1990, questions regarding ocular health were added to biennial questionaires completed by health professionals participating in the NHS and HPFS. This allowed us to formulate (PI: S. Hankinson; NEI) and maintain (PI: L. Pasquale; NEI) a cohort at risk for POAG derived from the respective general cohorts who were under ophthalmic care. We then developed a definition of POAG that allowed us to identify cases from a population that was geographically dispersed. The centerpiece of this definition is the presence of reproducible visual field loss consistent with nerve fiber layer (NFL) dropout (the NFL contains the axons that comprise the optic nerve) on reliable tests. Reproducible visual field loss occurred in the context of anterior segment findings that did not suggest a secondary cause of elevated IOP and posterior segment findings that did not suggest a secondary cause of visual field loss. We selected controls from the cohort at risk for POAG on the basis of age, gender and time period when cases were identified. GEP - The Genetic Etiologies of POAG was initiated in 1996 with funding from the National Eye Institute under the direction of Dr. Janey Wiggs. The purpose of this work was to discover novel genetic loci associated with POAG. In the GEP, cases were derived predominantly from the Glaucoma Service at MEEI. The majority of cases had an examination by a glaucoma specialist and met the definition for POAG used in NHS and HPFS. Cases with only one reliable visual field consistent with NFL dropout were included if there was a cup-disc ratio of 0.7 or more. The majority of controls were patients who presented to the MEEI comprehensive ophthalmology service for routine eye examination or from spouses of MEEI patients with secondary forms of glaucoma. Other controls were identified from regional glaucoma screenings held throughout Massachusetts. Members of GEP have detailed ocular phenotype data but limited information on environmental exposures. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to primary open-angle glaucoma through large-scale genome-wide association studies of three well-characterized cohorts of cases and controls, some in matched pairs. Genotyping was performed at the Broad Institute of MIT and Harvard, a GENEVA genotyping center. Data cleaning and harmonization were performed at the GEI-funded GENEVA Coordinating Center at the University of Washington.

  Study phs000308