Skip to main content
Advances in Health Information Science and Practice logoLink to Advances in Health Information Science and Practice
. 2025 Dec 12;1(2):LFYE5539. doi: 10.63116/LFYE5539

Correct Coding and Navigating Payer Expectations

Leah Akers 1
PMCID: PMC12917905  PMID: 41743489

Abstract

In this commentary, the author examines the root cause and barriers to billing compliance due to varying payer (insurance) requirements. The author examines uniform code set requirements enacted with the Health Insurance Portability and Accountability Act (HIPAA) and offers practical recommendations for health information (HI) professionals striving for compliance. Recommendations offered by the author include proactive approaches for compliance, monitoring techniques, and policy development.

Keywords: billing compliance, HIPAA

Introduction

Medical coders, compliance auditors, and appeals staff often face challenges with varying health plan requirements at one time or another. For example, imagine a perfectly coded health insurance claim: it is compliant and accurately depicts the services provided to the patient. However, the health plan will only accept the claim without a particular American Medical Association Current Procedural Terminology® (CPT®) modifier that was originally appended. Maybe the health plan (ie, insurance company) requires an entirely different CPT® code or may not follow the reimbursement policies in Medicare’s National Correct Coding Initiative (NCCI).1 While this can add unwanted complexity for those committed to coding and billing compliance, it is imperative that there is an understanding of why differing guidelines exist in the first place, and how one should navigate those going forward.

An Overview of Differing Guidelines

There are two areas where a coder or auditor may encounter differing payer guidelines: 1) within the payers’ own requirements for code selection (eg, ICD-10, CPT®), which involves the assignment of codes that represent the services provided to the patient and 2) the insurance company’s rules for payment and reimbursement of the service. Insurance companies have different guidelines for code selection and rules for payment because each company has a different population of members with different risks and each member will utilize healthcare resources differently. In evaluating their own risk pool, the insurance companies’ allowance to formulate their own guidelines is often a cost-containment strategy. After the billing entity submits their claim according to the payer requirements for code selection, the payer makes their own coverage decision, according to their conditions of participation and payment (eg, medical policies).2 The payer then adjudicates the claim and makes payment for services that are reimbursable according to policy. For instance, the concepts of NCCI become applicable at this point, if incorporated by the payer. To aid in understanding why these differing payer guidelines for code selection and reimbursement rules exist, it is necessary to begin with the Health Insurance Portability and Accountability Act of 1996 (HIPAA).3 Before HIPAA was enacted, there was a variety in the standards that insurance companies had for the format, content, and even the code sets submitted to them. This forced health care providers to conform to a wide range of formats for payments via electronic claims submission.3 Conforming to multiple standards made for a slow and costly process. As noted in the Department of Health and Human Services’ CY 2000 Final Rule, a 1993 Lewin-VHI research study found that administrative costs were 17% of the total healthcare expenditures and HIPAA standards implementation would purportedly save billions of dollars.4 The potential cost savings and privacy security needs propelled the HIPAA rule further along.

The HIPAA regulations are comprised of five different Titles. Title II, Preventing Health Care Fraud and Abuse; Administrative Simplification; Medical Liability Reform, directly impacts the code sets utilized today.5 When HIPAA was initially enacted by Congress in 1996, the secretary for Health and Human Services (HHS) had 18 months to adopt the administrative simplification standards.4 Today, the adopted regulations and standards are found in Title 45 of the Code of Federal Regulations (CFR) Parts 160 and 162.4 The administrative requirements of the regulation instruct covered entities (like health care providers) in the way they communicate with other covered entities (like health plans). As defined by the rule, each entity is to use the ICD, CPT®, HCPCS, and CDT code sets.4

Flexibility Still Persists

Insurance companies have flexibility because the code set, as defined by the rule, includes the codes themselves and the descriptor but not the guidelines for correct code application or code usage. In the Final Rule, a few commentors asked for guidelines and instructions applicable to code sets in the maximum defined data set.4 While HHS could agree that standardization of the code set guidelines would be beneficial, after their review, they found that there were many practical barriers to standardization at the guideline level.4 Barriers included a variation in the level of detail and completeness of guidelines between the code sets. HHS also noted that for some code sets, there could only be limited participation in the development of coding guidelines.4 As a result, the only guidelines they could adopt were the Official ICD-9-CM and ICD-9-PCS Guidelines for Coding and Reporting.4 Ultimately, the maximum defined data set included the code sets, but not any other operational guidelines or instructions.4 The resulting time spent complying with varying operational guidelines and instructions is part of the estimated $200 billion dollars spent annually on administrative functions in US healthcare.6

