Skip to content

RFA-DA-26-055 Existing Data R01 Eligibility

Updated 5 official sources

Quick Answer: RFA-DA-26-055 is a NIDA R01 for substance-use research using existing data. It is clinical trial not allowed, does not allow primary data collection, and should be compared with companion RFA-DA-26-056 R21 when the analysis is exploratory or not ready for a full R01.

Full answer and how we checked it

The 2026 decision turns on 7 checks.

Who this is for: Substance-use researchers, HIV and addiction research teams, data scientists, epidemiologists, health-services researchers, and sponsored-research offices deciding whether an existing-data project is R01-ready.

Data note: This guide uses NIH RFA-DA-26-055, companion RFA-DA-26-056, NIDA source context, Grants.gov listing 357544, and Grantsights award-data signals checked on June 2, 2026.

Source review by Grantsights, June 3, 2026: We rechecked NIH RFA-DA-26-055, companion RFA-DA-26-056, NIDA context, Grants.gov listing 357544, NIH data-sharing rules. Where official sources stop: The R01 still bars primary data collection and clinical trials, and NIH removed AIDS due dates from this NOFO, so current planning should focus on the non-AIDS dates and existing-data proof.

In this guide

RFA-DA-26-055 isn't a general addiction R01. According to NIH RFA-DA-26-055 (opens in a new tab), the NOFO encourages analyses of public-use and other extant community-based or clinical datasets to increase knowledge of substance-use etiology, trajectories, consequences, risk, resilience, services, prevention, treatment, and HIV-related outcomes.

The common failure in NIH secondary-data proposals is not weak statistics. It's route mismatch: the team says "existing data" but still needs new recruitment, new data collection, or a new intervention.

Use this guide with the live NIDA Existing Data R01 program record. Then compare NIH grants complete guide, NIH R01 R21 R03 K awards comparison, grants for substance abuse programs, what is a NOFO, and the Grantsights grant database.

Source Check

Checked June 2026.

This guide was first checked June 2, 2026 against NIH RFA-DA-26-055, companion RFA-DA-26-056, Grants.gov listing 357544, NIH application guidance, and NIDA source context. On October 10, 2026, Grantsights checked its dates, budget rules, and award-data figures against the NOFO, NIH notices, and USAspending.

The practical gap is the data-readiness boundary. RFA-DA-26-055 is an R01 clinical trial not allowed route for analyses of existing public-use, restricted-use, administrative, community-based, clinical, or linked datasets. NIH states that primary data collection is not allowed. If the aims need new recruitment, new surveys, new interviews, new biospecimens, or prospective intervention assignment, this route is wrong.

The live decision is R01 versus R21 versus another NIH path. Use RFA-DA-26-055 when the data access, data rights, analysis plan, power, privacy controls, substance-use fit, and team capacity are ready for a full R01. Use companion RFA-DA-26-056 when the analysis is exploratory or needs a smaller proof step.

Before drafting, build a data-readiness file with data owners, DUA status, restricted-file approvals, linkage rights, missingness risks, privacy controls, variable-to-aim mapping, and a budget check. The RFA says application budgets are not limited but must reflect the project's actual needs, and under NOT-OD-26-019 (opens in a new tab) NIH no longer requires applicants requesting $500,000 or more in direct costs in a year to contact the institute before submission.

Use this page with the live NIDA Existing Data R01 program record, R21 companion guide, NIH R01 R21 R03 K awards comparison, substance abuse grants guide, and grant search.

Get grant deadline alerts by email

About once a week, we email a short list of open grant calls with real deadlines from different funders. It isn't limited to the programs in this guide.

No spam. Unsubscribe anytime.

6 RFA-DA-26-055 Eligibility Stop Checks

6 stop checks decide whether the R01 route fits before a 5 year analysis plan is drafted. The project must be existing-data research, substance-use relevant, non-trial, and mature enough for R01 scope.

