A Documentation Workflow Built for Greenway Intergy / Prime Suite
Clinical documentation inside Greenway Intergy rarely fails because clinicians lack dedication—it fails because the note architecture demands manual routing of narrative into discrete sections. Greenway's ambulatory platform, spanning Intergy v22 and Prime Suite v22 (the ONC-certified minimum for HTI-1 requirements, with Prime Suite certified August 14, 2025 under ID 15.04.04.2913.Prim.22.04.1.250814), supports configurable templates, structured orders, diagnoses, medications, and narrative documentation. The interoperability plumbing is mature; the human bottleneck is the click-and-type labor of moving spoken encounter data into the right editor.
Merry AI addresses that bottleneck by treating each note section as an addressable destination rather than a monolithic text dump. Our browser-native Chrome Extension maps ambient-scribe output directly to the rendered DOM input selectors that clinicians already see: the HPI editor, ROS controls, examination fields, the assessment/problem area, and the plan editor. This preserves the semantic separation Greenway's own organization depends on, without a single marketplace contract or per-transaction fee.
Because this operates at the browser layer, general-practice and multispecialty groups deploy in minutes. There is no interface engine to commission, no FHIR endpoint to provision, and no queue latency between dictation and chart. The tradeoff we disclose plainly: DOM injection is a controlled automation layer, not a vendor-authorized transaction, so we validate persistence rather than assume it.
Why DOM Injection Beats API Marketplaces and Copy-Paste
Closed and semi-closed ambulatory EMRs often gate write access behind developer certification, contractual negotiation, and limited write scopes—months of overhead before a single note lands in a chart. Even where Greenway exposes FHIR infrastructure for Intergy and Prime Suite data, standardized exchange interfaces are frequently better suited to downstream data movement than to real-time, section-by-section note composition at the point of care.
Manual copy-paste, the fallback most clinics tolerate, produces poor field fidelity and elevates the risk of wrong-section placement. Pasting an entire encounter into a single free-text box collapses the HPI, ROS, exam, and plan into an undifferentiated block, degrading reviewability and defeating the EHR's structured design. Merry AI's DOM approach sits between these extremes—fast like paste, but section-aware like an API.
| Architecture | Deployment Overhead | Latency | Field Fidelity | Annual Fee |
|---|---|---|---|---|
| Traditional API Marketplace | High — contracts, certification, IT provisioning | Queue/sync delay | Good persistence, limited write scope | Per-transaction + platform fees |
| Manual Copy-Paste | None | Human-speed | Poor — single-block risk | $0 (hidden labor cost) |
| Merry AI DOM Injection | Minimal — browser extension only | 0.4s streaming | Section-mapped, validated | No API or marketplace fees |
The strategic distinction is deployment velocity without sacrificing structure. Merry AI dispatches native input and change events into each mapped field so Intergy and Prime Suite register the content as a genuine keystroke sequence, then fails closed when a selector cannot be confidently resolved—protecting against silent writes to the wrong encounter.
Visual Placement Versus Native Data Capture
A field can appear structured in the interface while actually persisting as narrative text in the underlying database, and DOM injection can occasionally bypass internal application events. We never conflate visible placement with native capture. For every mapped field, our validation confirms the content persists in the intended data element, appears in the longitudinal chart, survives export and C-CDA or FHIR exchange, and records the correct audit trail against the responsible author.
The Versioned Field-Mapping Matrix
Our field map is a living configuration artifact, not a universal Intergy schema. Each entry records product (Intergy or Prime Suite), exact build, tenant configuration, specialty, encounter type, template revision, the DOM selector, the expected event sequence, a persistence test, and defined failure and rollback behavior. Chief complaint routes to the encounter complaint field; HPI to the HPI editor; ROS to its controls; vitals only to structured vital-sign observations—never as visual text alone. We prefer stable attributes over brittle labels, coordinates, or autogenerated IDs, and we re-run regression after every vendor release, browser update, and template edit.
Preserving E/M Integrity and Capturing CPT G2211
The 2021 E/M framework shifted documentation emphasis toward medical decision-making and total time, a change the AMA advanced specifically to reduce the administrative burden that consumes roughly a third of physician EHR time. Merry AI's structured routing supports that framework by placing assessment complexity and time-based elements where Greenway's coding logic can read them, rather than burying them in free text.
CPT add-on code G2211, effective January 1, 2024, captures the inherent complexity of visits that serve as the continuing focal point for a patient's care or ongoing management of a single serious or complex condition. Per CMS guidance, it is not specialty-restricted—any professional billing office/outpatient E/M codes 99202–99215 may report it when the longitudinal relationship criteria are met. Merry AI surfaces and structures the relationship context that justifies G2211, so primary-care and multispecialty clinicians document the continuity that supports the claim. Consult peer-reviewed guidance at https://www.ncbi.nlm.nih.gov/pmc/ alongside CMS transmittals when operationalizing G2211 capture.
Copy-forward behavior deserves particular vigilance in general-practice and multispecialty charts, where historical content is easily mistaken for current findings. Merry AI distinguishes information stated by the patient or clinician from inferred content, flags anything requiring confirmation, and never fabricates negatives, exam findings, or counseling. Access 1,000+ EHR Clinical Templates pre-structured for clean section mapping across specialties.
Security, HIPAA, and the DOM Threat Model
Any workflow handling protected health information must address business associate agreements, minimum-necessary access, role-based control, unique user attribution, encryption in transit and at rest, audit logging, and enforced data-retention rules. Merry AI operates under an executed BAA with zero retention of audio, transcripts, or intermediate drafts, and model training on customer PHI is contractually prohibited and technically enforced.
DOM injection introduces specific threats we engineer against: a broad-permission extension could expose unrelated patient data, injected scripts could conflict with the EHR's own JavaScript, and content could land in the wrong chart after a session switch. Our controls are least-privilege browser permissions, explicit patient- and encounter-context verification before every injection, content isolation, tamper-evident logs, and a fail-closed response whenever a target field cannot be identified with confidence.
We also acknowledge the information-blocking dimension of the 21st Century Cures framework. Because Merry AI preserves provenance and authorship, enables clinician review and correction, and never alters data in a way that cannot be exported or exchanged, it strengthens rather than impairs certified functionality. Explore Merry AI Practice Partner Plans to review the full governance posture.
Production Validation and Getting Started
A production-readiness study for your organization begins with a version and template inventory—Intergy or Prime Suite build, deployment model, browser, and every general-practice and specialty template variant. From there we execute field-level mapping, persistence testing (save, sign, reopen, search, export, exchange), and negative testing against wrong-patient, expired-session, missing-field, duplicate-submission, and partial-load conditions.
Structured-data verification is the non-negotiable acceptance criterion. Success is not that text appeared in the right place—it is that after clinician review and save, the content is persistently bound to the correct patient and encounter, represented in the intended data type, visible to downstream workflows, auditable to the responsible user, and correctable without corrupting the record. Clinical, HIM, compliance, and IT security stakeholders each sign off before go-live.
Merry AI treats every generated draft as clinical content pending clinician review and signature; automatic signature is disabled unless your organization establishes a separate compliant policy. This keeps the clinician firmly as the author of record. To map your exact Intergy or Prime Suite configuration and quantify the documentation-time recovery, Schedule a 15-Minute Workflow Audit.
