Why Nephrology Documentation Is Longitudinal
Chronic kidney disease rarely resolves within a single encounter. A stage 3b patient seen in March is the same patient seen in September, carrying the same albuminuria category, the same SGLT2 inhibitor question, and often a new potassium value that changes the ARB plan. The nephrologist is frequently the continuing focal point for renal care, and the chart should say so plainly rather than leave an auditor to infer it from scattered lab flowsheets.
HCPCS G2211 was written for exactly this relationship. CMS describes it as an add-on for visit complexity inherent to ongoing care of a single, serious or complex condition, reported with office/outpatient codes 99202 to 99205 and 99211 to 99215, and with home or residence codes 99341, 99342, 99344, 99345, and 99347 to 99350. No specific diagnosis code is required. What matters is evidence that the clinician has assumed, and intends to continue, longitudinal responsibility.
Most ambient scribes treat each visit as an isolated transcript. That serves a sore throat well. It does not serve a transplant recipient whose creatinine has drifted over four visits, or a peritoneal dialysis patient whose care is shared with a facility team, a cardiologist, and a renal dietitian.
Building a Defensible G2211 Attestation
Merry listens for longitudinal CKD cues during the encounter: prior eGFR values, KDIGO stage, dialysis modality, transplant status, and named coordinating clinicians. When temporal, clinical, and coordination signals together meet a configurable threshold, Merry drafts a short attestation. When they do not, as in a first-time consult with no planned follow-up, it drafts nothing.
eGFR Trajectory and KDIGO Staging
The attestation states the trend in numbers, not adjectives. A typical draft reads: Ongoing management of CKD G3b/A2. eGFR 41 to 34 mL/min/1.73m2 over 14 months across five nephrology visits; UACR 180 mg/g. Continuing SGLT2 inhibitor and ARB titration with potassium monitoring. Each value comes from what was said or reviewed during the visit, and each remains editable before signature. The ICD-10 code, such as N18.32 for stage 3b, should match the documented stage, which you can confirm at https://www.cms.gov/medicare/coding-billing/icd-10-codes.
Coordinating Specialists and Dialysis Facilities
Coordination is the second pillar reviewers look for. Merry captures named partners when they are discussed: the primary care physician adjusting metformin, the cardiologist managing cardiorenal overlap, the transplant center reviewing tacrolimus troughs, and the dialysis facility social worker addressing transportation. The attestation summarizes these relationships in one sentence, which is usually enough to show that nephrology is integrated with the broader care team.
Modifier 25 Suppression Logic
CMS generally denies G2211 when the associated E/M carries modifier 25, with narrow exceptions for certain same-day preventive services such as the annual wellness visit and vaccine administration. Same-day procedures therefore trigger suppression, and Merry flags the claim for the billing team. G2211 also never attaches to ESRD monthly capitation codes 90951 to 90970, which are not qualifying E/M base codes.
| Specialty Diagnostic Metric | Required Clinical Data Points | Billing Evidence |
|---|
| eGFR trajectory | Dated serial eGFR values, visit count, interval in months | Longitudinal complexity for G2211 |
| KDIGO stage and albuminuria | G1 to G5, A1 to A3, UACR in mg/g | ICD-10 N18.1 to N18.6 specificity |
| Dialysis or transplant status | HD or PD modality, access type, immunosuppressant levels | Single serious condition narrative |
| Care coordination | Named PCP, cardiology, transplant center, facility team | Continuing focal point attestation |
| Same-day procedure check | Procedure CPT, modifier 25 status, preventive exception | G2211 suppression or billing flag |
The matrix reflects how a careful department chair reviews a chart: data first, narrative second, billing logic last. Nothing in the attestation should exist only to justify a code.
DOM Verification Before Every Visit
Merry's Chrome Extension writes directly into the Assessment/Plan field of browser-based EHRs. There is no API contract, no interface engine, and no IT ticket. Because these editors often run as single-page applications with shifting element IDs, Merry anchors to visible labels and ARIA roles such as Assessment and Plan rather than brittle selectors.
Before each visit, the extension verifies its target. It reads the patient name, MRN, and encounter identifier from the chart header and binds the draft to that context, so an attestation built for one patient cannot land in a neighboring tab. It checks for an existing attestation to prevent duplication and inserts visible, editable text at the end of the assessment, never hidden markup. When an iframe blocks direct access, Merry falls back to a clinician-initiated paste.
Compliance, Retention, and State AI Law
Every insertion is logged outside the EHR with encounter identifier, timestamp, template version, and the longitudinal cues that justified it. Audio and transcripts are processed in memory and shredded after the session closes, under an executed Business Associate Agreement. The log supports payer audits and Texas AI-use reporting, while AB 3030 disclaimer toggles apply whenever drafted language reaches patient-facing summaries in California.
Specialty prompt packs for nephrology, including CKD follow-up, home dialysis reviews, and post-transplant visits, are available at https://templates.scribing.io. They provide a predictable starting structure, and the attestation is always the clinician's to accept, revise, or delete. The signature remains with the physician, as it should.