Specialty Coding Complexity: E&M, Inpatient vs Outpatient Coding, and the Audit Framework for Medical Coding Compliance

Most coding-related compliance issues do not begin with fraud or deliberate upcoding. They often stem from documentation gaps, inconsistent workflows, or coding practices that have not kept pace with evolving regulations. While these issues may seem minor in isolation, they can gradually lead to denials, reimbursement losses, and increased audit exposure.

The impact of these challenges is becoming increasingly visible across the healthcare industry. Healthcare organizations experienced a 126% surge in coding-related denials in 2024 despite significant investments in outsourcing and automation. At the same time, the CMS Comprehensive Error Rate Testing (CERT) program reported $28.83 billion in Medicare fee-for-service improper payments in FY2025, representing a 6.55% error rate, with coding-related issues remaining a major contributor. External audit activity has also intensified, with audit volumes more than doubling in 2024 compared to the previous year and average at-risk dollars per healthcare organization increasing fivefold to $11.2 million.

The financial consequences extend far beyond individual claim denials. Industry data indicates that the average hospital loses approximately $5 million annually to denied claims, representing nearly 5% of net patient revenue. Even more concerning, up to 65% of denied claims are never resubmitted, turning preventable coding and documentation issues into permanent revenue leakage.

These trends highlight a broader reality: specialty coding within today’s medical billing specialties is no longer just a coding function. It depends on strong coordination between clinical documentation, coding teams, revenue cycle operations, and compliance programmes. When these areas operate in silos, even small documentation gaps can evolve into significant financial, operational, and regulatory risks.

A healthcare revenue cycle is only as strong as the coding and documentation framework behind it. Understanding where breakdowns occur is the first step toward building a more accurate, compliant, and resilient coding programme. This article examines four areas where specialty coding programmes most commonly encounter risk—E&M and Emergency Department coding, inpatient versus outpatient coding distinctions, pathology and diagnostic coding, and the audit framework required to maintain ongoing compliance.

Understanding Specialty Coding Complexity

Medical coding is often viewed as a process of translating clinical documentation into billing codes. While that may be true for routine, low-acuity encounters, specialty coding involves a much broader set of considerations.

Healthcare organisations must navigate multiple coding systems, payer-specific coverage requirements, professional and facility billing rules, documentation standards, and reimbursement methodologies that vary across care settings. The complexity increases further when clinical conditions, admission status, and specialty-specific coding requirements come into play.

For example, a single Emergency Department visit may generate both a professional claim and a facility claim, each governed by different documentation and reimbursement requirements. Similarly, a patient’s admission status can influence reimbursement methodology, quality reporting, and audit exposure. In pathology services, billing modifier errors can create recurring denial patterns that often remain hidden until they become a larger operational issue.

What makes specialty coding particularly challenging is that these issues rarely exist in isolation. A documentation gap can affect code selection. A coding error can impact reimbursement. A reimbursement issue can trigger an audit review. Each part of the process is interconnected.

For most healthcare organisations, specialty coding challenges tend to concentrate around four key areas: E&M and Emergency Department coding, inpatient versus outpatient coding distinctions, pathology and diagnostic coding, and the audit framework that supports ongoing compliance. Together, these four pillars form the foundation of a strong coding compliance programme.

Pillar 1: Evaluation &Management and Emergency Department Coding

The 2023 E&M Changes and Why Organisations Still Struggle with Them

The 2023 AMA E&M guideline revisions marked one of the most significant changes to E&M coding in years, but they were not the last major update. Additional CPT revisions effective January 1, 2024 further changed how certain E&M services are reported, particularly for time-based coding, multiple same-day services, and split/shared visits.

Previously, history and physical examination played a central role in determining code levels. Under the revised E&M coding guidelines, office and outpatient visit levels (CPT 99202–99215) are now primarily determined by MDM (Medical Decision Making) or the total time spent on the encounter date. Together, these changes shifted documentation requirements away from extensive histories and examinations and toward clearly demonstrating clinical complexity, decision-making, and the work performed during the encounter.

Under the updated framework, MDM is evaluated across three key areas: the number and complexity of problems addressed, the amount and complexity of data reviewed, and the overall risk associated with patient management decisions. The supporting documentation must be present in the medical record at the time of billing and align with the selected code level.

