1654 results for "fc coins xbox one Navštivte Buyfc26coins.com Mezinárodně uznávaná společnost v herním průmyslu..L14h"

in 19.64 milliseconds.

• Antihypertensive and Lipid-Lowering Treatment to Prevent Heart Attack Trial (ALLHAT-BioLINCC)

  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. ObjectivesHypertension Study: To determine whether treatment with a calcium channel blocker or an angiotensin-converting enzyme inhibitor lowers the incidence of coronary heart disease (CHD) or other cardiovascular disease (CVD) events vs treatment with a diuretic.Lipid Study: To determine whether pravastatin compared with usual care reduces all-cause mortality in older, moderately hypercholesterolemic, hypertensive participants with at least an additional CHD risk factor. BackgroundHypertension Study: Antihypertensive therapy is well established to reduce hypertension-related morbidity and mortality, but the optimal first-step therapy is unknown.Lipid Study: Studies have demonstrated that statins administered to individuals with risk factors for coronary heart disease (CHD) reduce CHD events. However, many of these studies were too small to assess all-cause mortality or outcomes in important subgroups.ParticipantsHypertension Study: A total of 33,357 participants. Lipid Study: A total of 10,355 participants. Baseline mean total cholesterol was 224 mg/dL; LDL-C, 146 mg/dL; high-density lipoprotein cholesterol, 48 mg/dL; and triglycerides, 152 mg/dL. Mean age was 66 years; 49% were women, 38% black and 23% Hispanic, 14% had a history of CHD, and 35% had type 2 diabetes. DesignHypertension Study: A randomized, double-blind, active-controlled clinical trial conducted from February 1994 through March 2002. Participants were randomly assigned to receive chlorthalidone, 12.5 to 25 mg/d (n = 15,255); amlodipine, 2.5 to 10 mg/d (n = 9048); or lisinopril, 10 to 40 mg/d (n = 9054) for planned follow-up of approximately 4 to 8 years. The primary outcome was combined fatal CHD or nonfatal myocardial infarction, analyzed by intent-to-treat. Secondary outcomes were all-cause mortality, stroke, combined CHD (primary outcome, coronary revascularization, or angina with hospitalization), and combined CVD (combined CHD, stroke, treated angina without hospitalization, heart failure (HF), and peripheral arterial disease).Lipid Study: Multicenter (513 primarily community-based North American clinical centers), randomized, non-blinded trial conducted from 1994 through March 2002 in a subset of participants from the Antihypertensive and Lipid-Lowering Treatment to Prevent Heart Attack Trial (ALLHAT). The interventions in the trial were pravastatin, 40 mg/d, vs usual care. The primary outcome was all-cause mortality, with follow-up for up to 8 years. Secondary outcomes included non-fatal myocardial infarction or fatal CHD (CHD events) combined, cause-specific mortality, and cancer.ConclusionsHypertension Study: Thiazide-type diuretics are superior in preventing one or more major forms of CVD and are less expensive. They should be preferred for first-step antihypertensive therapy.Lipid Study: Pravastatin did not reduce either all-cause mortality or CHD significantly when compared with usual care in older participants with well-controlled hypertension and moderately elevated LDL-C. The results may be due to the modest differential in total cholesterol (9.6%) and LDL-C (16.7%) between pravastatin and usual care compared with prior statin trials supporting cardiovascular disease prevention.

  Study phs004021

