VA taps familiar face as acting health secretary overseeing EHR work

Executive Summary

The Veterans Health Administration (VHA) has appointed John Figueroa as acting Under Secretary for Health following John Bartrum's resignation. This leadership transition places Figueroa in charge of the Federal Electronic Health Record (FEHR) modernization program at a critical point: the program plans to deploy to 19 sites by end of year with full deployment targeted for 2031. The change in senior leadership introduces program continuity and decision-making risk for contractors supporting the multi‑billion dollar EHR modernization effort and related VHA technology initiatives.

Contractors in the listed market segments — Healthcare IT; Electronic Health Records; IT Services; Health Information Technology; IT Modernization; Systems Integration; Cloud Services — should pay attention now because near‑term rollout milestones (19 sites by end of year) may drive procurement, task orders, integration pushes, and compliance gating. Firms with experience in VA/VHA work, the FEHR program, or the relevant compliance regimes should prepare to respond quickly to potential changes in priorities, pacing, or contract scopes tied to the leadership transition.

Impact Matrix

Healthcare IT

• Risk Level: High
• Opportunity: Continued FEHR rollout and broader VHA technology initiatives create demand for Healthcare IT services and program support. Specific NAICS codes and contract vehicles identified in Tags: 541512, 541519, 541330, 518210, 541511, 541715, 611430; vehicles: T4NG, VETS 2, OASIS+, 8(a) STARS III, Alliant 2.
• Timeline: Deploy to 19 sites by end of year; full deployment targeted for 2031.
• Action Required: Reassess resourcing and staffing to be able to bid on near‑term task orders; align proposals to FEHR timelines and emphasize VA/VHA experience.
• Competitive Edge: Demonstrate prior Healthcare IT delivery at EHR cutover scale, include concrete transition-risk mitigation plans and compliance posture tied to the listed compliance surfaces.

Electronic Health Records

• Risk Level: High
• Opportunity: Direct EHR integration, deployment, testing, data migration, and sustainment work tied to FEHR modernization. Specific NAICS/vehicles: see Tags (541512, 541519, 541330, 518210, 541511, 541715, 611430; T4NG, VETS 2, OASIS+, 8(a) STARS III, Alliant 2).
• Timeline: Deploy to 19 sites by end of year; full deployment targeted for 2031.
• Action Required: Prioritize proposals and technical approaches that address phased rollouts, cutover risk, interoperability, and continuity of care during deployments.
• Competitive Edge: Offer phased implementation playbooks, validated migration/testing artifacts, and staffing models for concentrated rollouts to 19 sites and beyond.

IT Services

• Risk Level: Medium
• Opportunity: Systems integration, program management, operations, and sustainment services supporting FEHR and other VHA IT work. Refer to Tags for NAICS/vehicles.
• Timeline: Deploy to 19 sites by end of year; full deployment targeted for 2031.
• Action Required: Ensure bench capacity and task‑order readiness; align service lines to short‑term deployment windows and long‑term sustainment.
• Competitive Edge: Position flexible, rapid‑scale teams and near‑term surge resourcing options that can be tapped for site rollouts.

Health Information Technology

• Risk Level: High
• Opportunity: HIT expertise for interoperability, clinical workflows, and compliance with data protection/regulatory expectations. Tags include relevant NAICS and vehicles.
• Timeline: Deploy to 19 sites by end of year; full deployment targeted for 2031.
• Action Required: Highlight HIT-specific compliance posture (see compliance surfaces) and clinical informatics experience in proposals.
• Competitive Edge: Pair clinical subject‑matter experts with technical teams to reduce clinical risk during EHR cutovers.

IT Modernization

• Risk Level: Medium
• Opportunity: Modernization efforts tied to FEHR deployments across infrastructure, security, and applications. Tags provide potential contract vehicles and NAICS.
• Timeline: Deploy to 19 sites by end of year; full deployment targeted for 2031.
• Action Required: Map modernization offerings to FEHR phases and ensure architectures support interoperability and long‑term sustainment.
• Competitive Edge: Offer modernization roadmaps that reduce lifecycle cost and align to FEHR pacing and sustainment needs.

