ImmPort — short for the Immunology Database and Analysis Portal — is a long-term public data repository and analysis platform for immunology research, funded by the National Institute of Allergy and Infectious Diseases’ (NIAID) Division of Allergy, Immunology, and Transplantation (DAIT). It exists to give NIAID-funded immunology investigators a place to deposit, share, and reuse study data, and to give the rest of the field an integrated warehouse of experimental and clinical immunology data rather than results scattered across individual labs’ local files. For a research administrator or investigator writing a data management plan that touches human or animal immunology data, ImmPort is usually the first repository option to evaluate.
What ImmPort is, and who runs it
ImmPort is operated as a NIAID/DAIT-funded resource and has served the immunology research community for two decades, hosting data mainly from studies funded through NIAID/DAIT. Its core is a data warehouse that integrates two kinds of immunology data that are usually kept apart elsewhere: mechanistic assay data (the laboratory measurements) and clinical study data (the subject-level context those measurements were collected under). ImmPort is registered as a repository with re3data.org and has gone through CoreTrustSeal certification review, the framework research-data repositories use to document long-term trustworthiness and sustainability practices — relevant context for anyone whose funder or DMS Plan asks about a named repository’s sustainability commitments.
ImmPort is more than passive storage. It also functions as an analysis platform: registered users can use built-in visualization tools to explore a study’s demographics and assay results interactively, and ImmPort Galaxy, ImmPort’s data-analysis application, provides a graphical interface to open-source analysis pipelines for conventional and mass cytometry data. That combination — deposit, integrate, and analyze in the same system — is part of what distinguishes ImmPort from a repository that only accepts and serves static files.
What data types ImmPort hosts
ImmPort’s scope is immunology and infectious-disease research broadly, not one narrow assay type. Reported data categories include:
- Subject-level clinical data — medical history, concomitant medications, and adverse events collected as part of a clinical study.
- Mechanistic assay data — results from immunology laboratory assays such as flow cytometry, ELISA, and ELISPOT, along with other cellular and molecular immune-response measurements.
- Study-level metadata — the experimental design, protocols, and sample annotation needed to interpret the assay and clinical data together, rather than as disconnected files.
NIAID has described ImmPort as holding data from more than 1,000 immunological studies spanning well over 100 disease areas and dozens of distinct assay/data types. Because that kind of count changes as new studies are deposited, treat any specific figure as a snapshot rather than a fixed number, and check immport.org directly for current holdings before citing a number in your own writing.
ImmPort and the Human Immunology Project Consortium (HIPC)
ImmPort is the designated central data repository for the Human Immunology Project Consortium (HIPC), a NIAID/DAIT program that funds multiple research centers to study well-characterized human cohorts using a shared set of modern immune-profiling methods — multiplex transcriptional, cytokine, and proteomic assays, multiparameter immune-cell phenotyping, and computational immunology methods. HIPC was established in 2010 and renewed in 2015. A HIPC-specific data standards working group defines the metadata fields, assay-result formats, and controlled vocabularies HIPC centers use when submitting results, and most of those standards are built directly into ImmPort’s own data-deposition templates — which is why HIPC data in ImmPort is comparatively consistent and reusable across studies, compared with immunology data deposited without a shared submission standard behind it.
A separate, related platform, ImmuneSpace, provides additional analysis and visualization tools purpose-built for HIPC’s systems-vaccinology datasets, drawing on data that also lives in ImmPort. The two are complementary: ImmPort is the archival repository of record, and ImmuneSpace is an HIPC-oriented analysis layer on top of a subset of that data.
ImmPort’s role in immunology data-sharing compliance
For an investigator or administrator working out where immunology data belongs in an NIH Data Management and Sharing (DMS) Plan, ImmPort sits in the same position GEO occupies for gene-expression data or dbGaP occupies for genotype-phenotype data: it is a discipline-specific repository for a defined data domain, funded and governed by the NIH institute most responsible for that domain (NIAID). NIH’s own repository-selection guidance places a suitable discipline-specific repository ahead of a generalist repository when one exists for the data type — and for immunology assay and clinical study data funded through NIAID/DAIT programs, ImmPort is generally that discipline-specific option, particularly for data collected under HIPC and related DAIT-funded initiatives.
Individual NIAID funding opportunity announcements and program requirements — not a single blanket NIH-wide mandate — are what actually specify whether a given award requires ImmPort deposit; HIPC awards, for example, build ImmPort submission into the program’s data-sharing expectations. Anyone drafting a DMS Plan under a NIAID/DAIT award should check the specific funding announcement and their program officer’s guidance rather than assume ImmPort deposit is either universally required or optional across all NIAID immunology funding.
How ImmPort fits alongside other NIH domain repositories
ImmPort is one of several NIH-affiliated domain repositories CASRAI covers, each scoped to a specific data type and each sitting ahead of generalist options in NIH’s repository-selection hierarchy for its respective domain:
- ImmPort — immunology assay results and associated clinical study data, funded by NIAID/DAIT.
- Gene Expression Omnibus (GEO) — gene-expression and other functional genomics data (microarray, RNA-seq), operated by NCBI/NLM, built around the MIAME/MINSEQE minimum-information standards.
- dbGaP — controlled-access genotype-phenotype data from human genetic studies, also operated by NCBI/NLM.
Where no NIH-designated or discipline-specific repository exists for a dataset, NIH points investigators toward the seven repositories coordinated under GREI, NIH’s Generalist Repository Ecosystem Initiative (Dataverse, Dryad, Figshare, Mendeley Data, OSF, Vivli, and Zenodo). ImmPort, GEO, and dbGaP sit ahead of any GREI-member repository in that hierarchy for their respective data types — a DMS Plan covering immunology assay or clinical data funded through NIAID/DAIT should generally name ImmPort rather than default to a generalist repository, in the same way a gene-expression study should generally name GEO. See CASRAI’s guide to research repositories versus archives for the broader vocabulary this hierarchy relies on.
Practical considerations for citing or depositing in ImmPort
- Confirm domain fit first. ImmPort is scoped to immunology and infectious-disease research data; it is not a general-purpose repository for unrelated data types generated in the same study (for example, genomic sequence data belongs in GEO or dbGaP, not ImmPort, even within an immunology-focused project).
- Check the specific funding announcement. Whether ImmPort deposit is required, and on what timeline, depends on the NIAID program or funding opportunity, not a single universal NIH rule.
- Use ImmPort’s deposition templates. For HIPC-affiliated studies in particular, ImmPort’s data-deposition templates already build in the HIPC data-standards working group’s metadata and controlled-vocabulary requirements, which reduces rework at submission time.
- Cite the accession correctly. As with any repository named in a data availability statement, confirm the exact study/accession identifier ImmPort assigns and cite that identifier, not just “data available in ImmPort,” so a reader or reviewer can locate the specific dataset. See CASRAI’s guide to writing a data availability statement for the general mechanics.
- Registration is required for some tools. Public browsing of ImmPort’s shared data does not require an account, but its analysis tools (including ImmPort Galaxy) require registration, and some data-submission and private workspace features require DAIT approval.
Frequently asked questions
What does ImmPort stand for?
ImmPort stands for the Immunology Database and Analysis Portal. It is funded by NIAID’s Division of Allergy, Immunology, and Transplantation (DAIT).
Is ImmPort only for NIAID-funded researchers?
ImmPort hosts data mainly from NIAID/DAIT-funded studies, but its shared data is publicly accessible for reuse by any researcher, not restricted to NIAID grantees. Depositing new data, however, is generally tied to NIAID/DAIT-funded programs.
Is ImmPort required for NIH Data Management and Sharing Plans?
There is no single NIH-wide mandate naming ImmPort for all immunology data. Whether a specific award requires ImmPort deposit depends on the NIAID funding opportunity and program requirements — HIPC awards, for example, build it in directly. Where no more specific requirement applies, ImmPort is still the discipline-specific repository NIH’s own repository-selection guidance points toward for immunology assay and clinical study data, ahead of a generalist GREI-member repository.
What is the difference between ImmPort and ImmuneSpace?
ImmPort is the archival data repository; ImmuneSpace is a separate, complementary analysis and visualization platform built specifically for HIPC systems-vaccinology datasets, drawing on data that also resides in ImmPort.
How does ImmPort compare to GEO or dbGaP?
All three are NIH-affiliated, discipline-specific repositories, but for different data domains: ImmPort for immunology assay and clinical study data (NIAID/DAIT), GEO for gene-expression and functional genomics data (NCBI/NLM), and dbGaP for controlled-access genotype-phenotype data (also NCBI/NLM). A single immunology study that also generates sequencing data may need to deposit in more than one of these repositories.
