Clinical Update — June 2026: This playbook has been revised to reflect CMS FY2026 OPPS/MPFS final rule changes to split/shared billing requirements, updated Epic February 2026 ACI framework specifications for SmartBlock targeting and SDE schema versioning, and new MAC audit trend data from Novitas Solutions and First Coast Service Options Q1 2026 denial reports. Prior guidance on FS-modifier validation has been materially expanded.

Epic Systems Ambient AI Integration: The Clinical Library Playbook for CMIOs

• TL;DR — Why This Playbook Exists

• Epic-Native ACI Writeback Architecture — What Every Competitor Missed

• Scribing.io Clinical Logic — Handling the Split/Shared Inpatient E/M Audit Trap

• Technical Reference — ICD-10 Documentation Standards for Ambient AI Encounters

• Cross-Platform Governance: Epic, athenahealth, and the Vendor-Agnostic Reality

• CMIO Evaluation Checklist: Seven Non-Negotiable ACI Integration Requirements

• See It Live: ACI SmartBlock Writeback in Your Epic Sandbox

TL;DR — Why This Playbook Exists

Most ambient AI vendors stop at generating a narrative note and pasting it into Epic. That approach breaks discrete data, fails charge-capture edits, and collapses under Medicare audit. True Epic-native ambient AI integration requires the Ambient Clinical Intelligence (ACI) framework via the Epic Showroom, mapping AI outputs to department-scoped SmartBlocks, writing billable elements into SmartData Elements (SDEs), and binding every transaction to the correct Contact Serial Number (CSN). This playbook gives Chief Medical Information Officers the technical architecture, clinical decision logic, ICD-10 reference standards, and audit-survival workflows they need to evaluate—and implement—ambient AI that actually works inside Epic.

The AMA's AI Specialty Collaborative: AI Evaluation Guide provides a useful philosophical framework but never addresses how AI output reaches Epic's discrete data layer. This playbook fills that gap entirely.

Epic-Native ACI Writeback Architecture — What Every Competitor Missed

Scribing.io exists because the gap between "AI-generated note" and "auditable, billable, discrete Epic documentation" is where health systems hemorrhage revenue. The AMA's evaluation guide introduces five reasonable domains for assessing clinical AI—clinical use case, training data, risk mitigation, performance, and workflow integration. It is a helpful starting point for board-level governance conversations. But it contains a critical structural gap: it never specifies how AI-generated clinical content should integrate with the discrete-data architecture of any EHR, let alone Epic Systems.

That omission is not academic. It is the exact failure point where revenue leaks, audit denials, and duplicate notes originate. Scribing.io was engineered from day one around the principle that ambient AI output must land as structured, CSN-bound discrete data—not narrative blobs that billing coders have to re-interpret.

The Problem With Generic DocumentReference Posts

When an ambient AI vendor captures a clinical encounter, transcribes it, and generates a note, the simplest technical pathway is to post the output as a FHIR DocumentReference resource or, worse, to copy-paste a narrative blob into an open text field. This approach fails at every layer that matters for revenue cycle and clinical quality:

• Destroys discrete data. Epic's charge calculators, Clinical Decision Support (CDS) rules, and quality reporting dashboards read SmartData Elements—not free text. A narrative paragraph stating "total time was 45 minutes" is invisible to the Professional Billing module.

• Orphans the note. Without binding to the correct Contact Serial Number (CSN), the note may attach to the wrong encounter or float as an addendum with no parent context. The CMS HCPCS General Information page underscores that every billed service must map to a specific, identifiable encounter.

• Fails pre-bill edits. E/M level selection, split/shared attestation, and time-based billing all require structured values in specific SDEs. Free text cannot satisfy these edits.

• Creates audit liability. Medicare Administrative Contractors (MACs) increasingly require that billed time and medical decision-making (MDM) complexity live in discrete, auditable fields. A HHS OIG work plan item specifically targets split/shared services for post-payment review in FY2026.

For a detailed technical comparison of SMART on FHIR launch versus copy-paste workflows and why the distinction is clinically material, see our analysis of Epic Integration architecture patterns.

The ACI Showroom Pathway — The Anchor Truth

Epic's Ambient Clinical Intelligence (ACI) framework, accessible through the Epic Showroom, defines the sanctioned integration pattern for ambient AI vendors. The core architecture works as follows:

