Glossary · Documentation

Progress note

A progress note is a dated, encounter-specific clinical record documenting a patient's current status, the clinician's assessment, and the plan of care—serving as both a communication tool among providers and the primary support document for E/M code selection and medical necessity.

Verified May 8, 2026 · 6 sources ↓

Drawn from LoincAafpTextexpanderNIHCMS

Definition

Source · Editorial summary grounded in 6 cited references ↓

A progress note captures a snapshot of a single patient encounter: what the patient reported, what the clinician observed or examined, and what decisions were made about diagnosis and treatment. It is not intended to re-document stable historical information already present in the chart; a reference to that prior documentation is sufficient. The note is authored by the treating clinician—physician, PA, NP, nurse, or therapist—and becomes a permanent part of the medical record. In orthopedics, progress notes span a wide range of encounter types: new-injury evaluations, post-operative follow-ups, fracture checks, and chronic musculoskeletal disease management visits.

Progress notes are typically structured using the SOAP framework (Subjective, Objective, Assessment, Plan), though hybrid formats are common in orthopedic practice. The Assessment and Plan sections carry the greatest weight for coding: they must reflect the medical decision-making (MDM) complexity or total time that justifies the selected E/M level. Bullet-padding those sections to inflate visit level—adding clinically irrelevant normal findings solely to hit a higher code—is a compliance risk that auditors specifically target.

From an interoperability standpoint, the progress note carries LOINC code 11506-3 and is a recognized document type in the HL7 C-CDA standard. This means structured progress notes exchanged between EHR systems are expected to follow defined section templates, a detail that matters when Mira's AI scribe generates documentation that downstream systems must ingest and parse correctly.

Why it matters

The progress note is the single document that ties clinical care to reimbursement: payers use it to validate the E/M level billed, confirm medical necessity for any ordered procedures, and adjudicate appeals when claims are denied or flagged in a RAC or CERT audit. An orthopedic progress note that is vague, undated, missing a legible signature, or lacks a coherent Assessment and Plan can trigger downcoding, claim denial, or—if the documented work doesn't match the billed code—a fraud-and-abuse finding. Conversely, a well-constructed note that accurately reflects the complexity of MDM or total clinician time protects appropriate reimbursement and gives appeal support when payers inappropriately bundle or deny associated procedure codes.

Common mistakes

Where people most often go wrong with this concept.

Source · Editorial brief grounded in cited references ↓

  • Billing a higher E/M level based on note length or bullet count rather than the actual complexity of medical decision-making or total time spent.
  • Re-documenting unchanged history and ROS in full at every follow-up visit instead of referencing the prior note—wasting time without adding compliance value.
  • Leaving the Assessment and Plan vague (e.g., 'continue current treatment') when the encounter involved meaningful clinical decisions such as ordering imaging, adjusting medications, or discussing surgical options.
  • Signing or finalizing a progress note days after the encounter without an addendum explaining the delay, which creates a credibility problem in audits.
  • Conflating a progress note with a Medicare Progress Report (as defined under Medicare B Section 1833e)—they serve different purposes and have distinct documentation requirements.
  • Using a copy-forward or copy-paste function that carries over prior-visit findings verbatim, making the current note inaccurate and potentially constituting cloning, which payers treat as a compliance violation.
  • Omitting the post-operative status or global period context in orthopedic follow-up notes, which can lead to improper billing of a separately payable E/M during a surgical global period.

Related codes

Codes commonly involved when this concept appears in practice.

Frequently asked questions

Source · Generated from the editorial pipeline, verified against 6 cited references ↓

01Does a progress note need to repeat the full history and review of systems at every visit?
No. CMS documentation guidelines allow a clinician to reference a previously recorded history or ROS rather than re-documenting it in full, as long as the note indicates the prior entry was reviewed and any relevant updates are noted. Re-documenting stable, unchanged information at every visit wastes time and does not increase the supportable E/M level.
02What is the difference between a progress note and a Medicare Progress Report?
A progress note documents the clinical details of a specific patient encounter and supports E/M billing. A Medicare Progress Report is a separate, distinct document required under Medicare B Section 1833e for certain therapy and rehabilitation services to justify ongoing medical necessity. The two documents serve different regulatory purposes and should not be confused or substituted for each other.
03Can an orthopedic surgeon bill a separate E/M service on the same day as a procedure using a progress note?
Only under specific conditions. Modifier 25 allows a separately identifiable E/M service on the same day as a minor procedure (0- or 10-day global), but the progress note must clearly document a distinct clinical evaluation beyond the pre-procedure assessment. Modifier 57 applies when the E/M on the day of or the day before a major procedure (90-day global) results in the decision to perform that surgery. The progress note must support that distinction for the modifier to survive audit scrutiny.
04What makes a progress note legally defensible in an audit?
A defensible progress note is dated and timed, bears a legible authenticated signature, reflects the actual work performed rather than templated or cloned text, contains an Assessment and Plan that logically connects to the diagnoses billed, and documents either the MDM elements or total clinician time sufficient to support the E/M level selected. Discrepancies between the billed code and the documented work are the leading audit trigger.
05How does LOINC code 11506-3 relate to orthopedic progress notes?
LOINC 11506-3 is the universal identifier assigned to the progress note document type in clinical information systems. When orthopedic progress notes are transmitted between EHR platforms or submitted in structured formats, this code ensures the receiving system correctly categorizes the document as an encounter-based progress note rather than a discharge summary, referral letter, or other note type.

Mira AI Scribe

Mira's AI scribe participates directly in progress note generation. When a clinician dictates or speaks through an encounter, Mira maps the spoken content to the standard SOAP structure and flags sections that appear incomplete for the E/M level being considered. Specifically, Mira checks whether the Assessment and Plan reflect sufficient MDM complexity—number and nature of problems addressed, amount and complexity of data reviewed, and risk of complications—or whether total time documentation is more defensible for the visit. If the spoken note contains copy-forward language identical to a prior encounter, Mira flags it as a potential cloning risk before finalization. For orthopedic post-operative visits occurring within a global surgical period, Mira identifies the active global period and alerts the clinician before an E/M code is attached, prompting either use of modifier 24 (unrelated E/M during global period) or documentation that the visit is included in the global package (CPT 99024). Mira also enforces LOINC 11506-3 metadata tagging so that exported progress notes are interoperable with downstream C-CDA-compliant systems. The scribe does not auto-select an E/M level; it surfaces the MDM or time evidence present in the note and lets the clinician confirm the appropriate code.

See Mira's approach

Related terms

Ready?

Ready to transform your orthopedic practice?

See how orthopedic practices are running documentation, billing, and operations on a single voice-first platform.

Get started for free