RFA-HD-27-007: Using Archived Data and Specimen Collections to Advance Maternal and Pediatric HIV/AIDS Research

RFA-HD-27-007: Using Archived Data and Specimen Collections to Advance Maternal and Pediatric HIV/AIDS Research

At a glance

Why this RFA is strategically important now

This call is unusually specific in its design: it asks researchers to build new studies on top of existing evidence, not start entirely new cohorts from scratch. That is important for maternal and pediatric HIV/AIDS because historically these populations are data-poor compared to broader adult studies, and large archived cohorts and specimen archives can hide important secondary insights that have not yet been extracted.

The call focuses on evidence reuse and integrative science in an area where two constraints usually collide:

• Valuable biological samples and longitudinal records already exist,
• New recruitment for new studies is expensive and often slow, especially for pregnant people living with HIV and pediatric subgroups.

By prioritizing secondary use of archived resources, this RFA lowers the barrier to scientifically valid innovation while still forcing rigor in harmonization, data cleaning, and translational interpretation. If your team already has repository access, clinical network links, or biostatistical infrastructure, this is one of the few NIH-style calls where that readiness can significantly reduce lead time.

The 2026/2027 timing is also relevant: NIH’s pattern in this family of RFAs has been to keep an annual rhythm with revised topics and renewed solicitation windows, so teams can often reuse institutional preparation, then pivot deliverables and endpoints based on prior cycle feedback.

What the funding actually supports

The announcement is narrow in scope but broad enough to support several project designs:

• Re-analysis of previously collected HIV cohort data with a maternal-child lens.
• New assay or biomarker work tied to archived specimens.
• Integrated analyses where maternal immune, virologic, and clinical trajectories are linked to pediatric outcomes.
• Methodological projects that improve the validity of findings from pooled data or multi-biobank datasets.

The language in the announcement emphasizes secondary use, integration, and feasibility for timely translational interpretation. It explicitly aligns with HIV/AIDS goals where historical repositories can answer questions about treatment evolution, transmission prevention, and long-term health outcomes without launching a full new trial.

The fund is not a replacement for large center-scale clinical trials; it is exploratory and targeted. Expect budgets and scope to match pilots and mechanism-building work with a clear path toward follow-on funding or implementation research.

Who should apply and who should not

This is a fit for teams that can do all of the following:

1. Demonstrate legitimate access to archived datasets or specimen collections.
2. Show that data are relevant to maternal HIV, pediatric HIV, or mother-to-child transmission questions.
3. Propose a design that is feasible in 2 years with modest direct funding.
4. Include a clear analysis strategy that goes beyond descriptive data mining.

Typical strong applicants:

• University-based HIV research groups with active data science and biostatistics capacity.
• Translational teams attached to established pediatric HIV networks.
• Groups with existing collaborations between clinicians, epidemiologists, and laboratory scientists.
• Biobank-linked investigators who can show chain-of-custody and ethical governance around archived specimens.

Typical mismatch profiles:

• Teams with no access rights or no realistic pathway to obtain archived material permissions.
• Large clinical trials that require a mechanism for new enrollment and intervention delivery.
• Teams proposing standard service contracts or commercial pilot products with no hypothesis-driven HIV maternal/pediatric research angle.
• Applications that understate data harmonization complexity.

Eligibility and institutional fit

The NOFO language and NIH context indicate U.S.-based research entities and collaborators are expected as core applicants. In practice, successful teams tend to satisfy three layers:

• Applicant eligibility: the institution and PI meet standard NIH eligibility and administrative requirements for this RFA’s mechanism.
• Scientific eligibility: explicit relevance to maternal and pediatric HIV/AIDS and direct use of archived resources.
• Compliance readiness: data use agreements, IRB pathways, and documentation for repository use.

A practical checklist before hitting submit:

• Confirm the exact sponsoring component’s policy on non-U.S. collaborators if your team spans borders.
• Confirm that every dataset and biospecimen source has reuse permissions aligned with the intended analyses.
• Prepare a data dictionary of available variables and note missingness, harmonization burden, and cross-site comparability.
• Verify that specimen quality constraints (storage conditions, storage age, assay compatibility) are not blocking proposed endpoints.

