ICD 10 Code - R26.2, Difficulty in Walking - 2025 Medical Coding Guide

Dr. Alex Carter
April 14, 2025
5 min read

Table of Contents

Share this post

Medical coders report R26.2 as one of the most frequently misapplied symptom-based codes, affecting documentation integrity across healthcare facilities nationwide. The code represents difficulty in walking—a functional limitation observed in 15% of patients over 65 and 8% of the general adult population seeking medical care.

R26.2 belongs to Chapter 18 of the ICD-10-CM classification system (Symptoms, Signs, and Abnormal Clinical Findings). The code sits within the R26 category encompassing abnormalities of gait and mobility. Healthcare providers use this code when patients present with walking difficulties without definitive diagnosis of underlying etiology.

The clinical significance of R26.2 lies in its specificity regarding functional limitation. Unlike codes indicating complete inability to walk or generalized gait abnormalities, R26.2 identifies patients capable of ambulation but experiencing noticeable difficulty or impairment. "R26.2 serves as the bridge between normal mobility and complete inability," notes Susan Miller, CPC, CDEO.

Article Image

In clinical documentation, R26.2 functions as a diagnostic placeholder while providers investigate root causes of walking difficulty. The code applies during initial assessments before diagnostic testing confirms neurological problems, musculoskeletal disorders, or other medical conditions affecting ambulation.

Critical differentiation exists between R26.2 and related codes R26.81 (gait imbalance) and R26.89 (other abnormalities of gait and mobility). While appearing similar, each describes distinct clinical presentations. A patient might demonstrate difficulty walking (R26.2) without exhibiting gait imbalance (R26.81) or unusual mobility patterns (R26.89).

What Clinical Conditions Qualify for the R26.2 Diagnosis Code?

Medical providers identify R26.2 as the appropriate code for patients demonstrating specific ambulatory limitations. The code applies to conditions where walking remains possible but presents significant challenges - affecting nearly 22% of adults over age 70 and 12% of post-surgical patients during recovery phases.

What are the primary symptoms that warrant ICD 10 code R26.2?

R26.2 coding requires documentation of observable walking difficulties. Qualifying patients typically demonstrate:

  • Noticeable exertion during ambulation attempts
  • Significantly reduced walking speed compared to baseline
  • Unstable stepping patterns without true balance disruption
  • Possible dependence on assistive devices (canes, walkers)
  • Self-reported pain or discomfort during walking attempts

"The critical distinction for R26.2 lies in the patient's retained ability to walk despite meaningful difficulty," explains Janet Thompson, PT, DPT. "When patients can ambulate but require extensive effort or assistance, R26.2 often represents the most appropriate code selection."

How does difficulty in ambulation differ from other gait disorders?

R26.2 differs from related gait codes through its focus on walking effort rather than pattern abnormality. Physical Medicine and Rehabilitation specialists report R26.2 concentrates on the exertion required for walking, not the appearance of the gait.

Distinguishing characteristics include:

  1. R26.2 identifies walking effort increases regardless of gait appearance
  2. Patients may demonstrate normal-appearing steps performed with extreme difficulty
  3. Temporary conditions frequently trigger R26.2 coding
  4. Pain-induced walking limitations without visual pattern changes qualify for R26.2

The code's application hinges on functional limitation assessment rather than visible walking mechanics.

Which neurological conditions commonly cause walking difficulties?

Neurological specialists report several conditions consistently producing R26.2-qualifying symptoms:

  • Parkinson's disease (G20) with characteristic shuffling steps
  • Multiple sclerosis (G35) during flare-ups affecting motor pathways
  • Post-stroke sequelae (I69.3-) with residual motor deficits
  • Peripheral neuropathy (G60.-) causing sensory disturbances
  • Cerebellar disorders (G11.-) affecting coordination and proprioception

"R26.2 frequently appears alongside neurodegenerative diagnoses where definitive treatment remains ongoing," notes Michael Chen, MD. "The code accurately captures functional limitations during disease progression stages."

What is the difference between R26.2 and other R26 subcategories?

The R26 category contains distinct subcodes addressing different mobility issues. R26.2 application requires understanding precise distinctions between:

R26.2 (Difficulty in walking) - Focuses on effort/exertion required for ambulation R26.81 (Unsteadiness on feet/Gait imbalance) - Primarily addresses balance disturbances R26.89 (Other abnormalities of gait and mobility) - Captures unusual movement patterns

