Codify — Article

VA bill creates scheduler portal for Veterans Community Care appointments

Requires the VA to build an IT program allowing VA employees to book covered veterans with participating community providers, with regulatory, outreach, and reporting requirements and a seven‑year sunset.

The Brief

This bill directs the Secretary of Veterans Affairs to establish an information‑technology program that allows a VA scheduler to arrange appointments for covered veterans with non‑Department health care providers who opt in to the program. The system must let schedulers find and book available appointments, transmit referrals or authorization documents to community providers, and perform other functions the Secretary deems necessary.

The change shifts some appointment initiation and booking authority into a VA‑managed, IT‑enabled workflow intended to reduce friction between VA and community providers. The statute requires the VA to issue implementing regulations and to run an outreach campaign for provider participation, builds in regular reporting to congressional veterans’ committees, and sunsets the program after seven years.

At a Glance

What It Does

Requires the Secretary to create, within one year, an IT program through which VA schedulers may view, search, sort, and schedule appointments with participating non‑VA providers under the Veterans Community Care Program and to transmit referral/authorization documents electronically. The Secretary must issue regulations and a directive to use the system when practicable, encourage provider participation via an outreach campaign, and report specified metrics to Congress.

Who It Affects

Directly affects VA schedulers and medical centers, non‑Department providers that participate in the Veterans Community Care Program (those that choose to opt in), and covered veterans who receive community care. It also implicates VA IT, provider contracting/enrollment teams, and congressional oversight staff.

Why It Matters

Centralizes scheduling for community care into a VA‑driven, IT‑mediated workflow—potentially speeding access and improving visibility into community appointments but also creating integration, training, and provider‑participation challenges. The bill creates a temporary, reportable experiment (7‑year sunset) with frequent congressional reporting to track outcomes.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill amends existing law to create a new VA program that lets a VA scheduler—using an information technology system—directly book a veteran into an appointment with a community provider who participates in the Veterans Community Care Program and elects to join the portal. Participation by non‑VA providers is voluntary: the statute asks the Secretary to encourage providers to opt in and to publish a publicly accessible website explaining how to do so and who to contact inside the VA.

Operationally, the system must give schedulers the ability to view, search, and sort available appointments (by care type, location, date), to schedule appointments, and to send referral or authorization documents directly to the community provider. The Secretary may add other functions as necessary and is instructed to use an existing agreement to implement the program where practicable—an acknowledgement that some implementation will rely on preexisting contracts or partnerships.The bill sets short regulatory and outreach timelines: it requires issuance of implementing regulations and an employee directive within 90 days of enactment, and commands an outreach plan and public materials aimed at drawing providers into the program.

It also builds in multiple reporting checkpoints: near‑term transmittals of determinations, a copy of the regulations and outreach plan, and then an 18‑month evaluation followed by semiannual reports for five years that must include provider participation counts and disaggregated appointment numbers. Those reporting requirements are intended to let Congress monitor adoption and operational effects.Practically, the measure also makes technical changes to codify the new program into title 38 (as section 1703H) and contains conforming editorial amendments.

The program is explicitly temporary: it terminates seven years after enactment, making this a finite policy experiment rather than an open‑ended operational mandate.

The Five Things You Need to Know

1

The Secretary must establish the scheduler IT program within one year of enactment and may implement it through an existing agreement if practicable.

2

Within 90 days of enactment the Secretary must issue regulations and a directive telling medical center employees to use the system to schedule community‑care appointments “whenever practicable.”, The VA must run an outreach campaign within 90 days and publish a public website that explains program details, how providers elect to participate, and a Department point of contact.

3

Congressional reporting: the Secretary must submit near‑term copies of determinations, the regulations, and the outreach plan, then an 18‑month report and semiannual reports for five years containing provider participation counts and appointment data disaggregated by scheduling pathway, service category, and month.

4

The program automatically terminates seven years after enactment (sunset provision).

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Subsection (d)(1)-(3)

Establishes the scheduler IT program and core functions

This provision requires the Secretary to stand up, within one year, an IT program that lets VA schedulers book appointments with non‑Department providers who opt in. It specifies the minimum functional scope: view/search/sort appointment inventory by care type/location/date, schedule appointments, and transmit referral/authorization documents directly to community providers. The subsection also authorizes the Secretary to add other necessary functions and directs implementation through an existing agreement where practicable, signaling reliance on current contracting vehicles or vendor relationships.

Subsection (d)(4)

Regulatory directive and employee use mandate

