464 results for "GitHub+primate+acoustics+baboon+Zenodo+10.5281+Gui*"

in 14.96 milliseconds.

• 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

• Out with the Java, in with the Python - new EGA data download client unveiled

  We will shortly be deprecating the Java-based download client also known as API V2. The Java client began its life at the back end of 2014, and during its time has seen many developments that have served our users well. During its tenure, the Java client enabled distribution of over 6.5 million files totalling nearly 15 petabytes of data to researchers around the globe. Recent increases in genomic and phenotypic data file sizes, the number of datasets archived in the EGA, the number of users downloading data, and the diversity of download locations has meant that at times the Java client struggled to distribute data efficiently. In response, our team of developers have built a new download client with more robust features and better functionality and reliability. Enter stage left our shiny new API V3.1! The new API V3.1 will replace both API V2 and API V3. The download client for the new API V3.1 is written in Python, and the code is openly available on Github. This Python client makes https calls to the EGA AAI (https://ega.ebi.ac.uk:8443/) and to the EGA Data API (https://ega.ebi.ac.uk:8052), both of which must be accessible from the client location. In addition to general updates to improve performance, the API V3.1 has three new features enhancing the EGA distributions services. First, requested data are now downloaded over secure https connections rather than http, meaning that data can be delivered unencrypted. Instead of separately requesting, downloading, and decrypting data using the Java client, data can now be requested and downloaded using a single command without the need for decrypting. The API V3.1 also automatically verifies each file’s unencrypted md5 after download to ensure the file has downloaded correctly. Second, the new API supports segmenting and automatic resuming. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the new resume feature, downloads - both segmented and continuous stream - will automatically resume if they encounter any errors or the connection is interrupted. These features result in both a faster and more reliable download experience. Finally, the new API V3.1 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file saving both time and storage space. The new features of the Python-based API V3.1 represent significant improvements in security, speed, reliability, and flexibility that are sure to provide a better data download experience. To take full advantage of these features, users must update to Python 3.X. Considering the changes in the data structures with the new API, the upgrade to a new version of the Python client is also mandatory. Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 -U We are excited for users to try out the new features and take advantage of the multifariously growing EGA distribution services for human biomedical omics data. If you have any questions or feedback, please email the EGA Helpdesk team. We'd love to hear from you!

  Blog new-ega-data-download-client

• Programmatic submission based on XML

  Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

  Documentation submission/metadata/submission/programmatic-submission-xml

• Papua New Guinean Genome Diversity Commitee

  Dac EGAC00001002177

• Papua New Guinean Y chromosome Diversity Commitee

  Dac EGAC00001002531

• Paired-end RNA-seq analysis of the TERT promoter mutant GBM cell lines

  This dataset contains 9 RNA-seq BAM files. RNA was derived from TERT promoter mutant GBM cell lines and sequenced on an Illumina HiSeq4000 sequencer with paired-end reads and an average read length of 50 base pairs. Reads were aligned with TopHat (v2.0.14) using a GENCODE V19 transcriptome-guided alignment.

  Dataset EGAD00001005435

• 3q-capture DNA sequencing of primary AMLs with 3q26 rearrangements

  This dataset contains DNA sequencing of the chromosome 3q region in 28 primary AML cases with 3q26 rearrangements (3q26-rearranged AML). Genomic DNA was fragmented using the Covaris shearing device (Covaris), and sample libraries were assembled following the TruSeq DNA Sample Preparation Guide (Illumina). After ligation of adapters and an amplification step, target sequences of chromosomal regions 3q21.1-q26.2 were captured using custom in-solution oligonucleotide baits (Nimblegen SeqCap EZ Choice XL). The design of target sequences was based on the human genome assembly hg19: chr3q21.1:126036241-130672290 - chr3q26.2:157712147-175694147. Amplified captured sample libraries were paired-end sequenced (2x100 bp) on the HiSeq 2500 platform (Illumina) and aligned against the hg19 reference genome using the Burrows-Wheeler Aligner (BWA).

  Dataset EGAD00001006820

• Comprehensive NGS Profiling to Enable Detection of ALK Gene Rearrangements and MET Amplifications in Non-Small Cell Lung Cancer

  We evaluate the analytical performance of the PGDx™ elio™ tissue complete assay, a 505 gene next-generation sequencing (NGS) tissue-based assay, that has now been FDA-cleared for use by physicians to help guide treatment decisions for cancer patients, using a NSCLC cohort of 38 patients.

  Dataset EGAD50000000016

• AVENIO Expanded ctDNA panel sequence alignments (BAMs)

  The AVENIO ctDNA Expanded Kit is a next-generation sequencing (NGS) liquid biopsy assay with a 77 gene panel (192 kb) containing genes in U.S. National Comprehensive Cancer Network (NCCN) Guidelines and emerging cancer biomarkers. This pan-cancer assay was applied to 100 plasma samples from patients with lung cancer undergoing treatment in the OSCILLATE trial. After 150 bp paired-end sequencing, reads were aligned to the human genome reference with the AVENIO Oncology Analysis Software. These files are the sorted non-deduplicated alignments generated by the analysis software used for subsequent variant, indel and CNV calling.

  Dataset EGAD50000000138

• Access to dataset, "Feasibility of Functional Precision Medicine for Guiding Treatment of Relapsed/Refractory Pediatric Cancers"

  Access to sequencing data from project.

  Dac EGAC50000000124

• SNP Genotype Data: Subpopulations of Filipino, Malaysian, and Papua New Guinea

  In the context of the study 'Exploring Adaptive Phenotypes for the Human Calcium-Sensing Receptor Polymorphism R990G,' this repository contains 11 VCF files. Each file includes genetic data from 22 autosomes, representing distinct subpopulations. The subpopulations are as follows: Malaysian: Aeta (15 samples) Agta (11 samples) Batak (10 samples) Mamanwa (6 samples) Filipino: Jehai (13 samples) Kintaq (6 samples) Temiar (5 samples) Papua New Guinea: Highlands (2 samples) Koinambe (10 samples) Kosipe (10 samples) Sepik (2 samples) The numbers in parentheses indicate the sample size for each respective subpopulation.

  Study EGAS50000000044

• MediMer: A versatile do-it-yourself peptide-receptive MHC class I multimer platform for tumor neoantigen-specific T cell detection

  Peptide-loaded MHC class I (pMHC-I) multimers have revolutionized our capabilities to monitor disease-associated T cell responses with high sensitivity and specificity. To improve the discovery of T cell receptors (TCR) targeting neoantigens of individual tumor patients with recombinant MHC molecules, we developed a peptide-loadable MHC class I platform termed MediMer. MediMers are based on soluble disulfide-stabilized β2-microglobulin/heavy chain ectodomain single-chain dimers (dsSCD) that can be easily produced in large quantities in eukaryotic cells and tailored to individual patients’ HLA allotypes with only little hands-on time. Upon transient expression in CHO-S cells together with ER-targeted BirA biotin ligase, biotinylated dsSCD are purified from the cell supernatant and are ready to use. We show that CHO-produced dsSCD are free of endogenous peptide ligands. Empty dsSCD from more than 30 different HLA-A,B,C allotypes, that were produced and validated so far, can be loaded with synthetic peptides matching the known binding criteria of the respective allotypes, and stored at low temperature without loss of binding activity. We demonstrate the usability of peptide-loaded dsSCD multimers for the detection of human antigen-specific T cells with comparable sensitivities as multimers generated with peptide-tethered β2m-HLA heavy chain single-chain trimers (SCT) and wild-type peptide-MHC-I complexes prior formed in small-scale refolding reactions. Using allotype-specific, fluorophore-labeled competitor peptides, we present a novel dsSCD-based peptide binding assay capable of interrogating large libraries of in silico predicted neoepitope peptides by flow cytometry in a high-throughput and rapid format. We discovered rare T cell populations with specificity for tumor neoepitopes and epitopes from shared tumor-associated antigens in peripheral blood of a melanoma patient including a so far unreported HLA-C*08:02-restricted NY-ESO-1-specific CD8+ T cell population. Two representative TCR of this T cell population, which could be of potential value for a broader spectrum of patients, were identified by dsSCD-guided single-cell sequencing and were validated by cognate pMHC-I multimer staining and functional responses to autologous peptide-pulsed antigen presenting cells. By deploying the novel CHO producer cell-based dsSCD MHC-I MediMer platform, we hope to significantly improve success rates for the discovery of personalized neoepitope- specific TCR in the future by being able to also cover rare HLA allotypes.

  Study EGAS50000000065

• AVENIO Expanded ctDNA panel sequence alignments (BAMs) from plasma DNA of lung cancer patients from the OSCILLATE trial

  The AVENIO ctDNA Expanded Kit is a next-generation sequencing (NGS) liquid biopsy assay with a 77 gene panel (192 kb) containing genes in U.S. National Comprehensive Cancer Network (NCCN) Guidelines and emerging cancer biomarkers. This pan-cancer assay was applied to 100 plasma samples from patients with lung cancer undergoing treatment in the OSCILLATE trial. After 150 bp paired-end sequencing, reads were aligned to the human genome reference with the AVENIO Oncology Analysis Software. These files are the sorted non-deduplicated alignments generated by the analysis software used for subsequent variant, indel and CNV calling.

  Study EGAS50000000103

• Sensitive circulating tumor DNA based residual disease detection in epithelial ovarian cancer

  We analyzed 264 plasma samples collected between June 2016 and September 2021 from 63 epithelial ovarian cancer patients using tumor-guided plasma cell-free DNA analysis to detect residual disease after treatment.

  Dataset EGAD50000000360

• Bulk Iso-Seq from brain tissue and exosomes isolated from brain tissue using long-read PacBio sequencing of poly-adenylated transcripts

  Human brain sEVs were isolated from postmortem human brain tissue. RNA was extracted from both the source brain tissue and sEVs and prepared for long-read sequencing. cDNA was sequenced on the PacBio Sequel II. The data provided have undergone processing using the tool ccs (v6.0.0) to generate circula consensus reads. For further processing, it is recommended to follow the guidelines at https://isoseq.how/, starting with using lima to remove cDNA primers.

  Dataset EGAD50000000043

• Comprehensive NGS Profiling to Enable Detection of ALK Gene Rearrangements and MET Amplifications in Non-Small Cell Lung Cancer

  We evaluate the analytical performance of the PGDx™ elio™ tissue complete assay, a 505 gene next-generation sequencing (NGS) tissue-based assay, that has now been FDA-cleared for use by physicians to help guide treatment decisions for cancer patients, using a NSCLC cohort of 38 patients.

  Study EGAS50000000010

• Cross-Sectional Characterization of Idiopathic Bronchiectasis

  This GDMCC protocol will study adult patients with non-CF, idiopathic bronchiectasis, whose genetic etiologies are not known. Idiopathic bronchiectasis is reportedly more common in females with certain tall, thin body types and associated with environmental organisms, such as nontuberculous mycobacterium (NTM). The other susceptibility factors predisposing to bronchiectasis or acquisition of NTM are unclear. The study will attempt to broaden the understanding of this disease by comparing gender-associated factors and NTM status. A relatively equal number of both females/males and NTM/non-NTM infected subjects will be enrolled. Approximately 300 people may be screened to find 260 eligible subjects, since a small number (e.g., 40 patients) may be diagnosed with PCD, vCF, or other known etiology as an explanation for the bronchiectasis. This single-visit protocol will use a systematic approach to characterize the physical features, radiographic patterns, and associated lower airway microbial flora. There is no natural history of disease course follow-up component to this protocol. Participants will have one outpatient clinic visit for evaluation with a physical examination including detailed body size measurements, medical history, collection of blood samples for routine lab tests and genetic analyses, and a chest X-ray if no recent one is available. Participants will also have tests of lung function, and measurement of a gas called nitric oxide in the nose. Participants whose initial tests show abnormal results may also be asked to have a nasal scrape to collect cell samples and/or a skin sweat test to measure salt concentrations. Participants will also have a sputum specimen collected during the visit and will be asked to collect two additional early morning sputum samples and a mouth rinse at home within 2 weeks of the clinic visit, and mail the sample collection materials to the research team. Careful evaluation and characterization of the physical and clinical characteristics will guide the genetic characterization of idiopathic bronchiectasis, and likely lead to an improved diagnostic approach. Identification of disease causing genes may provide new therapeutic targets.

  Study phs001279

• Discovering the Genetic Basis of Human Neuroblastoma: A Gabriella Miller Kids First Pediatric Research Program (Kids First) Project

  The Gabriella Miller Kids First Pediatric Research Program (Kids First) is a trans-NIH effort initiated in response to the 2014 Gabriella Miller Kids First Research Act and supported by the NIH Common Fund. This program focuses on gene discovery in pediatric cancers and structural birth defects and the development of the Gabriella Miller Kids First Pediatric Data Resource (Kids First Data Resource). All of the WGS and phenotypic data from this study are accessible through dbGaP and kidsfirstdrc.org, where other Kids First datasets can also be accessed. Children with disseminated neuroblastoma have a very high risk of treatment failure and death despite receiving intensified chemotherapy, radiation therapy and immunotherapy. The long-term goal of our research program is to ultimately improve neuroblastoma cure rates by first comprehensively defining the genetic basis of the disease. The central hypothesis to be tested here is that neuroblastoma arises largely due to the epistatic interaction of common and rare heritable DNA variation. Here we will perform a comprehensive whole genome sequencing of 563 quartets of neuroblastoma patient germline and diagnostic tumor DNAs and germline DNAs from both parents. The case series was recently collected through a Children&#39;s Oncology Group epidemiology clinical trial and is robustly annotated with complete demographic (age, sex, race, ethnicity), clinical (e.g. age at diagnosis, stage, risk group), epidemiologic (parental dietary and exposure questionnaire) and biological (e.g. tumor MYCN status and multiple other tumor genomic measures) co-variates. Subjects were consented for genetic research and DNA is immediately available for shipment for sequencing. We propose Illumina-based whole genome sequencing in the 593 "trio" germline samples (Aim 1; due to missing parent: 487 full neuroblastoma triads, 106 child-single parent dyads = 1673 whole genome sequences) and matched diagnostic tumor DNA (Aim 2; N=366) at 30x sequencing depth (N=2039 whole genome sequences). Also in Aim 2 we will perform whole exome (100x) and RNA sequencing on the 366 tumor DNA and 228 tumor RNA samples from this cohort. Finally, we propose a pilot study of structural variation using long-range sequencing in 10 non-overlapping tumor samples chosen based on potentially relevant chromosomal alterations discovered with conventional NGS. Thus, a total of 2277 individual samples and 2655 sequences will be generated. We will use our established analytic pipeline that is currently being used to study the germline genomes of all cases sequenced through the NCI supported Therapeutically Applicable Research to Generate Effective Treatments program. We plan a three-stage analytic approach, first focusing on classic de novo and inherited Mendelian damaging alterations. We will next integrate our extensive epigenomic data from human neuroblastoma cell lines and genome-wide association study data (N=5,703 neuroblastoma cases to date) to guide a comprehensive assessment of noncoding variants that influence tumor initiation with a recently established analytic pipeline. Finally, we will utilize the tumor DNA analyses to inform relevance via somatic gain or loss of function effects at the sequence and/or copy number levels. All data generated in this project will be immediately placed into the Genomic Data Commons (GDC) and we will compute within this environment by importing our analytic pipelines into the GDC. These data will be fully integrated into the Kids First Data Resource and freely shared with all academically qualified petitioners. This comprehensive data set derived from a large and richly phenotyped series of neuroblastoma DNA quartets will be integrated with existing germline and/or tumor genomic data from over 6,000 neuroblastoma subjects (but none with matched patient-parent germline sequencing data) to provide an unparalleled opportunity to comprehensively discover the genetic basis of neuroblastoma.

  Study phs001436

• International Cancer Proteogenomics Consortium (ICPC): Proteogenomics of East-Asian Breast Cancer

  The incidence of invasive breast cancer is rapidly increasing in East Asia, enriching in younger patients and luminal disease. We presented a deep proteogenomic landscape of a prospectively enrolled early-stage cohort in Taiwan to uncover the etiology, age-related subtype and oncogenic vulnerabilities underlying the heterogeneous disease. Multilayer proteogenomic architecture revealed distinct endogenous and environmental carcinogen-associated mutagenesis, linking APOBEC (apolipoprotein-B mRNA editing enzyme, catalytic polypeptide-like) cytidine deaminase and DBAC (dibenz[a,j] acridine) signatures to significantly elevated hormone biosynthesis and chemical carcinogenesis in younger patients, and identifying a novel subset of high mutation burden and immune escape potentially beneficial from combined epigenetic therapy and immunotherapy. A proteomics-informed classification resolves luminal heterogeneity, defines high-risk recurrent luminal disease and nominates biomarkers and actionable druggable pathways. Furthermore, proteogenomics profile distinguished a young luminal population susceptible to exogenous carcinogen and having DNA repair deficiency. This study illuminates the age-related molecular subtypes and oncogenic vulnerabilities, providing a proteogenomics-transformative guide for patient stratification and precision therapeutics beyond clinical staging.

  Study phs003150

• Ghana Breast Health Study

  The Ghana Breast Health Study (GBHS) was a multi-disciplinary, population-based case-control study conducted in Accra and Kumasi, Ghana that was designed to investigate breast cancer etiology in the West Africa region. The study enrolled 1,126 invasive breast cancer cases and 2,106 frequency matched population-based controls using census-based sampling. GHBS participants were between the ages of 18 to 74 years of age. Breast cancer cases were recruited at the time they presented with lesions suspicious of breast cancer at three hospitals: Korle Bu Teaching Hospital (Accra), Komfo Anoyke Teaching Hospital (Kumasi) and Peace and Love Hospital (Kumasi). These hospitals are the primary providers of treatment for breast cancer in Ghana, allowing for cases in our study to represent most breast cancers diagnosed in these areas during the study period. The following publications describe the GBHS in detail: 1) Brinton LA et al. Design considerations for identifying breast cancer risk factors in a population-based study in Africa. Int J Cancer 2017;140:2667-2677 (PMID:28295287). 2) Nyante SJ et al. Recruiting population controls for case-control studies in sub-Saharan Africa: The Ghana Breast Health Study. PloS one 2019;14:e0215347 (PMID:30990841)Among subjects with an available source of germline DNA genotyping was performed using the Infinium Global Screening Array-24 per the manufacturer&#8217;s guidelines using the Infinium automated protocol. We excluded probable duplicates and close relatives, and samples with a call rate &lt; 95% or samples with extreme heterozygosity. Female sex was verified by Identifiler using X chromosome heterozygosity and the X chromosome inbreeding coefficient F statistics. The GLU genetics&#8217; ld.tagzilla module was used to confirm African ancestry. To resolve more detailed population substructure, principal components analysis was conducted among all unrelated subjects using the EIGENSOFT v7.2.1. Imputation was performed using the Michigan imputation server Minimac3 with 1K genomes phase3 as reference panel.

  Study phs002387

