PAR-25-337: Academic-Industrial Partnerships for Translation of Technologies for Diagnosis and Treatment (R01, Clinical Trial Optional)

PAR-25-337: Academic-Industrial Partnerships for Translation of Technologies for Diagnosis and Treatment (R01, Clinical Trial Optional)

PAR-25-337 is an NIH Notice of Funding Opportunity (NOFO) that funds translational work where academic and industrial collaborators deliver a measurable new capability for diagnosis, treatment, risk assessment, or disease monitoring. It is intentionally positioned as an applied partnership mechanism, not a basic research only track. The NOFO is reissued from an earlier cycle and explicitly asks teams to move technologies, methods, or systems from proof-of-concept into a validated setting that has end-user value.

If you are deciding whether this is the right opportunity for your group, the core test is simple: can your team include both a strong academic base and an industrial partner, and can you show that your planned work directly closes the gap between a technical concept and a real-world deployment context? If the answer is yes, this is likely worth a serious draft.

As of the current check date, this NOFO is in active multi-cycle mode with key dates listed through 2027 and 2028. The immediately relevant next submission window is 2026-06-05 (5:00 PM local applicant time) for new, renewal, and resubmission/revision applications.

Key details at a glance

What this opportunity is and is not

This call is for teams with a translation problem, not a pure discovery-only problem. The NOFO defines innovation as the likelihood of delivering a new capability to end users. That framing changes how reviewers judge you. An exciting idea is not enough; you must show a path to a usable, validated method or platform in the context it will be used.

In scope

PAR-25-337 supports work that enhances, adapts, optimizes, validates, or otherwise translates existing technologies or methods for diagnosis, imaging, detection, monitoring, and disease-relevant applications. The NOFO gives examples like molecular diagnostics, imaging/spectroscopy systems, quality assurance, data harmonization, quantification, and software or analytics tools that improve reproducibility and practical performance.

The opportunity is also explicitly open to non-clinical use contexts so long as they still relate to meaningful biomedical problem solving and translational readiness. It is not limited to one clinical setting; pre-clinical, clinical, and non-clinical applications are all contemplated. Projects can be designed around underserved populations or low-resource settings if the adaptation and validation plan addresses feasibility and impact.

Out of scope

The same announcement is explicit that this is not for:

• commercial production funding,
• basic research disconnected from a translational development plan,
• standalone clinical studies that do not prioritize translation,
• phase III clinical trials.

In practical terms, if your proposal is mostly “science curiosity” with no clear deployment logic, it will likely fail responsiveness before review. Similarly, projects with no industrial contribution to commercialization or implementation planning are usually weak in this mechanism, because partnership structure is a central design requirement.

Why the academic-industrial model is central

A practical read of the NOFO shows that this is not merely an “add a sponsor letter” sort of collaboration. The mechanism expects a genuine alliance: at least one academic partner and one industrial partner, and a governance structure capable of coordinating ownership, deliverables, and resource allocation.

The partnership should usually include:

• clear roles for who owns method design, validation, and technical transfer,
• a joint timeline for milestone achievements,
• shared definitions of end-user needs,
• explicit responsibilities for generating evidence that supports adoption.

This NOFO repeatedly emphasizes capability transfer, not just publication output. The strongest applications generally describe how each partner’s contribution is required to complete the translational pipeline.

Who this is best for

The best-fit teams tend to share five characteristics:

1. A real translational friction point: They can identify a known bottleneck (accuracy, standardization, scalability, reproducibility, affordability, integration into care workflows).
2. A mature method with transition potential: The approach is beyond pure conceptual stage, with enough preliminary evidence to justify practical development.
3. A committed industrial partner: A company or translational entity with skin in the game and clear deployment intent.
4. An end-user deployment hypothesis: Who uses the output, in what setting, with what expected benefits.
5. Evidence-first planning: A credible schedule and experimental design for validation.

These applications perform best in high-value, high-friction domains such as cancer diagnostics, imaging workflows, or systems where validation across laboratories/platforms is essential. The NOFO is explicit that applications are expected to deliver capability improvements like enhanced rapidity, reliability, usability, or standardization.

Eligibility and structural requirements in practice

This is a broad NOFO by institutional type. It includes higher education institutions, nonprofits, for-profits including small businesses, local governments, and federal entities. It also notes that non-domestic entities are eligible, but foreign participants must follow NIH registration and compliance requirements.

Critical eligibility mechanics

Registrations are hard gates. All required registrations must be complete before submission:

• SAM registration and UEI,
• eRA Commons profile for the applicant organization and each PD/PI,
• Grants.gov registration,
• associated identifiers (including NCAGE/NATO codes where applicable).

The NOFO states that registration may take weeks; delay is not an acceptable excuse for late submission. If your institution has not completed this early, this is a major risk.

No cost sharing is required. This lowers one barrier, but it does not lower standards. You still must provide strong justification, complete plans, and budget realism.

Multiple applications are possible, but overlap is tightly regulated. You may submit more than one if scientifically distinct, but NIH will reject duplicates or essentially identical submissions in process.

Partnership mechanics and roles

Because this is an academic-industrial NOFO, the quality of your consortium design is as important as your science:

• Explain why each partner is needed.
• Show governance coordination.
• Show how budgets map to tasks and milestones.
• Avoid “paper alliances” where one partner’s role is generic.

Applications that do not show a realistic governance model are often scored as weak in Approach even when the technical idea is promising.

Application materials and process: what to prepare

All NIH NOFO-standard forms and page limits apply through the How to Apply Guide, and this NOFO adds additional requirements that matter for reviewers:

