Merry AI writes interventional pain procedure data directly into CareCloud templates
Clinical documentation inside CareCloud rarely fails because interventional pain physicians lack dedication. It fails because the procedure workflow splits data across tabs. The pre-injection pain score lives in Vitals, the spinal levels live in a procedure template pick-list, and the fluoroscopic findings live in a narrative editor. After a full day in the fluoroscopy suite, reconstructing those details from memory is where accuracy erodes.
Merry AI closes that gap by listening to the clinician's narration during the encounter and procedure, extracting the discrete elements that payers audit, and writing them into the exact CareCloud fields where they belong. A spoken phrase such as 'under continuous fluoroscopic guidance, needles were advanced to the right L4-L5 and L5-S1 facet joints' becomes a checked guidance field, two structured level entries, and a standardized narrative sentence.
Browser-native DOM mapping bypasses EHR marketplace paywalls entirely
The Chrome Extension operates client-side inside the clinician's active CareCloud tab. It recognizes the encounter view by URL path and page landmarks, such as the patient header and the Vitals, Notes, and Procedures tabs. It then locates target inputs using semantic attributes like aria-label and data field keys rather than brittle positional selectors.
Write-back happens at the individual field level. For simple inputs, the extension sets the value and dispatches the same input and change events that a keystroke generates, so CareCloud's front-end state registers the entry as if the clinician typed it. For rich-text sections, it inserts standardized sentences into the designated procedure note block. Each field write completes in under 500 milliseconds.
Because no server API is involved, there is no marketplace listing fee, no interface engine, no HL7 or FHIR build, and no firewall change. Practice IT installs nothing on the server side, and the clinician's existing CareCloud login and permissions govern every action.
Multi-tab workflows use a short-lived client-side queue. If the pain score field lives in Vitals and the fluoroscopy narrative lives in the Procedures tab, the extension writes each value when that view becomes active. A small overlay marks every auto-populated field and offers one-click undo, and idempotence checks prevent duplicate entries when a clinician repeats a phrase.
CareCloud does not publish its DOM structure, so Merry AI validates field selectors against each practice's live templates during onboarding and runs regression checks after CareCloud releases.
Interventional pain medical necessity depends on discrete, anatomically specific data
Payers reviewing spinal injections look for a consistent set of elements: pain severity on a 0 to 10 Numeric Rating Scale or VAS before injection, functional impact such as an Oswestry Disability Index score, symptom duration, documented failure of conservative care such as physical therapy and NSAIDs, exam and imaging correlation, and response to prior injections. Medicare LCDs for facet joint interventions and epidural steroid injections make several of these elements explicit.
Merry AI's interventional pain lexicon recognizes spinal levels from C2 through S1, laterality, and procedure type, including medial branch blocks, radiofrequency ablation, and transforaminal or interlaminar epidurals. It also captures spoken scale values like 'pain eight out of ten' or 'ODI forty percent.' Each element maps to a discrete field plus a narrative sentence, so coders do not have to infer details from prose.
Response to prior injections is captured as magnitude and duration, for example '70 percent relief for three weeks.' Structured capture of prior response supports repeat injection and radiofrequency ablation coverage decisions.
Direct DOM injection populates CareCloud procedure templates without an interface build or retyping
The three available documentation pathways differ sharply in cost, setup burden, and how much discrete pain data reaches the template.
| Criterion | Traditional API Marketplace Integration | Manual Copy-Paste | Merry AI Chrome DOM Injection |
|---|---|---|---|
| Setup requirement | Vendor contract, interface build, IT project | None | Chrome Extension install |
| Cost model | Marketplace and per-interface fees | Clinician time | No API or marketplace fees |
| Target location in CareCloud | Often a general document or progress note | Wherever the clinician pastes | Specific procedure, Vitals, and E/M fields |
| Discrete pain score, levels, guidance | Limited to fields the interface exposes | Retyped by hand | Auto-populated as discrete values |
| Firewall or server changes | Typically required | None | None |
| Time to deploy | Weeks to months | Immediate | Same-day onboarding |
| Audio and transcript retention | Varies by vendor | Not applicable | Zero retention under executed BAA |
| Clinician attestation | Required | Required | Required before chart commit |
General ambient scribes often stop at a separate note editor or a document-level export. That leaves clinicians to move spinal levels and pain scores into CareCloud procedure templates by hand, which is the exact step where errors and lost time accumulate.
Section separation protects Modifier 25 and respects NCCI fluoroscopy bundling
Modifier 25 requires a significant and separately identifiable E/M service beyond the usual pre-procedure work. Merry AI structures each same-day note with distinct Evaluation and Management and Procedure sections. Medication management, risk discussion, and treatment planning sit in the E/M section. Fluoroscopic guidance, levels, and needle placement stay in the procedure section, so routine pre-procedure assessment is not presented as separate E/M work.
Fluoroscopic guidance is documented, not separately billed, when the primary code already includes it. NCCI policy states that when a code descriptor includes imaging guidance, separate guidance codes such as 77003 or 76000 may not be reported. Facet joint injection codes 64490 through 64495 and the imaging-guided epidural codes 62321 and 62323 include guidance in their descriptors. Merry AI records guidance confirmation for medical necessity and patient safety, and it never generates language implying a separately billable radiology service.
When distinct procedures occur on the same date at separate sites or levels, the extension delineates each procedure's indication, site, and timing so the coding team can evaluate Modifier 59 or XS. Merry AI surfaces structured data for coders. It does not apply modifiers automatically.
G2211 capture depends on documenting the longitudinal pain management relationship
HCPCS G2211 is an add-on to office and outpatient E/M codes 99202 to 99205 and 99211 to 99215, and to home or residence E/M codes, when the clinician serves as the continuing focal point for care or manages a single serious or complex condition, per the CMS G2211 FAQ. In interventional pain, that means longitudinal chronic pain management that coordinates medications, therapy, imaging, and interventions over time, not one-off injection visits.
CMS pays G2211 with Modifier 25 only in limited circumstances, such as when the same-day service is an annual wellness visit, vaccine administration, or a Medicare Part B preventive service. A same-day injection visit billed with Modifier 25 generally does not support G2211. Merry AI surfaces longitudinal complexity elements, including comorbidities, high-risk medications such as opioids, and recurring imaging and interventions, on the E/M visits where G2211 applies. The final coding decision stays with the clinician and coder.
Manchikanti and colleagues, writing in Pain Physician in 2023, describe three decades of confusion over E/M documentation in interventional pain practice (PubMed 37976475). Structured, section-aware capture addresses that confusion directly at the point of care.
Merry AI assists documentation and never makes medical necessity determinations
California SB 1120 prohibits health plans from using AI, algorithms, or software to deny, delay, or modify care based on medical necessity without licensed clinician determination. Merry AI is a clinician-assist tool. It captures the physician's own medical necessity reasoning, such as why fluoroscopy was required or why specific levels were chosen, and it never suppresses or alters orders.
Practices that reuse drafts in patient-facing messages should also note California AB 3030, which requires a generative AI disclosure unless a licensed provider reviews the content. Every Merry AI draft is clinician-reviewed before use, and every auto-inserted field is logged for audit.
Clinician attestation remains the final control on every CareCloud note
No injected content becomes part of the legal record until the clinician reviews, edits, and signs it in CareCloud. Audio is processed and discarded, and no audio or transcript is retained under an executed BAA. Pain psychology or psychotherapy content, when present, uses a segregated template and never merges into procedure or E/M fields.
To see this workflow on your own procedure templates, start with Access 1,000+ EHR Clinical Templates or Schedule a 15-Minute Workflow Audit.




