14430 results for ""Pennsylvania+German"+ACS+study+'Socius'+open+access"

in 14.91 milliseconds.

• International Multiple Sclerosis Genetics (IMSGC) Data Access Committee

  Dac EGAC00001001662

• ASD WGS DAC

  This data access committee will oversee the request for applications to whole genome sequencing data (WGS) generated at The Centre for Applied Genomics (TCAG), as part of our Autism Genome Project.

  Dac EGAC50000000279

• Walter and Eliza Hall Institute - University of Melbourne

  Data Access Committee for Gocuk, Lancaster et al. 2024: nanopore sequencing data of patients with choroideremia and X-linked retinitis pigmentosa, to determine X inactivation skew.

  Dac EGAC50000000301

• ADAGESIII: Contribution of genotype to glaucoma phenotype in African Americans

  Glaucoma results in vision loss due to damage of the optic nerve that is irreversible if undetected or untreated. The most common form of glaucoma is primary open angle glaucoma (POAG). While glaucoma affects all races, persons of African descent are disproportionately affected; studies show African-Americans (AAs) are about four to five times more likely than Caucasian Americans to develop the disease. Glaucoma is the leading cause of irreversible blindness in Americans of African descent, and the second leading cause in all Americans. The lack of understanding about the etiology of POAG impedes our ability to identify and treat it early in its development. Evidence of genetic contribution in the pathogenesis of POAG is well established. Since POAG tends to run in families, it is critical to identify the genetic basis of the disease in order to develop effective therapies for early intervention. While genome wide association studies (GWAS) for glaucoma have been completed for Caucasian populations, evidence from other studies suggests that a GWAS of glaucoma specific genes to the African-American population will yield unique and important findings for both this population and for glaucoma in general. A better understanding of the relationship among the stage of disease, the rate of change, ancestry, and other important risk factors being tracked in the ongoing African Descent and Glaucoma Study (ADAGES) will allow us to evaluate the relationship between genetics, visual loss and structural damage in this high-risk cohort. The scientific plan for this new study focuses on glaucoma in ∼2058 African-Americans by detailed phenotyping of new subjects, acquisition of samples from both new and established previously phenotyped study subjects for a repository, establishment of a data coordinating center, and genome wide association studies. The recruitment, enrollment, and phenotyping of both established and new subjects occurs at five clinical centers, University of California (UCSD), New York Eye and Ear Infirmary (Mt Sinai) and Columbia University Medical Center, a private practice in the Atlanta area, the University of Alabama at Birmingham, and the Robert Cizik Eye Clinic in Houston, TX. UCSD is also the location for the Data Coordinating Center and the Repository with Robert N. Weinreb as Principal Investigator. LA BioMed at Harbor-UCLA did the genotyping with a GWAS panel of ∼1 million single nucleotide polymorphisms (SNPs) using the Illumina MEGA array under the direction of Jerome Rotter, Ida Chen, and Kent Taylor.

  Study phs001673

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• MOMA Data Access Committee

  Dac EGAC00001000145

• Data Access Committee for Deciphering Developmental Disorders (DDD) Project

  Dac EGAC00001000282

• B-lineage cells in coeliac disease Data Access Committee

  The DAC will be made up of: Ida Lindeman ida.lindeman@medisin.uio.no (admin) Ludvig M. Sollid l.m.sollid@medisin.uio.no Rasmus Iversen rasmus.iversen@medisin.uio.no

  Dac EGAC50000000162

• Roifman DAC

  This Data Access Committee will oversee all requests for data submitted by Dr. Chaim Roifman at the Hospital for Sick Children in Toronto, Canada. Requests should be directed by email to chaim.roifman@sickkids.ca.

  Dac EGAC50000000396

• Sickle Cell Disease Natural History Data Resource (SCD NHDR)

  Data Access NOTE Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. BackgroundThe NHLBI initiated the Sickle Cell Disease Natural History Data Resource (SCD NHDR) to leverage existing SCD studies to build a data resource to provide phenotypic data on contemporaneous control cohorts for gene therapy trials and other studies. The potential uses of the NHDR are broad, including providing matched controls for clinical trials, observing a cohort of untreated patients as part of a natural history study, or conducting comparative effectiveness research on a subpopulation with selected co-morbidities or drug treatment profiles. The SCD NHDR includes two multi-center SCD longitudinal cohort studies with extensive annual clinical data and patient surveys, the Sickle Cell Disease Implementation Consortium (SCDIC-I and SCDIC-II) and the Globin Research Network for Data and Discovery (GRNDaD). The SCDIC-I, initiated in 2017 and concluded in June 2022, enrolled over 2400 patients with SCD from 8 US treatment centers. The SCDIC-II reconsented 1220 of the SCDIC-I patients as well as enrolling an additional 450 new patients from the same 8 centers between September 2022 and October 2023, for a total of 1670 in SCDIC-II. Only two of the many GRNDaD centers are submitting data to the SCD NHDR for deposit into BDC (approximately 122 patients). Data submissions from the SCD NHDR to BDC will be annually starting in early 2024. Description of the Study Data All data obtained for the SCD NHDR are considered common data elements (CDEs) important for studies of SCD. These CDEs were identified from several workgroups of SCD experts convened under the NHLBI's Cure-SC Initiative (https://curesickle.org/cde-catalog). The following types of data elements were abstracted from the medical record – variables that describe the SCD diagnosis, SCD co-morbidities and other clinical complications, elements from the physical examination, medications and transfusions, insurance type, laboratory measurements, healthcare utilization, history of SCD-related procedures, and measurements from cardiac procedures. The following types of data were self-reported on the patient survey – demographics, diagnosis information, pain experience, social and mental health information, other patient reported outcome domains (e.g., sleep, fatigue), and alcohol and smoking history. Standard PRO measures were used from ASCQ-Me, PROMIS and Neuro-QoL. Patient surveys were completed approximately annually. Under SCDIC-I, two medical record abstractions and labs were reported at enrollment and approximately 3 years later. Under SCDIC-II and GRNDaD, all data are collected annually. Patients may refuse to complete the survey.

  Study phs003529