Allergy and Immunology Ambient Scribe Playbook

Why the Allergy Shot Room Needs Two Narratives

Clinical documentation in Allergy and Immunology carries a structural tension that most ambient tools never resolve. A single Tuesday afternoon may include forty maintenance injections under CPT 95115 or 95117, a handful of percutaneous panels under 95004, and one patient whose asthma has quietly worsened since the last visit. Under NCCI policy and CMS article A57472, the routine pre-injection screen, informed consent, and standard post-injection observation belong to the immunotherapy service itself. They do not justify a separate evaluation and management code.

The difficulty is not clinical but architectural. When an ambient scribe writes one composite note, the vial verification, dose escalation, and wheal measurement sit beside the new nocturnal cough and the step-up in controller therapy. A payer reviewer reading that blended narrative cannot easily see where the injection ended and the separately identifiable visit began. Merry AI treats these as two distinct narratives from the first second of the recording and routes each into its own EHR field.

The Allergy and Immunology Clinical Logic Matrix

Every billing decision in allergy ultimately rests on whether the chart shows measurable data tied to a distinct plan. The matrix below reflects the indicators Merry extracts from ambient dialogue and the evidence each one contributes to a defensible claim.

Diagnosis codes must match narrative. Clinicians can verify current code descriptors through the https://www.cms.gov/medicare/coding-billing/icd-10-codes reference before attestation. Specialty prompt packs that reproduce this matrix inside the note template are available at https://templates.scribing.io.

How Merry Gates Modifier 25 and G2211

Merry segments each transcript into two labeled streams: immunotherapy administration and new or exacerbated problem evaluation. Its scoring model then reads the evaluation stream alone for problems addressed, data reviewed, and risk, asking whether that content would support a 99213 or 99214 even if no injection had occurred that day.

Directive One: A Separately Identifiable Problem

Modifier 25 is suggested only when a separately identifiable problem beyond injection reaction review has been evaluated. Reviewing a 12 mm local wheal, confirming no interval symptoms, and administering the scheduled dose is the injection service. Evaluating new wheeze with an ACT of 14, reviewing spirometry, and adding a LABA to inhaled corticosteroids is a separate visit. Merry draws that line explicitly and states its reasoning in the suggestion panel so the clinician can accept or reject it.

Directive Seven: The Empty Assessment Rule

The Chrome Extension suppresses modifier 25 whenever the Assessment field of the E/M note is empty. A visit without a documented assessment cannot carry separate medical decision making, regardless of how long the conversation ran. If a clinician attempts to append modifier 25 manually to a shot-only encounter, Merry displays a quiet flag noting that no distinct assessment exists. The same logic flags modifier 59 when multiple immunotherapy codes appear without documented distinct sessions.

G2211 Longitudinal Complexity Boundaries

Longitudinal complexity add-on code G2211 fits allergy practice well, since many patients are followed for years through biologic therapy and immunotherapy courses. CMS does not pay G2211 when the base E/M carries modifier 25 alongside a same-day procedure such as allergen immunotherapy, with narrow exceptions limited to preventive services. Merry therefore surfaces G2211 on standalone follow-up visits where the allergist is the continuing focal point, and withholds it on injection days billed with modifier 25.

Chart Delivery, Audit Trail, and Attestation

Merry writes each narrative into its mapped DOM field: the immunotherapy log into the procedure section and the evaluation into Subjective, Objective, and Assessment and Plan. Selector maps are versioned per EHR release, and when cross-origin iframes block direct writes, the clinician chooses the destination explicitly so separation is preserved.

Every field-level write is logged with timestamp, field identity, text hash, and any coding suggestion shown. That record allows a practice to demonstrate that modifier 25 recommendations were conditioned on separate MDM, and it supports transparency expectations emerging under California AB 3030 and SB 1120 and Texas HB 1709. Merry never creates orders, diagnoses, or codes on its own; every suggestion waits for clinician confirmation.

The result is a quieter afternoon in the shot room and a chart that reads the way a careful auditor expects it to read. Allergists who want to see their own injection-day encounters mapped against this logic can request a fifteen-minute workflow audit.