Specialty - Physical Therapy
PT coding is time-based to the minute. Generic AI breaks here.
Physical therapy is one of the hardest specialties to automate: the 8-minute rule, timed vs. untimed logic, a payer- and credential-dependent modifier stack, progress note cadence rules, and MPPR all run simultaneously on every Medicare session. Linx is built for clinics that code from time-stamped treatment notes - not generic E/M charts.
Why PT Coding Resists Generic AI
Physical therapy runs two billing rule systems in parallel - time-based and per-session - under a credential-aware modifier stack. Any one of these failing silently turns into systematic over- or underbilling on every affected claim.
The 8-Minute Rule, applied at the session level
Medicare unit math is calculated across total timed minutes for the session, not per CPT code. A generic coding model that adds units code-by-code will systematically overbill or underbill. Linx parses start/stop times for every intervention, sums timed minutes, divides by 15, and applies the ≥8 / ≤7 minute remainder rule correctly.
Timed vs. untimed code logic
Timed codes (97110, 97112, 97116, 97140, 97530) bill in 15-minute units under the 8-minute rule. Untimed codes (97010 hot/cold pack, 97012 traction) bill exactly once per session regardless of time. Applying the wrong rule to either family creates a per-claim error that compounds across thousands of visits per month.
PT-specific modifier stack
GP on every Medicare PT service, KX above the annual therapy threshold, 59 for distinct procedures, CQ/CO for PTA/OTA-rendered services (50% Medicare reduction), and GN for shared sessions. CQ/CO requires knowing the rendering provider's credential - data that lives in the practice roster, not the clinical note.
Progress note cadence tracking
Medicare requires a progress report every 10 treatment visits or 30 calendar days, whichever comes first. Submitting a claim past that window without a fresh progress note is an automatic denial. This is a longitudinal tracking problem that most per-encounter AI coders ignore.
Multiple Procedure Payment Reduction (MPPR)
When multiple timed services bill in one Medicare session, the practice expense component of the second and subsequent services is reduced by 50%. Expected reimbursement, posting, and AR variance all depend on applying MPPR correctly. A generic coder that ignores MPPR will quietly mis-forecast revenue every day.
Commercial payer fragmentation
Visit caps (often 20–30/year per condition), pre-authorization requirements, and adoption of the 8-minute rule all vary by carrier. Telehealth PT reimbursement remains uneven across states in 2026. Linx routes each claim through payer-specific rule sets instead of one global billing logic.
Real PT Sessions, Coded Correctly
The scenarios that quietly cost outpatient PT clinics revenue every month.
97110-GP × 2, 97112-GP × 1 (3 units total, session-level math)35 timed minutes ÷ 15 = 2 with 5 remainder. Linx applies the rule at session level, not per code, and stamps GP on every Medicare PT service.
97110-GP-CQCQ pulled from the rendering provider's credential on file. Medicare auto-reduces reimbursement 50% - billing forecast and posting reconciliation adjust accordingly.
Claim held + flag to clinicianProgress report due every 10 visits or 30 days. Linx blocks submission, opens a task for the treating PT, and routes the claim once the note is signed.
97140-KX, 97530-KXKX modifier applied once the patient crosses the carrier-specific therapy threshold, with documentation reference attached to the claim.
PT Modifier Reference
Linx applies each of these based on payer, plan of care status, threshold tracking, and the rendering provider's credential on file.
Built for the PT Workflow
From signed treatment note to clean claim, with credential-aware modifiers and session-level unit math baked in.
Treatment note + start/stop times ingested
Linx pulls the daily note, intervention list, start/stop timestamps per service, and the rendering provider's credential from WebPT, Raintree, Prompt, Net Health, or your EHR.
AI applies PT-specific billing logic
Session-level 8-minute math, timed vs. untimed routing, GP/KX/CQ/CO/59/GN modifier stack, MPPR adjustment, and progress-note cadence check - all in one pass.
Clean claim, payer-aware routing
Each claim is routed through the right payer rule set (Medicare, Medicare Advantage, commercial) and lands in your billing system with full audit trail back to the documentation.
Calculate Your PT Coding ROI
High-volume outpatient PT clinics typically recover a full coder's worth of capacity within the first quarter, plus a measurable revenue lift from correct unit and modifier capture.
Estimated Savings
Physical Therapy Coding FAQ
How does Linx apply Medicare's 8-Minute Rule?
Linx sums total timed minutes across all timed CPT codes in the session, divides by 15, and applies the ≥8 / ≤7 minute remainder rule to determine billable units at the session level - not per code. Start and stop times are pulled directly from the treatment note.
Can Linx distinguish PTA-rendered services for CQ / CO modifier application?
Yes. Linx integrates with the practice's credentialing roster to identify the rendering provider on each service line and automatically attaches CQ (PTA) or CO (OTA) when required, including the 50% Medicare reimbursement reduction in posting and AR forecasting.
Does Linx track Medicare progress note cadence?
Linx tracks treatment visit count and calendar days since the last progress report on every Medicare episode. Claims that would submit past the every-10-visits-or-30-days threshold are held and a task is opened for the treating PT.
How does Linx handle MPPR on multi-service Medicare sessions?
When multiple timed services bill in one session, Linx applies the 50% practice expense reduction to the second and subsequent units inside the expected reimbursement calculation so billing, posting, and AR variance reflect the actual Medicare payment.
Start Your Physical Therapy AI Pilot
Multi-clinic PT groups, hospital outpatient therapy departments, and PT-focused RCM vendors all run on Linx. Plug into WebPT, Raintree, Prompt, or your EHR - or white-label the workflow under your brand.