Stop checkStrong R01 signalRed flag
Data sourceExisting dataset is available and usableNew recruitment is needed
Data rightsAccess, DUAs, and linkage permissions are credibleAccess is uncertain
Substance-use fitAddiction, overdose, services, HIV, risk, or resilience is centralSubstance use is incidental
Analysis planQuestions, variables, power, and limitations are clearFishing expedition
Mechanism scaleR01-level scope and team capacityExploratory R21 would fit better
Trial statusNo prospective intervention assignmentIntervention test belongs elsewhere

The first question is whether the data already exist in a usable form. If the project depends on new recruitment, new measures, or new intervention exposure, it probably does not fit this NOFO.

5 Funding, Timing, and Mechanism Rules

5 public rules should appear before the specific aims page. NIH lists RFA-DA-26-055 as an R01 clinical trial not allowed opportunity. The remaining due dates are December 3, 2026, July 15, 2027, and December 3, 2027, and the RFA expires December 4, 2027. NIDA intends to commit $2 million in FY 2026 for 2 to 4 awards, plus another $2 million for 2 to 4 HIV-focused awards, shared with the companion R21. NIH says primary data collection is not allowed for this NOFO.

RuleSource-backed read
Funding numberRFA-DA-26-055
MechanismR01 research project grant
Clinical trial statusNot allowed
Primary data collectionNot allowed
Companion routeRFA-DA-26-056 R21
Next due dateDecember 3, 2026 (then July 15, 2027 and December 3, 2027)
Set-aside$2 million for 2-4 awards plus $2 million for 2-4 HIV-focused awards, shared with the R21

According to NIH, the RFA encourages analysis of public-use and other extant datasets. According to USAspending.gov (opens in a new tab) data, NIDA's assistance listing, 93.279 Drug Use and Addiction Research Programs, had about $1,489.2M in FY2024 obligations across 4,651 awards. (Listing 93.273 is NIAAA's Alcohol Research Programs, not NIDA.)

5 R01 Versus R21 Route Choices

5 route choices matter within 21 days because NIH also lists a companion R21. RFA-DA-26-055 fits existing-data work with enough scope, data access, and analytic maturity for an R01. RFA-DA-26-056 fits more exploratory existing-data work.

RouteBetter first read when...Why
RFA-DA-26-055 R01Existing-data project is mature and multi-yearR01 scale fits
RFA-DA-26-056 R21Analysis is exploratory or proof-of-conceptR21 scale fits
Parent R01Substance-use element is not central to this RFABroader route may fit
New data NOFOPrimary data collection is requiredThis RFA bars it
HIV services routeHIV service-delivery question is dominantInstitute fit may differ

For broader substance-use funding, use grants for substance abuse programs. For NIH mechanism choice, use NIH R01 R21 R03 K awards comparison.

What NIH Doesn't Tell You

4 hidden readiness questions decide whether this belongs under RFA-DA-26-055. NIH gives the source rules, but it does not know whether your dataset can answer your aims.

First, NIH does not make a dataset adequate just because it exists. Variable quality, missingness, sampling, timing, measurement consistency, and linkage limits matter.

Second, NIH does not make every secondary analysis R01-ready. If the analysis is a first pass or method test, R21 may be a cleaner route.

Third, NIH does not let the project smuggle in primary data collection. If the project needs new surveys, interviews, recruitment, or biospecimen collection, use another route.

Fourth, NIH does not remove data-governance risk. Data use agreements, privacy, tribal data governance, restricted-use files, and platform access can all block execution.

6 Real-World RFA-DA-26-055 Scenarios

6 scenarios show where the route fits over 5 years of analysis. One team using linked administrative, clinical, and overdose data to study treatment access after policy changes may fit. One team that needs to recruit people for new interviews does not.

