PAR-27-072: Bioengineering Research Grants (R01) for Translational Biomedical Engineering

PAR-27-072: Bioengineering Research Grants (BRG) (R01, Clinical Trial Optional)

Bioengineering Research Grants (BRG) are designed to fund projects that sit at the boundary between quantitative science and biomedical need. Under PAR-27-072, NIH is calling for R01 applications that do more than produce ordinary hypothesis-driven results; each proposal should materially advance translation, validation, or deployment of technologies, methods, or models with practical human-health impact.

Unlike many older opportunities that are tied to a narrow annual submission cycle, this NOFO runs as a recurring date sequence with key deadlines across 2026 and 2027 and remains active through 2029. It also explicitly welcomes clinical trial optional proposals, as long as the application remains focused on bioengineering development and translational value.

If your team works in cancer, optical or imaging methods, immunology, blindness, rehabilitation, measurement systems, AI-enabled diagnostics, or physically grounded modeling, this NOFO often sits closer to your problem set than a basic biology call. The challenge is that NIH review is highly explicit about responsiveness, so what you ask for and how it is packaged are both as important as the science.

Key details at a glance

What this opportunity is for, and what it is not

The official purpose language says this NOFO supports multidisciplinary bioengineering approaches that solve biomedical problems through integration, optimization, validation, and translational acceleration. In practice this means the proposal should clearly answer: what biomedical problem are you solving, which technology gap are you filling, and why does your engineering or quantitative approach produce a better solution than existing methods.

This includes discovery-driven, design-driven, and developmental modes. A central distinction in the reviewer criteria is that this is not a call for straightforward extension of known methods without substantial novelty in integration, performance, or translation. If your project only applies a standard technique without adapting or combining it for new capability, the NOFO text explicitly treats that as non-responsive when no substantive technology development is proposed.

The NOFO is also explicit about exclusions. NIH says it is not intended for phase III clinical trials, not intended to support conventional trials without translational motivation, and not designed for projects proposing only traditional biological studies that do not move a method, tool, or model toward application.

What this means for teams:

• If your concept has strong science but weak translation pathway, the application will be scored on impact but likely viewed as poorly aligned.
• If your proposal is clinically oriented, the trial can be included only when the technology validation is central, not merely incidental to a late-phase efficacy question.
• If your project relies on an existing off-the-shelf technology without meaningful redesign or adaptation, expect reviewer questions about whether it is truly BRG material.

The NOFO currently identifies interest areas spanning cancer, visual function and blindness, noninvasive sensing, immune profiling, imaging, and computational/AI-enabled interpretation. These are indicative examples, not an exhaustive list. The strongest applications are those that demonstrate cross-fertilization between life science and physical/engineering methods in a way that changes what is possible in the target field.

Why it is a strong fit for 2026/2027 planning

PAR-27-072 was posted in 2026 and includes recurring deadlines, which effectively gives applicants multiple windows each year across the 2026-2029 period. For planning purposes, this is useful for teams not fully ready in 2026:

• It lowers the pressure to force submission in one single quarter.
• You can treat each due date as a learning cycle.
• Multi-team collaborations can use earlier cycles for internal pilot-level work and resubmit with stronger validation.

The presence of both October 2026 and February, June 2027 opening points in sequence means teams with different readiness can align strategically. Because NIH expects revised and renewed applications, many applicants can improve from earlier rounds, as long as they avoid duplicate/overlapping submissions under active review. NIH forbids a new application while a related earlier submission is still awaiting a summary statement.

If your group is in pre-proposal stage, the practical value of this opportunity may be to map one cycle of development around a date in the BRG sequence and plan for proof points before submission: technical feasibility, early benchmark data, and an implementation plan for deployment in user settings.

Eligibility and eligibility traps

This is one of the first eligibility items teams should check before drafting. The NOFO is broad in organizational scope.

Eligible entities include:

• public or private higher-education institutions
• nonprofits (including non-501(c)(3) and 501(c)(3))
• for-profits and small businesses
• local, federal, and tribal government-affiliated organizations
• certain public housing and regional organizations
• foreign organizations (with specific rules around foreign components)

The headline: organizational eligibility is broad. But there is a strict rule that can derail otherwise excellent proposals: foreign subawards/subcontracts are not allowed. If your design requires funded foreign partners in the budget structure, this NOFO can be noncompliant unless the collaboration model fits NIH-approved pathways outside this call. Unfunded international scientific collaboration can still be allowed in other ways, but funded foreign subawards are explicitly rejected.

Eligibility also includes PI and organizational readiness:

• Any individual with the needed skills and resources can be PI; there is no strict “new investigator only” limitation in this NOFO.
• Multi-PI applications are allowed but must be managed by clear leadership design.
• A single organization may submit multiple applications only if scientifically distinct.
• Duplicate or highly overlapping applications are blocked by policy while one is under consideration.

