Leading Frontend for a US Healthcare Platform

The problem

MatchRite Care needed three applications — a patient portal, a provider portal, and a mobile app — built in parallel, by a small team, in a domain where the cost of a bad release is measured in patient trust rather than bounce rate. There was no established frontend architecture, no shared UI language between the apps, and no delivery rhythm the business could plan around.

Healthcare adds constraints most products never face: strict privacy expectations around patient data, users who span every age group and ability level, and integrations with clinical data sources that don't behave like clean REST APIs.

The decisions

One architecture, three surfaces. Rather than three independent codebases drifting apart, I designed a shared foundation — a common UI kit, shared API client patterns, and consistent state-management conventions — so a fix or a pattern learned in one app transfers to the others. The patient and provider portals share components; the React Native app shares the design language and the API layer.

Accessibility as an architectural requirement, not a checklist. Patients include elderly users, low-vision users, and people navigating by keyboard or screen reader. Semantic HTML, focus management, and contrast were built into the component library itself, so product screens inherit accessibility instead of retrofitting it.

A delivery cadence the business could see. I introduced clear release rhythms with R&D spikes timeboxed and separated from committed work, so stakeholders could tell the difference between "we're exploring" and "this ships on Friday."

Mentoring as a multiplier. Code review standards and pairing were aimed at making the team's median output safer, because in healthcare the weakest merge is the risk profile.

The outcome

Three production applications sharing one coherent frontend architecture, shipped and iterated on a predictable cadence. The portals run as installable PWAs with a consistent UI kit across patient and provider experiences, and the accessibility baseline is built into the components rather than audited in after the fact. The role has since grown from frontend lead into owning solution architecture and API integration across the product — the clearest sign the foundation held.