ScenarioBetter routeWhy
Mature linked dataset and clear NIDA questionRFA-DA-26-055 R01Existing-data R01 fit
Exploratory analysis of one public datasetRFA-DA-26-056 R21Smaller scope may fit
New participant interviewsDifferent NOFOPrimary data collection is barred
Intervention assignmentClinical-trial routeR01 is not trial-allowed
HIV and substance-use service analysisRFA-DA-26-055 possibleScope can fit
Data access still pendingDelay or pilot routeExecution risk is high

One research team in North Carolina might have Medicaid, claims, and overdose data ready for multi-state analysis. One team in New York with only a planned survey should not use this route yet.

7 Draft Checks to Run First

7 checks should happen before writing. They keep the team from building an R01 around data that cannot carry the aims.

  1. Confirm all aims use existing data only.
  2. Confirm the project is clinical trial not allowed.
  3. Verify data access, DUAs, linkage rights, and timeline.
  4. Test whether the aims are substance-use central.
  5. Compare R01 versus companion R21.
  6. Check that each budget year reflects the project's actual needs (budgets aren't capped, and $500,000+ requests no longer need advance NIH contact).
  7. Contact NIDA program staff if dataset fit or scope is unclear.

According to NIH, primary data collection is not allowed for this RFA. Put that sentence in the first internal routing note so the whole team understands the boundary.

7 Evidence Assets That Make This R01 Stronger

7 evidence assets separate a fundable existing-data R01 from a loose secondary analysis. The strongest version of this application reads like a planned study, not a dataset tour.

First, name the data sources and prove access. According to NIH, this RFA can support analyses of public-use and other existing community-based or clinical datasets, including public, restricted-use, and administrative data sources. The application should state which files are in hand, which require approval, which need linkage, and who controls each timeline.

Second, map every aim to variables that actually exist. Aims should not depend on proxy measures that only partly match the science. Reviewers need to see outcome definitions, exposure measures, time windows, missingness, and limits.

Third, explain why the question is substance-use central. RFA-DA-26-055 can touch HIV, prevention, treatment, services, policy, neurodevelopment, risk, resilience, and trajectories, but the substance-use logic cannot be incidental.

Fourth, show the analysis plan before the application becomes a fishing expedition. The honest test is whether a reviewer can tell what the applicant expects to learn, why the data can answer it, and what would count as a meaningful result.

Fifth, handle bias and missing data directly. Existing data often have uneven collection, policy changes, coding drift, unmeasured confounding, and population gaps. Avoid hiding those issues in limitations.

Sixth, include a governance file. One university in North Carolina with signed access to Medicaid, claims, overdose, and treatment-service data could make a credible R01 if the linkage rights and privacy controls are clear. One team with a hoped-for data agreement cannot.

Seventh, decide whether the R01 is too much. According to NIH, RFA-DA-26-056 is the companion R21 route. If the project is mostly a proof-of-concept analysis, the R21 may be the better first move.

21-Day Existing-Data R01 Routing Plan

21 days is enough to decide whether the R01 should proceed. Days 1 through 3 should confirm data existence, access, restricted-file status, and the no-primary-data boundary.

Days 4 through 7 should test aims against available variables. The team should prove each aim can be answered with existing measures.

Days 8 through 12 should compare R01 and R21. If the analysis is exploratory, use the R21 or a pilot route before building a full R01.

Days 13 through 16 should build the analysis and governance file: data dictionaries, linkage plan, missingness review, DUA timeline, privacy controls, and reproducibility plan.

Days 17 through 21 should run NIH submission checks against the next due date, December 3, 2026. Advance contact for $500,000+ budgets is no longer required under NOT-OD-26-019, but talk to NIDA program staff if scope or dataset fit is unclear.

6 Reviewer-Risk Signals to Fix

6 risk signals should be fixed before submission. First, the aims should not depend on variables that are weak, missing, or inconsistently collected.

Second, the application should not read like a broad data-mining exercise. It needs theory, hypotheses, and substance-use relevance.

Third, data access should be credible before submission. Reviewers can spot "we will obtain" risk when the entire project depends on access.

Fourth, the project should not imply new data collection. The RFA says primary data collection is not allowed.

