Health Information & Coding · Independent exam preparation

CPMA Preparation Guide: Documentation, Coding, Sampling, and Audit Decisions Study Guide

Practise defensible medical audit decisions: validate documentation, apply coding rules, design samples, quantify findings, and communicate corrective actions.

By CertMedbry · Updated 29 October 2026

60 concepts explainedWorked examples & common pitfallsOfficial blueprint references

Learn to decide whether documentation supports a claim, distinguish coding errors from broader compliance concerns, and turn audit evidence into defensible findings. This guide addresses AAPC's Certified Professional Medical Auditor credential through physician-service auditing examples, including United States federal program and Medicare rules where identified. Its 60 concepts are a selective foundation; AAPC's official public outline defines the full examination scope. The accompanying questions and flashcards are independently authored learning materials.

Try 20 free practice questions

What is the exam format?

Check the question types, timing and outline before planning your revision.

How many questions and audit cases does the CPMA examination contain?

AAPC describes 100 multiple-choice questions and approximately 18 audit cases within the examination. The consulted issuer description does not identify a separate number of scored and unscored or pretest questions, nor does it explain how individual cases map to questions.

Certified Professional Medical Auditor (CPMA) certification — AAPC Help Center

How long is the examination, and what passing threshold is published?

AAPC states that candidates complete the examination in one sitting within four hours and must answer 70% of the questions correctly to pass. Performance on this guide's independent drills does not predict an examination result.

Certified Professional Medical Auditor (CPMA) certification — AAPC Help Center

How is the examination delivered, and is it adaptive?

AAPC lists computer-based testing at a testing center or online at home with a live remote proctor. The consulted description does not state that the examination is adaptive or describe an adaptive algorithm. Both delivery options concern the same CPMA credential.

Certified Professional Medical Auditor (CPMA) certification — AAPC Help Center

Is CPMA open book, and which references are identified?

AAPC describes an open-book examination and lists AMA CPT Professional Edition, ICD-10-CM, and HCPCS Level II as approved code books. Its article recommends current-year books, permits the preceding year, current year, or a combination, and allows only one copy of each book. Confirm the applicable candidate instructions before testing.

Certified Professional Medical Auditor (CPMA) certification — AAPC Help Center

Which outline and effective dates apply to this guide?

The public AAPC certification article is dated May 23, 2024, and the current study-guide page offers a 2026 edition. These sources were verified on October 29, 2026. Neither states a blueprint effective date, revision identifier, or numerical domain weights. The article publication date and study-guide edition are not examination blueprint effective dates.

Certified Professional Medical Auditor (CPMA) certification — AAPC Help Center · Official CPMA Certification Study Guide — AAPC

How is coverage allocated when AAPC publishes no domain weights?

The guide assigns ten concepts to each of the six supplied content domains. The 20 questions and 20 flashcards distribute coverage across all six domains with small editorial differences. These allocations support breadth and do not represent official examination percentages. Use the complete issuer outline to identify additional study needs.

Official CPMA Certification Study Guide — AAPC · Certified Professional Medical Auditor (CPMA) certification — AAPC Help Center

What experience level and jurisdiction do the examples assume?

AAPC describes CPMA as a difficult, high-level examination for candidates with auditing training or experience and familiarity with physician services, including E/M. Legal examples here concern United States federal law; Medicare payment examples are labeled accordingly. A Medicare rule should not automatically be applied to every commercial payer.

Certified Professional Medical Auditor (CPMA) certification — AAPC Help Center · Fraud & Abuse Laws — HHS Office of Inspector General

How do coding-reference dates differ from examination-outline dates?

The FY 2027 ICD-10-CM guidelines apply October 1, 2026–September 30, 2027. The supplied 2026 Medicare NCCI Chapter I has a January 1, 2026 revision date. These dates identify coding-reference applicability, not CPMA blueprint changes. For an audit, select the rules and code versions applicable to the reviewed services.

ICD-10-CM Official Guidelines for Coding and Reporting — FY 2027 · Medicare NCCI Policy Manual 2026 — Chapter I

CPMA is an advanced medical auditing certification for candidates with relevant training or experience, including evaluation and management auditing. It builds on coding knowledge and requires judgments about evidence, reimbursement, sampling, compliance, and communication. This guide follows the six content sections identified in AAPC's current study-guide description.

Outline used: Public AAPC CPMA exam content outline verified on 2026-10-11 (Asia/Hong_Kong): official certification help article dated May 23, 2024, corroborated by AAPC's current 2026 CPMA study-guide description. Neither consulted source states a blueprint effective date, revision identifier, or numerical domain weights. The six learning domains below follow the study-guide content sections and encompass the expertise areas in the certification article. The workbook label matches the official credential; the assigned canonical slug is preserved.

60 key concepts: understand, apply and avoid the traps

Work through the questions by exam domain. Explain the answer in your own words, try the example, then check the common pitfall.

Medical Record Standards and Documentation Guidelinesnot stated

1.What makes a medical record usable as audit evidence?

A usable record connects the patient, service date, responsible practitioner, clinical work, and authentication in a traceable account. Auditors compare those elements with the billed service rather than treating the presence of a note as sufficient support. Missing components have different consequences: an unidentified author raises authentication concerns, while a complete signature cannot supply an undocumented service. The decisive question is whether reliable evidence supports each material claim element.

Apply it

A claim reports a procedure, but the only available note documents counseling and contains a valid signature. Record the missing procedural support separately from authentication; request existing procedure documentation before deciding whether the billed service is supported.

Common pitfall: A signed record is not automatically a sufficient record. Authentication establishes responsibility for content; it does not establish every billed service or payment requirement.

Medicare Program Integrity Manual — Chapter 3

2.How should a correction preserve the original record?

A defensible correction preserves the original information and identifies the correction's author and date. This allows reviewers to distinguish the original clinical account from later clarification. Electronic systems should retain a traceable change history rather than silently replacing content. Evaluate both the correction process and what the corrected information actually establishes. A transparent correction may resolve an error, but its existence does not automatically validate a previously unsupported claim.

Apply it

A clinician discovers that a note names the wrong side. The correction identifies the clinician and current date, preserves the original wording, and explains the change. The auditor evaluates that entry alongside the contemporaneous procedure evidence.

Common pitfall: Deleting the original wording makes a cleaner-looking note but weakens its evidentiary history. Never treat a backdated replacement as equivalent to a transparent correction.

Medicare Program Integrity Manual — Chapter 3

3.When can a delayed entry contribute to an audit?

A delayed entry records information after the original service and should identify its actual entry date and author while preserving existing content. Distinguish the service date from the date information was added. Assess whether the entry supplies a credible clarification consistent with other evidence and applicable review requirements. Its later timing is relevant to evidentiary weight, but timing alone does not establish either that the service occurred or that the entry is fraudulent.

Apply it

A note entered several days after an encounter explicitly identifies the encounter date and later entry date. Compare its account with the order, results, and existing notes, and document which facts depend on the delayed entry.

Common pitfall: Do not assume every late entry is invalid or accept every late entry without scrutiny. Transparency and consistency matter more than a cosmetic timestamp.

Medicare Program Integrity Manual — Chapter 3

4.How does authentication differ from clinical sufficiency?

Authentication identifies the person responsible for a record entry through an acceptable handwritten or electronic signature process. Clinical sufficiency asks whether the content supports the service, diagnosis, and medical necessity under review. These are separate tests, and a record may pass one while failing the other. An auditor should describe the specific deficiency and applicable authentication pathway instead of using a single generic label such as incomplete documentation.