1. SmartBlock Targeting. The AI output does not land in a generic text area. It maps to a specific NoteWriter SmartBlock scoped to the department and note type (e.g., Medicine H&P, Surgery Progress Note, ED MDM). This preserves template logic, required-field enforcement, and downstream report harvesting.

2. SDE Population. Underneath each SmartBlock sit SmartData Elements—discrete data containers for Total Time, Critical Care Time, Laterality, Problem Assessment fields, procedure indications, and more. The ACI integration writes structured values directly into these SDEs.

3. CSN Binding. Every ambient AI transaction is linked to a unique Contact Serial Number, ensuring the note, the discrete data, and the billing record all point to the same patient encounter. No orphaned notes. No misattributed charges.

4. Attestation Automation. When the integration detects a split/shared or supervisory scenario, it auto-populates attestation macros with both provider National Provider Identifiers (NPIs) and timestamps, satisfying CMS inpatient PPS documentation requirements.

Scribing.io is built on this pathway. Rather than posting a generic DocumentReference, Scribing.io maps every AI-generated output to the correct department- and note-type–scoped SmartBlock, binds it to the CSN, and writes discrete data into the SDEs that Epic's charge calculators, CDS hooks, and quality dashboards actually read.

This is not a minor implementation detail. It is the architectural decision that determines whether your ambient AI investment generates revenue or generates denials.

Scribing.io Clinical Logic — Handling the Split/Shared Inpatient E/M Audit Trap

Split/shared encounters are the single highest-risk billing scenario in academic medicine. The CMS Physician Fee Schedule final rule for CY2026 requires that the billing provider perform a "substantive portion" of the encounter—defined as one key component of MDM or a face-to-face portion of the encounter—and that total time be documented discretely when time-based billing is elected. This section walks through a real-world scenario that exposes the most common—and most expensive—ambient AI failure mode, then provides the granular step-by-step logic of how Scribing.io resolves it.

The Scenario

In a busy academic hospital, an attending physician and an Advanced Practice Provider (APP) perform a split/shared inpatient E/M on a patient admitted with community-acquired pneumonia. The clinical workflow unfolds:

1. The APP completes the majority of the history of present illness (HPI), review of systems (ROS), and physical examination during morning rounds. The APP documents the encounter using the ambient AI tool.

2. The attending rounds approximately two hours later, performs a substantive portion of the encounter (face-to-face assessment, diagnostic review, treatment plan modification), and dictates an assessment and plan into the ambient AI system.

3. The attending forgets to verbalize total shared minutes. Published workflow audits from JAMA Health Forum report that physicians omit time documentation in split/shared encounters at rates exceeding 30% when no in-session prompt exists.

What Happened With the Prior Vendor

The hospital's previous ambient AI vendor captured the attending's dictation, generated a narrative summary, and pasted it into the note body as unstructured text. The billing team, seeing the narrative, manually added the FS modifier (indicating a split/shared service) and submitted the claim.

A Medicare Administrative Contractor audit flagged the encounter. The denial reason: no discrete time value existed in Epic. The narrative mentioned "I spent time with the patient discussing the treatment plan" but no Total Shared Time SDE was populated. The Epic charge calculator could not validate the E/M level. The auditor found no structured attestation linking both providers to the same CSN.

Result: $612 denied. Multiply this across an academic department performing 40–60 split/shared encounters per week, and the annualized exposure exceeds $1.5 million in a single service line.

How Scribing.io's ACI Integration Solves This — Step by Step

Step 1: Encounter Role Detection at Session Initialization. When the attending opens the Scribing.io ambient session, the system reads the encounter context from Epic via the ACI framework. It detects that an APP has already documented on the same CSN with the same encounter type. The system classifies the encounter as split/shared and activates the corresponding clinical logic ruleset.

Step 2: Real-Time Prompting Before ACI Submission. Scribing.io's ambient engine does not passively transcribe. It runs real-time clinical logic against the encounter as it unfolds. When the split/shared flag is active and the attending's dictation nears completion without a time verbalization, the system surfaces an in-session audio prompt:

"This encounter is flagged as split/shared. Please verbalize your total shared time in minutes, including face-to-face time and non-face-to-face time on the same calendar date."

