GW-FEAST: Difference between revisions

From HIVE Lab
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
(6 intermediate revisions by the same user not shown)
Line 13: Line 13:
     <div style="flex: 1; margin: 5px; min-width: 210px; border: 1px solid #CCC; padding: 0 10px 10px 10px; box-shadow: 0 2px 2px rgba(0,0,0,0.1); background: #f5faff;">
     <div style="flex: 1; margin: 5px; min-width: 210px; border: 1px solid #CCC; padding: 0 10px 10px 10px; box-shadow: 0 2px 2px rgba(0,0,0,0.1); background: #f5faff;">
         <h2>About GW-FEAST</h2>
         <h2>About GW-FEAST</h2>
Federated Ecosystems for Analytics and Standardized Technologies ([https://hivelab.biochemistry.gwu.edu/gw-feast FEAST]) is a cloud-based, agile bioinformatics and data analysis platform under development through the ARPA-H Biomedical Data Fabric (BDF) toolbox program. The project is led by [https://dnahive.com DNA-HIVE] and other funded collaborators include Cornell University, Vanderbilt University, Georgetown University, European Bioinformatic Institute, and Kaiser Permanente. Our team is responsible for the GW instance of FEAST (GW-FEAST) and for co-leading the project with DNA-HIVE. This project is part of the ARPA-H FEAST performer team initiative to create bridges across data silos and make health data more accessible and usable.  
Federated Ecosystems for Analytics and Standardized Technologies ([https://hivelab.biochemistry.gwu.edu/gw-feast FEAST]) is a cloud-based, agile bioinformatics and data analysis platform under development through the ARPA-H Biomedical Data Fabric (BDF) toolbox program. The project is led by [https://dnahive.com DNA-HIVE] and other funded collaborators include Cornell University, Vanderbilt University, Georgetown University, European Bioinformatics Institute, and Kaiser Permanente. Our team is responsible for the GW instance of FEAST (GW-FEAST) and for co-leading the project with DNA-HIVE. This project is part of the ARPA-H FEAST performer team initiative to create bridges across data silos and make health data more accessible and usable.  


Several hospitals and cancer centers will have a FEAST platform, which enables cross-site data analysis without the need to export or transform the data. Currently, large chunks of data are used by insurance companies, pharmaceutical companies, and others for research and development purposes. The FEAST platform, which is particularly strong with noisy, real-world data, aims to enable more precise data selection for research use while preserving patient privacy. When clinical data is submitted to the suite of tools, submission is handled via the HL7 FHIR protocol, ensuring only authorized parties ever have access to protected data. Models that provide update mechanisms such as online training will be updated appropriately without retaining any personally identifiable information (PII). Thus, these tools support federated data sets and training without ever retaining clinical PII within the system. All services are treated as independent microservices through containerization within docker containers.  
Several hospitals and cancer centers will have a FEAST platform, which enables cross-site data analysis without the need to export or transform the data. Currently, large chunks of data are used by insurance companies, pharmaceutical companies, and others for research and development purposes. The FEAST platform, which is particularly strong with noisy, real-world data, aims to enable more precise data selection for research use while preserving patient privacy. When clinical data is submitted to the suite of tools, submission is handled via the HL7 FHIR protocol, ensuring only authorized parties ever have access to protected data. Models that provide update mechanisms such as online training will be updated appropriately without retaining any personally identifiable information (PII). Thus, these tools support federated data sets and training without ever retaining clinical PII within the system. All services are treated as independent microservices through containerization within docker containers.  
Line 27: Line 27:
* [[GW-FEAST Data|GW-FEAST Data Sources]]
* [[GW-FEAST Data|GW-FEAST Data Sources]]
* [[GW-FEAST Data Access Portal]]
* [[GW-FEAST Data Access Portal]]
* [[GW-FEAST BCOs]]
* [[GW-FEAST Data De-identification|GW-FEAST De-identification]]
* [[GW-FEAST De-identified Data Templates]]
</div>
</div>
     </div>
     </div>
Line 34: Line 33:
<div id="ggw_row3" style="display: flex; flex-flow: row wrap; justify-content: space-between; padding: 0; margin: 0 -5px 0 -5px;">
<div id="ggw_row3" style="display: flex; flex-flow: row wrap; justify-content: space-between; padding: 0; margin: 0 -5px 0 -5px;">
     <div style="flex: 1; margin: 5px; min-width: 210px; border: 1px solid #CCC; padding: 0 10px 10px 10px; box-shadow: 0 2px 2px rgba(0,0,0,0.1); background: #f5faff;">
     <div style="flex: 1; margin: 5px; min-width: 210px; border: 1px solid #CCC; padding: 0 10px 10px 10px; box-shadow: 0 2px 2px rgba(0,0,0,0.1); background: #f5faff;">
         <h2>GW-FEAST Project Architecture</h2>
         <h2>GW-FEAST Project Architecture</h2>[[File:GW-FEAST_architecture.png|none|thumb|658x658px]]


[[File:GW-FEAST_architecture.png|frameless|1136x1136px]]
''The GW-FEAST architecture diagram showcases the GW environment set up to facilitate FEAST queries through the GW node (or instance of FEAST at GW). While other consortium sites may have slightly different environment configurations, the overall structure and security practices will be similar across all sites. This diagram is subject to change throughout the life of the project.''
 
''This figure illustrates the GW-FEAST project architecture and is subject to change throughout the life of the project.''
</div>
</div>
     </div>
     </div>

Revision as of 16:28, 26 March 2025


Welcome to GW-FEAST Wiki!
This is the MediaWiki for the GW-FEAST project.

About GW-FEAST

Federated Ecosystems for Analytics and Standardized Technologies (FEAST) is a cloud-based, agile bioinformatics and data analysis platform under development through the ARPA-H Biomedical Data Fabric (BDF) toolbox program. The project is led by DNA-HIVE and other funded collaborators include Cornell University, Vanderbilt University, Georgetown University, European Bioinformatics Institute, and Kaiser Permanente. Our team is responsible for the GW instance of FEAST (GW-FEAST) and for co-leading the project with DNA-HIVE. This project is part of the ARPA-H FEAST performer team initiative to create bridges across data silos and make health data more accessible and usable.

Several hospitals and cancer centers will have a FEAST platform, which enables cross-site data analysis without the need to export or transform the data. Currently, large chunks of data are used by insurance companies, pharmaceutical companies, and others for research and development purposes. The FEAST platform, which is particularly strong with noisy, real-world data, aims to enable more precise data selection for research use while preserving patient privacy. When clinical data is submitted to the suite of tools, submission is handled via the HL7 FHIR protocol, ensuring only authorized parties ever have access to protected data. Models that provide update mechanisms such as online training will be updated appropriately without retaining any personally identifiable information (PII). Thus, these tools support federated data sets and training without ever retaining clinical PII within the system. All services are treated as independent microservices through containerization within docker containers.

FEAST Video

GW-FEAST Project Architecture

The GW-FEAST architecture diagram showcases the GW environment set up to facilitate FEAST queries through the GW node (or instance of FEAST at GW). While other consortium sites may have slightly different environment configurations, the overall structure and security practices will be similar across all sites. This diagram is subject to change throughout the life of the project.