The challenge is not necessarily that clinicians are documenting less. Rather, many organisations continue to struggle with aligning clinical documentation, coding interpretation, and evolving E&M coding requirements. As a result, gaps between documented care and coding support remain a leading contributor to E&M audit findings.

Why ED Facility Coding Carries High Audit Risk

ED facility coding remains one of the most heavily audited outpatient billing areas and is frequently reviewed as part of broader compliance and reimbursement assessments. ED Level 1–5 facility codes (CPT 99281–99285) generate significant outpatient reimbursement, making them a consistent target for payer reviews and OIG oversight. A major challenge is that facility coding requirements do not fully mirror physician E&M coding requirements. Yet many organisations still treat them as interchangeable workflows, creating a systematic misalignment between what is billed and what can be defended.

Place of Service (POS) coding adds another layer of complexity. An E&M service billed with POS 22 (on-campus outpatient hospital) is reimbursed at the facility rate, lower than the non-facility rate applied to POS 11 (office). Incorrect POS assignment can create both reimbursement leakage and compliance risk. Importantly, many POS issues originate from EHR configuration problems rather than coder mistakes, which means education alone will not resolve the issue.

Without aligned workflows between documentation, coding, and billing systems, ED coding becomes highly vulnerable to denials and audits.

Pillar 2: Inpatient vs Outpatient Coding

Why Inpatient vs Outpatient Coding Still Creates Major Compliance Risk

Even after years of CMS guidance, inpatient vs outpatient coding remains one of the most misunderstood areas in healthcare reimbursement.

The CMS two-midnight rule states that inpatient admission is generally appropriate when a physician expects the patient to require hospital care spanning at least two midnights. However, the documentation supporting that expectation must align with the patient’s condition and care plan.

Many organisations continue to struggle with accurately determining whether a patient should be classified under observation or inpatient status, particularly when admission documentation is incomplete or medical necessity is not clearly established in the clinical record. Accurate documentation not only supports reimbursement and compliance but also enables more coordinated patient-centred care delivery by ensuring that care decisions, treatment plans, and resource allocation align with the patient’s clinical needs.

These challenges become even more complex when patient status changes occur late in the care cycle, creating inconsistencies between clinical documentation, billing, and reimbursement logic. As a result, such cases frequently surface in MAC Targeted Probe and Educate (TPE) reviews. When denial rates exceed acceptable thresholds, what begins as a limited review in one service area can quickly expand into a broader organisation-wide audit.

DRG vs APC: Why Reimbursement Logic Changes by Setting

Inpatient and outpatient reimbursement systems operate under entirely different reimbursement frameworks, which is why admission classification plays such a critical role in healthcare coding and billing accuracy. Accurate inpatient vs outpatient coding is essential because inpatient reimbursement under the Inpatient Prospective Payment System (IPPS) is primarily driven by MS-DRG assignment, principal diagnosis sequencing, ICD-10-CM diagnosis coding, and ICD-10-PCS procedure coding.

Outpatient reimbursement, on the other hand, follows the Outpatient Prospective Payment System (OPPS), where payment is determined through APC grouping based on CPT and HCPCS code assignment. Because these frameworks follow different coding and reimbursement logic, the same clinical encounter can produce significantly different financial outcomes depending on whether the patient is classified as inpatient or outpatient.

This distinction becomes especially important in high-acuity cases such as sepsis, respiratory failure, and complicated infections, where diagnosis sequencing directly influences DRG assignment and reimbursement weight. Even small sequencing errors can alter reimbursement levels and impact the accuracy of the final claim. Accurate POA indicator reporting further adds to the complexity. When a POA indicator is assigned incorrectly or supporting documentation is incomplete, hospitals may face Hospital-Acquired Condition (HAC) reporting issues and payment reductions. In many cases, these problems originate not from incorrect coding decisions, but from gaps in clinical documentation that were never resolved before the claim was coded and submitted.

Pillar 3: Pathology and Diagnostic Coding

The TC/PC Billing Problem Many Organisations Overlook

