The bill directs the Department of Veterans Affairs to ensure each VA medical facility establishes a formal partnership with a medical facility in a rural area. Partnerships may span telehealth, co-location or leasing arrangements, training, care coordination and emergency services; the statutory purpose is to expand rural veterans' access and reduce costs across partners.
To support implementation the bill gives the Secretary limited waiver authority, requires an initial briefing to congressional veterans and appropriations committees within 180 days, and compels biennial reporting on partnership formation and performance. The proposal creates a compliance timetable and defines key terms, including a RUCA-based definition of “rural.”
At a Glance
What It Does
Requires every VA medical facility to enter a partnership with a rural medical provider and authorizes a range of legal arrangements (leases, MOUs, employment or contractor agreements) to deliver telehealth, co-location, training, care coordination and emergency services. The Secretary can waive the requirement under defined procedures and must brief Congress and later report on operations and outcomes.
Who It Affects
VA medical centers and community-based outpatient clinics; rural hospitals, critical access hospitals, and independent clinics defined by RUCA codes; veterans who live in rural commuting areas; and local transport and emergency providers used in partnership emergency services.
Why It Matters
If implemented, the requirement would institutionalize VA-local provider collaboration as a national policy rather than a voluntary patchwork, driving telehealth scale-up, local capacity-building, and new contractual relationships that could alter how VA delivers outpatient and emergency care in rural regions.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The core mandate directs the VA to pair each of its medical facilities with a rural medical facility using any legal structure that fits—leasing space or equipment, co-location, contracts, memoranda of understanding, employment arrangements, or independent contractor agreements. The partnerships are meant to be flexible: they can expand telehealth capacity, allow VA clinicians to operate in local clinics, place local clinicians in VA settings, coordinate patient care and transport for emergencies, and share training or equipment to reduce overall costs.
Implementation oversight sits with a named VA official and supporting organizational elements the Secretary must describe to Congress in an initial 180-day briefing. That briefing must lay out an implementation timeline, identify the official responsible for oversight, report any task forces or personnel assigned, and provide standardized waiver forms and eligibility criteria.
Operationally, the Department will need to create contracting templates, credentialing pathways for clinicians working across sites, data‑sharing arrangements to connect electronic health records, and reimbursement practices for shared services.The bill creates two reporting tracks: an initial report two years after enactment and biennial updates thereafter. Reports must list new and existing partnerships and evaluate performance using specific measures—changes in regional VA patient enrollment, accessibility comparisons to pre-partnership service levels, documentation of emergent best practices, and regional counts of veterans receiving service‑connected compensation.
Those metrics are meant to show whether local partnership arrangements increase veterans’ access and shift care patterns, but they also require the VA to assemble regional enrollment and claims data and to compare results against a five‑year historical baseline.The Secretary may grant temporary waivers to the partnership requirement for up to five years under conditions the Secretary sets; renewals require evaluation in consultation with the medical facility’s leadership. The statute treats the partnership requirement as additive to existing legal authorities (it explicitly remains separate from 38 U.S.C. 8153) and defines “rural” by the USDA’s RUCA coding system, which will govern which outside facilities qualify.
Finally, the law imposes a three‑year compliance window for existing facilities and the same three‑year clock for any VA facility established after enactment, counted from the date patients are first seen at the new site.
The Five Things You Need to Know
Existing VA medical facilities must be compliant with the partnership requirement or hold an approved waiver within three years of enactment; facilities created after enactment have the same three‑year compliance window measured from the date they first see patients.
The Secretary may waive the partnership mandate for a specific facility for up to five years, but must notify Congress of that waiver not later than 48 hours before it takes effect; renewals require an evaluated need in consultation with the facility head.
The Secretary must provide an initial briefing to the Senate and House Veterans’ Affairs and Appropriations Committees within 180 days that identifies an oversight official, timeline, supporting offices or task forces, and standardized waiver forms and eligibility criteria.
The first required report is due two years after enactment and must, at minimum, list new partnerships and preexisting partnerships and assess outcomes using metrics that include regional enrollment under 38 U.S.C. 1705(a), accessibility comparisons to pre‑partnership services, newly developed best practices, and counts of veterans receiving service‑connected compensation compared to the prior five‑year period.
The statute defines “partnership” broadly (leases, co‑location, MOUs, employment, independent contractor or service agreements) and adopts the USDA RUCA coding system to define “rural”; it also states the new requirements are additional to, and separate from, VA authority under 38 U.S.C. 8153.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Establishes the act’s name as the “Improving Access to Care for Rural Veterans Act.” This is a formal marker that helps practitioners and contracting officers identify implementing guidance and appropriations language tied to this statute.
Mandated partnerships and permitted agreement types
Subsection (a) requires each VA medical facility to enter a partnership with a rural facility and lists permissive forms those partnerships may take—telehealth arrangements, co‑location or leasing, training, care coordination and emergency services including transportation. Practically, this gives procurement and legal teams latitude to tailor agreements to local conditions but also obliges them to develop a menu of standard contract templates, credentialing processes and shared‑services billing arrangements.
Temporary waivers with notice and renewal criteria
Authorizes the Secretary to waive the requirement for a facility for up to five years, subject to Secretary‑established rules, and requires the Secretary to notify Congress before a waiver takes effect. Renewals are limited and conditional: the Secretary must consult with the facility head and evaluate the ongoing need. For operations teams this creates a formal exceptional‑circumstances pathway but also a near‑real‑time congressional notification obligation that can drive oversight and inquiries.
180‑day implementation briefing to congressional committees
Requires an early, detailed briefing to the Senate and House Veterans’ Affairs and Appropriations Committees that identifies the implementation timeline, the official accountable for oversight, any new offices or task forces, oversight plans, and the waiver forms and eligibility criteria. The briefing will set expectations on sequencing and signal whether the VA plans to use existing organizational structures or stand up new program offices.
Biennial operational and performance reports with defined metrics
Directs a report two years after enactment and biennially thereafter covering new and existing partnerships and assessing their success using enumerated measures: regional VA enrollment counts, accessibility compared to prior service levels, best practices and regional counts of veterans receiving service‑connected compensation. Program evaluation and data teams must align datasets to five‑year baselines and agree on measurement approaches to satisfy the statute’s comparative requirements.
Three‑year compliance windows for existing and new facilities
Sets a three‑year compliance timetable for facilities already seeing patients and the same three‑year window for newly established VA facilities measured from the date they first see patients. Operational leaders will have to prioritize high‑need regions and sequence partnership negotiations to meet these deadlines, and they should expect to triage resources for facilities that cannot promptly identify viable partners.
Statutory relationships and key definitions
Declares the new authority is in addition to but separate from 38 U.S.C. 8153 and provides statutory definitions: ‘partnership’ (broadly enumerating agreement types), ‘rural’ (defined by USDA RUCA codes) and ‘service‑connected’ (per 38 U.S.C. 101(16)). These definitions determine eligibility and scope for partnership candidates and will affect data pulls and program eligibility assessments.
This bill is one of many.
Codify tracks hundreds of bills on Veterans across all five countries.
Explore Veterans in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Rural veterans — gain closer, more varied points of care (telehealth and local in‑person options), likely reduced travel time and better emergency coordination; the bill is expressly designed to improve local access and continuity.
- Rural hospitals and clinics — can receive new revenue streams through lease/co‑location, contracted services and training partnerships, and may gain VA telehealth capacity and shared equipment that expand local service offerings.
- VA facilities and regional networks — can offload routine or low‑acuity care to local partners, reduce travel‑burden costs for beneficiaries, and tap local emergency capacity to improve responsiveness in remote areas.
- Local emergency and transport providers — stand to receive more coordinated contracts and funding for transportation and emergency coverage tied to the partnerships, improving response redundancy in underserved regions.
Who Bears the Cost
- VA central administration — must staff an oversight office, produce briefings and regular reports, build contracting templates and run program evaluation, creating a nontrivial administrative and IT cost burden.
- Individual VA medical facilities — must devote legal, procurement and clinical resources to identify, negotiate and operationalize partnerships, and to support credentialing and EHR integration efforts.
- Small rural providers — may face upfront capital, credentialing, documentation and liability‑management costs to meet VA standards, and they may need to expand capacity without guaranteed long‑term reimbursement terms.
- Regional data and analytics teams — will need to assemble and validate five‑year historical baselines, pull 1705(a) enrollment figures and produce comparative analyses for the mandated reports, increasing workload and technical demands.
Key Issues
The Core Tension
The bill forces a choice between a uniform, nationwide mandate that aims to standardize VA access to rural veterans and the practical reality that rural communities vary widely in provider capacity, infrastructure and readiness; achieving scale requires central direction and resources, but heavy central mandates risk imposing burdens on small rural providers and VA sites that lack the funds or local partners to comply.
The bill solves a coordination problem by using a statutory mandate to push VA and rural providers into formal partnerships, but it leaves critical implementation details to VA regulation, contracting practice and internal planning. Funding and reimbursement mechanisms are not specified: the statute allows the parties to enter many kinds of agreements but does not create a dedicated appropriation or set standards for who pays for telehealth infrastructure, shared equipment, or transportation.
That omission raises the risk that local providers will shoulder upfront costs while VA absorbs some downstream savings, creating negotiation friction and uneven rollout.
Operationally, credentialing, malpractice coverage, and EHR interoperability will be the thorniest hurdles. The law authorizes cross‑site staffing and contractor arrangements but does not prescribe credentialing reciprocity, data‑sharing standards, or indemnity rules—each of which has legal and regulatory complexity (state licensing laws, HIPAA and HITECH constraints, and varying malpractice frameworks).
The defined performance metrics in the reporting requirement push the VA toward quantitative measures (enrollment counts and compensation recipients) that are measurable but may not capture nuanced access barriers like appointment wait times, broadband availability for telehealth, or patient experience; agencies could therefore demonstrate metric improvement without delivering uniformly better care.
Finally, the waiver authority and short congressional notice period create governance trade‑offs. Waivers enable pragmatic exceptions where local capacity is missing, but widespread or frequent waivers could produce a patchwork implementation that undermines the statute’s national intent.
The 48‑hour notice to Congress increases transparency but may also trigger rapid oversight interventions that slow otherwise reasonable administrative solutions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.