• Joslin Study on the Genetics of Type 2 Diabetes

  Between 1993 and 2003, families were recruited in the Joslin Study on the Genetics of Type 2 Diabetes for the presence of an autosomal dominant mode of inheritance of diabetes. Recruiting and screening of families occurred through probands who were receiving medical care at the Joslin Clinic (Boston, MA). Screening of families included 1) a proband and at least one sibling with type 2 diabetes, 2) diabetes occurring in at least three generations, 3) diabetes inherited on one side of the prospective family. Probands had to have a diabetes diagnosis between the age range from 10 to 60 years. Demographic data, clinical data, and family history were collected from participating family members, along with blood and urine samples. This study includes genetic and phenotypic data from one family examined in Simeone, Wilkerson, et. al. (NPJ Genomic Medicine 2022, PMID: 35869090). Genotype data for 14 family members and whole genome sequencing data for 6 individuals were generated with the goal of identifying a potential genetic cause of disease in this family. To de-identify this family and protect confidentiality, information on sex in phenotype data and variants identified in X, Y, and MT chromosomes have been removed in compliance with IRB guidelines.

  Study phs002959

• Whole Exome Sequencing and RNA-Seq to Characterize the Somatic Breast Cancer Landscape Among Latinas in California

  Somatic mutational profiles are increasingly being used to guide treatment. However, there is a dearth of data from non-European populations. To address this gap, we conducted paired tumor/normal whole exome paired-end sequencing and tumor RNA-Seq on 146 breast tumors from 140 Hispanic/Latina (H/L) women with breast cancer. We characterized somatic mutations, copy number alterations, tumor subtypes [Prediction Analysis of Microarray 50 (PAM50)], Catalogue Of Somatic Mutations In Cancer (COSMIC) mutation signatures and expression profiles, and compared them to breast tumors from non-Hispanic White (White) women in The Cancer Genome Atlas (TCGA). Using MutSigCV, we found that the most commonly mutated genes, including TP53, RUNX1, PTEN, PIK3CA, MAP3K1, GATA3, CDH1 and CBFB, were similar to those in breast tumors from non-Hispanic white women. Novel findings were that outliers of BLTP2 (aka KIAA0100) over-expression and COSMIC mutational signature 16 were more common in tumors from H/L women than White women. We also identified that the known germline APOBEC3A/B deletion variant was significantly more common in H/L women and was associated with indigenous American ancestry. Data available through dbGaP will be whole-exome sequencing (WES) and RNA sequencing (RNA-Seq) data, as well as phenotypic data, including estrogen receptor, progesterone receptor, and HER2 receptor status, tumor histology, stage, and grade, and age at diagnosis.

  Study phs003218