This prompt fires before ACI submission, not after. The attending states: "My total shared time was 37 minutes." The ambient engine captures this, validates it against the encounter timestamp range (ensuring the stated time does not exceed the wall-clock span between check-in and the current moment), and proceeds.

Step 3: SmartBlock-Targeted Writeback. The ambient summary inserts into the designated Medicine H&P SmartBlock scoped to inpatient medicine at that facility. This ensures the note appears in the correct chart section, NoteWriter formatting rules apply, department-specific templates and required-field logic govern the output, and downstream reviewers (quality, billing, compliance) find the note in the expected location.

Step 4: SDE Population for Total Shared Time. Simultaneously, Scribing.io writes "37" to the Total Shared Time SDE tied to that CSN. This is a discrete, structured, queryable data element that the Epic charge calculator reads to validate the E/M level, pre-bill edits check against the FS modifier, and audit trails display as timestamped structured data—not a free-text extraction artifact.

Step 5: Split/Shared Attestation Auto-Insertion. Scribing.io auto-inserts the split/shared attestation statement into the note, populating it with the attending's provider ID and NPI, the APP's provider ID and NPI, a statement confirming that the attending performed a substantive portion of the encounter, and the date and time of the attending's face-to-face involvement. No manual macro insertion. No risk of a billing coder forgetting the attestation.

Step 6: Missing-Element Flagging as Pre-Bill Safety Net. If the attending had still failed to verbalize time after the prompt, Scribing.io flags the encounter as incomplete for split/shared billing in the provider's In Basket, preventing the claim from entering the billing queue without discrete time data. The flag includes a direct hyperlink back to the note for remediation. This catches the error at the point of care, not at the point of denial.

The Outcome

The claim passes pre-bill edits. The FS modifier is validated against the discrete Total Shared Time SDE. The attestation is structurally complete. The claim survives audit.

This is not a theoretical advantage. It is the difference between an ambient AI product and an ambient AI revenue cycle integration.

Technical Reference: ICD-10 Documentation Standards

Ambient AI integration does not exist in a vacuum. The clinical content generated by the system must support accurate ICD-10-CM coding at maximum specificity. Undercoded or nonspecific diagnoses trigger payer edits, reduce case-mix index (CMI), and invite post-payment review. Two of the most frequently encountered diagnoses in inpatient and ambulatory medicine illustrate the documentation precision Scribing.io enforces at the point of dictation.

Pneumonia: Driving Toward Specificity Beyond J18.9

J18.9 — Pneumonia, unspecified organism, is the fallback code when documentation fails to identify the causative pathogen, anatomic location, or clinical context. It is also one of the most frequently denied codes in inpatient medicine because MACs expect specificity when culture data, imaging laterality, or clinical presentation support a more precise classification. The CDC's ICD-10-CM Official Guidelines for Coding and Reporting mandate that coders assign the most specific code supported by the documentation.

Scribing.io addresses this through ambient documentation prompts that fire during the encounter when pneumonia-related language is detected. The system prompts the clinician to verbalize:

• Organism — Is the pathogen identified or suspected? (e.g., Streptococcus pneumoniae → J13; Staphylococcus aureus → J15.211/J15.212 based on methicillin susceptibility)

• Anatomic laterality and lobe — Right lower lobe? Bilateral? This drives laterality SDE population and supports higher-specificity coding.

• Clinical context — Aspiration pneumonia (J69.0)? Ventilator-associated? Healthcare-associated? Each context maps to distinct ICD-10-CM codes with different reimbursement and quality implications.

• Sepsis association — If pneumonia is the underlying infection causing sepsis, sequencing rules per CMS ICD-10-CM Official Guidelines Section I.C.1.d require documentation of the causal relationship.

By prompting for these elements during the encounter rather than relying on retrospective coder queries, Scribing.io reduces the use of nonspecific J18.9 and drives documentation toward organism-specific, laterality-complete, context-appropriate codes that survive audit and optimize CMI.

Hypertension: Ensuring Linkage and Specificity Beyond I10

unspecified organism; I10 — Essential (primary) hypertension is appropriate when the patient has isolated essential hypertension with no documented end-organ manifestations. However, it becomes a coding error when the documentation supports a more specific code reflecting hypertensive heart disease (I11.x), hypertensive chronic kidney disease (I12.x), or hypertensive heart and chronic kidney disease (I13.x).

