1186 results for "fut credit 26 Visitez le site Buyfc26coins.com Paiement sûr et coins FC 26 sans attente.gZv1"

in 16.93 milliseconds.

• Neurodevelopmental Genomics: Trajectories of Complex Phenotypes

  This study is a collaboration between the Center for Applied Genomics (CAG) at Children's Hospital of Philadelphia (CHOP) and the Brain Behavior Laboratory at the University of Pennsylvania (Penn). The cohort consists of youths aged 8-21 years who consulted the CHOP network and volunteered to participate in genomic studies of complex pediatric disorders. All participants underwent clinical assessment, including a neuropsychiatric structured interview and review of electronic medical records. They were also administered a neuroscience based computerized neurocognitive battery (CNB) and a subsample underwent neuroimaging. These are described separately below. Clinical Testing: GOASSESS, a computerized, structured screener developed from a modified version of the Kiddie-Schedule for Affective Disorders and Schizophrenia (K-SADS, Kaufman et al. 1997, PMID: 9204677). Components of the interview include a timeline of life events, demographics and medical history, Global Assessment of Functioning, and Interviewer Observations. A psychopathology symptom and criterion-related assessment of mood disorders (depression, mania/hypomania), anxiety disorders (overanxious/generalized-, separation-, social-anxiety, specific phobia, panic disorder, agoraphobia, obsessive compulsive disorder, post-traumatic stress disorder), behavioral disorders (attention deficit hyperactivity disorder, oppositional defiant disorder, conduct disorder), psychosis spectrum (psychosis and prodromal symptoms), eating disorders, suicidal thinking and behavior, and treatment history. This is also based on K-SADS. An abbreviated Family Interview for Genetics Studies (FIGS) to assess major domains of psychopathology in the proband's first-degree relatives. Computerized Neurocognitive Battery: The CNB, developed for large-scale studies, yields measures of accuracy and speed for domains of executive-control functions (abstraction, attention, working memory), episodic memory (verbal, facial, spatial), complex cognitive processing (language reasoning, nonverbal reasoning, spatial processing), social cognition (emotion identification, emotion intensity differentiation, age differentiation) and sensorimotor and motor speed. The following neurobehavioral domains were assessed: Penn Conditional Exclusion Test is a measure of abstraction and concept formation. Participants decide which of 4 objects does not belong with the other 3, based on one of three sorting principles, which change. Feedback is used. Attention: The Penn Continuous Performance Test. Participants respond to a set of 7-segment displays whenever they form a digit or letter. Working Memory: The Letter N-back Test displays sequences of uppercase letters with a stimulus duration of 500 ms (ISI 2,500 ms.) In the 0-back condition, participants respond to a single target (i.e., X). In the 1-back condition they respond if the letter is identical to that preceding it. In the 2-back condition, they respond if the letter is identical to that presented two trials back. Verbal Memory: The Penn Word Memory Test presents 20 target words that are then mixed with 20 distracters equated for frequency, length, concreteness and low imageability. A 20 min delayed recall procedure is also administered. Face Memory: The Penn Face Memory Test presents 20 digitized faces that are then mixed with 20 distracters equated for age, gender and ethnicity. The procedure is repeated at 20 min delay. Spatial Memory: The Visual Object Learning Test uses Euclidean shapes as stimuli with the same paradigm as the word and face. Language and Analogical Reasoning: The Penn Verbal Reasoning consists of verbal analogy problems. Spatial Processing: Penn Line Orientation Test presents two lines at an angle, and participants click on a button that makes one line rotate until it has the same angle as the other. Emotion Processing: Facial displays of 4 emotions (Happy, Sad, Anger, Fear) and Neutral faces, 8 each, are presented and the subject identifies the emotion in a multiple-choice format. The facial stimuli are balanced for gender, age, and ethnicity. Sensory-motor Processing Speed: The task requires moving the mouse and clicking on a green square that disappears after the click. The square gets increasingly small and appears in unpredictable locations. Neuroimaging Protocol: Studies were performed at Penn using a Siemens Trio (Erlangen, Germany) 3T scanner equipped with 40mT/m gradients and 200 mT/m/s slew-rates. RF transmission utilized a quadrature body-coil, and reception a 12-channel head coil optimized for parallel imaging. Total image acquisition time was about 45 min. Structural Imaging: The T1-weighted protocol utilized a 3D, inversion-recovery, and magnetization-prepared rapid acquisition gradient echo. Relevant imaging procedures include: Structural magnetic imaging Diffusion tensor imaging ASL perfusion BOLD fMRI Neuroimaging tasks: Fractal N-Back Task of Spatial Working Memory Face Emotion Identification Task Neuroimages: The current data release includes over 9700 MRI images that may be downloaded through Authorized Access.

  Study phs000607

