A practice runs claims in athenahealth. When a payer rejects a charge, the agent that proposes a fix needs a place to record the rationale, the CPT or ICD-10 edit it suggests, and which biller approved the resubmission. Dock holds that row. athenahealth holds the claim. The two records point at each other, and the history survives staffing changes, payer disputes, and downstream questions from the healthcare operations team.
Healthcare data is sensitive. Hold any tool, Dock included, to your own HIPAA policies and your compliance team's review before you connect clinical systems.
athenahealth and Epic stay the system of record for the claim itself, the encounter, the patient chart, and the remittance. Dock holds the work around it: what the billing agent interprets from that data and who approved it. Each Dock row carries athena_claim_id (or epic_claim_id for Epic-integrated practices), the agent, the proposed correction, the human reviewer, and a timestamp. When the biller needs current claim state, they check athenahealth directly rather than trusting a stale snapshot in Dock.
The Dock surface: claim_review_queue
| athena_claim_id | denial_code | agent_rationale | proposed_edit | reviewer | status |
|---|---|---|---|---|---|
| ATH-884217 | CO-11 (dx not consistent with procedure) | Encounter note supports 99214; original coding used 99213. AAPC guidance on E/M level selection points to MDM complexity here. | Resubmit as 99214 with modifier 25 | k.nguyen@practice | approved |
| ATH-884301 | CO-97 (bundled service) | 36415 is bundled into 80053 per payer policy. No separate reimbursement available. | Write off $18.00 | s.alvarez@practice | approved |
| ATH-884355 | CO-16 (missing referral) | Referral on file in athena under prior auth ATH-PA-44219. Not attached to claim line. | Attach PA-44219, resubmit | pending | awaiting_review |
Three rows. Each one points back at an athenahealth claim and forward at a human who took responsibility for the decision.
A worked workflow
Each morning, a biller exports the daily denial report from athenahealth with the practice's own access and brings it into Dock. For each denial, the agent works through the encounter details, the payer's policy, and the relevant coding guidance. It writes one Dock row per denial with its proposed action and rationale. A biller opens the queue, reviews the row, and either approves the resubmission, requests a revision, or rejects it. After approval, the biller makes the correction and resubmits in athenahealth, then records the resubmission ID on the Dock row and closes it. The practice's rule is simple: no edits in athenahealth without an approved Dock row, which makes agent audit and compliance reviews straightforward.
Why this matters
Practice-management software treats a claim as a single object with a status field. That object cannot hold the reasoning that produced a resubmission, the alternate codes the agent considered, or the biller who signed off. When someone asks why a code changed, the answer lives in a free-text note or, more often, nowhere. Dock gives that reasoning a row.
It also closes the attribution gap. A shared login tells you nothing about which agent ran which logic on which claim. With agent identity attached to every row, the practice can answer the question "who decided this" for any line item, going back as far as the rows exist.
The same pattern carries to the practice's books. Write-offs and resubmitted balances can be tracked on the same attributed surface the controller already uses for Dock for accounting work, so revenue cycle and ledger reconcile against the same evidence.
Start with the healthcare operations pillar and the compliance overview to see how the pieces connect.
FAQ
Does Dock change codes inside athenahealth? No. The agent proposes the edit in a Dock row. A human biller approves it, then makes the change in athenahealth with the practice's own access.
What if athenahealth and Dock disagree on claim status? athenahealth is the source of truth for status. Check it before acting. Dock rows record what the agent saw and proposed at a given moment, not the current claim state.
Does this work for Epic-integrated practices too?
Yes. The row swaps athena_claim_id for epic_claim_id, and the team pulls denials from Epic instead. The rationale, the reviewer, and the history in Dock work the same way. See agent identity for how one agent's work stays attributable across both.
What standards back the agent's coding decisions? AAPC publishes the CPC certification standards and coding guidance the agent cites in its rationale (AAPC certifications). Volume context for U.S. practices comes from the AHA's annual hospital survey, which tracks 6,100 hospitals and over 35 million admissions (AHA Fast Facts).