Medical coding and billing software encompasses several distinct functional layers: charge capture, code assignment, claim editing, and revenue cycle workflow management. The supplied documentation shows no single universal definition. The VA Integrated Billing package focuses on patient billing, third-party billing, and insurance data capture within a federal facility [1]. Amazon Connect Health positions medical coding as an asynchronous point-of-care agent for ICD-10-CM and CPT generation [2]. athenaOne Medical Coding is a contracted service for ambulatory practices, with explicit routing and fee schedule requirements [3]. AdvancedMD and MediMobile describe coding and charge capture tools aimed at practices and health systems [7][8]. Each product imposes different workflow constraints, and the buyer's task is to match those constraints to existing operational and technical realities.

Workflow Boundaries Define the Software

The VA Integrated Billing package illustrates how deeply coding and billing functions can be tied to facility operations. Patient billing options update retroactive award periods, link Community Care Long Term Care charges to Patient Treatment File entries, and warn users when security keys are missing [1]. Third-party billing automates forms such as UB-92 and HCFA-1500, allowing entry, editing, authorizing, printing, and cancellation of bills [1]. Insurance data capture stores multiple carrier addresses, including outpatient claims, inpatient claims, prescription claims, appeals, and inquiries, and supports group plans pointed to by patient policies [1]. These features are not generic; they reflect VA-specific enrollment, community care, and site parameter structures. A private practice evaluating software for ambulatory coding would not encounter the same PTF linkage or Medal of Honor copayment cancellation context, but the underlying lesson applies: coding software is rarely separable from the billing and enrollment systems that feed it.

Amazon Connect Health describes a narrower boundary. Medical coding is a point-of-care agent integrated through two asynchronous APIs, StartMedicalCodingJob and GetMedicalCodingJob, and does not require a contact center [2]. It is a gated preview in US East (N. Virginia) and US West (Oregon) Regions, so it should not be used in production environments [2]. The software generates ICD-10-CM codes for documented diagnoses and CPT codes for procedures and services, with modifiers, E/M level, and supporting evidence [2]. It does not support inpatient facility coding such as ICD-10-PCS procedure codes or DRG assignment [2]. This boundary is explicit: the service is optimized for primary care office and telehealth encounters coded with E/M services, while other specialties may be submitted but may be less accurate and require particular review [2]. Buyers must determine whether their encounter mix fits that documented scope.

Contracted Coding Services Introduce Operational Prerequisites

athenaOne Medical Coding is not a standalone software license but an add-on service for ambulatory practices using athenaOne Base or athenaCollector plus athenaClinicals [6]. The service description applies only to clients who sign an athenahealth services agreement for Medical Coding [3]. Several prerequisites are explicit. Track Missing Slips must be enabled for every active provider; if Missing Slips are not enabled, Medical Coding has no knowledge of visits performed and claims must be manually created [3]. If auto-checkout is not selected, the practice must manually check each patient out before auto routing can pick up a visit [3]. Automated routing is only compatible with standard appointment workflows; practices using Expedited Encounter or Appointment Workflow Bypass must use manual routing [6]. These requirements show that even a service positioned as outsourced assistance still depends on internal practice configuration decisions.

The division of responsibility is also documented. athenahealth will provide supported procedure, evaluation and management, and diagnosis coding with appropriate modifiers, but medical coding excludes specialized or non-standard coding such as MIPS, CPT II codes, customer-specific directives, or payer contracts [6]. The practice completes a Practice Directive and is responsible for updating it when practice setup or billing changes [3]. Fee schedules with non-reimbursable CPT II codes must not exceed payer required amounts, or athena Onboarding will alter the values to match payer requirements [3]. Each visit routed for coding must be individually evaluated for accuracy and completeness prior to sending, unless an auto route product request is made during onboarding [3]. A team member holding an AAPC or AHIMA certification performs or reviews all medical coding before claims are submitted [6]. These are contractual and workflow obligations, not optional features.

