Use this guide as a structured review of payer-side medical coding: code set conventions, diagnosis selection, Medicare and payer policy, privacy rules, claims processing, and audit risk analysis. Work the groups in order, since later application builds on earlier foundations. Each concept pairs a rule or distinction with a short resolved example and a common error, so you can self-test decisions rather than memorize definitions. This is teaching material, not an official syllabus or exam replica.
Code Set Foundations for Payer Review
1. Distinguishing CPT Conventions from Payer Payment Policy
CPT instructions, parenthetical notes, and symbols guide code assignment, but not every payer follows them. A payer-side reviewer must identify the payer's published variations, apply them during review, and explain the difference between the code set rule and the payer's payment rule to the provider.
Example: A payer reviewer sees a payer bulletin contradicting a CPT parenthetical note. Decision: apply the payer policy for that claim and note the CPT rule separately, because the contract controls payment.
Mistake to avoid: Do not deny a claim citing only CPT guidance when the payer's contract or policy states a different requirement.
Reference: AAPC CPMA study guide sample
2. Add-On Codes Never Stand Alone
Add-on codes, marked with a plus symbol, describe services performed in addition to a primary procedure and are never reported alone. A parenthetical note identifies the associated primary codes. Add-on codes are also exempt from the multiple procedure payment reduction concept.
Example: A claim shows only an add-on code with no primary procedure. Decision: reject or return the claim, because an add-on code cannot stand alone without its listed primary code.
Mistake to avoid: Avoid appending a modifier to force payment of an add-on code billed without its primary procedure.
Reference: AAPC CPMA study guide sample
3. Multiple Procedure Payment Reduction Logic
When multiple procedures are performed in the same operative session, the multiple procedure payment reduction may apply: the highest valued code at full payment, the second at a reduced percentage, and additional procedures at a further reduction. The fee schedule indicator shows whether a code is subject to this reduction.
Example: Three surgical procedures are billed on one claim. Decision: expect the highest valued code paid in full and the others reduced per the payer's multiple procedure policy, not each at full value.
Mistake to avoid: Do not apply the reduction to every line automatically; check the indicator for each code first.
Reference: AAPC CPMA study guide sample
4. Using the Code Book Version Matching the Date of Service
Code sets change annually, and new or revised codes are marked in the book. When reviewing or auditing claims, apply the codes valid on the date of service, not the date of the review. A procedure performed under one year's codes must be evaluated with that year's conventions and instructions.
Example: An audit performed in March covers October dates of service from the prior year. Decision: apply the code set in effect for the October service date, not the current edition.
Mistake to avoid: Avoid auditing older claims with the current year's code descriptions and then declaring coding errors.
Reference: AAPC CPMA study guide sample
5. HIPAA Standardized Code Sets and Transaction Formats
Covered entities conducting electronic transactions must use the adopted standard code sets and transaction formats, including the ASC X12 Version 5010 standard and the pharmacy transaction standard. Payer systems and clearinghouses rely on these standards to process claims uniformly, so nonstandard data causes rejections.
Example: A clinic submits electronic claims using a homemade format. Decision: the transactions are noncompliant, because covered entities must use the adopted standard transaction formats.
Mistake to avoid: Do not assume any electronic claim format is acceptable; only adopted standard transactions qualify.
Reference: AAPC CPB study guide sample
6. National Provider Identifier Requirement on Claims
The National Provider Identifier is a unique ten-digit identification number required by HIPAA and used on electronic HIPAA-compliant transactions. Every billing and rendering provider needs an active NPI, and claims lacking valid NPIs fail payer edits before adjudication, regardless of the services billed.
Example: A claim arrives with the billing provider's state license number but no NPI. Decision: the claim cannot process, because the ten-digit NPI is required on standard electronic transactions.
Mistake to avoid: Avoid substituting a tax ID or legacy payer number where the NPI field is required.
Reference: AAPC CPB study guide sample
ICD-10-CM Structure and Conventions
7. Alphabetic Index First, Then Tabular Verification
Diagnosis code selection starts in the Alphabetic Index, which lists terms with corresponding codes, and finishes in the Tabular List, where the code is verified against its title, inclusion terms, and excludes notes. Assigning a code straight from the index without tabular verification risks missing required characters or sequencing instructions.
Example: A note documents diabetes with a foot ulcer. Decision: locate the combination in the Alphabetic Index first, then verify the full code and any instructional notes in the Tabular List before reporting it.
Mistake to avoid: Never report a code pulled only from the index without confirming it in the Tabular List.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
8. Placeholder X in ICD-10-CM Codes
The placeholder character X fills empty positions in codes that require a seventh character but are not naturally six characters long, such as many adverse effect and poisoning codes. Without the X, the code is invalid for reporting because the seventh character would occupy the wrong position in the data field.
Example: A poisoning code requires a seventh character but is only five characters long. Decision: insert the placeholder X in the empty positions so the seventh character lands in the seventh position.
Mistake to avoid: Do not drop the X or shift the seventh character left; the code is invalid without correct placement.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
9. Seventh Character Requirements
Certain categories require a seventh character for all codes within them, such as extension identifying initial, subsequent, or sequela encounters. A code with an applicable seventh character is invalid without it, and the seventh character must always occupy the seventh position, with placeholder X filling any gaps.
Example: A fracture category requires an extension identifying the encounter type. Decision: append the applicable seventh character even though the base code has fewer characters, using the placeholder where needed.
Mistake to avoid: Avoid reporting a fracture or injury code without its encounter extension, which makes the code invalid.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
10. Excludes1 Versus Excludes2 Notes
An Excludes1 note means the excluded code is never reported with the code above the note, typically because the two conditions cannot coexist, such as congenital versus acquired forms. An exception exists when the two conditions are clearly unrelated. An Excludes2 note instead permits both codes when the patient truly has both conditions.
Example: A congenital form of a condition is billed alongside the acquired form of the same condition. Decision: only one code is reportable, because the Excludes1 note bars reporting both together.
Mistake to avoid: Do not treat every excludes note as a prohibition; Excludes2 conditions may be coded together when documented.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
11. The With Presumption of Causal Linkage
The words with or in between two conditions in a code title or index entry mean associated with or due to, and the classification presumes a causal relationship even without explicit provider linkage. Code the conditions as related unless documentation clearly states they are unrelated or a specific guideline requires documented linkage.
Example: Documentation shows diabetes and a circulatory complication without explicit linkage. Decision: code the conditions as related, because the classification presumes the causal relationship unless the provider states otherwise.
Mistake to avoid: Avoid querying the provider for linkage the classification already presumes, unless documentation contradicts it.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
12. Default Codes When Detail Is Absent
A default code appears next to a main term in the Alphabetic Index and represents the condition most commonly associated with that term, or its unspecified form. When a condition is documented without additional detail such as acute or chronic, the default code is assigned rather than a more specific alternative.
Example: A discharge note says appendicitis with no acute or chronic qualifier. Decision: assign the default code listed at the main term, which represents the unspecified presentation.
Mistake to avoid: Do not select a more specific code than the documentation supports just because it exists in the index.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Diagnosis Selection and Documentation Rules
13. Provider Statement Over Clinical Criteria
Code assignment rests on the provider's diagnostic statement that a condition exists, not on the clinical criteria the provider used to reach it. If the provider says the patient has the condition, that statement is sufficient for coding. When record documentation conflicts, the correct action is to query the provider rather than choose between statements.
Example: A provider documents hypertension based on repeated readings meeting clinical thresholds. Decision: assign the hypertension code, because the diagnostic statement alone controls code assignment.
Mistake to avoid: Avoid withholding a code because the coder believes the clinical evidence supporting the diagnosis is thin.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
14. Uncertain Diagnoses in Outpatient Coding
For outpatient encounters, diagnoses described as suspected, possible, rule out, or working are not coded as if confirmed. Instead, code the signs, symptoms, or other reason for the visit. This contrasts with inpatient rules, where conditions confirmed after study may be retroactively coded as established at discharge.
Example: An office note lists a suspected condition as the reason for the visit. Decision: code the symptom or reason instead, because the unconfirmed condition is not reported in the outpatient setting.
Mistake to avoid: Do not code a suspected outpatient diagnosis as confirmed; report the documented symptoms or reason instead.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
15. Principal Versus First-Listed Diagnosis
Inpatient coding uses the principal diagnosis, defined after study as the condition chiefly responsible for admission, with detailed rules for interrelated conditions, comparative diagnoses, and failed treatment plans. Outpatient coding instead selects a first-listed diagnosis for the encounter. Payer reviewers must know which setting's rule governs the claim at hand.
Example: A hospital inpatient record shows two interrelated conditions each meeting the principal diagnosis definition. Decision: follow the inpatient sequencing guidance for interrelated conditions, which has no outpatient equivalent.
Mistake to avoid: Avoid applying inpatient principal-diagnosis sequencing rules to outpatient claims and vice versa.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
16. Non-Provider Documentation Exceptions
Code assignment generally rests on the treating provider's documentation, but limited exceptions allow other clinicians' documentation to support specific data: BMI, pressure ulcer stage, coma scale, laterality, and similar items. The associated diagnosis itself must still come from the provider, and conflicts between clinicians require a provider query.
Example: A nurse documents a pressure ulcer stage but the provider documents the ulcer diagnosis. Decision: use the nurse's stage with the provider's diagnosis, because staging is a permitted exception.
Mistake to avoid: Do not assign a diagnosis solely from nursing or ancillary notes; only the enumerated data elements qualify.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
17. Appropriate Use of Symptom and Unspecified Codes
Sign, symptom, and unspecified codes have legitimate uses when documentation does not support a definitive diagnosis. Each encounter is coded to the level of certainty known at that time. Payer reviewers should not treat every unspecified code as an error, though a pattern of avoiding available specificity warrants provider education.
Example: A visit note documents fatigue with no workup conclusion. Decision: report the fatigue symptom code, because it accurately reflects the level of certainty known for that encounter.
Mistake to avoid: Avoid automatically flagging unspecified codes as deficiencies; judge them against the documentation available.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
18. Laterality and Conflicting Documentation
When laterality is not documented by the patient's provider, code assignment may rely on documentation from other clinicians. If documentation conflicts about the affected side, the provider should be queried. Unspecified side codes should rarely be used, and only when clarification is genuinely unobtainable.
Example: The provider documents right knee pain but a therapy note references the left knee. Decision: query the provider, because conflicting laterality documentation cannot be resolved by choosing one source.
Mistake to avoid: Do not default to an unspecified side code when a simple provider query could resolve the conflict.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Medicare Policy Distinct from CPT Rules
19. Reading the Medicare Fee Schedule Relative Value File
The Medicare Physician Fee Schedule Relative Value File lists indicators for global days, multiple procedure status, bilateral surgery, and assistant surgeon applicability. A zero in the multiple procedure column means no reduction applies; a two means the reduction applies. Payer reviewers use this file to validate payment logic rather than guessing.
Example: A payer reviewer questions whether a procedure is reduced when billed with others. Decision: check the multiple procedure indicator in the relative value file before applying any reduction.
Mistake to avoid: Avoid assuming all surgical codes are subject to the same payment reduction without checking the indicator.
Reference: AAPC CPMA study guide sample
20. Non-Participating Provider Limiting Charge
A non-participating provider who does not accept assignment is limited in what may be billed to the beneficiary. The limiting charge is set at a percentage above the non-participating fee schedule amount, and charges beyond it expose the provider to penalties. Payer reviewers check that balance billing stays within this ceiling.
Example: A non-participating provider bills above the approved amount. Decision: the provider may collect only up to the limiting charge, not the full billed amount, from the patient.
Mistake to avoid: Do not confuse the limiting charge with the participating provider's approved amount; they are different ceilings.
Reference: AAPC CPB study guide sample
21. Assignment and Contractual Write-Offs
When a provider accepts assignment, Medicare pays its approved amount directly to the provider and the provider must write off the difference between the charge and the approved amount. The patient owes only deductible and coinsurance amounts. Payer review confirms write-offs were taken rather than balance-billed to the beneficiary.
Example: A participating provider bills a service above the approved amount. Decision: the provider writes off the difference, because accepting assignment binds them to the approved amount.
Mistake to avoid: Avoid billing the patient the difference between the charge and the approved amount after accepting assignment.
Reference: AAPC CPB study guide sample
22. Part B Coinsurance Calculation on the Approved Amount
Medicare Part B beneficiaries generally owe a coinsurance percentage of the approved amount once the annual deductible is satisfied, with the payer covering the remainder. Payer-side reviewers verify that patient responsibility is calculated on the approved amount, never on the provider's full submitted charge.
Example: A service billed at $95.00 carries a Medicare approved amount of $68.40, and the patient's annual Part B deductible is already met. Decision: the payer pays 80 percent of the approved amount ($54.72) and the patient owes the 20 percent coinsurance ($13.68); neither amount is computed from the $95.00 submitted charge.
Mistake to avoid: Do not compute patient coinsurance from the billed charge instead of the payer's approved amount.
Reference: AAPC CPB study guide sample
23. Screening Service Diagnosis Requirements
Preventive and screening services often carry payer-specific diagnosis requirements that determine coverage, such as frequency rules or documented risk factors. A correctly coded service can still be non-covered when the reported diagnosis fails the policy. Payer reviewers must read the full screening policy, not just the code description.
Example: A screening service is submitted with a diagnosis that does not meet the payer's coverage criteria. Decision: deny for lack of covered indication, because screening policies carry diagnosis requirements.
Mistake to avoid: Avoid approving a screening claim solely because the procedure code is listed as covered; verify the diagnosis too.
Reference: AAPC CPB study guide sample
24. Reasonable and Necessary as the Coverage Standard
Payers, including Medicare, pay only for services meeting the reasonable and necessary standard for diagnosing or treating the patient's condition. Providers may order any test they judge appropriate, but payment depends on documented medical necessity. Payer reviewers link each service to a documented indication before approving payment.
Example: A provider orders extensive testing for general surveillance. Decision: the claim is vulnerable to denial, because payment requires the service be reasonable and necessary for the condition.
Mistake to avoid: Do not treat a provider's order alone as proof of medical necessity; the record must support the indication.
Reference: AAPC CPMA study guide sample
Fraud, Abuse, and Compliance Exposure
25. Fraud Versus Abuse Distinction
Abuse describes actions creating unnecessary costs without intentional deception, such as misuse of codes or billing non-medically-necessary services. Fraud requires false statements or misrepresentation made to obtain payment. The distinction drives severity: abuse typically invites education and repayment, while fraud triggers enforcement exposure.
Example: A practice bills a higher service level than was provided to increase payment. Decision: classify as fraud, because intentional misrepresentation distinguishes fraud from abuse.
Mistake to avoid: Avoid labeling careless billing mistakes as fraud; intent to deceive separates the two categories.
Reference: AAPC CPMA study guide sample; AAPC CPB study guide sample
26. False Claims Act Conduct in Billing
The False Claims Act reaches healthcare conduct including falsifying chart notations, billing services not performed, upcoding, unbundling, and billing physician services performed by non-physician providers without regard to supervision guidelines. Payer reviewers recognizing these patterns escalate them rather than treating them as routine coding variances.
Example: A claim is submitted for physician services actually performed by an unqualified staffer. Decision: this is a false claim, because services billed as physician work must meet applicable supervision rules.
Mistake to avoid: Do not resolve an apparent false claim through a simple coding correction without compliance escalation.
Reference: AAPC CPMA study guide sample
27. Reverse False Claims and Overpayment Retention
Beyond submitting false claims, liability arises under the reverse false claims concept when a person acts improperly to avoid paying money owed to the government, such as keeping identified overpayments. Payer-side reviewers treat discovered overpayments as triggering repayment obligations, not optional adjustments to absorb.
Example: A practice discovers an overpayment but delays repayment while continuing to bill. Decision: this creates reverse false claims exposure, because avoiding repayment of money owed is actionable.
Mistake to avoid: Avoid sitting on identified overpayments; retention itself creates liability exposure.
Reference: AAPC CPB study guide sample
28. Qui Tam Whistleblower Actions
A qui tam action is a civil suit brought on behalf of a private relator and the government. If a recovery occurs, the relator may be awarded a percentage of the amount recovered. Payer and provider staff should understand that internal billing irregularities can surface through whistleblowers, making proactive compliance preferable.
Example: A billing employee reports systematic upcoding and the government recovers funds. Decision: the whistleblower may receive a percentage of the recovery through the qui tam mechanism.
Mistake to avoid: Do not assume billing improprieties stay internal; whistleblower mechanisms can surface them externally.
Reference: AAPC CPB study guide sample
29. OIG Role and Verifiable Audit Authority
The Office of Inspector General oversees fraud and abuse in federal healthcare programs, publishes guidance, and supports enforcement. Audit findings and recommendations must be supported by applicable, verifiable guidelines that are enumerated and explained for the provider. Payer reviewers cite the specific OIG or CMS authority behind each finding.
Example: A payer-side reviewer wants authority for a documentation standard. Decision: cite OIG-published guidance, because audit findings must rest on verifiable applicable rules.
Mistake to avoid: Avoid issuing findings based on custom or opinion without citing a controlling published source.
Reference: AAPC CPMA study guide sample
30. Improper Payment Error Identification Programs
The Comprehensive Error Rate Testing program identifies errors causing improper payments in the Medicare program. Its findings highlight documentation areas needing improvement. Payer-side and practice reviewers can use published error patterns to focus audits and education on service types where documentation failures recur, rather than sampling blindly.
Example: A reviewer sees recurring payment errors in a specific service category. Decision: use the error findings to target provider education and focused review in that area.
Mistake to avoid: Do not dismiss error-rate findings as payer trivia; they direct where documentation risk concentrates.
Reference: AAPC CPMA study guide sample
HIPAA Privacy in Payer Operations
31. Covered Entity Categories Under the Privacy Rule
The Privacy Rule covers three categories: health plans, healthcare clearinghouses, and any healthcare provider transmitting health information electronically in connection with standard transactions. Payers are health plans and thus covered entities. A payer reviewer applies privacy requirements knowing both sides of the transaction are regulated.
Example: A billing service processes claims containing identifiable health data for a clinic. Decision: it functions as a clearinghouse covered entity, subject to the Privacy Rule's applicable provisions.
Mistake to avoid: Do not assume only providers are covered; health plans and clearinghouses are equally regulated.
Reference: HHS Summary of the HIPAA Privacy Rule
32. Business Associates and Required Agreements
A business associate performs functions for a covered entity involving protected health information, such as claims processing, data analysis, utilization review, billing, or repricing. The covered entity must impose written safeguards through a business associate agreement and cannot authorize any use or disclosure the Rule itself would prohibit.
Example: A payer hires an outside firm for utilization review involving identifiable data. Decision: a business associate agreement with required safeguards must be in place before the work proceeds.
Mistake to avoid: Avoid exchanging protected data with a contractor before a compliant agreement is executed.
Reference: HHS Summary of the HIPAA Privacy Rule
33. Minimum Necessary Standard
Covered entities must make reasonable efforts to limit uses, disclosures, and requests of protected health information to the minimum necessary for the purpose. The entire record may not be requested unless specifically justified. Exceptions include disclosures for treatment, to the individual, under authorization, or required by law.
Example: A payer requests a patient's entire record to adjudicate one claim. Decision: limit the request to the minimum necessary, because payment review does not justify the whole record absent specific justification.
Mistake to avoid: Do not request or send full records routinely; justify the amount or narrow the request.
Reference: HHS Summary of the HIPAA Privacy Rule
34. Authorization Requirements Beyond Permitted Uses
Uses and disclosures beyond treatment, payment, healthcare operations, or other permitted purposes require the individual's written authorization, which must be in plain language and specify the information, recipients, expiration, and revocation rights. Authorizations should be updated periodically, and certain communications like marketing require them.
Example: A payer wants claim data for its own marketing communications. Decision: written authorization is required, because marketing falls outside treatment, payment, and operations.
Mistake to avoid: Avoid relying on a treatment consent form where a distinct HIPAA authorization is required.
Reference: HHS Summary of the HIPAA Privacy Rule; AAPC CPB study guide sample
35. De-Identification of Health Information
De-identified health information neither identifies nor provides a reasonable basis to identify an individual, and it is unrestricted under the Privacy Rule. De-identification is achieved either through a formal statistical determination or by removing specified identifiers, with no actual knowledge that the remainder could identify someone.
Example: A payer prepares a public report of utilization statistics. Decision: use de-identified data with specified identifiers removed, because de-identified information carries no use restrictions.
Mistake to avoid: Do not strip only the name and call data de-identified; the full identifier list must be addressed.
Reference: HHS Summary of the HIPAA Privacy Rule
36. Psychotherapy Notes Heightened Protection
Psychotherapy notes, a mental health professional's separately kept session analysis notes, require authorization for most uses, including payment purposes, with narrow exceptions such as the originator's own treatment, training, legal defense, and oversight. They are also excluded from the individual's right of access to records.
Example: A payer requests a provider's counseling session notes for payment review. Decision: the notes cannot be released without authorization, because psychotherapy notes receive heightened protection.
Mistake to avoid: Do not treat psychotherapy notes like ordinary record content for payment disclosure purposes.
Reference: HHS Summary of the HIPAA Privacy Rule
Health Plan Models and Coverage Determinations
37. HMO Versus PPO Network Rules
HMOs arrange prepaid care through designated providers and typically require members to maintain a primary care physician and obtain referrals. PPOs build negotiated-fee networks but let members see network providers without referrals and without a primary care gatekeeper. Payer reviewers confirm which model's rules govern a disputed referral claim.
Example: A member wants to see a specialist without seeing a primary care physician first. Decision: the PPO permits direct access, while an HMO generally requires the referral gatekeeping step.
Mistake to avoid: Do not deny a PPO claim for lacking a referral; that requirement belongs to HMO models.
Reference: AAPC CPMA study guide sample; AAPC CPB study guide sample
38. Medicare Part A Versus Part B Coverage Split
Part A covers hospital care, skilled nursing facility care, hospice, and home health services, with beneficiaries generally enrolled automatically. Part B covers medically necessary physician services, ambulance, durable equipment, and expanded preventive services, and requires enrollment with premium and deductible obligations. Payer processing depends on matching the service to the correct part.
Example: A claim arrives for a physician office visit under Part A. Decision: route it under Part B, because physician services fall under Part B while Part A covers hospital-type stays.
Mistake to avoid: Avoid adjudicating a physician claim under Part A benefits; physician services belong to Part B.
Reference: AAPC CPB study guide sample
39. Medicaid Federal-State Structure
Medicaid is federally overseen but state administered: each state sets eligibility, scope, and payment rates. To receive federal matching funds, states must cover mandatory categories including inpatient and outpatient hospital services, physician services, laboratory and X-ray, and specified services for children. Optional services vary by state and affect what claims are payable.
Example: A state plan omits a federally mandatory service category. Decision: federal matching funds are at risk, because mandatory categories must be covered for eligibility to draw funding.
Mistake to avoid: Do not assume Medicaid benefits are uniform nationally; verify the specific state plan's covered services.
Reference: AAPC CPB study guide sample
40. CHIP Coverage for the Medicaid Income Gap
The Children's Health Insurance Program offers free or low-cost coverage for families whose incomes exceed Medicaid limits but who cannot afford private insurance. It is state administered and jointly funded. Payer staff verifying pediatric coverage must distinguish CHIP from Medicaid because eligibility rules and funding differ.
Example: A family earns too much for Medicaid but cannot afford private coverage for a child. Decision: check CHIP eligibility, because the program covers children in that income gap.
Mistake to avoid: Avoid denying pediatric coverage without checking CHIP when Medicaid eligibility fails on income.
Reference: AAPC CPB study guide sample
41. Birthday Rule for Dependent Coordination
When a child is covered under both parents' plans, the birthday rule designates the plan of the parent whose birthday falls first in the calendar year as primary. Only month and day matter, not year of birth. Payer staff apply this coordination rule before adjudicating which plan pays first on a dependent claim.
Example: A child's father has a birthday in March and the mother has a birthday in November. Decision: the father's plan is primary, because the parent whose birthday falls earlier in the calendar year holds the primary plan, regardless of birth year.
Mistake to avoid: Do not make one parent's plan primary based on age; the rule ignores birth year entirely.
Reference: AAPC CPB study guide sample
42. Medicare Secondary Payer Screening
When a Medicare beneficiary has other coverage, Medicare may be the secondary payer. Providers use the Medicare Secondary Payer questionnaire to determine primary versus secondary status before submitting claims. Billing Medicare as primary when another payer owes first can generate overpayments requiring repayment later.
Example: A Medicare patient presents another active group health plan. Decision: complete the secondary payer inquiry before billing Medicare, because another plan may owe primary payment.
Mistake to avoid: Avoid defaulting to Medicare as primary without screening for other coverage on file.
Reference: AAPC CPB study guide sample
Claims Processing and Data Capture
43. Clean Claim Standard
A clean claim contains all information necessary for processing. Payers measure submission quality against this standard, and incomplete claims reject or delay. Payer-side staff identify the specific missing element, such as subscriber data or service detail, so the provider can correct and resubmit rather than guess at the deficiency.
Example: A claim arrives missing the subscriber ID. Decision: it is not a clean claim and will reject, because processing requires all necessary data elements.
Mistake to avoid: Do not adjudicate a claim lacking required elements; return it with the specific deficiency identified.
Reference: AAPC CPB study guide sample
44. Clearinghouse Role in Claim Transmission
A clearinghouse processes or facilitates claim processing for providers and healthcare plans, converting nonstandard data into standard formats and vice versa. Many small practices submit through clearinghouses to meet transaction standards. Payer staff recognize clearinghouse-transmitted claims and address format rejections at that layer.
Example: A practice's claims fail because its format is nonstandard. Decision: route submissions through a clearinghouse, which converts data into the standard transaction the payer accepts.
Mistake to avoid: Avoid telling a provider to fix a payer edit when the rejection actually sits in the clearinghouse translation.
Reference: AAPC CPB study guide sample
45. Chargemaster and Revenue Code Classification
The chargemaster is the hospital-specific master list of all procedures, services, supplies, and medications billed to payers, with charges, codes, and revenue codes. Revenue codes are four-digit codes established by the national uniform billing committee that classify line items. Payer processing of institutional claims depends on these classifications.
Example: A hospital line item lacks its four-digit revenue code. Decision: the chargemaster entry is incomplete, because revenue codes classify each billable line for payers.
Mistake to avoid: Do not confuse the internal item number or general ledger number with the revenue code on a claim.
Reference: AAPC CPB study guide sample
46. Insurance Card Verification at Registration
Front and back copies of the patient's insurance card should be kept in the record for identification and claim data. When eligibility fails or a claim rejects for subscriber data, staff verify against the card copy, contact the patient for updates, and let the patient choose to reschedule or self-pay if coverage truly lapsed.
Example: A claim rejects for an invalid subscriber ID. Decision: pull the copied insurance card and correct the system entry before rebilling, rather than transferring the balance to the patient.
Mistake to avoid: Avoid billing the patient for a rejection that a card verification would have prevented.
Reference: AAPC CPB study guide sample
47. Rejection Versus Denial Handling
A rejection means the claim failed front-end edits and never entered adjudication; the fix is correcting data and resubmitting. A denial is an adjudicated determination requiring an appeal or adjustment with supporting documentation. Payer staff route each event differently, and confusing them wastes appeal windows on correctable data errors.
Example: An electronic report shows a claim rejected for a missing subscriber ID. Decision: correct the data and rebill, because a rejection never entered adjudication and no denial determination exists.
Mistake to avoid: Do not appeal a data rejection; correct and rebill it, and reserve appeals for adjudicated denials.
Reference: AAPC CPB study guide sample
48. Inpatient Versus Outpatient Payment Basis
Inpatient and outpatient hospital claims are paid on different bases: inpatient payment is driven by the diagnoses reported for the stay, while outpatient payment follows the procedures reported. Misclassifying patient status therefore changes the entire payment methodology, not just a code or two, and requires corrected billing.
Example: An inpatient stay is mistakenly billed as outpatient. Decision: payment basis is wrong, because inpatient claims are paid on diagnoses while outpatient claims follow reported procedures.
Mistake to avoid: Avoid treating patient status as a minor demographic field; it determines the payment methodology.
Reference: AAPC CPB study guide sample
E/M, Modifiers, and Medical Necessity Review
49. One Initial Infusion Code, Chosen by Encounter Reason
When multiple infusions, injections, or combinations are administered, only one initial service code is reported unless protocol requires that two separate IV sites be used. The initial code that best describes the key or primary reason for the encounter is reported irrespective of the order in which the infusions are administered. Payer reviewers therefore validate the initial administration code against the documented purpose of the encounter, not the administration sequence.
Example: A claim reports the initial infusion code for an antiemetic administered first, followed by a 45-minute antibiotic infusion that was the documented reason for the encounter. Decision: the antibiotic infusion is the initial service, because the key reason for the encounter controls initial code selection, not which medication was administered first.
Mistake to avoid: Do not assign the initial code to whichever infusion started first; the encounter's primary purpose governs.
Reference: AAPC CPMA study guide sample
50. NCCI Edits and Modifier Bypass Review
NCCI edits pair codes that cannot ordinarily be reported together, with one column code inclusive of the other. Where documentation supports a distinct service meeting edit criteria, an appropriate modifier may bypass the edit. Payer reviewers verify the documentation actually supports separation before accepting modifier-bypassed pairs.
Example: Two codes on a claim hit an edit marking one inclusive to the other. Decision: review whether documentation supports a distinct service, and only then consider the appropriate modifier.
Mistake to avoid: Avoid accepting a modifier that overrides an edit without documentation proving the services were distinct.
Reference: AAPC CPMA study guide sample
51. Medical Necessity Linking Service to Diagnosis
Medical necessity ties each reported service to a documented diagnosis or clinical indication the payer accepts for coverage. A perfectly performed and coded service is still non-covered without a supporting indication. Payer reviewers match service codes to diagnosis codes and request additional documentation when the link is unclear.
Example: A laboratory panel is billed with only a general exam diagnosis. Decision: deny or develop the claim, because the reported diagnosis fails to establish medical necessity for the test.
Mistake to avoid: Do not approve services solely on technical correctness; verify the diagnosis supports the indication.
Reference: AAPC CPMA study guide sample
52. Incidental Hydration Is Not Separately Reported
The fluid used to administer a drug is considered incidental hydration and is not separately reported. Payer reviewers examine the administration record to determine whether the fluid functioned as the medication vehicle before allowing a separate hydration charge on the same claim.
Example: A claim reports a hydration code alongside an infusion code where the administration note documents 500 mL of saline running solely as the vehicle for an IV antibiotic. Decision: no separate hydration payment is due, because the fluid used to administer the drug is incidental to the administration.
Mistake to avoid: Do not pay a hydration line when the fluid was the medication vehicle; the hydration is bundled into the drug administration.
Reference: AAPC CPMA study guide sample
53. IV Push Versus Infusion by Time and Presence
An intravenous or intra-arterial push is defined as an injection in which the healthcare professional administering the substance is continuously present to administer the injection and observe the patient, or an infusion of 15 minutes or less. Administrations exceeding 15 minutes without continuous presence are infusions, and the reported administration code changes accordingly. Payer reviewers verify documented start and stop times before accepting a push code.
Example: A claim reports a push administration code for a medication documented as infused over 32 minutes, with the nurse returning periodically rather than remaining at the bedside. Decision: the push code is not supportable, because the administration exceeded 15 minutes and the administering professional was not continuously present; infusion reporting applies instead.
Mistake to avoid: Do not accept a push code based on the drug name or route alone; documented time and continuous presence control the distinction.
Reference: AAPC CPMA study guide sample
54. Anesthesia Coding from Time and Physical Status
Anesthesia coding is driven by the procedure performed plus the patient's physical status, with time from documented anesthesia start to stop determining units. Physical status modifiers reflect documented severity. Additional procedures the anesthesiologist personally performs, such as line placement, are reported separately with supporting documentation.
Example: An anesthesia record shows start and stop times plus a physical status of 2. Decision: compute total time from the documented start and stop and append the physical status modifier reflecting the documented status.
Mistake to avoid: Avoid selecting the anesthesia code from the surgical technique rather than the procedure that determines the base code.
Reference: AAPC CPMA study guide sample
Payer Audit, Risk Analysis, and Communication
55. Defining Audit Objective and Scope
An audit's objective states its high-level goal, while the scope defines the parameters: which providers, payers, date range, service types, and record settings are included, and explicitly what is excluded. A clear scope prevents misleading outcomes and keeps findings tied to the questions the review was designed to answer.
Example: A review intends to cover one new provider's billing since hire. Decision: state the objective, the provider, the date range, and the payers included, and note what is excluded.
Mistake to avoid: Avoid starting a review without written boundaries; unscoped findings invite disputes over relevance.
Reference: AAPC CPMA study guide sample
56. Controlling Versus Persuasive Standards
To declare an error, an auditor is limited to controlling standards, such as binding regulations or contract terms. Where no controlling standard exists, persuasive sources may identify potential post-payment risk, with citations and qualifications. Distinguishing the two is a core skill, because it separates defensible error findings from advisory risk commentary.
Example: A payer bulletin is ambiguous about a reporting method. Decision: report potential risk with citations rather than declaring error, because no controlling standard governs the question.
Mistake to avoid: Do not declare a billing error citing only persuasive guidance; label it as risk instead.
Reference: AAPC CPMA study guide sample
57. Contract-Based Payer Rules
Commercial plans are contract based: benefits arise between insurer and subscriber, and in-network providers agree to abide by payer policies through separate contracts. The auditor must read the contract to determine whether nonconformance permits recoupment, only network termination, or a corrective action opportunity, which changes how findings are framed.
Example: A provider disputes a finding based on a payer policy. Decision: review the participation contract first, because contract terms determine which policies are binding and their consequences.
Mistake to avoid: Avoid assuming every published payer policy is enforceable against a provider without checking the contract.
Reference: AAPC CPMA study guide sample
58. EHR Copying and Cloning Risk
When records are printed from electronic health record systems, auditors must watch for copying or cloning, where prior note content is carried forward unchanged. Cloned documentation undermines the credibility of the record supporting each encounter's billed services and is a recognized audit risk requiring provider education and correction.
Example: A record shows identical history and exam text across many visits. Decision: flag cloned documentation, because copied entries undermine the reliability of the billed services.
Mistake to avoid: Do not accept identical multi-visit documentation at face value as support for separately billed encounters.
Reference: AAPC CPMA study guide sample
59. Sample Selection Methods for Reviews
Audit selections can be random, controlled to a service type or level, or targeted by high volume, high risk, frequent denials, or past errors. Retrospective audits sample from billing reports, while prospective audits review held claims before release. The selection method must serve the stated objective and be documented.
Example: A practice wants to audit its highest-risk service category. Decision: select by high-risk and high-volume criteria rather than pure randomization, to target the review's purpose.
Mistake to avoid: Avoid letting convenience drive chart selection; document the method so findings are defensible.
Reference: AAPC CPMA study guide sample
60. Communicating Findings and Corrective Action
Audit results are validated through risk analysis performed at the outset, and findings must cite the applicable policy provision or binding rule. Communicating results to the provider includes identifying specific risks, recommending corrective action with supporting documentation, and distinguishing mandated changes from suggested improvements.
Example: A review finds repeated unsupported service levels. Decision: present findings with citations, quantify the pattern, and recommend a corrective action plan with follow-up education.
Mistake to avoid: Avoid delivering findings without citations or a recommended corrective path; unsupported conclusions get dismissed.
Reference: AAPC CPMA study guide sample
References and further reading
Source links checked on Oct 2, 2026.