If your team can answer these questions with documents, you are at the right level of readiness. If not, build that readiness before drafting aims.

Key dates, cycle pattern, and how to think about the deadline

The published details list an October 21, 2026 target date for this solicitation window. In the context of NIH RFAs in this class, cycles can recur in subsequent years as the program manager updates scope and scientific priorities. The target year context in this repository is 2026 and 2027, so this should be treated as current and relevant for teams that can quickly reframe existing analyses for 2027 calls.

Why the timing matters:

• Pre-submission phase: now-to-summer 2026 should be used for data access documentation, preliminary harmonization, and team alignment.
• Submission window: expect most high-quality teams to spend late summer on final internal review and compliance sign-offs.
• Post-submission: reviews for these mechanisms can be fast-moving, so budget, personnel roles, and timeline realism matter as much as scientific novelty.

For teams aiming for 2027 follow-on opportunities, this cycle can produce preliminary data that supports stronger renewals and larger applications.

Budget and budget behavior in plain terms

The NOFO’s budget statement indicates a total FY2027 set-aside of $1,000,000. Individual projects are capped at $275,000 in direct costs over two years, and no more than $200,000 direct costs per year.

That has three practical consequences:

1. No room for broad, under-scoped pilot expansion. You should avoid trying to solve every secondary question in one proposal.
2. Use budget for analysis leverage, not administrative overhead. Prioritize data access processing, assay interpretation, and core staff who can execute quickly.
3. Design a single coherent output. Most strong proposals aim for one major analytic package and one proof-concept translational claim.

Suggested internal budget posture:

• PI and scientific lead: limited but defined effort.
• Biostatistics and data management staffing from day 1.
• Assay and data integration expenses clearly tied to feasibility and outcome generation.
• Travel only when essential and linked to consortium/consent requirements.

Avoid vague budget language such as “additional validation work as needed.” Reviewers will treat that as weak feasibility under a mechanism intended to deliver clear short-cycle products.

Required application elements and where people usually get stuck

Because this is an NIH application pathway, the standard eRA submission architecture applies, with extra attention to archived material justification. The core pieces teams usually include:

• Project narrative, with specific aims centered on maternal/pediatric HIV/AIDS questions.
• Data source plan: what is already available, what can be requested, what is missing.
• Specimen handling and analytical plan: from storage constraints to assay strategy.
• Analysis strategy and power/precision framing for re-used datasets.
• Personnel table and management structure aligned with project risk.
• Data sharing and reporting strategy, where applicable.

Common failure modes in NIH RFA submissions of this type:

• Insufficient specificity on data sources. A vague statement like “we have access to multiple cohorts” without mapping identifiers, variables, and governance is often scored down heavily.
• Weak endpoint definition. A broad “improve maternal outcomes” objective without measurable endpoints and milestones under time limits looks exploratory in the wrong way.
• Overstated novelty claims without reproducible reproducibility. Reused data can produce noise if harmonization plans are thin; reviewers look for concrete methods and assumptions.
• Unclear chain of custody and compliance posture. Specimen-based work fails quickly if governance and approval status are underspecified.

To strengthen your submission, explicitly show: what is already available, what can be integrated, what is not feasible, and what secondary analyses are pre-registered or at least analytically pinned down in advance.

How applications are evaluated and what reviewers usually reward

NIH-style reviews for this class typically favor the following:

• Strong scientific rationale tied to existing evidence gaps.
• Feasibility within the budget and two-year window.
• Methodological rigor in handling archived data heterogeneity.
• A clear translational path from findings to future NIH or non-NIH studies.

The strongest applications have an argument structure like this:

• Public health relevance: maternal and pediatric HIV still has unresolved questions in prevention and long-term outcomes.
• Data logic: archived datasets are uniquely placed to answer those questions faster than de novo studies.
• Methodological credibility: harmonization and missingness are pre-empted, not discovered late.
• Implementation credibility: outputs that could guide future clinical or policy work.

