A Documentation Workflow Built for AdvancedMD
Clinical documentation inside AdvancedMD rarely fails because clinicians lack diligence. It fails at the boundary between exam room and chart. A family physician may manage diabetes, hypertension, depression, and a pediatric asthma follow-up in one afternoon, then reconstruct each encounter from memory. Every reconstruction costs minutes, and those minutes add up across a twenty-patient panel.
Merry AI addresses that boundary with a Chrome extension that operates inside the clinician's active AdvancedMD session. The extension drafts a structured SOAP note from the visit and presents it for review. It then writes the approved text into the matching AdvancedMD note fields. Because the integration never leaves the browser, there is no marketplace listing, no interface engine, and no per-transaction API fee.
The architecture is deliberately narrow. It does not claim native FHIR write access to AdvancedMD. The extension writes only where a clinician could type, only after the clinician approves, and only into the encounter open on screen.
How DOM Injection Works Inside AdvancedMD
AdvancedMD renders its charting surfaces as HTML and JavaScript in the browser. The encounter shell, the History, Exam, and Assessment/Plan panes, and the billing tab are all document object model elements. A permissioned extension can read and populate them, and Merry AI treats them as its integration surface.
Pinning the Extension to the AdvancedMD Tab
AdvancedMD launches as a pop-up window by default, which isolates it from standard extension context. Before first use, open AdvancedMD as a full browser tab. On Windows, right-click the top bar and select Show as tab. On macOS, choose Window, then Show as Tab. Pin the Merry AI extension to that tab and grant clinical note field injection permission when Chrome prompts.
This permission is scoped tightly. The extension requests access only to the AdvancedMD domain. Injection stays inactive until a clinician explicitly approves a draft. No IT ticket, firewall change, or server-side installation is involved.
Selector Mapping and Autosave Events
Because AdvancedMD loads tabs lazily, the Assessment/Plan editor exists in the DOM only while its pane is active. Merry AI uses a MutationObserver to detect when the editor mounts. It then locates the input with label- and ARIA-based selectors anchored to the active encounter container, rather than brittle positional paths. The extension handles both textarea and contenteditable rich-text targets.
After writing the approved text, the extension dispatches native input, change, and blur events. AdvancedMD's own autosave and validation logic then fire as they would for typed text. Existing clinician-entered content is preserved, never overwritten. Injection typically completes in under 500 milliseconds.
G2211 Logic for Family Medicine Encounters
HCPCS add-on code G2211 recognizes the complexity of serving as the continuing focal point for a patient's care. It also covers ongoing care for a single serious or complex condition. It attaches only to office/outpatient E/M codes 99202-99205 and 99211-99215, or to home and residence E/M visits. Family medicine is its natural home, and also where unsupported attestation draws the most audit scrutiny.
The Three-Element Attestation Gate
Merry AI appends G2211 language only when three elements are present in the note. The first is a role statement establishing the clinician as the continuing focal point. The second is a longitudinal problem map linking the visit to chronic conditions under active management. The third is a patient-specific plan covering titration, monitoring, or coordination. If any element is missing, Merry AI withholds the suggestion and flags the gap.
The attestation text is parameterized from documented content alone. Consider a note that references NYHA class II HFrEF with beta-blocker titration and cardiology co-management. The attestation cites exactly those facts, and a note without cardiology coordination will never claim it. Diagnoses are checked against the current code set at https://www.cms.gov/medicare/coding-billing/icd-10-codes, so problem specificity supports the complexity claim.
Modifier logic stays deliberately conservative. A minor procedure such as a joint injection may occur on the same day as the visit. In that case, Merry AI suggests Modifier 25 only when the E/M history, exam, and medical decision-making are documented separately from the procedural work. It never proposes Modifier 59 unless the record shows distinct anatomy, session, or procedure type. The physician retains final authority on coding and medical necessity.
Integration Architecture Compared
Family medicine practices evaluating AdvancedMD documentation tools typically choose among three architectures. They differ in deployment overhead, latency, cost, and control.
| Architecture | Deployment Overhead | Write Latency | Annual Fee | Clinician Control |
|---|---|---|---|---|
| Traditional API Marketplace Integration | Vendor approval, IT project, interface configuration | Queue-dependent, often batched | Marketplace and per-interface fees | Review after data lands in EHR |
| Manual Copy-Paste | None | Minutes per note plus tab-switching | None, but high labor cost | Full, but error-prone |
| Merry AI Chrome DOM Injection | Install and pin extension | Under 500ms after approval | No API or marketplace fees | Approval before every write |
Audio is held in RAM only. Visit audio is buffered in memory during capture, streamed for transcription, and released once the note is completed and injected. Nothing is written to local disk, and no recording is retained for model training. This lifecycle supports California SB 1120's intended-purpose standard and simplifies HIPAA risk analysis.
Clinician review remains the control point. AI-drafted segments are marked in the review pane and must be accepted before injection. Patient-facing summaries are never sent without explicit physician action, which keeps practices aligned with California AB 3030 disclosure rules.
To start with proven structures, browse Family Medicine templates for chronic care, well-child visits, and behavioral health follow-ups at https://templates.scribing.io. Then configure them for your AdvancedMD encounter layout.
