The exam produces codes, the codes a claim, the claim a payout — today that crosses five intermediaries and takes 90 days. shteg.ai makes it one ledger, one gate, one rail.
Verified in code today; the dollar and PHI wait on named approvals — see the register.
Between a coded ophthalmology encounter and a dollar in the practice's account sit an EMR vendor, a clearinghouse, a payer's adjudication, an RCM service, and a payments processor — each renting you a slice, none accountable for the whole. The record fragments across systems, the money takes weeks, and no single ledger can tell you which exam field earned which dollar. shteg.ai was built to close that gap on purpose.
Encounter, code, claim, remittance, payout — held in a single hash-chained, double-entry ledger the practice owns. Because the clinical record and the settlement rail live in the same system, a settled payout can be traced back through a deterministic compliance gate to the specific signed exam field it came from. That is an audit trail no stack of separate vendors can assemble after the fact.
one system · one ledger · one day.
The product is a single system with four layers that share one hash-chained ledger: the sovereign rails that move money, the compliance gate that authorizes it, the ophthalmology-first clinical record that originates it, and the practice economy that surrounds it.
Provider legitimacy is not a report you read after the fact — it is a condition of settlement. A deterministic gate checks six conditions in conjunction, including a live OIG-LEIE and NPPES exclusion screen, a 276/277 duplicate-claim check, and NCCI coding validation. If any one fails, the instruction stops. Above everything sit a kill-switch and a database-level halt. Compliance is inside the money path because that is the only place it cannot be skipped.
Kill-switch and DB-halt sit above all of it.
Automation suggests — a coding level, an appeal draft, a device-to-chart merge. A human disposes, on every clinical and money path, with no exceptions. Unconfigured integrations return typed refusals and make zero network calls; production never simulates success. The gate is fixed; vendors are swappable. And we keep an honest status register.
Fail closed, everywhere.
Propose, never dispose.
The gate is fixed; vendors are swappable.
Honest status registers.
Everywhere else you will read “AI-powered, seamless, end-to-end, live.” Here is our register instead. Verified-green: the ledger, the settlement gate, the reconciliation waterfall, the clinical cockpit, the interop layer — real code, tested at HEAD. Gated: the movement of a real dollar and the flow of real PHI, which wait on named legal and banking approvals — bank sponsorship, BAAs, credentialing, a money-transmission opinion. We would rather tell you that than sell you a number we made up.
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.
Point one authenticated POST at the settlement gate for an encounter and read back a typed disposition — GATE_EVALUATED, passed or halted, with the first condition that failed named. No happy-path stub, no simulated success: the same fail-closed contract you get in production. Read the docs to run it against your own encounter.
# Evaluate the six-condition settlement gate for one encounter.
curl -X POST https://api.shteg.ai/api/settlement/gate/enc_8f21c \
-H "Authorization: Bearer $SHTEG_SESSION" \
-H "Content-Type: application/json"
# 200 OK — a disposition, never a fabricated pass
# {
# "code": "GATE_EVALUATED",
# "passed": false,
# "status": "halted",
# "firstFailed": "provider_screened"
# }