The Secretary must promulgate regulations within 90 days and include a directive that medical center staff use the new IT system instead of the prior process whenever practicable. That creates an early, department‑wide operational shift: local schedulers will be instructed to prefer the portal, but the statute preserves practical discretion through the “whenever practicable” qualifier—important for facilities with local constraints or partial provider participation.

Subsection (d)(5)

Provider outreach and public materials

The statute compels the VA to plan and carry out an outreach campaign to encourage community providers to participate in the scheduler program. The VA must publish a publicly accessible web page with program details, steps for providers to elect participation, and a point of contact. This is a low‑cost statutory lever to boost enrollment; its effectiveness will hinge on how actionable the enrollment process is for small practices versus larger health systems.

2 more sections
Subsection (d)(6)

Reporting requirements to congressional committees

This section imposes a structured transparency regime: 30‑day transmittals for certain determinations and for the regulations and outreach plan, plus an 18‑month operational report and semiannual reports for five years on program activity. The semiannual reports must include the number of participating community providers and appointment counts broken out by whether VA or the new program scheduled the appointment, service category, and month—data designed to measure adoption and operational impact.

Subsection (d)(7) and Codification

Sunset and technical placement in title 38

The program is time‑limited and terminates seven years after enactment. The bill also moves the amended provision into subchapter I of chapter 17 in title 38 (to be codified as 38 U.S.C. §1703H) and makes conforming edits to headings and cross‑references. Those codification steps are administrative but signal that Congress intends this as a formal addition to the Veterans Community Care statutory architecture, albeit for a defined period.

At scale

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

  • Covered veterans who need community care — they may gain faster access when VA schedulers can directly book community appointments and transmit authorizations without requiring the veteran to navigate multiple systems.
  • VA schedulers and medical center scheduling teams — they receive a consolidated tool to find and book community appointments, which can reduce back‑and‑forth and improve visibility across VA and participating community slots.
  • Congressional oversight and VA leadership — the statute’s reporting cadence provides structured operational data (provider participation, disaggregated appointment counts) to assess whether community‑care scheduling improves access.
  • Participating non‑Department providers that opt in — they can receive direct referrals and authorization documents from VA schedulers, potentially shortening referral timelines and reducing administrative overhead for handling VA referrals.
  • Care coordination teams and third‑party administrators — improved electronic transmission of authorizations and appointment data can streamline patient handoffs and reduce missed or duplicative authorizations.

Who Bears the Cost

  • Non‑Department providers that elect to participate — they may face integration costs (EHR/scheduling interface work), changes to intake workflows, and potential technical support burdens to accept electronic referrals from VA.
  • Small or solo practices — those with limited IT staff will likely bear a disproportionate share of the onboarding burden relative to larger health systems, creating a participation barrier.
  • VA IT and implementation teams — standing up the portal, integrating with existing VA systems, maintaining interfaces, and supporting users will require funding, project management, and ongoing operations resources.
  • VA medical facility staff — clinics will need training, change‑management support, and time to transition scheduling workflows, which could temporarily reduce productivity during rollout.
  • Privacy, security, and compliance teams — transmitting referrals and authorization data to external providers increases responsibilities for data governance, consent handling, and secure exchange.

Key Issues

The Core Tension

The bill pits two legitimate goals against each other: speed and coordination of community‑care access through centralized, VA‑driven booking versus provider autonomy and the practical costs of technical integration—improving access by centralizing booking can streamline care for veterans but requires community providers and VA operations to absorb integration, training, and data‑security costs that may slow or limit adoption.

The bill sets up a useful operational experiment but leaves important implementation questions open. Provider participation is voluntary, so the portal’s value depends on sufficient community buy‑in; if many providers decline to opt in, schedulers will still need to use legacy processes, reducing the program’s impact.

The “existing agreement if practicable” language eases procurement but creates uncertainty about which contracts will govern the rollout and whether additional contracting will be required for broader interoperability.

Interoperability is a major technical risk. Community providers use diverse EHRs and scheduling systems; building secure, reliable interfaces to allow live inventory viewing, booking, and transmission of authorizations is nontrivial and can be costly.

The directive to use the system “whenever practicable” balances centralization against local constraints, but the statute does not define practicability or provide fallback processes, which could produce inconsistent adoption across facilities. Finally, the reporting requirements generate transparency but also administrative overhead; the metrics chosen (participating providers, disaggregated appointment counts) measure inputs and activity but may not capture patient outcomes like wait times or clinical continuity.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.