PAR-26-042: Research Grants in Clinical Informatics (R01 Clinical Trial Optional)

PAR-26-042: Research Grants in Clinical Informatics (R01 Clinical Trial Optional)

Clinical informatics sits at the center of modern care delivery, but most groups still struggle to turn clinical data into robust, reusable tools that actually change practice. PAR-26-042 is NIH’s new initiative to fill that gap: the National Library of Medicine (NLM) is asking for R01-level projects that build innovative, scalable, and generalizable methods for organizing, analyzing, and applying clinical and healthcare data.

The opportunity is real and practical for teams that can move beyond pilot-only ideas and propose tools or approaches with translational value across biomedical settings. It is a good fit for teams combining healthcare domain understanding with data engineering, machine learning, and software delivery.

Key details at a glance

What this opportunity supports

NLM frames this announcement as a mission-forward call to fund methods that help clinicians, patients, and health systems make better decisions from real-world health data. The program intentionally favors approaches that are broader than niche, one-off tools.

What counts as a strong fit

The NOFO says proposals should focus on clinical informatics methods that are:

• scalable across settings,
• reusable beyond one dataset or hospital,
• relevant to research and care improvement,
• capable of producing broadly useful outputs,
• and anchored in robust validation and maintenance planning.

The list of priority-aligned themes includes:

• improving information and knowledge tools for care teams and patients,
• next-generation clinical decision support,
• EHR usability and interoperability improvements,
• predictive analytics and prevention-oriented models,
• data integration and harmonization methods,
• AI methods with clear benefits to workflow, outcomes, or health system efficiency,
• and reducing administrative friction that drives clinician burden.

The initiative is also explicit about what it does not want:

• narrowly scoped projects with little generalizability,
• work focused only on social determinants/ETHICS-only framing without core informatics innovation,
• incremental patching of existing systems without meaningful novelty,
• high-cost projects without clear innovation,
• or work that does not commit to open dissemination of outputs.

The program purpose is not just to produce prototypes; it aims to produce methods with evidence of sustained value.

Who is likely to be eligible

The eligibility section is broad but strict where compliance is concerned. In plain terms, both institutions and investigators can be broad in scope as long as all submission rules are followed.

Eligible organizations and collaborators

From the NOFO’s text, eligible applicants include:

• higher education institutions (public and private),
• nonprofits with and without 501(c)(3) status,
• small businesses and for-profit entities,
• local governments,
• some federal entities and eligible U.S. territory agencies,
• selected “other” categories (e.g., school districts, housing authorities, regional organizations),
• foreign non-domestic entities in certain categories.

What is unusual is the explicit policy update around foreign subcontracts: NIH will not accept applications with foreign subawards/subcontracts under this NOFO. That means international collaborators are not prohibited generally, but monetary collaborations via subawards may be disallowed, and the line between collaboration and funded subawards matters.

Individuals and applicant profile

Any individual with sufficient expertise can be PI or Co-PI if the institution supports the submission. This is not a people-centric fellowship program; this is an organization-led R01 mechanism requiring institutional administration.

What to confirm before starting

At minimum, teams should ensure:

• the PI/PD and organization are registered in eRA Commons,
• organization has active SAM registration and a valid UEI,
• organization-specific accounts and signing authority are complete,
• no duplicate or overlapping pending applications are submitted simultaneously,
• institution can support submission workflows through ASSIST/Grants.gov/eRA Commons.

What it funds (and what it does not)

The budget language is concise and clear: maximum $250,000 direct costs per year. That is the top line to anchor scope and team planning. The NOFO still gives room for up to 4 years project period, but duration must match realistic scope.

Funding model implications

This is a standard NIH R01-style framework with no mandatory cost sharing. In practice, teams should:

• budget to the data lifecycle, not just model development,
• include compute, staffing, evaluation, and dissemination,
• keep all spending defensible against requested scientific outcomes,
• and avoid overselling large infrastructure ambitions that exceed year-by-year direct cost limits.