• A_study_of_the_genetic_basis_of_evation_by_Acute_Myeloid_Leukaemia_of_Graft_vs_Leukaemia_effects_after_allogeneic_bone_marrow_transplantation

  Acute myeloid leukaemia (AML) is an aggressive and molecularly diverse disease with a poor overall survival of 20-25%. With an annual incidence of 2.9 per 100,000, AML is currently the commonest myeloid malignancy in Europe, yet the two main therapeutic options for this disease, anthracyclines and purine analogues, have remained unchanged for over 20 years. Currently patients are stratified at diagnosis according to a series of clinicopathological parameters (e.g. age, white cell count and presence/absence of previous clonal haematological disease) and molecular markers (e.g. chromosomal translocations/deletions, aneuploidy and mutations in genes such as FLT3 and NPM1). Patients with adverse prognostic features, whose prognosis is particularly poor (e.g. <15% long-term survival) are offered treatment with allogeneic bone marrow transplantation (allo-BMT) if a sibling or unrelated donor is available. This can significantly improve survival (e.g. up to 40% long-term survival in some contexts), albeit at the expense of significant toxicity and transplant-related mortality (TRM). Allo-BMT is thought to work in part by allowing the delivery of large doses of chemotherapy followed by haemopoietic "rescue" with donor haemopoietic stem cells (haemopoietic failure would otherwise ensue). However, potentially the most potent effect of allo-BMT is the cytotoxic effect of donor lymphocytes against AML blasts, a phenomenon known as graft-vs-leukaemia (GVL) effect. Increasingly, transplants using reduced chemotherapy intensity (mini-allografts) are being used that partially circumvent the toxicity from chemotherapy and rely on GVL to effect cure. Nevertheless, AML relapse after allo-BMT still occurs at a significant rate of up to 80% depending on the type of transplant. There is accumulating evidence that genetic events in residual leukaemic cells enable them to evade immunodetection and therefore survive the GVL effect and expand to cause relapse. The most striking example of this is the loss of HLA antigens after transplants in which donor and recipient are not fully HLA-matched. In these cases, the leukaemia "deletes" the genomic region containing the disparate HLA antigen which was preferentially targeted as "foreign" by the GVL effect. However, the genetic basis of immune evasion in the majority of transplants, which are fully HLA matched, is not known. One possibility is that loss of genes coding for antigens outside the HLA locus but which are also targets of GVL may operate, alternatively genetic events that affect processes downstream of immunological cytotoxicity may be responsible.The identification of genetic events that mediate immune evasion would not only facilitate the understanding of this process but can help plan therapeutic interventions that improve the outcomes of allogeneic transplantation for AML and other disorders. We intend to study this by conducting exome sequencing on 6 cases of AMLs from patients that attend my clinic at Addenbrooke's hospital and have relapsed after allogeneic transplantation. Samples from AML diagnosis, remission/normal and AML relapse (total n=18) will be studied to identify somatic mutations in the primary AML and those acquired by the relapsed clone. The 18 samples will also be studied by array CGH to detect regions of genomic amplification or deletion.

  Study EGAS00001000145

