Medical Coding Full Guide: Documentation, Codes, and Workflow Examples

Medical coding translates a patient’s clinical documentation into standardized codes that describe the reason for care, the services performed, and, when relevant, supplies or equipment. In the U.S., that usually means using ICD-10-CM for diagnoses and reasons for visits, CPT® for many professional services and procedures, and HCPCS Level II for certain supplies and services.

The essential idea is simple: the code must reflect the record—not fill in what the record does not say. Medical coding supports billing workflows, but it also makes health information more consistent for care operations, reporting, and public health. Under HIPAA, standard code sets classify diagnoses, procedures, tests, treatments, equipment, and supplies. CMS explains the role of these code sets.

This is a high-level U.S. overview, not a coding manual or reimbursement guide. Always use the current official guidance and your organization’s approved compliance process for a live coding decision.

Editorially reviewed: August 2026. This article was checked against the cited CMS ICD-10-CM and HCPCS resources for general educational accuracy. It does not replace current official guidance, organizational policy, or professional coding and compliance review.

In this guide:

• What is medical coding?
• How medical coding works
• ICD-10 vs. CPT vs. HCPCS
• Documentation requirements
• Medical coding examples
• Common documentation gaps
• Coder–clinician collaboration
• Medical coding vs. medical billing
• When to consult official guidance
• Medical coding FAQs
• The takeaway

What is medical coding?

Medical coding is the process of reviewing a healthcare encounter and representing documented information with standardized codes. A coder works from the medical record—not from a menu of the most detailed codes available.

The result lets different healthcare systems interpret the encounter consistently. In plain language, coding helps answer three questions:

• Why did the patient receive care? A diagnosis, symptom, condition, or reason for the encounter.
• What care was provided? A documented service or procedure.
• What else was involved? When applicable, an item, supply, equipment, or additional service.

The point is accuracy. A code does not establish a diagnosis, guarantee coverage, or determine payment by itself. CMS specifically notes that the existence of an HCPCS code does not, on its own, determine Medicare coverage or noncoverage. Read CMS’s overview of coding and classification systems.

How does medical coding work?

The medical coding workflow begins with the encounter and ends with a coded record that can move into downstream clinical, administrative, and reporting processes.

Patient visit → clinician documents care → record is reviewed → codes are assigned under current rules → unclear details are clarified when needed → → coded information supports downstream workflows

In practice, the workflow has two distinct roles:

1. The clinician documents the patient’s condition, assessment, services, medical decision-making, and plan of care. 2. The coder reviews the record and applies the applicable code-set rules and organizational processes.

The official ICD-10-CM guidelines say that a joint effort between provider and coder is essential for complete, accurate documentation and code assignment. They also direct users to review the entire record to determine the reason for the encounter and the conditions treated. See the official ICD-10-CM guidelines.

ICD-10 vs. CPT vs. HCPCS: what is the difference?

These code families describe different parts of an encounter. They often appear together, but they are not interchangeable.

ICD-10-CM is the U.S. clinical modification of ICD-10 used for diagnoses and reasons for encounters across healthcare settings. CPT® is HCPCS Level I and is maintained by the American Medical Association. HCPCS Level II is maintained by CMS and is used primarily for products, supplies, and services not captured in CPT®, such as certain durable medical equipment and ambulance services. CMS’s HCPCS resource explains the two levels.

For a routine office visit, the diagnosis or symptom may be represented by ICD-10-CM and the documented professional service by CPT®. If an eligible item or supply is part of the encounter, HCPCS Level II may also be relevant. The precise approach depends on the setting, service date, and applicable rules.

Medical coding documentation requirements

Clinical documentation is the foundation of the coding process. A coder needs enough information to understand what happened during the encounter and to apply the rules without assumptions.

A clear note usually makes these elements easy to find:

• Reason for the encounter: why the patient was seen or what was being managed.
• Assessment: the diagnosis, symptom, condition, or documented uncertainty.
• Services performed: what was actually done—not only what was ordered or planned.
• Relevant clinical detail: such as site, laterality, acuity, stage, status, or episode, when clinically established and pertinent.
• Plan and follow-up: the clinician’s actions and next steps.

Specificity is useful only when it is true and documented. Official guidelines call for the highest specificity supported by the medical record and recognize that symptom or unspecified codes can be appropriate when a definitive diagnosis is not established. The ICD-10-CM guidance covers both principles.

