Security
Currently doesn't bolt security on as an afterthought. Dual-database PHI isolation, session-first access control, scope-based data filtering, and full audit trails are baked into every layer of the platform.
Core Protections
From database architecture to application logic to user permissions — security decisions are structural, not configurable.
Protected health information lives in a dedicated Cloud SQL database with its own access controls. The platform database contains only de-identified, anonymized data.
Every request resolves a session with scope, permissions, and data filter before any business logic runs. No role strings scattered through application code.
Database queries are automatically filtered by the authenticated user's scope. A provider user physically cannot query another organization's data.
Every action, transformation, and permission change is logged. Full traceability from raw data input to processed output to user access.
Infrastructure
Built on Google Cloud Platform with defense-in-depth across compute, storage, networking, and identity layers.
Hosted on GCP with Cloud SQL for databases, Cloud Run for compute, and Cloud Storage for file staging. All data encrypted at rest and in transit.
Enterprise-grade authentication with multi-factor support, session management, and organization-level user provisioning. Auth state synced to both databases via webhooks.
All six connectivity types (GCS, S3, Azure, SFTP, FTP, API) use encrypted transport. Credentials stored securely and connection-tested before activation.
Inbound webhooks from Clerk, Stripe, and Linear are signature-verified before processing. No unverified payloads reach application logic.
Service-to-service authentication via API keys with scope-limited access. Keys are revocable and audited independently from user sessions.
The platform database follows data minimization principles — only what's needed for non-PHI operations. PHI stays isolated in the dedicated health data store.
By Design
Isolated Databases
Access Scopes
PHI in Platform DB
Actions Logged
Get started
Start processing HL7 messages, ensure data quality, and enable FHIR-based interoperability — all from one platform.