The study is designed to identify genetic modifiers of cardiovascular defects in subjects with 22q11.2 deletion syndrome (22q11.2DS), also known as DiGeorge syndrome or velo-cardio-facial syndrome. Affymetrix 6.0 arrays were processed on 1,480 subjects with known cardiovascular anomalies or with normal structures, all with 22q11.2DS. One sample is a duplicate so it was removed. There are 1,472 samples total of unrelated, de-identified, probands. Over 90% have the same sized 3 million base pair deletion flanked by low copy repeats (LCR22) A and D, while approximately 6% have nested A to B deletions. The rest have other nested deletions, that include a deletion in the vicinity of TBX1 (between LCR22 A and B). A subset of the data was used to identify copy number variations serving as modifiers. Some data were previously published by Dr. Emanuel's team at Children's Hospital of Philadelphia in PA, USA (PMID:26742502; PMID:4896312; PMID:25892112; PMID:4570279). The de-identified DNA data from unrelated subjects come from multiple research sites in the US and Europe as part of the International 22q11.2 Consortium and the International 22q11.2 Brain and Behavior Consortium.
This study aimed to determine whether or not treatment with hydroxyurea titrated to maximum tolerated doses would reduce the frequency of vaso-occlusive (painful) crises by at least 50% in 299 men and women between 18 and 50 years old with a diagnosis of sickle cell anemia by gel electrophoresis conducted by a Core Laboratory. A secondary objective investigated correlations of fetal hemoglobin (HbF) levels and other patient or treatment characteristics with the occurrence of vaso-occlusive (painful) crises, and the effect of treatment on the quality of life.This controlled trial made hydroxyurea the first drug of proven benefit in preventing vaso-occlusive pain crisis and acute chest syndrome caused by sickle cell disease, with additional findings including reduced mortality in adult patients taking hydroxyurea for frequent painful sickle cell episodes after 9 of years follow-up. No significant side-effects of hydroxyurea therapy were noted.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.
The data included in this project were generated from several IRB projects focused on the identification of the underlying genetic cause of undiagnosed rare conditions in infants, children and adults enrolled across the southeastern United States. Long read genome sequencing was performed on DNA samples collected as part of an IRB-approved study and findings from this testing was returned to enrolled study participants and the clinical team providing care. Proband participants in these studies were enrolled in both inpatient (neonatal intensive care units) and outpatient settings. When possible, biological relatives (including both biological parents) were also enrolled to help clarify inheritance of variants identified. Sequencing and analysis for SouthSeq is conducted at the HudsonAlpha Institute for Biotechnology in Huntsville, Alabama (https://www.hudsonalpha.org/). Results of testing are disclosed to participants by genetic counselors or trained non-genetics providers who also facilitate sharing of results with the participants' medical care teams when appropriate. Further, participant families may choose to opt-into return of secondary findings identified in the proband, which focus on pathogenic and likely pathogenic variation identified within the current ACMG gene list.
Transcriptional profiles for stemB and proB cells harvested from either primary or secondary xenografts. This dataset contains six types of samples: - diagnostic stemB cells harvested from primary xenografts - diagnostic proB cells harvested from primary xenografts - relapse stemB cells harvested from secondary xenografts injected with stemB cells from primary xenografts - relapse proB cells harvested from secondary xenografts injected with stemB cells from primary xenografts - relapse stemB cells harvested from secondary xenografts injected with proB cells from primary xenografts - relapse proB cells harvested from secondary xenografts injected with proB cells from primary xenografts
Dataset contains paired-end Whole Exome sequencing data from 257 glioma samples from 28 patients. 26 normal blood samples are also included.
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.
Purpose: In oncology, precision medicine centers on tailoring the most appropriate therapy to a patient according to their tumor molecular profile. We addressed the question whether there is a consensus in the classification of actionability of somatic variants and their alignment to treatment recommendations. To this end, we evaluated three commercial clinical decision support tools to assess their variant classification and drug matching strategies.Methods: In this two centers study 48 patients with metastatic breast (n=12), colorectal (n=17) or non-small cell lung cancer (n=19) were recruited based on circulating tumor DNA levels in peripheral blood. In individual patients’ plasma samples, we established somatic copy number alterations and somatic mutations across a 77 cancer-associated gene panel and exposed the obtained molecular profiles to the decision support packages NAVIFY Mutation Profiler (NMP; Roche), Qiagen Clinical Insight (QCI) Interpret (Qiagen) and CureMatch Bionov (CureMatch).Results: In the plasma samples, altogether 492 somatic alterations were assessed. Each decision support platform varied in their format of data input, mode of variant classification and strategies for identifying druggable targets and clinical trials, which resulted in discrepancies in tier classification as well as designations of actionability. The frequency of concordant actionable events for tier I-A or tier I-B classifications, i.e. those with the strongest clinical evidence, was only 4.3%, 9.5% and 28.4% when comparing NMP with QCI, NMP with CureMatch, and CureMatch with QCI, respectively. As a consequence, the obtained treatment recommendations differed drastically, and alignment of treatment recommendations was limited to established predictive markers.Conclusions: The lack of standards for the extraction of treatment recommendations from comprehensive tumor molecular profiling data challenge the promising concepts of precision oncology.
Ewing’s Sarcoma is a bone and soft tissue tumor that primarily affects adolescents and young adults. With current therapies, 70% of patients with localized disease survive but survival for metastatic and recurrent disease is poor. Whole genome sequencing of 19 Ewing’s Sarcoma tumors showed that STAG2 was mutated in 10% (2/19) of the tumors and STAG2 protein was absent in 14% (13/106) tumors by immunohistochemical staining. Previous studies have shown that glioblastoma cells lacking STAG2 are more sensitive to poly-ADP ribose polymerase (PARP) inhibitors. We found that Ewing’s Sarcoma cell lines are sensitive to PARP inhibitors irrespective of STAG2 protein expression. Ewing Sarcoma cell lines are defective in double strand DNA break repair. PARP inhibitor cytotoxicity in Ewing’s Sarcoma cells was potentiated 10-1,000 fold by DNA damaging agents (irinotecan and temozolomide). To extend these studies in vivo, we developed an orthotopic Ewing’s Sarcoma mouse model and performed pharmacokinetic and pharmacodynamic studies with three different PARP inhibitors (BMN-673, olaparib and veliparib) in clinical development for pediatric cancer. Those data were used to design preclinical phase I studies to identify tolerable drug combinations for pilot efficacy testing (preclinical phase II). Based on the results of the preclinical phase I/II data, we performed a double blind, randomized, placebo controlled preclinical phase III trial with 274 mice in 15 treatment groups. Irinotecan administered in a low-dose protracted schedule optimized for pediatric patients was an effective DNA damaging agent to combine with olaparib and BMN-673 and was better tolerated than combinations with temozolomide. Combining olaparib or BMN-673 with irinotecan and temozolomide gave complete and durable responses in over 80% of the mice.
Purpose:Accurate assessment of response during neoadjuvant systemic treatment (NST) poses a major clinical challenge. Therefore, a minimally-invasive assessment of tumor response based on cell-free circulating tumor DNA (ctDNA) may be beneficial to guide treatment decisions.Experimental Design: We profiled 93 genes in tissue from 193 early breast cancer patients. Patient-specific assays were designed to track ctDNA during NST from 145 patients with available plasma. ctDNA presence and levels were correlated with complete pathological response (pCR) and residual cancer burden (RCB) as well as with clinicopathologic characteristics of the tumor to identify potential proxies for ctDNA release. Moreover, we tested the predictive value of driver events identified in the tumor.Results:At baseline, ctDNA could be detected in 63/145 (43.4%) patients and persisted in 25/63 (39.7%) patients at mid-therapy (MT) and 15/63 (23.8%) patients at the end of treatment. ctDNA detection at MT was significantly associated with higher RCB (OR 0.062, 95% CI 0.01-0.48, P=0.0077). Out of 31 patients with detectable ctDNA at MT, 30 patients (96.8%) were non-responders (RCB II, n=8; RCB III, n=22) and only one patient responded to the treatment (RCB I). Considering all 145 patients with baseline (BL) plasma, none of the patients with RCB 0 and only 6.7% of patients with RCB I had ctDNA detectable at MT, while 30.6% and 29.6% of patients with RCB II/III, respectively, had a positive ctDNA result. Conclusion:Overall, our results demonstrate that the detection and persistence of ctDNA at mid-therapy may have the potential to negatively predict response to neoadjuvant treatment and identify patients who will not achieve pCR or be classified with RCB II/III.
Raw data of ctDNA profiling using the PredicineWES+ or PredicineBEACON assay in patients enrolled in divarasib phase I GO42144 study.