• NHLBI Recipient Epidemiology Donor Evaluation Study (REDS)-III - Red Blood Cell Omics (RBC-Omics) Study

  The Recipient Epidemiology and Donor Evaluation Study-III (REDS-III) is an initiative launched by the National Heart, Lung, and Blood Institute (NHLBI) with the goal to improve transfusion medicine practice, ensure safety and reduce risks. Extensive variation exists in donor iron metabolism, hemoglobin production, and hemolysis. Despite this variation, current blood banking guidelines regulating blood donation frequency, donation volume, and storage time and conditions remain uniform for all donors. The RBC-Omics study proposed to investigate if this approach is appropriate. Specifically, the RBC-Omics study: Established a multi-ethnic cohort of blood donors with well-characterized demographic, behavioral, and donation history. Developed a database linking donations from these blood donors to outcomes in transfusion recipients. Identify genetic factors impacting hemoglobin, donation history, ferritin, and iron metabolism. Identify markers and clinical factors associated with the iron-related disorders pica and restless leg syndrome (RLS). Define the genetic and metabolic basis for donor-specific differences in spontaneous, osmotic and oxidative hemolysis at the end of storage. RBC-Omics study has 13,403 blood donors over the age of 18 that were recruited from December 2013 to December 2015 at four REDS-III blood centers: the American Red Cross (Farmington, CT), the Institute for Transfusion Medicine (ITxM, Pittsburgh, PA), Blood Center of Wisconsin (Milwaukee, WI), and the Blood Centers of the Pacific (San Francisco, CA). All blood donors are healthy volunteers who passed donation screening and were not anemic. The samples were genotyped with a customized Affymetrix Axiom array called the TM-Array. The TM-array was specifically designed to cover genetic variations related to transfusion medicine. Also copy number polymorphisms in the alpha globin, beta globin and Rh gene clusters were added. The genetic variations among different ethnicity groups were considered as well.

  Study phs001955

