What the VA health systems technology integrator RFI is buying, and when responses are due
The VA health systems technology integrator would be one contractor owning the integration, data, and measurement layer under a value-based community care model. VA has not settled that structure. Question H-1 asks whether the scope should be a single award at all. The requiring activity is a new office, the Veterans Health Administration’s Office of Veterans Community Care. RFI No. 36C10G26Q0087 posted September 10, 2026. Responses are due October 2 at noon Eastern. It carries NAICS 541512, product service code DA01, and no set-aside. The attached questions leave the code open.
This is new-business capture, not a retention risk you can attach a contract number to. For a systems integrator or mid-market federal health-IT firm with VA past performance, October 2 is the only shaping date VA has committed to. VA is also asking what contract type fits and how to weight its factors. Those are capture questions.
| Field | Answer |
|---|---|
| Signal | RFI No. 36C10G26Q0087, posted September 10, 2026, with a draft Statement of Objectives and 78 questions |
| BD implication | A pre-solicitation shaping window on a role VA calls new, first input due October 2 |
| Customer | VHA Office of Veterans Community Care, a new office consolidating policy, operations, and financial accountability for non-VA care |
| Buyer | VA Enterprise Procurement Office, Fredericksburg, Virginia. Contact: Gary T. Basile |
| Funding | None identified. Market research only, no ceiling, appropriation, or obligation |
| Vehicle / path | Undecided. A-3 asks which vehicles respondents hold, naming GSA Multiple Award Schedule, GWACs, and T4NG2 |
| Incumbents / ecosystem | VA names no contract this would recompete. Adjacent: the community care administrators, the federal EHR vendor, the financial-system integrators |
| Access strategy | Open to any respondent. A-5 asks you to declare prime, subcontractor, or team |
| Timing | Due October 2, 2026, noon Eastern. Archives 60 days later. No solicitation date |
| Confidence | High on the notice, dates, office, codes, and draft objectives; none on award timing or vehicle |
| Pursuit posture | SHAPE |
| Upgrade triggers | A draft or final RFP, an industry day, or one-on-one sessions |
| Downgrade triggers | VA tabling the effort, or dividing the scope until no integrator role remains |
Three things the notice does not do:
- Commit VA to a solicitation or an award. It says so directly.
- Reimburse response costs, or confer any later advantage.
- Replace the health records or the financial system, or perform third-party administrator functions.
VA ranked financial integration above clinical interoperability
Objective 4 of the draft Statement of Objectives covers financial systems and payment integration. It is the only one of ten carrying a priority sentence. VA calls it of primary importance to the Government. That should reorder how health-IT and IT modernization firms plan a response.
The instinct is to lead with interoperability. VA runs two electronic health records at once, Oracle Health’s federal record and legacy VistA. Full deployment is not expected before the early 2030s. That work sits in Objective 3.
Objective 4 asks for something narrower. Claims and encounter data from the third-party administrators must be normalized at production volume. That includes ASC X12 sets 837, 835, 834, 278, and 270/271. Obligations, accruals, and disbursements must reconcile to the general ledger without manual bridging.
Question C-7 asks for experience with federal financial systems, including CGI Momentum. It also asks about reconciling transactions to a federal general ledger. Objective 4 widens that to “CGI Momentum or comparable federal financial platforms.” Comparable ledger work counts. Delivery also has to accommodate the wave sequencing of the Integrated Financial and Acquisition Management System, or iFAMS, with VHA in a later wave.
I would lead with payer-side claims operations reconciled to a federal ledger. Fast Healthcare Interoperability Resources, or FHIR, and EHR integration are strengths. They answer the objective VA did not flag.
VA wrote the usual integrator lock-in out of this requirement
The usual economics of an enterprise integration award run one way. You own the semantic layer and the measure logic. Three years in, the customer cannot leave. The draft objectives build against it.
| Provision in the draft | What it costs the winner |
|---|---|
| Government purpose or unlimited rights in the data model, mappings, transformation logic, and measure specifications | The switching cost transfers to VA |
| A priced transition-out plan, delivered from the outset and kept current | Exit cost is a proposal line item the winner cannot defer |
| Architecture, mappings, and measure logic in portable form, target 100% | No proprietary format can hold the semantic layer |
Draft Section 6.2 states the posture outright. A solution whose semantic layer or measurement logic is not portable to a successor environment will be viewed as high risk. That is an evaluation penalty, not an exclusion. You can still offer a proprietary measure engine. Price it against the penalty, and state the license terms and the cost of dropping it.
None of this is settled. The document is stamped draft and pre-decisional. Anti-lock-in language routinely softens before a final solicitation. It still reads well for a mid-market integrator. Removing lock-in removes what an entrenched incumbent carries into year three.
VA is screening for size too. Section 9.0 asks for past performance at comparable federal scale. A-4 asks your health-IT integration revenue and its federal share. D-6 puts the footprint at roughly 170 medical centers and 1,000-plus outpatient sites. Weigh that before deciding to prime.
Competitive Landscape: who the disclosure screen reaches, and who it misses
Draft Section 10.0 treats organizational conflict of interest as a substantive evaluation matter under the subpart it cites, RFO Subpart 9.5, not a certification signed at award. The reason is structural. The integrator computes the results that measure other contractors. A-6 asks for, and Section 10.0 would require, disclosure of any affiliation or financial interest in four categories:
- A community care third-party administrator, or an offeror for a community care task order.
- The federal EHR vendor, Oracle Health, or its affiliates.
- Anyone performing claims adjudication, utilization management, or network administration for VA.
- Anyone whose performance would be measured by the integrator’s own deliverables.
Disclosure is not disqualification. Section 9.0 asks for a mitigation plan alongside it. I expect mitigation cost to fall hardest on payer-affiliated and EHR-affiliated firms. Community care runs today through Optum Public Sector Solutions, a UnitedHealth Group subsidiary, in Regions 1, 2, and 3. TriWest Healthcare Alliance holds Regions 4 and 5. VA is consolidating those five into two, East and West, under the CCN Next Generation solicitation. Proposals closed in March 2026 with no award announced. Its winner would inherit a disclosure obligation by pursuing this role.
No firm has publicly declared an intent to bid, and few will before a solicitation. VA does not publish respondent identities at this stage.
Read the four categories for what they leave out. None names a financial-systems integrator by function, while payer and EHR firms are named directly. That is the asymmetry a mid-market respondent should price against. The screen leaves untouched the firms strongest on the objective VA ranked first.
What a response has to contain, and what VA says it will not read
VA is specific about failure modes. A response saying what a firm can do, without saying where it has done it, is of limited value. Material not responsive to a numbered question goes unreviewed.
- Answer using the RFI’s own numbering, A-1 through H-9, and identify any question you skip.
- Reconcile the response summary matrix first. It lists Section H as H-1 through H-10, while Section H stops at H-9. Note that in your own matrix.
- Keep Sections 5.0 through 11.0 of the questions document to 50 pages. Section 4.0 has no page limit.
- Cite engagements by client type, scale, duration, and outcome, and give any figure with its basis.
- Submit by October 2, 2026, noon Eastern, to the division chief named in the notice.
Question C-10 is where I would spend the candor. It asks for a federal health integration engagement that went badly, the cause, and what you would do differently. The question says a candid answer beats a list of successes. Take it literally.
- Capture lead: pick prime, subcontractor, or team per A-5, and inventory every affiliation in the four conflict categories.
- Delivery engineer: assemble B-5 evidence that a computed payment is correct, not merely executed, and state your largest production bulk export for F-2.
- Founder or BD lead: answer Section H, where scope, contract type, and weighting get shaped.
- Specialty vendor or smaller integrator: approach federal health-IT integrators with VA past performance in Sections B, C, and F, and declare it in A-5.
- Anyone with adjacent VA community care, EHR, or financial-systems work: check your own option-exercise dates against the RFI-to-solicitation window.
What would turn this from a shaping move into a pursuit
The VA health systems technology integrator is a shaping target today, not a pursuit. VA has named a buyer and drafted the scope. The questions are open enough that a good response changes the requirement. Nothing is there to pursue: no solicitation, vehicle, set-aside, or funding line is identified. Treating it as a proposal event spends against a competition that does not yet exist.
Three events would move it toward capture:
- A draft or final request for proposals, which converts shaping into a bid decision.
- An industry day or one-on-one sessions, both reserved in the notice.
- A named acquisition vehicle, which tells you whether you need a seat you do not hold.
Two would move it the other way. VA could table the effort after reading responses, which the notice permits. Or it could take the advice invited in H-1 and divide the scope, leaving no single integrator role. Firms holding adjacent community care, EHR, or iFAMS work should watch that outcome. It would redraw the work they hold. For them this stays a scope-boundary watch item and not yet a validated federal contracting opportunity, because the notice names no existing contract as affected.
FAQ
Is this a funded acquisition or just market research?
Market research. VA issued the notice for information and planning only. It is not a request for proposals, not an invitation for bid, and not a commitment to solicit or award. No ceiling, appropriation, or obligation figure is attached. Missing the date forfeits nothing. Failure to respond does not preclude participation.
Does responding here create a conflict if I have a CCN Next Generation proposal pending?
Potentially, and the draft says to disclose rather than avoid. Section 10.0 lists a community care third-party administrator, or an offeror for a community care task order, among the disclosable affiliations. Section 9.0 pairs that disclosure with a mitigation plan. Decide which role you want. The integrator would measure whoever administers the networks.
Do I need a vehicle or a set-aside status to respond?
Neither is required, and VA has not selected a vehicle. A-3 asks which vehicles respondents hold, naming GSA Multiple Award Schedule, governmentwide acquisition contracts, and VA-specific vehicles such as T4NG2. H-3 asks what contract type to recommend. The RFI carries no set-aside. A-5 contemplates a subcontractor or team role. H-8 invites comment on small business participation.
Which existing contractors could see scope absorbed by this role?
The draft names none as affected. Section 3.2 puts four things outside scope: replacing the electronic health records, performing third-party administrator functions, delivering clinical care, and replacing the financial system. Work between those is what the integrator takes. VA calls this a new consolidated role. No single current VA contract covers that scope. Read Sections 3.1 and 3.2 against your own statements of work.
What happens between October 2 and a solicitation?
The notice publishes no schedule. VA reserved the option to hold one-on-one sessions, an industry day, or a draft Statement of Objectives comment period. All are non-exclusive. A later solicitation may incorporate concepts from RFI responses. That is the reason to mark proprietary content by paragraph.
