Blog

    eClinicalWorks Denial Appeals

    By GauravNovember 4, 20268 mins read
    On this page

    eClinicalWorks practices see denials arrive the same way every practice does: as adjustment codes on an electronic remittance. What happens next decides whether the money is recovered. Some practices work every denial within days; others let them age until appeal deadlines pass.

    This guide covers how denial information reaches eClinicalWorks, what the codes mean, how to organize denial work, Medicare's appeal deadlines, what goes into a strong appeal, where AI helps and how to stop the same denials from coming back.

    What is denial and appeal management in eClinicalWorks?

    Too many denials to work?

    Agnotic builds AI denial management that classifies denials, drafts appeals and feeds prevention rules back into billing.

    Denial and appeal management in eClinicalWorks is the process of identifying denied or underpaid claims from electronic remittances, sorting them by cause, correcting and resubmitting what can be fixed, appealing what was wrongly denied within each payer's deadline, and changing upstream workflows so the same denials stop recurring.

    eClinicalWorks provides the practice management and billing tools, and the company also offers revenue cycle management services. Whether a practice works denials in-house, through eClinicalWorks or through a billing company, the principles are the same.

    Denials are not all equal. A rejection from the clearinghouse never reached the payer and only needs a fix and resubmission. A denial was adjudicated and needs either a corrected claim or a formal appeal. An underpayment was paid, but not in full. Each needs a different workflow, and mixing them in one queue slows everything down.

    How does denial information reach the practice?

    Denial information arrives in the electronic remittance advice, the X12 835, which the billing system posts against the original claims. Each adjustment carries a group code, a claim adjustment reason code and often a remittance advice remark code.

    • ERA posting: Payments and adjustments posted automatically to claims, with exceptions flagged for review.
    • Zero-pay claims: Claims paid at zero are denials and should be routed to work queues, not just posted.
    • Partial payments: Lines paid below expectation may be underpayments rather than denials.
    • Paper remittances: Payers that still send paper need manual entry, which delays denial work.

    Check that every denial lands somewhere visible. A denial that is posted but not routed to a queue is the most common way practices lose money they could have recovered.

    What do group codes and reason codes tell you?

    Group codes show who is responsible for an adjustment, and claim adjustment reason codes, maintained by X12, show why. Together they decide what action to take.

    • CO, contractual obligation: The provider bears the amount and cannot bill the patient for it.
    • PR, patient responsibility: The amount may be billed to the patient, such as deductibles and copays.
    • OA, other adjustments, and PI, payer-initiated reductions: Adjustments that fit neither of the above.
    • CARC 16: The claim lacks information or has submission or billing errors; X12 notes that at least one remark code must be provided.
    • CARC 45: Charge exceeds the fee schedule or contracted amount, usually an expected reduction.
    • CARC 50: Non-covered services because the payer does not deem them a medical necessity.
    • CARC 197: Precertification, authorization or notification absent.

    Route denials by code. CARC 16 usually means fix and resubmit, CARC 197 means check authorization records, and CARC 50 usually means a clinical appeal with documentation.

    Remark codes add the detail. The same reason code can mean a missing modifier on one claim and a missing referring provider on another, and only the remark code tells them apart. Routing rules should read both.

    How should denials be worked in queues?

    Denials should be worked in queues organized by cause and payer, prioritized by value and deadline, and assigned to staff with the right skills. eClinicalWorks describes work queues as part of its revenue cycle offering.

    • By cause: Front-end errors, coding issues, authorization, medical necessity and timely filing in separate queues.
    • By deadline: Claims closest to their appeal or corrected-claim deadline at the top.
    • By value: High-dollar claims prioritized, with low-value claims batched.
    • By skill: Coders for coding denials, authorization staff for authorization denials, clinicians for medical necessity.
    • By payer: Payer-specific rules and contacts grouped for efficiency.

    Set a target for how quickly a new denial is first touched, such as within a few working days of posting. Denials that are worked early have the full appeal window available, the clinical details are fresh, and any pattern is caught before the same error repeats on hundreds of claims.

    Each denial record should carry its history: who worked it, what action was taken, what was sent and when the payer responded. Without that trail, staff repeat each other's work and managers cannot tell which actions succeed.

    What are Medicare's appeal deadlines?

    For Medicare Part A and B claims, the first level of appeal is a redetermination by the Medicare Administrative Contractor. Under 42 CFR 405.942, the request must be filed within 120 days of receiving the initial determination, and receipt is presumed to be 5 days after the date of the notice unless shown otherwise.

    Commercial payers and Medicaid programs set their own deadlines in contracts and manuals, often shorter than Medicare's. Store each payer's appeal and corrected-claim limits in the system and calculate the deadline for every denial as soon as it posts. eClinicalWorks describes an alerts dashboard for timely filing in its revenue cycle materials, and whatever tool is used, the deadline should be visible on every denial record.

    • Redetermination: The first Medicare appeal level, decided by the contractor that processed the claim.
    • Later levels: Reconsideration by a qualified independent contractor, then further levels if the amount in controversy is met.
    • Reopenings: Simple clerical errors can often be fixed through a reopening rather than a formal appeal.
    • Commercial appeals: Internal appeal levels set by the plan, sometimes followed by external review.

    What goes into a strong appeal packet?

    A strong appeal packet states clearly what is being appealed and why the denial is wrong, and includes the evidence that proves it: the claim, the remittance, the relevant records and the payer policy or contract clause.

    • Cover letter: Patient, claim number, date of service, denial reason and the specific request.
    • Argument: Why the service meets the payer's policy, citing the policy by name and section.
    • Clinical records: Notes, orders, results and authorizations that support the service.
    • Claim and remittance: Copies of the original claim and the denial.
    • Contract terms: For payment disputes, the clause and the calculation of the correct amount.

    Templates per denial type save time, but each letter must address the specific claim. Generic letters that do not engage with the denial reason are rarely successful.

    Where can AI help with eClinicalWorks denials?

    AI can classify denials, predict which are worth appealing, assemble records and draft appeal letters for staff to review. eClinicalWorks says its revenue cycle services use AI to help build appeal packets, and practices can add similar tools through integrations.

    • Classification: Read reason and remark codes plus claim data to assign the right queue and action.
    • Prioritization: Estimate the chance of success and the value recovered for each denial.
    • Record gathering: Pull the relevant notes, orders and authorizations from the chart.
    • Drafting: Prepare a letter that addresses the denial reason, for a person to review and sign.
    • Pattern detection: Spot denial trends by payer, code or provider before they grow.

    Keep a person in the loop for every appeal that goes out. AI-drafted letters should be checked against the record, because an appeal that misstates the facts damages the practice's credibility with the payer. Track overturn rates for AI-drafted and staff-written appeals separately, so the practice knows whether the tool is helping.

    How do you prevent repeat denials?

    Prevent repeat denials by tracing each denial category back to the step that caused it and fixing that step, whether it is registration, eligibility, authorization, coding or charge entry.

    • Eligibility: Verify coverage before every visit, not just the first one.
    • Authorization: Check authorization requirements at scheduling and block services without them.
    • Coding: Add claim scrubber rules for common coding denials.
    • Registration: Validate demographics and subscriber details at check-in.
    • Feedback: Share monthly denial reports with front desk, coders and clinicians.

    Each prevention rule should be measured. If a new scrubber rule does not reduce the matching denial within a couple of months, revisit it.

    Prevention also needs payer policy updates. Payers change coverage and authorization rules through bulletins and policy updates, and a practice that tracks those changes for its main payers can adjust scheduling and claim rules before the first denial arrives.

    What should a denial dashboard show?

    A denial dashboard should show the denial rate, the top reasons, the value at risk, the deadlines coming due and the success rate of appeals, by payer and over time.

    • Denial rate: Denied claims as a share of submitted claims, by payer.
    • Top reasons: The most frequent and most costly CARC and RARC combinations.
    • Aging: Open denials by age and by days left to appeal.
    • Appeal outcomes: Overturn rates and amounts recovered by denial type.
    • Staff workload: Open denials per person and average time to first touch.

    Review the dashboard monthly with billing, front desk and clinical leads together. Denials usually start outside the billing office, so the people who can prevent them need to see the numbers too.

    Compare payers against each other. If one payer denies a code that others pay without question, the problem may be the payer's policy or system, and the right response is a conversation with provider relations rather than another round of individual appeals.

    How Agnotic can help

    Agnotic Technologies builds AI denial management for clients, including those using eClinicalWorks: denial classification from 835 data, priority scoring, record assembly, draft appeal letters for staff review and denial dashboards.

    Agnotic connects these tools to the practice management system and clearinghouse, and feeds denial patterns back into eligibility, authorization and claim scrubbing rules so fewer denials happen in the first place.

    Recover more from denials

    Explore Agnotic's AI claims denial management, or browse the revenue cycle hub.

    Related reading on Agnotic

    Continue with medical coding automation, revenue cycle management, AI claims processing and payer contract management.

    Sources

    Frequently Asked Questions

    A redetermination request must be filed within 120 days of receiving the initial determination, with receipt presumed 5 days after the notice date, under 42 CFR 405.942.

    Talk to an engineer about your project

    We help practices and billing companies classify denials, draft stronger appeals and stop repeat denials at the source.

    Go deeper

    Services and solutions on this topic