How DOM Injection Differs From API Marketplaces
Clinical documentation inside Aesthetic Practice Mgmt rarely fails because clinicians lack diligence—it fails because the tooling forces a choice between slow marketplace integrations and error-prone manual transcription. Aesthetic Practice Mgmt, like most closed aesthetic platforms, does not expose an open FHIR write endpoint for third-party scribes. Vendors who claim native API write access into such systems are usually describing a limited read scope, a paid marketplace listing with quarterly sync lag, or an aspirational roadmap. Merry AI takes a different and more honest architectural position: we do not claim API write access to a system that does not offer it.
Instead of routing protected health information through a server-side integration, our browser-native Chrome Extension operates inside the authenticated session you already have open. It reads the rendered DOM, identifies the discrete input selectors for chief concern, history of present illness, examination, assessment, and plan, and—only after your approval—dispatches native input events into those exact fields. There are no marketplace setup fees, no OAuth provisioning cycles, and no API rate limits introducing latency between your spoken note and the committed chart.
| Architecture | Deployment Overhead | Field-Level Accuracy | Latency | Annual Fee |
|---|---|---|---|---|
| Traditional API Marketplace | Weeks of provisioning, IT tickets, OAuth setup | High but limited to exposed endpoints | Sync lag from seconds to hours | Per-seat marketplace + platform fees |
| Manual Copy-Paste | None, but fully human | Error-prone; formatting drift, wrong fields | Human typing speed | Hidden cost in clinician hours |
| Merry AI DOM Injection | Minutes; extension install only | Precise selector mapping to native fields | Sub-second, client-side | Flat practice subscription, no API tax |
Peer-reviewed work on plastic-surgery EHR usage confirms that documentation burden and interface friction are persistent dissatisfiers among surgeons, and that standardized note templates measurably improve charge capture. Our design is a direct response to that evidence: reduce keystrokes, preserve structure, and keep the clinician in control of every field before it commits.
Why Field-Level Mapping Beats Free-Text Paste
Copy-paste workflows collapse structured content into a single free-text blob, forcing the clinician to manually re-sort narrative into the correct discrete fields. This is where charge capture erodes and where audit-relevant detail—injection sites, device settings, lot numbers—gets lost. DOM injection preserves the structure of a template by targeting each field selector individually, so a SOAP note lands in SOAP fields and a treatment record lands in the treatment record fields. Templates are available at Access 1,000+ EHR Clinical Templates and load pre-mapped to Aesthetic Practice Mgmt selectors.
Browser Permissions and Security Boundaries
The extension requests scoped host permissions limited strictly to your Aesthetic Practice Mgmt domain. It does not read other tabs, does not open inbound ports, and does not exfiltrate the DOM to an unmanaged endpoint. Audio and transcript processing occurs under an executed Business Associate Agreement with zero retention, meaning no audio or transcript persists after your session. Because injection is client-side within an already-authenticated session, Merry AI never circumvents the platform's own role-based access controls, session timeouts, or audit logging.
Intake, Classification, and Conservative Routing
Merry AI functions as an intake-and-routing layer, not an autonomous diagnostic system. When aesthetic inquiries arrive by phone, chat, SMS, or portal, the system classifies each by procedure type—injectables, energy-based treatments, body contouring, breast procedures, facial procedures, or reconstructive consults—and by urgency tier. The practice controls the taxonomy and maps it to its actual services. Classification describes the requested service or presenting issue; it never implies clinical candidacy, which remains the responsibility of a licensed clinician.
Urgency classification prioritizes risk indicators over the requested procedure. A routine filler inquiry accompanied by sudden severe pain, skin blanching, or visual symptoms must route as a possible vascular-occlusion complication—an ophthalmologic and dermatologic emergency—rather than as a routine lead. The routing model uses conservative tiers: emergency (airway compromise, uncontrolled bleeding, rapidly progressive swelling) triggers immediate emergency-services instruction; urgent clinical review (possible infection, vision changes after facial treatment) demands same-day clinician review; priority and routine tiers route to scheduling; and a mandatory 'cannot determine' state escalates ambiguous high-risk language to a human. Sensitivity is deliberately favored over convenience, because a false-positive urgent referral carries less clinical risk than a missed emergency.
Separating Marketing Leads From Clinical PHI
The system distinguishes prospective marketing leads from existing-patient clinical communications. Once a person reports symptoms, complications, or postoperative concerns, the interaction may contain protected health information and is handled under the practice's HIPAA-compliant workflow. Promotional messaging, testimonials, and before-and-after photographs require separate written authorization; a general treatment consent is never treated as publication permission. This operational and legal separation is codified in the note-class segregation described in our FAQ.
G2211, E/M Integrity, and Documentation Fidelity
Longitudinal aesthetic and reconstructive care frequently qualifies for CPT add-on code G2211, which per CMS guidance may be reported alongside office/outpatient E/M visits (99202–99205 and 99211–99215) when the visit serves as the continuing focal point for a patient's care or as part of ongoing care for a single serious or complex condition. Merry AI's templates prompt for the medical-necessity narrative that substantiates G2211, ensuring the complexity is documented rather than assumed. For clinicians establishing internal compliance standards, the current CMS E/M guidance and the G2211 FAQ should govern reporting decisions.
Treatment and postoperative documentation must identify the licensed provider, procedure performed, product with lot number and expiration date, dose or device settings, injection sites or treated areas, anesthesia agents, tolerance, complications, aftercare instructions, and follow-up interval. Our injectable and device templates enforce these discrete fields so that postoperative messages do not remain stranded in a chat platform but are summarized into the official record with source and timestamp preserved. Evidence-based office-based plastic surgery guidelines and the broader clinical literature indexed at the National Library of Medicine reinforce that continuity of records and procedure-specific consent are the backbone of a defensible chart.
Governance, Validation, and Getting Started
Our operating boundary is deliberate and non-negotiable: Merry AI routes inquiries based on procedure type and urgency and drafts structured documentation, but it does not independently diagnose, consent, prescribe, select injectables, determine surgical candidacy, or replace clinician assessment. Every high-risk or ambiguous interaction reaches a qualified human, and every routing decision remains reviewable in the medical record. Before production use, practices should validate the system against a test set spanning routine inquiries, ambiguous messages, postoperative concerns, vascular-occlusion warning signs, and frank emergencies—measuring urgent-case sensitivity, false-negative escalation rate, and chart-linking accuracy.
Governance requires named clinical and privacy owners, a written intended-use statement, an approved taxonomy, standardized escalation scripts, a human-review policy, and periodic sample audits. Because Merry AI may receive protected health information, the practice should confirm business-associate status and execute a BAA; our zero-retention posture and scoped permissions are designed to simplify that due diligence, but the practice remains responsible for configuration, workforce training, and minimum-necessary use.
Getting started takes minutes, not weeks. Install the Chrome Extension, load a plastic-surgery template, and begin drafting notes that inject cleanly into Aesthetic Practice Mgmt fields. To see the workflow against your own chart layout, Schedule a 15-Minute Workflow Audit. To review coverage tiers for multi-provider practices, Explore Merry AI Practice Partner Plans. The result is a documentation layer that respects both the closed architecture of your EMR and the clinician's role as author of record.
