The H3Africa Data and Biospecimen Access Committee (DBAC) is the governance body that decides who may access the human genomic data and biospecimens generated by the H3Africa Consortium — Africa’s largest coordinated program of human genomic research. Because most of these samples and datasets were collected under broad consent from participants across dozens of African countries, and the researchers who originally collected them typically no longer retain oversight once a sample or dataset moves into shared repositories, H3Africa built a standing committee to make continuing access decisions on participants’ behalf rather than leaving that judgment to individual data custodians. This guide explains what the DBAC is, how it decides requests, what conditions it attaches to access, and how it fits alongside other international genomic-data governance frameworks a research administrator may already know.
What Is H3Africa?
Human Heredity and Health in Africa (H3Africa) is a research consortium launched in 2010 to build African-led capacity for genomic and heredity-related research into common diseases, using funding and technical resources contributed jointly by African and international investigators. It is primarily funded by the US National Institutes of Health (NIH) Common Fund and the UK’s Wellcome Trust, and it has established biorepositories and genomic data infrastructure at institutions across the continent, including hubs in Nigeria, Uganda, and South Africa. A companion initiative, H3ABioNet, is the pan-African bioinformatics network responsible for building local capacity to analyze and manage this data rather than routing it exclusively through infrastructure outside Africa.
Why a Dedicated Access Committee, Rather Than Ordinary Data Sharing Agreements?
Large biobanking and genomics consortia elsewhere often rely on a combination of institutional data use agreements (DUAs) and funder-level policy — for example, the NIH Genomic Data Sharing (GDS) Policy in the United States. H3Africa layered a purpose-built committee on top of that kind of instrument for a specific reason: most H3Africa biospecimens and datasets were collected under broad consent, where a participant agrees, at the time of collection, to future research uses that are not yet fully specified. Broad consent shifts real ongoing responsibility onto whoever authorizes each subsequent use, rather than resolving it once at the point of collection — a governance gap the DBAC was created to fill. The Committee has published its own account of that role: a 2025 paper by DBAC-affiliated researchers describes it as “a pioneering access committee in Africa” tasked with the “responsible governance of genomics data and biospecimens in the context of broad consent,” reviewing whether each proposed use is actually consistent with what participants originally agreed to, not simply whether a requester has a valid credential.
How the DBAC Is Structured
Per the H3Africa Data and Biospecimen Access Committee Guidelines, the DBAC is a semi-autonomous body with independent decision-making authority over access requests — it is not merely an advisory panel to the individual studies that contributed samples. Its published composition combines nine voting members, selected for expertise spanning research relevant to H3Africa’s scientific scope, biorepository operations, data and bioinformatics, African research ethics, and African legal matters, with four ex officio members. A secretariat maintains records of every researcher granted access to Consortium biospecimens and datasets, giving H3Africa continuing programmatic oversight of how previously collected material is actually used — the record-keeping layer that makes downstream accountability possible once broad consent has been exercised.
The Access Request Process
The DBAC accepts Data and Biospecimen Access Request applications on a rolling basis, with the Committee committing to act within 60 days of receiving a complete application. In practice, the process requires:
- Eligible applicant. Only Senior Scientists or Principal Investigators may submit a request — not students or unaffiliated researchers directly.
- A defined research proposal. The application must describe the proposed research question and methodology, and demonstrate alignment with H3Africa’s objectives.
- Evidence of funding and local ethics approval. Applicants must show secured funding and documented institutional ethics review before the DBAC will evaluate a request.
- Consistency with the original consent. The Committee checks that the proposed use is compatible with the informed consent under which each specific dataset or biospecimen was originally collected, plus any additional limitations the submitting H3Africa investigators attached to that study.
- A benefit and disposition plan. Applicants must show anticipated benefit to African research and health, and state what will happen to any unused biospecimen material — disposal or transfer — once the approved research concludes.
- A data-return commitment. Successful applicants commit to returning any newly generated data to H3ABioNet or the European Genome-phenome Archive (EGA), so that derivative data flows back into shared African-governed or internationally archived infrastructure rather than dead-ending in a single external lab.
Conditions Attached to a Grant of Access
Even after approval, DBAC access comes with conditions that distinguish it from an unrestricted open-data download:
- Priority for African-based or African-collaborating research. Researchers based on the African continent, or collaborating directly with African scientists, receive priority access to samples and data over external requests that lack that connection.
- An embargo period. A defined embargo protects the publication rights of the researchers who originally generated the data or collected the specimens, before it becomes available more broadly for secondary use.
- A prohibition on commercializing the biospecimens themselves. Requesters may conduct approved research using the material, but the DBAC guidelines explicitly bar commercialization of the biospecimens as such.
How the DBAC Fits Alongside GA4GH, CARE, and Broad Consent Standards
Research administrators who already work with the Global Alliance for Genomics and Health (GA4GH) — the body behind widely used international frameworks for responsible genomic data sharing, including its Data Use Ontology and consent-coding standards — should read the DBAC as a regional, participant-and-community-embedded governance layer that operates alongside those global technical standards, not a replacement for them. GA4GH’s frameworks are largely about making consent and use conditions machine-readable and interoperable across jurisdictions; the DBAC’s role is the human governance decision underneath that layer — evaluating, for African-collected samples specifically, whether a given proposed use is actually consistent with participants’ broad consent and with the interests of the communities and institutions that contributed them. That framing overlaps conceptually with the CARE Principles for Indigenous Data Governance (Collective Benefit, Authority to Control, Responsibility, and Ethics) even though H3Africa’s own guidelines are not written as a CARE implementation — both frameworks share the underlying premise that governance of sensitive data about a community must account for that community’s collective interest, not just the individual consent of each participant. See CASRAI’s guide on broad consent under 45 CFR 46.116(d) for how the concept of broad consent is defined and regulated in the US human-subjects context, and the CARE Principles vs. FAIR Principles comparison for how Indigenous and community data-governance frameworks relate to open-data principles more broadly.
What This Means for Research Administrators Outside Africa
An institution collaborating with an H3Africa-affiliated site, or seeking secondary access to H3Africa-generated data, should expect the DBAC process to function similarly to — but not identically with — the material transfer and data governance instruments already familiar from other contexts. It still requires the institutional building blocks research administrators manage routinely: documented local IRB/ethics approval, a material transfer agreement (MTA) where physical biospecimens are involved (see CASRAI’s guide to the MTA process), and a data sharing agreement or DUA governing any data received. What differs is the additional layer of committee-level consent-consistency review, the priority given to African and African-collaborating researchers, and the explicit no-commercialization and data-return conditions — none of which are typical of a standard bilateral DUA between two non-African institutions. Administrators handling international genomic collaborations more broadly may also find CASRAI’s guide to Access and Benefit-Sharing (ABS) compliance for international material transfer agreements useful, since ABS obligations under the Nagoya Protocol can apply in parallel to DBAC review for certain biological material moving across African borders, and CASRAI’s guide to AESA, DELTAS Africa, and Grand Challenges Africa for the broader African research-funding landscape H3Africa sits within. For sensitive data more generally, CASRAI’s guide to data trusts as a community-governed model for sharing sensitive research data covers the same underlying governance problem — how to give a community, not just an individual data holder, real authority over ongoing access decisions — in a non-genomic context.
Frequently Asked Questions
Is the DBAC the same thing as an institutional review board (IRB)?
No. Local ethics approval (IRB or equivalent) is a precondition the DBAC checks for, not a function it performs itself. The DBAC reviews whether a proposed secondary use of already-collected H3Africa data or biospecimens is consistent with the original broad consent and with H3Africa’s own access guidelines; it does not replace the ethics review each requesting institution must independently obtain for its own proposed research.
Can a researcher outside Africa get access to H3Africa data?
Yes, but not on equal footing with African or African-collaborating researchers by default. The DBAC guidelines give priority access to researchers based on the African continent or collaborating directly with African scientists; a request without that connection can still be submitted and reviewed, but is not prioritized the same way.
How long does DBAC review take?
The Committee accepts applications on a rolling basis and commits to taking action within 60 days of receiving a complete application — not 60 days from initial submission if information is missing.
Can approved data or biospecimens be used commercially?
Research conducted under an approved request can proceed, but the DBAC guidelines explicitly prohibit commercialization of the biospecimens themselves.
What happens to data generated from DBAC-approved research?
Applicants commit, as a condition of access, to returning newly generated data to H3ABioNet (the pan-African bioinformatics network) or the European Genome-phenome Archive (EGA), rather than retaining it solely within the requesting lab.
