Primary care is the longitudinal home for heart failure management in Elation Health
Primary care clinicians using Elation increasingly manage heart failure patients in the months between cardiology visits. Each of those visits should restate the current ejection fraction, the functional class, and where every guideline-directed medication sits on its titration path. In practice, that information is scattered across echo reports, medication lists, and prior notes, and rebuilding it by hand costs minutes the clinician does not have.
Merry AI closes this gap by writing a structured heart failure block directly into the active Elation visit note through a Chrome Extension content script. There is no server API connection, no marketplace subscription, and no IT ticket. The clinician reviews the draft in place and signs it as their own record.
Merry AI writes into the Elation visit note through the browser DOM, not a server API
The Chrome Extension runs locally inside the clinician's Elation browser tab. It locates the editable visit note field by semantic signals, such as the ARIA textbox role and visible section labels, rather than brittle CSS class names that break after a vendor update. Writes are confined to the open encounter, so signed historical notes are never modified.
This pattern mirrors existing dictation workflows that Elation already supports. Elation documents third-party templating software and Dragon dictation that write directly into visit notes. Merry's injection behaves the same way: text appears in the field the clinician is already looking at, ready for editing.
Elation supports three note layouts: SOAP, Single Narrative, and H&P Two-Column. Merry detects the active layout and routes the heart failure block into the Assessment or Assessment & Plan field where it exists. Fields with no matching content are left untouched, and existing clinician text is never overwritten.
Browser-native DOM mapping bypasses EHR marketplace paywalls entirely
Server API integrations carry hidden costs for small primary care practices: vendor review cycles, per-connection fees, and IT configuration. Manual copy-paste avoids those costs but reintroduces clicks and transcription errors. The comparison below shows where DOM injection sits between them.
| Criterion | Traditional API Marketplace Integration | Manual Copy-Paste | Merry AI Chrome DOM Injection |
|---|---|---|---|
| Setup time | Weeks of vendor and IT review | None | Minutes, single extension install |
| Integration fees | Marketplace and per-connection fees | None | Zero API fees |
| IT or firewall changes | Often required | None | None required |
| Field-level placement | Depends on exposed endpoints | Clinician pastes by hand | Maps directly to the Assessment field |
| Clicks per note | Low after setup | High, with context switching | Low, one review in place |
| Transcription error risk | Low | Elevated | Low |
| Heart failure structure (LVEF, NYHA, GDMT) | Generic unless custom built | Depends on clinician memory | Enforced in every HF note |
| Audio retention | Varies by vendor | Not applicable | Shredded from RAM, zero days |
The tradeoff favors browser-native injection for independent and small-group practices on Elation, where IT capacity is limited and every subscription line item is scrutinized.
Every heart failure visit note records LVEF, NYHA class, and four-pillar GDMT titration
Merry structures the Assessment block around the data a cardiologist expects to see when the patient returns. Each element is written as discrete, reviewable text.
LVEF percent, source, and date. The most recent ejection fraction is recorded as a number with its modality and study date, plus a trend of improved, stable, or worsened. This value defines HFrEF versus HFpEF and drives therapy selection.
NYHA functional class with justification. Merry states the class, I through IV, alongside the symptom evidence from the encounter, such as dyspnea climbing one flight of stairs.
ARNI or ACEi/ARB titration status. The current agent, dose, target dose, and any barrier such as hypotension or hyperkalemia are captured in one line.
Evidence-based beta-blocker titration status. Merry records the agent, current dose, resting heart rate, and the plan to hold, increase, or maintain.
MRA titration status and labs. Spironolactone or eplerenone status is paired with the latest potassium and eGFR so the safety rationale is visible.
SGLT2 inhibitor status and tolerance. The note records whether the patient is on therapy, not tolerated, or contraindicated, with the reason stated.
A finished Assessment entry reads: HFrEF, LVEF 30% by echo 03-2026, stable. NYHA II, dyspnea with moderate exertion. Sacubitril/valsartan 49/51 mg BID, titrate to 97/103 mg if BP allows. Carvedilol 12.5 mg BID, HR 68. Spironolactone 25 mg daily, K 4.6. Empagliflozin 10 mg daily, tolerated. Repeat BMP in 2 weeks.
G2211 requires the note to prove a continuing focal point relationship
CMS defines HCPCS add-on G2211 as visit complexity inherent to care that serves as the continuing focal point for all needed health care services, or ongoing care of a single serious or complex condition. Per the CMS G2211 FAQ, it may be reported with office/outpatient E/M codes 99202-99205 and 99211-99215, and with home or residence E/M codes 99341, 99342, 99344, 99345, and 99347-99350.
Merry appends a focal point statement that names the clinician's longitudinal role, for example: this practice serves as the continuing focal point for the patient's heart failure and comorbid care, coordinating titration, laboratory monitoring, and cardiology communication. Medicare Administrative Contractor guidance asks the record to explain why the visit was complex because of that ongoing relationship, not simply because the patient was seen before.
Modifier 25 visits need clean separation. Since January 1, 2025, G2211 may be reported with an E/M billed with modifier 25 when performed the same day as an annual wellness visit, vaccine administration, or a qualifying Part B preventive service, as described in CMS MLN006764. Merry keeps the heart failure block inside the problem-oriented section, distinct from preventive or procedure documentation.
Merry never assigns billing codes. It documents clinical work. Code selection remains with the clinician and the practice's coding staff.
Setup takes three steps and no IT involvement
Step one: install the Chrome Extension from the Merry AI dashboard and sign in with your practice credentials.
Step two: open visit note. Launch a new or in-progress Elation visit note for the patient. The extension activates only when an editable encounter note is in focus.
Step three: map Assessment. Select the Assessment or Assessment & Plan field once. Merry stores that mapping for your layout and routes every future heart failure block to the same location.
Encounter audio is shredded from memory and never stored
Merry processes encounter audio transiently in memory and shreds it from RAM with zero-day retention. No audio file or transcript persists after the draft is generated, and processing runs under an executed Business Associate Agreement.
State AI rules continue evolving. Practices should confirm disclosure, consent, and audit obligations in their state with counsel. Merry supports a conservative posture: clinician review of every draft, insertion audit logs, and role-based access controls.
Clinician attestation remains the final step. Nothing enters the signed chart until the clinician reads, edits, and attests to the note, preserving the integrity of the signature and the medical record.




