Medical billing and coding practice software is not one category but three overlapping tool types that attach to different points in a revenue cycle. Separate product designs exist for code lookups and compliance checking, for charge capture inside a broader payer-facing platform, and for government facility accounting that passes charges to accounts receivable. The operational split matters because a tool that speeds coding does not automatically submit claims, while a practice management suite may outsource coding review through a defined service boundary. Reading primary documentation from AAPC, athenahealth, the Department of Veterans Affairs, and a public-sector market research notice shows which workflows each system covers and where decision-making still belongs to a person.

Decision support versus claim submission

Codify by AAPC is described as a decision-support system for healthcare revenue work that combines guidance, search tools, and code-set updates without replacing core systems [1]. It is purpose-built for the interpretive work that happens before a claim is generated. AAPC documentation lists natural-language search across CPT, ICD-10-CM, HCPCS, modifiers, and guidance simultaneously, plus built-in filters and direct links to full code details [1]. The product page also describes AAPC-built crosswalks between ICD-10-CM, CPT, HCPCS, DRGs, revenue codes, and modifiers for translating diagnoses to procedures or reviewing DRG impacts [1]. The same page lists a CMS 1500 real-time scrubber and an NCCI edits checker as validation features [1].

In contrast, athenaOne's medical billing and practice management description presents AI-powered charge capture and claim follow-up within a broader suite. Athenahealth states that one-click E&M and CPT coding is informed by documentation, orders, and practice rules [2]. The vendor also markets automated claim scrubbing, claim alarms, and denial advice that explain likely issues and recommend next steps [2]. These are different moments: Codify's scrubber and NCCI edit checker address pre-submission validation from a coder's workbench context [1], while athenahealth's follow-up language points at downstream claim workflow inside practice operations [2]. The documentation does not establish whether either vendor's accuracy claims have been independently validated.

The service boundary in a hybrid coding model

Athenahealth publishes a Spring 2026 service description for athenaOne Medical Coding that separates what the vendor performs from what the practice must complete [4]. Certification is a documented constraint: all medical coding is performed or reviewed by a team member holding an AAPC or AHIMA certification before claims are submitted to payers [4]. The service excludes specialized coding areas including MIPS, CPT II codes, customer-specific directives, and payer contracts [4]. The same document requires Track Missing Slips to be enabled for every active provider; without it, Medical Coding cannot detect visits and the practice must create claims manually [4].

The routing sequence defines where human action is unavoidable. A claim is not created until a coder selects Coding Complete, and submission then follows only if no other holds prevent the claim from being sent [4]. The user guide adds billing integrity conditions such as a signed and closed encounter and completed billing tab review before automated routing can pull a missing slip [6]. This makes the boundary explicit: athenahealth's coders assign codes, but the practice owns documentation sign-off and billing configuration. Codify does not document an equivalent outsourced coding service; its materials describe shared notes, favorites, and workflows for internal consistency across locations and teams [1].

A simple pre-selection audit for one encounter

Take one unsigned encounter and test the failure behavior across the products you are evaluating. In athenaOne, a missing slip that has not been signed and closed fails a billing integrity check and appears under Unmet Criteria for Medical Coding on the Workflow Dashboard [6]. In Codify, the comparable question is whether a code selection passes an NCCI edit check, a separate validation moment from encounter sign-off [1]. In Integrated Billing, the audit question is whether a bill reaches the authorized state for form generation and accounts receivable handoff, with security key requirements documented for certain actions [3].

Record two facts for each system: which artifact is produced at the failure point, and which person can resolve it without vendor support. The public documentation only fully documents the athenahealth resolution table, which lists actions such as completing billing tab review, adding a supervising provider, or ensuring provider encounter sign-off [6]. For the other systems, mark the resolution ownership as unknown unless primary documentation specifies it. This audit is a workflow test, not an accuracy benchmark; it shows how much operational friction lives inside the software versus in your own clinical or administrative processes.

Government billing systems as a separate problem

The Veterans Affairs Integrated Billing package illustrates a third category, closer to an accounting subsystem than a commercial coding tool. The September 2026 user guide states that Integrated Billing moved from identifying billable episodes and creating bills to a package responsible for the whole billing process through passing charges to Accounts Receivable [3]. It includes patient billing and third-party billing modules, plus insurance data capture for verifiers and billing clerk functions [3]. Third-party billing automates creation of forms including HCFA-1500 and UB-92, with entry, editing, authorizing, printing, and canceling of bills [3].

The same documentation shows a system shaped by federal benefit rules rather than payer negotiation. One revision discusses enrollment priority group determinations for urgent care charges, community care long-term care linkage to patient treatment file entries, and a pandemic response cancellation reason [3]. A VA request for information dated October 23, 2026, with a November 6, 2026 response deadline, describes a future acquisition for an enterprise, modular, cloud-based system supporting coding, clinical documentation integrity, billing, utilization review, compliance, and supervisory functions [7]. The RFI asks for tamper-evident audit history, configurable work queues, and edits for medical necessity, provider identifier, present-on-admission, grouping, and sequencing [7]. That requirement set is enterprise governance work, not a small-practice tool purchase.

A hypothetical evaluation with three artifacts

A concrete evaluation exercise can reveal category fit without vendor scorecards. One suggested prompt is to run the same encounter through three workflows: a Codify code lookup and NCCI edit check [1], an athenaOne manual routing scenario in which a missing slip fails because the encounter is unsigned [6], and an Integrated Billing third-party bill form generation scenario using its HCFA-1500 workflow [3]. Each artifact differs: a code set with edit flags, a blocked routing status with unmet criteria, and a bill template passed to accounts receivable. No single document in the public documentation shows all three outputs for the same patient record, so the comparison would need to be assembled from separate system tests.

The evaluation should record unknowns. Amazon Connect Health's medical coding documentation, a gated preview, states that its feature is optimized for primary care office and telehealth E/M encounters and that other specialties may be less accurate [8]. It also says inpatient facility coding such as ICD-10-PCS and DRG assignment is not supported [8]. These scope limits are documented for that agent, not for the other products. Whether Codify's AI-powered Codie assistant or athenahealth's Express Coding performs equivalently for specialty documentation is not established in the retrieved pages. A defensible evaluation should mark those comparisons as untested rather than filling the gap.

Where scoring metrics do not exist

Vendor materials carry ratings that should be treated as claims, not evidence. Athenahealth states it was named Best in KLAS 2026 for Practice Management, 11-75 Physicians, Independent, for the fourth straight year [2]. The page adds a footnote that a cited customer's results reflect one practice and are not necessarily what every customer should expect [2]. AAPC's materials say Codify is built by an organization trusted for more than 35 years in coding education and certification [1]. Neither statement establishes comparative coding accuracy, denial reduction rates, or reimbursement gains for a specific practice profile.

The VA RFI is the clearest illustration of requirements that go beyond vendor marketing. It requests reporting at enterprise, regional, facility, workgroup, and user levels with auditable metrics, plus support for large user populations without per-user barriers [7]. The notice also asks respondents to identify which capabilities are commercially available today, which have planned delivery dates, and which would require VA-funded development [7]. This explicit request for a capability gap list is a more rigorous procurement question than a feature brochure typically answers. A practice evaluating commercial tools could adopt the same discipline: ask the vendor to separate shipped features from planned ones and to identify integrations that would require customer-funded work.