Medical documentation must reflect these differences. A patient might demonstrate perfect balance (no R26.81) yet qualify for R26.2 due to pain, weakness, or stiffness making walking difficult. Conversely, a patient with significant balance problems (R26.81) might walk without the exertional difficulty that defines R26.2.

ICD-10-CM guidelines emphasize these distinctions affect treatment planning and reimbursement outcomes. Accurate code selection directly impacts both clinical care pathways and billing acceptance rates.

How Should Medical Professionals Document R26.2 Properly?

Medicare claim denials increase by 37% when R26.2 documentation lacks specificity, according to 2024 CMS audit findings. Medical professionals must record detailed observations justifying this diagnosis code to establish medical necessity and secure appropriate reimbursement.

"IF YOU DON'T DOCUMENT OBSERVABLE WALKING DIFFICULTIES, YOUR R26.2 CLAIM WILL BE REJECTED"

What specific observations should be included in patient notes?

R26.2 documentation requires precise mobility limitation descriptions rather than general statements. Medical records should contain these essential elements:

1. Assistive device usage - document type, frequency, and dependence level

2. Observable physical behaviors during walking attempts:

  • Walking speed compared to age-expected norms
  • Step consistency and stability patterns
  • Visible exertion signs (facial expressions, breathing changes)
  • Starting and stopping difficulties

3. Patient-reported symptoms affecting ambulation:

  • Pain location, intensity, and duration during walking
  • Weakness patterns in specific muscle groups
  • Fatigue onset timing during ambulatory activities

"Providers consistently miss the critical distinction between effort-based difficulties and balance problems," notes Richard Walker, MD, FACP. "Your documentation must clearly establish whether the patient struggles with the physical act of walking versus maintaining balance."

How detailed should the functional assessment be?

Functional assessments must demonstrate clear medical necessity through quantifiable metrics. Claims analysis shows 82% of denied R26.2 claims contained vague functional descriptions lacking measurable parameters.

Required functional assessment documentation includes:

  • Maximum ambulation distance before rest requirement (specify exact footage)
  • Specific daily activities impacted by walking limitations (bathroom use, kitchen activities)
  • Comparison to previous functional baseline with percentage changes
  • Environmental factors requiring accommodation (document specific barriers)
  • Safety risk assessment during ambulatory activities

The assessment must differentiate R26.2 from related conditions like R26.81 (gait imbalance) or complete inability to walk. Document explicit exclusion criteria when applicable to strengthen code selection justification.

What objective measurements support this diagnosis?

R26.2 diagnoses require objective, quantifiable measurements to withstand scrutiny. CMS guidelines emphasize measurable parameters over subjective assessments.

Effective documentation includes:

1. Standardized mobility test results:

  • Timed Up-and-Go Test (specify seconds required)
  • 6-Minute Walk Test (document distance achieved)
  • Berg Balance Scale scores (noting specific deficit areas)

2. Physical measurement parameters:

  • Stride length in centimeters
  • Cadence (steps per minute)
  • Step symmetry percentages between affected/unaffected sides

3. Comparative assessment values:

  • Baseline vs. current performance metrics
  • Week-to-week functional progression/regression
  • Response to therapeutic interventions

Thorough documentation creates a comprehensive clinical picture supporting the R26.2 diagnosis code while guiding appropriate treatment planning. The provider note should clearly connect observed limitations to treatment necessity and expected outcomes.

Practice documentation reviews reveal 67% of R26.2 claims lack proper objective measures—the primary trigger for medical necessity denials. Your attention to measurement detail directly impacts reimbursement success.

When Should You Use Related ICD-10 Codes Instead of R26.2?

Code selection errors in the R26 category trigger 42% of mobility-related claim denials, according to recent Medicare audit findings. Accurate differentiation between these closely related codes demands careful clinical assessment and precise documentation standards.

How does R26.89 differ from R26.2?

R26.89 (other abnormalities of gait and mobility) applies to unusual movement patterns rather than walking difficulties. The key distinction hinges on pattern versus effort:

R26.2 Focus: Increased exertion or strain during otherwise normal-appearing walking R26.89 Focus: Unusual or abnormal movement patterns without necessarily requiring extra effort

Clinical indicators requiring R26.89 instead of R26.2 include:

  1. Festinating gait without significant exertion
  2. Scissors gait with normal effort expenditure
  3. Circumduction without reported fatigue
  4. Unusual foot placement patterns that don't impede walking efficiency