Medical coding examples

The following fictional examples show how documentation drives the workflow. They do not identify code numbers or replace formal guidance.

Example 1: A symptom without a confirmed diagnosis

A patient visits for a persistent cough. The clinician documents the history, exam, testing ordered, and return precautions. The assessment states that no definitive diagnosis has been established at this visit.

The coding workflow can reflect the documented symptom and services provided. It should not convert a possible cause into a confirmed diagnosis merely because it is being considered. A useful note makes clear what is known, what is uncertain, and what will happen next.

Example 2: A follow-up for an active condition

A patient returns to follow up on an ongoing condition. The clinician documents the current status, relevant clinical detail, medication adjustment, and follow-up plan.

The coder needs to see that the condition was assessed or managed today. A condition carried forward in a problem list, without evidence it was addressed in the encounter, does not tell the same story. The assessment and plan should distinguish active management from history.

Example 3: A service and a supply in one encounter

A patient receives an in-office service and is given a medically necessary item that the clinician documents in the plan.

The record needs to show the reason for care, what was performed, and what item was supplied. Different code families may describe different components of the same encounter. The goal is a coherent record, not the largest possible list of codes.

Common medical coding documentation gaps

Most coding questions are documentation questions in disguise. The most common gaps are straightforward to reduce.

Avoid treating every gap as an invitation to infer. In practitioner discussion of post-encounter queries, an important distinction emerged: coding to the highest level supported by documentation is not the same as seeking the most specific code available. See the ACDIS discussion. If a material fact is unclear, use the organization’s approved clarification process.

How coders and clinicians work together

Medical coding is a shared quality loop. Clinicians establish and document the clinical story; coders translate that record using the applicable rules. Neither role replaces the other.

When documentation is incomplete, unclear, inconsistent, or contradictory, an organization may use a compliant query or clarification process. A good query asks for clarity based on the record; it does not steer the clinician toward a preferred answer.

Recurring questions are useful signals. They can point to a template that needs adjustment, a workflow that obscures the assessment, or a shared terminology issue. Strong medical documentation makes the record clearer for the care team first—and makes coding easier as a result.

Medical coding vs. medical billing

Medical coding and medical billing are related but different. Coding converts documented care into standardized codes. Medical billing uses coded and other administrative information in processes such as claim preparation, submission, and follow-up.

Keeping the distinction clear prevents a common misconception: accurate coding supports a billing workflow, but it does not promise that a payer will cover a service or pay a particular amount.

When to consult official coding guidance

Consult current official resources and your organization’s coding or compliance team when a decision depends on:

• the code-set version or effective date;
• inpatient versus outpatient rules;
• sequencing, modifiers, uncertain diagnoses, or bundled services;
• payer-specific requirements, coverage rules, or local policies; or
• a documentation conflict or possible query.

Start with current ICD-10-CM guidance, current CPT® materials from the AMA, and CMS HCPCS resources. Code sets and instructions change, so a past example should never be the final authority for a current encounter.

Medical coding FAQs

Is medical coding the same as medical billing?

No. Coding translates documented clinical information into standardized codes. Billing uses that information in claim and payment workflows.

Can a coder code a diagnosis from a test result?

Coding must follow the applicable rules and the documented clinical assessment. A test result or medication list does not automatically substitute for a clinician’s documented diagnosis. When a material detail is unclear, the right next step is clarification—not guesswork.

Does every note need maximum detail?

No. It needs the relevant, clinically established facts for that encounter. More detail is not better if it is unsupported, copied forward, or unrelated to the care provided.

How do patient intake and prior authorization relate to medical coding?

Structured patient intake can surface the reason for a visit and relevant history before the encounter, but it does not replace the clinician’s assessment. Clear documentation can also help teams prepare information for prior authorization, though authorization and coding rules are different.

The takeaway

Medical coding works when the coded record accurately reflects the care documented. Clinicians document the patient story and plan; coders apply the current rules; the team clarifies material uncertainty instead of filling in blanks. The outcome is not “more coding”—it is a complete, reliable record of the care provided.

Editorial sources

• CMS: Code Sets Overview
• CMS: Overview of Coding and Classification Systems
• CMS/NCHS: ICD-10-CM Official Guidelines for Coding and Reporting — replace with the version effective for the service date before publishing if needed.
• ACDIS forum: post-encounter specificity queries — workflow perspective only; not authoritative coding guidance.