Frequently asked questions
For research teams and governance officers.
Does Foundry120 store identifiable participant data?
No. Foundry120 holds pseudonymised research data only. Direct identifiers must not be uploaded.
What is Helix?
Helix is the AI assistant in Foundry120. You ask a question in plain English over the samples, datasets, and documents your account is approved to use.
Where is data stored, and where does Helix run?
Core platform data is stored in the University of Glasgow’s Microsoft Azure environment in the UK South region. Helix inference runs in Microsoft Azure regions in the EU.
Could it run in our own environment?
We consider this case by case, for suitable collaborations where the arrangement and costing fit. Discuss it with the team.
Are research data used to train AI models?
No. Research data processed through Helix is not used to train external foundation models.
Who owns the data, and can we get it out?
Your team keeps full ownership of its samples and datasets. Sample and study-tracking records export as CSV at any time, and dataset files can be downloaded. Nothing locks your data inside the platform.
Is Foundry120 a clinical system?
No. It is a translational research platform. It is not a medical device, and Helix outputs must not be used for clinical care.
Does Helix make autonomous decisions?
No. Helix is computational assistance. Researchers review its outputs. It does not replace scientific, statistical, or governance judgement.
Who approves user access?
Study admins and lab leads approve access within their own study or lab group. They cannot grant access outside that group.
Does using Foundry120 need a REC amendment or reconsent?
Not automatically. Computational analysis of pseudonymised research data often already fits existing approvals. Extra review may be needed for new secondary uses or cross-study pooling. The adopting team, sponsor, and institution decide.
How does a team start?
Write to shaun.chuah@glasgow.ac.uk. We discuss the study, the data, and the users. Your team checks protocol, consent, REC approval, and local policy. Onboarding is hands-on: bringing existing sample inventories and datasets in is work we do together. We then set up the workspace, add users, and onboard the first datasets.
The resources page has the Platform Reference Guide, the user agreement, and the platform user privacy notice.
Interested in using Foundry120, or exploring a research collaboration?
We’d be glad to hear from research groups and institutions exploring the platform, or holding data that has outgrown spreadsheets and shared drives.
Request a platform walkthrough →