• Specific Aims should define the final capability target and include measurable performance milestones.
• Research Strategy should describe the collaboration architecture, translational rationale, and the path from readiness to validated utility.
• Approach should present feasibility, validation data strategy, and potential bottleneck mitigations.
• Statistical and rigor expectations should be explicit, especially where sample size, variability, and generalization matter.
• Resource sharing plan and Data Management and Sharing Plan requirements apply and must be addressed.

Submission platforms and timing

You must submit electronically via NIH/Grants.gov route options:

• NIH ASSIST,
• institutional system-to-system (if approved in your office),
• Grants.gov Workspace.

Paper submissions are not accepted. NIH expects on-time electronic submission and tracks late changes strictly. A corrected submission after the deadline remains late.

Required content details to avoid administrative rejection

• Include valid eRA Commons IDs for all PD(s)/PI(s).
• Use consistent UEI/SAM identity across eRA Commons and Grants.gov.
• Confirm clinical trial status honestly: optional in this NOFO, but if you involve human subjects or clinical studies, include required human subjects and clinical trial records as appropriate.
• Keep appendix materials strictly compliant; NIH forbids excessive publication appendices and only narrow appendix categories are allowed.

Review logic and what reviewers score highest

The NOFO uses standard NIH review structure with factors around Significance, Innovation (as defined by end-user capability), Approach, and Investigator/Environment.

Where proposals usually win or lose

Strong points that score well:

• Clear target problem and user context.
• Strong evidence of translational readiness.
• Credible partnership governance.
• Concrete performance targets and milestones.
• Feasible execution timeline with controls for reproducibility.

Common reviewer concerns:

• Weak end-user logic (“we can build it, but no one uses it yet”).
• Partnership with no operational integration (no management and ownership model).
• Overpromising budget or timeline without risk controls.
• Inadequate rigor around validation across platforms and settings.

Reviewers also check whether your project is genuinely in scope versus a project that should be handled by a different grant line. That includes screening for basic-research-only proposals and phase III trials.

Preparation strategy for a high-quality submission

A practical 12-week workflow helps teams move from concept to submission:

Week 1–2: scope and partnership alignment

• Map the problem to an explicit disease or care-relevant workflow.
• Force one-line definitions of end-user benefit for each module.
• Confirm at least one firm industrial collaborator with realistic contribution.

Week 3–4: evidence and methods package

• Draft Specific Aims with concrete performance targets.
• Define how you will adapt, optimize, and validate the technology.
• Gather preliminary data and identify data quality controls.

Week 5–6: governance and budgets

• Write governance section for day-to-day execution.
• Align budget with roles, milestones, and task ownership.
• Build internal compliance checklist for registrations and PI credentials.

Week 7–8: technical and regulatory compliance layer

• Add Data Management and Sharing Plan.
• Build human subjects logic if applicable.
• Add clinical trial logic only where justified.

Week 9–10: internal review and corrections

• Route through internal grants office.
• Validate SF424(R&R) forms and required profiles.
• Ensure page limits and appendix rules are followed.

Week 11–12: submission rehearsal and margin planning

• Run final checks well before deadline because corrected submissions after deadline are still late.
• Verify eRA Commons and Grants.gov status views before final submission.

Common mistakes and how to avoid them

1. Treating this as a standard R01 without partnership architecture. This is one of the highest-frequency issues. If the partnership is superficial, the application can be perceived as non-responsive.

2. Ignoring registration timelines. Registration delays are a frequent cause of late/no submissions. Start at least 6+ weeks early.

3. Using appendices as a dumping ground. NIH expects tight compliance. Include only allowed materials.

4. Overstating readiness. A technically strong concept without readiness evidence (validation pathway, user settings, deployment plan) is vulnerable at both compliance and approach scoring.

5. Submitting to “one-size-fits-all” review standards. This NOFO has specific criteria around capability translation and end-user use; proposals must speak directly to that language.

6. Underspecifying clinical translation if clinical studies are included. If human subjects are involved, include full rationale, inclusion considerations, and recruitment/retention planning.

FAQ (practical)

Is this for phase III clinical trials?

No. The NOFO explicitly says phase III clinical trials are not sought. This NOFO is for translational development and validation toward usable capability.

Can my institution submit with another R01 this round?

Yes, if applications are scientifically distinct and compliant. The NIH screening rule is strict for duplicate or overlapping submissions.

Is cost sharing mandatory?

No.

Is this open only in 2026?

No. The key dates show recurring NIH submission windows with cycles into 2027 and beyond, which is relevant for planning if you miss the June 2026 deadline.

What is the maximum budget?

The NOFO states the budget is limited to $499,000 direct costs per year and up to 5 years.

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

No, foreign entities are mentioned as eligible, but all foreign and NIH registration requirements still apply. Validate foreign-component compliance early.

Decision checklist before pressing submit

Use this checklist to filter risk before finalization:

• Confirm at least one genuine academic and one industrial partner with a defined governance model.
• Confirm application category (new, renewal, resubmission, or revision) is correct.
• Complete SAM/eRA Commons/Grants.gov registrations.
• Validate specific aims to a defined end-user capability.
• Include robust translation milestone timeline and metrics.
• Build a defensible approach to reproducibility, validation, and generalization.
• Confirm data-sharing requirements and resource-sharing plans.
• Recheck submission method (ASSIST or Grants.gov Workspace or S2S) and deadlines.
• Resolve all required IDs and credentials before final upload.

Official links

• Official NOFO page: https://grants.nih.gov/grants/guide/pa-files/PAR-25-337.html
• NIH funding opportunities list: https://grants.nih.gov/funding
• NIH How to Apply – Application Guide: https://grants.nih.gov/grants-process/how-to-apply-application-guide
• NIH Grants Policy Statement: https://grants.nih.gov/grants/policy