Technical component (TC) and professional component (PC) billing errors remain one of the most common yet overlooked challenges in hospital-based pathology coding. These issues typically arise when pathology groups, outreach laboratories, and hospital billing systems operate independently without aligned modifier logic or coordinated billing workflows. As a result, multiple claims may be submitted for the same service encounter, with one billing globally, another using modifier TC for the technical component, and another using modifier 26 for the professional component. This creates competing claims for the same date of service, often triggering recurring NCCI edit denials and reimbursement delays.

In many organisations, these denials are handled manually on a case-by-case basis instead of addressing the underlying workflow and billing rule inconsistencies causing the problem. While individual denials may initially appear isolated, they gradually accumulate into larger accounts receivable backlogs, reimbursement delays, and recurring compliance issues. Over time, what begins as a billing coordination gap can evolve into a significant operational and financial burden for pathology and revenue cycle teams.

Diagnostic Sequencing Errors in Outpatient Coding

Another common challenge in specialty coding involves outpatient ICD-10-CM diagnostic sequencing. Outpatient coding guidelines clearly state that suspected, probable, or “rule out” diagnoses should not be coded as confirmed conditions. Inpatient coding rules, however, follow a different convention and allow qualified diagnoses to be coded at the highest level of certainty documented. Problems arise when coders move between inpatient and outpatient workflows without clear specialty-specific guidance, leading to these distinctions being applied incorrectly across settings.

As a result, organisations often face two different types of coding risk. In some cases, unsupported outpatient diagnoses are overcoded as confirmed conditions, creating compliance and audit concerns. In other situations, confirmed findings that evolve later during the encounter process may not be captured accurately, resulting in undercoding and missed reimbursement opportunities. While only some of these issues surface through denial reporting, both create significant documentation, compliance, and reimbursement challenges over time.

Pillar 4: The Audit Framework That Keeps Coding Programmes Defensible

Why Audit Programmes Need to Be Continuous

Strong coding programmes are not built solely on coder accuracy. Strong coding programmes are not built solely on coder accuracy. An effective medical coding audit strategy relies on continuous audit visibility, workflow governance, and proactive risk monitoring, aligned with evolving regulatory expectations. One of the most important indicators of future audit focus areas continues to be the OIG Work Plan, which healthcare organisations frequently use to strengthen audit preparedness and regulatory monitoring. Current priorities include modifier 25 E&M billing, clinical diagnostic laboratory testing, Medicare Advantage RADV audits, and documentation support for medical necessity. Organisations that fail to align their internal audit strategies with these evolving regulatory priorities often find themselves reacting only after external audits or payer reviews have already begun, significantly increasing both financial and compliance risk.

Prospective vs Retrospective Audit Design

Both prospective and retrospective audits play a critical role in maintaining coding accuracy, medical coding compliance, and regulatory adherence, but they serve very different purposes within a healthcare organisation. Prospective audits take place before claims are submitted and are designed to identify documentation gaps, coding inconsistencies, and high-risk claims early in the process. Their primary value lies in prevention, helping organisations correct issues before they turn into denials, repayment demands, or audit triggers. Retrospective audits, on the other hand, review claims after payment to uncover recurring workflow failures, denial trends, and broader systemic coding issues that may have developed over time. These audits are essential for long-term process improvement and operational governance.

To strengthen both prospective and retrospective review processes, many healthcare organisations leverage medical coding audit services to identify documentation gaps, coding inconsistencies, and emerging compliance risks before they escalate into denials, repayment demands, or external audit findings. However, these efforts deliver value only when audit insights translate into workflow improvements. Organisations that treat audits as reporting exercises rather than catalysts for corrective action often allow recurring issues to persist, increasing both compliance exposure and financial risk over time.

Prospective Audit vs Retrospective Audit vs RAC Audit — triggers, scope, ownership, and regulatory implications:

CERT Findings as a Signal for Deeper Workflow Issues

CERT improper payment data gives healthcare organisations valuable insight into where coding and documentation errors occur most frequently across the industry. One of the most important findings from CERT reviews is that the problem is often not incorrect code selection, but insufficient documentation to support the code that was billed. This distinction matters because the solution is not always additional coder training. In many cases, the underlying issue lies in disconnected workflows between Clinical Documentation Improvement (CDI) teams and coding teams.

