The Department of Veterans Affairs is soliciting industry input for a single technology integrator to help restructure how veterans’ health care data and business processes operate across the department.
Integrator will stitch together clinical, community and financial data
In a request for information posted on the federal contracting portal, the Veterans Health Administration outlined plans to establish an enterprise integration, data and measurement layer that would unify information flowing among the VA’s dual electronic health records, its reorganized Community Care Network and associated federal financial systems. The agency is accepting industry responses through Oct. 2.
The move is part of a broader shift toward a value‑based, accountable care model for veterans, officials said in the solicitation. The integrator would not replace departmental ownership of architecture or data standards; instead, the VA intends to retain ultimate control over its target architecture, canonical data models and associated intellectual property while relying on contractor delivery expertise.
- Scope: Build a cohesive integration, data and measurement layer across clinical, community and financial domains.
- Ownership: VA keeps rights to target architecture and canonical data models; vendor provides implementation capability.
- Timeline for industry feedback: Responses due by Oct. 2, according to the RFI notice.
The VA described current veterans community care capabilities — such as eligibility determination, scheduling, claims processing and referral management — as “loosely coupled” systems that require redundant data entry and offer limited shared analytics. The integrator’s work is intended to reduce duplication, improve data flow and support new performance measurement tied to accountable care goals.
Operational complexity: concurrent enterprise transitions
The solicitation warns that the integrator will need to operate within multiple, ongoing enterprise transitions rather than provide a one‑time replacement. Among the structural challenges the VA highlighted is the sustained coexistence of different electronic health record environments at scale, creating interoperability and governance complexities that the integrator must navigate.
| Challenge | Implication for integrator |
|---|---|
| Sustained coexistence of multiple EHR environments | Must enable data exchange and consistent analytics across platforms |
| Fragmented community care systems | Consolidate eligibility, scheduling, claims and referral data flows |
| Integration with federal financial systems | Link clinical and administrative data to support accountability and measurement |
The RFI further indicates the VA intends to maintain control of the target architecture and canonical models while contracting implementation expertise. That approach is aimed at preserving the agency’s ability to govern data standards and measurement over time.
Where this fits in federal health IT priorities
The VA’s request arrives as federal health agencies are wrestling with how to balance modernization, data governance and vendor partnerships. The Potomac Officers Club’s announced Healthcare Summit on Dec. 3 in McLean, Virginia, is slated to convene leaders from the Veterans Health Administration, Department of Health and Human Services and the Defense Health Agency for panels on topics including AI governance and federal health data strategy, offering industry a venue to hear more about evolving priorities.
By seeking a single integrator, the VA is signaling a desire to reduce fragmentation that officials say inhibits analytics and coordinated care across community partners. How the department defines success — including measurable outcomes, data stewardship policies and procurement terms — will determine whether the integrator model accelerates or complicates the agency’s transition to an accountable care operating model.
Industry respondents to the RFI will have an opportunity to shape the VA’s subsequent procurement strategy, including technical approaches, staffing models and proposed governance frameworks. The department’s decision to retain ownership of architecture and canonical data models suggests future contracts will emphasize implementation and collaboration rather than transfer of control.
Responses to the RFI must be submitted by the published deadline on the federal contracting portal.
