Coding and revenue cycle management (RCM) are distinct but interdependent functions. Medical coding extracts billable information from clinical documentation, while RCM manages the financial lifecycle from scheduling to final payment. The two converge at charge capture, where codes become claims. This guide explains the concrete workflows, the regulatory and standards context, and the metrics used to measure performance. It also provides a hypothetical evaluation example for a healthcare organization considering technology to support these functions. The focus is on primary documentation and clear unknowns, not vendor claims or clinical outcomes.

The Coding and RCM Workflow

Revenue cycle management begins when a patient schedules an appointment and ends when the account balance is resolved through reconciliation of insurance payments, contractual adjustments, write-offs, or patient payments [7]. The workflow includes appointment scheduling, registration, charge capture, billing, and denial management [7]. HFMA describes RCM as the process used by healthcare systems to track revenue from initial encounter to final payment, including communication with patients, insurance companies, and government payers [4]. Each step depends on accurate data from the previous step.

Medical coding is a distinct activity within this cycle. AAPC explains that coding involves extracting billable information from the medical record and clinical documentation, while billing uses those codes to create insurance claims and patient bills [7]. The AMA guide describes a typical flow: physicians complete documentation in the EHR, select CPT codes, and close the chart; administrative staff then review the documentation and codes for concordance [2]. If a misalignment is identified, staff may send a query to the clinical team requesting additional information [2].

Standards and Code Sets

HIPAA requires HHS to establish national standards for electronic transactions, applying to health plans, clearinghouses, and providers who conduct electronic transactions [5]. The adopted standard format for most transactions is ASC X12 Version 5010, with exceptions for retail pharmacy transactions using NCPDP standards [5]. These standards govern the electronic exchange of claims and related transactions, not the clinical content of the codes themselves.

The adopted code sets are specific to the type of service. Diagnosis coding uses ICD-10-CM, hospital inpatient procedure coding uses ICD-10-PCS, outpatient procedure and physician services coding uses CPT, supplies not included in CPT use HCPCS, and dental procedure coding uses CDT [5]. This distinction matters for technology evaluation: a system must support the code sets relevant to the organization's service mix. The VA's RFI for coding optimization software, for example, requires support for current diagnosis, inpatient procedure, professional procedure, supply, dental, and other applicable code sets, including effective-date validation and version management [3].

Evaluating a Coding and RCM System: A Specific Example

A hypothetical hospital system evaluating a unified middle revenue cycle platform could structure its assessment around three decision points. First, does the system support the full range of code sets the hospital uses, including ICD-10-PCS for inpatient procedures and CPT for outpatient services [5]? Second, does it provide configurable work queues for concurrent and retrospective clinical documentation review, as the VA RFI describes [3]? Third, does it offer auditable metrics at the enterprise, facility, and user levels [3]? The hospital would then request a demonstration of how the system handles a specific scenario: a patient with multiple diagnoses and procedures across an inpatient stay, where documentation is incomplete at discharge. The evaluation would observe whether the system identifies documentation gaps, supports code assignment, and maintains an audit trail of changes [3]. This scenario is illustrative, not a test protocol, and the sources do not provide evidence of how any specific vendor performs in such a demonstration.

Metrics and Performance Measurement

The AMA guide identifies specific metrics for coding and revenue cycle performance. Coding accuracy is measured as the percentage of codes accurately assigned based on clinical documentation, with a goal of 95% accuracy [2]. Charge capture lag evaluates how long it takes physicians to close charts post-encounter, with same-day closure as ideal and three days as acceptable [2]. First-pass resolution measures the percentage of claims approved on first submission without payer adjustment, with a goal of 95% [2]. Denial volume is tracked as the percentage of all claims denied, with a goal below 10% and 2-3% considered exceptional [2].

AAPC identifies additional benchmarks: point-of-service cash collections, days in accounts receivable, days in total discharged not billed, clean claim rate, and bad debt [7]. HFMA references MAP Keys as publicly available industry-standard metrics for tracking revenue cycle performance using objective, consistent calculations [4]. These metrics are useful for evaluating both current performance and the potential impact of technology changes. However, the sources do not provide comparative benchmarks across organizations, so any baseline must be established internally.

Technology and the Middle Revenue Cycle

The middle revenue cycle encompasses documentation, coding, and charge capture. Optum describes a fractured system where point solutions wrap around a central EHR, creating siloed technological environments [8]. The company's documentation argues for a unified platform that ensures communication between the EHR, coding software, and billing systems [8]. This is a vendor perspective, not an independent assessment, but it identifies a real structural challenge: integration between clinical and administrative data is essential for clinical documentation integrity and charging accuracy [8].

Computer-assisted coding (CAC) is one technology approach. AHIMA's practice guidance notes that CAC implementation requires integrating people, defined processes, and suitable technology tools [6]. The guidance emphasizes that a CAC software implementation will not succeed without upfront identification and commitment of dedicated internal IT, EHR system, and HIM resources [6]. CAC can play a role in the revenue cycle by enabling system convergence, enhancing monitoring of the coding process, and reducing inefficiencies, but the guidance does not quantify these benefits [6].

A Hypothetical Evaluation Framework

Consider a hypothetical multi-specialty physician group evaluating coding and RCM technology. The evaluation would begin with the code sets required: CPT for outpatient procedures and physician services, ICD-10-CM for diagnoses, and HCPCS for supplies [5]. The group would then assess whether the system supports effective-date validation and version management for these code sets, as the VA RFI specifies [3]. The evaluation would also examine whether the system provides configurable workflows for coding, clinical documentation integrity, billing, and compliance functions [3].

The group would then define measurable criteria. Based on the AMA guide, it could set targets of 95% coding accuracy, same-day chart closure, 95% first-pass resolution, and denial rates below 10% [2]. The evaluation would require the vendor to describe how the system supports these metrics, including whether performance data is available in real time [6]. The group would also need to assess integration requirements with its existing EHR and the internal IT resources required for implementation [6]. This framework is a suggestion, not a tested methodology, and the sources do not provide evidence that any specific system achieves these targets.