As healthcare organisations increasingly adopt technologies such as natural language processing (NLP) to improve documentation quality and extract clinical insights from unstructured records, greater attention is being placed on strengthening documentation workflows and ensuring that clinical intent is accurately captured for coding and compliance purposes.

When organisations respond to documentation-related audit findings solely through coding education programmes, the underlying workflow gaps often remain unresolved. As a result, the same denial patterns and audit findings continue to recur. Strong coding compliance programmes therefore require tighter integration between clinical documentation processes, CDI workflows, and coding operations rather than focusing exclusively on coder accuracy.

Where the Four Pillars Commonly Break Down

Even organisations with mature coding programmes often face recurring operational challenges when coding, documentation, compliance, and audit functions operate independently instead of as part of a connected governance model. Across many specialty coding environments, similar failure patterns continue to emerge repeatedly.

Failure Pattern 1: Documentation Evidence Is Disconnected

One of the most common issues occurs when documentation evidence is spread across multiple systems without a unified audit trail. A CDI team may review a patient record and issue a query, the physician may respond with updated documentation, and the coding team may assign the final code correctly. However, if the physician addendum, CDI query, and coding rationale are all stored separately without a shared encounter identifier, the organisation may struggle to assemble a complete documentation package during an external audit.

In these situations, the coding itself may technically be correct, but the organisation cannot fully defend the claim because the supporting evidence is fragmented across systems. This creates significant audit vulnerability, especially in high-complexity inpatient cases where documentation integrity becomes critical during RAC reviews.

Failure Pattern 2: Audit Findings Do Not Lead to Workflow Changes

Another common breakdown occurs when audit findings are treated as reporting exercises instead of operational improvement opportunities. For example, an audit may identify a recurring documentation issue in ED Level 4 and Level 5 encounters caused by incomplete nursing triage notes. The finding is presented to leadership and included in compliance reports, but no clear ownership is assigned to fix the underlying workflow problem.

As a result, the same issue continues to appear in future audits because the organisation never translated the finding into clinical documentation changes, provider education, or workflow redesign. Without accountability and follow-through, even well-executed audits fail to produce meaningful compliance improvement.

Failure Pattern 3: Coding Logic Is Not Continuously Updated

Many organisations still treat coding compliance as a one-time validation exercise completed during implementation or system go-live. In reality, coding rules evolve continuously through payer policy changes, LCD updates, NCCI revisions, and CPT modifications. When organisations fail to actively monitor and update their coding logic, their workflows gradually drift away from current regulatory requirements without immediate visibility.

Over time, these unnoticed gaps begin to create recurring denials, reimbursement delays, and audit exposure. In one multi-site pathology programme, outdated TC/PC billing logic resulted in thousands of recurring NCCI edit denials over more than a year before the issue was identified through retrospective audit review. Problems like these rarely emerge overnight as they build slowly through disconnected governance and outdated workflows.

Building a More Defensible Specialty Coding Programme

Specialty coding compliance is no longer just about assigning the correct code. It requires coordinated governance across HIM, CDI, revenue cycle operations, compliance teams, clinical documentation workflows, and technology systems within today’s healthcare provider ecosystem. As healthcare organisations modernise through digital health platforms, integrating coding, documentation, and compliance processes into connected ecosystems is becoming essential for maintaining accuracy, transparency, and audit readiness.

Organisations that rely solely on annual audits or isolated compliance reviews often identify issues only after denials, reimbursement losses, or payer scrutiny have already increased. In contrast, the most effective coding programmes operate with continuous audit feedback loops, proactive workflow monitoring, and strong alignment between documentation, coding, and compliance functions. This approach enables organisations to identify risks earlier, improve reimbursement accuracy, strengthen audit defensibility, and reduce long-term compliance exposure before issues escalate.

Building and sustaining such a programme requires more than coding expertise alone. With our medical coding capabilities, SRM Tech helps healthcare organisations improve documentation integrity, streamline clinical and operational workflows, and create connected digital ecosystems that strengthen compliance, audit readiness, and revenue cycle performance.