One platform. Six brands. Zero stored procedures. A modern multi-tenant SaaS that replaces legacy AdminConsole / ClientConsole / Client Central stacks at roughly one-tenth the cost of running the same workload.
Every business rule — claim scrub, modifier injection, group-size adjustment, COB cascade, denial categorisation, EVV validation — lives in TypeScript services with content-addressed YAML rule artifacts. Eight rule-set kinds span the whole pipeline.
The customer ships the change; engineering does not.
A single edi-gateway centralises 270/271, 276/277, 278, 837P/I, 835, 999, TA1, and 834 across every tenant. Routing rules are declarative; replay is a UI button; companion-guide validation is live-previewable from a Monaco editor.
“We lost a batch” becomes a click, not an incident.
EMR and EHR partners register themselves via the federated SSO trust registry: RFC 7519 JWTs, RFC 7517 JWKs, staged → active → superseded → revoked key lifecycle. Revoke propagates across every running instance in under 30 seconds.
One self-service registration replaces a custom integration project.
There is no row-level security. Tenant isolation is physical — one PostgreSQL database per customer, connection strings sealed in Azure Key Vault, never persisted in the master DB.
Routing is subdomain-based, brand selection follows the URL, and tenant resolution happens at the API edge before any business code runs.
It is structurally cheaper, structurally faster, and structurally more flexible than any legacy platform — because the architectural choices remove the categories of work that drive legacy cost.
Three paths through the dossier — pick the one that matches what you want to verify.
