MDClarity · mined from the SQL
What the legacy pipelines actually compute
Typed task names (LoadVisits, BatchProcessAccounts) say what step runs; the meaning lives in the SQL those steps execute. These are the business concepts mined from the SQL text itself — the coverage-status gate, the good-faith estimate, the underpayment math — and which pipelines compute each. Pick one to see the actual SQL steps (with plain-language glosses) that implement it.
concepts · 8
Computed concepts
Ordered along the revenue cycle. Colored by where they belong —Flow front-of-house vs RevFind back-office. Bar = share of the 53 scheduled pipelines whose SQL computes it.
Derives Active / Inactive / Failed coverage from the eligibility result — the gate that decides who gets a letter.
Computes the patient's good-faith cost estimate / patient responsibility.
Groups procedures into bundles for the estimate.
Encodes which visits should NOT get a letter (the do-not-send rules).
Loads fee schedules / contracted rates for expected-reimbursement modeling.
Models what the payer should have paid.
Detects denials, short-pays, and underpayment variance — the core RevFind output.
Procedure-code / modifier logic (pricing, grouping, or filtering by CPT).
payers · 9
Payers named in the SQL
A business dimension the typed model never exposes: which payers each pipeline's SQL references — mostly RevFind contract / underpayment work. Bar = number of pipelines naming the payer.