Apply it

An electronically signed note clearly identifies its author but contains no support for the billed additional service. Mark authentication as satisfied and analyze the service deficiency independently, preserving an accurate explanation of why payment support is lacking.

Common pitfall: A legible practitioner name in a header may identify an intended author without proving authentication. Conversely, a valid signature cannot compensate for absent clinical work.

Medical Record Maintenance & Access Requirements — CMS, January 2026 · Medicare Program Integrity Manual — Chapter 3

5.Which signature problems can logs or attestations address?

A signature log links an illegible signature to its author. For Medicare documentation eligible for a signature attestation, the original entry's author must sign and date a statement sufficiently identifying the beneficiary and the existing entry and confirming authorship of that entry. Another practitioner cannot attest merely because both practitioners belong to the same group. The statement authenticates existing documentation; it does not supply undocumented clinical work. Medicare does not accept a signature attestation to cure an unsigned order, so distinguish progress-note authentication from order requirements.

Apply it

An unsigned progress note identifies its author and beneficiary. A signed, dated statement by that author identifying the beneficiary and note and affirming that the author wrote it can address the missing signature under Medicare review rules. A group colleague's statement cannot substitute. For an unsigned order, evaluate the applicable order requirements and existing ordering evidence separately.

Common pitfall: An attestation must establish who authored the existing entry, not merely that someone agrees with its contents. A signature log resolves illegibility; it does not replace a missing signature or establish missing ordering intent.

Medicare Program Integrity Manual — Chapter 3 · Medical Record Maintenance & Access Requirements — CMS, January 2026

6.How should auditors assess templated documentation?

Templates can organize documentation, but their presence does not prove that the recorded work occurred or supports payment. Review the patient-specific information, internal consistency, and connection to the billed service. Default statements that conflict with the assessment deserve investigation. A template should support an accurate clinical account rather than replace one. The discriminating cue is meaningful, consistent content about this encounter, not the number of completed fields.

Apply it

A template states that every system was normal, while the assessment describes an active respiratory complaint. Compare the narrative and examination details, seek clarification when material, and avoid awarding support solely because every template field is populated.

Common pitfall: Do not automatically reject template-based notes or automatically credit checked boxes. Either shortcut substitutes document appearance for evaluation of reliable, service-specific evidence and consistency.

Medicare Program Integrity Manual — Chapter 3

7.Why does copied text require encounter-specific verification?

Copied text may accurately carry forward relevant history, but it can also preserve resolved conditions, outdated findings, or work not performed at the current encounter. Audit its relevance and consistency with current decision making. Repeated wording is a signal for review rather than proof of misconduct. The key distinction is whether the responsible practitioner has created a reliable account of the present service, including changes that affect coding or necessity.

Apply it

Three consecutive notes repeat a condition that the latest assessment calls resolved. Check whether the condition was actually assessed or affected current care before counting it as an active problem or using it to justify services.

Common pitfall: Identical wording alone does not prove false documentation. Equally, a signed copied paragraph does not establish that its contents remain accurate for today's encounter.

Medicare Program Integrity Manual — Chapter 3

8.How does HIPAA minimum necessary apply to audit access?

For uses and disclosures subject to HIPAA's minimum-necessary standard, a covered entity makes reasonable efforts to limit protected health information to what is needed for the purpose. An internal payment or operations audit therefore needs an access rationale tied to its objectives. Minimum necessary is not a fixed page limit. A full chart may be justified for some reviews, but routine unrestricted access without a purpose-based assessment is different.

Apply it

An auditor reviewing duplicate laboratory billing requests billing records, orders, and relevant encounter notes. If unrelated historical records become necessary, the auditor explains the expanded need rather than routinely exporting every patient's complete chart at the outset.

Common pitfall: Minimum necessary does not always mean the smallest possible record extract. Insufficient information can undermine review; the standard requires reasonable, purpose-related limits on access.

Minimum Necessary Requirement — HHS

9.Which treatment disclosures are outside minimum necessary?

HIPAA's minimum-necessary requirement does not apply to disclosures to, or requests by, a health care provider for treatment. This exception is tied to purpose, not simply to the recipient's professional title. A clinician conducting a payment audit is not automatically acting for treatment. Determine why information is being requested before applying the exception, and keep the separate requirements governing permissible use, disclosure, and safeguards in view.

Apply it

A specialist requests records to treat a referred patient, while a physician auditor requests records to evaluate billing accuracy. Classify each request by its actual purpose; the provider-to-provider treatment exception does not automatically extend to the audit.

Common pitfall: A medical license does not make every information request a treatment request. Also, an exception to minimum necessary does not eliminate other applicable privacy obligations.

Minimum Necessary Requirement — HHS

10.How should record production preserve evidentiary integrity?

A record-production process should deliver the relevant maintained documentation in a form that preserves identity, dates, authorship, and completeness. Auditors need to distinguish a missing record from a record that exists but was omitted from the response. Track requests, received materials, and unresolved gaps. Applicable Medicare maintenance and access obligations also matter; a practice cannot assume that another organization holding a document eliminates its own responsibility to provide required support.

Apply it

A response includes an encounter note but omits the referenced diagnostic report. Log the missing report, request it from the responsible source, and record whether the final finding reflects absent documentation or documentation received after the initial response.

Common pitfall: Treating the first document bundle as the entire medical record can create false findings. Uncontrolled additions, however, can obscure what was available at each review stage.

Medical Record Maintenance & Access Requirements — CMS, January 2026 · Medicare Program Integrity Manual — Chapter 3

Coding and Documentation Compliancenot stated

11.What knowledge standard matters under the civil False Claims Act?

The civil False Claims Act reaches knowing false claims, with knowledge encompassing actual knowledge, deliberate ignorance, and reckless disregard. Specific intent to defraud is not required. This makes ignored warnings and unsupported billing practices important audit evidence. A coding discrepancy alone does not establish the legal elements. Document the claim issue, the applicable requirement, and evidence about what responsible parties knew or disregarded before characterizing the compliance concern.

Apply it

A manager receives repeated, substantiated warnings that a service is not performed but directs staff to continue billing it. Preserve the warnings and billing instructions, validate the affected claims, and escalate the knowledge evidence with the underlying claim findings.

Common pitfall: Do not equate every mistake with fraud or assume that lack of an explicit confession removes FCA risk. Deliberate ignorance and reckless disregard also matter.

Fraud & Abuse Laws — HHS Office of Inspector General

12.How should an auditor distinguish error from suspected misconduct?

An audit establishes evidence about documentation, coding, and payment support; a legal conclusion requires analysis of the relevant law's elements. An isolated misapplied rule may indicate training needs, while concealment or continuation after clear warnings may warrant deeper investigation. Preserve facts without overstating intent. The strongest finding separates the observed billing error, its financial effect, its recurrence, and any evidence suggesting knowing conduct rather than blending these into an unsupported accusation.

Apply it

A new coder misapplies a modifier, receives instruction, and corrects the affected claims. Another team is instructed to hide the same error. Document each billing defect consistently while separately escalating the concealment evidence through the compliance process.

Common pitfall: A high error rate can justify investigation without proving intent. Conversely, calling a practice a training issue does not resolve evidence of knowing misconduct.

Fraud & Abuse Laws — HHS Office of Inspector General · HHS-OIG General Compliance Program Guidance — November 2023