"Coding selection between R26.2 and R26.89 rests on whether the abnormality involves the walking pattern or the physical effort required," explains Joan Rivera, CPC. "Observe whether patients struggle with the act of walking versus displaying unusual movements."

When is gait imbalance (R26.81) the more appropriate code?

Gait imbalance (R26.81) represents the correct coding choice when balance disruption constitutes the primary concern. Patient assessments revealing the following indicators warrant R26.81 coding:

R26.81 Indicators
Code Description
R26.2 Indicators Balance loss during stance
Normal balance with effortful walking
Sway during normal activities
Minimal sway with exertional difficulty
Risk of falling despite normal strength
Low fall risk with high exertion
Coordination deficits without weakness
Normal coordination with weakness

When both conditions exist simultaneously, sequence the code addressing the predominant clinical feature first. Medicare data shows incorrect sequencing triggers 23% of R26-related claim rejections.

What if the patient can't walk at all?

R26.2 exclusively describes difficulty walking—not inability. Complete ambulatory failure requires alternative code selection:

  • Z74.01: Bed confinement status
  • Z74.09: Other reduced mobility
  • R53.1: Weakness (when causing immobility)
  • M62.81: Muscle weakness (generalized)
  • Specific codes identifying underlying immobility causes

For cases where inability stems from previous conditions, proper sequela coding requires listing current manifestation first, followed by appropriate sequela code. Medicare sees improper sequela coding in 31% of rejected mobility claims.

How do you code for temporary versus chronic walking difficulties?

Duration considerations affect code selection and sequencing. Temporary walking difficulties typically warrant the R26.2 code alone, while chronic cases often require additional coding elements:

Temporary walking difficulties:

  • Use R26.2 without additional chronicity indicators
  • Document expected recovery timeframe
  • Include external cause codes where applicable

Chronic walking difficulties:

  • Add G89.29 (Other chronic pain) if pain causes chronic difficulty
  • Document duration exceeding 3 months
  • If representing sequela of previous condition:
    • Code current condition (R26.2) first
    • Add sequela code identifying original cause second

The 2025 ICD-10-CM guidelines emphasize: "The code for the acute phase of an illness or injury that led to the sequela is never used with a code for the late effect." Violating this principle constitutes one of the most common R26.2 coding errors seen in practice.

Proper duration documentation proves essential for accurate code assignment and claim acceptance. Your records must clearly establish whether difficulties represent acute, persistent, or chronic conditions to support appropriate code selection.

What Are Common Coding Mistakes with R26.2 and How Can You Avoid Them?

CMS audit reports reveal R26.2 claims face a 27% higher denial rate than other symptom-based codes, primarily due to documentation deficiencies. Medicare Administrative Contractors identified walking difficulty codes among their top five audit targets for 2025.

Why is specificity crucial when coding walking difficulties?

R26.2 coding demands precise clinical differentiation. Medical record audits show three primary error patterns:

  1. Code confusion errors - Mistaking R26.2 (difficulty walking) for R26.81 (gait imbalance) or R26.89 (other gait abnormalities)
  2. Sequencing mistakes - Placing codes in incorrect order for sequela conditions
  3. Documentation gaps - Missing objective measurements supporting medical necessity

"The distinction between exertion during walking versus unusual gait pattern determines which R26 code applies," states Mark Johnson, CCS, CDIP. "Yet 57% of rejected claims contained insufficient documentation to support this distinction."

The ICD-10-CM guidelines explicitly state that symptom codes must reflect the most specific clinical presentation possible. For sequela cases, proper sequencing proves critical - "the condition or nature of the sequela is sequenced first. The sequela code is sequenced second."

R26.2 relationships with other diagnostic codes require careful attention. For instance, many musculoskeletal conditions like arthropathies (M00-M25) naturally include walking difficulty as a symptom. Adding R26.2 in these cases creates redundancy unless the walking difficulty exceeds typical expectations for the primary condition.

How can you prevent denials related to this diagnosis code?

Medical claims data shows successful R26.2 submissions contain four critical documentation elements absent in 76% of denied claims:

Documentation Requirement
Requirement Common Error Correct Approach
Specific mobility measurements "Patient walks with difficulty" "Patient walks 20 feet before requiring rest, reduced from 100-foot baseline"
Distinct symptom clarification "Abnormal gait present" "Patient exerts significant effort during walking without balance problems"
Proper sequela sequencing Acute injury code with R26.2 R26.2 first, then sequela code with "S" seventh character
Duration specificity "Patient has walking problems" "Walking difficulty present for 6 weeks following surgery"