In an exploratory mechanism with capped budgets, “scientifically interesting but technically under-engineered” proposals are less competitive than “technically precise and narrow but high-quality.”

Preparation plan: a practical 12-week runway

Below is a practical playbook for teams starting once a solicitation is identified:

1. Weeks 1–2: confirm source eligibility and assign one PI plus one data steward as decision owners.
2. Weeks 3–4: finalize data/specimen source commitments and draft the source map for each cohort/specimen bank.
3. Weeks 5–6: lock project aims and primary/secondary analyses into a one-page timeline.
4. Weeks 7–8: write Specific Aims and methods with explicit assumptions and fallback plans.
5. Weeks 9–10: complete budget, facilities narrative, and governance sections including permissions and ethics.
6. Weeks 11–12: conduct internal peer review focused on feasibility and reviewer clarity, then submit.

If any upstream task is still unresolved by week 6, pause writing and resolve compliance first. NIH reviews still score heavily on execution confidence, and unresolved permissions are a top reason for weak discussion points.

Frequently asked questions

Is this limited to one mechanism or does it support multiple award types?

The solicitation language indicates a single RFA framework with the stated funding and scope; applicants should assume one standard route and design within stated direct-cost limits.

Are only clinical trials eligible?

No. This call specifically supports archived-data/specimen research and is aligned to secondary analysis and translational exploratory outputs, not necessarily interventional trial initiation.

Can new institutions join as collaborators?

Yes if roles, permissions, and data governance are coherent, but the core applicant path should be institutionally compliant and realistic within the direct-cost cap.

What should a pilot application prove to be competitive?

A clear causal or mechanistic hypothesis, a tractable analytical design, and a timeline that is realistically deliverable with existing data and specimens.

Is this only for U.S.-based teams?

The funding mechanism is NIH-administered and U.S.-anchored in this solicitation. Confirm partnership and governance details early for any non-U.S. collaborators.

What changed between 2026 and 2027 cycles?

Annual cycles often retain the same core scientific intent but can shift priorities and deadlines. Teams that treat this as a reusable “platform cycle” have strategic advantage.

Official links and direct references

• Full NOFO text: RFA-HD-27-007 full announcement
• NIH Grants and Funding listing: NIH funding opportunities
• NIH eRA Commons and submission systems links should be used through the current official NIH pathways linked in the NOFO package.

Risks, assumptions, and practical fit for your organization

This is a highly specialized opportunity. The biggest advantage is speed: you can launch from existing assets rather than building a new study cohort. The biggest risk is the same: existing assets can look attractive and still be analytically unusable if variable definitions vary or specimen metadata is incomplete.

A conservative way to evaluate your fit:

• If you already have two or more usable cohorts and a functioning data integration pipeline, this is a strong fit.
• If your team needs to secure access during submission, treat that as a pre-submission risk and fix before drafting aims.
• If your team has mostly conceptual innovation without data rights and harmonization capacity, this RFA will expose gaps quickly.

For teams that can prove readiness, this is one of the cleanest ways to generate credible maternal and pediatric HIV/AIDS outputs under a constrained budget. The resulting data products can feed larger programs in prevention, care continuity, and maternal-child outcomes with significantly lower lead time than a new RCT.

Next step checklist before submission

1. Lock the scientific question into one primary endpoint and two secondary outputs.
2. Map every dataset and specimen to custodians, permissions, and timeline.
3. Write a harmonization plan before writing the significance section.
4. Build a 12-item compliance matrix (IRB, data use agreements, chain of custody, de-identification standards).
5. Run internal review using the lens: feasibility, innovation, and evidence quality.
6. Confirm submission artifacts are complete for NIH electronic systems and final compliance.
7. Submit with a date buffer for corrections.

The opportunity is strong because it rewards disciplined teams that already do rigorous secondary-data science. With the 2026 publication date and the 2027 planning context, this is a practical target for teams that are ready to operationalize archived resources now.