13.What makes remuneration relevant to the Anti-Kickback Statute?

The federal Anti-Kickback Statute addresses knowing and willful remuneration intended to induce or reward referrals or business involving federally payable items or services. Remuneration includes things of value beyond cash, such as free rent or excessive consulting compensation. Both offering and receiving parties can be implicated. The audit distinction is between a genuine business arrangement and value linked to referral generation; medically necessary services do not by themselves eliminate kickback concerns.

Apply it

A supplier offers a physician free office space in exchange for directing federally insured patients to that supplier. Identify the economic benefit and referral condition, preserve the agreement, and refer the arrangement for compliance and legal evaluation.

Common pitfall: Do not dismiss a benefit because no cash changed hands. Also, actual delivery of a medically necessary item does not neutralize an improper referral payment.

Fraud & Abuse Laws — HHS Office of Inspector General

14.How should an auditor interpret an AKS safe harbor?

An Anti-Kickback Statute safe harbor protects a qualifying arrangement when all applicable conditions are satisfied. A label such as rental agreement or consulting contract is insufficient. Compare the arrangement's actual terms and operation with every relevant condition. Failure to fit a safe harbor does not, by itself, establish a violation; it means automatic safe-harbor protection has not been demonstrated and the arrangement needs evaluation under the statute's elements.

Apply it

A referral source receives consulting payments under a written agreement, and management asserts safe-harbor protection. Request evidence supporting each claimed condition and actual services performed rather than treating the contract's title as conclusive protection for the arrangement.

Common pitfall: Avoid both extremes: partial compliance does not establish safe-harbor protection, and lack of safe-harbor protection alone does not prove a knowing and willful kickback.

Fraud & Abuse Laws — HHS Office of Inspector General

15.Which relationships trigger physician self-referral analysis?

Stark analysis examines a physician's referral for designated health services, the relevant financial relationship with the receiving entity, and whether an exception applies. Financial relationships can involve ownership, investment, or compensation, including relationships involving immediate family members. Clinical laboratory and certain imaging services are examples of designated health services. Because Stark is a strict-liability framework, the absence of an intent to violate the law does not substitute for satisfying an applicable exception.

Apply it

A physician refers Medicare patients to an imaging entity partly owned by the physician's immediate family member. Map the referral, service category, and financial relationship, then determine whether the arrangement meets an applicable exception before concluding that billing is permissible.

Common pitfall: A clinically appropriate referral can still raise self-referral restrictions. Do not limit financial-relationship review to direct ownership or require proof of improper intent first.

Fraud & Abuse Laws — HHS Office of Inspector General

16.How do Stark and the Anti-Kickback Statute differ?

Stark focuses on specified referrals for designated health services involving financial relationships unless an exception applies. The Anti-Kickback Statute focuses on knowing and willful remuneration to induce or reward federally reimbursable referrals or business. Their elements differ, so satisfying an exception under one framework does not automatically resolve the other. Review the same arrangement through each applicable legal lens rather than treating all referral-related laws as interchangeable billing restrictions.

Apply it

An imaging arrangement includes physician ownership and payments tied to referrals. Analyze the ownership and designated-service referral under Stark, and separately assess whether remuneration was knowingly and willfully used to induce federally payable business under the AKS.

Common pitfall: Do not import Stark's strict-liability structure into AKS analysis or assume an AKS safe harbor establishes a Stark exception. Each framework has distinct requirements.

Fraud & Abuse Laws — HHS Office of Inspector General

17.Why must exclusion screening extend beyond billing clinicians?

OIG exclusion affects federal health care program payment for items or services furnished, ordered, or prescribed by excluded individuals or entities. Risk can arise through employees and contractors whose work contributes to reimbursed services, not only practitioners submitting claims. Screening should therefore reflect the organization's workforce and contractual relationships. A possible database match requires identity verification; a name similarity alone is not a defensible conclusion that a particular worker is excluded.

Apply it

A practice screens physicians but overlooks a contracted service contributor. Expand the review to relevant contractors, compare identifiers for potential matches, and assess whether any verified exclusion affected federally reimbursed items or services furnished through the practice.

Common pitfall: Checking only people with billing identifiers can miss indirect exposure. Conversely, immediately treating a common-name match as confirmed exclusion risks an inaccurate and harmful finding.

Fraud & Abuse Laws — HHS Office of Inspector General

18.How can indirect billing create exclusion-related exposure?

Routing a service through an employer or group does not erase the effect of an individual's OIG exclusion. Federal programs generally will not pay for items or services furnished, ordered, or prescribed by excluded persons within the exclusion's reach. Audit the actual service contribution and applicable dates rather than looking only at the name on the claim. The payment pathway and the underlying excluded contribution are separate parts of the analysis.

Apply it

A verified excluded practitioner performs services that the group submits under its organizational billing process. Trace the practitioner's contribution and service dates, identify affected federal program claims, and escalate the payment implications even though the individual's name is absent.

Common pitfall: An organization's valid enrollment does not automatically make every service payable. Changing the billing name cannot cure an excluded person's otherwise prohibited contribution to services.

Fraud & Abuse Laws — HHS Office of Inspector General

19.When do copayment waivers raise compliance concerns?

Routine advertised waivers of required copayments can raise federal Anti-Kickback Statute and beneficiary-inducement concerns because the financial benefit may influence service selection. OIG distinguishes such practices from an individual determination of financial need or unsuccessful reasonable collection efforts. Audit the waiver process, supporting facts, and marketing rather than assuming every unpaid balance is equivalent. A policy's existence is less informative than how consistently its eligibility criteria are actually applied.

Apply it

A clinic advertises that Medicare patients never pay copayments, while another documents individual financial assessments before occasional waivers. Examine the advertising and waiver records separately; the individualized process provides materially different evidence from a universal promotional promise.

Common pitfall: Do not classify every hardship waiver as a kickback or treat a blanket marketing promise as justified merely because some patients have financial difficulty.

Fraud & Abuse Laws — HHS Office of Inspector General

20.What does voluntary OIG compliance guidance establish?

OIG's General Compliance Program Guidance is voluntary guidance describing a compliance-program framework and related federal risk areas. It helps organizations structure oversight, education, communication, auditing, and response. Its recommendations should not be represented as a standalone mandatory regulation. Distinguish an applicable legal obligation from a recommended control: an organization may choose an effective alternative control, but it cannot disregard a binding billing or legal requirement simply because the guidance is voluntary.

Apply it

An audit identifies weak escalation procedures. Explain how a defined reporting channel would address the risk and cite OIG's guidance as a recommended framework, while separately identifying any actual legal or contractual requirement implicated by the underlying conduct.

Common pitfall: Calling every recommended practice legally mandatory overstates the source. Calling the guidance voluntary does not make the laws and payment requirements discussed within it optional.

General Compliance Program Guidance — HHS OIG · HHS-OIG General Compliance Program Guidance — November 2023

Coding and Reimbursement Conceptsnot stated

21.How should an auditor select date-specific coding rules?

Coding review must use the code set, guidelines, and payment policies applicable to the service and setting being audited. Publication of a newer reference does not automatically change an earlier claim's governing rules. For example, FY 2027 ICD-10-CM applies from October 1, 2026, through September 30, 2027. Record the applicable version in the workpaper so another reviewer can reproduce the decision and distinguish a historical coding error from a later rule change.

Apply it

