Lesson · 20 min

What Medical Billing and Coding Actually Is

Understand the two distinct jobs behind the title, how they relate, and why a clinic cannot get paid without both being done well.

By the end of this lesson you can

Explain the difference between medical coding and medical billing
Describe how a clinical encounter becomes a paid claim
Name the parties involved in a healthcare transaction and what each one wants
Explain why coding accuracy is a compliance issue and not only a payment issue

📘 Reading Lesson

Lesson Notes

Read through the key concepts before you try the challenge.

Two jobs, one title

On the job

You are starting as a billing specialist at Lakeside Medical Associates.

A patient sees Dr. Okafor for persistent knee pain. The visit lasts twenty minutes, the provider examines the knee, orders an X-ray, and diagnoses osteoarthritis. Clinically the encounter is finished. Financially nothing has happened at all — and unless someone translates that visit into a specific set of codes and sends it to the right payer in the right format within the right window, the practice will never be paid for it.

Your task: Understand the pipeline that turns a documented visit into money in the practice's account, and where you sit in it.

The job title joins two related but genuinely different roles. A medical coder reads the clinical documentation and translates what happened into standardized codes: a diagnosis code describing the patient's condition, and a procedure code describing what the provider did. A medical biller takes those codes, attaches the patient's insurance information, produces a claim, submits it to the payer, and pursues it until it is paid or properly resolved.

In a large hospital these are separate departments. In a practice the size of Lakeside, one person often does both, which is why the training covers both. The skills differ: coding rewards precision, patience, and comfort with reference material. Billing rewards persistence, organization, and a willingness to make the follow-up phone call nobody else wants to make.

Key terms

Encounter: A single documented interaction between a patient and a provider. Every claim begins with one.
Diagnosis code: A code describing the patient's condition — why care was needed. In the United States these come from ICD-10-CM.
Procedure code: A code describing what the provider did — the service delivered. These come from CPT and HCPCS Level II.
Claim: The formal request for payment sent to a payer, carrying the codes, the provider's identifiers, and the patient's coverage information.
Payer: Whoever is being asked to pay — a commercial insurer, Medicare, Medicaid, or in some cases the patient directly.
Reimbursement: The payment a payer makes for a covered service, which is usually a contracted rate rather than the amount billed.

The pipeline from visit to payment

The sequence below is the backbone of the entire field. Every later module in this program is a detailed treatment of one or two of these steps, so it is worth learning the shape of the whole thing before going deeper into any part of it.

Step	What happens	Who does it
1. Pre-registration	Demographics and insurance are captured and verified before the visit	Front desk
2. Eligibility and authorization	Coverage is confirmed; prior authorization obtained if the payer requires it	Front desk or billing
3. The encounter	The provider delivers and documents care	Provider
4. Coding	Documentation is translated into diagnosis and procedure codes	Coder
5. Charge entry	Codes and charges are entered into the practice management system	Biller or coder
6. Claim scrubbing	The claim is checked against payer rules before it goes out	Billing software and biller
7. Submission	The claim is transmitted, usually electronically through a clearinghouse	Biller
8. Adjudication	The payer decides what to pay, reduce, or deny	Payer
9. Payment posting	Payment and adjustments are recorded against the account	Biller
10. Denial follow-up	Denied or underpaid claims are corrected, appealed, or written off	Biller
11. Patient billing	The remaining patient responsibility is billed and collected	Biller

How an encounter becomes revenue

Notice that steps 1 and 2 happen before the patient is ever seen. A large share of denials trace back to something that went wrong at the front desk — an expired policy, a transposed member number, a missing authorization. Billing problems are very often registration problems that took three weeks to become visible.

Why accuracy is a compliance matter

It is tempting to think of coding as a revenue exercise where higher codes are better. That framing is both wrong and genuinely dangerous. A code is a factual assertion about what happened to a patient, submitted to a payer that may be a federal program. Submitting a code the documentation does not support is a false claim, and the consequences are not limited to the money being recouped.

Error	What it means	Consequence
Upcoding	Reporting a more complex or expensive service than was documented	Overpayment recovery, penalties under the False Claims Act, exclusion from federal programs
Undercoding	Reporting a lower level of service than was documented	Lost revenue, and a distorted record of the patient's care and the practice's case mix

The two ways coding goes wrong

Undercoding is sometimes treated as the safe error. It is not. It misrepresents the care delivered just as upcoding does, it starves the practice of revenue it legitimately earned, and a pattern of it can itself attract attention. The goal is never the highest code or the lowest code. It is the code the documentation supports.

The governing principle of this entire field is one sentence: if it was not documented, it was not done. A coder codes from the documentation, not from what they assume happened, not from what the provider says in the hallway, and not from what would pay better. When the documentation does not support a code, the correct action is to query the provider — never to code what you believe they meant.

Check your understanding

A provider tells you verbally that an office visit involved a detailed examination, but the note in the chart documents only a brief exam. What should you do?

Challenge

Apply what you've learned in this lesson.

Trace a single encounter through the whole pipeline in writing, in your own words.

Invent a straightforward encounter: a patient with a sore throat sees a provider, who examines them and performs a rapid strep test. Write three sentences describing what happened clinically.
For each of the eleven pipeline steps, write one sentence describing what happens to this specific encounter at that step. Where you do not yet know the detail, write what question you would need answered.
Identify the two steps in your list where you think an error would be most expensive to fix later, and explain why in a sentence each.
Write down one question about this pipeline that you cannot yet answer. Keep the list — by the end of this program you should be able to answer it, and checking back is a good measure of your progress.

Finished this lesson?

Progress is saved in this browser only. It is not a grade — official progress lives in Brightspace.

The Revenue Cycle and Where Money Is Lost →