RFA-AR-27-002: HEAL INITIATIVE: INTERACT Data Coordination and Integration Center (U24 Clinical Trial Not Allowed)

RFA-AR-27-002: HEAL INITIATIVE: INTERACT Data Coordination and Integration Center (U24 Clinical Trial Not Allowed)

Opportunity snapshot

This call is an NIH HEAL opportunity in the official HEAL funding list under open Funding Opportunities with opportunity ID RFA-AR-27-002. The row identifies the opportunity title as HEAL Initiative: INTERACT Data Coordination and Integration Center, activity type U24, research area Data Dissemination & Secondary Analysis, and closing date in October 2026.

At minimum, this is a 2026/2027-cycle opportunity and the timing places it in planning windows for late-2026 applications and 2027 award execution or data ecosystem follow-on use.

What this opportunity actually offers

HEAL RFA-AR-27-002 is for a Data Coordination and Integration Center (DCIC) structure rather than a typical lab-level biological discovery grant. The program is meant to support infrastructure, standards, harmonization, and integration work that helps transform pain-associated datasets into interoperable research assets.

This is a meaningful distinction:

• it is not a grant for a single hypothesis-driven experiment package in one disease model;
• it is not only one lab collecting a new cohort;
• it is about centralizing data processing and cross-dataset integration in ways that other researchers can use.

For teams, the opportunity changes what “good science” looks like in the application. Strong teams should be able to explain:

1. Their architecture plan for integrating heterogeneous datasets.
2. Their governance plan for metadata quality, provenance, and versioning.
3. Their access model for downstream users and policy alignment for NIH- or HEAL-aligned data sharing.
4. How outputs feed research reuse, reproducibility, and translational discovery across consortium stakeholders.

Because this is a U24 cooperative agreement, NIH is not only funding a project; NIH staff and project leadership are expected to have substantial interaction, with shared oversight and programmatic coordination.

Why this is relevant for 2026/2027 planning

The listed close date in the NIH opportunities page is in the near term for teams in 2026. In practice, that means teams should treat this as:

• a near-live strategic opportunity for planning this autumn;
• a chance to shape center-level assets ahead of 2027 publication and implementation cycles;
• a candidate for groups that want a role in cross-program data infrastructure rather than purely bench-only work.

The practical upside in a 2026/2027 cycle is that a center awarded in this area creates long-lived value:

• it improves discoverability and reuse of pain research outputs;
• it lowers fragmentation across datasets that would otherwise remain siloed;
• it supports a broader ecosystem beyond one project and one institution.

For teams asking “is this too large/institutional for us?”, the more useful question is “can we contribute to interoperability and reproducible data infrastructure at a consortium-compatible level?”

Who this is for and who it is not for

This call is clearly not a conventional PI-only pilot program. It is a candidate for organizations with serious data architecture capability and operational discipline.

Strong fit profiles

• institutions with data science, biostatistics, pain biology, and information management expertise;
• groups experienced with harmonization standards and longitudinal or multimodal research datasets;
• centers that can operate at technical coordination scale (ingestion pipelines, quality control workflows, metadata standards, controlled vocabularies);
• organizations that have prior experience with federal data stewardship, publication expectations, and consortium communication.

Profiles that are likely weaker fits

• groups proposing only a small single-site study without plans for scalable integration workflows;
• teams unable to support FAIR-aligned documentation and governance;
• teams that assume NIH will provide unlimited scope, no reporting, or no governance requirements.

The official listing text indicates a broad set of domestic applicant types on similar HEAL pages (higher education, nonprofits, governments, for-profits), but your success will be gated by whether the proposed work is truly a DCIC-scale activity and whether your team can show consortium-grade execution.

Eligibility, scope, and legal/compliance boundaries

The only clearly visible official constraints are:

• it is a U24 opportunity;
• clinical trials are not allowed;
• HEAL framing includes pain data coordination and secondary analysis context;
• foreign organizations are generally excluded in NIH HEAL pages of this class.

Because the complete NOFO text is not publicly retrievable in the current session (the official page references the Grants.gov workflow), use only confirmed constraints from accessible official sources for now:

• do not assume foreign entity eligibility;
• treat domestic registration requirements as mandatory where applicable to U.S. federal grant submission;
• do not include clinical-trial activity in scope.

At submission time, always confirm:

• whether your specific entity type is eligible;
• whether any collaborative partner structures change eligibility obligations;
• any restriction on non-domestic components in budget and subcontracting;
• whether NIH HEAL-specific review criteria include data-sharing obligations beyond generic NIH standards.

Practical preparation strategy (what to do in the next 90 days)

A U24 center application is mostly about readiness. The scientific idea must be strong, but readiness determines whether your narrative survives scrutiny.

Days 90–75: Program alignment and architecture draft

• Read the HEAL row and any linked NOFO updates for the exact latest scope language.
• Translate your current data capabilities into a one-line “problem → integration strategy → deliverable” model.
• Identify at least one painful interoperability gap your team can solve quickly (terminologies, QC pipelines, harmonized variable maps, missing provenance).

Days 75–60: Team and governance blueprint

• Define a core team: lead PI, data architect, statistics/analytics lead, and governance point of contact.
• Build an explicit authority map: which group owns standards, which group validates data quality, and who is accountable for release cadence.
• Prepare a governance statement that explains how the center will handle requests from external researchers while remaining compliant.

Days 60–45: Registration and compliance

• Confirm NIH-required registrations for your institution early.
• Map internal legal/compliance review dependencies to avoid last-minute bottlenecks.
• Validate your organization’s eligibility class and any cost-sharing constraints.

Days 45–30: Proposal architecture

