What is ARPA-H?
The Advanced Research Projects Agency for Health (ARPA-H)
ARPA-H is a U.S. federal health research agency funding high-impact, high-risk, high-reward projects to deliver transformational health solutions faster than traditional models. Modeled after DARPA, ARPA-H accelerates breakthroughs that are difficult to support through standard NIH mechanism. Visit their website for a list of ARPA-H Submission Resources and FAQs. If you have any questions, please contact KUMC Research Development.
What Does ARPA-H Fund?
ARPA-H uses the "Other Transactions" (OT) agreement mechanism, which is more flexible than a grant and allows for faster, milestone-driven, negotiated contracts. Funding opportunities include:
- Programs focusing on specific challenges driven by ARPA-H priorities: Short submission turnarounds, ~60 days after issuing.
- Mission Office Innovative Solution Openings (ISO): Similar to a Broad Agency Announcement (BAA), ARPA-H solicits bold ideas from PIs that they may turn into a new program. Open longer/year-round/accepted on a rolling basis.
- Initiatives and Sprints: Special efforts designed to move from proposal to funding in a few months.
Across all funding opportunities, ARPA-H prioritizes:
- Bold, high-risk, high-reward projects
- Translational and real-world application driven
- Revolutionary platforms, systems, technologies and solutions
- Broad applicability with short timelines
- An even-footing partnership teaming approach as opposed to a prime awardee/subaward(s) model
ARPA-H Key Takeaways
ARPA-H vs. NIH
How ARPA-H differs from traditional NIH funding mechanisms
| Dimension | ARPA-H | NIH |
|---|---|---|
| Who drives the agenda? | ARPA-H program managers drive programs. ISO calls may receive PI ideas and turn them into a new program. | Investigator-initiated; PIs propose their own research questions. |
| Mechanism | Other Transaction (OT) agreement — milestone-driven, negotiated contract with clear go/no-go decision points. | Grants and cooperative agreements with annual progress reports. |
| Fast and Flexible | Rapid execution; product/outcome driven, not incremental research. | Longer review cycles; incremental science is acceptable. |
| Scope | Full-scale development: proof-of-concept through deployment readiness. | Typically funds discrete research phases. |
| Submission process | Many programs require a Solution Summary first; competitive teams are invited to submit a full proposal or pitch directly. | Full application submitted to a study section for peer review. |
Full-Scale Development Pathway
Funding Opportunities
Three primary mechanisms for engaging with ARPA-H
Pitching Your Capabilities at Proposer's Day
Most ARPA-H funding opportunities involve a Proposer's Day, where program information is shared and entities discuss their capabilities, gaps, and capacities to make teaming connections. Project teams may also be invited to speak directly with ARPA-H.
Aggressive Program Timelines
ARPA-H programs are milestone-driven with aggressive, clearly defined checkpoints
Unlike NIH grants which report progress annually, ARPA-H programs are structured around technical milestones with explicit go/no-go decision points. Teams must demonstrate measurable progress at each milestone or risk program discontinuation. The example below illustrates a simplified 24-month program timeline.
Example (simple):
Demonstrate assay sensitivity at X threshold
Validate in Y sample set
Demonstrate reproducibility across Z sites
Product built out and ready
Design Thinking Mindset
ARPA-H expects teams to demonstrate a clear design thinking approach throughout the program lifecycle:
The Heilmeier Catechism
The framework ARPA-H uses to assess every proposed research program
ARPA-H relies on the Heilmeier Catechism to ensure clarity of vision, feasibility, cost, and impact for every proposed program. Every proposal should be able to answer these ten questions clearly and concisely.
Strong Proposal Attributes
What ARPA-H looks for in competitive teams and proposals
Attributes That Strengthen an ARPA-H Proposal
- A bold vision and strong technical background
- Comprehensive interdisciplinary team and partners
- Strong leadership and clearly defined execution plan
- Commercialization expertise
- Capability to scale, pivot, and take the project to its end goal
- Clear metrics for milestones and success
- Demonstrated success (prior platforms/proof-of-concept/infrastructure)
Metrics For Success:
- A clearly defined end product
- A robust team and teaming approach, including technical leads, a project manager, and engineering, product design, data/computational/software, clinical validation, manufacturing, commercialization, and deployment capabilities
- Evidence of a design thinking mindset:
Design ➤ Build ➤ Test ➤ Iterate ➤ Validate ➤ Scale ➤ Commercialization ➤ Deployment
Before Committing
Questions to answer before deciding to pursue an ARPA-H program
Given the intensity and pace of ARPA-H programs, teams should carefully evaluate readiness before committing. Work through the following questions with your team and RD.
- Do the proposed PIs and research team demonstrate a strong track record aligned with ARPA-H expectations, including peer reviewed publications, prior funding, industry or cross sector partnerships, and translation relevant outputs (e.g., tools, technologies, products)?
- Can the PIs and research teams prioritize their focus on the ARPA-H program for a minimum of 24 months?
- Does this opportunity align with, and complement, the professional timelines, goals, and incentives of the PIs and key team members?
- What is the product? Who will use this/how? Why is this only possible now? What are the milestones?
- What happens if a key technical or operational assumption fails? What are the fallback strategies or pivots?
- What is the go/no-go decision point to submit a Solution Summary?
Next Steps
How to move from interest to submission