Use this guide as a structured review companion for the Registered Medical Biller credential. Work through the ten groups in order, because early groups build the regulatory and privacy foundations that later claims and coding decisions depend on. Each concept pairs a rule with a resolved example and a common error, so read the explanation, predict the example's outcome before finishing it, and use the mistake note as a self-check. Verify current payer policies and code sets against official sources, since rules change and this guide teaches reasoning rather than every detail.
Regulatory and Compliance Foundations
1. Distinguishing Fraud from Abuse
Fraud requires making false statements or misrepresenting facts to obtain payment or a benefit from a federal healthcare program. Abuse produces unnecessary costs without the same intentional deception. The distinction changes exposure: fraud invites civil and criminal liability, while abuse typically triggers payment corrections and education.
Example: A biller submits claims for visits that never occurred to boost monthly revenue. This is fraud, not abuse, because false statements were made specifically to obtain undeserved payment.
Mistake to avoid: Treating intentional false billing as mere abuse and underestimating the legal consequences of the conduct.
Reference: AAPC CPB study guide sample
2. Reverse False Claims Liability
The False Claims Act reaches not only false billing but also reverse false claims, where a person acts improperly to avoid paying money owed to the government. A biller who knowingly retains an overpayment instead of refunding it creates liability under this provision.
Example: A practice discovers a payer overpayment but quietly keeps the funds. Liability arises under the reverse false claims provision because the practice acted improperly to avoid paying money owed.
Mistake to avoid: Assuming the False Claims Act only punishes inflated billing and ignoring retained overpayments.
Reference: AAPC CPB study guide sample
3. Qui Tam Whistleblower Actions
A qui tam action is a civil suit brought by a private person on behalf of both that person and the United States government. The private plaintiff, called a relator, may be awarded a share of the recovery, which gives whistleblowers a financial incentive to report billing misconduct.
Example: A billing employee sues on behalf of the government after the employer systematically upcodes claims. If funds are recovered, the employee may receive a percentage of the amount recovered as the relator.
Mistake to avoid: Confusing qui tam with a private lawsuit seeking only the relator's own damages.
Reference: AAPC CPB study guide sample
4. Truth in Lending Act in Collections
The Truth in Lending Act protects consumers dealing with lenders and creditors. A medical practice becomes a creditor when it charges finance charges on outstanding balances, which triggers disclosure obligations that a practice using simple interest-free payment plans does not face.
Example: A clinic charges a monthly finance charge on an unpaid patient balance. Because the clinic now functions as a creditor charging finance fees, Truth in Lending disclosures must be provided to the patient.
Mistake to avoid: Adding finance charges to patient balances without recognizing the practice has become a regulated creditor.
Reference: AAPC CPB study guide sample
5. HIPAA Standard Transaction Formats
Covered entities conducting electronic transactions must use the adopted standards, ASC X12 Version 5010, and NCPDP formats for certain pharmacy transactions. A provider is covered whether it transmits directly or uses a billing service to transmit on its behalf, so outsourcing does not escape the standard.
Example: A clinic sends eligibility inquiries and claims through a billing vendor. Because the vendor transmits these standard transactions on the clinic's behalf, the clinic must use the adopted electronic formats for those transactions.
Mistake to avoid: Believing a third-party billing service exempts the provider from electronic transaction standards.
Reference: AAPC CPB study guide sample
6. NPI Requirement on Electronic Claims
The National Provider Identifier is a unique 10-digit identification number required by HIPAA and used on electronic HIPAA-compliant transactions. Every billing and rendering provider on a claim must be identified by an NPI, and credentialing ties payer enrollment to this number before claims can be reimbursed.
Example: A claim is submitted with the physician's state license number where the NPI belongs. The transaction fails because the required 10-digit National Provider Identifier is missing from the electronic submission.
Mistake to avoid: Substituting a tax ID, license number, or payer number for the NPI on electronic claims.
Reference: AAPC CPB study guide sample
HIPAA Privacy Rule Scope
7. Who Is a Covered Entity
The Privacy Rule covers three categories: health plans, healthcare clearinghouses, and any healthcare provider that transmits health information electronically in connection with standard HIPAA transactions. Using email alone does not make a provider covered; the electronic transmission must relate to a transaction for which HHS adopted standards.
Example: A small lab emails appointment reminders but files claims electronically through a vendor. It is a covered entity because standard transactions occur on its behalf, even though its own email use is incidental.
Mistake to avoid: Assuming any provider using email or computers is automatically a covered entity.
Reference: HHS Summary of the HIPAA Privacy Rule
8. Business Associate Relationships
A business associate is a person or organization outside a covered entity's workforce that performs functions involving individually identifiable health information on the entity's behalf, such as claims processing, billing, utilization review, or data analysis. A written business associate agreement imposing specified safeguards is required.
Example: A practice hires an outside firm to process its claims. The firm is a business associate, and the practice must have a written agreement imposing safeguards before any protected information is shared.
Mistake to avoid: Exchanging patient data with a billing vendor before a signed business associate agreement exists.
Reference: HHS Summary of the HIPAA Privacy Rule
9. What Counts as Protected Health Information
Protected health information is individually identifiable health information held or transmitted by a covered entity or its business associate in any form: electronic, paper, or oral. It includes demographic data relating to health, care provision, or payment. Employment records a covered entity keeps as an employer are excluded from protection.
Example: A receptionist discusses a patient's outstanding balance by phone within earshot of others. The conversation is protected health information because oral health and payment information identifies the patient.
Mistake to avoid: Treating oral or paper information as outside HIPAA because only electronic data is protected.
Reference: HHS Summary of the HIPAA Privacy Rule
10. De-Identification Safe Harbor
De-identified health information carries no use or disclosure restrictions. De-identification is achieved either through a formal determination by a qualified statistician or by removing specified identifiers of the individual and relatives, household members, and employers, and only if the entity has no actual knowledge the remaining data could identify someone.
Example: A researcher wants claims data without patient names or addresses. Removing the specified identifiers and confirming no remaining data could identify anyone allows unrestricted use of the de-identified dataset.
Mistake to avoid: Stripping only names and calling a dataset de-identified while dates, ZIP codes, or record numbers remain.
Reference: HHS Summary of the HIPAA Privacy Rule
11. Limited Data Sets and Data Use Agreements
A limited data set is protected health information with certain direct identifiers removed but not fully de-identified. It may be used for research, healthcare operations, and public health only when the recipient signs a data use agreement promising specified safeguards. This is a middle option between full de-identification and authorization-based disclosure.
Example: A hospital shares a dataset retaining treatment dates and partial geography with a university researcher. Because a data use agreement is signed, the limited data set may be shared even though it is not fully de-identified.
Mistake to avoid: Releasing a limited data set for marketing or general business purposes, which fall outside the permitted categories.
Reference: HHS Summary of the HIPAA Privacy Rule
12. State Law Preemption Exceptions
Contrary state laws are generally preempted by the Privacy Rule, but exceptions protect state laws that provide greater privacy protections, that require reporting of disease, injury, child abuse, birth, or death, or that require certain health plan reporting. A biller must check whether an exception preserves the state requirement.
Example: A state law requires reporting of communicable disease cases. The state rule stands because public health reporting exceptions preserve contrary state laws rather than letting the federal rule override them.
Mistake to avoid: Automatically applying the federal rule and dismissing a stricter state privacy law that actually survives preemption.
Reference: HHS Summary of the HIPAA Privacy Rule
Permitted Uses and Authorizations
13. Treatment, Payment, and Operations Uses
A covered entity may use and disclose protected health information without authorization for its own treatment, payment, and healthcare operations. Payment includes a provider's activities to obtain payment or reimbursement, so claim submission, eligibility inquiries, and collection efforts on unpaid patient balances all fall within this permitted category.
Example: A biller mails a claim with diagnosis details to the patient's insurer. No authorization is needed because obtaining payment for provided care is a permitted payment activity.
Mistake to avoid: Delaying claim submission while waiting for an authorization that the payment activity does not require.
Reference: HHS Summary of the HIPAA Privacy Rule
14. Minimum Necessary Standard and Exceptions
Covered entities must make reasonable efforts to limit uses, disclosures, and requests to the minimum necessary for the purpose. The standard does not apply to treatment disclosures to providers, disclosures to the individual, disclosures under an authorization, disclosures to HHS, or uses required by law.
Example: An attorney requests a patient's complete chart for a records review. Sending the entire record is improper unless the biller can specifically justify the whole record as the minimum needed for that purpose.
Mistake to avoid: Sending an entire medical record when only specific dates of service were requested, ignoring minimum necessary limits.
Reference: HHS Summary of the HIPAA Privacy Rule
15. When Written Authorization Is Required
Written authorization is required for uses and disclosures beyond treatment, payment, operations, and other permitted categories. Authorizations must be in plain language and specify the information, who discloses and receives it, an expiration, and the right to revoke in writing. Life insurer, employer physical results, and pharmaceutical marketing disclosures require authorization.
Example: A life insurer asks for exam results to underwrite a policy. The biller must obtain the patient's written authorization before releasing anything, because coverage underwriting is not a permitted purpose.
Mistake to avoid: Releasing records to an employer or insurer based on a verbal request instead of a valid written authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
16. Psychotherapy Notes Protection
Psychotherapy notes, which are a mental health professional's separately kept session analyses, require authorization for nearly all uses, including most treatment, payment, and operations purposes. Exceptions include the originator's own treatment use, training, legal defense, HHS compliance review, and averting serious threats. Medication and session time records are excluded from the definition.
Example: A payer requests psychotherapy notes to process a claim. The biller must refuse absent authorization, because payment review is not among the narrow exceptions permitting their release.
Mistake to avoid: Treating therapy appointment times and medication logs as psychotherapy notes requiring authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
17. Marketing Rules and Carve-Outs
Marketing requires authorization, but communications describing the covered entity's own health-related services, participating providers, plan replacements, treatment communications, and care coordination are carved out. An arrangement where the entity is paid to disclose information for another company's product marketing requires authorization that reveals the remuneration, except face-to-face communications.
Example: A practice mails flyers about a new weight-loss program included in patients' benefit plans. No authorization is needed because describing the plan's own covered services falls outside the marketing definition.
Mistake to avoid: Sending a sponsored product mailing paid for by a vendor without an authorization disclosing the payment arrangement.
Reference: HHS Summary of the HIPAA Privacy Rule
18. Personal Representatives and Minors
A personal representative, someone legally authorized to act for the individual or the estate, must be treated as the individual. Parents are generally personal representatives for minor children, but exceptions defer to state law, and where state law is silent, a licensed healthcare professional may exercise judgment to grant or deny parental access.
Example: A divorced father demands his adolescent daughter's records. Because state law in that situation gives the minor control over the requested service's records, the biller must follow state law rather than automatically honoring the parent.
Mistake to avoid: Automatically releasing a minor's records to any parent without checking applicable state law exceptions.
Reference: HHS Summary of the HIPAA Privacy Rule
Health Plan Models and Coverage Design
19. HMO versus PPO Plan Mechanics
An HMO typically requires members to maintain a primary care physician and obtain referrals before seeing specialists, keeping costs controlled through that gatekeeping structure. A PPO negotiates predetermined fees within a network but gives members more options, with no primary care physician requirement and no referral requirement for network specialists.
Example: A patient with an HMO card wants a dermatology visit without a referral. The biller must confirm a referral exists first, because HMO plans generally require one before specialist claims will pay.
Mistake to avoid: Billing a specialist visit under an HMO without verifying that a referral was obtained and documented.
Reference: AAPC CPB study guide sample
20. Managed Care Organization Functions
A managed care organization combines health insurance functions, delivery of care, and administration in one entity. For a biller, this changes where claims go and which rules apply: the MCO's own authorization, network, and payment policies govern, rather than the original insurer's fee-for-service rules the member might have had before.
Example: A state Medicaid program pays a monthly per-member fee to an MCO that then arranges all covered care. The biller sends claims to the MCO, not the state, because the MCO holds both insurance and delivery functions.
Mistake to avoid: Sending MCO member claims to a prior fee-for-service payer address and wondering why they reject.
Reference: AAPC CPB study guide sample
21. FSA versus HSA Fund Rules
A flexible spending account holds employee contributions for out-of-pocket healthcare costs but generally forfeits unused money at the plan year's end. A health savings account pairs with high-deductible insurance, is portable, can be funded by employer or employee, earns interest, and retains balances, so leftover funds remain available for future deductibles.
Example: An employee with $400 left in an FSA at year end loses it, while a coworker's HSA balance carries forward and earns interest. The biller explains why only the HSA patient can apply old funds to today's deductible.
Mistake to avoid: Telling a patient that unused FSA funds will roll over the way HSA balances do.
Reference: AAPC CPB study guide sample
22. Medicare Part A versus Part B Coverage
Medicare Part A covers hospital care, skilled nursing facility care, hospice, and home health services, while Part B covers medically necessary services like physician visits, ambulance, durable medical equipment, and mental health, plus expanded preventive services. The biller must route each claim to the part that covers the service delivered.
Example: A patient expects a physician office visit to be covered like her hospital stay was. The biller explains Part B covers physician services subject to its own deductible and coinsurance, separate from her Part A hospital benefits.
Mistake to avoid: Billing a physician service under Part A benefits because the patient was recently hospitalized.
Reference: AAPC CPB study guide sample
23. Medigap Supplemental Coverage
Medigap policies are designed by the federal government but marketed by private commercial insurers to fill gaps in Medicare coverage, such as deductibles, copayments, and coinsurance. The biller identifies Medigap coverage so patient responsibility amounts are transferred to the supplement rather than collected from the beneficiary directly.
Example: A Medicare patient faces a hospital deductible and 20 percent physician coinsurance. Her Medigap premium covers those gaps, so the biller bills Medigap second rather than pursuing the patient for them.
Mistake to avoid: Pursuing the patient for coinsurance that an active Medigap policy is designed to pay.
Reference: AAPC CPB study guide sample
24. Medicare Eligibility Before Age 65
Most beneficiaries qualify at age 65, but Part A coverage is available before 65 for individuals who have received Social Security or Railroad Retirement Board disability benefits for 24 months, or who have end-stage renal disease and meet certain requirements. Verifying the qualifying basis prevents wrongly denying a claim as ineligible.
Example: A 58-year-old on dialysis applies for Medicare. The biller verifies eligibility because end-stage renal disease with certain requirements can qualify a person under 65 for Part A coverage.
Mistake to avoid: Rejecting a disabled or ESRD patient's claim on the assumption that Medicare starts only at 65.
Reference: AAPC CPB study guide sample
Medicare and Medicaid Billing Rules
25. Accepting Assignment and Contractual Write-Offs
When a provider accepts assignment, the provider agrees to take the Medicare approved amount as full payment and must write off the difference between the billed charge and the approved amount. Medicare pays its share of the approved amount, and the patient's coinsurance is calculated on the approved amount, never on the billed charge.
Example: A practice bills 210 dollars for an office visit, but the remittance lists the approved amount as 140 dollars. Because assignment is accepted, the 70 dollar difference is written off, Medicare pays 112 dollars (80 percent of the approved amount), and the patient's coinsurance is 28 dollars, calculated on the approved amount rather than on the 210 dollar charge.
Mistake to avoid: Billing the patient for the balance between the charge and the approved amount after accepting assignment.
Reference: AAPC CPB study guide sample
26. Non-Participating Limiting Charge
A non-participating provider who does not accept assignment is still limited in what can be charged to the beneficiary. The limiting charge is set at 115 percent of the non-participating Medicare Physician Fee Schedule amount, so the provider cannot balance-bill the patient beyond that ceiling even while remaining outside the participating system.
Example: A non-participating provider treats a Medicare patient. The biller may charge the patient no more than the limiting charge, which is capped at 115 percent of the applicable fee schedule amount.
Mistake to avoid: Assuming non-participation permits charging the patient the full billed amount without any cap.
Reference: AAPC CPB study guide sample
27. Medicare Secondary Payer Determination
When a Medicare patient has other insurance, the Medicare Secondary Payer form is used to determine whether Medicare is primary or secondary for that patient. The answer controls claim order: billing Medicare first when another payer is primary causes denials, while the MSP form establishes the correct sequence before submission.
Example: A 68-year-old patient presents an employer group card plus her Medicare card. The biller completes the MSP form first, which reveals the group plan is primary, so Medicare is billed second.
Mistake to avoid: Automatically billing Medicare first for every beneficiary without completing the secondary payer screening.
Reference: AAPC CPB study guide sample
28. Medicaid Mandatory Services and Federal Matching
States design their own Medicaid programs, but to receive federal matching funds, known as the Federal Medical Assistance Percentage, they must provide mandatory services like inpatient and outpatient hospital care, physician services, prenatal care, and vaccines for children. Optional services such as optometry or physical therapy vary by state.
Example: A state drops coverage for a service to save money. The biller learns that because the service is federally mandatory, dropping it jeopardizes the state's federal matching funds under FMAP.
Mistake to avoid: Assuming every Medicaid plan covers the same services in every state when optional benefits differ.
Reference: AAPC CPB study guide sample
29. CHIP Coverage for Children
The Children's Health Insurance Program offers free or low-cost coverage for children in families whose incomes are too high to qualify for Medicaid but who cannot afford private coverage. States administer it, and it is jointly funded by the federal government and the states, so eligibility rules and billing procedures differ from Medicaid even though both serve similar populations.
Example: A family earns too much for Medicaid but cannot afford a marketplace plan. The children are enrolled in CHIP, and the biller verifies benefits through the state-administered program rather than Medicaid.
Mistake to avoid: Confusing CHIP eligibility with Medicaid and submitting claims to the wrong state program.
Reference: AAPC CPB study guide sample
30. Preventive Service Diagnosis Requirements
Medicare screening services often carry specific diagnosis requirements, and coverage can depend on documented risk factors or time intervals since the last screening. For example, more frequent screening Pap smears are covered when the medical history shows high-risk factors such as early onset of sexual activity or a history of sexually transmitted disease.
Example: A screening Pap claim denies because the diagnosis shows a routine screening frequency. The biller checks the high-risk criteria and finds documented early onset history supporting more frequent screening, so the claim is corrected and rebilled.
Mistake to avoid: Attaching a routine screening diagnosis to a preventive claim without checking the payer's frequency and risk criteria.
Reference: AAPC CPB study guide sample
Patient Registration and Data Capture
31. Reading and Copying the Insurance Card
The insurance ID card carries the identification or policy number, policyholder name, benefit types, deductible, and copayment amounts that vary by service type such as office, urgent care, or hospital. The back lists contact information and the claims submission address. Copying both sides into the financial record preserves this data for billing.
Example: A claim rejects for wrong submission address. The biller checks the card copy on file, finds the payer's claims address on the back, and resubmits correctly.
Mistake to avoid: Filing only the card front and losing the payer's claims address and contact details printed on the back.
Reference: AAPC CPB study guide sample
32. Eligibility Verification versus Benefits Verification
Eligibility verification confirms whether the patient is currently covered under the plan, while verification of benefits reveals the specifics: effective dates, copay, coinsurance, deductible status, and plan benefits by specialty and place of service. Both steps together let staff collect the right amounts at the visit rather than chasing balances afterward.
Example: Before a visit, staff confirm the patient's policy is active and note a 35 dollar office copay and unmet deductible. Because both eligibility and benefits were verified, the correct amounts are collected at check-in.
Mistake to avoid: Confirming only that coverage is active and assuming the visit's copay or deductible status without checking benefits.
Reference: AAPC CPB study guide sample
33. Birthday Rule for Dependent Coverage
When a child is covered under both parents' plans, the birthday rule designates the plan of the parent whose birthday comes first in the calendar year as primary. Only the month and day matter; the year of birth is not a factor. The other parent's plan is billed secondary.
Example: A child's mother, born February 17, and father, born September 3, both cover the child under employer plans. The mother's plan is primary because February 17 falls earlier in the calendar year than September 3, so the father's plan is billed secondary.
Mistake to avoid: Letting the older parent's plan be primary based on birth year instead of month and day.
Reference: AAPC CPB study guide sample
34. Determining Primary versus Secondary Coverage
When a patient is the subscriber on a plan, that plan is primary. Coverage held through another person, such as a spouse's employer plan, is secondary. Getting this order wrong causes the primary payer to deny or recoup, so the biller confirms subscriber relationships before the first submission.
Example: A patient holds her own employer plan and is also covered under her husband's plan. Her own plan is billed first because she is the subscriber on it, and the spouse's plan is secondary.
Mistake to avoid: Billing the spouse's plan first simply because its benefits appear richer, ignoring subscriber status.
Reference: AAPC CPB study guide sample
35. Handling Ineligible Patients at Check-In
When eligibility verification fails, the patient must be contacted for updated insurance information. If the patient believes the coverage is correct, the patient should contact the insurance company to have eligibility files updated. The patient then decides whether to reschedule the appointment or be treated as self-pay for that visit.
Example: Verification shows the patient ineligible, but she insists coverage is active. The biller has her contact the insurer to fix the eligibility file and lets her choose to reschedule or self-pay for today's visit.
Mistake to avoid: Refusing the visit outright or billing the old payer repeatedly instead of letting the patient choose rescheduling or self-pay.
Reference: AAPC CPB study guide sample
36. Consent for Payment on the Registration Form
The registration consent for payment authorizes payment of medical benefits to the practice, documents that the patient listed all applicable plans, and establishes the patient's responsibility for copayments, coinsurance, deductibles, and non-covered services. It also authorizes use of health information for treatment, payment, and operations, and notes refusal may affect treatment.
Example: A patient signs the registration consent agreeing to pay copays at service time and authorizing benefit payment to the practice. The biller relies on this signed form when collecting today's copay without a separate negotiation.
Mistake to avoid: Collecting patient responsibility amounts without a signed consent establishing that obligation on file.
Reference: AAPC CPB study guide sample
Claims Processing and Electronic Submission
37. Clean Claim Standard
A clean claim is one submitted with all the information necessary for the payer to process it. Missing subscriber IDs, invalid codes, or absent provider numbers turn a clean claim into a rejection or a suspended claim, delaying payment and creating rework that a complete data check before submission would prevent.
Example: A claim transmits with subscriber, provider, and diagnosis data complete, so the payer processes it without follow-up requests. It qualifies as a clean claim, which matters for timely payment expectations.
Mistake to avoid: Submitting claims with known missing fields and expecting the payer to request the rest later.
Reference: AAPC CPB study guide sample
38. Clearinghouse Role in Claims Flow
A clearinghouse is an entity that processes or facilitates the processing of claims between providers and healthcare plans, converting nonstandard information into standard format or vice versa. Billers route electronic claims through the clearinghouse, and daily processing reports from it reveal which claims were acknowledged or rejected before payer adjudication.
Example: A practice's claims fail because its software outputs a nonstandard format. The clearinghouse converts the data into the standard transaction the payer accepts, and the claims move forward.
Mistake to avoid: Waiting on a payer response for a claim that actually sits rejected at the clearinghouse, unacknowledged.
Reference: AAPC CPB study guide sample
39. Acting on EDI Rejection Reports
An EDI report distinguishes acknowledged claims, forwarded to the payer, from rejected claims that must be corrected and rebilled. A rejection is a data problem solved by checking the information on file, such as the insurance card copy, not a coverage decision, so the balance should not move to patient responsibility.
Example: The morning EDI report lists two claims: one acknowledged and forwarded to the payer, another flagged REJ with a data error. The biller marks the acknowledged claim as reviewed and waits for adjudication, but for the rejected claim she pulls the insurance card on file, corrects the flagged data, and rebills, because the rejection never reached the payer as a coverage decision and the balance must not move to the patient.
Mistake to avoid: Writing off or patient-billing a rejected claim instead of correcting the data error and resubmitting.
Reference: AAPC CPB study guide sample
40. DSL versus Dial-Up for Claim Transmission
DSL is an electronic transmission method that uses the same wires as a regular telephone line while operating at very high speed. Dial-up uses those same telephone wires but cannot move data at comparable speed, so a practice submitting daily batches of electronic claims must match its connection to its claim volume rather than assuming every telephone-line option performs alike.
Example: A four-provider practice sends nightly claim batches to its clearinghouse, but on the practice's dial-up line the transmission is still running when staff leave for the day. Because DSL delivers very high-speed transmission over the same telephone wiring already installed, the practice switches to DSL and the batches finish in minutes.
Mistake to avoid: Treating all connections that use the telephone line as equivalent and leaving high-volume claim submission on a slow dial-up connection.
Reference: AAPC CPB study guide sample
41. Chargemaster and Revenue Codes
The chargemaster is the hospital-specific master list of all procedures, services, supplies, and medications billed to payers, pairing each item with its charge, code, revenue code, and general ledger number. The revenue code is a four-digit numeric code established by the National Uniform Billing Committee that classifies each line item for the payer.
Example: A hospital biller charges a pelvic ultrasound. The chargemaster row pairs the item with its CPT/HCPCS code, a four-digit revenue code, the general ledger number, and a listed charge of 300 dollars. She enters the four-digit revenue code in the line-item classification field and the CPT code in the procedure field, keeping the two numbers in their separate fields.
Mistake to avoid: Confusing the revenue code with the CPT or HCPCS code and entering the wrong number in the line item field.
Reference: AAPC CPB study guide sample
42. Encounter Form versus Chargemaster
An encounter form, often called a superbill, is the provider-office document listing services and charges for a single visit, while the chargemaster is the hospital-wide master list of all billable items. The biller uses the encounter form to capture what happened at the visit and the chargemaster to find standardized charges and codes for hospital billing.
Example: A physician office records today's visit and procedures on a superbill that the patient hands to check-out. The hospital across town instead bills from its chargemaster, its comprehensive department-level price list.
Mistake to avoid: Using the terms interchangeably and expecting a superbill to function as a hospital-wide price master.
Reference: AAPC CPB study guide sample
ICD-10-CM Conventions and Structure
43. Index-First, Tabular-Verified Code Search
Code selection begins in the Alphabetic Index to locate the term, then the code is verified in the Tabular List, where notes, seventh characters, and exclusions apply. Reading and following the tabular instructions is mandatory because the index alone can point to an incomplete code that the tabular list modifies or blocks.
Example: The index entry for a condition points to a code, but the tabular entry adds a required seventh character. The biller returns to the index for the fuller code rather than appending characters independently.
Mistake to avoid: Assigning a code straight from the Alphabetic Index without verifying it against the Tabular List instructions.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
44. Placeholder X in Code Structure
The placeholder character X fills empty character positions when a code requiring a seventh character is shorter than six characters. It exists purely to hold the place so the seventh character lands in the correct position, and it carries no clinical meaning of its own in the assigned code.
Example: A fracture code needs a seventh character but has only five characters available. The biller inserts the placeholder X so the seventh character occupies its correct position in the final code.
Mistake to avoid: Omitting the placeholder and appending the seventh character directly, producing an invalid code length.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
45. Excludes1 versus Excludes2 Notes
An Excludes1 note means the excluded code can never be used with the code above the note, applying when two conditions cannot coexist, such as congenital versus acquired forms. An Excludes2 note means the condition is not included here but the patient may have both, so both codes may be assigned when documented.
Example: A congenital form of a condition sits under an Excludes1 note beneath the acquired code. The biller cannot report both, because the note marks the two forms as mutually exclusive for that code.
Mistake to avoid: Reading every Excludes note as an absolute bar and dropping a code that an Excludes2 note actually permits.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
46. Code Also Notes Without Sequencing
A code also note signals that two codes may be required to fully describe a single condition, but it deliberately provides no sequencing direction. The sequencing depends on the circumstances of the encounter, so the biller must decide which condition explains the reason for the visit rather than assuming a fixed order from the note itself.
Example: A note instructs the biller to also code the underlying infection. Because the note gives no sequencing direction, the biller sequences based on the reason for this particular encounter.
Mistake to avoid: Treating a code also note as a sequencing rule and automatically listing the additional code second.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
47. Default Codes for Unqualified Documentation
A default code is the code listed next to a main term in the Alphabetic Index, representing the condition most commonly associated with that term or its unspecified form. When a condition is documented without qualifying detail, such as acute versus chronic, the default code is assigned instead of a more specific option.
Example: A record documents appendicitis with no acute or chronic qualifier. The biller assigns the default code listed with the index term rather than guessing chronicity the record never states.
Mistake to avoid: Selecting a specific acute or chronic code when the documentation never establishes which applies.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
48. Other and Unspecified Code Use
Codes titled unspecified are used when the record is insufficient for a more specific code, and other specified codes capture documented conditions that lack their own unique code. Unspecified codes are acceptable when they best reflect what is known at the encounter; selecting unsupported specific codes or ordering unnecessary testing to refine them is inappropriate.
Example: Pneumonia is diagnosed but the organism is unknown. The biller reports the unspecified pneumonia code because it accurately reflects what is known, rather than guessing a bacterial type.
Mistake to avoid: Assigning a specific code unsupported by documentation simply to avoid ever using an unspecified code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Diagnosis Documentation and Coding Decisions
49. Provider Statement over Clinical Criteria
Code assignment rests on the provider's diagnostic statement that the condition exists, not on the clinical criteria the provider used to reach it. When record documentation conflicts, the coder or biller must query the provider for clarification instead of resolving the conflict by choosing one documented version over another.
Example: A note shows findings suggesting a condition, but the provider never states the diagnosis. The biller queries the provider rather than assigning the code the findings seem to imply.
Mistake to avoid: Assigning a diagnosis because lab values or imaging appear to support it when the provider never documented the condition.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
50. Clinician Data Exceptions for Code Assignment
Code assignment is based on the patient's provider's documentation, with limited exceptions allowing other clinicians' data: BMI, non-pressure ulcer depth, pressure ulcer stage, coma scale, stroke scale, social determinants, laterality, blood alcohol level, underimmunization status, and firearm injury intent. The associated diagnosis must still come from the provider.
Example: A dietitian documents a BMI and a nurse stages a pressure ulcer. The biller may use those values for the BMI and stage codes, but the obesity and pressure ulcer diagnoses themselves must come from the provider.
Mistake to avoid: Letting a nurse's note establish the underlying diagnosis itself rather than only the permitted data element.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
51. Uncertain Diagnoses by Care Setting
The guidelines handle uncertain diagnoses differently by setting. Section II governs principal diagnosis selection for non-outpatient settings and addresses uncertain diagnoses at discharge, while Section IV governs outpatient reporting, where each encounter is coded to the level of certainty known at that encounter, typically symptoms rather than unconfirmed conditions.
Example: An outpatient record lists suspected pneumonia at visit end. The biller codes the documented symptom instead, because outpatient certainty rules differ from inpatient rules for conditions still under workup.
Mistake to avoid: Applying inpatient uncertain-diagnosis conventions to an outpatient encounter still awaiting confirmation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
52. Borderline Diagnosis Handling
A borderline diagnosis documented at discharge is coded as confirmed, unless the classification provides a specific entry such as borderline diabetes. Because borderline conditions are not uncertain diagnoses, no distinction is made between inpatient and outpatient settings, and coders are encouraged to query whenever the documentation is unclear.
Example: A discharge note calls a condition borderline. The biller codes it as confirmed unless the classification has a specific borderline entry, and queries when the documentation remains unclear.
Mistake to avoid: Treating every borderline documentation as uncertain and downgrading it to a symptom code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
53. Complications of Care Documentation
Complication coding depends on the provider's documentation of a relationship between the condition and the care or procedure. A cause-and-effect relationship and clinical significance must be supported, but the word complication need not appear; a condition that alters the surgical course qualifies. Unclear relationships call for a provider query.
Example: Bleeding alters a procedure's course per the operative report, though the word complication never appears. The biller reports the complication code because the documented cause-and-effect relationship qualifies it.
Mistake to avoid: Reporting a routine post-procedure symptom as a complication without documented cause and effect.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
54. Symptom Codes When Diagnosis Is Pending
When no definitive diagnosis is established by the end of the encounter, codes for the documented signs and symptoms are reported in place of a definitive diagnosis. Each encounter is coded to the level of certainty known at that time, and conducting medically unnecessary testing just to reach a more specific code is explicitly inappropriate.
Example: At visit end the workup is incomplete and no definitive diagnosis exists. The biller reports the documented symptom code, which accurately reflects the encounter's certainty level.
Mistake to avoid: Carrying a suspected diagnosis forward from a prior visit onto today's claim without current confirmation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Advanced Coding and Billing Scenarios
55. Diabetes Type Default and Drug Use Codes
When the diabetes type is not documented, the default is type 2, even if the patient uses insulin. Long-term use of insulin, oral hypoglycemics, or injectable non-insulin drugs is captured with additional codes from category Z79, and combinations require multiple codes. Temporary inpatient insulin for glucose control does not earn the insulin use code.
Example: A record documents diabetes with insulin use but no type. The biller assigns the type 2 default and adds the long-term insulin use code, without changing the type based on the insulin.
Mistake to avoid: Coding type 1 diabetes because the patient uses insulin, or adding an insulin use code for temporary control.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
56. Urosepsis Requires a Query
Urosepsis is a nonspecific term that is not considered synonymous with sepsis and has no default code in the Alphabetic Index. When a provider uses it, the provider must be queried for clarification before any sepsis-related code is assigned, because the term alone cannot support a severe or specific infection code.
Example: A provider documents urosepsis with no further detail. The biller queries the provider rather than assigning a sepsis code, because the term has no default code in the index.
Mistake to avoid: Automatically translating urosepsis into a sepsis code without querying the provider first.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
57. Severe Sepsis Code Structure
Severe sepsis requires a minimum of two codes: first the underlying systemic infection, then a code from subcategory R65.2 for severe sepsis, plus additional codes for the associated acute organ dysfunction. Negative or inconclusive blood cultures do not preclude sepsis when clinical evidence exists, though the provider should be queried.
Example: A patient has sepsis with documented acute kidney injury related to it. The biller sequences the underlying infection code, then the severe sepsis code, then the organ dysfunction code, per the required structure.
Mistake to avoid: Assigning a severe sepsis code when no acute organ dysfunction associated with the sepsis is documented.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
58. Burn Coding and Sequencing
When multiple burns are present, the code reflecting the highest degree is sequenced first. Burns of the same anatomic site and side but of different degrees are classified to the subcategory for the highest degree recorded, using a single code. Separate codes are assigned for each burn site, and multiple-site codes apply only when individual sites are not specified.
Example: A patient sustains second and third degree burns of the left lower leg. The biller assigns a single code for the third degree burn at that site, because burns of the same anatomic site and side classify to the highest degree recorded; a separate code would apply only to a different, separately documented burn site.
Mistake to avoid: Assigning separate codes for second and third degree burns of the same site instead of the highest degree only.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
59. Pressure Ulcer Staging and Evolution
Pressure ulcer stage may be taken from clinicians other than the provider, such as nursing staff, but the pressure ulcer diagnosis itself must be documented by the provider. When an ulcer evolves to a higher stage during admission, two codes are assigned: the site and stage at admission plus the same site at the highest stage reported during the stay.
Example: A patient admitted with a stage 2 pressure ulcer progresses to stage 4 during the stay. The biller assigns two codes: the admission stage and the highest stage reached for the same site.
Mistake to avoid: Coding only the final ulcer stage and losing the admission-stage code required for the same site.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
60. Underdosing versus Poisoning Classification
Underdosing means taking less of a medication than prescribed or discontinuing it on the patient's own initiative, and a code is assigned without requiring a documented condition change. Underdosing codes are never principal or first-listed; noncompliance or complication codes indicate intent. Reactions from a nonprescribed drug combined with a properly taken one are poisoning.
Example: A patient stops her prescribed medication on her own and lands in the emergency department. The biller assigns the underdosing code as an additional code with a noncompliance code, never as the first-listed code.
Mistake to avoid: Sequencing an underdosing code first, or coding a self-discontinued drug as poisoning without an interaction.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
References and further reading
Source links checked on Oct 2, 2026.