An outpatient encounter occurred in September 2026, but the audit begins in November. Use the ICD-10-CM version applicable to the September service rather than applying a code change that first became effective on October 1.

Common pitfall: The audit date does not select the coding version. Also, a coding-reference effective date does not establish when the CPMA examination blueprint changed or applied.

ICD-10-CM Official Guidelines for Coding and Reporting — FY 2027

22.What does an NCCI procedure-to-procedure edit test?

An NCCI procedure-to-procedure edit identifies code combinations that generally should not be separately reported together under the applicable Medicare edit framework. Review the actual services, code-pair relationship, effective dates, and modifier indicator. The edit is not simply a prohibition on every pair of services performed the same day. Separate reporting depends on whether the coding rules permit it and whether the documented circumstances satisfy any recognized exception.

Apply it

Two procedures on one date trigger an edit. Before deleting a code or adding a modifier, compare the operative details with the code pair, applicable edit date, modifier indicator, and documented circumstances supporting any distinct service.

Common pitfall: Different code descriptions do not guarantee separate payment. Conversely, an edit does not authorize automatic modifier use merely because both procedures appear in the note.

Medicare NCCI Policy Manual 2026 — Chapter I

23.How do NCCI modifier indicators affect review?

For Medicare NCCI procedure-to-procedure edits, modifier indicator 0 means an NCCI-associated modifier cannot bypass the edit. Indicator 1 means an appropriate modifier may bypass it when the documented circumstances justify separate reporting. Indicator 1 is permission to evaluate an exception, not proof that an exception exists. The auditor must still establish that services are distinct under applicable rules and that the selected modifier accurately describes the circumstances.

Apply it

A code pair has modifier indicator 1, but the note describes work integral to a single procedure. Do not approve a distinct-service modifier solely because the indicator permits one; the record must support the substantive exception.

Common pitfall: Indicator 1 is not a recommendation to append a modifier. Indicator 0 cannot be overcome simply by choosing a more specific distinct-service modifier instead.

Medicare NCCI Policy Manual 2026 — Chapter I

24.When is modifier 59 appropriate?

Modifier 59 identifies a distinct procedural service when the documented circumstances meet the relevant coding requirements and a more descriptive modifier is not appropriate. Distinctness may involve a separate encounter, site, or other qualifying circumstance. It should not be appended merely to obtain payment or because diagnoses differ. Evaluate the relationship between the procedures and the applicable edit; the modifier communicates a supported exception rather than creating one.

Apply it

A billing team adds modifier 59 to every denied code pair. Audit the underlying records for qualifying distinct circumstances, remove unsupported automatic applications, and choose a more descriptive available modifier when the facts and payer requirements support it.

Common pitfall: Two diagnoses do not by themselves establish distinct procedures. A modifier changes claim information; it cannot transform integral procedural work into a separately reportable service.

Proper Use of Modifiers 59, XE, XS, XP & XU — CMS

25.Which circumstances distinguish XE, XP, XS, and XU?

The X modifiers communicate specific distinct-service circumstances: XE identifies a separate encounter, XP a separate practitioner, XS a separate structure, and XU an unusual non-overlapping service. Select the modifier matching the documented reason for distinctness, subject to the applicable payer and edit rules. A different practitioner or structure does not automatically make every code pair separately reportable. The substantive coding exception must exist before its most accurate modifier can be selected.

Apply it

A Medicare code pair permits a modifier, and the record establishes a qualifying separate encounter later that day. XE directly communicates the documented distinction; another X modifier would describe a different circumstance despite also indicating separation.

Common pitfall: Do not choose an X modifier by habit or treat it as stronger than modifier 59. Specific wording improves accuracy only when the underlying exception is valid.

Proper Use of Modifiers 59, XE, XS, XP & XU — CMS

26.How are documented quantities converted to billed units?

Billed units follow the applicable code descriptor and reporting rules, which may differ from the number of packages, procedures, or physical items recorded. Start with the documented quantity, identify what one code unit represents, and perform the conversion. Then check any relevant limits or special reporting instructions. A mathematically correct conversion still needs evidence that the quantity was provided and that the service satisfies coverage and payment requirements.

Apply it

A fictional supply code represents ten items per unit, and the record supports thirty items furnished. The basic conversion is three units. Check applicable reporting instructions before comparing those units with the submitted claim and any edits.

Common pitfall: Do not equate one package with one billed unit unless the descriptor supports that relationship. Correct arithmetic cannot establish an undocumented quantity or medical necessity.

Medicare NCCI Policy Manual 2026 — Chapter I

27.How do MUE adjudication indicators determine the treatment of excess units?

A Medicare medically unlikely edit evaluates units for a code. MUE adjudication indicator (MAI) 1 applies the edit separately to each claim line; separate lines are permissible only when correct reporting and appropriate modifiers support them. MAI 2 is an absolute date-of-service limit. MAI 3 is a date-of-service clinical benchmark that may be exceeded when review establishes that the units were actually provided, correctly coded, and medically necessary. MAI 2 and MAI 3 aggregate units across lines for the same code and date; splitting lines does not avoid those edits.

Apply it

Assume a fictional code has an MUE of two units and four units were documented. With MAI 1, two lines of two units may satisfy the line edit only if separate reporting and modifiers are appropriate. With MAI 2, all four units are aggregated and exceed the absolute limit. With MAI 3, the same aggregate exceeds the benchmark, but review may support payment if actual provision, correct coding, and necessity are established.

Common pitfall: MAI 1 does not authorize artificial line splitting, and MAI 3 does not guarantee payment above the benchmark. Units below an MUE still require documentation and payment support.

Medicare NCCI Policy Manual 2026 — Chapter I

28.When can modifier 25 support same-day E/M reporting?

Modifier 25 identifies a significant, separately identifiable E/M service by the same practitioner on the day of a procedure or other service when applicable rules permit separate reporting. Routine evaluation associated with the procedure is insufficient. A different diagnosis is not required, and a different diagnosis alone does not establish separate work. Look for documented assessment and management beyond the work ordinarily included in the procedure being reported.

Apply it

During a scheduled minor procedure visit, the practitioner separately evaluates and manages a new, substantive complaint. Determine whether that documented work exceeds the procedure's usual evaluation before supporting a separate E/M service with modifier 25.

Common pitfall: Every procedure involves some evaluation. Do not count that routine work twice or require a different diagnosis when the documentation otherwise establishes a separate E/M service.

Medicare NCCI Policy Manual 2026 — Chapter I

29.How does a major-surgery decision differ from routine perioperative care?

Medicare identifies major surgery by the 090 global indicator. An E/M service resulting in the initial decision for that surgery on the day before or day of surgery supports modifier 57 on the E/M service. Routine preoperative care within that global period after an earlier decision is included in the surgical package. Procedures with 000 or 010 global indicators are minor procedures; their immediate procedural decision does not qualify for modifier 57. A separate same-day E/M service for a minor procedure instead requires significant, separately identifiable work supporting modifier 25.

Apply it

A practitioner first decides on Monday that a patient needs a procedure with global indicator 090, performed Tuesday. The Monday E/M service supports modifier 57. If the decision was made the previous week and Monday is only a routine preoperative check, modifier 57 is unsupported. Changing the procedure to global indicator 010 also removes the major-surgery basis for modifier 57.

Common pitfall: Neither the procedure's perceived complexity nor its location establishes Medicare major-surgery status. Verify the global indicator, initial decision, and qualifying date rather than treating every preoperative visit as separately payable.