Further denial prevention strategies include:

  • Document functional limitations using standardized assessment tools (Timed Up-and-Go, 6-Minute Walk Test)
  • Include comparative baseline measurements showing functional changes
  • Specify exact assistive devices required for ambulation
  • Note environmental factors affecting walking ability
  • Clearly differentiate between temporary versus chronic difficulties

"Medical coders consistently miss exclusionary relationships between R26.2 and other codes," reports Susan Miller, RHIA, CCS. "For example, coding R26.2 with R29.3 (abnormal posture) creates an illogical clinical scenario in many cases."

For sequela coding, remember the critical guideline: "The code for the acute phase of an illness or injury that led to the sequela is never used with a code for the late effect." Documentation must clearly establish whether walking difficulty represents an acute symptom or the lasting result of previous injury.

Physical therapy notes prove particularly vulnerable to R26.2 denial. Nearly 42% of PT-submitted R26.2 claims lack sufficient objective measurements to justify medical necessity. Successful claims consistently include timed functional tests, strength measurements, and specific range-of-motion limitations affecting ambulation.

How Will the 2025 Updates Affect Coding for Difficulty in Walking?

The 2025 ICD-10-CM Official Guidelines introduce substantial changes affecting R26.2 coding practices. Healthcare providers must adjust documentation approaches to maintain compliance with updated standards effective October 1, 2024.

Medicare contractors report receiving clarification on R26.2 sequencing through transmittal MM12756, establishing new prioritization standards. These updates address longstanding confusion identified through claim analysis, where 43% of R26.2 rejections stemmed from improper sequencing.

What new sequencing rules should coders know for 2025?

The 2025 guidelines establish clear hierarchies when R26.2 appears alongside other conditions. CMS now requires specific sequencing in common clinical scenarios:

1. Dehydration scenario: When walking difficulty stems from dehydration due to underlying conditions, sequence:

  • Dehydration code first (E86.0)
  • Walking difficulty code second (R26.2)
  • Underlying cause code third

2. Anemia-related difficulty: When walking difficulty accompanies anemia associated with malignancy:

  • Malignancy code first
  • Anemia code second (D63.0)
  • Walking difficulty code third (R26.2)

"These sequencing changes reflect clinical decision-making pathways," explains Thomas Roberts, MD, MPH. "The guidance now aligns coding priority with treatment priority, improving documentation accuracy."

How have the sequela coding requirements changed?

The 2025 updates emphasize precise sequela coding when walking difficulties result from previous conditions. CMS audit data reveals 36% of R26.2 claims contained improper sequela code assignment.

Updated sequela coding requirements include:

  • Current condition (R26.2) must be sequenced first
  • Appropriate sequela code must follow with "S" seventh character
  • Never use acute phase illness/injury code with late effect code

The guidelines explicitly state: "The code for the acute phase of an illness or injury that led to the sequela is never used with a code for the late effect." This critical requirement affects post-stroke patients particularly - coders must document current walking difficulties (R26.2) followed by the appropriate I69 sequela code.

"Medical coders frequently reverse this sequence," notes Jennifer Williams, RHIT, CCS. "The updated guidelines leave no room for interpretation - current manifestation always comes first."

What documentation changes will affect R26.2 claims?

The 2025 guidelines heighten specificity standards for symptom-based codes. Documentation requirements now include:

Documentation Element
Documentation Element Prior Standard 2025 Requirement
Symptom differentiation General mobility issues Clear distinction between effort vs. balance vs. pattern
Measurement requirements Subjective assessments acceptable Objective, quantifiable measurements required
Functional impact General statement of limitation Specific ADL impacts with measured limitations
Duration specification General timeframe Exact onset date and progression documentation

Medical necessity validation now requires clear documentation differentiating whether mobility issues involve effort/exertion (R26.2), balance problems (R26.81), or unusual movement patterns (R26.89).

The 2025 guidelines state: "Symptom codes must reflect the most specific clinical presentation possible based on objective measurements." Failure to meet these enhanced documentation standards represents the primary reason for anticipated claim denials.

Common Documentation Errors

One of the most frequent mistakes is using R26.2 when a more specific code would be appropriate. For example, if a patient presents with difficulty walking due to coordination issues, R26.0 (ataxic gait) should be used instead of R26.2. Another common error is pairing R26.2 with fall-related codes such as R29.6 (falling), which is explicitly prohibited by ICD-10 guidelines. These two conditions cannot be coded together due to an "Excludes 1" note.

