08/26/2026
We are modernizing interoperability everywhere except between the veteran and the systems they’re expected to navigate.
I’ve spent significant time following the VA’s Federal Electronic Health Record modernization effort, particularly as deployment approached Indiana.
The objective makes sense: a veteran’s clinical information should move with them.
VA. Department of Defense. Community providers. One veteran. A more connected record.
At the same time, CMS has pushed the broader healthcare system toward greater interoperability—improving information exchange between payers and providers and creating better continuity as patients move through increasingly complex systems.
But there’s another interoperability problem we aren’t talking about enough:
Human interoperability.
Because interoperable data doesn’t automatically create interoperable services.
A rural veteran can have an accessible medical record and still be asking:
-Is this VA or Community Care?
-Do I need my County Veteran Service Officer?
-Who helps with transportation?
-What if the problem is housing, utilities, accessibility, employment or caregiver support?
And most importantly:
Who makes sure the handoff actually worked?
Our veteran-support ecosystem contains extraordinary organizations, programs, service officers, healthcare providers and community partners.
The problem isn’t always that the resource doesn’t exist.
Sometimes the veteran has effectively been made the systems integrator.
That’s where I believe community-based Veteran Navigators could fundamentally change the model.
Not another VSO. Not someone replacing accredited claims professionals, VA staff, healthcare providers or community organizations.
A Navigator is the human interoperability layer between them.
One accountable person who understands the veteran’s situation, connects each need to the appropriate specialist, creates warm handoffs, follows those handoffs across organizational boundaries, identifies where the system stalled, and stays engaged toward resolution.
Technology already understands this principle:
A system isn’t integrated simply because all of its components exist. Integration requires those components to communicate—and the handoffs have to work.
We should expect the same from the systems serving veterans.
The Federal EHR can help the information follow the veteran.
Interoperability standards can help the data move between systems.
Now we need to make sure the veteran can move through them, too.
That’s the principle behind RIVA’s developing Veteran Navigator model for rural Indiana:
One veteran. One accountable Navigator. Many specialized partners. One documented path toward resolution.
Because a referral isn’t an outcome.
And access isn’t really access if the veteran still has to figure out the system alone.
— Lindsey
Founder & CEO
Rural Indiana Veterans Alliance, Inc.