The SME landing zone

Capabilities, deeply.

Seven sub-pages designed for the people who will scrutinise whether the platform can actually run their state and their programs. Each carries the diagrams, surface inventories, and verbatim claims that matter for that decision.

Tenant workflows

RCM Application

Every tenant-facing surface: eligibility, claims, members, group sessions, encounters, receivables, authorizations, denials, charges. 22 admin Configuration tabs.

X12 as a service

EDI Engine

Centralized EDI: 270/271, 276/277, 278, 834, 835, 837P/I, 999, TA1. Trading-partner directory, companion guides, routing rules, replay.

No stored procedures

Configuration & Rules

Eight rule-set kinds, content-addressed YAML artifacts, 7+1 scope precedence, effective dating, lifecycle state machine, paste-a-claim simulator.

Canonical catalogs

Master Data

NPPES, CPT, HCPCS, ICD-10, POS, TOB, Revenue, NCCI, CARC/RARC, modifiers, state rate codes, payer registry, Transparency in Coverage.

Built in, not bolted on

Security & HITRUST

TOTP + WebAuthn MFA, federated SSO with key lifecycle, physical tenant isolation, PHI sealed in Key Vault, BCDR with RTO ≤ 1h.

Six brands today

White-Label & Tenancy

Hostname-routed brand selection, physical multi-tenancy, federated integration. New brands onboard in a single day.

The operational model

AI-First Development

Every line of production code was authored by AI agents under a structured roadmap/workplan/session protocol. 234 commits in 50 business days.

Everything an analyst would have asked back-office engineers to do in the legacy system is here.

RCM Application Features

Or zoom out

Choose your verification path.

If you'd rather see the head-to-head against legacy first, or look at the program × state coverage, both paths lead back to the same capability detail.

Side-by-side