To avoid these errors, it's essential to understand the exclusions associated with the R26 category. The ICD-10 guidelines specify several conditions that are excluded from being coded with R26.2 due to the "Excludes1" note:

  • Ataxia NOS (R27.0)
  • Hereditary ataxia (G11.-)
  • Locomotor (syphilitic) ataxia (A52.11)
  • Immobility syndrome (paraplegic) (M62.3)

These exclusions highlight the importance of selecting the precise code that aligns with the patient’s specific condition. By paying attention to these details, healthcare providers can ensure accurate and compliant medical coding.

How will external cause coding change for walking difficulties?

External cause coding receives significant clarification in the 2025 guidelines. Key changes include:

  1. External cause codes can never serve as principal diagnosis when coding conditions causing walking difficulties
  2. External cause codes require 7th character matching associated R26.2 code
  3. Late effect external cause codes apply only when actively treating the late effect

"YOU MUST MATCH SEVENTH CHARACTERS BETWEEN RELATED CODES"

The new guidelines emphasize consistency between related codes. When external cause and R26.2 codes appear together, they must share identical 7th character values (A, D, or S) to indicate initial encounter, subsequent encounter, or sequela status.

For fracture sequelae causing walking difficulties, the guidelines now require the S form of both codes. Combined with the sequela sequencing rules, this creates a specific pattern: current manifestation (R26.2,S) followed by sequela code (injury with S seventh character).

Documentation must explicitly connect the external cause to the walking difficulty while maintaining proper sequencing. This relationship proves especially important for patients with injury-related walking difficulties representing the largest demographic for R26.2 coding.

What Are the 2025 Updates for Coding Difficulty in Walking?

Medical coding standards continue evolving through annual updates. The 2025 ICD-10-CM Official Guidelines introduce critical modifications to R26.2 coding practices, affecting medical necessity determinations and claim approval rates nationwide.

CMS published these changes following analysis of 87,000+ walking difficulty claims, identifying four primary areas requiring standardization. Healthcare providers must adapt documentation practices before implementation date.

What are the new sequencing priorities?

The 2025 guidelines establish definitive sequencing hierarchies for R26.2 coding scenarios. These changes address longstanding confusion identified by Medicare Administrative Contractors.

When coding R26.2 alongside related conditions, follow these updated sequencing rules:

  1. Dehydration pathway: For walking difficulties secondary to dehydration from underlying conditions:
    • Code dehydration (E86.0) first
    • Code R26.2 second
    • Code underlying cause third
  2. Anemia considerations: For walking difficulties with malignancy-related anemia:
    • Code malignancy first (appropriate C code)
    • Code anemia second (D63.0)
    • Code R26.2 third

Medical documentation must reflect awareness of these sequencing requirements. "These sequencing changes establish logical clinical relationships between conditions," explains Robert Thomas, MD. "Proper sequencing now follows physiological cause-effect relationships."

How have external cause requirements changed?

External cause coding changes significantly under 2025 guidelines. Key modifications include:

  • External cause codes (Y codes) cannot function as principal diagnoses
  • External cause codes require 7th character alignment with associated R26.2 code
  • Initial encounter codes use matching "A" seventh characters
  • Subsequent encounter codes require matching "D" seventh characters
  • Sequela status requires matching "S" seventh characters on both codes

The 2025 guidelines state: "External cause codes provide valuable information for epidemiological research and injury prevention, but cannot represent primary diagnoses."

Medical coders report external cause misalignment as a frequent audit trigger. Documentation must clearly establish the relationship between external cause and resulting walking difficulty while maintaining proper character assignment.

What documentation standards are changing?

Documentation standards face substantial elevation under 2025 guidelines. CMS now requires significantly enhanced specificity:

Previous Documentation Standard: "Patient walks with difficulty requiring cane."

2025 Requirement: "Patient ambulates 50 feet before requiring rest, compared to 200-foot baseline. Walking requires visible exertion evidenced by increased respiratory rate from 18 to 26 breaths/minute during ambulation. Patient demonstrates normal balance but requires single-point cane for energy conservation rather than stability."

R26.2 documentation must explicitly distinguish between:

  • Effort/exertion issues (R26.2)
  • Balance problems (R26.81)
  • Unusual movement patterns (R26.89)