Systems Integration

• Risk Level: High
• Opportunity: Integration of FEHR with VHA systems, testing, and cutover orchestration. Refer to Tags for contract/NAICS references.
• Timeline: Deploy to 19 sites by end of year; full deployment targeted for 2031.
• Action Required: Prepare integration test plans, end‑to‑end validation capabilities, and cross‑vendor coordination strategies.
• Competitive Edge: Demonstrate prior systems integration at scale with documented cutover success metrics and clear vendor coordination frameworks.

Cloud Services

• Risk Level: Medium
• Opportunity: Cloud hosting, migration, and security services to support FEHR and ancillary VHA workloads. Tags identify compliance surfaces relevant to cloud work (FedRAMP (Federal Risk and Authorization Management Program), FISMA, NIST 800‑53, etc.) and NAICS/vehicles.
• Timeline: Deploy to 19 sites by end of year; full deployment targeted for 2031.
• Action Required: Ensure compliance certifications and cloud service offerings align with VA expectations; ready migration and hybrid/cloud integration plans.
• Competitive Edge: Emphasize compliant cloud baselines, FedRAMP posture, and migration blueprints that minimize service disruption during EHR rollout phases.

Cross-Segment Implications

• EHR deployments will drive coordinated demand across Healthcare IT, EHR, Systems Integration, Cloud Services, and IT Modernization segments — success requires cross‑segment planning and vendor coordination.
• Compliance surfaces listed in Tags (FedRAMP, NIST 800-171 (NIST Special Publication 800-171), HIPAA, FISMA, NIST 800-53) are cross‑cutting requirements that create gating factors for Cloud Services, Systems Integration, and HIT teams; firms lacking clear compliance posture may be removed from consideration.
• Near‑term rollout milestones (19 sites by end of year) create concentrated windows where integration, testing, clinical training, and cloud readiness must align — contractors that can synchronously offer these capabilities will be advantaged.
• Leadership transition increases the possibility of adjusted priorities or pacing; vendors should maintain flexibility across contracting vehicles listed in Tags to follow program-level changes.

