VA just put CLEAR pods inside six VA medical centers to help Veterans create VA.gov accounts faster. Good. A Veteran dealing with mobility, connectivity, or other challenges should not have to wrestle the internet in the parking lot just to reach care and benefits already earned.
But let us not confuse a green beep with victory music.
VA says the pilot is live in Atlanta, Brooklyn, Orlando, Palo Alto, San Juan, and Washington. The service is free and optional. VA staff help Veterans create the account, and expansion depends on the pilot results. Those are not side details. They are the beginning of the scorecard.
A Faster Front Door Matters
VA.gov is now a working front door for appointments, secure messages, prescription refills, disability claims, travel reimbursement, and other services. VA says a Veteran can use a CLEAR pod with a valid government issued photo ID, a phone number, and a personal email address. Staff assist with the setup, and the process can create the account in minutes.
That can remove a real barrier. It can also create a false sense of completion if the only measure is how quickly the pod produces a successful screen. The technology matters because of what the Veteran can do after the account exists, not because the scanner photographed well in a news release.
The Pilot Has Six Real Tests
Any technology can look like a genius when the demo team controls the room. A pilot is where the equipment meets a busy lobby, a forgotten password, uneven connectivity, staff who already have full jobs, and the one printer that apparently holds a federal appointment. The operating model has to survive Monday morning.
For health technology companies, this pilot points to six practical questions:
Veteran experience: Can the person understand the process and finish it without unnecessary friction?
Staff workload: Who helps when the normal path breaks, and how much time does that support require?
Trust: Do Veterans understand what information is collected, who receives it, and what remains with VA?
Access: Does the new option serve people who struggled with the prior process, or mostly move existing users to a different screen?
Reliability: Does the service keep working in the real environment, across ordinary problems and busy days?
Evidence for scale: What result would justify a seventh site, and what result would send the design back to the workbench?
Trust Belongs in the Operating Model
VA says CLEAR does not receive or access Veterans' personal health information through this account setup process, and participation is optional. VA also says using CLEAR does not change a Veteran's benefits or care. Those statements matter because trust is not the paragraph somebody adds after legal review. It is part of the implementation.
If the Veteran does not believe the process is safe or worth the trouble, the pod becomes expensive lobby furniture. A company entering VA needs more than a privacy statement. It needs a plain explanation, a support path, staff who can answer normal questions, and a response when the person standing at the device says, “I do not understand what happens next.”
Measure the Hallway, Not Just the Scanner
A useful pilot does not merely ask whether the product worked. It asks whether the Veteran journey made sense, whether staff could support it, whether problems were resolved without summoning twelve people to a meeting, whether trust survived the process, and whether the evidence is strong enough to earn the next site.
The scanner produces the green beep. The program has to measure what happens down the hall. Did more Veterans complete account setup? Did they reach the service they needed? Which failures required staff intervention? How long did recovery take? What did Veterans abandon, and why? Did one site succeed because of a local champion or because the model is actually repeatable?
What Emerging Technology Companies Should Learn
A six site pilot is not a miniature national rollout. It is a chance to learn which parts of the model survive variation. The sites will not have identical staff patterns, lobby conditions, Veteran populations, support habits, or daily pressure. That variation is useful if the company and VA agree on what they are trying to learn.
Before asking for sixty sites, a company should know the Veteran use case, the staff owner, the purchasing path, the support model, the data boundaries, the failure process, the measures of value, and the decision rule for scale. “Install it and train somebody” is not an implementation plan. It is a sentence wearing a hard hat.
Questions Worth Answering Before Scale
Industry: If VA gave your company six sites tomorrow, what would you measure before asking for sixty?
VA staff and leaders: Which part of a new front door creates the hidden workload after the demo team leaves?
Veterans: What would make this process feel genuinely easier instead of merely more official?
JhetVet® helps health technology companies define the Veteran use case, assess readiness, map the stakeholders and purchasing path, build the implementation and support model, and decide what evidence must exist before anybody starts talking about scale. Explore our Emerging Health work and how we operate. If your product can ace a controlled demo but the VA path still ends with “install it and train somebody,” let us map what happens down the hall.