A major practical gate is registration. NIH calls out this point repeatedly. Required pieces include:

• active SAM registration (with UEI),
• eRA Commons identity for PI and organization,
• Grants.gov registration,
• ORCID registration for each PI.

Registrations can take time. NIH says SAM can take several weeks to complete. A late registration is not considered a valid excuse for late submission. If you miss a deadline because registrations were incomplete, your application is late or non-compliant, and NIH applies strict late submission enforcement.

The safest interpretation for teams: begin SAM/eRA/Commons/Grants.gov setup immediately. If you only start during final month, use a pre-flight with your sponsored programs office and confirm each account is active before packaging. Do not wait for the PI to sign; do it in parallel with project scoping.

Funding size, budget, and award mechanics

The NOFO provides a direct annual cap statement: less than $500,000 direct costs per year. It does not publish an absolute total award amount and does not promise a fixed number of awards. NIH says the total number of awards is contingent on appropriations and merit.

Project duration is capped at five years, and the scope should drive the duration. In practice, most teams use shorter initial planning windows and phase the rest into a second phase only if translational milestones remain realistic. If your timeline requires longer-term tool deployment, set this expectation explicitly in the proposal budget narrative.

Notable operational points:

• Application type can be new, renewal, resubmission, or revision.
• Cost sharing is not required.
• Clinical trials are optional.
• No cooperative agreement terms are listed for this NOFO (no special term-of-management model).

For budget design, reviewers evaluate whether requested budget and period are reasonable for your stated research plan. Given the “engineering + translational + multidisciplinary integration” intent, include explicit budget logic tied to technical development milestones, rather than generic line-items. For example, if a prototype imaging algorithm needs repeated model retraining, specify compute and personnel tied to that cycle.

Application workflow and required materials

The NOFO requires electronic submission. Paper submissions are not accepted. Submission pathways include:

• NIH ASSIST,
• institutional system-to-system solutions,
• Grants.gov Workspace.

In practical terms, this matters because the application is only accepted if it passes the NIH electronic compliance checks and is fully corrected by the deadline. A changed/corrected package submitted after due time is late.

Critical submission mechanics:

1. Submit by Grants.gov and track in eRA Commons.
2. Review for submission errors before deadline.
3. Ensure PD/PI credential field includes a valid eRA Commons ID.
4. Use same UEI across SAM and Commons profile.
5. Include mandatory plans and records (where applicable) in the SF424(R&R) sequence.

Material requirements are strict and deserve a timeline:

• SF424(R&R) forms and other form instructions follow the NIH Application Guide.
• The Research Strategy section should directly state: unmet need, engineering/quantitative integration, translational pathway, and expected risks/limitations.
• Data Management and Sharing Plan is required for data-generating projects.
• Appendix is limited; publication uploads are not allowed.
• Human subjects and clinical trial sections must include required records and justifications.

This requirement is more than paperwork: BRG applications are reviewed heavily for fit between the proposed biomedical question and the enabling technology development. If you miss one of the compliance items, even strong science can be routed as non-responsive and not reviewed.

Practical submission plan

A practical pre-deadline calendar is often more important than proposal brilliance:

• 6+ weeks before: finalize registrations and check ORCID links.
• 4 weeks before: first full draft pass of Specific Aims, Approach, and preliminary translational justification.
• 3 weeks before: upload and run compliance checks through your portal.
• 1 week before: verify no unresolved warnings and check eRA Commons review for correct PI credentials.
• 48 hours before: run final content freeze and generate a correction plan.
• 24 hours before: force a full dry-run in case of portal latency.

Applicants are encouraged to apply early. That advice is practical: portal corrections can become the difference between “discussed” and “late.”

Review process and reviewer expectations

The review system applies NIH peer review criteria. The BRG-specific framing is built into three scored factors:

• Factor 1 (Importance): significance and innovation, with special focus on whether the approach develops a technology/tool/method that addresses an important biomedical gap.
• Factor 2 (Rigor and feasibility): quality of design, reproducibility, appropriateness of models/samples/controls, and timing feasibility.
• Factor 3 (Expertise and environment): team capability and institutional support, including multidisciplinary collaboration.

A recurring BRG lens is the integration quality. Reviewers explicitly assess whether engineering, computational, and physical science methods are appropriately integrated, not merely attached as labels.

For nonhuman or human-oriented work:

• Human subjects protections are assessed against NIH human subjects review criteria.
• Vertebrate animal plans are reviewed for appropriateness of species/procedures and welfare safeguards.
• Biohazard handling is evaluated where applicable.

For resubmissions and renewals, NIH re-evaluates progress and improvements. This is why a first unsuccessful cycle should be treated as data: strengthen methods rigor, close review criticisms, and reframe the translational path in the second cycle.

Funding decisions proceed from peer review into second-level IC review, where both merit and relevance to program priorities matter. Even applications with good science can lose to institutional policy fit and funding availability.