Fifth, the statistical plan should address bias, missingness, confounding, and generalizability.

Sixth, the dissemination plan should fit the audience. NIDA existing-data work can influence prevention, diagnosis, treatment, services, overdose response, HIV care, and policy.

6 Budget And Scope Questions Before Submission

6 scope questions should be answered before the institutional deadline. Existing-data applications can look inexpensive, but R01 scope still needs the right people, data fees, security work, and analytic time.

The first question is whether each dataset has a cost, access window, or restricted-use environment. Public-use files may be easy, but state data, claims files, EHR extracts, and restricted archives can take months.

The second question is whether the team has the statistical depth for the proposed design. Causal inference, longitudinal modeling, linkage, geospatial policy data, and missing-data work should not be treated as ordinary descriptive analysis.

The third question is whether software, secure computing, and privacy review are funded. According to NIH, applicants must follow the Research instructions unless the NOFO says otherwise. For sensitive substance-use data, privacy and reproducibility need real planning.

The fourth question is whether the project is too broad. Avoid a three-aim R01 where each aim uses a different dataset, population, and method unless the integration logic is clear.

The fifth question is whether collaborators with data rights are paid and accountable. Data owners should not appear only in a support letter if the whole project depends on them.

The sixth question is whether the R21 would be cleaner. Start with the R21 when the data are real but the linkage, power, or analysis strategy still needs proof.

5 Applicant Types and Best Next Move

5 applicant types commonly ask about RFA-DA-26-055.

Applicant typeBest next moveWhy
Data-ready addiction research teamBuild R01 fit memoRoute may fit
Exploratory analystCompare R21R01 may be too large
Team needing new recruitmentUse another NOFOPrimary data is barred
HIV services researcherTest NIDA fitScope may fit if substance use is central
Sponsored-project officeCheck data rights and budgetTechnical issues can block

The best answer is: use RFA-DA-26-055 when all data already exist, access is credible, the question is substance-use central, and the project is mature enough for an R01.

7 Existing-Data R01 Checks Updated June 2, 2026

According to Grants.gov, teams should verify the live record before relying on a copied deadline.

Checked on June 2, 2026 against RFA-DA-26-055 (opens in a new tab), RFA-DA-26-056 (opens in a new tab), and the Grants.gov listing (opens in a new tab).

CheckWhat to confirm
EligibilityConfirm the applicant, institution, and route rules for RFA-DA-26-055 existing data R01 eligibility.
Source statusVerify the official listing, notices, due date, and expiration status.
BudgetCheck award size, cost limits, match, or budget logic when the source provides it.
EvidenceName the data, preliminary work, partner role, or implementation proof needed.
Bad fitStop if the project belongs in a nearby NIH or federal route.
Review criteriaTie the first page to significance, approach, team, environment, and source-specific criteria.
Next actionDecide whether to draft, ask a program contact, or redirect.

According to official source 2 (opens in a new tab), the companion R21 record should be checked before the team chooses R01 scope.

Final public checklist

  • Confirm whether R01 is the right route or whether a nearby program fits better.
  • Check budget, partner, match, or data-readiness constraints.

Sources

Next steps

Where to go next

These next pages help you move from research into a specific grant choice.

Federal Program Records to Compare

Use these current program records to check eligibility, award history, deadlines, and past winners before your team commits writing time.

Frequently Asked Questions

What does RFA-DA-26-055 fund?

NIH says the R01 supports analysis of public-use and other extant community-based or clinical datasets to advance substance-use research.

Can applicants collect primary data?

No. NIH says primary data collection is not allowed for applications in response to this NOFO.

Are clinical trials allowed?

No. RFA-DA-26-055 is clinical trial not allowed.

What is the companion R21?

NIH lists RFA-DA-26-056 as the companion R21 for existing-data substance-use research.

Who should skip this route?

Skip it if the project needs new participant recruitment, new biospecimen collection, or intervention testing.

Last updated October 10, 2026. Corrected October 10, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.