FREE · SELF-PACED · FOUNDATIONS
Medical Billing & Coding Foundations
Understand the claim journey, coding principles, insurance basics, and responsible follow-up.
8 lessons · 8 practice cases · 15-question final quiz · No sign-up
Free, AI-assisted introductory education. Not an accredited program, professional certification, CE credit, or clinical qualification. No fees, registration, or patient information required.
01The revenue cycle and your role
Learning goal: Trace an encounter from registration to account resolution.
Billing organizes the information needed to request payment and track the outcome. Coding translates supported diagnoses and services into standardized codes. These functions depend on one another, but neither replaces the treating provider’s clinical judgment.
A typical outpatient workflow is registration → eligibility and benefits → required authorization checks → encounter and provider documentation → charge capture and code review → claim submission → payer response → payment posting → follow-up. Tasks may overlap, and each practice assigns ownership differently.
At every handoff, record what is missing, who owns the next action, and the follow-up date. An appointment being completed does not mean its claim was accepted or paid. A useful work queue separates unsubmitted encounters, rejected claims, denied claims, and unpaid accepted claims.
Before taking an action, confirm the account, date of service, payer, and authorized access. Keep an audit trail. Never move a balance to the patient merely to clear a work queue; first verify the remittance, contract, coverage, and applicable billing rules.
Pause and practice
A visit is documented, but no claim appears in the submission report. Is this an unpaid accepted claim?
Show the explanation
Not yet. First investigate charge capture, documentation completion, claim creation, and submission status. Do not begin payer follow-up as though receipt has been confirmed.
02Insurance, benefits, and patient responsibility
Learning goal: Distinguish coverage terms without promising payment.
The subscriber holds the insurance policy; the patient receives the service. They may be different people. Verify identifying information through the practice’s approved process, including the payer and plan applicable to the date of service.
A premium purchases coverage. A deductible is an amount the member may owe before certain plan benefits apply. A copayment is a defined amount for a covered service. Coinsurance is a percentage share. Coverage, exclusions, network status, and out-of-pocket limits depend on the plan and service.
Eligibility means enrollment or benefit information was returned; it is not a guarantee that a particular claim will be paid. Referral requirements, authorization, medical necessity, coding, and timely filing can still affect payment. Authorization also does not guarantee reimbursement.
Simplified example: the allowed amount is $100, the deductible has been met, and covered coinsurance is 20%. The illustrative patient share is $20 and payer share $80. Real accounts may include other adjustments and coordination of benefits. When multiple plans exist, confirm payer order rather than guessing from the insurance cards.
Pause and practice
An eligibility response is active. Can you promise the patient the service is fully covered?
Show the explanation
No. Review service-specific benefits and requirements and explain that the final claim determination may differ. Use the practice’s approved estimate process.
03Terminology, anatomy, and documentation
Learning goal: Read a record carefully and recognize when clarification is needed.
Medical terms often combine a root, prefix, and suffix: cardi/o relates to the heart, hyper- means above or excessive, and -itis indicates inflammation. These patterns help you understand records, but they do not prove a diagnosis. Context and the provider’s documentation control.
Recognize location and laterality: right versus left, upper versus lower, and proximal versus distal. Know the difference between a symptom, a confirmed diagnosis, a historical condition, and a condition explicitly ruled out. Do not convert a medication or an abnormal result into an undocumented diagnosis.
Review encounter date, author, reason for visit, relevant history, findings, assessment, plan, and authentication status. A problem list may contain old or unverified conditions. Copying every problem into a claim can create inaccuracies.
If the note conflicts with itself, use an authorized clarification process. Describe the conflict neutrally and route it to the appropriate provider or coding lead. Do not alter the medical record to obtain a desired payment outcome. Distinguish missing documentation from a payer’s request for existing supporting records.
Pause and practice
A problem list says left knee pain, but the current note describes right knee pain. What comes next?
Show the explanation
Clarify the conflict through the approved workflow before selecting a laterality-specific code. Do not silently choose the side that seems most likely.
04Code systems and the coding workflow
Learning goal: Identify the purpose of each code set and verify current guidance.
ICD-10-CM classifies diagnoses and reasons for encounters. CPT (HCPCS Level I) describes many professional procedures and services. HCPCS Level II covers additional items and services such as certain supplies and drugs. ICD-10-PCS serves inpatient hospital procedure coding; it is not interchangeable with outpatient CPT coding.
Begin with the record, identify the documented concept, look up a candidate in the appropriate index, and verify it in the applicable tabular list or codebook. Review descriptors, inclusion notes, exclusion notes, required additional codes, sequencing, laterality, and encounter characters when applicable. An index result alone is not enough.
Use the code set effective for the relevant service or discharge date and the rules for that setting. Outpatient uncertain diagnoses generally are not coded as confirmed; instead, follow the official guidance for the documented symptoms, findings, or reason for the encounter. Inpatient rules differ.
Never select a more specific code than the documentation supports. A search engine, AI suggestion, or old cheat sheet cannot replace the current official guidance and required code references. This foundation course does not reproduce a CPT codebook or provide a complete coding credential preparation program.
Pause and practice
An AI tool suggests a diagnosis code. Is copying it into the claim enough?
Show the explanation
No. Verify the documented condition, setting, effective date, full descriptor, and all instructions in authoritative current references.
05Charges, modifiers, and professional claims
Learning goal: Check claim accuracy before submission.
A professional claim commonly uses the electronic 837P transaction or, when permitted, the CMS-1500 paper form. Institutional billing uses different formats. A clearinghouse can check and transmit data, but it does not guarantee payment.
Review the patient and subscriber information, payer, rendering and billing provider identifiers, dates, place of service, supported diagnosis and procedure codes, diagnosis pointers, charges, units, and required authorization information. Compare the submitted work with the actual documentation and service.
Modifiers provide additional information about a service under specific rules. They are not generic tools for bypassing an edit. For example, distinct-service concepts and evaluation-and-management modifier concepts each have their own documentation requirements. Escalate uncertainty to a qualified coding professional.
Inspect validation messages before sending. Check whether a batch was transmitted, whether the clearinghouse accepted it, and whether the payer acknowledged it. These are different milestones. Protect the submission deadline and retain evidence of receipt. Never submit invented services or inflate units to improve reimbursement.
Pause and practice
A clearinghouse accepts a batch. Does that mean the payer has approved payment?
Show the explanation
No. Track payer acknowledgment and adjudication separately. Acceptance at one stage does not establish payment at a later stage.
06Remittances and payment posting
Learning goal: Reconcile the payer’s decision with the account ledger.
A remittance explains how a payer processed a claim. An electronic remittance advice is often called an ERA and commonly uses the 835 transaction. An explanation of benefits may be provided to a member. Neither should be confused with the payment itself or a patient bill.
For each service, compare the billed amount, allowed amount, payer payment, adjustments, and patient responsibility. Read the adjustment group and reason codes plus any remark codes. Do not infer the meaning of an adjustment from its dollar amount alone.
Reconcile deposit or payment totals, remittance totals, and posted ledger entries. Identify zero-pay claims, reversals, take-backs, secondary-payer needs, and unmatched payments. Prevent duplicate posting by checking transaction identifiers and prior activity.
Simplified example: a practice bills $150, the contracted allowed amount is $100, the payer pays $80, and the remittance assigns $20 to the patient. If the $50 difference is a contractual adjustment under the agreement, it is not automatically collectible from the patient. Apply actual contracts, payer instructions, and legal requirements.
Pause and practice
A $50 contractual adjustment is present. Should it automatically become a patient bill?
Show the explanation
No. Follow the payer remittance and applicable contract. Distinguish contractual adjustments from valid patient responsibility.
07Rejections, denials, appeals, and A/R
Learning goal: Choose a follow-up action based on the actual processing stage.
A rejection usually means a claim did not pass an intake or processing requirement. A denial generally reflects a payer’s adjudication decision. Terminology varies, so read the actual response rather than relying only on a status label.
For a rejection, identify the specific data problem, verify the correct information, correct through the approved workflow, resubmit, and confirm acceptance. For a denial, read the remittance and policy, check the documentation, identify the cause, and determine whether correction, reconsideration, appeal, or another action is appropriate.
An appeal should address the stated reason with relevant support, not a generic demand for payment. Do not change a diagnosis merely because a payer denied a service. Observe payer-specific filing and appeal deadlines; there is no single universal deadline.
Accounts receivable follow-up needs an owner, a documented action, a next review date, and a resolution. Track aging by defined buckets and monitor recurring causes such as missing authorizations or registration errors. Prevent duplicates: confirm whether an existing claim is still pending before submitting another original claim.
Pause and practice
A denial cites missing authorization. Should you add a modifier and resubmit immediately?
Show the explanation
No. Verify authorization requirements, the actual authorization record, payer instructions, and available correction or appeal options. A modifier does not create authorization.
08Compliance and a complete worked case
Learning goal: Bring the workflow together without sacrificing accuracy.
Use only authorized systems and the information necessary for your assigned task. Never use real patient records in this public learning center, personal email, or an unapproved AI tool. HIPAA’s minimum-necessary rule has exceptions, including certain treatment disclosures; follow the organization’s actual privacy policies rather than inventing a blanket rule.
Upcoding reports a higher service than supported. Unbundling separates services contrary to applicable coding rules. Duplicate billing requests payment more than once for the same service. Report suspected issues through the compliance process; an internal performance target never justifies a false claim.
Practice case, entirely fictional: a professional claim is rejected because a subscriber number was transposed. The authorized staff member checks the verified registration source, corrects the number, resubmits within the payer deadline, and confirms payer receipt. When the ERA arrives, staff reconcile payment and adjustments, check secondary coverage, and route any valid patient balance through the approved process.
Your final checklist: correct record and date; supported current codes; complete claim fields; confirmed receipt; explained payer response; reconciled payment; documented follow-up. Use practice-specific training and current payer guidance before handling live claims.
Pause and practice
A supervisor asks you to choose a higher-paying service despite insufficient documentation. What should you do?
Show the explanation
Do not submit unsupported coding. Escalate through the coding or compliance process and retain an appropriate record of the concern.
PUT YOUR LEARNING INTO PRACTICE
Final knowledge check
Answer all 15 questions, then check your score. Aim for 80% (12 correct). This is an untimed learning goal, not a professional passing standard. You can retry as often as you like.
No personal information is requested. Scores are calculated on your device.
Watch on YouTube — @MVA-US ↗ (opens in a new tab).
References and further study
Use current official guidance for real-world decisions. The links below provide further reading; they do not indicate endorsement of Elite Care or this course.
- CMS: professional billing and correct coding ↗
- CMS: ICD-10 code sets and official guidelines ↗
- CMS: Evaluation & Management services ↗
- HHS: minimum necessary requirement ↗
AI-assisted educational content prepared November 14, 2026. Examples are fictional. This introductory course does not replace a complete curriculum, current professional references, employer training, or required clinical supervision.
← Explore the other free learning paths