Claims are routed by the company that owns the track — scrubbed, sent as an 837, and reconciled as an 835 on the same ledger that settles the money.
shteg.ai is a registered HIPAA clearinghouse with its own Type-2 organizational NPI — a covered entity, not a reseller of someone else's connection.
No claim has yet routed and no real dollar has moved — the standing and the routing code are real, and the register below says which.
Most stacks rent a clearinghouse relationship and mark it up. On this rail the 837 out and the 835 back reconcile on the same hash-chained ledger, tied to the signed exam field, in integer cents.
One system carries both the claim record and the money rail — no reconciliation gap for a middleman to hide inside.
Payer connectivity is an executor, not a dependency — shteg.ai routes through its own registration or across partner clearinghouses by configuration. What never moves is the six-condition settlement gate and the WORM ledger beneath it.
A clearinghouse of record is a position other practices route through, not a feature bolted onto an EMR.
The wedge is built; the network is the work ahead — we are honest that this is the design, not yet the reality.
We will not quote claim counts or a practice roster, because none exist. The register says what is verified-green and what still waits on a named gate.
No real dollar has moved. No real PHI has flowed.
What is real: the architecture — hash-chained ledger, settlement gate, and reconciliation waterfall, tested in code at HEAD — the Type-2 organizational NPI and registered HIPAA clearinghouse identity, and the doctrine. We register capability as capability, never as traction.