• Write a high-integrity Specific Aims narrative:
  • Aim 1: harmonization and integration workflow
  • Aim 2: quality assurance and provenance standards
  • Aim 3: access and reuse model for the broader HEAL research community
• Make sure no section depends on clinical outcomes if clinical trials are disallowed.
• Prepare measurable milestones (datasets integrated, pipelines validated, release artifacts, metadata coverage).

Days 30–14: Technical annex and consistency pass

• Standardize metadata templates and repository naming conventions.
• Build a reviewer-facing implementation chart with timeline, risks, and mitigations.
• Verify all figures, tables, and workflow diagrams are self-contained and not dependent on missing external files.

Days 14–0: Submission controls

• Run a final technical-compliance pass against any official checklist available from NIH/Grants.gov at the time.
• Build slack for server issues in eRA/Grants channels.
• Prepare backup submission strategy and monitor status updates.

Application process and submission mechanics

The HEAL listing points applicants to Grants.gov for workflow and status updates. In practice, this means the standard NIH electronic route is expected. The practical implications:

• use the Grants.gov application workflow expected for NIH opportunities,
• keep internal documents versioned and labeled to the exact opportunity number,
• and prepare enough internal proofing to avoid missing mandatory fields.

For RFA-AR-27-002, the planning should prioritize three layers of readiness:

1. Programmatic readiness: is your narrative squarely within data coordination/integration and no clinical trial claims;
2. Institutional readiness: registrations and compliance are already complete;
3. Operational readiness: release plan, governance, and quality control are realistic.

Proposal design: how reviewers usually evaluate this type of center

A reviewer for this kind of opportunity is usually checking three questions:

• Does this center reduce fragmentation and increase reusability?
• Can the team actually deliver harmonization at scale with verifiable quality controls?
• Is this proposal scientifically and technically coherent with clear milestones and governance?

You should therefore emphasize:

• concrete data harmonization outcomes,
• clear quality-control standards,
• reproducibility and provenance workflows,
• explicit plans for how the broader HEAL/NIH user base benefits.

A weak but common pattern is to present a technically impressive stack without equally strong governance design. For a DCIC, governance is not optional: it is the central product. Your methods section should read like an operational operations plan, not only a computational workflow.

Common mistakes and how to avoid them

1) Treating this as a classic laboratory grant

A U24 center is not judged like a single PI discovery project. Reviewers expect ecosystem-wide impact, not only internal publication output.

2) Under-specifying data governance

If your proposal does not explicitly address provenance, versioning, and harmonization policy, it may read as an IT project rather than a NIH-compatible research infrastructure program.

3) Scope creep beyond secondary analysis

Clinical trial components are not part of the opportunity call, and misaligned scope here can invalidate the application.

4) Ignoring interoperability constraints

A data center that cannot map vocabularies, metadata, and access semantics across studies underperforms in review even if its algorithms are strong.

5) Weak readiness assumptions

Many teams discover too late that federal registration and system setup are incomplete. For a high-deadline window, this is fatal.

6) Vague collaboration model

Saying “we will partner with consortia” is not enough. Reviewer confidence rises when there is a defined structure: leadership cadence, governance committee, and clear deliverables.

Budget and effort planning when amounts are not yet confirmed

Because the exact funding amount and budget caps are not confirmed in the accessible official page snapshot used for extraction, this proposal should keep budget strategy flexible while staying realistic.

Build budget plans around:

• data platform engineering (integration, harmonization, validation);
• quality assurance and documentation workload;
• metadata and repository-related costs,
• staff time for governance, release operations, and collaboration support;
• dissemination and reporting support consistent with NIH requirements.

If no cost-sharing is required per the center NOFO section (often the case, but verify at official publication), design a budget that is robust but restrained, with clear role-level cost justification.

Key evidence you should collect before submission

Because this is a data infrastructure call, evidence quality is in your process design. Before submission, assemble:

• Evidence of prior harmonization work: examples of handling heterogeneous datasets or multi-modal data.
• Demonstrated data governance maturity: previous SOPs, metadata workflows, and QA standards.
• Consortium communication plan: how you coordinate with PI teams, NIH partners, and downstream users.
• Sustainability logic: not only “we can build this,” but “we can maintain this for the award period and transition outputs into reuse.

If any one of these is missing, reviewers may view the opportunity as high-risk operationally.

Frequently asked questions

Is this a grant or another mechanism?

It is a U24 cooperative agreement under NIH HEAL, not a standard R01-style grant. That means NIH expects active project/program involvement.

Is this for clinical trials?

No. The listed call language says clinical trials are not allowed.

Is the amount confirmed?

The exact dollar amount and full detailed budget structure could not be validated from the accessible pages used in this pass. The front matter keeps amount empty to avoid guessing.

Who can apply?

Use the official listing and NIH notices for the definitive entity list on the posting you submit against. Broad NIH guidance commonly includes academic, nonprofit, government, and for-profit categories, but eligibility confirmation should be based on the active NOFO text.

Is this still useful for 2027 planning?

Yes. A near-term award in late 2026 for a coordination center typically sets up outputs and collaboration infrastructure that can be used throughout a 2027 research cycle.

Official links and next actions

Primary source for opportunity listing and deadline context:

• NIH HEAL Funding Opportunities

Official opportunity listing referenced in the NIH row:

• HEAL INTERACT Data Coordination Center listing

Grants workflow and application status for NIH opportunities are generally handled via Grants.gov:

• NIH opportunities page entries on Grants.gov

Next steps you should take before submission:

1. Open the active official NOFO link from the Grants.gov workflow and confirm the latest budget, award limits, and eligible registrant list.
2. Finalize a data-governance framework with explicit roles and release rules.
3. Confirm internal registration completion and submission window logistics well ahead of deadline.
4. Prepare a submission package that mirrors the review logic for a data-coordination center.