Emerging Technology

In the absence of standard operational guidelines and instructions surrounding code use, there is a unique opportunity to leverage emerging technology such as artificial intelligence (AI) for coding and billing compliance. For instance, AI could be used to prompt a coder or compliance professional to evaluate a particular insurance company’s coding guidelines, instruction, or policy. AI algorithms could efficiently analyze payer policy or coding guidelines and improve compliance and effectively decrease denials. Under much scrutiny from congress and consumers alike, insurance companies are already utilizing AI to help evaluate prior authorizations and also to approve or deny claims.7 Some of the scrutiny insurance companies have faced regarding their “automated decision-making tools” comes from the lack of transparency and inappropriate denials.8 One of the US’ largest insurers, Cigna, was able to deny hundreds of thousands of claims in only two months, spending an average of only 1.2 seconds on each case.9 When done correctly, with appropriate human checks and balances, it is reasonable to consider how AI could be used to ease the process of compliant coding. An emphasis on transparency could create an even better AI product for coders. For example, if insurance companies are required by regulation to be more transparent in how their AI decisions are made, that information could become available to incorporate into a software system for compliance functions. If AI could incorporate insurance policies and guidelines into coding software, this could certainly bring an impactful and measurable benefit.

Volume, Variation, and Solutions

Adapting to guidelines for coding that vary from payer to payer leaves a coder or compliance professional in a difficult situation as they adhere to their professional ethics. According to the American Health Information Management Association’s Standards in Ethical Coding, coders are to “apply accurate, complete, and consistent coding practices that yield quality data.”10 In an environment where coders are measured by their productivity, such as notes or charts coded per day, how should one achieve consistency with the pressure of high volume and varying guidelines?

There are some possible solutions to consider as a coder or compliance professional:

  • Review health plan policies, provider manuals, and agreements. While not always easy to find quickly, organize these electronic sources when located, so they are readily accessible. The goal is to code accurately and follow the health plan guidelines consistently in accordance with contracts.

  • Log variances on something as simple as an Excel® (Microsoft, Inc; Redmond, Washington) spreadsheet. This can be organized by health plan, shared with your team, and updated as they change.

  • Monitor denials, appeals, and share variances in coding expectations during department meetings.

  • Utilize internal contract management teams and external provider representatives when necessary.

  • Document details and coding direction from any verbal conversation with health plans. Include the name, date, title, reference number, and any contact information. Ask for the written policy so that it’s readily accessible for the present issue and for the future.

  • In those cases where a payer has not adopted code selection rules such as CPT® Editorial Panel rules or Medicare’s Coding Determination rules (which also references CPT® coding guidelines), seek clarification from the payer.11 If the payer does not provide direction, craft an internal policy that includes your entity’s best practice standards. Perhaps incorporating Medicare’s Program Integrity Manual rules for code selection may be prudent.11

  • As a coding auditor, identify the purpose of the audit. It is important to establish whether the goal of the audit is to assess compliance risk or to conduct a forensic audit for declaration of an error. In the former, generally accepted guidelines such as CPT® Assistant may be employed to gauge overall risk of overpayment/underpayment.12 However, a forensic audit will require an objective review according to the binding standards within payer agreements/contracts. It is important to avoid interjecting non-incorporated coding guidelines into a forensic audit.12 As established earlier, payers are not required by the HIPAA regulations to follow (incorporate) all the guidelines that might be familiar to a coder or auditor.

While the root of frustration for a coder or compliance professional lies in adapting to the variation in payer expectations, health plans are well within HIPAA regulations to choose which guidelines are applicable and are present in their binding agreements with providers. The flexibility that health plans have, as it pertains to the application of coding guidelines, doesn’t necessarily aid a coder in their own personal, administrative simplification; however, coders and auditors can equip themselves by becoming familiar with the contracted payer’s policies and expectations.

Disclosures

The author has nothing to disclose. The analysis and opinions expressed are those of the author and do not necessarily reflect the views, policies, or opinions of the author’s employer.

Acknowledgments

The author is sincerely thankful to Michael D. Miscoe, Esq., CPC, CASCC, CUC, CCPC, CPCO, CPMA, CEMA, FCE, AAPC Fellow, for his contributions and generous response to questions as well as Hailee Domash for her work editing this article.

Funding

The author received no funding for this research.

Funding Statement

The author received no funding for this research.

References


Articles from Advances in Health Information Science and Practice are provided here courtesy of American Health Information Management Association

RESOURCES