AMPC Designation common mistakes
AMPC Designation · Understand the traps and how to avoid them.
Selecting an E/M level from the chief complaint or a single vital sign instead of applying the full medical decision-making or time criteria to the documented note.
Candidates carry over habits from simpler coding work and pick the level that 'feels right' for the visit type, so they miss that level selection now depends on documented problems, data reviewed, and risk, or on total time with a supporting statement.
What to do instead
Before answering, underline the documented problems addressed, the data ordered or reviewed, and the risk of complications, then score each element against the MDM table. If time is used instead, confirm the note states total time and the activities. Practice on ten notes per study session and write the two MDM elements that drive the level.
Coding a procedure or diagnosis from the operative report heading or the surgeon's summary line rather than reading the body of the report to the end.
The summary line is short and looks authoritative, so candidates stop reading and miss additional procedures, laterality changes, or conversion from laparoscopic to open that the body documents.
What to do instead
Read the entire report first, then list every distinct procedure and the approach, laterality, and extent actually documented. Compare that list against the codes selected and add any procedure the body supports but the heading omits.
Assigning a diagnosis code based on a test result, pathology report, or suspected condition when the provider has not documented that diagnosis in the encounter.
Candidates treat clinical evidence as equivalent to a documented diagnosis and want the claim to look complete, forgetting that outpatient diagnosis coding follows provider documentation.
What to do instead
Code only what the provider documents in that encounter. When a result is present but the diagnosis is not stated, code the sign, symptom, or reason for the visit that the provider did document, and flag the record for a query rather than guessing.
Ignoring payer-specific rules and filing every claim the same way, then treating denials as random.
Candidates learn a single national rule set and assume it applies universally, so they miss that modifiers, bundling edits, and prior authorization requirements vary by payer and plan.
What to do instead
Before answering, identify which payer and plan type the scenario names and recall that payer's published policy for the service in question. Build a habit of checking the payer policy grid for the top ten billed services in the practice.
Submitting a claim without verifying eligibility, benefits, or prior authorization status, or without checking the timeliness deadline for appeals.
Candidates focus on code accuracy and treat front-end and follow-up steps as clerical, so they overlook that most denials in these scenarios stem from eligibility, authorization, or missed filing windows.
What to do instead
For every scenario, run a checklist: eligibility verified, authorization on file, claim filed within the payer window, denial appealed within the appeal deadline. Memorize that appeal and filing deadlines are payer-specific and must be looked up, not assumed.
Using a modifier to force a claim to pay without confirming the documentation supports it, such as appending a distinct-service modifier to a bundled pair.
Candidates see a denial or a bundling edit and reach for the modifier that unlocks payment, rather than asking whether the services were truly separate and documented as such.
What to do instead
State the documentation requirement for each modifier before applying it: separate site, separate session, distinct service. If the note cannot support that statement, do not append the modifier; instead correct the coding or accept the bundling.
Designing or evaluating a front-office workflow without accounting for registration accuracy, scheduling templates, and patient financial counseling as connected steps.
Candidates treat each office function in isolation and answer as if a fix in one area has no effect on the others, missing how a registration error propagates into coding and collections.
What to do instead
Trace the patient encounter end to end in every scenario: scheduling, registration and insurance capture, coding, charge entry, claim submission, and follow-up. Identify where the failure originates and what downstream step it corrupts before choosing an answer.
Answering a compliance scenario by choosing the option that maximizes revenue or speed instead of the option that meets the legal or policy requirement.
Candidates import business instincts from general management study and undervalue the compliance constraints, so they pick the efficient answer over the defensible one.
What to do instead
For any compliance question, first name the governing rule, such as a false claims prohibition, an anti-kickback concern, or a privacy standard, then eliminate options that conflict with it. The correct answer must satisfy the rule even when it costs time or money.
Treating an audit finding as a single bad code instead of identifying the root cause and the corrective action the auditor should recommend.
Candidates stop once they spot the error and do not carry the analysis forward to education, policy change, or monitoring, which is what audit scenarios actually test.
What to do instead
After identifying each error, write the root cause category: documentation gap, code selection error, modifier misuse, or process failure. Then pair it with a corrective action such as targeted provider education, a template change, or a re-audit sample size.
Calculating an audit error rate or sample result without defining the sampling method, the unit of review, and whether errors are counted per claim or per code.
Candidates compute a percentage from raw counts without establishing the denominator, so the rate is inconsistent and cannot be compared to a benchmark or threshold.
What to do instead
State the population, the sample size, the unit of review, and the error definition before calculating. Count errors consistently at the stated unit, show the numerator and denominator explicitly, and only then compare against the practice threshold.