A service-request platform routing work across a county and 400+ partner organizations.
The situation
A county government and a network of provider organizations needed one place to receive, route, and track service requests that cross jurisdictional and organizational lines. Requests involving people’s services can carry sensitive information, so privacy considerations couldn’t be bolted on later — they had to shape the architecture from the start.
What I built
- Automated request routing that moves each request to the right jurisdiction and organization without manual triage.
- Provider matching, so requests land with organizations actually equipped to handle them.
- Audit trails for operational review — who touched what, when — designed with compliance review in mind.
- HIPAA-aware safeguards throughout: minimum-necessary data collection, role-based access, and logging decisions documented so a compliance team can evaluate them.
Why it holds up
Multi-organization platforms live or die on the boring parts: access control that matches how organizations actually share work, audit capability that satisfies review without burying staff, and interfaces that staff with every level of technical comfort — and every kind of assistive technology — can use. Those were treated as requirements, not polish.
In production and in daily use across the county’s partner network.