Inside the Claim Edit Library · Article 3 of 6
What Is the System Looking For?
Consider three questions a billing system might ask about a procedure code.
Is the code valid?
Is it appropriate for the reported date and transaction?
Does it create a problem when combined with another service on the claim?
All three concern the same code, yet each requires a different kind of logic. The first examines a value, the second introduces context, and the third evaluates a relationship.
That progression provides a useful way to understand how claim edits work.
Start With the Value
A basic validation rule compares information against an expected condition.
Required fields must contain information when the applicable transaction calls for it. Identifiers follow defined formatting requirements, and reported codes need to be valid under the relevant code set and date.
These checks address relatively narrow questions.
For example, when a transaction requires subscriber identification, the system can recognize that the corresponding field is blank.
Even a correctly formatted value, though, can be inappropriate elsewhere in the claim. A procedure code must satisfy the coding and billing requirements applicable to the service, beyond its existence in the code set.
Add a Relationship
Some edits evaluate how two or more values interact.
Procedure-to-procedure editing provides a useful illustration. Medicare's National Correct Coding Initiative includes pairs of HCPCS/CPT codes that generally should not be reported together under specified circumstances.
A rule examining these codes must identify the relevant combination and apply the associated requirements, not merely confirm that both codes are valid.
For some NCCI PTP edit pairs, an appropriate modifier can be considered under defined circumstances. Others do not permit that exception. The applicable modifier indicator and supporting documentation determine whether a modifier is justified.
A missing-field check evaluates whether required information exists. Procedure-to-procedure editing examines relationships among reported services, even when each individual value is complete and valid.
Other locally configured rules examine combinations involving provider information, service locations, diagnosis codes, or payer-specific conditions.
The information is evaluated together because its relationship carries meaning that the individual fields cannot convey on their own.
Add Quantity and Scope
Reported units introduce another dimension to claim editing.
One rule could recognize a missing or invalid quantity. Another might evaluate whether the number of units exceeds a threshold associated with a particular service.
Medicare's Medically Unlikely Edits (MUEs) illustrate how the scope of a check influences its outcome. MUE adjudication indicators distinguish how these checks apply. MAI 1 edits are evaluated at the claim-line level, while MAI 2 and 3 edits consider units reported for the same code across the relevant date of service. The indicators also distinguish how exceptions and denials are handled.
An unusually high quantity calls for examination of the documentation and applicable billing requirements. The number alone cannot establish whether the service was reported incorrectly.
These evaluations extend beyond an isolated field, sometimes considering multiple lines, a date of service, or another defined grouping.
Add the Circumstances
Now consider two charges with the same procedure code and service date.
A duplicate-detection rule might flag them as a possible repeated charge.
The answer depends on the underlying records. Separate encounters, documented units, timing, and other service information can help establish whether the charges represent distinct billable activity.
A system can recognize a meaningful similarity without possessing all the evidence needed to resolve it.
Provider enrollment checks, coverage-related conditions, and certain service-specific rules present similar challenges. The available data identifies something worth examining, while the final determination requires additional context.
Some edits identify a definite missing or invalid value. Others identify circumstances that call for further investigation.
Reading the Result More Intelligently
Recognizing what an edit evaluates helps narrow the investigation.
A format error points toward a different review than a procedure combination. A unit limit requires different evidence from a potential duplicate. Missing information can often be addressed through verified records, whereas a coding relationship may require closer examination of documentation and applicable policy.
Employees don't need to memorize every rule in a large library to develop this skill.
Understanding the question behind the check makes an edit message more informative. It reveals what the system evaluated and provides a clearer starting point for determining the next action.
References & Further Learning
- CMS, Medicare NCCI Procedure-to-Procedure Edits
- CMS, Medicare Medically Unlikely Edits
- CMS, Medicare NCCI FAQ Library
About This Resource
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.