mln907166-global-surgery-booklet.pdf · Medicare NCCI Policy Manual 2026 — Chapter I

30.Why must coding accuracy and payment eligibility be evaluated separately?

A correctly selected code describes a service but does not establish all conditions for payment. Coverage, medical necessity, documentation, bundling, units, and other applicable requirements can independently affect reimbursement. Likewise, claim payment does not prove coding compliance because processing systems may not evaluate every supporting fact. A defensible audit identifies which requirement failed rather than using a denial, payment, or accurate code descriptor as a complete answer.

Apply it

A laboratory code accurately describes the test performed, but the records do not establish why it was ordered. Keep code selection separate from the medical-necessity finding and obtain relevant existing clinical support before finalizing the payment assessment.

Common pitfall: An accepted claim is not an audit approval. A technically correct code can still represent a service that lacks required documentation or payment support.

Medicare NCCI Policy Manual 2026 — Chapter I · Complying With Documentation Requirements for Lab Services — CMS, May 2026

Audit Scope and Statistical Sampling Methodsnot stated

31.How should an audit objective define scope?

An audit objective states the question the review will answer, and scope defines the population, period, services, providers, and payment context to which that answer applies. These choices determine what evidence and sampling approach are appropriate. A review of modifier use by one practitioner is different from an estimate of organization-wide overpayments. Define exclusions explicitly so readers can understand the conclusion's boundaries and avoid extending findings beyond the reviewed universe.

Apply it

Leadership asks whether one clinic correctly reports a distinct-service modifier. Define the clinic, service period, payer, relevant codes, and modifier-bearing claims before selection, and state whether the review is diagnostic or intended to estimate broader financial exposure.

Common pitfall: A broad title such as billing audit cannot substitute for operational scope. An undefined universe makes sample selection, reproducibility, and interpretation of results unreliable.

Medicare Program Integrity Manual — Chapter 8

32.What makes a sampling frame fit its population?

The sampling frame is the operational list from which units are selected. It should accurately represent the defined population, with understood exclusions, duplicates, and data limitations. A population of paid claims cannot be sampled reliably from a file that silently omits an entire provider. Reconcile frame counts and amounts with source data before selection. Frame defects create coverage problems that a random selection method cannot repair after the fact.

Apply it

An intended all-provider claims file contains no records from a recently acquired clinic. Reconcile the provider roster and claim totals, correct the frame if the clinic belongs in scope, and document any justified exclusion before drawing the sample.

Common pitfall: Random numbers do not cure an incomplete list. A precisely selected sample can still misrepresent the intended population when eligible units never enter the frame.

Medicare Program Integrity Manual — Chapter 8

33.Why must the sampling unit match the audit question?

A sampling unit may be a claim, claim line, encounter, beneficiary, or another defined element. Its definition controls selection probabilities, review workload, and the meaning of the resulting error rate. Selecting beneficiaries and reviewing all their claims produces a different design from independently selecting claim lines. Define how related records are handled and keep analysis aligned with the selected unit. Otherwise, a reported percentage may use a denominator unrelated to the design.

Apply it

A project selects encounters and reviews every line within each encounter. Report encounter-level error frequency separately from line-level errors, and avoid treating all reviewed lines as independently sampled observations without an analysis that accounts for the design.

Common pitfall: Do not switch casually between patients, claims, and lines. The same records can yield different valid measures, but each measure needs its own defined denominator.

Medicare Program Integrity Manual — Chapter 8

34.When is targeted sampling useful?

Targeted sampling deliberately selects records with characteristics associated with suspected risk, such as high payments or unusual modifier combinations. It is useful for investigating mechanisms, validating alerts, and directing education. Its findings describe the selected records and may guide further review. Because selection is purposefully concentrated rather than probability-based, the observed error rate should not automatically be treated as the population's error rate or multiplied across the entire universe.

Apply it

An auditor reviews the twenty highest-paid claims after a billing alert and finds eight errors. Use those cases to understand the problem and plan next steps, while explicitly stating that the selected group does not estimate overall prevalence.

Common pitfall: A high targeted-sample error rate may reflect the selection strategy. It supports concern and investigation without automatically supporting a statistically valid population-wide overpayment estimate.

Medicare Program Integrity Manual — Chapter 8

35.What distinguishes probability sampling from convenient selection?

Probability sampling uses a defined random selection process in which population units have known selection probabilities appropriate to the design. This supports statistical inference when the frame, review, and estimation methods are also sound. Choosing the easiest charts to obtain is not equivalent, even if selection feels impartial. Preserve the frame, selection procedure, and selected units so the process can be reproduced and evaluated rather than relying on an unsupported claim of randomness.

Apply it

A practice proposes using the first available charts from each office. If the objective requires statistical estimation, establish an appropriate probability design and reproducible selection process instead of treating chart availability as a random mechanism for selection.

Common pitfall: Casual selection is not made statistical by using the word random. Known selection probabilities and a documented design matter more than the selector's good intentions.

Medicare Program Integrity Manual — Chapter 8

36.How can stratification improve an audit sample?

Stratification divides a population into defined, non-overlapping groups before probability selection within those groups. It can improve precision or ensure attention to categories with different payment or risk characteristics. Analysis must preserve the design, including differing selection probabilities and population sizes. A simple average of stratum error rates is not necessarily the overall rate. The value of stratification comes from purposeful grouping and correct estimation, not merely creating more categories.

Apply it

An audit separates high-payment and lower-payment claims and samples each at different rates. Retain each stratum's population size and selection information so the analyst can combine results appropriately instead of averaging the two observed error percentages equally.

Common pitfall: Oversampling a high-risk stratum can be useful, but ignoring its sampling weight can exaggerate overall prevalence. Stratification requires corresponding analysis rather than just separate spreadsheets.

Medicare Program Integrity Manual — Chapter 8

37.How is a claim-level error rate calculated?

A claim-level error rate divides claims meeting the predefined error criterion by claims reviewed under that measure. A claim with several erroneous lines generally counts once in an any-error claim rate. Define whether undercoding, overcoding, and nonfinancial deficiencies qualify before calculation. The arithmetic is simple, but interpretation depends on the denominator and selection design. Report the measure's definition so it cannot be confused with line-level frequency or a dollar-based error measure.

Apply it

Of forty reviewed claims, ten contain at least one defined error, including two with multiple erroneous lines. The any-error claim rate is ten divided by forty, or 25%; multiple defects do not increase the claim numerator.

Common pitfall: Adding every defect and dividing by claims can exceed the intended claim-level measure. Count the defined unit consistently and label separate defect-frequency measures accurately.

Medicare Program Integrity Manual — Chapter 8

38.How does a dollar error measure differ from error frequency?

Error frequency measures how often units contain defined errors; a dollar measure describes financial effect relative to a stated amount. They answer different questions. Many small errors can produce high frequency with limited dollar exposure, while one large error can dominate financial impact. Specify whether the denominator is paid, allowed, or another defined amount, and distinguish gross overpayments from any separately assessed underpayments. Neither measure should be mislabeled as the other.

Apply it

A sample contains $10,000 in paid amounts and $2,000 in supported overpayments across five of fifty claims. Report a 10% claim error rate and a 20% overpayment-to-paid ratio, with both definitions and sampling limitations clearly stated.