• Genomic Predictors of Combat Stress Vulnerability and Resilience

  The Genomic Predictors of Combat Stress Vulnerability and Resilience Study was designed to probe the likely hereditary basis for risk or resilience to develop PTSD and other trauma spectrum disorders. The overall guiding hypothesis was that genomic variation gives rise to risk/susceptibility traits that, when actuated by traumatic environmental stimuli, such as combat, give rise to PTSD and other stress-related phenotypes. Two studies designed to identify risk and resilience factors for combat-induced, stress-related symptoms are being conducted by our group: The Marine Resiliency Study (MRS) is a prospective PTSD study with longitudinal follow-up (pre- and post-exposure to combat stress) of US Marines bound for deployment to Iraq or Afghanistan. Extensive phenotyping includes 3 domains: Psychosocial, Psychophysiologic, and Biophysiologic. The biological and physiological measures collected were chosen in part due to their potential to serve as intermediate phenotypes for stress-related disorders. A second, cross-sectional study involves a cohort of combat-exposed active duty or previously deployed service members (CAVC), including PTSD cases and controls with comparable psychosocial and clinical phenotypes. Little information is available about the factors that explain why some trauma survivors develop stress disorders and some do not. It is hoped that the insights gained from this approach will improve understanding of the genetic contributors to PTSD, and potentially provide novel diagnostic tests and therapeutic approaches to this currently enigmatic and difficult-to-manage condition.

  Study phs000864