• A Genome-Wide Association Study in Breast Cancer Patients from the Prospectively Randomized SUCCESS Trial

  The SUCCESS-A Study (http://www.success-studie.de) is a randomized Phase III study of response to treatment of early primary breast cancer with adjuvant therapy after surgical resection. The primary outcome is disease-free survival and secondary outcomes are overall survival and toxicity. The study design includes comparison of two pairs of treatment regimes performed in sequence. The first randomization contrasts treatment with and without Gemcitabine (3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC)-chemotherapy, followed by 3 cycles of Docetaxel(D)-chemotherapy versus 3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC), followed by 3 cycles of Gemcitabine-Docetaxel(DG)-chemotherapy). The second randomization contrasts treatment with Zoledronate for two versus five years. Patients were recruited from 2005 to 2007 and a total of 3754 patients were included from 250 study sites across Germany. Genome-wide SNP microarray data and phenotype outcomes for the first phase of the study (treatment with and without Gemcitabine) are included in the GARNET (Genomics and Randomized Trials Network) pharmacogenomic study in this dbGaP submission. (The Zoledronate treatments are still underway). SUCCESS-A is a an open-label, multicenter, 2x2 factorial design, randomized controlled, Phase III study comparing the disease free survival after randomization in patients treated with 3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC)-chemotherapy, followed by 3 cycles of Docetaxel(D)-chemotherapy versus 3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC), followed by 3 cycles of Gemcitabine-Docetaxel(DG)-chemotherapy, and to compare the disease free survival after randomization in patients treated with 2 years of Zoledronate versus 5 years of Zoledronate in patients with early primary breast cancer. Patients were required to have histopathological proof of axillary lymph node metastases (pN1-3) or high risk node negative, defined as: pT>2 or histopathological grade 3, or age , ≤ 35 or negative hormone receptor, but were not allowed to have evidence of distant disease. Patients were entered into the study no later than 6 weeks after complete resection of the primary tumor. No antineoplastic treatment other than surgical treatment, the defined cytotoxic and endocrine treatment, and radiotherapy was allowed prior to study entry and during the course of the study. After surgery, leading to complete resection of the invasive and intraductal components of the primary tumor, patients were randomized to one of the following two treatments for the first phase of the project (which is included in this GARNET pharmacogenomics study): AA: 3 cycles of 5-Fluorouracil 500 mg/m² i.v. body surface area and Epirubicin 100 mg/m² i.v. and Cyclophosphamide 500 mg/m² i.v., (FEC100), each administered on day 1, repeated on day 22, subsequently followed by 3 cycles of Docetaxel 75 mg/m² body surface area i.v. (D), and Gemcitabine 1000 mg/m² i.v. (30 min infusion) (G), administered on day 1, followed by Gemcitabine 1000 mg/m² i.v. (30 min infusion) on day 8, repeated on day22 AB: 3 cycles of 5-Fluorouracil 500 mg/m² i.v. body surface area and Epirubicin 100 mg/m² i.v. and Cyclophosphamide 500 mg/m² i.v., (FEC100), each administered on day 1, repeated on day 22, subsequently followed by 3 cycles of Docetaxel 100 mg/m² body surface area i.v. (D), administered on day 1, repeated on day 22 A second randomization was made for assigning patients to one of the following two subsequent treatments for the second phase of the project (NOT included in the pharmacogenetic study in this dbGaP submission): BA: Zoledronic acid 4 mg i.v., every 3 months for the duration of two years, subsequently followed by zoledronic acid 4 mg i.v., every 6 months for the duration of additional three years BB: Zoledronic acid 4 mg i.v., every 3 months for the duration of two years Patients with positive hormone receptor status (≥10% positively stained cells for estrogen and/or progesterone) of the primary tumor were recommended to receive Tamoxifen treatment 20 mg p.o. per day for 2 years, after the end of chemotherapy . Subsequent to chemotherapy, postmenopausal patients with positive hormone receptor status were recommended to be treated with Anastrozole (Arimidex®) 1 mg p.o. for additional 3 years, premenopausal patients will continue Tamoxifen treatment for those additional 3 years. In addition to tamoxifen, all patients with positive hormone receptor status of the primary tumor and under the age of 40 or restart of menstrual bleeding within 6 months after the completion of cytostatic treatment or with premenopausal hormone levels as defined below were recommended to receive Goserelin (Zoladex®) 3.6 mg subcutaneously every 4 weeks over a period of 2 years following chemotherapy. Premenopausal endocrine status will be assumed, if the following serum levels are met: LH < 20 mIE/ml, FSH < 20 mIE/ml and E2 > 20 pg/ml. Endocrine therapy will start after the end of chemotherapy. All patients with breast conserving therapy or more than 3 axillary lymph node metastases or in the following cases after mastectomy will receive adjuvant radiotherapy: T3/T4-carcinoma, T2-carcinoma > 3 cm, multicentric tumor growth, lymphangiosis carcinomatosa or vessel involvement, involvement of the pectoralis fascia or a safety margin < 5 mm. Radiotherapy was usually performed after the chemotherapy and parallel to the beginning of the zoledronic acid therapy. Initially, DNA was extracted for performing SNP microarray assays using blood collected at baseline prior to the first randomization. However, the first set of SNP microarray results indicated a quality problem with approximately 50% of the DNA samples. A majority of the problematic samples were replaced with DNA extracted from redrawn blood. The remaining problematic samples were 'restored' using an Illumina FFPE Restoration procedure. A total of 3322 subjects (1638 from arm AA and 1684 from arm AB) were successfully genotyped. Among those, 1771 were from original blood samples, 1092 from redrawn blood samples and 459 from restored blood samples. The SUCCESS-A study is part of the Genomics and Randomized Trials Network (GARNET, http://www.garnetstudy.org) funded by the National Human Genome Research Institute (NHGRI). The overarching goal is to identify novel genetic factors that contribute to disease-free survival for breast cancer patients using different forms of chemotherapy through large-scale genome-wide association studies of treatment response in randomized clinical trials. The study was conducted at the University Hospital Erlangen, Friedrich-Alexander University Erlangen-Nuremberg, Germany. Genotyping was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR). Data cleaning and harmonization were performed at the GARNET Coordinating Center at the University of Washington.

  Study phs000547

• 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

• Distribution of data using Live Distribution

  Live Distribution Welcome to the documentation for using the Live Distribution feature for distributing data files securely through the EGA platform. This guide will walk you through the process of downloading encrypted files and decrypting them using Crypt4GH. Please follow the steps below to ensure a smooth experience. Before Downloading Create an EGA user. Make sure that you have the permissions to download the dataset of interest. In case you don’t have access, request access to the dataset. Add your Crypt4GH-compatible public key to your EGA account. Please allow a few hours for your public key to be synced with your profile. Afterwards, you will be able to connect to your EGA outbox using the SFTP protocol. Download Graphical User Interface (GUI) You can use any GUI that supports SFTP connections, such as FileZilla, an open-source FTP client. For Filezilla as your GUI, follow these steps to download files: Open FileZilla and access Site Manager (File > Site Manager). Create a new connection with the following settings (Figure 1): Protocol: SFTP - SSH File Transfer Protocol Host: __EGA_OUTBOX_DOMAIN__ Logon Type: Key file User: your EGA username Key file: path/to/your/private_key Figure 1: Process of establishing a new connection to __EGA_OUTBOX_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 EGA outbox, ensuring seamless data transfers. Click Connect to access your Outbox. This folder serves as your storage space within the EGA cloud, containing files accessible for download in a secure way. Browse the remote directory on the right side of the FileZilla screen. Select the files you wish to download, right-click, and choose Download (Figure 2). Figure 2: Step-by-step process of manually downñoad files from __EGA_OUTBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can downñoad data from the EGA outbox to their local storage by following the depicted steps SFTP command line You can also use the SFTP command line to securely download files from the EGA Outbox. Using SFTP command line client in Linux/Unix Open a terminal window Enter the following command to connect: sftp username@hostname Enter your EGA password To see a list of available sftp commands type help sftp> put – Upload file sftp> get – Download file sftp> cd path – Change remote directory to ‘path’ sftp> pwd – Display remote working directory sftp> lcd path – Change the local directory to ‘path’ sftp> lpwd – Display local working directory sftp> ls – Display the contents of the remote working directory sftp> lls – Display the contents of the local working directory Type get command to download files. For example: get encrypted_file.c4gh Use the bye command to close the connection (SFTP session). Convenient SSH settings Include the following settings in your SSH config file, located in ~/.ssh/config Host __EGA_OUTBOX_DOMAIN__ EGA-outbox hostname __EGA_OUTBOX_DOMAIN__ User username IdentityFile path/to/the/private/key Replace username and path/to/the/private/key with the appropriate settings, and you will be able to connect to the __EGA_OUTBOX_DOMAIN__ simply using sftp EGA-outbox. How to decrypt Files archived at the EGA are encrypted based on Crypt4GH. Hence, to decrypt the files you need to install Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git After installing Crypt4GH, decrypt files using the following command: crypt4gh decrypt --sk /path/private/key < encrypted_file.c4gh > decrypted_filename The command reads the encrypted file from stdin (with <) and output the decrypted version to stdout (with >). Replace encrypted_file.c4gh and decrypted_filename with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write. Frequently Asked Questions What username should I use to log in to my outbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username, not your email address. Therefore, if you registered a username different from your email address when creating your EGA account, you must use that username to log in. If you have forgotten your registered username, please, contact our Helpdesk team for assistance. I see that some files in my dataset have 'unavailable' as extension. What should I do? Within your Outbox, you'll find a list of all the datasets available for download. Occasionally, certain files may be marked as "unavailable". These unavailable files can be identified by the "unavailable" extension added to their filenames (e.g. filename.fastq.gz.unavailable.c4gh). If you encounter an unavailable file that you need, please reach out to our Helpdesk. We'll promptly work on making the file accessible for download as soon as possible. Specific to using keys 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_OUTBOX_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 access/download/files/live-outbox

• Treatment of Pulmonary Hypertension and Sickle Cell Disease with Sildenafil Therapy (Walk-PHaSST)

  Pulmonary arterial hypertension (PAH) is a progressive condition characterized by narrowing or stiffening pulmonary arterioles resulting in increased pulmonary blood pressure and reduced delivery of oxygenated blood to the body. It is a common complication of sickle cell disease and initially presents with the symptom of shortness of breath (dyspnea) on exertion. As the condition worsens, other symptoms such as dizziness, lower extremity edema, and chest pain can develop. The drug, sildenafil, works by relaxing blood vessels in the lungs which reduces pulmonary blood pressure and allows more oxygenated blood to circulate. Increased levels of oxygenated blood allows individuals with PAH to tolerate more activity, but guidelines for using sildenafil in patients with PAH and sickle cell disease were unavailable at the time of the Walk-PHaSST trial.Participants were screened for the existence of pulmonary hypertension with a six minute walk test and a Doppler echocardiogram that assessed TRV, diastolic function, and valvular and systolic function. Subjects with TRV &#8805; 2.7 m/s received further clinical evaluation for possible causes of pulmonary hypertension. Other screening data included medical history, a physical exam, and standard laboratory testing. For individuals with moderate to severe pulmonary hypertension (TRV &#8805; 3.0), a cardiac catheterization was done at the baseline and week 16 data collection periods.Subjects eligible for the main intervention trial based on screening results were randomized in a 1:1 double blind fashion to receive sildenafil or placebo for 16 weeks. Subjects received 20 mg of oral sildenafil or matching placebo 3 times daily for 6 weeks, followed by 40 mg 3 times daily for 4 weeks, followed by 80 mg 3 times daily for 6 weeks, as tolerated. Participants could also receive other therapies as needed to manage sickle cell and related complications. The primary outcome measure of the trial was change in the six minute walk test, a standard indicator of a person's heart and lung function and exercise capacity, from baseline to week 16. After completing the study treatment (or placebo), participants could choose to be part of the open-label follow-up phase of the study and continue to be assessed for up to one year.The study was intended to screen about 1000 subjects and randomize 132 subjects, however it was terminated early due to the unforeseen increase in adverse events in participants treated with sildenafil as compared to placebo. When the study was stopped, 33 participants had completed the trial. Subjects continued to be monitored, but were instructed to taper sildenafil treatment over three to seven days.There was no evidence that treatment with sildenafil impacted the six minute walk distance from baseline to week 16. In addition, treatment with sildenafil appeared to increase rates of hospitalization due to sickle cell disease pain.Due to in part to the early termination of the trial, the majority of subject data was collected from the screening phase of the study (n=720), as opposed to the main intervention trial (n=74).Instructions for requesting individual-level data are available on BioData Catalyst at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BioData Catalyst. For questions about availability, you may contact the BioData Catalyst team at https://biodatacatalyst.nhlbi.nih.gov/contact.

  Study phs002383

• A Genomic Approach to Warfarin Dose Prescription in Admixed Caribbean Hispanics

  Warfarin is an oral anticoagulant and one of the most used drugs in the world accounting for up to 1.5% of prescriptions globally. Warfarin inhibits vitamin K epoxide reductase complex 1 (VKORC1), an enzyme responsible for the vitamin K recycling that is required for the activation of clotting factors. Warfarin is prescribed at an average dose of 5 mg/day for most of the indications but significant inter-patient variability has been observed. Single nucleotide variations at the VKORC1 (GeneID: 79001) and CYP2C9 (GeneID: 1559) genes alone explain from 28 to 35% of variability in warfarin dose requirements and up to 56% when clinical factors (age, gender, body surface area, diabetes and heart valve) are incorporated into regression analysis. However, genetic-guided dosing algorithms are mostly derived from studies in Europeans. The objective of the present study was to identify genetic polymorphisms that can explain variability in warfarin dose requirements among Caribbean Hispanics of Puerto Rico. VKORC1 (GeneID: 79001) and CYP2C9 (GeneID: 1559), the most important genetic predictors of warfarin response, were sequenced using Next Generation sequencing. Other candidate genes in DMET Plus Assay were assessed to identify genetic variants with relevance in warfarin dose requirements among Puerto Ricans. Our study used the Extreme Discordant Phenotype approach to perform a case-control association analysis that were confirmed with univariate and conditioned regressions. Accordingly, patients were stratified based on stable warfarin doses as sensitive (&#60;4 mg/day), control (4-6 mg/day) and resistant (&#62;6 mg/day). Genetic variants associated with warfarin response among the study cohort were used to perform a multivariate regression analyses to develop a genetic-guided dosing algorithm tailored for Puerto Ricans. The CYP2C9rs2860905 SNP was found to be strongly associated with warfarin dose requirements in Puerto Ricans. The CYP2C9 rs2860905 SNP tags four haplotypes that represent the trihybrid admixture of Puerto Ricans. Therefore, haplotypes harboring the rs2860905 variant are more informative in predicting warfarin dose among Puerto Ricans than the common single segregating SNPs (i.e., CYP2C9*2 and CYP2C9*3) relevant to Europeans. DMET Plus array confirmed the strong association of VKORC1 (GeneID: 79001) and CYP2C9 (GeneID: 1559) with warfarin dose requirements, but also identified other polymorphisms in CES2 (GeneID: 8824) and ABCB1 (GeneID: 5243) associated with warfarin resistance (&#62;6 mg/day). Ancestry analysis showed that Puerto Ricans from Veteran Affairs Caribbean Healthcare System (VACHS) using warfarin had higher Native American proportions than Puerto Ricans from the 1000 Genomes project; however, this difference was not significant. Incorporation of rs2860905 in a regression model (R2=0.60 MSE=0.38) that also included additional genetic predictors (i.e., VKORC1-1639G&#62;A; CYP2C9 rs1856908; ABCB1 rs10276036; CES2 rs4783745) and non-genetic factors (i.e., hypertension, diabetes and age) showed better prediction of warfarin dose requirements than CYP2C9*2 and CYP2C9*3 combined (partial R2=0.132 versus 0.023 and 0.007, respectively, p&#60;0.001). Interestingly, deep vein thrombosis and diabetes were found associated with high warfarin dose requirements among Puerto Ricans. Our results support the use of CYP2C9 rs2860905 along with other genetic markers [e.g., VKORC1(GeneID: 79001 )] and clinical covariates to predict warfarin dose in Puerto Ricans. Although our findings need further replication, this study contributes to the field of Pharmacogenetics and to improve anticoagulation therapy among Puerto Ricans.

  Study phs001496

• Angelman, Rett, Prader-Willi Syndrome Consortium (ARP) Rett Syndrome Natural History Protocol

  This observational study will involve the comprehensive assessment of the clinical features of Rett syndrome with this Rare Diseases Clinical Research Network. A clinical database of 1350 individuals with Rett syndrome including MECP2 mutation status for the purpose of elaborating phenotype-genotype correlations will be established. Eligible participants will be enrolled in the natural history study for 11 years from the 4 clinic sites currently involved with Rett syndrome (BCM, GGC, and UAB, CHB) as well as from the several thousand registrants in the International Rett Syndrome Foundation registry who will be invited to the nearest consortium site involved in Rett syndrome. Potential participants are expected to have had determination of their MECP2 mutation status, but will not be excluded should no mutation be present. All individuals who meet criteria and are currently receiving care from study sites will be invited to participate (N&#62;600). Additional participants will be invited through the assistance of the International Rett Syndrome Foundation (IRSF). All individuals with RS registered with IRSF will be invited to participate in this study via the IRSF website and the IRSF newsletter. Potential participants will be apprised of the participating study sites and invited to contact one of the sites based on feasibility of travel. Inasmuch as the enrollment goal of 1350 participants is 40% of the current IRSF registry, we believe this will be a representative sampling. Bias can certainly occur based on travel requirements, level of interest, and other factors. However, inclusion of such a large sample should minimize sampling bias. No travel expenses will be covered, so it is likely that participants will be those with geographic proximity to Houston, Greenwood, Birmingham, or Boston. From the sample pool described above, the aim is to conduct the observational longitudinal (natural history) study on up to 1350 participants with classic Rett syndrome and variant forms of Rett syndrome, that is, participants who fully meet the established clinical criteria for Rett syndrome and those who meet some but not all of these criteria. All participants expressing MECP2 mutations irrespective of phenotype will be eligible for enrollment. For each of the eight common genetic mutations as well as those with large scale deletions, the prevalence of the following RS characteristics will be estimated for each age category and overall: seizure presence and frequency, ambulation status, scoliosis, ECG abnormality, breathing irregularities while awake, feeding difficulties, growth as measured in percentiles from NCHS standards curves, the presence of osteopenia as evidenced by bone fracture, and the presence of gallbladder disease. Both incidence and prevalence estimates will be made using a combination of data obtained at the regularly scheduled clinical visits and that obtained from the medical history. Incidence estimates will be calculated using time-to-event analyses (e.g., Kaplan-Meier survival curves) with appropriate calculations of standard errors and 95% confidence intervals. Cox proportional hazard regression models will be used to allow control for other factors, and t-tests will be calculated on the coefficients themselves. Appropriate transformations on explanatory variables will be used as deemed necessary in Cox models. Prevalence estimates will be calculated from estimates of proportions with exact confidence intervals. For a sample size of 275, the standard error of the estimate will not exceed 0.03 (3%) and for a sample size of 60, the standard error of the estimate will not exceed 0.06 (6%).

  Study phs000574

• Resuscitation Outcomes Consortium (ROC) Prehospital Resuscitation on Helicopter Study (PROHS) (ROC-PROHS-BioLINCC)

  Accessing Data: Please refer to the "Authorized Access" section below regarding accessing data through the BioData Catalyst ecosystem. The data from this accession is not available for download through dbGaP.Objective: To observe if patients with severe traumatic injuries evacuated to level 1 trauma centers on air ambulances who received prehospital red blood cells and/or plasma had decreased in-hospital mortality compared to patients who received only crystalloids.Background: Injury is the leading cause of death in adults and children between the ages of 1 and 44 years. However, approximately 40% of in-hospital deaths among injured patients involve massive truncal hemorrhage that is considered potentially salvageable. Multiple retrospective military and civilian studies have reported that transfusion involving blood component ratios approaching whole blood are associated with significant decreases in 24-hour and 30-day mortality among injured patients. Furthermore, prehospital transfusion (PHT) studies from military and civilian hospitals have shown that prehospital transfusion of plasma and red blood cells (RBCs) is not only feasible, but associated with improved coagulation status on arrival. Prehospital resuscitation practices in the US differ significantly in approach, with most systems using crystalloids while a few offer RBCs or a combination of plasma and RBCs. No large multicenter civilian studies have evaluated the use of prehospital plasma and RBCs in severely injured patients compared to crystalloids.Participants: A total of 25,118 trauma patients were admitted during the 10 month enrollment period to the nine participating centers, of which 2341 arrived by helicopter, and 1058 met the highest risk criteria. Of the high risk sub-set, 585 arrived on helicopters with blood products available and 473 patients arrived via helicopters without blood available. One hundred forty two patients (24%) of those transported on helicopters with blood products available actually received PHT and 916 patients did not.Design: PROHS was a multicenter, prospective pragmatic, observational study of prehospital resuscitation approaches. There were no study guidelines dictating resuscitation practice (i.e., use of blood products or end of resuscitation). Of the 9 participating Level I trauma centers, 5 had helicopter systems with plasma and/or RBCs while the other 4 had helicopter systems that used only crystalloid resuscitation. All patients arriving to the participating center's trauma emergency department via helicopter directly from the scene were screened and had initial data collected. Of that group, all patients who met the highest risk category or received blood during transport were followed by direct observation during the initial resuscitation period and then indirectly through medical chart review until hospital discharge or 30 days after admission (whichever occurred first).The primary outcome was in-hospital mortality at 3 hours, 24 hours, and 30 days. Other outcome measures included length of hospital stay, number of ICU days, number of ventilator days, blood product usage, GOSE score at discharge, number of patients with complications, and number of patients who required hemostatic devices. Conclusions:Because of the unexpected imbalance in injury severity between systems with and without blood products on helicopters, all analyses were inconclusive. With few units transfused to each patient and small outcome differences between groups, large randomized studies will be required to detect significant survival differences in this important population.

  Study phs003826

• Prediction of Resistance and Sensitivity to HER2 Targeted Therapy in the Neoadjuvant Setting

  Women with breast cancers that overexpress HER2 are at greater risk for disease progression and death than women whose tumors do not overexpress HER2. Trastuzumab, a recombinant humanized monoclonal antibody against the extracellular domain of the HER2 protein blocks downstream signaling of HER2 and substantially improves the efficacy of chemotherapy in women with metastatic and early-stage HER2-positive breast cancers. Because resistance to trastuzumab eventually results in progressive disease in the metastatic setting and contributes to recurrence following adjuvant trastuzumab-based therapy, it is important to develop agents other than trastuzumab that target HER2 signaling through different mechanisms of action. Lapatinib is an oral, small molecule, dual tyrosine kinase inhibitor of HER2 and EGFR. Lapatinib has shown a lack of cross-resistance with trastuzumab in preclinical studies and activity in women with HER2-positive, metastatic breast cancer that has progressed during trastuzumab treatment. Trastuzumab blocks the downstream signaling of HER2 by binding to the extracellular domain of the receptor. Lapatinib binds to the intracellular domains of HER2 and EGFR and prevents activation of downstream signaling pathways. Because of this different mechanism of action, lapatinib may be effective in trastuzumab-resistant disease. The study will also provide important safety information on trastuzumab and lapatinib combinations immediately following anthracycline exposure, and also provide an initial direct comparison of cardiac effects of trastuzumab and lapatinib when incorporated into a standard sequential adriamycin and cyclophosphamide (AC) followed by weekly paclitaxel neoadjuvant regimen. Availability of a second agent that can interrupt HER2-signaling pathways through completely different mechanisms than those of trastuzumab offers the potential for further improvement in the management of patients with HER2-overexpressing breast cancer in both the adjuvant and metastatic setting. Co-administration of both trastuzumab and lapatinib with chemotherapy may be important in improving outcomes in subsets of HER2-positive breast cancers. However, use of two inhibitors of the HER2 pathway will increase costs and may increase toxicity, so it will be important to identify the subsets of patients who would benefit from the dual therapy. Inhibition of HER2 with a single agent clearly is sufficient for many patients as evidenced by the results of the trastuzumab trials. Therefore, co-administration to unselected populations of women with HER2-positive breast cancers would not represent an optimal approach. Given the activity of lapatinib, it is likely that it will also be sufficiently active in inhibiting HER2-pathway activation in some patients to allow for its use as the sole inhibitor of the HER2 pathway. Different populations may also derive greater benefit from one of the HER2-blocking agents relative to the other. Identification of potential predictive factors for pathologic complete response to the combination or to either agent administered alone in neoadjuvant trials would provide important information for adjuvant trials designed to definitively address these important issues. This study will compare 3 combined chemotherapy regimens: AC followed by paclitaxel plus trastuzumab and lapatinib, AC followed by paclitaxel plus lapatinib, and AC followed by paclitaxel plus trastuzumab given before surgery to patients with HER2-positive breast cancer.Tumor samples were collected prior to and post-treatment, and RNA sequencing was performed with this version.

  Study phs003275