Common mistakes and how to avoid them

From the NOFO language, these mistakes repeatedly cause avoidable disqualifications:

1. Submitting a conventional late-stage clinical trial without clear technology-development center.

   • The NOFO does not support phase III conventional trials; if trial activity is central, ensure the proposal is still technology development-led and translationally grounded.

2. Treating BRG as pure hypothesis testing.

   • If the science does not clearly include a technology/tool/model method development arc, review may score it weakly.

3. Using existing tools without adaptation.

   • The NOFO flags unmodified existing technology use as non-responsive.

4. Applying with incomplete registrations.

   • A single missing profile, ORCID, or UEI issue can invalidate submission quality.

5. Assuming foreign collaborators can be funded as normal subcontracts.

   • Under this NOFO, funded foreign subawards/subcontracts are explicitly noncompliant.

6. Duplicate submissions and overlapping applications.

   • NIH does not accept overlapping applications at the same time for the same organization and PI context.

7. Treating page limits and appendices loosely.

   • Appendix restrictions are strict; publications generally are not acceptable there unless explicitly blank questionnaire/survey style.

8. Under-describing dissemination and adoption pathway.

   • Reviewers expect your Research Strategy to show what happens after technical development, including intended adoption route.

Frequently asked questions

What is the best first step before writing?

Map your problem statement into one clear biomedical question and one quantitative/engineering intervention. If you cannot express the “new capability” in two sentences, start over on scope. The NOFO is explicit about technology development, so your first paragraph should reflect that.

Can I include a clinical trial in BRG?

Yes, clinical trial activity is optional. But your trial should be tied to validating tool performance or function in a meaningful biomedical context. Avoid generic clinical trial asks without technology-centric rationale.

Is this only for biomedical PhDs and postdocs?

No. PI eligibility is broad as long as the organization is eligible and leadership can credibly run the work.

Is foreign participation possible?

Yes, with constraints. Eligible foreign organizations can participate, but funded foreign subawards/subcontracts are not allowed in this NOFO. Teams should use non-funded technical inputs or other allowable collaboration structures.

Do I need cost sharing?

No cost sharing is required under this opportunity.

Can we apply more than once from one institution?

Yes, if each application is scientifically distinct. If your applications overlap in concept or data, NIH policy can block the later one until the earlier summary statement is received.

What happens after submission?

The application goes through NIH compliance checks and peer review according to NIH timelines shown in the NOFO. If under consideration for funding, NIH may request just-in-time documentation.

Can a renewal application apply?

Yes. Renewal and revision are eligible, but the same technical and fit constraints apply.

Reviewer-quality preparation checklist

Use this pre-review checklist before clicking submit:

• The one-page summary explains the technical innovation and target biomedical gap.
• The Research Strategy section links methods to translational adoption.
• The approach includes reproducibility and rigor elements (controls, sample rationale, variability handling).
• Team structure is clearly multidisciplinary (PI + engineering + clinical/scientific collaborator).
• DMS plan is complete and concise (no narrative beyond required structured format constraints where applicable).
• Human subjects/clinical modules are complete where required.
• Project milestones and risks are written as a realistic 12-, 24-, 36-month arc.
• UEI, ORCID, eRA Commons IDs match exactly across systems.
• The PI checks every due date and time against the correct cycle.

Who should prioritize this opportunity

This opportunity tends to be strongest for:

• translational engineers partnering with clinical investigators,
• teams with a validated concept at readiness level where technical innovation is clear,
• small to mid-size groups looking for flexible R01-style structure within strict NIH administrative compliance,
• applicants who can submit an early-cycle draft and improve based on feedback.

Teams with only basic lab infrastructure and no implementation path rarely fare well unless they can demonstrate strong external co-development pathways and institutional support for multidisciplinary execution.

Official links

• Full NOFO: https://files.simpler.grants.gov/opportunities/4fa4f79e-d43d-42c9-9269-f219c7bc09df/attachments/df17417b-1461-4df7-9d22-e6db9be87c44/PAR-27-072-Full-Announcement.html
• NIH grants guide: https://grants.nih.gov/how-to-apply-application-guide
• eRA Commons: https://era.nih.gov/
• Grants.gov: https://www.grants.gov/
• NIH eRA Service Desk: https://www.era.nih.gov/
• NCI bioengineering contact email: [email protected]
• NEI contact email: [email protected]
• NICHD contact email: [email protected]

Final assessment

PAR-27-072 is a technically demanding but operationally attractive NIH track for teams that can show both engineering novelty and biomedical relevance. It is especially useful if your proposal can show a concrete path from method development to validation and broader adoption. If your organization is already active in translational research and can deliver compliant application materials on deadline, this NOFO is one of the better-structured NIH opportunities for crossing disciplinary boundaries without forcing you into a narrow disease-only mechanism.