Successful claims now require objective measurements supporting diagnosis. The most common measurement tools include:

  • Timed Up-and-Go Test (TUG) scores
  • 6-Minute Walk Test distances
  • 10-Meter Walk Test results
  • Functional Independence Measure (FIM) mobility scores

How should you handle sequela coding?

The 2025 guidelines clarify sequela coding requirements for walking difficulties resulting from previous conditions. This section experienced significant enhancement after analysis revealed 43% sequela coding errors in R26.2 claims.

Proper sequela coding now requires:

  1. Current walking difficulty (R26.2) coded first
  2. Appropriate sequela code with "S" seventh character coded second
  3. Never using acute phase code alongside sequela code

"The code for the acute phase of an illness or injury that led to the sequela is never used with a code for the late effect."

This sequencing directly impacts post-stroke patients with walking difficulties. Documentation must establish both the current functional limitation and its relationship to the previous condition while adhering to proper coding sequence.

CMS anticipates these updates will reduce claim denials by standardizing documentation requirements across healthcare settings. Provider education before October 1, 2024 implementation date remains critical for continued reimbursement success.

Reimbursement Considerations

When the ICD code R26.2 is applied correctly, it serves as a billable diagnosis code. However, using this code without the necessary supporting documentation can result in claim denials or underpayment. Therapists must ensure that their clinical notes clearly support the use of R26.2 by describing the patient’s condition in detail.

To avoid issues with claims and billing, healthcare providers should always document thoroughly and choose symptom codes that best match the patient's symptoms. This approach not only facilitates accurate billing but also enhances communication among healthcare professionals, ensuring that all aspects of the patient's condition are considered in their treatment plan.

Here is the Reimbursement for R26.0:
Procedure Code Diagnosis Code Claim Amount Insurance Company
97110 M54.2, R29.3, R26.0, M25.552, M25.512 45.24 IL Medicare Part B
97112 M54.2, R29.3, R26.0, M25.552, M25.512 39.92 IL Medicare Part B
97140 M54.2, R29.3, R26.0, M25.552, M25.512 21.12 IL Medicare Part B
97110 R26.89, R26.0, M25.561, M62.81, M17.11 37.09 OH BCBS Professional
97112 R26.89, R26.0, M25.561, M62.81, M17.11 40.36 OH BCBS Professional

Payer-Specific Guidelines

Different insurance companies may have specific requirements for processing claims that include R26.2. For instance, some payers may require additional documentation that describes the underlying causes of the patient’s walking difficulty. It’s also important to note that while R26.2 is a billable code, it may not be sufficient on its own for reimbursement in more complex cases. In these instances, therapists may need to include secondary ICD-10 codes that further describe the patient’s condition.

FAQs

Q1. What exactly does the ICD-10 code R26.2 represent?

R26.2 is the code for difficulty in walking, not elsewhere classified.

Q2. How does R26.2 differ from other related mobility codes?

R26.2 focuses on the effort of walking, while R26.81 (gait imbalance) addresses balance issues, and R26.89 covers other gait abnormalities.

Q3. What information should healthcare providers include when documenting R26.2?

Providers should record speci

Frequently asked questions

How to Write a Soap Note for Physical Therapy?
Start with the Subjective (patient-reported issues), Objective (measurable observations), Assessment (analysis of progress), and Plan (treatment strategy). Use clear, concise language and focus on therapy-specific details.
How to Write a Soap Note for Speech Therapy?
Document the patient's speech concerns (Subjective), therapy observations (Objective), progress or challenges (Assessment), and the proposed treatment plan (Plan). Ensure it’s tailored to speech goals.
Are Soap Notes Legal Documents?
Yes, SOAP notes are considered legal documents. They provide a formal record of patient care and may be used in audits, billing, or legal proceedings
What Goes in the Assessment Part of a Soap Note​?
The assessment includes the therapist's professional evaluation of the patient’s progress, response to therapy, and any changes in the treatment approach.
How to Create an AI Medical Scribe?
An AI medical scribe is built to capture spoken notes during sessions, transcribe them into structured formats, and assist with documentation. It combines speech recognition with intelligent algorithms to streamline the process.
What Are Some Best Physical Therapy Soap Note Example?
Effective examples include notes with clear Subjective details (patient input), measurable Objective data (e.g., ROM tests), a concise Assessment, and actionable Plans for the next steps.

Why settle for long hours of paperwork and bad UI when Spry exists?

Modernize your systems today for a more efficient clinic, better cash flow and happier staff.
Schedule a free demo today