Browser-native DOM mapping writes PT notes into Raintree Systems without a server API
Clinical documentation inside Raintree Systems rarely fails because clinicians lack dedication. It fails because a physical therapist carrying a full outpatient caseload must reconstruct interventions, minutes, and objective measures after the session ends, often from memory and often after clinic hours. Merry AI removes that reconstruction step by drafting the note during the visit and writing it into the Raintree chart the clinician already has open.
The Merry AI Chrome Extension runs inside the clinician's authenticated Raintree browser session. It reads the visible page structure, identifies the target fields for the active template, writes drafted content into those inputs, and dispatches standard browser input and change events so Raintree's own form logic registers each entry as if the clinician typed it. No server-to-server API connection, marketplace listing, or vendor integration fee sits between the extension and the chart.
Merry AI is not affiliated with Raintree Systems. The extension works at the browser layer, which means it does not alter Raintree's servers, database, or configuration. Nothing is saved or signed until the clinician reviews the draft and commits it using Raintree's normal save and sign workflow.
Merry AI anchors to Raintree template labels, not fragile CSS paths
Raintree's configurable EMR templates allow practices to assign custom fields and screens, and its rehab documentation supports specialty-specific exams and multiple episodes of care in one patient record. That flexibility is useful for clinics, but it means two practices on Raintree can present very different note layouts. Hard-coded CSS selectors would break the first time a template was edited.
Merry AI treats each documentation pane as a logical zone: Subjective, Objective, Assessment, Plan, flowsheet, and charges. The extension anchors to visible semantic labels and adjacent inputs first, then to stable element attributes confirmed during onboarding. Those mappings live in a configuration file that can be updated without shipping new code, so a template revision becomes a mapping change rather than an outage.
Episode of care detection runs before every injection. Because Raintree can hold several active plans of care for one patient, the extension confirms which episode and encounter are open, scopes timers and flowsheet rows to that episode only, and warns the clinician if content appears to belong to a different plan of care.
Per-intervention timers turn the 8-minute rule into auditable units
Timed therapy codes under Medicare follow the 8-minute rule. Total timed minutes across all 15-minute codes in a session determine billable units, while untimed codes such as evaluations 97161 through 97163 are excluded from the timed total. Merry AI tracks start and stop times per intervention and applies the CMS thresholds in real time:
- Eight to 22 total minutes supports 1 unit.
- Twenty-three to 37 total minutes supports 2 units.
- Thirty-eight to 52 total minutes supports 3 units.
- Fifty-three to 67 total minutes supports 4 units, with each further 15-minute band adding one unit.
Unit allocation follows CMS guidance. Full 15-minute increments are assigned first, and any remaining unit goes to the service with the most remaining minutes. For example, 33 minutes of therapeutic exercise (97110) plus 7 minutes of manual therapy (97140) totals 40 minutes and 3 units: 97110 receives 2 units for its first 30 minutes, and the final unit goes to 97140 because its 7 remaining minutes exceed the 3 remaining minutes of 97110.
Every calculation writes an audit record containing timestamps, interventions, minutes per intervention, and the final unit distribution. The CMS outpatient rehabilitation documentation booklet (MLN905365) identifies insufficient documentation as a leading source of CERT errors in PT, OT, and SLP claims. A minute-level log that ties each unit to a documented intervention is the record auditors ask for.
Structured flowsheet capture links every billed minute to a measured deficit
Narrative text alone cannot prove medical necessity at the line-item level. Merry AI writes objective measures into discrete Raintree fields: range of motion in degrees with side, manual muscle testing grades, special test results, and functional scores such as LEFS, Oswestry, Neck Disability Index, Berg Balance, and Timed Up and Go. Pediatric practices can capture developmental milestones and standardized test scores the same way.
Discrete capture creates a chain that holds up under review: a measured deficit, a goal tied to that deficit, an intervention addressing the goal, the minutes spent, and the resulting CPT units. When baseline and follow-up values sit in structured fields, progress reports show trajectory without manual chart review.
Modifier 59 and modifier 25 require distinct documentation zones, not narrative inference
NCCI procedure-to-procedure edits apply to common PT pairs, such as 97530 with 97140. Modifier 59 is supported only when the services are genuinely distinct, for example performed in separate time intervals or on separate anatomic regions. Merry AI flags these pairs, requires the clinician to confirm the distinct region or interval, and inserts a concise justification line into the note before modifier 59 is suggested for the charge grid.
Modifier 25 applies only to E/M codes, and only when the E/M service is significant and separately identifiable from other services that day. In multidisciplinary Raintree practices where a physician or APP performs an E/M on the same date as therapy, Merry AI keeps the E/M history, exam, and medical decision making in a separate documentation zone from the PT flowsheet, and logs the rationale for every modifier 25 recommendation.
G2211 belongs to E/M visits, so Merry AI never suggests it for PT-only encounters
HCPCS add-on code G2211 describes visit complexity inherent to office/outpatient E/M codes 99202-99205 and 99211-99215, and, for 2026, home or residence E/M codes, according to the CMS G2211 FAQ. Physical therapists do not bill E/M codes, so G2211 is never presented as an option on a PT-only encounter. Suggesting it there would be upcoding.
Physicians and APPs on Raintree who manage patients longitudinally receive a different workflow. Merry AI surfaces documentation evidence of ongoing care for a single serious or complex condition, and checks same-day modifier 25 combinations against the policy described in MLN006764, including the exceptions for annual wellness visits, vaccine administration, and other Part B preventive services.
Chrome DOM injection removes the API marketplace from the integration path
Three integration paths exist for getting documentation into Raintree. The comparison below reflects their structural differences, not vendor-specific pricing.
| Criterion | Traditional API Marketplace Integration | Manual Copy-Paste | Merry AI Chrome DOM Injection |
|---|---|---|---|
| Setup path | Vendor review, contracting, and IT build cycle | None | Per-user extension install with executed BAA |
| Recurring integration fees | Marketplace or interface fees common | None | Zero API fees |
| IT involvement | Required for credentials and interface testing | None | Optional, for managed Chrome deployment |
| Flowsheet field targeting | Limited to fields the API exposes | Clinician pastes into each field by hand | Writes to any visible field in the active template |
| 8-minute rule calculation | Depends on vendor build | Clinician calculates manually | Real-time per-intervention timers and unit allocation |
| Audit trail of minutes and units | Varies by interface | None beyond the final note | Timestamped log per intervention and unit |
| Error surface | Interface mapping errors | Transcription and wrong-field errors | Label-anchored mapping with episode checks |
| Clinician attestation | Raintree sign workflow | Raintree sign workflow | Required review before Raintree sign workflow |
Narrative-first ambient scribes typically generate a single text block for the note body. In physical therapy, that leaves flowsheet rows, timed minutes, and charge units for the clinician to enter separately, which is exactly where most PT documentation time and audit exposure sit. Field-level injection addresses that gap directly.
California AB 3030 disclosure logic travels with every patient-facing draft
California AB 3030 requires providers using generative AI for patient clinical communications to include a disclaimer that the content was AI-generated and clear instructions for reaching a human provider, unless a licensed provider reads and reviews the communication before it is sent (bill text). Merry AI tags AI-drafted segments, stores AI-use metadata with each draft, and applies state-specific disclaimer templates to patient-facing summaries and home exercise instructions.
Immutable generation and edit logs record what the system drafted and what the clinician changed. That record supports internal compliance review today and leaves room for additional state requirements as AI health care statutes continue to evolve.
Clinician attestation remains the final control on every Raintree chart
No injected content becomes part of the legal medical record until the treating clinician reviews it, edits it as needed, and signs it in Raintree. Merry AI drafts, maps, and calculates. The clinician decides. Audio and transcripts are not retained after drafting, and all processing occurs under an executed Business Associate Agreement.
Practices evaluating this workflow can see their own Raintree templates mapped in a live session. Schedule a 15-Minute Workflow Audit to review field mapping, 8-minute rule logic, and modifier safeguards against your current documentation.




