Compliance-first by design
PHI is assumed pervasive across the HIPAA-eligible GCP substrate. Isolation is per-customer and per-feature GCP project, with minimum-necessary, task-scoped, audit-logged agent access.
A posture built around PHI
PHI is assumed pervasive across the substrate. The design response is per-project isolation and minimum-necessary agent scoping, not a PHI-free zone.
PHI is treated as pervasive
In NEMT and related healthcare transportation, almost every workflow involves protected health information. The platform is built to handle it directly with proper controls, not to route around it.
Isolation per customer and per feature
The coarse blast-radius guarantee is a dedicated GCP project per customer and per feature area. A problem in one project does not automatically affect another.
Minimum-necessary agent access
Every agent, workflow, and connector gets a least-privilege, task-scoped, audit-logged view of PHI. No component holds a blanket read on the PHI store.
Encryption at rest and in transit
Data is encrypted in transit and at rest across the substrate. Customer-managed keys give key-kill capability and key-use auditing.
Least-privilege connector tools
Connector tools are annotated read-only or destructive, so agents request only the access a task needs and destructive actions are explicit.
Defense-in-depth program posture
MFA, SSO, automatic deprovisioning, idle and absolute session limits, and a documented breach playbook are part of the program design.
The HIPAA-eligible substrate
The entire platform runs on Google Cloud under a Business Associate Agreement. Every service that touches trip, rider, or health-linked data is treated as a PHI surface.
Google Cloud
The HIPAA-eligible cloud for the platform, covered under a single Business Associate Agreement across all customer and feature projects.
HIPAA-eligible
Cloud SQL
Managed Postgres with private IP, CMEK, and PITR. Row-level tenant scoping enforced at the database layer.
PHI store
Gemini Enterprise Agent Platform
Managed inference for agent and BI workloads, kept inside the Business Associate chain. PHI never leaves the project boundary.
BAA inference
Per-project isolation
A dedicated GCP project per customer and per feature area, with an API-layer boundary designed to contain the blast radius of any one project.
Blast-radius isolation
Controls and approach
A posture summary, not a list of audited production facts. These describe how the platform is designed to handle each control area.
| Control area | Approach |
|---|---|
| Identity and access | MFA enforced, SSO and SAML, automatic provisioning and deprovisioning, idle and absolute session limits. |
| Data isolation | Per-customer and per-feature GCP project isolation. Row-level tenant scoping within a project. |
| Audit logging | Append-only audit trail for PHI reads, writes, and agent tool calls, written through a single helper path. |
| Encryption | TLS in transit, CMEK at rest with key-kill capability, customer-managed key auditing. |
| Agent safety | Minimum-necessary, task-scoped access per agent call. Connector tools annotated read-only or destructive. Inference routed under a Business Associate chain. |
| Incident response | Documented contingency activation, deprovisioning SLA, patch SLA, and breach notification playbook. |
| Vendor management | Business Associate Agreements tracked across the substrate and ancillary vendors before any live PHI flows. |
Compliance is the first conversation, not the last
If HIPAA posture is what your team asks about first, let us walk you through how OneOps is built around it.