Common pitfall: A 20% dollar ratio does not mean 20% of claims were wrong. Also, billed charges and paid amounts are not interchangeable financial denominators.

Medicare Program Integrity Manual — Chapter 8

39.What limits extrapolation from sampled overpayments?

Population overpayment estimation requires an appropriate sampling design, reliable frame, consistent claim determinations, and an estimation method matched to that design. Uncertainty must be described rather than hidden behind a single precise-looking total. A targeted review does not become a probability sample because its average is multiplied by population size. Medicare contractor extrapolation also operates within specific program requirements, which should not be assumed identical to an organization's internal exploratory audit.

Apply it

A manager wants to multiply the error amount from selected high-risk claims across all claims. Explain the selection limitation, report the verified sample amount, and design a suitable probability-based follow-up if a defensible population estimate is needed.

Common pitfall: Large sample size alone does not repair biased selection or incorrect determinations. Statistical terminology cannot turn an unsupported multiplication into a defensible overpayment estimate.

Medicare Program Integrity Manual — Chapter 8

40.What can RAT-STATS contribute to an audit?

RAT-STATS is OIG's statistical software resource relevant to audit sampling and estimation. Software can support calculations and documented selection processes, but it does not define the audit objective, validate the population, or decide whether a claim is erroneous. Users must choose methods appropriate to the design and interpret outputs correctly. A recognizable software name is evidence of a tool used, not independent proof that every methodological decision was valid.

Apply it

An analyst produces a RAT-STATS output for a claims review. Before relying on the result, verify the population file, sampling unit, selected method, inputs, and claim determinations, and retain enough documentation to reproduce and assess the analysis.

Common pitfall: Do not present software output as automatic validation of a sample. Accurate computation can still produce a misleading result when design assumptions or input data are wrong.

RAT-STATS — Statistical Software — HHS OIG · Medicare Program Integrity Manual — Chapter 8

Medical Record Audit Abstractionnot stated

41.How should an auditor build a reproducible abstraction?

Abstraction converts the record into a structured account of facts relevant to the audit question. Capture the service, dates, practitioner, diagnoses, procedures, quantities, and supporting locations as needed, while separating recorded facts from reviewer interpretation. A defensible workpaper lets another reviewer follow the path from source entry to coding conclusion. Do not import facts from a claim into the clinical record merely because the claim already reports them.

Apply it

A claim lists a diagnosis absent from the assessment. Record what the note actually states, identify the claim discrepancy, and cite the relevant record location so another reviewer can verify the finding without reconstructing the entire encounter independently.

Common pitfall: Copying claim fields into an abstraction can make unsupported coding appear documented. The claim is an object of review, not automatic proof of its own accuracy.

Medicare Program Integrity Manual — Chapter 3 · ICD-10-CM Official Guidelines for Coding and Reporting — FY 2027

42.How are uncertain outpatient diagnoses abstracted?

Under ICD-10-CM outpatient guidelines, diagnoses described as probable, suspected, questionable, rule out, or similar uncertainty are not coded as established conditions. Report the highest degree of certainty for that encounter, such as documented symptoms, signs, abnormal findings, or another reason for the visit. The setting is decisive: do not import inpatient discharge rules into an outpatient office review. Later confirmation also does not automatically establish what was known during the earlier encounter.

Apply it

An office assessment states possible pneumonia, with cough documented and imaging pending. Abstract the supported symptom or other established finding for that encounter rather than treating the possible diagnosis as confirmed solely because treatment was considered.

Common pitfall: A clinician's suspicion can justify evaluation without establishing a reportable confirmed outpatient diagnosis. Do not convert diagnostic testing intent into proof of the suspected disease.

ICD-10-CM Official Guidelines for Coding and Reporting — FY 2027

43.Which condition belongs first in an outpatient diagnosis sequence?

The outpatient first-listed diagnosis is generally the diagnosis, condition, problem, or other reason chiefly responsible for the services provided, subject to applicable coding conventions and specific guidelines. It is not automatically the most severe condition in the patient's history. Identify the encounter's purpose and documented assessment, then check sequencing instructions. When no definitive diagnosis is established, a supported symptom or other encounter reason may appropriately lead the sequence.

Apply it

A patient with several stable historical diagnoses attends for evaluation of new dizziness, and no cause is established. Determine the first-listed diagnosis from the documented reason for today's services and applicable guidelines rather than selecting the most serious historical disease.

Common pitfall: Do not rank diagnoses solely by perceived seriousness or reimbursement effect. Encounter purpose and coding instructions govern sequencing, with specific guidelines overriding a generic rule.

ICD-10-CM Official Guidelines for Coding and Reporting — FY 2027

44.How do active chronic conditions differ from historical conditions?

An outpatient abstraction should distinguish conditions that coexist and require or affect care from conditions that no longer exist. Chronic diseases receiving ongoing treatment may remain reportable across encounters when supported. A condition's appearance in a carried-forward problem list is insufficient by itself to establish current relevance. History codes may be appropriate when a past condition affects current care, subject to applicable instructions. Look for present clinical status and connection to management.

Apply it

A note addresses ongoing treatment of a chronic disorder but lists a remote, resolved illness only in history. Abstract the active disorder as supported; evaluate whether the past illness affects this encounter before considering an appropriate history code.

Common pitfall: Do not code every problem-list entry as an active disease. Also, stable does not necessarily mean resolved when a chronic condition remains under ongoing management.

ICD-10-CM Official Guidelines for Coding and Reporting — FY 2027

45.When should symptoms be reported with a confirmed diagnosis?

Symptoms routinely associated with an established diagnosis generally are not separately reported unless classification instructions direct otherwise. Symptoms that are not routinely associated may be reportable when supported, subject to applicable guidelines. The auditor must first establish whether the diagnosis is confirmed and whether the symptom is integral to it. This avoids both unnecessary symptom duplication and inappropriate deletion of a distinct complaint that remains independently relevant to the encounter.

Apply it

A record contains a confirmed diagnosis and several symptoms. Check which symptoms are routinely associated and whether any has independent significance under the coding guidelines before retaining every symptom code or deleting all of them as redundant.

Common pitfall: Do not use a blanket rule that symptoms are always omitted once any diagnosis appears. The relationship to the established condition and classification instructions matter.

ICD-10-CM Official Guidelines for Coding and Reporting — FY 2027

46.How can abstraction isolate separately identifiable E/M work?

For a same-day procedure and E/M review, abstract the procedure-related work and the additional assessment and management separately. Identify what the practitioner evaluated, what decisions were made, and which work exceeds the usual service components. A separate note can make review easier but does not itself prove distinctness. Conversely, one combined note may contain adequate support. The content and service relationship determine whether separate reporting is defensible under applicable rules.

Apply it

One note contains a minor procedure and management of an unrelated active problem. Create a workpaper identifying the additional assessment and plan, then compare that work with the procedure's included evaluation before deciding whether modifier 25 is supported.

Common pitfall: Two note titles do not establish two payable services. A combined note is not automatically deficient when its content clearly distinguishes the additional E/M work.

Medicare NCCI Policy Manual 2026 — Chapter I · Medicare Program Integrity Manual — Chapter 3

47.How should an office/outpatient E/M level be audited?

For office/outpatient E/M services allowing either pathway, evaluate the documented MDM or the physician's or qualified practitioner's total qualifying time on the service date. MDM requires the applicable level in at least two of three elements: problems addressed, data reviewed and analyzed, and management risk. Time selection requires the full applicable threshold and excludes staff time and time for separately reported services. Medically appropriate history and examination support the encounter but do not determine its level; documentation volume cannot substitute for MDM or qualifying time.