• Privacy Notice for EGA Web user

  Privacy Notice for EGA Public Website This Privacy Notice explains what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. 1. Who controls your personal data and how to contact us? European Genome- Phenome Archive - EGA offers a service for permanent archiving and sharing of all types of personally identifiable genetic and phenotypic data resulting from biomedical research projects, jointly managed by European Molecular Biology Laboratory – European Bioinformatics Institute (EMBL-EBI) and Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG). EMBL-EBI and CRG represent joint Data Controllers’ of processing of your personal data. They and their Data protection officers may be contacted for data protection queries and for exercising your rights under Section 8. You may contact EMBL-EBI, represented by Mallory Freeberg, by: email at: mfreeberg@ebi.ac.uk , or post at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: telephone at +49 6221 387-8590, email at dpo@embl.org , or post at EMBL Heidelberg, Data protection officer, Meyerhofstraße 1, 69117 Heidelberg, Germany. You may contact CRG, whose EGA team is represented by dr. Jordi Rambla de Argila, by: email at jordi.rambla@crg.eu, or post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), Dr.Aiguader 88, PRBB Building, 08003 Barcelona, Spain. CRG Data protection officer may be contacted by: email at dpo@crg.eu post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), C/ Dr. Aiguader, 88, PRBB Building, 08003 Barcelona, Spain. 2. Which is the lawful basis for processing personal data? For providing you access to the website and for offering support whilst using the website, we need your consent under Article 5 (2) of the IP 68 (equivalent to Article 6 (1)(a) of the GDPR). For monitoring your activities on the website, we process your personal data on the grounds of important public interest. Such legal basis is found in Article 5(1)(a) of EMBL Internal Policy No 68 on General Data Protection (hereinafter IP 68), which is equivalent to Article 6 (1)(e) of the EU General Data Protection Regulation (hereinafter GDPR) and upon which personal data are processed for the achievement of the aims laid down in 1973 agreement establishing EMBL, such as the promotion of the cooperation in the fundamental research, in the development of advanced instrumentation and in advanced teaching in molecular biology and dissemination of information. 3. What personal data is collected from users of the service? How do we use this personal data? We collect the following personal data from you: IP addressesDate and time of a visit to the service website Operating systemAmount of data transmittedBrowserEmail address (only when support is requested by the user) The data controller will use your personal data for the following purposes: To provide the user access to the serviceTo better understand the needs of the users and guide future improvements of the serviceTo monitor website activities according to and in compliance with the Terms of UseTo better understand the needs of the website visitors and guide future improvements of the serviceTo conduct and monitor website security activitiesTo create anonymous usage statistics 4. Who will have access to your personal data? The personal data will be disclosed to: Authorised staff in the data controller’s institutions acting on data controller`s behalf and instructions. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? There are no personal data transfers to third countries or international organisations. 6. How long do we keep your personal data? Any personal data directly obtained from you will be retained as long as the service is live. Such duration serves the purpose of enabling scientific research and ensures legal compliance and facilitates internal and external audits if they arise. By contrast, the log files for the data categories related to anonymous usage statistics (raw web service logs) are processed only for 30 days and thereafter erased. 7. The joint Data Controllers provide these rights regarding your personal data You have the right to: Not be subject to decisions based solely on an automated processing of data (i.e. without human intervention) without you having your views taken into consideration.Request at reasonable intervals and without excessive delay or expense, information about the personal data processed about you. Under your request we will inform you in writing about, for example, the origin of the personal data or the preservation period.Request information to understand data processing activities when the results of these activities are applied to you.Object at any time to the processing of your personal data unless we can demonstrate that we have legitimate reasons to process your personal data.Request free of charge and without excessive delay rectification or erasure of your personal data if we have not been processing it respecting the data protection policies of the respective controllers. It must be clarified that rights under points 4 and 5 are only available whenever you need support whilst using our website. For other processing based on the grounds of important public interest you cannot exercise your rights to object, rectify or erase your personal data according to the Article 13(2)(a)(b) of IP 68 (equivalent to Article 17(3)(b)(d) and Article 21(6) of the GDPR). 8. Supervisory authority If you wish to complain against the processing of your personal data, you may do so by post at: EMBL Heidelberg, Data Protection Committee, Meyerhofstraße 1, 69117 Heidelberg, Germany, or Autoritat Catalana de Protecció de Dades (Catalan Data Protection Authority), C/Rosselló 214, Esc A, 1r 1a, Barcelona 08008, Spain. 9. CookiesWe use cookies and similar technologies that are strictly necessary for the correct functioning and security of the EGA website (for example, to enable core site features and to help protect the service). These cookies do not store information that directly identifies you.You can set your browser to block or delete cookies. Please note that if you disable strictly necessary cookies, parts of the website may not function properly.Published on February 6, 2019

  Documentation data-protection/privacy-notice/ega-website

• eMERGE Network Phase III Clinical Sequencing: eMERGEseq Panel

  The Electronic Medical Records and Genomics (eMERGE) Network is a National Institutes of Health (NIH)-organized and funded consortium of U.S. medical research institutions. The primary goal of the eMERGE Network is to develop, disseminate, and apply approaches to research that combine biorepositories with electronic medical record (EMR) systems for genomic discovery and genomic medicine implementation research. eMERGE was announced in September 2007 and began its third phase in September 2015. eMERGE III consists of nine study sites, two central sequencing and genotyping facilities, and a coordinating center. eMERGE Phase III aims to: 1) sequence and assess the phenotypic implication of rare variants in a custom designed eMERGEseq panel consisting of 109 genes (including 56 ACMG actionable finding list genes and the top 6 genes from each site relevant to their specific aims), as well as approximately 1400 SNPs; 2) assess the phenotypic implications of these variants by developing, validating and implementing new phenotype algorithms, 3) integrate genetic variants into EMRs to inform clinical care; and 4) create community resources. Included in this study are: ~24,000 eMERGE participants from 10 eMERGE III study sites. Corresponding demographics, body mass index measurements. Top PheWAS codes generated from a collated list of ICD codes from all study sites. Study sites and participants include: Cincinnati Children's Hospital Medical Center (CCHMC): Cincinnati Children's Hospital Medical Center (CCHMC) is a not-for-profit hospital and research center pioneering breakthrough treatments, providing outstanding family-centered patient care and training healthcare professionals for the future, and dedicated to improving health and welfare of children and to the shared purpose of discovery and practical application of new genomic information to the ordinary care of children. We bring a comprehensive electronic health record (EPIC), a deidentified i2b2 data warehouse of 680K patient records, a biobank with >261,000 consents that allow return of results to >84,000 patients and guardians who have provided DNA samples, and hundreds of faculty and senior staff who make genomics or informatics an active focus of their research. CCHMC will help the eMERGE III Steering Committee identify genes for the eMERGE III targeted sequencing panel, provide 3,000 DNA samples from CCHMC patients to be sequenced, review targeted gene panels from clinical care at CCHMC for somatic mosaicism and reinterpretation, and further develop and disseminate a software workflow suite for sequence analysis. We will also extend our work generating phenotype algorithms using heuristic and machine learning methods to many new childhood diseases. We will develop tools to evaluate adolescent return of results preferences, examine the ethical and legal obligations and potential to reanalyze results, and develop clinical decision support for phenotyping, test ordering, and returning sequencing results. Children's Hospital of Philadelphia (CHOP): The Center for Applied Genomics (CAG) is a specialized Center of Emphasis at the Children's Hospital of Philadelphia (CHOP), and one of the world's largest genetics research programs, with to state-of-the-art high-throughput sequencing and genotyping technology. Our primary goal is to translate basic research findings to medical innovations. We aim to develop new and better ways to diagnose and treat children affected by rare and complex medical disorders, including asthma, autism, epilepsy, pediatric cancer, learning disabilities, and a range of rare diseases. Ultimately, our objective is to generate new diagnostic tests and to guide physicians to the most appropriate therapies. Participants were recruited from the CAG biorepository (n>450,000), specifically from >100,000 CHOP pediatric patients and family members, which is enriched for rare-diseases (n>12,000). Center for Applied Genomics, The Children's Hospital of Philadelphia We gratefully thank all the children and their families who enrolled in this study, and all individuals who donated blood samples for research purposes. Genotyping for this project was performed at the Center for Applied Genomics and supported by an Institutional Development Award from The Children's Hospital of Philadelphia. Sequencing was supported by the National Institutes of Health through an award from the National Human Genome Research Institute's Electronic Medical Records and Genomics (eMERGE) program (U01HG008684). Columbia University: The goal of the Columbia eMERGE III project is to develop methods for integrating genomic data in EHRs and to study the impact of such genomic informatics interventions on the health of a diverse, underserved urban adult English- and Spanish-speaking patient population in Northern Manhattan served by Columbia University Medical Center/New York-Presbyterian Hospital system. The study group is 2500 patients recruited from diverse clinics and community outreach centers of self-reported White (~61%), Asian (~11%), African-American (~11%), American Indian/Alaska Native (<1%) racial and Hispanic (~33%) ethnic backgrounds. There are two subgroups in the study cohort - a retrospective group (N=1052) that includes patients from oncology and nephrology clinics, and a prospective one (N=1448) that includes healthy individuals as well as participants with diverse medical conditions. Confirmed pathogenic variants in 70 selected genes will be returned to participants and their healthcare providers through the EHR integration. Participants are able to choose the results they receive and will have the freedom to meet with a genetic counselor and a geneticist to review results. The impact of genetic testing on clinical care is determined by periodic monitoring of EHRs. Geisinger: Samples and phenotype data in this study were provided by the Geisinger MyCode® Community Health Initiative. Participants are recruited across the Geisinger System via online consents or in-person consents at a hospital or clinic visit. Enrollment is ongoing with over 100,000 individuals currently consented. Partners Healthcare (Harvard University): The Partners HealthCare Biobank is a large research program designed to help researchers understand how people's health is affected by their genes, lifestyle, and environment. This large research data and sample repository provides access to high-quality, consented blood samples to help foster research, advance our understanding of the causes of common diseases, and advance the practice of medicine. For the Partners research community (Massachusetts General Hospital and Brigham and Women's Hospital), the Biobank provides: Banked samples (plasma, serum, and DNA) collected from consented patients Blood samples that were discarded after clinical testing in the Crimson Cores maintained in the Brigham and Women's Hospital and Massachusetts General Hospital Pathology Departments Sample handling and preparation services Link to the biobank data to the Partners Research Patient Data Registry (RPDR) a research instance of our electronic clinical chart Data access through our research portal. To date, over 70,000 Partners patients have given their consent to enroll, give a blood sample, receive research results and agreed to be re-contacted for additional research studies. The Biobank has enabled Partners investigators to compete for nationally recognized grants in personalized medicine such as a clinical electronic Medical Records and Genomics network (eMERGE) site and the national All of US program. The Biobank currently supports over 120 Partners investigators and over 130 million dollars in NIH research. Kaiser Permanente Washington/ (KPWA) / University of Washington (UW): KPWA participants were enrolled in the eMERGE Network through the Northwest Institute of Genetic Medicine (NWIGM) biorepository, and provided the appropriate consent to receive clinically relevant genetic results (N=2,500.) NWIGM is based at the University of Washington and co-managed by the University of Washington and KPWA. The purpose of the NWIGM biorepository is to build infrastructure and resources to carry out a broad range of future genetic research. KPWA members enrolled in the biorepository are asked to provide informed consent to providing a DNA sample for storage in the NWIGM biorepository. The consent is purposefully broad to serve the dual purpose of reducing the burden on researchers who wish to use this biorepository and the IRB committees who will be responsible for reviewing these requests in the future. Participants were eligible if aged 50 - 65 years old at the time of their enrollment into the NWIGM repository, living, enrolled in KPWA's integrated group practice, and had completed an online Health Risk Appraisal. The selection algorithm was based on several data sources from the EHR at KPWA. 1) Demographics - participants with self-reported race as Asian ancestry were prioritized and selected to enrich for non-European ancestry. The KPWA eMERGE cohort includes N=1,245 members of Asian ancestry. 2) Participants were also selected for a history of colorectal cancer (N=1,255), in order to allow us to enrich germline pathogenic variants. Mayo Clinic: The Return of Actionable Variants Empirical (RAVE) Study was approved by the Mayo Clinic IRB. We recruited 2537 participants from Mayo Clinic biobanks in Rochester, MN, who had hypercholesterolemia or colon polyps, thereby enriching for Familial hypercholesterolemia (FH) and monogenic causes of colorectal cancer (CRC). Additional eligibility criteria were: 1) residents of Southeast MN who were alive and aged 18-70 years; 2) LDL-C level >155 or >120 mg/dl while on lipid-lowering therapy; 3) no known cause of secondary hyperlipidemia; and 4) no cognitive impairment or dementia that would compromise their ability to give written informed consent. Based on these criteria, we identified 5270 eligible patients and obtained informed consent from 3030 participants. Recruitment was conducted in waves and utilized mailed recruitment packets consisting of a study brochure, a written informed consent form, a baseline psychosocial questionnaire, and a return postage-paid envelope. DNA of 2537 participants was sent for CLIA-certified targeted sequencing of 109 genes including genes associated with FH and CRC. Targeted sequencing and genotyping was performed in a Central Laboratory Improvement Amendment (CLIA)-certified laboratory. Northwestern University: Samples and data used in this study were obtained from patients from Northwestern Medicine, an integrated healthcare system, formed through a partnership of Northwestern Memorial HealthCare and Northwestern University Feinberg School of Medicine. Participants include a retrospective cohort from the Northwestern Pharmacogenomics Study, funded through the eMERGE II project, NHGRI (3U01HG006388-02S1) and a prospective cohort from the Genetic Testing and Your Health Study, funded through the eMERGE III project, NHGRI (U01HG008673). Patients were eligible to participate if they were18 years or older and see a physician at Northwestern Medicine. Patients consented to genetic testing and to allow their results to be placed in their electronic medical record. Vanderbilt University Medical Center: Vanderbilt University Medical Center (VUMC) participants were enrolled in the eMERGE Network through the Vanderbilt Genome-Electronic Records (VGER) project. Patients were provided the appropriate consent to receive clinically relevant genetic results (N=2,700). Participants were eligible if aged 21 or over, had a healthcare provider at VUMC, and visited the provider at least 3 times in the past 3 years. Meharry Medical College: Inclusion of ethnic groups in genomic research is critical to identify possible reasons for health disparities. African-Americans are being enrolled in various outpatient clinics of Nashville General Hospital at Meharry, an inner city hospital primary serving a poorer patient group. A total of 500 African Americans with four cancer types demonstrating health disparities in this population - prostate, colon, breast, lung are identified and approached by clinical research coordinators. The purpose of the study is to determine if any genetic information can be identified from these patients who have or are at high risk of one of these disparate cancers. All participants provide written informed consent and HIPAA authorization to provide blood samples for broad research use and permission to access data in their hospital electronic medical record for research now and in the future. An extensive demographic profile is obtained and entered into a REDCap database. Blood samples are obtained for a panel of alleles from extracted DNA at Baylor. In addition, de-identified coded samples are processed and stored in a central biorepository for further DNA, RNA and proteomic analyses. The survey and phlebotomy are performed at the time of the initial contact and agreement to participate. Nearly all patients approached willingly agree to participate for potential benefit to themselves, family members, or humankind. Little concern is voiced of providing samples for genetic analysis. Study investigators will share results with the participants and providers if testing does not indicate high risk. Results indicating increased risk or actionable alleles for the patient and/or family will be returned by a genetic counselor. Monitoring of the patients' health in this cohort will continue to be followed in the EMR to identify any future associations that might explain health disparities in African Americans. Proposals will be reviewed from investigators to study the genetic or proteomic samples as well as the clinical and demographic information in the repository. Please note that this version of the dataset has a handful of mismatches between genotyped and provided sex. Data with the following IDs should be removed prior to analysis: 420252874213744142412243424569384245694642672223

  Study phs001616

• How to upload Crypt4GH files

  Uploading files Users who hold an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files, please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention, such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. To manage the available resources, we enforce a limit of 10TB per submission account at any one time. If you exceed this limit, a “permission denied” message will be displayed. This will prevent you from uploading more files, but connecting to your inbox.For submissions larger than 10TB, please perform uploads in 10TB batches: register all the metadata and then finalise the submission. Upload the next batch of files and repeat the same metadata registration and finalisation process until you have completed the file upload. Further information can be found in the SP documentation. INBOX FTP The INBOX is only compatible with files encrypted using the Crypt4gh tool Before uploading If you are not a registered EGA user, you will first need an EGA user account. Please note that it may take a few days for your account to be activated, as it needs to be vouched for by the EGA Helpdesk. Once your account is validated, you will be able to request a submitter role. [Optional] Meanwhile, you can create and add your public key to your EGA account profile. This option is not available for old submission accounts (e.g., ega-box-NNN). As soon as you have been granted a submitter role, you will be able to connect with your username and password to the EGA inbox using the SFTP protocol. If you have also registered a public key in your profile, you can also connect using this key. To upload files to your account, you can use the graphical user interface (GUI) or the command line. Graphical User Interface (GUI)We recommend using FileZilla, a free, open-source FTP client. However, you can use any other GUI that allows connecting over the SFTP protocol. For FileZilla as your GUI, follow these steps to upload files: Create a new connection in Site Manager (File > Site Manager) and select the following options (Figure 1): Protocol: SFTP - SSH File Transfer ProtocolHost: __EGA_INBOX_DOMAIN__Logon Type: Key fileUser: your EGA usernameKey file: Path/to/your/private_keyFigure 1: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers.Click Connect, and you will log in remotely to your home directory. You can think of this folder as a storage "in the EGA cloud" in which you will add your files for the EGA. The uploading area has three folders:To-encrypt: Files uploaded in this folder will be encrypted automatically on the fly.Encrypted: Files uploaded in this folder must already be encrypted with Crypt4gh. Upload your files here if your connection is unstable or you have problems completing the upload into-encrypt.Etc: This folder contains two files that allow the server to show you your username and group instead of some internal numbers. Please do not upload files here; otherwise, you will obtain a permission denied error. Find the files you want to upload by browsing your local storage (left side of your screen in FileZilla). Select all the files you want to upload, then right-click on them and select Upload (Figure 2). Figure 2: Step-by-step process of manually uploading files to __EGA_INBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can transfer data from their local storage to the "EGA cloud" by following the depicted steps Please note that regardless of which folder you upload your files in, both folders (to-encrypt, encrypted) will point to the same path (/) (Figure 3). Therefore, you will see your files in both folders. Figure 3: Both folders, to-encrypt and encrypted, point to the same path (/)" If your connection is unstable, please encrypt your files first using Crypt4gh. Then upload them to the ‘encrypted’ folder. The example above shows how to connect to __EGA_INBOX_DOMAIN__ using the private key. However, if you prefer to log in using your credentials, you can do so. Please go to the Frequently Asked Questions (FAQs)  for more information. SFTP command line To upload files securely to your private area of the EGA, you can use SFTP(Secure File Transfer Protocol) with your favorite FTP client. Here's what you need to know to get started: Connect to the target host __EGA_INBOX_DOMAIN__. This is the new hostname for the EGA SFTP service. Log in with your EGA username and key files (or password). Upload files to your private EGA inbox to ensure that only you can access the files. By following these steps, you can securely upload your files to the EGA for safe storage and sharing. Using the SFTP command line client in Linux/Unix Open a terminal and type sftp username@hostnameEnter your EGA passwordTo see a list of available SFTP commands, type helpsftp> put – Upload filesftp> get – Download filesftp> cd path – Change remote directory to ‘path’sftp> pwd – Display remote working directorysftp> lcd path – Change the local directory to ‘path’sftp> lpwd – Display local working directorysftp> ls – Display the contents of the remote working directorysftp> lls – Display the contents of the local working directoryType the "put" command to upload files. For example: put *.bamUse the bye command to close the connection (SFTP session). After uploading- Once you have uploaded files to the inbox, please bear in mind that the checksum needs to be calculated, which can take up to two days. You will only be able to link your files to a run/analysis once the encrypted checksum has been calculated.- When linking your files to the 'Run' or 'Analysis', ensure that the file name matches the file path '/name' in the INBOX folder.- Please delete the files from your SFTP INBOX after all the runs/analyses have been registered and files are ingested (SP > Files > Files ingested). This will clear your inbox space an allow you to upload more files. This will also prevent the files from reappearing in your Submitter Portal inbox. Frequently Asked Questions Specific to the inbox What username should I use to log in to my inbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username.  If you have forgotten your registered username, please contact our Helpdesk team for assistance. How are checksums calculated in your inbox? If you encrypt the file beforehand and upload it to the "encrypted" folder, the unencrypted checksum will not be calculated until the file is ingested (i.e., until it is used in a run/analysis). If the file is uploaded to the "to-encrypt" folder, then both checksums are calculated.Please bear in mind that after files have been uploaded to the inbox, the checksum must be calculated, which can take from a few hours to two days.  Specific to using keys to authenticate Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

  Documentation submission/data/uploading-files/inbox

• Data Use Ontology (DUO)

  Data Use Ontology Data Use Ontology at EGA The EGA is committed to its involvement in the work of GA4GH. In an effort to enhance data discoverability and streamline data access, EGA have implemented the use of the Data Use Ontology (DUO), based on consent codes as described in Dyke et al. 2017. The Data Use Ontology codes will be displayed on the live dataset page of your submission to advise any would be requestor on how the data can be used and also to enhance data discoverability as users will be able to search on these codes to find applicable datasets. DUO can be browsed online via the Ontology Lookup Service Learn more reading the Data Use Ontology publication and the GA4GH Machine-Readable Consent Guidance! Check our DAC Portal Take The Tour and learn how to add DUO codes to your policy! Term Shorthand Label Description DUO:0000004 NRES no restriction This data use permission indicates there is no restriction on use. DUO:0000042 GRU general research use This data use permission indicates that use is allowed for general research use for any research purpose. DUO:0000006 HMB health or medical or biomedical research This data use permission indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. DUO:0000007 DS disease specific research This data use permission indicates that use is allowed provided it is related to the specified disease. DUO:0000011 POA population origins or ancestry research only This data use permission indicates that use of the data is limited to the study of population origins or ancestry. DUO:0000012 RS research specific restrictions This data use modifier indicates that use is limited to studies of a certain research type. DUO:0000015 NMDS no general methods research This data use modifier indicates that use does not allow methods development research (e.g., development of software or algorithms). DUO:0000016 GSO genetic studies only This data use modifier indicates that use is limited to genetic studies only (i.e., studies that include genotype research alone or both genotype and phenotype research, but not phenotype research exclusively) DUO:0000018 NPUNCU not for profit, non commercial use only This data use modifier indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use. DUO:0000019 PUB publication required This data use modifier indicates that requestor agrees to make results of studies using the data available to the larger scientific community. DUO:0000020 COL collaboration required This data use modifier indicates that the requestor must agree to collaboration with the primary study investigator(s). DUO:0000021 IRB ethics approval required This data use modifier indicates that the requestor must provide documentation of local IRB/ERB approval. DUO:0000022 GS geographical restriction This data use modifier indicates that use is limited to within a specific geographic region. DUO:0000024 MOR publication moratorium This data use modifier indicates that requestor agrees not to publish results of studies until a specific date. DUO:0000025 TS time limit on use This data use modifier indicates that use is approved for a specific number of months. DUO:0000026 US user specific restriction This data use modifier indicates that use is limited to use by approved users. DUO:0000027 PS project specific restriction This data use modifier indicates that use is limited to use within an approved project. DUO:0000028 IS institution specific restriction This data use modifier indicates that use is limited to use within an approved institution. DUO:0000029 RTN return to database or resource This data use modifier indicates that the requestor must return derived/enriched data to the database/resource. DUO:0000043 CC clinical care use This data use modifier indicates that use is allowed for clinical use and care. DUO:0000044 NPOA population origins or ancestry research prohibited This data use modifier indicates use for purposes of population, origin, or ancestry research is prohibited. DUO:0000045 NPU not for profit organisation use only This data use modifier indicates that use of the data is limited to not-for-profit organisations. DUO:0000046 NCU non-commercial use only This data use modifier indicates that use of the data is limited to not-for-profit use. Point to Notice: For the consent code DUO:0000007 where data is restricted to use on a specific disease, please accompany it with an appropriate ontology from MONDO e.g., If the data is restricted to the use of research into juvenile idiopathic arthritis the code should be displayed as DUO:0000007; MONDO:0011429.

  Documentation access/data-access-committee/data-use-ontology

• Implementation of the GDPR

  Data Protection 1 About the EGA The European Genome-phenome Archive (EGA) was formally 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. In late 2012, with the signing of a memorandum of understanding (and subsequent formal agreement in 2016) between EMBL-EBI and the Centre for Genomic Regulation (CRG), the EGA formally became a joint project of the two institutes. The two institutes work together to support the EGA services, including supporting submissions, web site, strategic leadership, and data infrastructure developments. 2 EMBL-EBI & GDPR The EGA is co-managed by EMBL-EBI and CRG. EMBL-EBI is an international organisation established by treaty and has certain privileges and immunities (e.g. exemptions from the application of national law) and also may self-regulate its activities (e.g. establish its own institutional legal framework) within the framework of its founding act of 1973. The General Data Protection Regulation (GDPR) is a European Union (EU) regulation that legislates how organisations can share and process personal data of EU citizens. EMBL places great value in maintaining collaboration with researchers who are subject to GDPR. For that reason, it is of utmost importance for EMBL to handle data received from those collaborators in a secure and responsible manner. Mindful of its public mandate and the sensitivity of the data it handles, EMBL has always ensured a high level of data protection in its activities. Since the introduction of GDPR in May 2018, EMBL has established its internal policy on General Data Protection (IP68), exercising its right to self-regulate its operations,., IP 68 establishes a robust personal data protection framework that provides for data protection principles, enforceable data subject rights and oversight and redress mechanisms offering a level of protection comparable with GDPR. 3 CRG & GDPR The Centre for Genomic Regulation (CRG) is an international biomedical research institute of excellence, created in July 2000 and mainly participated by the Catalan Government. It is a non-profit foundation and its mission is to discover and advance knowledge for the benefit of society, public health and economic prosperity. The CRG is a CERCA center. CERCA is the collective organisation for all research centres of excellence in Catalonia. CERCA ensures these centres develop successfully by promoting synergies and strategic cooperation improving their visibility and the impact of their research and promoting the dialogue amongst both public and private stakeholders. As a legal entity based in Spain and operating within the EU, the CRG ensures the compliance with the GDPR and the legal regulations on personal data protection applicable at the national level, as well as any other legislation that may replace, modify or supplement the above-mentioned in terms of personal data protection. 4 EGA & GDPR EGA GDPR Schema 4.1 Genetic and phenotypic data Within GDPR, there are two main actors: data controllers and data processors. Data controllers are persons or entities which determine the purposes and means that the personal data may be processed, e.g. companies, researchers, or universities. For EGA, the data controller is ultimately the data producer and the submitter(s) who submit the data to EGA. The data controller also creates a Data Access Committee (DAC) who will decide on data access permissions at EGA. Data processors are the persons or entities which process the data on behalf of a data controller. With regard to GDPR, EGA is a data processor as it processes data as instructed by the data controller. GDPR applies to any organisation which accesses personal data from an individual within the EU. Under GDPR, personal data is defined as any data that is identifiable, including names and email addresses as well as health-related and genetic data. EGA does not accept personally identifiable data except genetic and phenotypic data, so all other data submitted to EGA, such as names and addresses, must be pseudonymised. GDPR requires that data controllers implement data protection principles, such as data minimisation, to minimise the risk of data leakage, and protect the rights of the data subjects. As a data processor, EGA has a set of security policies that are followed to minimise the risk of unauthorised data access or data loss. In its role as a data processor, EGA requires all submitters to sign a Data Processing Agreement (DPA) when the submission account is first created. This agreement is only required to be signed once per submitter, and will remain valid for future submissions to EGA. 4.2 Other personal data The EGA also collects personal data as part of our interactions with submitters, data access committees, and researchers accessing data distributed by EGA. The below privacy notices explain what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. Privacy Notices for EGA Title Version Last Updated EGA Data Access Committee Account Privacy Notice for EGA Data Access Committee Account 1.0 February 6, 2019 EGA User Account Privacy Notice for EGA User Account 1.0 February 6, 2019 EGA Helpdesk Service Privacy Notice for EGA Helpdesk Service 1.0 February 6, 2019 EGA Website Service Privacy Notice for EGA Website Service 1.0 February 6, 2019 Documentation Title Version Description EGA Security Overview Security Document 1.1 The EGA Security Document provides an overview of EGA’s practices in ensuring the security of data stored at EGA. EGA Data Processing Agreement Data Processing Agreement 1.5 The Data Processing Agreement must be completed and returned as part of the submission process. Please note that this document is non-negotiable. Authorised Submitters Authorised Submitters Formulary 1.0 The Authorised Submitters Form must be completed and returned as part of the submission process. Please list all those that should have access to the submission account in order to submit to the EGA should be detailed here. Dispute Resolution Any controversy or claim arising out of, or relating to, the DPA (including the enforceability or breach thereof, any question regarding its existence, validity or termination) or relating to the EGA Service shall be resolved using the internal dispute resolution mechanisms of EGA including those related to Data Protection. The EGA’s internal dispute resolution mechanism has the following procedure: EGA OPERATIONAL PHASE: Meetings between EGA staff and the Data Controller.LEGAL MANAGEMENT PHASE: Meetings between legal teams of EMBL, CRG and the Data Controller. DIRECTION MANAGEMENT PHASE: Negotiation between the legal representatives of EMBL, the CRG and the Data Controller. If the internal dispute resolution mechanism doesn’t resolve the controversy or claim the next phase is:ARBITRATION PHASE: Resolution by arbitration under the WIPO Expedited Arbitration Rules (“Rules”).

  Documentation about/privacy-notice

• Research Program on Genes, Environment and Health (RPGEH)

  The Kaiser Permanente Research Program on Genes, Environment, and Health (RPGEH) is a resource developed to facilitate research on genetic and environmental factors on common diseases and healthy aging. The RPGEH resource links biospecimens, health surveys, and comprehensive electronic medical records on broadly consented adult members of Kaiser Permanente Medical Care Plan, Northern California Region (KPNC). KPNC is an integrated health care delivery system with a membership of approximately 3.3 million people in northern California. The membership of KPNC is representative of the general population in the 14 county area in which facilities are located, although extremes of income are underrepresented. At the end of 2013, the RPGEH resource included: (1) demographic and behavioral surveys from over 430,000 participants; (2) biospecimens (DNA, serum, plasma, and/or saliva) from over 204,000 participants, including over 13,000 pregnant women; (3) genome-wide genotype data (70 billion SNP genotypes) on over 100,000 participants, including the Genetic Epidemiology Research on Adult Health and Aging (GERA) cohort; and (4) the longitudinal electronic medical records of the participants. The RPGEH was developed beginning in 2005 at the Division of Research of Kaiser Permanente Northern California by Catherine Schaefer (Director), Neil Risch (Co-Director), Lisa Croen, Eric Jorgenson, Lawrence Kushi, Charles Quesenberry, Sarah Rowell, Carol Somkin, Stephen Van den Eeden, Larry Walter, and Rachel Whitmer. Funding of the RPGEH was provided to C. Schaefer (PI) and N. Risch (co-PI) by the Wayne and Gladys Valley Foundation, The Ellison Medical Foundation, the Robert Wood Johnson Foundation, Kaiser Permanente Northern California, and the Kaiser Permanente National and Regional Community Benefit Programs. The GERA cohort was funded by a grant from NIH to RPGEH and UCSF (RC2 AG036607; C. Schaefer and N. Risch, PIs). At the time of the award of the RC2 project in late 2009, the RPGEH had established a cohort of about 140,000 individuals who had answered a detailed survey, provided saliva samples for extraction of DNA, and given broad consent for the use of their data in studies of health and disease. Survey and Cohort Recruitment. Initially, the RPGEH developed electronic disease registries to enable identification of phenotypes, using algorithms applied to EMR data. In 2007, the RPGEH mailed a four page survey to 1.9 million adult (&#8805; 18 years old) members of KPNC who had been members for two years or more, to obtain data on demographic and behavioral factors complementary to the clinical data in the EMR. The survey materials included a cover letter introducing the RPGEH, a two page list of Frequently Asked Questions, and the survey, which included questions on demographic factors such as education, race-ethnicity, income and marital status, dietary factors, physical activity, smoking, and alcohol consumption, as well as reproductive history and reproductive health. Members whose electronic medical records indicated a preference for written communications in Chinese or Spanish received survey materials both in English and a Chinese or Spanish translation. Approximately 400,000 completed surveys were returned. Saliva Sample Collection. Beginning in July 2008, respondents to the survey were asked to sign and return a consent form and authorization for use and disclosure of protected health information. The consent form authorized broad use of biospecimens, survey data, and data from participants&#39; electronic health records for use in studies of genetic and environmental influences on health and disease. Respondents who returned completed consent forms were mailed (Oragene) saliva collection kits; more than 132,000 saliva samples were collected in two years. Completed saliva kits were scanned and archived in a temporary biorepository at the KPNC Division of Research. In late 2009, the RPGEH began collection of saliva samples from the California Men&#39;s Health Study (CMHS), a cohort that had been previously assembled in 2002-2003 and had been excluded from the RPGEH survey mailing with the intent of later adding CMHS participants to the assembled RPGEH cohort. The CMHS was developed to facilitate research on prostate cancer and other conditions in older men; the study protocol is described in Enger, et al., 2006. It enrolled and surveyed more than 40,000 men in KPNC, ages 45-69 years, who were members of KPNC during 2002-2003. CMHS men completed two mailed surveys with demographic and behavioral data similar to that of the RPGEH. The data on analogous variables were reconciled and integrated with the data derived from the RPGEH cohort for use in the RPGEH resource. By 2011, RPGEH collected approximately 15,400 saliva samples from men participating in the CMHS. RPGEH Access and Collaborations Website and Procedures. The RPGEH maintains a web portal for inquiries and applications for collaboration and access to data. The url is: https://rpgehportal.kaiser.org/. RPGEH has an application process and an Access Review Committee that reviews applications for collaboration and use. For more information, please contact RPGEH through the website.

  Study phs000788

• Sleep Heart Health Study (SHHS-BioLINCC)

  Data Access NOTE: Please refer to the &#8220;Authorized Access&#8221; section below for information about how access to the data from this accession differs from many other dbGaP accessions.Related StudiesParent cohort phenotype data can be accessed through ARIC-BioLINCC, Framingham-BioLINCC, and CHS-BioLINCC. Objectives To determine the cardiovascular and other consequences of sleep-disordered breathing and to test whether sleep-disordered breathing is associated with an increased risk of coronary heart disease, stroke, all-cause mortality and hypertension by examining subjects from well-characterized and established epidemiologic cohorts. Background Obstructive sleep apnea syndrome (OSA) is a potentially debilitating condition characterized by repetitive episodes of apnea while asleep, nocturnal oxygen desaturation, excessive daytime sleepiness, and loud disruptive snoring. Epidemiologic data from middle-aged adults indicate that OSA is common, with prevalence rates of 4% in men and 2% in women. Prior studies implicated OSA as a risk factor for the development of hypertension, ischemic heart disease, congestive heart failure, stroke and consequently premature death. Questions arose as to whether an increased propensity for cardiovascular and cerebrovascular diseases was limited to only those with frank OSA or whether more subtle forms of sleep-disordered breathing (SDB) would also confer elevated risk. Further evidence was also needed to clarify whether, SDB, including OSA, is an independent risk factor for the development of cardiovascular or cerebrovascular disease. Known cardiovascular and cerebrovascular disease risk factors such as obesity and smoking are commonly present in those with SDB; therefore, apparent associations between SDB and cardiovascular and cerebrovascular diseases may have resulted from the effects of these concomitant risk factors. Moreover, there was no understanding as to whether such factors as race, age, gender, and prevalent cardiovascular or cerebrovascular disease might interact with SDB to alter future cardiovascular and cerebrovascular disease risk. Mechanisms underlying any propensity to develop cardiovascular or cerebrovascular disease with SDB had not been firmly established (Quan, et al., 1997, PMID: 9493915). Participants Participants in SHHS were recruited from nine existing NHLBI epidemiological studies in which data on cardiovascular risk factors had been collected previously. The &#8220;parent&#8221; cohorts included: Two sites of the Atherosclerosis Risk in Communities Study (ARIC) Three sites of the Cardiovascular Health Study (CHS) The Framingham Offspring Cohort The Strong Heart Study (SHS) sites in South Dakota, Oklahoma, and Arizona The New York Hypertension Cohorts The Tucson Epidemiologic Study of Airways Obstructive Diseases and the Health and Environment Study From these parent cohorts, a sample of participants who met the inclusion criteria (age 40 years or older; no history of treatment of sleep apnea; no tracheostomy; no current home oxygen therapy) was invited to participate in the baseline examination of the SHHS, which included an initial polysomnogram (SHHS-1). Several cohorts over-sampled snorers in order to increase the study-wide prevalence of sleep-disordered breathing. In all, 6441 individuals were enrolled between November 1, 1995 and January 31, 1998. During exam cycle 3 (January 2001-June 2003), a second polysomnogram (SHHS-2) was obtained in 3295 of the participants. Due to sovereignty issues, Strong Heart Study participants are not included in the shared SHHS data. Data from a total of 5839 participants (1920 ARIC, 1249 CHS, 997 Framingham Offspring and OMNI 1, and 1673 from other studies), consenting to share data are available. Design The Sleep Heart Health Study added in-home polysomnography to the data collected in each of the parent studies at a baseline SHHS exam and a follow-up approximately 4 years later. Using the Compumedics PS polysomnograph, sleep studies were obtained in an unattended setting, usually in the homes of the participants, by trained and certified technicians. The recording montage consisted of: C3/A2 and C4/A1 EEGs, sampled at 125 Hz right and left electrooculograms (EOGs), sampled at 50 Hz a bipolar submental electromyogram (EMG), sampled at 125 Hz thoracic and abdominal excursions (THOR and ABDO), recorded by inductive plethysmography bands and sampled at 10 Hz "airflow" detected by a nasal-oral thermocouple (Protec, Woodinville, WA), sampled at 10 Hz finger-tip pulse oximetry (Nonin, Minneapolis, MN) sampled at 1 Hz ECG from a bipolar lead, sampled at 125 Hz for most SHHS-1 studies and 250 Hz for SHHS-2 studies Heart rate (PR) derived from the ECG and sampled at 1 Hz body position (using a mercury gauge sensor) ambient light (on/off, by a light sensor secured to the recording garment)This montage provides data on the occurrence of sleep-disordered breathing, sleep stages, heart rate, oximetry and on arousals. Each participant in the parent studies was also asked to complete the Sleep Habits Questionnaire which covers usual sleep pattern, snoring, and sleepiness.

  Study phs003637

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• Pharmacogenomics Research Network Antidepressant Medication Pharmacogenomic Study (PGRN-AMPS)

  This pharmacogenomic study focused on the response of patients with MDD to an 8-week course of treatment with citalopram or escitalopram. Briefly, clinical assessments and research assessments were performed at each study visit as summarized in Table 1. Many patients continued on antidepressant medication after the 8 week study. Table 1: Study timeline and patient contacts. Week Consent/Med Hx Write Rx SI Qx SCID HRS-D17 QIDSC16 CGI-I 0 SC RC RC SC SC SC 4 RC RC SC SC RC 8 RC RC SC SC RC HRS-D17=Hamilton Rating Scale for Depression, QIDS-C16=Quick Inventory of Depressive Symptomatology, CGI-I=Clinical Global Impression-Improvement, SCID=Structured Clinical Interview for DSM-IV, SC=Study Coordinator, RC=Research Clinician. Enrollment and baseline assessment. Upon initial intake, the Study Coordinator (SC) obtained informed consent as well as clinical and demographic information, including history of bone marrow or liver transplant or blood transfusion within the previous 6 weeks, and prior history of treatment during the current major depressive episode. The SC completed the Structured Clinical Interview for DSM-IV (SCID), the HRS-D17 (17-item Hamilton Rating Scale for Depression) and the QIDS-C16 (Quick Inventory of Depressive Symptomatology) and reviewed the inclusion/exclusion criteria. After review with the Research Clinician (RC) and when appropriate, after a negative pregnancy test, the SC invited the subject to participate in the study if entry criteria were met. If the subject agreed, he/she received treatment according to the study protocol. Treatment schedule. Participants selected for inclusion in the study were seen at weeks 0, 4, and 8. The appropriate treatment antidepressant (citalopram or escitalopram) was determined following discussion between the patient and RC concerning medical, financial, and insurance considerations. The study medication citalopram was given in tablet or liquid form, depending on the patient&#39;s need. A fixed-flexible dose schedule was employed with the possibility of a dose escalation. In particular, the initial dose of citalopram was 20 mg and escitalopram was 10 mg. This dose was increased to 40 mg and 20 mg, respectively, after 4 weeks if the subject had a score of &#62;/= 6 on the QIDS-C16 and the RC concluded that the subject could tolerate the increase. If necessary, dose was reduced at the discretion of the RC. The importance of medication compliance was discussed with the subject, and subjects were asked to bring in the medication at each visit for the purpose of counting remaining pills to assess compliance. Participants may have had an abbreviated course of therapy if they were clearly intolerant of the drug or failed to respond to a 40 mg dose of citalopram or a 20 mg dose of escitalopram. They then received standard treatment from a primary physician or psychiatrist with different medications and/or therapeutic modalities (e.g. psychotherapy). Special attention was given to subjects with suicidal ideation. Those subjects were offered additional appointments as needed to ensure their safety. Participants were also contacted by telephone at week 1 and week 2 by the Clinical Nurse Specialist (CNS) or other study personnel to ensure medication compliance and patient safety. The CNS was supervised by the study psychiatrist and principal investigator and deferred to the physician&#39;s judgment as needed. The SC was trained to notify the RC at the time of the clinical visits or the phone interviews if the subject endorsed any suicidal ideation or plans. For those subjects who were unable to attend the follow-up visits as scheduled, the patient was contacted by phone to complete the HRS-D17/QIDS-C16. The participant was also asked to return to the clinic to complete a final blood draw for the study. Adjunctive and concurrent medications. Adjunctive treatments were those used to manage transient associated symptoms (e.g., insomnia) or transient or longer-term medication side effects (e.g., sexual dysfunction). Adjunctive treatments that were not used to treat depression were allowed during the study. However, drugs in the exclusion criteria for this study were not used as adjunctive therapies. Subjects were allowed to participate in the study while receiving concurrent medications for general medical conditions as long as there was no contraindication to use while taking citalopram or escitalopram. Drug efficacy phenotype evaluation. The change in QIDS-C16 score and change in HRS-D17 score were used as the major research outcome measures to assess drug response. At each clinical research visit, the RC also completed the Clinician Global Impression of Improvement (CGI-I) scale. For the primary genome-wide association analyses, dichotomous outcome variables, remission and response, were defined based on the QIDS-C16 last visit score. Remission was defined as a QIDS-C16 score of 5 or less, while response was defined as at least a 50% reduction in the QIDS-C16 score from baseline. Specimen collection. Specimen collections were obtained by the General Clinical Research Center (GCRC) at St. Mary&#39;s Hospital (SMH). Subjects had blood drawn on an outpatient basis at GCRC-SMH on three separate occasions - baseline (0), week 4 and week 8 visits. Prior to sample collection, date and time of last dose of study medication was gathered at the 4 and 8 week visits. For those patients who were unable to complete the regularly scheduled visits, a dismissal blood draw was requested. GCRC then shipped samples to Mayo Clinic&#39;s Biospecimens Accessioning and Processing Lab. Genotyping and biomarker assays. DNA from 529 patients was genotyped by the RIKEN Center for Genomic Medicine (Yokohama, Japan) using Illumina Human610-Quad BeadChips (Illumina, San Diego, CA). The study also included the determination of plasma drug levels at weeks 4 and 8, and metabolite levels at baseline and weeks 4 and 8 for a subset of subjects. The primary genome-wide association study based on these data, which includes a summary of the protocol, subject description, selection of subjects for genetic analyses, and definitions of clinical outcomes, was published in the Pharmacogenomics Journal (Ji et al., 2012).

  Study phs000670