• eMERGE Network's Multi-Center Pilot of Pharmacogenetic Sequencing in Clinical Practice

  eMERGE-PGx is a multi-site test of the concept that sequence information can be coupled to electronic medical records (EMRs) for use in healthcare. The promise of personalized medicine - health care guided by each individual&apos;s biological characteristics - is being fostered by increasingly powerful and economical methods to acquire clinically relevant biomarkers from large numbers of people. One therapeutic area that seems especially ripe for an early test of the personalized medicine concept is pharmacogenomics (PGx) - the idea that individual variation in drug response includes a genomic component. Drug response variation is an accepted feature of virtually all drug treatments, and contemporary molecular biologic tools continue to identify key genes mediating drug metabolism, transport, and targets. Importantly, common variation in these genes is an increasingly well-recognized contributor, sometimes with large effects, to variation in drug responses. As a result, recommendations for genotype-guided therapy are increasing. These evidence-based recommendations, if implemented in health care practice, could reduce adverse drug events and improve time to therapeutic response. Through eMERGE-PGx, we are developing strategies for the optimal implementation of genetic sequence data into the clinical environment with the ultimate goal of improving patient care. Site and participants include: Children&#39;s Hospital of Pennsylvania (CHOP): The Center for Applied Genomics (CAG) at the Children&#39;s Hospital of Philadelphia (CHOP) is a high-throughput, highly automated genotyping and sequencing facility equipped with state-of-the-art genotyping and sequencing platforms. Children who are treated at the Children&#39;s Hospital Healthcare Network and their parents may be eligible to take part in a major initiative to collect more than 100,000 blood samples, covering a wide range of pediatric diseases. The PGx population selected for sequencing with the PGRNseq panel at CHOP is 1,650 children from CAG&#39;s biorepository with well-documented drug-related severe adverse events (SAEs) or EHR-based drug response profiles. SAEs were extracted from EPIC records and from CHOP&#39;s Adverse Event (AE) database, which documents every AE at CHOP. These AEs are classified by a medical review panel according to the causal relationship with the suspected drug into &#39;doubtful&#39;, &#39;possible&#39;, and &#39;probable&#39;. Individuals with events classified as probable, severe and objective, were selected for sequencing. The drugs more frequently associated with adverse events are antibiotics, antineoplastics, immunosuppressants and psychotropic drugs. This cohort constitutes 50% of the target population. The remaining subjects were selected using EHR-based algorithms that we have developed and validated at CAG for identifying patients not responding to ADHD medication (primarily atomoxetine) and patients refractory to antiepileptic treatment from responders. Cincinnati Children&#39;s Hospital Medical Center/Boston&#39;s Children&#39;s Hospital (CCHMC/BCH): 811 CCHMC samples were obtained from children, adolescents or young adults exposed to medication or at risk for needing medication of study interest. 55% of participants were exposed to one or more opioids and their DNA source was a CCHMC study-specific biobank; while 27% of participants were at risk for needing an opioid for surgical pain management and were newly recruited. The remainder of the cohort was exposed to methylphenidate and their DNA samples were obtained from a CCHMC study-specific biobank. The focus of Boston Children&#39;s Hospital eMERGE PGx project is on individuals with epilepsy. Samples were taken from a current pharmacogenomics study already in place through which DMET analysis was run and used as confirmation for PGRN-Seq results. A total of 109 samples were sent for PGRN-Seq analysis at University of Washington. The remaining 141 epilepsy samples were from Children&#39;s Hospital of Philadelphia and underwent testing with PGRN-Seq at CHOP. Geisinger Health System: A research cohort of adult Geisinger Clinic patients was enrolled from community-based primary care clinics of the Geisinger Health System. Patients were eligible for enrollment if they were a primary care patient of a Geisinger Clinic physician and were scheduled for a non-emergent clinic visit. All data are from Geisinger patients who consent to participate in the MyCode project. MyCode participants agree to provide biological samples for broad research use, including genomic analysis, and for linking of sample data to information in the participant&#39;s Geisinger health record. The consent also permits sharing of de-identified data for research purposes. Group Health(GH)/University of Washington (UW): Potential GH participants for the PGx project 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~6300). Participants were eligible if aged 50 - 65 years old at the time of their enrollment into the NWIGM repository, living, enrolled in GH&#39;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 Group Health: 1. Demographics - participants with self-reported race as Asian or African ancestry were prioritized and selected to enrich for non-European ancestry; 2. Diagnosis and procedure codes - participants were selected if found to have a history of hypertension, atrial fibrillation (AF,) or congestive heart failure (CHF). Participants with a history of arrhythmia were added if the entire selection algorithm did not generate 900 individuals. We also enriched for participants with EHR evidence of actionable indications related to PGRNSeq genes. Participants were selected if found to have an ICD9 code for malignant hyperthermia, hypertension, atrial fibrillation, congestive heart failure or long QT syndrome (LQTS); 3. Laboratory values - if a participant had any laboratory event of creatine kinase (CK) &#62; 1000, and were dispensed statins within 6 months of the event, then they were selected; and 4. Medications - participants were excluded if ever on carbamazepine or had a current regimen of warfarin. Essentia Institute of Rural Health, Marshfield Clinic, Pennsylvania State University (Marshfield): For this study, 750 subjects were selected and enrolled into PGx based on Vanderbilt&#39;s algorithm designed to enrich for patients who are most likely to receive one of three common drugs (Clopidogrel, Warfarin or Simvastatin) in the next 2-3 years. These patients were sent a letter of invitation and description of the PGx project. Follow-up phone calls were made, and interested subjects came in for a one time meeting to discuss the project and go through the informed consent with the research coordinator. If they were interested they signed the consent and HIPAA forms and gave blood. Subjects were chosen and enrolled into PGx independently of previous biobank participation. Mayo Clinic: The Right Drug, Right Dose, Right Time - Using Genomic Data to Individualize Treatment (The RIGHT Protocol) enrolled 1013 patients to test the hypothesis that prescribers could deliver genome-guided drug therapy at the point-of-care by using pharmacogenomic data preemptively integrated in the electronic medical record. Complete details regarding the study population have been previously described (Bielinski et al., 2014). Icahn School of Medicine at Mount Sinai School (Mt Sinai): Our study site is the Primary Care Associates (PCA) practice group of the Mount Sinai Faculty Practice Associates (FPA) of the Mount Sinai Medical Center in New York City. This practice has 12 physician providers. All patient encounters are documented and managed with EpicCare ambulatory electronic medical record. Active PCA Patients eligible for enrollment fulfilled the following criteria: a) age 50 or older receiving clinical care at Mount Sinai FPA PCA practice with at least one practice encounter within 18 months prior to commencement of enrollment; b) no history or current use of clopidogrel, warfarin, or simvastatin. Eligible patients were invited to participate through de novo recruitment by letter sent by their provider. Interested patients were screened for eligibility and enrolled to participate in the eMERGE PGX study on site by a dedicated research coordinator. In addition to de novo enrollment from clinical practice, patients of FPA PCA who had previously enrolled in Mount Sinai&#39;s BioMe Biobank program AND fulfilled eligibility criteria as stated under a) and b) were identified by chart review and samples sequenced at CIDR using PGRNseq platform (N=300). PGRNseq data from 291 samples passed stringent quality control and are included in the current data set. Furthermore, 56 of these patients carrying known and validated &#39;actionable&#39; variants affecting prescribing of clopidogrel, warfarin, and/or simvastatin were enrolled in the eMERGE PGX study following invitation through recontacting by the Principal Investigator of the BioMe Program. Northwestern University: Participants for this study were recruited from the General Internal Medicine (GIM) clinic at Northwestern Medical Group (NMG). Patients were selected for invitation to participate if they had been seen a minimum of two times over the last four years, having a high likelihood to receive a prescription for warfarin, Plavix, or a statin, and are seeing a physician who has agreed to allow their patients to be contacted for the study. We utilized an algorithm developed at Vanderbilt and tailored to our population which uses our EHR to estimate the probability that individuals will receive a prescription for warfarin, Plavix, or a statin in the next three years. Participants were sent a letter explaining the study prior to their GIM appointment and offered participation at the time of their visit. Participants were consented on-site and blood drawn after consent was obtained. The GIM clinic consists of 39 primary care physicians who provide approximately 80,000 patient encounters per year. As with any large primary care clinic, a significant proportion of patients in GIM clinic suffer from a variety of chronic health conditions, such as diabetes, hypertension, and coronary artery disease. Over 50,000 individuals have been seen by GIM doctors in the past 5 years; 11,562 of these patients have evidence of a statin prescription in the EHR, 3,436 have evidence of a warfarin prescription, and 1,872 have evidence of a Plavix prescription. Vanderbilt University: The more than 1000 participants enrolled into Vanderbilt&#39;s eMERGE PGx study were newly recruited from the Cardiology and Internal Medicine Clinics and the Hillsboro Medical Group within Vanderbilt University Medical Center (VUMC). Patients were selected based on a predictive algorithm estimating the patient&#39;s likelihood of receiving Clopidogrel, Warfarin, and/or Simvastatin. The algorithm identifies primarily older middle-aged patients, and the mean age of the study group is 74. The cohort is approximately 45% female with 75% of subjects self-identified as EA and 24% as AA. Subjects were consented in person by study personnel following a routine clinic visit and an introduction to the study staff by their doctor. VUMC is a comprehensive health care facility dedicated to patient care, research, and the education of health care professionals. Translational research into the causes and treatment of disease as well as studying fundamental biological properties is the primary focus of discovery at Vanderbilt. Clinical research is conducted in Vanderbilt University Hospital, the Nashville Veterans Administration Hospital, Meharry General Hospital and in their associated outpatient clinics. These hospitals and clinics, all associated with the Vanderbilt system, each have full time Vanderbilt faculty and medical housestaff and provide clinical care and participate in research programs. The Vanderbilt Clinic is comprised of more than 95 adult outpatient specialty practices and received over 1.5 million ambulatory visits in 2012-13. The Vanderbilt Heart and Vascular Institute offers a comprehensive heart program offering diagnosis, medical treatment, minimally invasive therapies, surgical intervention and disease management, tailored to each individual&#39;s unique needs. All programs within the Vanderbilt Clinic have survival figures that surpass the national average.

  Study phs000906