Because budget review criteria include reasonableness and justification, review panels often treat overly aggressive staffing or platform costs skeptically if not tied to clear milestones.

Strong and weak budget patterns (practical)

Strong pattern:

• clear tie between each major cost and a validated methodology milestone,
• explicit maintenance and dissemination resources,
• realistic compute and staffing curves,
• modest but adequate project management.

Weak pattern:

• heavy fixed overhead on internal tools without direct science output,
• no plan for reusable software/resource packaging,
• unrealistic expansion into clinical implementation with little budget basis.

Timeline and workflow: planning with the real dates

This opportunity is structured for recurring annual cycles, not a one-off once-a-year window.

Key dates

• Posted: 2026-02-11
• Open date: 2026-04-06
• First R01 application due: 2026-06-05 (5:00 PM local time)
• recurring cycles: 2026-10-05, 2027-02-05, 2027-06-05, 2027-10-05, etc.
• Expiration (program): 2029-03-06

The NOFO explicitly encourages early submission because technical correction windows can close quickly.

Practical timeline for a 2026 June cycle

If you target June 5, 2026:

1. Now–March

   • Confirm eligibility and institutional registrations,
   • build concept paper with scope and impact statement,
   • assemble PI team and assign writing roles.

2. April

   • finalize project idea and mapping to NOFO-specific priorities,
   • prepare data strategy and dissemination plan,
   • pre-check for duplicate application conflicts.

3. May

   • draft full SF424(R&R) components,
   • add explicit benchmark/evaluation plans,
   • internal compliance review against NIH page limits and appendix constraints.

4. Early June

   • dry-run submission,
   • final PI signature readiness,
   • submit with contingency for error correction.

This schedule is ambitious but realistic if roles are assigned early.

Application process and submission mechanics

The NOFO allows the standard NIH options:

• NIH ASSIST,
• institution system-to-system,
• Grants.gov Workspace,
• plus eRA Commons tracking.

Paper applications are not accepted.

Mandatory preparation before submission

• complete organizational registrations (SAM/eRA Commons/Grants.gov),
• ensure PD/PI Commons credentials are in place,
• include correct entity and PI identifiers,
• confirm no prohibited foreign subawards are built into your budget.

NOFO-specific preparation points

The call is explicit about open science expectations:

• include a resource-sharing plan,
• make method/software outputs discoverable,
• plan for broad dissemination and reproducibility,
• include robust metrics and use-case framing,
• document benchmarking and validation carefully,
• include maintenance and downstream use considerations.

The requirement to share data/resources is not optional here. This is one of the strongest signals reviewers use to separate serious proposals from purely internal tool builds.

Application instructions that are easy to trip over

• strict NIH page limits still apply,
• software/tools licensing policy should enable redistribution and adaptation,
• appendix is limited to a narrow set of allowed materials,
• human-subjects workflow, clinical data safety, and review sections must be internally consistent.

Review criteria and reviewer expectations

Reviewer scoring follows NIH standards but with NOFO-specific emphasis. Three review factors matter most:

Factor 1: Importance of research (significance + innovation)

Reviewers evaluate how well the problem addresses real barriers, whether it fills a meaningful gap, and whether the concept is genuinely novel or repurposes existing approaches in a substantive way.

Factor 2: Rigor and feasibility

This is where many proposals fail if overly aspirational. You need:

• clear experimental design,
• valid control logic where relevant,
• robust statistical or computational methodology,
• clearly justified sample size and data quality strategy,
• explicit metrics and reproducibility safeguards,
• and concrete plans to handle failure modes.

Factor 3: Investigator and resources

The PI credentials need to show capability, and the institution must be able to support computing, data access, and governance requirements.

NOFO-specific overlays

Reviewers specifically check:

• whether tools are scalable and generalizable,
• whether benchmarking and comparisons are planned,
• whether risks and limits are addressed transparently,
• and whether product maintenance/long-term stewardship is planned.

Non-response risk

Because this is a targeted NOFO, projects not centered on clinical informatics scope can be rejected without full review. That is why alignment language in the project aims is critical.

Common mistakes and how to avoid them