Apply it

An established-patient office claim reports 99214 using time. The practitioner documents 38 total minutes, expressly including 12 minutes performing a separately reported procedure. The remaining 26 minutes are qualifying, medically necessary E/M work on that date. With 99213 requiring at least 20 minutes and 99214 at least 30 minutes, time supports 99213. If the record also supports only low MDM, neither pathway supports 99214, regardless of note length. Evaluate modifier 25 separately.

Common pitfall: Do not count procedure time twice, add staff minutes to practitioner time, or round up to an unmet threshold. A time shortfall does not automatically require downcoding if the documented MDM independently supports the reported level.

Evaluation & Management Services | CMS · mln006764-evaluation-management-services.pdf

48.What establishes laboratory ordering intent?

Medicare laboratory documentation review looks for evidence that the treating practitioner intended the specific test to be performed. An unsigned requisition is not automatically fatal when an authenticated medical record establishes the practitioner's ordering intent and the other requirements are met. Distinguish that situation from a record containing only a test result. A result shows that testing occurred; it does not independently establish who ordered it or why it was needed.

Apply it

A laboratory requisition lacks a signature, but an authenticated encounter note explicitly orders the named test. Link the documents and assess the remaining requirements rather than denying solely for the requisition signature or accepting the result as sufficient evidence.

Common pitfall: A test result is not an order. An unsigned requisition also does not automatically establish noncompliance when qualifying authenticated documentation demonstrates the treating practitioner's intent.

Complying With Documentation Requirements for Lab Services — CMS, May 2026

49.How is laboratory medical necessity distinguished from test performance?

Laboratory medical necessity requires clinical support for why the ordered test was reasonable and necessary under applicable Medicare requirements. The fact that a laboratory performed a test and generated a result does not establish that support. Review the treating practitioner's documentation, relevant diagnoses or findings, and any applicable coverage criteria. A diagnosis appearing only on the claim should be traced to supporting records rather than accepted as a self-validating justification for payment.

Apply it

A claim carries a diagnosis supporting coverage, but the supplied office record contains no related assessment or test rationale. Request the relevant existing clinical documentation and validate the diagnosis linkage before concluding that medical necessity is established.

Common pitfall: Do not infer necessity from a completed test or normal versus abnormal result. The clinical rationale and applicable coverage requirements govern the payment-support analysis.

Complying With Documentation Requirements for Lab Services — CMS, May 2026

50.Why must laboratory records be linked across organizations?

A laboratory claim may depend on records held by both the laboratory and the ordering practitioner. The laboratory may possess requisitions and results while the practitioner's record contains ordering intent and clinical necessity. A complete abstraction links these sources by patient, date, and test. Record-sharing arrangements should support timely access to necessary evidence. The absence of clinical detail in the laboratory's initial packet does not establish that the practitioner never documented it.

Apply it

A laboratory submits a requisition and result, while the ordering clinic retains the relevant assessment. Obtain and link the clinic documentation to the exact test and service date before finalizing whether the claim has adequate order and necessity support.

Common pitfall: Do not stop at organizational boundaries or assume all records will be in one chart. Equally, unrelated clinical notes cannot support a test merely by proximity.

Complying With Documentation Requirements for Lab Services — CMS, May 2026

Category Risk Analysis and Communicationnot stated

51.What makes an audit finding defensible?

A defensible finding connects the applicable criterion, observed condition, supporting evidence, and resulting effect or risk. The criterion explains what should have occurred; the condition explains what actually occurred. Keep confirmed facts separate from hypotheses about cause. A useful recommendation addresses the demonstrated gap and can be evaluated later. This structure lets a reader assess the conclusion without relying solely on the auditor's authority or an unexplained error label.

Apply it

Instead of reporting incorrect modifiers, identify the applicable distinct-service rule, the unsupported circumstances in the reviewed notes, the affected claims, and the payment consequence established by the review. Link the recommendation to the demonstrated documentation or workflow gap.

Common pitfall: A conclusion without an applicable criterion is difficult to defend. A recommendation without a demonstrated cause may sound useful while leaving the actual problem untouched.

HHS-OIG General Compliance Program Guidance — November 2023

52.How should disputed findings be validated?

Validation checks whether the correct rule, relevant records, and consistent reasoning support a proposed finding. A provider response may identify overlooked evidence or a misapplied requirement, but disagreement alone does not invalidate the finding. Use a defined reconsideration process, preserve the original rationale, and document why a conclusion changes or remains. Independent review is especially useful for material or ambiguous issues, helping separate legitimate uncertainty from inconsistent reviewer application.

Apply it

A practitioner disputes an unsupported-order finding and supplies an existing authenticated note containing the order. Verify the note's relevance and integrity, revise the determination if justified, and document the reason rather than defending the original finding automatically.

Common pitfall: Do not treat every challenge as resistance or accept every challenge as a correction. Findings should change because evidence or rule application changes, with documented reasoning.

HHS-OIG General Compliance Program Guidance — November 2023 · Medicare Program Integrity Manual — Chapter 3

53.Which factors determine audit-risk priority?

Risk prioritization considers the likelihood and consequences of a compliance problem, informed by organizational services, payment exposure, past findings, legal concerns, and control weaknesses. Frequency is only one dimension. A low-frequency issue with serious legal or patient implications may deserve earlier attention than a common minor defect. State the basis for prioritization and update it as evidence changes rather than presenting a subjective ranking as an official universal risk formula.

Apply it

An audit finds frequent low-dollar clerical errors and a less frequent arrangement involving possible referral remuneration. Evaluate financial, legal, and operational consequences separately; the larger error count should not automatically determine which issue receives immediate compliance attention.

Common pitfall: Do not rank risk solely by dollars or error counts. A lower-volume issue can demand priority when its potential consequences or control failures are substantial.

HHS-OIG General Compliance Program Guidance — November 2023

54.How can patterns reveal a root cause?

Compare validated findings across practitioners, sites, codes, dates, and workflows to identify plausible causes. A sudden increase after a software change suggests a different investigation from errors isolated to one newly trained team. Patterns generate hypotheses; they do not prove causation without further evidence. Examine configuration, instructions, and actual practice before selecting corrective action. Distinguishing a system defect from an individual knowledge gap helps avoid repeated errors after superficial education.

Apply it

Unsupported modifiers appear across all clinicians immediately after a billing-system update. Inspect the new rule and workflow before assigning individual retraining, then test whether the configuration automatically adds modifiers without requiring evidence of qualifying distinct circumstances.

Common pitfall: A statistical association is a clue, not proof of cause. Training everyone may appear decisive while leaving an automatic billing rule that reproduces the defect.

HHS-OIG General Compliance Program Guidance — November 2023

55.What limitations belong in an audit report?

Report limitations that materially affect interpretation, including population boundaries, selection method, unavailable records, unresolved issues, and whether statistical inference is supported. State verified results clearly before explaining those boundaries. Limitations should constrain conclusions rather than obscure findings. A targeted sample can support strong conclusions about reviewed claims while supporting weaker conclusions about overall prevalence. Readers need that distinction to decide whether further investigation, correction, or broader sampling is warranted.

Apply it

A targeted review identifies six unsupported claims among fifteen selected outliers. Report the six validated findings and their established financial effect, describe the outlier-based selection, and state that the observed rate is not an estimate for all claims.

