A Documentation Workflow Built for SimplePractice EHR
Clinical documentation inside SimplePractice EHR rarely fails because clinicians lack dedication. It fails because the cognitive load of session presence competes directly with the mechanical load of typing structured notes into a browser editor. In psychotherapy and counseling, this tension is acute: the therapeutic alliance depends on undivided attention, yet the medical record demands diagnosis, modality, session timing, and progress-toward-goals documentation for every date of service.
Merry AI resolves this tension without asking SimplePractice to do anything it was not designed to do. SimplePractice is a closed EHR. It does not expose a public write-back FHIR API that lets third-party vendors push finished notes into custom fields, and it charges nothing for the privilege because that privilege does not exist. Rather than fight that architecture, Merry AI operates one layer higher—inside the authenticated browser session the clinician already controls—injecting reviewed drafts directly into the rendered DOM input elements of the progress note editor.
The practical result is a workflow where the clinician records the session, Merry AI streams a structured draft in real time, and the reviewed note lands in the correct SimplePractice field with a single confirmation. No marketplace onboarding. No API latency. No IT ticket.
Why Closed EMRs Reward DOM Injection Over API Marketplaces
The conventional integration model assumes every EHR offers a write API through a certified partner marketplace. That assumption holds for large enterprise systems but collapses for the platforms most psychotherapists actually use. SimplePractice, TherapyNotes, and Kipu are deliberately closed environments—they publish read-oriented documentation and system requirements but do not offer general third-party note write-back endpoints.
Vendors who pretend otherwise either quietly resort to fragile screen-scraping servers, force clinicians into brittle copy-paste rituals, or overstate their capabilities. Merry AI takes the honest engineering path: a browser-native Chrome Extension that identifies the exact DOM input selectors SimplePractice renders for the note body and its subsections, then writes text into those elements exactly as a keyboard would. Because the write happens in the same session context as manual typing, it is indistinguishable to the platform and requires no credential handoff.
DOM Field Mapping in Practice
When a clinician opens the Progress Note editor for a given appointment, SimplePractice renders a predictable set of rich-text and textarea elements. Merry AI's extension resolves these selectors on load and maps each generated section—Subjective, Objective, Assessment, Plan, or the DAP and BIRP equivalents—to its corresponding field. The mapping is validated against the visible editor state before any write occurs, so a layout change surfaces as a review prompt rather than a silent misplacement of clinical text.
Latency and the Cost of API Round-Trips
Marketplace API integrations introduce round-trip latency and rate limits that make real-time documentation impossible. A server-mediated write must serialize, authenticate, queue, and confirm before the note appears. Merry AI's DOM injection is local to the browser, completing field population in roughly 0.4 seconds after clinician approval—fast enough to feel like autocomplete rather than an upload.
The Integration Architecture Comparison
The three viable ways to move an AI-generated note into SimplePractice differ sharply in overhead, speed, and cost. The table below compares them directly.
| Architecture | Deployment Overhead | Latency | Annual Fee | Closed-EMR Support |
|---|---|---|---|---|
| Traditional API Marketplace | Enterprise onboarding, OAuth, IT approval | 2–8s round-trip | $$$ + per-seat marketplace fees | Not available for SimplePractice |
| Manual Copy-Paste | Zero, but 100% human effort | Human-speed, error-prone | $0 tooling, high labor cost | Works but breaks note structure |
| Merry AI DOM Injection | 5-minute Chrome install, no IT | ~0.4s local write | Flat practice plan, no marketplace fee | Native to SimplePractice browser |
Copy-paste technically works but degrades the structured field boundaries that SimplePractice depends on, frequently collapsing formatted SOAP sections into a single unformatted block. DOM injection preserves the section-by-section structure because it writes into each mapped field individually.
Protecting the Progress Note vs. Psychotherapy Note Boundary
SimplePractice enforces a compliance-critical distinction that any automation layer must respect. Progress notes are part of the client's medical record and are included when records are exported or shared with insurers and other professionals. Psychotherapy notes are handled separately, are not part of the standard record, and are disclosed only in limited circumstances such as a subpoena. This mirrors the federal framing that keeps a therapist's process analysis more tightly protected than the shareable clinical summary, a boundary well documented in the peer-reviewed literature indexed at https://www.ncbi.nlm.nih.gov/pmc/.
Merry AI encodes this boundary into its field mapping. Only shareable clinical content—diagnosis, treatment modality, session start and stop times, clinical impressions, and progress toward treatment goals—is generated for and injected into progress note fields. Sensitive process content and any 42 CFR Part 2 material stays in the separately protected psychotherapy note workflow and is never auto-populated into an exportable container. This prevents the single most dangerous automation failure: leaking protected process detail into an insurer-facing record.
CPT G2211 Capture for Longitudinal Care
Psychotherapy is often the continuing focal point for a patient's mental health care, which makes it a natural fit for the CMS complexity add-on code G2211. Per current CMS guidance, G2211 is reportable alongside office and outpatient E/M visits (CPT 99202–99215) when the clinician serves as the ongoing focal point for the patient's care. Merry AI surfaces the documentation cues that substantiate this complexity so eligible longitudinal sessions are captured rather than left on the table.
Governance, Review, and the Clinician as Author of Record
Every note Merry AI produces is a draft until a licensed clinician reviews and signs it. The extension never commits text to the chart autonomously; the human confirmation step is a hard requirement in the workflow, preserving the clinician as the legal author of record. This design keeps AI in the role of scribe rather than decision-maker, consistent with responsible clinical governance.
Under executed Business Associate Agreements, Merry AI retains zero audio and zero transcript data—processing is ephemeral and session-scoped, so nothing sensitive persists on our infrastructure after the note is delivered. Combined with the browser-native architecture, this means protected health information never leaves the trust boundary the clinician already operates within SimplePractice.
To see this workflow mapped against your own practice, Schedule a 15-Minute Workflow Audit, browse ready-to-inject structures at Access 1,000+ EHR Clinical Templates, and review deployment tiers via Explore Merry AI Practice Partner Plans.
