shteg.ai documents its build in public because the doctrine demands it. De-theatricalization and honest status registers only mean something if the work behind them is legible — so we write up the real commits, the real dated milestones, and the bugs the discipline caught. Every post below is grounded in git history and specs in the current build. No invented releases, no fabricated volume, no live-money claims we have not earned.
RSS feedNewest first. Each write-up is anchored to git history and specs in the current build — the discipline made public.
A variance report is not money. It is a list of arithmetic disagreements between what a payer allowed and what your contract says it should have allowed — and most practices that build one discover within a month that ha
Read the postHere is the uncomfortable part of payer underpayment: the remittance that shortchanged you is arithmetically correct. Every segment ties out. Your practice management system posts it without a warning, the claim closes,
Read the postMost "HIPAA-compliant payment link" pages tell you to use encryption. You already use encryption — every link you send is TLS, and has been for a decade. That is not where these systems leak.
Read the postPatient responsibility is the slowest-moving dollar in most practices, and the usual explanation — patients don't pay — is mostly wrong. The dominant failure is upstream of the patient: the practice asks for the wrong nu
Read the postPatient responsibility is the slowest-collecting line in most practices' AR, and the reason is structural rather than behavioral. The instrument you use to ask for it — a printed statement, or an SMS containing a link to
Read the postThe statement cycle is a 30-day loop with three costs attached to it: a print-and-postage cost, an inbound-call cost, and a reconciliation cost that shows up later because a check or a card payment arrives detached from
Read the postDays in AR is the most-cited number in practice financial reporting and the least standardized. The formula is stable — total AR divided by average daily charges — but every input in it is a choice, and no two practices
Read the postA practice manager looking at 38 days in A/R usually assumes the money is stuck somewhere in the banking system. It is almost never stuck there. Under standard ACH, the payer's credit clears in one banking day; the other
Read the postYour AR total is not a debt. It's an inventory of four different things that happen to be denominated in dollars, and each one closes through a completely different action. One of them isn't a receivable at all and shoul
Read the postMost practices post remittances at the claim level: the payer says the claim paid $102.40, someone posts $102.40, the balance moves, the account closes. The file that produced that number contains four to five times more
Read the postThe payer decided on Thursday evening. The money arrives Monday morning. Nothing happened in between — no review, no additional edit, no human looked at the claim again. Three days of your working capital sat still becau
Read the postEvery practice manager has run the same report: total AR divided by average daily charges, and the number is higher than it should be. The usual response is to work the aging bucket — call the payer, refile, escalate. Th
Read the postMost practice management systems can download an 835 and post a payment. Very few can tell you why the payment was what it was, line by line, in a form you can act on the same day. The gap between those two capabilities
Read the postYour clearinghouse drops an 835 in the morning. It contains a deposit amount, a trace number, and a batch of adjudicated claims. Somewhere inside is the answer to the only question the front office actually needs: what d
Read the postEvery practice that collects at the front desk is running an estimator, whether or not anyone calls it that. "Copay's twenty dollars." "You've got a high deductible, so let's take a hundred." "We'll bill you." Those are
Read the postA patient approves a $141.20 balance at 8:14 AM on a Saturday. Whether that money is in your operating account by 8:15 AM or on Wednesday afternoon is not a function of how motivated your billing staff is. It is a functi
Read the postA card transaction has three separate events that practices routinely collapse into one word: authorization, clearing, and funding. The patient sees approval at 4:52 PM Friday. The practice management system marks the ba
Read the postEvery patient balance request is a disclosure. The moment your system asks a patient for $55.00, it has told someone that this person received care, from you, on a date, at a price. That is protected health information,
Read the postA patient balance has two clocks. The first runs from the encounter to the moment you know the exact amount the patient owes — that clock is controlled by the payer, and it stops when the 835 posts. The second runs from
Read the postMost practices treat patient balance collection as a persistence problem. Statement one, statement two, statement three, then a phone call, then an agency. Ninety days of cycle time before anyone has a real conversation,
Read the postPatient responsibility is the slowest-collecting line in an independent practice's A/R, and the reason is architectural, not behavioral. By the time a patient balance is knowable, the practice has already waited for adju
Read the postSearch "same day claim settlement" and you will get pitches from four different kinds of company. A clearinghouse, a bank, a factoring firm, and a payments platform will all use the phrase, and they are describing four p
Read the postA deposit tells you how much. It does not tell you what for.
Read the postReal-time settlement solves transit. It does not solve identification.
Read the postMost FedNow explainers written for physicians stop at "payments settle in seconds." That sentence is true and nearly useless, because it describes the network and not your practice. FedNow is plumbing. Whether water come
Read the postThere is one interval in your revenue cycle that no payer controls, no coder touches, and no clearinghouse edit affects: the gap between the moment a payer's adjudication engine finishes and the moment the money is spend
Read the postYour payer finished adjudicating on Thursday evening. The deposit shows up Monday morning. In between, nothing happened — no reviewer looked at the claim again, no edit fired, no additional information was requested. Thr
Read the postIf you've looked at "instant payments" for your practice, you've probably hit the same wall: the pitch says money in seconds, your AR aging report says 41 days, and nobody explains where the other 41 days went.
Read the postEvery physician-platform pitch deck opens with a shortage number nobody can trace. We went to the primary source instead — the BLS Occupational Outlook Handbook — and the real numbers say something more useful than the slide does.
Read the postWe migrated the claim, remittance, and wallet spine off floating-point dollars and onto integer cents — and the compiler-invisible unit change surfaced three latent 100x bugs that were already in the tree.
Read the postOur EMR sync had a callback that could exchange a code for tokens — but nothing that ever sent the clinician to the vendor's consent screen. We built the authorize leg, and made it refuse rather than fake a connection.
Read the postAn OIG-excluded or unlicensed provider's claim should never originate money. So provider legitimacy isn't a report you run alongside billing — it's a fail-closed condition inside the one gate that authorizes every advance.
Read the postA solo operator running a fleet of AI agents rebuilt this system in a six-day, 310-commit sprint. The reason the output didn't collapse into fiction is the doctrine the codebase enforces on itself.
Read the post'The code exists and is tested' is a different claim than 'it runs in production moving real money.' We keep those two claims separate on purpose — and we publish which is which.
Read the postDeterministic architecture, governed by explicit compliance gates.
Every clinical and financial surface is built on a hash-chained WORM double-entry ledger, a six-condition settlement gate, and an integer-cent 835 reconciliation waterfall under a registered HIPAA clearinghouse and Type-2 organizational NPI. Integrations without active counterparty credentials or executed BAAs fail closed by contract.