TL;DR: NextGen Encompass stores its ophthalmic widgets (Visual Field canvas and OD/OS IOP fields) inside a shadow DOM. Values only persist when masked inputs and the VF canvas receive proper focus/blur/change events. Scribing.io's Specialty Connector traverses the shadow-root, performs coordinate-accurate UI injection, normalizes mmHg per eye, and fires Encompass-native commit events—writing discrete, audit-safe OD/OS IOP and Visual Field data that drive coding, MIPS eCQM numerator capture, and clean claims. This bypasses the $5,000 native integration surcharge. Below: the clinical decision logic, ICD-10 reference, and the technical "information gain" the CMS billing documentation never addresses.

• Jump to section Discrete Mapping Overview

• Jump to section Glaucoma Suspect Clinical Logic

• Jump to section Shadow DOM Problem Explained

• Jump to section ICD-10 Documentation Standards

• Jump to section Deployment and Pricing Path

NextGen Encompass Integration: Discrete Ophthalmic Mapping

NextGen Encompass Integration: Why Discrete Ophthalmic Mapping Determines Reimbursement

CLINICAL UPDATE 2026: Revised for new CMS CPT G2211 standards, SB 1120 compliance, and FHIR interoperability.

For a Clinical Operations Director, the gap between "documented" and "discrete" is the gap between a paid claim and a $3,200 denial. CMS billing and coding articles (such as A57600) tell you which ICD-10 codes support medical necessity for ophthalmic imaging. They are silent on the single failure mode that sinks ophthalmology claims in practice.

NextGen Encompass renders ophthalmic widgets—the Visual Field (VF) plotting canvas and the OD/OS intraocular pressure (IOP) inputs—inside a shadow DOM. Standard scribe tools and copy-paste workflows dump prose into the encounter note. Scribing.io was built to reach the shadow-root those tools never touch.

Scribing.io's Specialty Connector closes exactly this gap between narrative documentation and discrete field capture. Explore the full EHR Integration Library for build-specific mapping profiles, or review the Clinical Specialties Directory for ophthalmology-tuned profiles.

Scribing.io Clinical Logic: The Glaucoma Suspect Whose Data Never Became Discrete

This is the scenario that converts a demo, because every ophthalmology billing lead has lived it.

The clinical situation: A 68-year-old glaucoma suspect presents with a Humphrey Visual Field mean deviation of -6.2 dB OS and IOP of 26 mmHg OD / 24 mmHg OS. The provider verbally documents everything and the scribe writes it into the note body. Clinically, the encounter is airtight.

The failure mode is structural: the values land only in narrative prose. Encompass's discrete OD/OS IOP fields and Visual Field data structure remain empty. Consequently, the downstream engines see nothing.

• The payer audit rejects the claim—the submitted record cannot substantiate the coded service with discrete data.

• The MIPS eCQM for glaucoma fails because the numerator logic queries structured fields, not free text.

• The financial result compounds: a $3,200 denial plus lost quality credit in the same encounter.

How the Specialty Connector Resolves It

With Scribing.io, the Connector executes a deterministic five-step sequence against the mapped build.

1. Maps the clinic's specific Encompass build, identifying the exact shadow-root DOM targets for OD/OS IOP and the VF canvas.

2. Injects OD/OS mmHg (26/24) into the masked input fields with coordinate accuracy.

3. Plots VF points and writes the MD (-6.2 dB OS) into the correct structured element via coordinate-based UI injection.

4. Fires the same focus/blur/change and commit events Encompass expects, so the platform persists the values as discrete data rather than discarding them.

5. Writes audit-safe discrete fields that drive coding, eCQM numerator capture, and claim approval.

Quantify the recovery for your own encounter volume with the AI Medical Scribe ROI Calculator.

The Shadow DOM Problem CMS Guidance Never Addresses

Payer coverage articles like A57600 exhaustively enumerate which ICD-10 codes support medical necessity and how often CPT 92132/92133/92134 may be reported. What they cannot address is the mechanical reason ophthalmic data fails to reach the claim.

What the competitor documentation misses: NextGen Encompass renders ophthalmic widgets inside a shadow DOM, and it only persists values when the masked inputs and VF canvas receive proper focus/blur and change events. A tool that writes to the visible note—or even the light DOM—never triggers persistence. The data evaporates on save.

The Anchor Truth of the Connector: Scribing.io traverses the shadow-root, performs coordinate-accurate clicks for VF plotting, normalizes mmHg per eye, and emits Encompass-native commit events. The 'Visual Field' and 'IOP' DOM elements save as discrete data via coordinate-based UI injection.

This is why the same result is achievable without the $5,000 native integration surcharge. The Connector operates at the UI layer Encompass already trusts, rather than requiring a paid backend interface build.

Technical Reference: ICD-10 Documentation Standards

Discrete capture is only valuable when it maps to correctly specified diagnosis codes. For the ocular hypertension and visual field defect scenarios central to glaucoma-suspect workflows, the two reference codes below are the most frequent audit touchpoints.

The laterality lesson holds firmly: unspecified codes survive a human glance but weaken audit posture. Discrete OD/OS capture lets coders resolve H40.059 to a specified laterality and lets the VF structure substantiate H53.40 with real MD data.

Deployment Path and Pricing Alignment

Deployment follows the mapped-build model, not a generic template. The Connector profile is built against your clinic's exact Encompass DOM structure before any live encounter injection occurs.

• Build discovery identifies shadow targets for the VF canvas and OD/OS IOP masked inputs.

• Coordinate calibration verifies plotting accuracy against your VF widget render dimensions.

• Commit-event validation confirms persistence across save and audit-export cycles.

Review deployment tiers and per-provider economics on Scribing.io Pricing & Plans, and confirm state documentation rules through the AI scribe compliance reference.

The operational takeaway is direct: discrete ophthalmic mapping is not a documentation preference. It is the mechanical prerequisite for clean claims, MIPS numerator capture, and audit survival in NextGen Encompass.