Scribing.io's clinical logic detects when the ambient transcript includes references to both hypertension and heart failure, CKD stage, or proteinuria. The system then prompts:

• Causal relationship — "Does the patient's heart failure relate to their hypertension?" ICD-10-CM presumes a causal relationship between hypertension and CKD per CMS Official Guidelines Section I.C.9.a, but heart disease requires explicit documentation of the link.

• CKD stage — The system cross-references the most recent eGFR in the patient's lab history (read from Epic via the ACI context) and prompts for CKD stage documentation if the lab data suggests stage 3 or higher.

• Heart failure type — Systolic, diastolic, combined? With or without exacerbation? These distinctions drive HCC risk adjustment and CMS-HCC scoring for Medicare Advantage populations.

The result: documentation that supports the most specific ICD-10-CM code at first pass, reducing coder query volume by eliminating the ambiguity that triggers retrospective clarification.

Cross-Platform Governance: Epic, athenahealth, and the Vendor-Agnostic Reality

Most CMIOs operate multi-EHR environments. Academic medical centers run Epic for inpatient and subspecialty care while affiliated practices, rural clinics, or recently acquired groups may run athenahealth, Cerner (now Oracle Health), or other platforms. Ambient AI governance cannot be Epic-only.

Scribing.io maintains parallel integration architectures. On Epic, the ACI SmartBlock/SDE pathway described above governs all writeback. On athenahealth, Scribing.io uses the platform's certified API framework to write structured clinical content into encounter-specific documentation sections with discrete field mapping for billing-relevant elements. For a detailed walkthrough of the athenahealth integration, including clinical inbox management and task routing, see our guide to the athenahealth API integration.

The governance principle is consistent across platforms: AI-generated content must land as structured, encounter-bound, discrete data that the billing engine and quality reporting layer can read natively. The technical mechanism differs per EHR, but the architectural commitment is identical.

CMIO Evaluation Checklist: Seven Non-Negotiable ACI Integration Requirements

Before signing an ambient AI contract, every CMIO should require demonstration—not just documentation—of these seven capabilities in a live Epic sandbox environment:

1. SmartBlock Targeting Proof. The vendor must demonstrate that AI output lands in a department- and note-type–scoped SmartBlock, not a generic text field. Request a screen recording showing the output in NoteWriter with the SmartBlock name visible.

2. SDE Population for Total Time and Critical Care Time. Query the SDE after an ambient session completes. The discrete value must exist independently of the narrative text. If deleting the narrative does not remove the SDE value, the integration is correct.

3. CSN Binding Verification. Open two encounters for the same patient on the same day. The ambient output for each session must bind to its respective CSN without manual encounter selection by the clinician.

4. Split/Shared Attestation Automation. Stage a split/shared encounter with two test providers. Verify that the attestation auto-populates with both provider IDs and that the Total Shared Time SDE is written—not just mentioned in the note body.

5. Missing-Element Flagging. Complete a split/shared encounter without verbalizing time. The system must flag the encounter as incomplete and prevent clean claim submission until the deficiency is resolved.

6. Laterality SDE Population. Dictate a unilateral finding (e.g., "right lower lobe consolidation"). Confirm that the Laterality SDE populates with the correct value and that the laterality is not limited to narrative text.

7. Audit Log Export. Request an export of the ambient session audit log showing timestamp, provider ID, CSN, SmartBlock target, SDE values written, and attestation content. This log must be producible for MAC audit response within 48 hours.

Any vendor that cannot demonstrate all seven in a live sandbox is selling you a transcription tool, not an Epic integration.

See It Live: ACI SmartBlock Writeback in Your Epic Sandbox

See a live ACI SmartBlock writeback in your Epic sandbox: CSN-bound insertion, SDE mapping for Total/CC Time and laterality, and audit logs proving FS-ready documentation—validated in under 30 minutes.

Scribing.io's implementation team will configure a test instance against your facility's SmartBlock library, run a simulated split/shared encounter, and walk your CMIO, revenue cycle director, and compliance officer through every discrete data element, attestation macro, and audit log entry. No slide decks. No marketing narratives. Live data in your environment.

Request your sandbox demonstration at Scribing.io.