Why compliance-first matters for NEMT operations
The data is sensitive by default
In non-emergency medical transportation, the link between a person and a trip is the thing that makes ordinary-looking data sensitive. A vehicle identifier, a license plate, a pickup address, or a trip purpose can each become protected health information the moment it is tied to a rider's medical context. That is not an edge case in this industry. It is the normal case.
Plenty of operations tools were never built with that reality in mind. They store everything in one place, give every user broad access, and add security controls later if a buyer asks. In a regulated domain, that order is backwards.
Compliance as a design point
A compliance-first posture starts by acknowledging that in NEMT, almost every workflow involves PHI, and then designing every component to handle it properly. In OneOps, PHI is assumed pervasive across the HIPAA-eligible GCP substrate. The design response is per-customer and per-feature project isolation, not a PHI-free zone.
That posture shapes the schema, the access model, and where inference runs. Every agent and workflow gets a minimum-necessary, task-scoped, audit-logged view of PHI. No component holds a blanket read on the data store. The platform runs uniformly on Google Cloud under a Business Associate Agreement, so adding a new service or agent does not require re-evaluating where it sits in a PHI boundary topology.
What that buys an operator
When compliance is built in, the controls a buyer asks about are already part of the design: per-project isolation, minimum-necessary PHI access at the agent layer, append-only audit logging for reads, writes, and agent tool calls, encryption in transit and at rest, and least-privilege connector tools that are explicit about what they can change.
These are posture statements, not audited production claims. The point is that the architecture is pointed in the right direction from the start, so the conversation with a careful buyer is about evidence, not about a redesign.