```json:

{

"tldr": "The Veterans Health Administration has appointed John Figueroa as acting Under Secretary for Health following John Bartrum's resignation. This leadership transition places Figueroa in charge of the Federal Electronic Health Record (FEHR) modernization program at a critical point: the program plans to deploy to 19 sites by end of year with full deployment targeted for 2031. The change in senior leadership introduces program continuity and decision-making risk for contractors supporting the multi‑billion dollar EHR modernization effort and related VHA technology initiatives. Contractors in the listed market segments — Healthcare IT; Electronic Health Records; IT Services; Health Information Technology; IT Modernization; Systems Integration; Cloud Services — should pay attention now because near‑term rollout milestones (19 sites by end of year) may drive procurement, task orders, integration pushes, and compliance gating. Firms with experience in VA/VHA work, the FEHR program, or the relevant compliance regimes should prepare to respond quickly to potential changes in priorities, pacing, or contract scopes tied to the leadership transition.",

"segments": [

{

"segment": "Healthcare IT",

"risk_level": "High",

"opportunity": "Continued FEHR rollout and broader VHA technology initiatives create demand for Healthcare IT services and program support. Specific NAICS codes and contract vehicles identified in Tags: 541512, 541519, 541330, 518210, 541511, 541715, 611430; vehicles: T4NG, VETS 2, OASIS+, 8(a) STARS III, Alliant 2.",

"timeline": "Deploy to 19 sites by end of year; full deployment targeted for 2031.",

"action": "Reassess resourcing and staffing to be able to bid on near-term task orders; align proposals to FEHR timelines and emphasize VA/VHA experience.",

"competitive_edge": "Demonstrate prior Healthcare IT delivery at EHR cutover scale, include concrete transition-risk mitigation plans and compliance posture tied to the listed compliance surfaces."

},

{

"segment": "Electronic Health Records",

"risk_level": "High",

"opportunity": "Direct EHR integration, deployment, testing, data migration, and sustainment work tied to FEHR modernization. Specific NAICS/vehicles: see Tags (541512, 541519, 541330, 518210, 541511, 541715, 611430; T4NG, VETS 2, OASIS+, 8(a) STARS III, Alliant 2).",

"timeline": "Deploy to 19 sites by end of year; full deployment targeted for 2031.",

"action": "Prioritize proposals and technical approaches that address phased rollouts, cutover risk, interoperability, and continuity of care during deployments.",

"competitive_edge": "Offer phased implementation playbooks, validated migration/testing artifacts, and staffing models for concentrated rollouts to 19 sites and beyond."

},

{

"segment": "IT Services",

"risk_level": "Medium",

"opportunity": "Systems integration, program management, operations, and sustainment services supporting FEHR and other VHA IT work. Refer to Tags for NAICS/vehicles.",

"timeline": "Deploy to 19 sites by end of year; full deployment targeted for 2031.",

"action": "Ensure bench capacity and task-order readiness; align service lines to short-term deployment windows and long-term sustainment.",

"competitive_edge": "Position flexible, rapid-scale teams and near-term surge resourcing options that can be tapped for site rollouts."

},

{

"segment": "Health Information Technology",

"risk_level": "High",

"opportunity": "HIT expertise for interoperability, clinical workflows, and compliance with data protection/regulatory expectations. Tags include relevant NAICS and vehicles.",

"timeline": "Deploy to 19 sites by end of year; full deployment targeted for 2031.",

"action": "Highlight HIT-specific compliance posture (see compliance surfaces) and clinical informatics experience in proposals.",

"competitive_edge": "Pair clinical subject-matter experts with technical teams to reduce clinical risk during EHR cutovers."

},

{

"segment": "IT Modernization",

"risk_level": "Medium",

"opportunity": "Modernization efforts tied to FEHR deployments across infrastructure, security, and applications. Tags provide potential contract vehicles and NAICS.",

"timeline": "Deploy to 19 sites by end of year; full deployment targeted for 2031.",

"action": "Map modernization offerings to FEHR phases and ensure architectures support interoperability and long-term sustainment.",

"competitive_edge": "Offer modernization roadmaps that reduce lifecycle cost and align to FEHR pacing and sustainment needs."

},

{

"segment": "Systems Integration",

"risk_level": "High",

"opportunity": "Integration of FEHR with VHA systems, testing, and cutover orchestration. Refer to Tags for contract/NAICS references.",

"timeline": "Deploy to 19 sites by end of year; full deployment targeted for 2031.",

"action": "Prepare integration test plans, end-to-end validation capabilities, and cross-vendor coordination strategies.",

"competitive_edge": "Demonstrate prior systems integration at scale with documented cutover success metrics and clear vendor coordination frameworks."

},

{

"segment": "Cloud Services",

"risk_level": "Medium",

"opportunity": "Cloud hosting, migration, and security services to support FEHR and ancillary VHA workloads. Tags identify compliance surfaces relevant to cloud work (FedRAMP, FISMA, NIST 800-53, etc.) and NAICS/vehicles.",

"timeline": "Deploy to 19 sites by end of year; full deployment targeted for 2031.",

"action": "Ensure compliance certifications and cloud service offerings align with VA expectations; ready migration and hybrid/cloud integration plans.",

"competitive_edge": "Emphasize compliant cloud baselines, FedRAMP posture, and migration blueprints that minimize service disruption during EHR rollout phases."

}

],

"cross_implications": [

"EHR deployments will drive coordinated demand across Healthcare IT, EHR, Systems Integration, Cloud Services, and IT Modernization segments — success requires cross-segment planning and vendor coordination.",

"Compliance surfaces listed in Tags (FedRAMP, NIST 800-171, HIPAA, FISMA, NIST 800-53) are cross-cutting requirements that create gating factors for Cloud Services, Systems Integration, and HIT teams.",

"Near-term rollout milestones (19 sites by end of year) create concentrated windows where integration, testing, clinical training, and cloud readiness must align — contractors that can synchronously offer these capabilities will be advantaged.",

"Leadership transition increases the possibility of adjusted priorities or pacing; vendors should maintain flexibility across contracting vehicles listed in Tags to follow program-level changes."

]

}

```