1) Treating this as a generic AI grant

If your application reads like “we build an AI thing,” with no direct clinical workflow and no translation pathway, it may be scored as weakly aligned. Anchor to clinical informatics use cases, outcomes, and integration constraints.

2) Building a software-only narrative with weak validation

A frequent failure mode is building a technical demo without a validation plan grounded in real-world constraints. Reviewers expect reproducibility, benchmarking, and usage evaluation.

3) Ignoring open dissemination

The NOFO repeatedly stresses wide dissemination, resource-sharing, and software availability. Silence on this is risky.

4) Underestimating compliance requirements

Many teams underestimate the registration burden and technical submission requirements. Missing SAM/eRA Commons prerequisites can delay submission and break compliance windows.

5) Substituting broad theory for scoped objectives

“Transform healthcare data” is too broad. Reviewers respond better to a narrow, measurable claim: one or more clinical settings, one or more target populations, and explicit transfer pathway beyond one pilot.

Preparation checklist before you submit

Use this as a practical self-audit:

• Confirm this is a fit with NLM’s focus on clinically relevant informatics methods.
• Map each objective to scalability and generalizability.
• Include a clear project timeline and risk register.
• Add benchmark datasets/validation plan with metrics.
• Specify data security and privacy handling where non-controlled-access data are used.
• Add a resource-sharing plan (code/data, where applicable) with access model.
• Confirm budget items under $250K direct/year and 4-year max timeline.
• Verify no foreign subawards/subcontracts conflict with NOFO policy.
• Align clinical-trial classification and corresponding human-subjects info.
• Perform pre-submission compliance check in ASSIST/eRA Commons/Grants.gov.
• Submit ahead of deadline to allow for validation fixes.

Frequently asked questions (FAQ)

Does this NOFO support clinical trials?

Yes. The announcement is clinical-trial optional. You can propose trials or non-trial studies.

Is there a fixed number of awards or total budget cap?

The NOFO says number of awards depends on appropriations and merit pool quality. It does not list a fixed single total budget amount.

Can non-US organizations apply?

Yes, some non-domestic entities are included in eligible organizations. But NIH will not accept awards involving foreign subawards/subcontracts under this NOFO, so collaborations need careful structuring.

What if I want to submit more than one application?

Allowed if each is scientifically distinct. NIH has overlap safeguards, so don’t submit near-duplicative applications simultaneously.

What happens after submission?

Applications first undergo technical and compliance checks, then peer review (relevance, merit, feasibility, resources), then NIH-level second-level review and funding decisions based on score, funds, and fit.

Official links and contact points

• Official NOFO: https://files.simpler.grants.gov/opportunities/131fabad-5506-431b-b87a-e564f1d8dcc4/attachments/61b6dce0-ffe6-4f50-b863-07b2ce70c1bf/PAR-26-042-Full-Announcement.html
• Submission systems: ASSIST, institutional S2S, or Grants.gov Workspace via NIH instructions
• Application submission and compliance help: eRA Service Desk and Grants.gov Support Center
• Scientific contact: NLMExtramural Programs ([email protected])
• Peer review contact: [email protected]
• Program grants management: [email protected]

Why this opportunity is strategically valuable right now

If your team’s work sits at the intersection of healthcare data, AI methods, and cross-setting transferability, this is one of the clearest NIH pathways for method development in 2026/27. The constraints are strict enough to force discipline ($250K direct/year), and broad enough to support meaningful translational work in hospitals, clinics, and research settings.

In contrast to narrow disease-specific calls, this NOFO can support generalizable informatics work if you can show a reusable core and a pathway to adoption. In short: teams that present strong engineering + methodological rigor + open dissemination plans and realistic execution are exactly the teams this NOFO was built for.

The practical edge is that this is recurring, so you are not forced into a single-year panic launch if your team misses June. You can target the October or February cycles, provided the proposal remains timely and compliant.

PAR-26-042 is therefore a credible 2026/2027 opportunity for groups that can demonstrate breadth, depth, and execution maturity in clinical informatics.