A Starting Point for a Parallel Pilot

A small facilitation can be run without buying either full product, provided access terms allow it. Select a fixed set of, for example, 50 primary care office and telehealth encounters with signed and closed notes. Route the same de-identified sample through the API coding job workflow, where the application requests StartMedicalCodingJob and retrieves results via GetMedicalCodingJob [2]. For the contracted service route, enable Track Missing Slips for every active test provider and use manual routing or standard appointment auto routing to send visits via the Send to Coding button [3][6]. Record whether each suggested code carries documentation evidence, whether diagnosis and procedure codes are linked as submitted on a claim [2], and whether the claim passes available payer edit checks without vendor-specific claims [7]. Compare coder review time and override decisions. Treat results as process observations, not as efficacy proof. Without a documented contract and a production-stage evaluation, no conclusion about reimbursement improvement or denial reduction is justified.

Claim Editing and Code Lookup Are Different Decision Points

AdvancedMD describes its medical billing software as including ICD-10, HCPCS, and CPT code sets, with updates managed centrally as code organizations release additions, removals, and revisions [7]. The proprietary AdvancedMD Claims Inspector checks every claim against industry guidelines including LCD, NCD, CCI, HIPAA, and LMRP edits, and reviews payer-specific rules [7]. The vendor also cites an American Medical Association industry report that as many as 5 percent of claims are denied after first submission, and states that as many as half of those claims are never resubmitted because staff are focused on processing new claims [7]. This is a vendor-cited statistic, not a claim supported by primary AMA documentation in the public documents. A buyer can treat it as directional vendor messaging, not as a validated denial rate for any particular specialty or geography.

The claim editing layer is distinct from the code lookup layer. Code lookup addresses whether a coder can find the correct ICD-10, HCPCS, or CPT code; claim editing addresses whether the assembled claim meets payer requirements, medical necessity logic, provider identifier rules, and grouping or sequencing edits before submission [4][7]. The VA RFI is explicit about this separation. It requests configurable workflows for coding, clinical documentation integrity, billing, utilization review, compliance, and supervisory functions, and asks for institutional and professional claim review before and, where needed, after submission [4]. It also requests transparent edit explanations, configurable messages, and authorized maintenance of custom rules, plus identification of incomplete, duplicate, non-billable, held, cancelled, retrospective-insurance, and same-day related encounters [4]. A software evaluation that treats all of these as one module will miss the distinction between a coder's workbench and a billing compliance queue.

A Specific Hypothetical Evaluation Example

As a suggestion rather than a tested scenario, consider a multi-site ambulatory group deciding between an API-based coding service and a contracted coding add-on. The group documents primary care and telehealth visits with E/M services, uses standard appointment workflows, and wants code generation integrated into a custom application. Under the documented scope, Amazon Connect Health supports primary care office and telehealth encounters coded with E/M services, offers asynchronous APIs, and does not require a contact center [2]. But it is a gated preview, restricted to two US regions, and should not be used in production environments [2]. That alone would likely disqualify it for a production rollout at review time. athenaOne Medical Coding can support ambulatory coding if the practice uses compatible athena products, enables Track Missing Slips, and operates standard appointment workflows [3][6]. If the group uses Appointment Workflow Bypass, automated routing is not compatible [6].

The example isolates two unknowns that generic buyer guides ignore. First, the API-based service's accuracy for the group's specific payer mix and note style is not established in the public documents; the documentation says specialties outside primary care may be less accurate, but it provides no quantitative benchmark for the group's specialties [2]. Second, the contracted service's turnaround and backlog expectations depend on onboarding communications and the practice's own routing behavior; the two business day goal applies to new work, while backlog will not be completed in the same goal [3]. Without a documented pilot using their own de-identified encounters, the group cannot compare denial or correction rates. The correct step is a parallel test with both vendors against a defined encounter sample, measuring code acceptance, coder override rate, claim readiness, and documentation evidence quality, all of which remain unknown from the public documents.