Explore a physical therapy evaluation example with a full SOAP note and CPT code guide.
You finish the eval, select your CPT code, submit the claim, and it comes back flagged. The payer's reason: your assessment didn't justify the complexity level you billed. It's a frustrating denial, especially when the clinical work was thorough.
Most of those flags trace back to how the initial evaluation was structured. Each section of your Subjective, Objective, Assessment and Plan (SOAP) note has a direct billing match. When those links aren't clear, payers find the gaps.
That's because a solid PT eval isn't just a form you fill out. It's a workflow. Every section feeds what comes next: coding, payer review, and outcomes tracking. The physical therapy evaluation example below shows how those pieces fit together.
Get that workflow right, and your notes survive scrutiny and get paid faster.
A physical therapy evaluation is the formal clinical process a licensed PT completes at the first visit. The therapist gathers the patient's history, measures baseline function, establishes a diagnosis, and builds a plan of care. The finished document becomes part of the patient's official medical record. Referring physicians, payers, and auditors can all access it.
One distinction trips up many clinicians: the examination and the evaluation are not the same thing. The examination is the data collection step. It covers the patient history, systems review, and objective tests and measures. The evaluation is the clinical judgment you apply to that data. It turns raw findings into a diagnosis, a prognosis, and a plan. You can't complete an evaluation without a thorough examination behind it. Payers review both. The examination proves you gathered the evidence. The evaluation proves you know what it means.
A physical therapy SOAP note has four sections:
Each one feeds a specific next-step action in billing, payer review, and outcomes tracking. When any section is vague, the next-step action it supports breaks down.
The subjective section details the patient's view to show the payer why skilled PT is needed. You need to document:
That detail is what separates a note that survives review from one that gets flagged. "It hurts" tells the reviewer nothing. Compare that to: "Sharp anterior shoulder pain with overhead reaching. Onset 3 weeks ago after painting ceiling." The second version gives the payer a mechanism and a timeline. It also sets a functional context they can trace through the rest of your eval.
The objective section is where you quantify what's wrong. Every measurement here becomes the baseline for future progress notes. It also provides the comparison point for the discharge summary. Document:
This is also where you set a baseline functional outcome measure. Give a condition-matched patient-reported outcome measure (PROM) at the initial eval, before treatment begins. Examples include the QuickDASH for shoulder or the Oswestry for lumbar.
That baseline ties directly to Merit-based Incentive Payment System (MIPS) quality measures, such as Measure 478. It gives you a solid discharge comparison as well. You can reference the baseline if a payer questions whether treatment produced measurable change.
The assessment is where most clinicians get flagged. It requires a two-part structure:
That link is how you justify medical necessity. For example, an assessment section may look like:
"Patient exhibits 3/5 shoulder abduction strength, limiting ability to perform overhead grooming and lifting tasks.
Skilled PT is required to restore neuromuscular control and pain-free function."
Documentation gaps are the leading cause of Medicare PT denials. The assessment is where most of those gaps start. Consider a vague assessment that says "patient has shoulder weakness." Not tying it to a functional limitation gives the reviewer no reason to approve continued care.
Payers also expect a prognosis with a stated rationale. A bare "good" or "fair" no longer holds up. You need to name the factors behind it, such as motivation, comorbidities, acuity, or surgical history. The rehab potential statement in the example below shows what that looks like in practice.
The Centers for Medicare & Medicaid Services (CMS) requires specific elements in every plan of care:
Short-term goals are stepping stones you expect the patient to hit in two to four weeks. Long-term goals are discharge targets. Both must be measurable. "Improve ROM" fails an audit. "Achieve 160° shoulder flexion AROM within 8 weeks" survives one.
Per the Medicare Benefit Policy Manual, the plan must include diagnoses, measurable long-term goals, and the specific type, amount, duration, and frequency of services. A re-eval (CPT 97164) is required when there's a major change in condition, a new clinical finding, or failure to respond to the current plan. A progress note documents expected progress within the existing plan. It doesn't replace or reset the eval.
2025 Update: CMS finalized a plan-of-care signature exception. If a written physician order is on file, you can send the plan within 30 days of the initial eval. Services meeting other requirements are payable before the signature arrives.
Here's a complete, coded initial evaluation for a fictional patient with shoulder impingement. Every value, test, and goal reflects the kind of detail payers expect. You can adapt this physical therapy evaluation example to any diagnosis. The documentation logic stays the same. Use it as an outpatient physical therapy evaluation template for your own notes.
Patient: Jane Doe, 42-year-old recreational tennis player
Referral: Dr. Smith, orthopedics
Chief complaint: Right shoulder pain limiting overhead reaching and sleep
Patient presents with R shoulder impingement syndrome. ROM deficits include flexion 135° and abduction 120°. Strength deficits include abduction 3+/5 and ER 3/5, with positive impingement signs (Neer's, Hawkins-Kennedy, Empty Can).
These impairments limit overhead reaching, grooming, sleep positioning, and recreational activity. Skilled PT is required to restore pain-free ROM, scapulohumeral mechanics, and rotator cuff strength to enable independent overhead function. Rehab potential: Good. Patient is motivated, no surgical history, acute-on-chronic presentation with clear modifiable impairments.
This presentation maps to CPT 97162 (moderate complexity). The rationale for that code selection is explained in the next section.
Short-term goals (4 weeks):
Long-term goals (8 weeks):
CPT codes 97161, 97162, and 97163 represent low, moderate, and high evaluation complexity. Your documentation must match the level you bill. Evaluation complexity comes down to four factors:
The table below shows how each code maps to these four factors. Use it as a decision framework when selecting your code.
The shoulder impingement patient from the SOAP example maps to 97162. Her eval shows three personal factors: recreational athlete, overhead work demands, and sleep disruption.
Three-plus examination elements were tested, including ROM, MMT, three special tests, postural assessment, and functional testing. Her presentation is evolving (acute-on-chronic, modifiable). Decision-making is moderate, balancing manual therapy with exercise progression across multiple intervention types.
The CPT descriptors also list typical face-to-face times: 20 minutes for 97161, 30 minutes for 97162, and 45 minutes for 97163. Treat these as descriptive, not decisive. Evaluation codes are untimed, so duration alone never justifies a complexity level. The four factors above drive the selection. Time simply tends to follow them.
The complexity level directly affects payment. A 97163 pays more than a 97161. But billing a higher code without documentation to support it creates code reduction risk. A PT-specific EMR like Empower EMR can flag when your documentation doesn't support the level you've selected. That catches the mismatch before submission.
Medicare, commercial insurers, and workers' comp each check different documentation elements in your initial eval. A note that passes Medicare review may get flagged by a workers' comp carrier expecting return-to-work language. Commercial payers may reject it for missing prior authorization details. Submitting the same note to all three is a fast path to denials.
Clinics treating mixed-payer caseloads need payer-specific checklists built into their workflow. That starts with an evaluation that captures the information each payer expects. A 2025 APTA survey found that 83% of PTs report prior authorization (PA) causes patients to abandon care. So your eval needs to be PA-ready for each payer from day one.
CMS data shows that 63.6% of improper payments stem from insufficient documentation. Medicare auditors check these elements first. A missing medical necessity statement or unmeasurable goal is enough to trigger a repayment demand.
Starting January 1, 2026, impacted payers must issue PA decisions within seven calendar days (standard) or 72 hours (expedited) under the CMS Interoperability and Prior Authorization Final Rule.
Some states have specific needs beyond the standard checklist. New York, for example, requires "Work Status" to be clearly visible. Return-to-work must be addressed at every visit.
Most eval denials don't come from missing sections. They come from weak phrasing that fails to show skilled need or measurable progress. The fixes below take seconds to apply. They can mean the difference between a clean claim and a denial.
Every phrase in your eval should answer two questions. What did you measure, and what does it mean for the patient's function? If a sentence could apply to any patient on your caseload, it's not specific enough.
Choosing the right patient-reported outcome measure at the initial eval gives you a solid baseline. Use it for discharge comparison, quality reporting, and payer justification. Give the PROM during the objective portion of your eval, before treatment begins.
Giving the right PROM at the initial eval satisfies MIPS quality reporting. It strengthens your medical necessity argument if a payer questions continued treatment. You also get an objective discharge comparison that goes beyond subjective patient reports.
Each phase of the eval maps to a specific EMR workflow action. When those actions are linked, you finish documentation faster without losing the detail payers require. Here's how the pipeline works:
Empower EMR handles this pipeline natively. Intake data flows into the subjective. PROMs populate the objective. Compliance checks run before submission. Billing codes are validated against your documentation in real time.
For clinics treating mixed-payer caseloads, the payer-specific checklists can be built into your EMR's compliance logic. The system flags what's missing for Medicare versus workers' comp before you submit. Your team finishes notes before the next patient is called, and claims go out clean.
Every PT evaluation sets the stage for what happens next. It affects coding, billing, payer review, and outcomes tracking. Strong documentation keeps every step connected. It starts with the SOAP note and carries through coding and payer review
The best evaluations tell a clear story. A payer should be able to follow the patient's complaint through your findings and plan of care. Every section should support that story with clear documentation and measurable findings.
We built Empower EMR to handle that entire workflow in one place.
Digital intake populates your subjective section before the patient arrives. Automated PROM delivery sets objective baselines without eating into treatment time. Compliance checkers flag documentation gaps before notes reach the billing queue.
Your team finishes evaluations before the next patient is called. Claims go out clean the first time.
The SOAP structure is universal. But Medicare, commercial insurance, and workers' comp each require different documentation elements:
Submitting identical notes to all three raises your denial risk. Build payer-specific checklists into your workflow. Each note should include what that reviewer is looking for.
Your documentation supports the CPT code you billed if your note clearly shows all four complexity factors:
Payers often reduce your code for two reasons. Either your assessment didn't connect impairments to functional limitations, or your objective section tested fewer body systems than the code requires. Run a self-check: can someone reading only your note identify which factors justify your code?
Document the barrier in the objective section. Note "PROM deferred due to [specific reason]."
Be specific about the reason. For example: "Patient unable to complete QuickDASH due to limited English proficiency. Spanish version will be given at visit 2 with interpreter present." That way the gap doesn't look like an omission.
Then schedule it at visit two or three once the barrier is resolved. MIPS Measure 478 allows PROM collection within the first three visits to still count as a baseline.
Document all special tests performed, both positive and negative results. Payers use the breadth of your examination to justify the CPT complexity level. Negative findings rule out differential diagnoses, which strengthens your clinical reasoning.
A note listing only "Neer's positive" looks incomplete. A note showing "Neer's positive, Hawkins-Kennedy positive, Speed's negative" shows a thorough exam. That supports moderate-to-high complexity billing. Negative findings aren't wasted documentation. They show skilled clinical decision-making.
Re-evaluate when any of these triggers apply:
A re-evaluation uses CPT 97164, not 97161–97163. It documents updated findings against the original baseline. A re-eval differs from a progress note. It reassesses the entire clinical picture and may result in a modified plan of care, per the Medicare Benefit Policy Manual.
