6257 results for "fc 26 ultimate team coins buy Buyfc26coins.com is FC 26 coins official site..E4Pd"

in 10.92 milliseconds.

• The Gene Partnership (TGP) - eMERGE Data

  The Gene Partnership (TGP) is a prospective longitudinal registry at Boston Children's Hospital (BCH) to study the genetic and environmental contributions to childhood health and disease, collect genetic information on a large number of children who have been phenotyped, and implement the Informed Cohort and the Informed Cohort Oversight Board (ICOB). The term "The Gene Partnership" reflects a partnership between researchers and participants. Children seen at BCH are offered enrollment, as are their parents and siblings. DNA is collected on all enrollees. BCH has a comprehensive EMR system, and virtually all inpatient and outpatient data are captured electronically. Clinical data in the BCH EMR is loaded in the i2b2 data warehouse which is available to investigators. Cases, phenotypes, and covariates are ascertained using the i2b2 database. Participants at BCH in TGP have consented to receive any research result and/or incidental finding that arises from studies using TGP that is approved by the Informed Cohort Oversight Board (ICOB) and is in accordance with the participants' preferences; results are returned through the Personally Controlled Health Record (PCHR). BCH and Cincinnati Children's Hospital Medical Center (CCHMC) have partnered as the Pediatric Alliance for Genomic and Electronic Medical Record (EMR) Research (PAGER) site for the eMERGE Phase II network for pediatric institutions, and the cohort for eMERGE at BCH is TGP.

  Study phs000495

• Developmental Mechanisms of Human Congenital Heart Disease in Subjects with 22q11.2 Deletion Syndrome (DiGeorge Syndrome/Velocardiofacial Syndrome)

  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.

  Study phs001339

• What is a DAC?

  What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions.  You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks.  Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, the EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

  Documentation access/data-access-committee/what-is-dac

• NIH RECOVER-Pediatric: Understanding the Long-Term Impact of COVID on Children and Families

  The NIH Researching COVID to Enhance Recovery (RECOVER) initiative comprises a set of three combined retrospective and prospective, longitudinal and observational meta-cohort studies with nested case-control studies designed to define and characterize the epidemiology, natural history, clinical spectrum, and underlying mechanisms of post-acute effects of SARS-CoV-2 infection (PASC or Post-COVID syndrome) in a diverse study population representative of the general COVID-19 population in the US. Enrolled patients, with and without known SARS-CoV-2 infection, will be observed for clinical signs and symptoms of PASC and will be assessed for risk and resiliency factors and potential mediating factors associated with the severity and progression of PASC. The objective of the RECOVER initiative is to enhance knowledge of recovery from SARS-CoV-2 infections in order to support development of novel diagnostic and therapeutic interventions. Overarching scientific objectives are as follows:Characterize the incidence and prevalence of sequelae of SARS-CoV-2 infection.Characterize the spectrum of clinical symptoms, subclinical organ dysfunction, natural history, and distinct phenotypes identified as sequelae of SARS-CoV-2 infection. Define the biological mechanisms underlying pathogenesis of the sequelae of SARS-CoV-2 infection. The RECOVER observational studies comprise three cohorts across the lifespan (adult, pediatric, and tissue pathology (autopsy)). The data collection and data analysis plans for each cohort have been harmonized to use common data elements where feasible. Brief descriptions of each cohort are provided in the following paragraphs: 1) NIH RECOVER: A Multi-site Observational Study of Post-Acute Sequelae of SARS-CoV-2 Infection in Adults (see phs003463)The RECOVER adult cohort study is a combined retrospective and prospective, longitudinal, observational meta-cohort of individuals who will enter the cohort with and without SARS-CoV-2 infection and at varying stages before and after infection. Individuals with and without SARS-CoV-2 infection, and with or without PASC symptoms, will be followed to identify risk factors and occurrence of PASC. This study will be conducted in the United States and subjects will be recruited through inpatient, outpatient, and community-based settings. Study data including age, demographics, social determinants of health, medical history, vaccination history, details of acute SARS-CoV-2 infection, overall health and physical function, and PASC symptom screen will be reported by subjects or collected from the electronic health record using a case report form at specified intervals. Biologic specimens will be collected at specified intervals, with some tests performed in local clinical laboratories and others performed by centralized research centers or banked in the Biospecimen Repository. Advanced clinical examinations and radiologic examinations will be performed at local study sites with cross-site standardization. 2) A Multi-Center Observational Study: The RECOVER Post Acute Sequelae of SARS-CoV-2 (PASC) Pediatric Cohort Study (this study)The RECOVER pediatric study is a combined retrospective and prospective, longitudinal, observational meta-cohort of individuals ages newborn-25 years who will enter the cohort with and without SARS-CoV-2 infection at varying stages before and after infection. Individuals with and without SARS-CoV-2 infection and with or without PASC symptoms will be followed to identify risk factors and occurrence of PASC. This study recruit participants inpatient, outpatient, and community-based settings in the United States. Study data including age, demographics, social determinants of health, medical history, vaccination history, details of acute SARS-CoV-2 infection, overall health and physical function, and PASC symptoms will be reported by participants or collected from the electronic health record using a case report form at specified intervals. Biologic specimens will be collected at specified intervals, with some tests performed in local clinical laboratories and others performed by centralized research centers or banked in the Biospecimen Repository. Advanced clinical and radiologic examinations will be performed at local study sites with cross-site standardization. 3) NIH RECOVER: A Multi-site Pathology Study of Post-Acute Sequelae of SARS-CoV-2 Infection The RECOVER tissue pathology study is a cross-sectional study designed to define and characterize the epidemiology, natural history, clinical spectrum, and underlying mechanisms of post-acute effects of SARS-CoV-2 infection in a diverse population representative of the general COVID-19 population in the US. The autopsy study will characterize the pathology of PASC in (i) non-hospitalized patients who die 30 days or later from symptom onset of COVID-19, and (ii) hospitalized patients who die 30 days or later after discharge from a hospitalization for COVID-19. The study will include decedents who had previously fully recovered from SARS-CoV-2 infection (i.e., >30 days from onset in non-hospitalized, or >30 days from discharge in hospitalized patients), and decedents who meet clinical criteria of PASC as defined by the recent World Health Organization publication (see Section 5.4 below). The autopsy study will also explore the pathology of acute SARS-CoV-2 infection in a smaller subset of patients who died 15-30 days from symptom onset. This protocol defines the common set of clinical data elements, autopsy procedures for tissue collection, core measures, pathology protocols, shared pathology tissues, data elements, and methodology. Each investigator site is expected to perform autopsies on the decedents to address the pathophysiology of the potential long-term effects of SARS-CoV-2 infection on human health. The Consortium analysis plan aims to address research questions by incorporating: 1) tissue obtained from autopsies performed at each Phase II participant's site; and 2) tissue available from other pathology investigators/autopsy sites within the Consortium.

  Study phs003461