Common pitfall: A vague phrase such as results may vary does not explain a material limitation. Describe the specific boundary and how it changes permissible interpretation.

Medicare Program Integrity Manual — Chapter 8 · HHS-OIG General Compliance Program Guidance — November 2023

56.How should education respond to audit findings?

Effective education addresses the demonstrated decision error using the applicable rule and realistic examples. Tailor content to the people who control the relevant step, such as ordering practitioners, coders, or system administrators. Explain discriminating cues rather than distributing a generic reminder. Education should also include a way to evaluate whether understanding and behavior changed. Attendance documents participation, but it does not establish that future claims meet the requirement or that the root cause was resolved.

Apply it

Coders repeatedly choose modifier 59 whenever diagnoses differ. Teach why diagnosis difference alone is insufficient, work through distinct-service examples, and review later claims for evidence-based modifier selection rather than relying only on completion of the training session.

Common pitfall: A signed attendance sheet is not proof of effective remediation. Education alone may be inadequate when the actual cause is a system default or conflicting incentive.

HHS-OIG General Compliance Program Guidance — November 2023

57.Which controls prevent errors and which detect them?

Preventive controls act before an error reaches the claim, while detective controls identify problems during or after processing. Examples include requiring a documented justification before a modifier can be submitted and periodically reviewing modifier outliers. Neither type is automatically sufficient alone. Match controls to the cause, identify who operates them, and consider how staff could bypass them. A control is meaningful when its operation and effect can be demonstrated rather than merely described in policy.

Apply it

After finding automatic unsupported modifiers, a practice disables the default, requires an evidence-based selection step, and adds a periodic exception report. The first changes the upstream process; the report checks whether inappropriate patterns continue despite the revised workflow.

Common pitfall: A warning that staff routinely override may provide little prevention. A dashboard no one reviews provides little detection, even if both controls exist on paper.

HHS-OIG General Compliance Program Guidance — November 2023

58.How should financial remediation follow a validated finding?

Financial remediation requires validated determinations, an affected population, and the applicable reporting-and-return rules. Medicare Part A/B example: under 42 CFR 401.305, an overpayment is identified when a person knowingly receives or retains it; knowing includes actual knowledge, deliberate ignorance, or reckless disregard. The general deadline is the later of 60 days after identification or the applicable cost-report due date. A timely, good-faith investigation of related overpayments can suspend the 60-day deadline. That suspension ends at the earlier of completing the investigation and calculating the aggregate initial and related overpayments, or 180 days after initial identification.

Apply it

A Medicare Part B practice identifies an overpayment and promptly begins a good-faith investigation for related overpayments from the same billing defect. Record the identification date and investigation start, calculate the aggregate amount, and track when the conditional suspension ends and the remaining reporting-and-return period resumes. Correct the prospective system rule while addressing historical payments.

Common pitfall: The investigation suspension is conditional, not an automatic 180-day extension for every audit. Do not postpone identification until every related claim is counted, assume a cost-report deadline applies to every payment, or treat a prospective fix as resolution of historical overpayments.

Federal Register :: Request Access · HHS-OIG General Compliance Program Guidance — November 2023 · Medicare Program Integrity Manual — Chapter 8

59.What makes corrective-action follow-up measurable?

A corrective-action plan should identify the specific action, responsible owner, completion expectation, and evidence used to assess effectiveness. Follow-up distinguishes implementation from sustained improvement: a revised policy can be complete while the underlying error continues. Define the review method and success criteria before evaluating later performance. If findings persist, reassess the cause and control design rather than repeatedly closing and reopening the same issue based only on promises.

Apply it

A department updates its laboratory-order workflow and reports completion. Follow-up examines later claims for documented ordering intent and clinical support, compares results with predefined criteria, and investigates remaining failures before declaring the corrective action effective across the workflow.

Common pitfall: A completed task is not necessarily an effective control. Closing a finding solely because a policy was issued leaves actual claim performance untested and unresolved.

HHS-OIG General Compliance Program Guidance — November 2023

60.How do monitoring and auditing complement each other?

Monitoring is an ongoing check of operations or indicators, while auditing is a more structured evaluation against defined criteria with an appropriate degree of independence. Monitoring can identify unusual patterns that trigger an audit; an audit can reveal which ongoing indicators would be useful. Neither should be confused with the other simply because both involve reviewing data. Clear ownership, escalation, and follow-up help convert detected anomalies into validated findings and sustained corrective action.

Apply it

A monthly dashboard flags rising modifier use at one clinic. Use that monitoring signal to select a focused audit with defined criteria and record review, then refine the dashboard after the audit identifies which patterns actually predict unsupported reporting.

Common pitfall: An outlier alert is not a confirmed violation. Conversely, completing an occasional audit does not replace ongoing operational monitoring when the relevant risk can recur.

HHS-OIG General Compliance Program Guidance — November 2023

What to focus on during revision

The following are CertMedbry study suggestions. Use the official outline to check the full scope of your examination.

  • Separate record authenticity, clinical content, coding accuracy, medical necessity, and payment eligibility instead of collapsing them into one documentation judgment.
  • Learn the distinct elements of the FCA, AKS, Stark, and exclusion rules; explain why the same arrangement may require more than one legal analysis.
  • Practise Medicare NCCI decisions using the service relationship, modifier indicator, actual distinct circumstances, and correct unit definition.
  • Define population, sampling frame, selection method, unit, and denominator before calculating or interpreting an audit result.
  • Abstract outpatient diagnoses, E/M level evidence, and laboratory support from the actual record. Distinguish MDM from qualifying practitioner time and exclude separately reported procedure time from E/M time.
  • Write findings that connect criteria to evidence, quantify only supported effects, and lead to measurable corrective action.

A practical preparation plan

1. Map the complete issuer scope

Use AAPC's public expertise list and six study-guide content sections as the full scope reference. Compare your experience with each area and identify gaps beyond this selective guide, including Recovery Audit Contractor (RAC) audits and broader physician-service E/M audit cases.

2. Create a date-and-setting reference habit

For each practice case, state the service date, setting, payer, and applicable rule version before deciding the code or payment issue. Keep coding-reference dates separate from examination-outline dates.

3. Abstract before judging

Record the clinical facts, source locations, ordering intent, authentication, and quantities first. Then compare those facts with the reported claim and applicable criteria.

4. Work competing explanations

For each finding, test whether missing records, a wrong rule version, a unit conversion, or a permitted documentation pathway changes the conclusion. Explain why the strongest alternative fails.

5. Calculate with labeled denominators

Practise claim error rates, line measures, and dollar ratios separately. Identify whether selection supports only descriptive findings or a properly designed population estimate.

6. Turn findings into follow-up

Draft a short finding with criterion, condition, evidence, effect, and limitation. Assign a cause-focused corrective action and specify what later evidence would demonstrate improvement.

7. Use the drills for diagnosis

Complete the questions independently, explain every alternative, and revisit the related concepts after errors. Use flashcards for active recall and practise efficient navigation of permitted references.

Use your sample score as a starting point

The free set contains 20 original practice questions. It is a small learning sample, not an official examination or a validated pass prediction. Review each explanation and its source before moving to another topic.

Start the free sample

Official sources and updates

Confirm current eligibility, fees, scheduling and policies directly with the examination provider. CertMedbry is independent and is not endorsed by these organisations. How we handle content and corrections.