"Billing" and "coding" get used almost interchangeably in day-to-day practice conversation, and most patients — and more than a few front-desk staff — assume it's one job. It isn't. They're two distinct disciplines that happen to sit next to each other in the revenue cycle, and mixing them up is one of the quieter ways practices end up with denied claims.
Coding is the translation step. A coder takes what happened during a patient encounter — the diagnosis, the procedure, the supplies used — and converts it into standardized codes that payers can process: ICD-10 codes for diagnoses, CPT codes for procedures, and HCPCS codes for supplies, equipment, and certain services.
This is detail work. A coder has to read the provider's documentation closely enough to pick the code that actually matches what was documented — not just what seems close. Miss a modifier, use an outdated code, or code to a level of specificity the documentation doesn't support, and the claim is already compromised before it's ever submitted.
Billing picks up where coding leaves off. Once the encounter is coded, the biller packages that information into a claim, checks it against payer-specific rules, and submits it — then follows up. That follow-up is most of the job: tracking whether a claim was accepted, chasing down denials, resubmitting corrected claims, posting payments, and following up on anything still outstanding.
Where coding is about accuracy at a single point in time, billing is about persistence over the life of a claim — sometimes days, sometimes weeks.
When one person (or one overloaded in-house employee) is expected to do both well, something usually slips — not from lack of effort, but because they're genuinely different skill sets. A great coder isn't automatically a great biller, and vice versa.
Specialty practices feel this especially hard, since accurate coding in fields like behavioral health, orthopedics, or dermatology requires familiarity with codes that a generalist coder may rarely touch.
You don't need to become an expert in either to run a healthy revenue cycle — you need people (or a partner) who are already experts in both, working together instead of one person stretched across both roles. That's the whole premise behind separating billing and coding into distinct, specialized functions rather than treating it as one generic "billing" task.
← Back to all posts