- VA is seeking a health systems technology integrator to support its shift toward a value-based, accountable care model for veterans
- The integrator would be responsible for unifying data across VA’s dual electronic health records, its restructured Community Care Network and its financial systems
- VA is accepting industry responses to the RFI through October 2
The Department of Veterans Affairs has issued a request for information seeking a health systems technology integrator to support the Veterans Health Administration’s transition toward an accountable care operating model.
As VA works to modernize how it exchanges data across VHA, community care partners and federal financial systems, the Potomac Officers Club’s 2026 Healthcare Summit offers a closer look at where federal health IT priorities are headed. The Dec. 3 event in McLean, Virginia, brings together leaders from VHA, HHS and the Defense Health Agency for panels on AI governance and federal health data strategy. Sign up to join the conversation!
What Is the VA Requesting Through This RFI?
According to the solicitation posted on SAM.gov, the VHA is establishing the Office of Veterans Community Care to consolidate policy, operations and financial accountability for community care delivered by non-VA healthcare providers.
Current veterans community care capabilities, including eligibility determination, scheduling, claims processing and referral management, rely on loosely coupled systems with redundant data entry and limited shared analytic functions.
To resolve these limitations, the VA is looking for an enterprise integrator to build a cohesive integration, data and measurement layer. Under the initiative, the department intends to retain ultimate ownership of its target architecture, canonical data models and underlying intellectual property while leveraging vendor implementation expertise.
What Operational Shifts Must the Future Integrator Navigate?
VA’s draft materials detail three concurrent, large-scale enterprise transitions that the selected integrator must operate within rather than bypass.
These ongoing shifts include the sustained, multi-year coexistence of Oracle Health’s federal electronic health record alongside the legacy VistA system extending into the early 2030s, the consolidation of the Community Care Network from five regional networks down to two managed by third-party administrators and the phased rollout of the Integrated Financial and Acquisition Management System across the department.
VA notes that roughly 40 percent of its care is currently delivered through community providers, underscoring the scale of the integration challenge.
What Objectives Would the Health Systems Technology Integrator Support?
The draft statement of objectives outlines 10 program areas the integrator would be expected to support:
- Enterprise integration architecture and data governance
- Member identity, eligibility and attribution
- Multi-EHR and community clinical data interoperability
- Financial systems and payment integration
- Semantic normalization and reference data
- Quality, cost and performance measurement
- Artificial intelligence enablement and governance
- Workflow orchestration across organizational boundaries
- Security, privacy and authorization to operate
- Transition-in, knowledge transfer and transition-out
A central focus is financial and payment integration, with VA seeking experience tying claims and encounter data to its general ledger through systems such as CGI’s Momentum platform, the same technology underpinning VA’s iFAMS financial modernization effort. The artificial enablement objective is paired with governance requirements consistent with VA’s broader AI adoption strategy.
Additionally, the integrator will be responsible for semantic normalization, quality/cost measurement capabilities, cross-boundary workflow orchestration and strict security compliance under FedRAMP and VA authority to operate frameworks.
How Can Contractors Respond to the RFI?
The VA is soliciting feedback on its proposed acquisition strategy, technical testing parameters, and capability-transfer models to refine requirements before issuing a formal solicitation. Submissions are due by Oct. 2 at 12:00 PM EDT and must be sent electronically to Division Chief Gary T. Basile at gary.basile@va.gov.
The market research initiative is classified under NAICS code 541512 (Computer Systems Design Services) and Product Service Code DA01. Input gathered from vendor submissions will directly shape the structure, contract type and potential live technical demonstration requirements for subsequent procurements.
