Medical coding systems software, for a small practice, is the check between the note and the claim: the tool that reads the codes the clinician or the coder chose and tests them against the edits a payer will apply, the bundling pairs, the modifier rules, the diagnosis-to-procedure policies, the units, before the claim leaves the practice. It is not the code lookup, which is the coder's reference to the code sets themselves, and it is not the coder, who decides what the note supports. This page sets out what the software checks, what it cannot decide, where it sits in a small practice's claim cycle, and what the claims register keeps that it does not.
What the software checks
The procedure-to-procedure edits, Medicare's National Correct Coding Initiative among them, that say which code pairs are not paid together on the same day and whether a modifier can separate them. The medically-unlikely units for a code in a day. The modifier rules per payer. The diagnosis pointers against the payer's coverage policies. The rendering and referring provider fields the claim form requires. A claim scrubbed against those before submission is a claim that does not come back as CO 16, CO 234 or CO 97 a month later.
What it cannot decide
Whether the note supports the code. Software can say that a biopsy and an excision on the same day need a modifier to be paid; it cannot say whether they were on separate sites, which is what the modifier asserts and what the note has to show. A scrubber that adds modifiers to pass the edits, rather than flagging the pair for the coder, is the tool an audit finds later. The practice's coder or clinician decides; the software checks.
Where it sits in a small practice's claim cycle
Between the superbill and the clearinghouse. The superbill from the visit carries the codes and the charges, which the free superbill worksheet on this site totals; the scrubber tests the codes; the claim goes out; the remittance comes back and is posted line by line. Most billing products for small practices carry a scrubber inside them, and the question to ask a vendor is which edit sets it checks and how often they are updated.
What the register keeps that the scrubber does not
The scrubber sees each claim once. The register keeps the claim's whole life: the codes as billed, the denial that came back despite the scrub, the corrected claim, the posted EOB per line, and the pattern across a month that says which edit the practice keeps hitting. The claims cycle worksheet here shows the denial rate the pattern produces; Eobify Pro keeps the lines. Under the HIPAA security rule the software holding those claims is held to the same safeguards as the chart.
Questions people ask about medical coding systems software
Is medical coding systems software the same as a code lookup?
No. The lookup is the coder's reference to the code sets; the coding software checks the codes chosen against the payer's edits before the claim goes out. This site publishes neither a code set nor a lookup.
Does a small practice need separate coding software?
Usually not as a separate product: most billing products for small practices include a claim scrubber. Ask which edit sets it checks and how often they update, and test it on last month's denials.
Can the software choose the codes for a visit?
It can suggest and it can flag, but the code is the coder's or the clinician's decision from the note. Software that assigns modifiers to pass edits without the note's support creates the audit finding it was bought to prevent.
Which edits matter most for a small practice?
The bundling pairs and the modifier rules for the practice's commonest code combinations, and the diagnosis policies of its two or three largest payers. Last month's denial codes on the register say which.