• Nasal MicroRNA during Bronchiolitis and Age 6y Asthma: MARC-35 Cohort

  We analyzed data from the 35th Multicenter Airway Research Collaboration (MARC-35) study to examine the relationship between nasal airway microRNAs (miRNAs) and the risk of developing childhood asthma. MARC-35 is a multicenter prospective cohort study which enrolled infants (age Structured interviews of the parents/guardians were performed by site investigators and clinical details were collected via emergency department and hospital inpatient chart reviews. Following the index hospitalization, trained study personnel conducted telephone interviews with parents/legal guardians at six-month intervals. Participants also underwent nasal swab sampling conducted by trained site personnel during the index bronchiolitis hospitalization and during an in-person follow-up examination at about age 6 years. Total RNA was extracted from nasal swab specimens using Trizol LS reagent (ThermoFisher Scientific, Waltham, MA) and the Direct-zol RNA Miniprep Kit (Zymo Research, Irvine, CA). Small RNA-seq was performed using the PerkinElmer NEXTFLEX&#174; small RNA-seq v3 kit with Unique Dual Indexes (PerkinElmer, Waltham, MA) and sequenced on an Illumina NovaSeq6000 sequencer using an S2 50bp PE Flowcell (Illumina, San Diego, CA). Through dbGaP, limited de-identified phenotypic data (e.g., demographics) and RNA-seq FASTQ files will be made available. Among a cohort of infants hospitalized with bronchiolitis, we applied a small RNA sequencing approach and found miRNAs were associated with asthma risk factors, and highly expressed in lung tissue and immune cells (e.g., TH cells, neutrophils). They also played key roles in mechanisms relating to asthma, such as innate immunity, airway remodeling, and IgE regulation.

  Study phs003564

• Whole Exome and Target Sequencing Data in 75 Samples from 5 Hepatocellular Carcinoma Patients.

  Whole Exome and Target Sequencing Data in 75 Samples from 5 Hepatocellular Carcinoma Patients. The sequencing was performed by Illumina HiSeq 4000. Background and aims: Intratumoral heterogeneity (ITH) challenges identifying mutations with target therapy potential whereas circulating cell-free DNAs (cfDNAs) could reflect nearly the entire mutation spectrum in given tumors. We investigated how to minimize the limit of ITH for profiling hepatocellular carcinoma (HCC).Methods: Thirty-two multi-regional HCC samples from five patients were subjected to whole exome sequencing (WES) and targeted deep sequencing (TDS). ITH extent was measured by the average percentage of non-ubiquitous mutations (present in parts of tumor regions). Matched cfDNAs were also analyzed by WES and TDS. Profiling efficiencies of single tumor specimen and cfDNA were compared and the one better depicted mutational landscape was selected to screen therapeutic targets.Results: We found variable extents of ITH in HCCs and observed branched and parallel evolution patterns. ITH level decreased at higher sequencing depth of TDS than that measured by WES (28.1% vs 34.9%, P &lt; 0.01) but it remained unchanged upon additional samples analyzed. TDS of single tumor specimen detected an average of 70% the total mutations in HCC. Although more mutations were detected in cfDNA under TDS than WES, an average of 47.2% total HCC mutations uncovered by cfDNA suggested tissue outperform cfDNA and the latter may serve as alternative in profiling HCC genome. Consequently, TDS of single tumor tissue in 66 patients and cfDNAs in four unresectable HCCs identified 38.6% (26/66 and 1/4) patients bearing therapeutic targets.Conclusions: TDS of single tumor specimen could largely circumvent ITH to uncover mutations indicative of target therapy in HCC.

  Dataset EGAD00001003278

• Childhood Cancer Model Atlas

  we establish a single-site collection of 243 cell lines, including 207 paediatric cancer cell lines representing 14 distinct extracranial and brain childhood tumour types. We subjected 164 paediatric cancer cell lines to multi-omic analyses across three dimensions (DNA-sequencing, RNA-sequencing, DNA methylation) to classify them based on clinically relevant molecular subtypes.

  Study EGAS00001006320

• Genetic Discovery and Application in a Clinical Setting: Continuing a Partnership (eMERGE Phase II)

  The electronic Medical Records and Genomics (eMERGE) Network is a consortium of ten participating sites funded by the NHGRI to investigate the use of electronic medical record systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 19,000 individuals using EMR-derived phenotypes and DNA from linked Biorepositories. The eMERGE Network brings together researchers with a wide range of expertise in genomics, statistics, ethics, informatics, and clinical medicine from leading medical research institutions across the country. Each center participating in the consortium is uniquely situated to provide critical resources to this highly collaborative and productive network. Each site combines a biobank or study cohort with extensive genomic data and access to clinical data derived from electronic medical records. Sites are geographically dispersed and have diverse patient populations, including two sites focusing specifically on pediatrics. The eMERGE Network is comprised of 9 sites and one coordinating center. Each site maintains its own biorepository where DNA specimens are linked to phenotypic data contained within EMRs. Children&#39;s Hospital of Pennsylvania, PI: Hakon Hakonarson, MD, PhD Cincinnati Children&#39;s Medical Center with Boston Children&#39;s Hospital, PI: John Harley, MD, PhD - CCHMC and Ingrid Holm, MD, MPH - BCH Geisinger Health System, PI: David Carey, PhD and Marc Williams, MD Group Health Cooperative with University of Washington, PI: Eric Larson, MD, MPH - GHC and Gail Jarvik, MD, PhD - UW Marshfield Clinic with Essentia Institute of Rural Health, PI: Catherine McCarty, PhD, MPH - Essentia and Murray Brilliant, PhD - Marshfield Mayo Clinic, PI: Christopher Chute, MD, DrPH and Iftikhar Kullo, MD Icahn School of Medicine at Mount Sinai, PI: Erwin Bottinger, MD Northwestern University, PI: Rex Chisholm, PhD and Maureen Smith, MS Vanderbilt University, PI: Dan Roden, MD eMERGE Coordinating Center - Vanderbilt University, PI: Paul Harris, PhD Using electronic phenotyping methods, the consortium used DNA samples from all participating sites to explore the genetic determinants of red cell indices, white blood count (WBC) differential, diabetic retinopathy, height, serum lipid levels, specifically total cholesterol, HDL (high density lipoprotein), LDL (low density lipoprotein), and triglycerides, and autoimmune hypothyroidism as well as using the phenome-wide association study (PheWAS) paradigm to replicate and discover relationships between targeted genotypes with multiple phenotypes.

  Study phs000948

• Center for Common Disease Genomics [CCDG] - Cardiovascular ATVB: Atherosclerosis Thrombosis and Vascular Biology

  Italian Atherosclerosis Thrombosis and Vascular Biology study is a prospective, nationwide, case-control study involving 125 coronary care units in Italy. The cases were patients who were hospitalised for a first MI before the age of 45 years and underwent coronary angiography. Acute MI was defined as resting chest pain lasting more than 30 minutes, accompanied by persistent electrocardiographic changes, and confirmed by an increase in total creatine kinase or in the MB fraction to more than twice the upper normal limits. The controls were healthy subjects without a history of thromboembolic disease who were unrelated to the patients, but individually matched with them by age, gender and geographical origin. They were enrolled from among the blood donors or staff of the same participating hospitals. Recruitment of cases and controls took place between 1994 and 2007. This site hosts data from ~60 whole exomes.

  Study phs001592

• Childhood Cancer Data Initiative (CCDI): Pediatric In Vivo Testing Program - Neuroblastoma

  The goal of NCI's Pediatric In Vivo Testing Consortium (PIVOT) is to advance the development of effective treatments for pediatric cancers through preclinical in vivo testing of novel therapeutic agents. To design impactful experiments that can be rapidly translated to the clinic, PIVOT investigators require comprehensive genomic characterization of the patient-derived xenograft (PDX) models used across the consortium. This robust experimental design enhances collaboration with industry partners by providing proof-of-concept data for drugs in development. As part of this effort, neuroblastoma PDX models are being molecularly characterized to identify promising therapeutic candidates. The molecular profiling includes whole exome sequencing (WES), RNA-seq, MethylEPIC array, CytoSNP array, and DNA fingerprinting for quality control. Additionally, demographic and clinical data (e.g., diagnosis, disease site, disease status) are shared. These characterized PDX models, matched with patient tumors, guide model selection for preclinical drug testing.

  Study phs003163