Browser-native DOM mapping writes endocrinology notes into CharmHealth without an API contract
CharmHealth runs entirely in the web browser. Documentation, orders, medications, and questionnaires load as standard web pages inside the clinician's session, and no local client is installed. This architecture is the reason Merry AI operates as a Chrome Extension overlay rather than a server integration.
The Merry AI Chrome Extension executes in the same browser context as the open CharmHealth encounter. It waits for the chart to finish loading, then locates the Assessment and Plan fields using label text, ARIA attributes, and field names. It writes the clinician-reviewed draft directly into those inputs. No FHIR client registration, marketplace listing, or server-side credential is involved.
Endocrinology documentation fails at data translation, not data availability
Most endocrinology documentation burden sits in one step: converting a 14-day CGM report and an insulin log into a defensible Assessment and Plan. The data already exists in the sensor platform. The cost is the minutes spent retyping percentages and justifying each dose change.
Merry AI structures every visit around four required elements: 14-day Time in Range (TIR %), Time Below Range (TBR %), Glucose Management Indicator (GMI), and every insulin dose change with its rationale. These elements are documented at every visit, not only when control worsens, so the longitudinal trend stays visible in the chart.
A typical injected Assessment reads: Type 1 diabetes with suboptimal control. 14-day CGM shows TIR 54% (goal 70% or higher), TAR 42%, TBR 4%. GMI 8.4% from mean glucose 192 mg/dL. Recurrent post-prandial excursions after dinner.
The matching Plan entry reads: Increase basal glargine from 18 units to 22 units at bedtime, targeting fasting glucose of 90 to 120 mg/dL. Adjust dinner insulin-to-carbohydrate ratio from 1:10 to 1:8. Re-review CGM in 4 weeks. The clinician edits, confirms, and attests before anything is committed to the chart.
Three integration paths produce different outcomes for CharmHealth endocrinology practices
The comparison below summarizes how each documentation path performs on setup, cost, field placement, and specialty depth.
| Criteria | Traditional API Marketplace Integration | Manual Copy-Paste | Merry AI Chrome DOM Injection |
|---|---|---|---|
| Setup requirement | Vendor partnership, OAuth client registration, IT review | None | Chrome Extension install and one-time field mapping |
| Marketplace or API fees | Typically recurring | None | None |
| Field-level placement | Limited to exposed API endpoints | Manual and error-prone | Direct write to Assessment and Plan fields |
| CGM metrics (TIR, TBR, GMI) | Usually generic note body | Retyped by clinician | Templated at every visit |
| Insulin dose change rationale | Rarely specialty-aware | Written from memory | Drafted from the visit for clinician edit |
| Time to first note | Weeks to months | Immediate, with high per-visit cost | Same day |
| Audio retention | Vendor-dependent | Not applicable | Processed in RAM, zero-day retention |
| Clinician attestation | Varies by vendor | Inherent | Required before commit |
Setup takes one encounter: install the extension, open a chart, map the Assessment field
Step one: install the Merry AI Chrome Extension in the browser profile used for CharmHealth. The extension requires no firewall changes and no administrator credentials inside CharmHealth.
Step two: open a CharmHealth encounter for an established patient. The Merry panel appears alongside the chart and confirms that the encounter page has loaded.
Step three: map the Assessment field. Click into the Assessment input once and confirm the mapping in the Merry panel, then repeat for Plan. If CharmHealth updates its interface, the compatibility layer re-resolves fields by label text rather than by class names that change between releases. Injected content is appended below any text the clinician has already written and never overwrites it.
Longitudinal CGM documentation supports G2211 when the ongoing relationship is real
CMS defines HCPCS code G2211 as an add-on recognizing complexity inherent to E/M visits that serve as the continuing focal point for a patient's care, or that are part of ongoing care for a single serious or complex condition. It pairs with office codes 99202 to 99205 and 99211 to 99215. Beginning January 1, 2026, it also pairs with home or residence codes 99341, 99342, 99344, 99345, and 99347 to 99350.
CMS adds no separate documentation requirements beyond the base E/M service. Contractors such as Noridian still expect the record to show why the visit is complex because of the longitudinal relationship. Generic phrases such as 'patient is complex' do not meet that standard.
Visit-over-visit CGM trends and titration history make that complexity visible. A note recording TIR moving from 73% to 58%, naming the cause, and documenting a specific basal and bolus response shows cognitive work an auditor can follow. Merry AI surfaces this evidence. The clinician decides whether G2211 applies.
Modifier 25 requires the E/M service to stand apart from same-day procedures
When CGM sensor placement or insulin pump training is billed on the same day, the E/M service needs modifier 25 and documentation showing it is significant and separately identifiable. CMS does not pay G2211 when the base E/M carries modifier 25 for a separately payable procedure, except alongside listed preventive services such as annual wellness visits and vaccine administration. Modifier 59 applies to procedures and is never appended to E/M codes.
Merry AI keeps the E/M narrative (CGM interpretation, risk assessment, regimen change) separate from the procedure note. Billing hints appear only in the clinician panel and are never written into the medical record.
Zero-day audio retention keeps protected health information inside CharmHealth
Audio is processed in RAM and discarded once the draft is generated. No audio or transcript is written to disk or retained on Merry servers, and processing is covered by an executed Business Associate Agreement. The signed note lives only in CharmHealth, which already sits inside the practice's compliance program.
Practices in California and Texas should still update patient notices to disclose ambient documentation tools and confirm with counsel how the workflow aligns with state medical privacy and telehealth rules. The note remains clinician-authored and clinician-signed.




