--- name: auditing-coding-accuracy language: en description: Reviews coded encounters for accuracy using OIG compliance guidelines and CMS documentation requirements. Use when auditing medical codes, reviewing coding accuracy, or conducting compliance audits. tags: - audit - medical-coding-and-billing - compliance metadata: author: casemark practice_areas: - Medical Coding - Revenue Cycle - Health Information Management document_types: - Audit Report skill_modes: - Audit - Compliance --- # Auditing Coding Accuracy Reviews coded encounters for accuracy against OIG compliance guidelines, CMS documentation requirements, AMA CPT rules, and ICD-10-CM/PCS Official Guidelines. Identifies over-coding, under-coding, unbundling errors, and documentation deficiencies that create compliance risk or revenue leakage. ## Why This Skill Exists Coding accuracy directly determines reimbursement integrity. The OIG Work Plan targets high-error-rate services annually — E/M upcoding, modifier misuse, and diagnosis specificity failures drive the majority of overpayment recoveries. A structured audit process catches errors before they become extrapolated liabilities. CMS CERT reports consistently show national paid-claim error rates between 6–8%, with improper payments exceeding $28 billion annually. Internal audits are the primary defense against external auditor findings and False Claims Act exposure. --- ## Checkpoint A — Intake ### Questions to Confirm Before Starting 1. What is the audit scope? (prospective pre-bill, retrospective post-payment, focused, or random) 2. Which service lines or provider specialties are included? 3. What date-of-service range applies? 4. Is this triggered by an external event (RAC audit, OIG inquiry, payer request)? 5. What sample methodology is required? (random, stratified, targeted by CPT range) 6. What coding systems are in scope? (CPT, ICD-10-CM, ICD-10-PCS, HCPCS Level II) 7. Are there known risk areas from prior audits or denial trends? ### Documents Required - Coded encounter records with assigned CPT/HCPCS, ICD-10-CM/PCS codes, and modifiers - Complete medical record documentation (physician notes, operative reports, diagnostic results) - Chargemaster or fee schedule for billed amounts - Prior audit findings and corrective action plans - Applicable LCD/NCD policies for services under review - NCCI edit files (current quarterly release) for bundling validation - Payer-specific coding guidelines if non-Medicare claims are in scope --- ## Step 1 — Define Audit Parameters and Sampling Establish the universe of claims and select the sample. - **Random sample**: Use statistically valid methodology — minimum 30 records per provider or service line for meaningful error-rate calculation. OIG probe audits use 30-claim samples; RAC audits may extrapolate from as few as 20–40. - **Stratified sample**: Weight by revenue, denial frequency, or known-risk CPT ranges (e.g., 99213–99215 for E/M, 10021–69990 for surgical). - **Targeted sample**: Focus on specific codes flagged by comparative billing reports (CBRs), payer audits, or outlier analysis. - Document the sampling frame, selection method, confidence level, and margin of error. - Record the audit universe size and sample size in the audit work papers. ## Step 2 — Validate Diagnosis Coding (ICD-10-CM/PCS) Review each diagnosis code for accuracy, specificity, and guideline compliance. - Verify the principal diagnosis follows ICD-10-CM Official Guidelines Section II (inpatient) or the reason for the encounter (outpatient). - Check laterality, episode of care (7th character), and anatomic specificity — e.g., M54.5 (low back pain) vs. M54.51 (vertebrogenic low back pain) vs. M54.59 (other low back pain). - Validate sequencing rules: manifestation codes cannot be principal; etiology/manifestation pairs must be sequenced correctly (e.g., E11.65 + E08.36). - Confirm "code first" and "use additional code" notes are followed. - For inpatient PCS coding, verify the root operation matches the operative report (e.g., Excision vs. Resection vs. Destruction). - Flag unspecified codes (categories ending in .9) where documentation supports greater specificity. - Confirm excludes1/excludes2 notes are respected — excludes1 codes cannot coexist on the same claim. ## Step 3 — Validate Procedure Coding (CPT/HCPCS) Review each procedure or service code for accuracy and documentation support. - Verify the CPT code descriptor matches the documented service — read the full code description, not just the short descriptor. - For E/M services, apply the 2021+ framework: confirm MDM level (number/complexity of problems, data reviewed, risk of management) or total time on date of encounter. - Check that add-on codes (+) are reported with their primary codes and never stand alone. - Validate that separate procedure codes (designated in CPT) are only reported when performed at a separate site, separate session, or for a distinct purpose. - Confirm HCPCS Level II codes are used where required (e.g., J-codes for drugs, A/L codes for DME). - For surgical codes, verify the operative report supports each code element: approach, extent, anatomic site. ## Step 4 — Validate Modifier Application Audit every modifier for clinical justification and correct usage. - **Modifier 25**: Confirm a separately identifiable E/M service is documented beyond the procedure's typical pre/post work. Look for a distinct chief complaint, history, exam, or MDM unrelated to the procedure decision. - **Modifier 59 / XE, XS, XP, XU**: Verify distinct procedural service — separate encounter (XE), separate structure (XS), separate practitioner (XP), or unusual non-overlapping service (XU). Modifier 59 is the modifier of last resort when X-modifiers do not apply. - **Modifier 26/TC**: Confirm correct component billing — 26 for professional interpretation only, TC for technical component only. - **Modifiers 76/77**: Verify repeat procedure documentation with clinical necessity for the repeat. - Flag any modifier used without supporting documentation as a coding error. ## Step 5 — NCCI and Bundling Edit Validation Check all code pairs against current NCCI edits. - Run all CPT code pairs on the same claim through the current NCCI Procedure-to-Procedure (PTP) edit table. - Column 1/Column 2 pairs: the Column 2 code is bundled into Column 1 and should not be separately reported unless an appropriate modifier is appended AND documentation supports the exception. - Check the Mutually Exclusive Edits (MUE) table — confirm units billed do not exceed the MUE value for each code. - Validate Medically Unlikely Edits against the claim's units of service. - Document each bundling exception with the specific clinical rationale. ## Step 6 — Score and Classify Findings Apply a consistent error classification to each finding. - **Over-coded**: Higher-level code assigned than documentation supports (e.g., 99215 billed when MDM supports 99214). - **Under-coded**: Lower-level code assigned, resulting in missed legitimate revenue. - **Unbundled**: Separately reported codes that should be bundled per NCCI or CPT guidelines. - **Incorrect code**: Wrong CPT/ICD code entirely (e.g., wrong anatomic site, wrong procedure type). - **Missing code**: Documented service not coded at all. - **Modifier error**: Incorrect, missing, or unsupported modifier. - **Documentation deficiency**: Code may be correct but documentation is insufficient to support it. - Calculate per-provider and per-service-line error rates. OIG considers >5% error rate a significant compliance concern. --- ## Checkpoint B — Review ### Before Finalizing the Audit Report - [ ] Every sampled record has been independently re-coded from source documentation - [ ] Error classifications are consistent across all reviewers - [ ] Financial impact has been calculated for each error type (over-payments and under-payments) - [ ] Extrapolation methodology is documented if projecting to the full universe - [ ] Provider-specific feedback summaries are prepared with concrete examples - [ ] Corrective action recommendations are prioritized by financial impact and compliance risk - [ ] All findings reference specific coding guidelines (CPT Assistant, Coding Clinic, ICD-10-CM Guidelines section) - [ ] The audit report distinguishes between coder errors and documentation deficiencies requiring physician education --- ## Quality Audit - [ ] Sample selection methodology is documented and defensible - [ ] Each finding cites the specific guideline, rule, or reference supporting the auditor's conclusion - [ ] Error rate calculations use correct numerator/denominator (errors / total code assignments reviewed) - [ ] Financial impact includes both overpayment exposure and underpayment recovery opportunity - [ ] Findings are categorized by root cause (coder knowledge gap, documentation gap, system configuration) - [ ] Corrective action plan includes responsible party, deadline, and re-audit date - [ ] Report includes comparison to prior audit periods for trend analysis - [ ] Disclaimers note that audit findings are based on documentation available at time of review --- ## Guidelines - Follow OIG Compliance Program Guidance for Individual and Small Group Physician Practices and Hospital Compliance Programs - Apply ICD-10-CM Official Guidelines for Coding and Reporting (current fiscal year edition) for all diagnosis code validation - Use CPT codebook conventions, instructions, and guidelines — including parenthetical notes and symbol definitions — for procedure code validation - Reference CMS Internet-Only Manuals (IOM) Chapter 12 for physician billing and Chapter 23 for fee schedule policies - Apply AHIMA Standards of Ethical Coding — coders shall not change codes or narratives of code descriptions to misrepresent diagnoses or procedures - Never extrapolate without documented statistical methodology and confidence intervals - Mark any finding where auditor confidence is below 90% with [VERIFY] and escalate to a credentialed coding specialist (CCS, CPC, or RHIA) - All audit work papers must be retained per organizational policy and applicable state/federal record retention requirements --- Source attribution: CaseMark Original project: https://github.com/CaseMark/skills/blob/449269ec49b6a8f1b4614cea52aa44b2a76e4e94/skills/med/auditing-coding-accuracy/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 CaseMark, Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: CaseMark Original project: https://github.com/CaseMark/skills/blob/449269ec49b6a8f1b4614cea52aa44b2a76e4e94/skills/med/auditing-coding-accuracy/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Finance & Accounting, Healthcare & Life Sciences, Legal Roles: Auditor, Compliance Officer, Data Analyst, Health Informatics, Medical Writer Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 215b71443c7d19086c96569f8be87e91757a83b3282a75fb45e548db9b8f2c49