When Patients Can’t Find the Right Clinic, They Don’t Get Care
Yakima Valley Clinic
3–5 minutes
Key results
Dynamic geotargeting surfaces location-specific clinic information, services, and language availability automatically
40-clinic network unified under one platform with location-specific content routing
Mobile-first, WCAG 2.1 AA platform designed for a predominantly mobile user base
Multilingual architecture built for the patient populations served across Washington and Oregon
Platform migration completed without disrupting patient access across 40 active clinic locations
If This Sounds Like You
You’re running a multi-location healthcare organization. The people you serve need to find the right location, confirm it offers what they need, and know whether care is available in their language — quickly, on a mobile device, often under some degree of stress.
If your site can’t route them to that answer fast, they call the main line and tie up staff, they show up at the wrong location, or they don’t access care at all. For a community health organization, that last outcome isn’t a bounce rate metric. It’s a population health consequence.
You probably also know that your site wasn’t built for this. Location data is static or hard to maintain. Language support is limited or an afterthought. The mobile experience works well enough on a desktop but falls apart on the devices your patients use. And making changes requires more coordination than the internal team has capacity for.
That’s exactly where Yakima Valley Farm Workers Clinic was.
The Situation
Yakima Valley Farm Workers Clinic is a Federally Qualified Health Center operating 40 clinics across Washington and Oregon, serving agricultural workers and underserved communities. Many patients are navigating the healthcare system in a second language, on a mobile device, trying to find which clinic is closest and whether it offers what they need. The platform isn’t a marketing site. It’s clinical access infrastructure.
With 40 locations and services that vary by clinic, the digital challenge is a routing problem as much as a content problem. If the site can’t quickly tell a patient which location serves them, what services are available, and whether care is offered in their language, patients find a workaround or don’t access care at all. For an FQHC, that outcome has real population health consequences.
The existing site wasn’t built for any of this. Location data was static. Language support was limited. The mobile experience was an afterthought. And migrating to a new platform while keeping a 40-clinic network operational, without disrupting patient access during the transition, was a constraint that had to be planned for from the very beginning of the project, not addressed at the end.
What We Did
We rebuilt the site with geotargeting and dynamic location logic at the center: Google Maps integration and real-time geolocation automatically surface the most relevant clinic information based on where the patient is, including services offered, languages spoken, and hours. Patients don’t have to search through a list of 40 locations. The site does the routing for them.
Multilingual support was built as a genuine part of the clinical experience, not a translation toggle. The content architecture was designed for multiple primary languages from the start, reflecting the patient populations served across both states. A patient navigating in Spanish isn’t getting a translated version of an English site; they’re navigating a site built for them.
The entire platform was rebuilt mobile-first and to WCAG 2.1 AA standards. For an organization whose patients are predominantly on mobile devices, in communities with limited reliable desktop access, this isn’t a compliance checkbox. It’s how you reach the people you exist to serve.
The migration was completed without disrupting patient access across 40 active clinic locations. That constraint shaped every decision from the start.
As Yakima Valley Farm Workers Clinic expands its network and services, the platform is built to absorb that growth. New clinics slot in without structural changes.
What This Means for You
If you’re running a multi-location healthcare organization, the routing problem is the core problem. Not design. Not content. The question of whether a patient can get from “I need care” to “I know where to go and what to expect when I get there” in under a minute, on their phone, in their language.
Most multi-location sites are built around the organization’s structure: a list of locations, a general service menu, a language toggle that was added later. That structure made sense when the sites were built. It doesn’t serve patients the way the organizations that built them intend to.
The fix is building the platform around the question the patient is asking, not the information the organization wants to present. It requires different architecture decisions, made earlier in the process, not retrofitted after the site goes live.
If your team knows the site isn’t doing what it should for the people you serve, that’s the conversation worth having.
We work with community health organizations, multi-location healthcare providers, and mission-driven digital platforms on exactly these problems: dynamic location routing, genuine multilingual architecture, mobile-first accessibility, and migrations that keep operations running throughout.
Camber Clemence is a Senior Product Marketing Manager at Nexcess, where she leads performance and managed cloud solutions. Her background in journalism, content, and product marketing helps her communicate complex products clearly.
