Verified

ICD-10 Z00.129: Routine Child Health Exam Guide Complete Documentation Playbook for Pediatricians

Master ICD-10 Z00.129 coding for well-child visits. Learn documentation best practices, avoid claim denials, and optimize revenue for your pediatric practice.

ICD-10 Z00.129: Routine Child Health Exam Guide — Complete Documentation Playbook for Pediatricians - Clinical Documentation Guide Illustration for Scribing.io

ICD-10 Z00.129: Routine Child Health Exam Guide — The Complete Clinical Documentation Playbook for Pediatric Practices

TL;DR — What This Guide Covers and Why It Matters

Z00.129 ("Encounter for routine child health examination without abnormal findings") is the default ICD-10-CM code for well-child visits — but it becomes a revenue liability the moment a physician identifies an abnormal finding mid-encounter. Most EHR systems never re-order the diagnosis array, leaving Z00.129 as the principal diagnosis even when the visit has shifted to include acute care. The result: denied E/M claims, post-pay audits, and six-figure annual revenue leakage across pediatric practices. This guide provides the complete clinical, coding, and technical framework that the CMS ICD-10 Clinical Concepts for Pediatrics reference (and every other publicly available guide) fails to address — including the FHIR R4 interoperability gap, payer-specific modifier-25 adjudication rules, and the real-time documentation workflow that prevents denials before they happen. Built for Pediatric Medical Directors who need audit-proof documentation standards across their care teams.

  • What Competitors Miss: The Z00.129 → Z00.121 Transition Gap in EHR Systems

  • Technical Reference: ICD-10 Documentation Standards for Z00.129 and Z00.121

  • The "Abnormal Finding" Trap: Why Well-Child Visits Generate the Highest Denial Rates in Pediatrics

  • Scribing.io Clinical Logic: Real-Time Scenario — AOM During a 9-Year-Old's Well Visit

  • FHIR R4 Interoperability: Why Your EHR's Diagnosis Array Is Costing You Revenue

  • Modifier-25 Payer Adjudication Matrix: Rules That Change by Carrier

  • Complete Otitis Media ICD-10 Code Map for Pediatric Well-Visit Transitions

  • Implementation Checklist: Deploying Audit-Proof Well-Visit Documentation Across Your Practice

What Competitors Miss: The Z00.129 → Z00.121 Transition Gap in EHR Systems

The CMS ICD-10 Clinical Concepts for Pediatrics document — the most widely referenced public guide for pediatric ICD-10 coding — lists Z00.129 and Z00.121 as a two-line entry under "Routine Child Health Examination." It offers no guidance on when to switch between them, how the transition must be documented, or what happens inside the EHR's data architecture when a physician identifies an abnormal finding during a preventive encounter. Scribing.io exists because that gap costs pediatric practices between $48,000 and $210,000 annually in denied or recouped E/M revenue — revenue that was clinically earned but architecturally lost.

This is not a minor documentation nuance. It is the single most consequential billing failure mode in pediatric primary care. When an abnormal finding is added during a well-child visit, the majority of certified EHR systems leave Z00.129 as the principal diagnosis because the encounter diagnosis array is not re-ordered. In FHIR R4 — the interoperability standard mandated under the ONC Cures Act Final Rule for certified EHR technology — the principal diagnosis must be explicitly set via Encounter.diagnosis.use = "principal" with rank = 1. If Z00.129 is not flipped to Z00.121 and there is no explicit, time-stamped "Transition to Acute Care" statement plus a payer-validated modifier-25, payers adjudicate the claim as preventive-only and deny the separately billed E/M service. Scribing.io detects abnormal findings in real time, auto-switches Z00.129 → Z00.121, inserts an audit-stamped Transition-to-Acute statement, and applies payer-specific -25 rules while linking the acute ICD-10 to the problem-oriented E/M via FHIR principal-diagnosis ordering.

See our real-time Abnormal Finding engine that auto-switches Z00.129↔Z00.121, inserts an audit-stamped Transition to Acute Care with timestamp, and applies payer-specific -25 rules via FHIR principal-diagnosis ordering — book a 15-minute demo to watch it in your EHR.

Explore the complete code definitions for Z00.129 and Z00.121 in the Scribing.io ICD-10 Documentation Library.

Documentation Requirement

CMS Clinical Concepts Guide

This Playbook + Scribing.io

When to switch Z00.129 → Z00.121

Not addressed

Complete decision logic with time-stamp protocol

EHR diagnosis array re-ordering

Not addressed

FHIR R4 Encounter.diagnosis field-level specification

Transition to Acute Care documentation

Not addressed

Audit-stamped narrative template with payer requirements

Modifier-25 payer-specific adjudication rules

Not addressed

Carrier-level matrix (commercial, Medicaid, CHIP)

Split-visit medical necessity linkage

Not addressed

ICD-10 → CPT linkage logic with DiagnosticReport references

Real-time EHR automation for code switching

Not addressed

Scribing.io detection and auto-correction workflow

Post-pay audit defense documentation

Not addressed

Audit flag architecture and recoupment prevention protocol

For Pediatric Medical Directors overseeing multi-provider practices, this gap is not theoretical. Current clinical benchmarks from the American Academy of Pediatrics indicate that well-child visits with incidental acute findings represent 18–25% of all pediatric preventive encounters. When the documentation fails to support the split-visit billing, the denied E/M code (typically 99212–99215 with modifier-25) represents $85–$210 per encounter in lost or recouped revenue.

Technical Reference: ICD-10 Documentation Standards for Z00.129 and Z00.121

Understanding the clinical and technical distinction between Z00.129 and Z00.121 is foundational to every workflow described in this guide. These are not interchangeable codes — they represent two fundamentally different clinical outcomes of the same encounter type, and their correct application determines whether a split-visit claim survives adjudication.

Z00.129 — Encounter for Routine Child Health Examination Without Abnormal Findings

Attribute

Detail

Full Code

Z00.129

Description

Encounter for routine child health examination without abnormal findings

Chapter

21 — Factors influencing health status and contact with health services (Z00–Z99)

Block

Z00–Z13 — Persons encountering health services for examinations

Category

Z00 — Encounter for general examination without complaint, suspected or reported diagnosis

Applicable Age

Pediatric (0–17 years per ICD-10-CM convention; age-specific CPT determines preventive service code)

7th Character

Not applicable

Primary Use

Principal diagnosis for well-child preventive visits where the entire encounter concludes with no abnormal findings identified

Billing Pairing

99381–99395 (age-appropriate preventive medicine CPT); Z00.129 should be the sole or principal diagnosis

Critical Rule

If any abnormal finding is identified during the visit — even if not treated — Z00.129 must be replaced with Z00.121 as the principal preventive diagnosis

Z00.121 — Encounter for Routine Child Health Examination With Abnormal Findings

Attribute

Detail

Full Code

Z00.121

Description

Encounter for routine child health examination with abnormal findings

Chapter

21 — Factors influencing health status and contact with health services (Z00–Z99)

Block

Z00–Z13 — Persons encountering health services for examinations

Category

Z00 — Encounter for general examination without complaint, suspected or reported diagnosis

Coding Convention

Use additional code(s) to identify abnormal findings (e.g., H66.002 for left acute suppurative otitis media)

Primary Use

Principal preventive diagnosis when one or more abnormal findings are identified during the well-child encounter

Billing Pairing

Z00.121 supports the preventive CPT (99381–99395); the acute ICD-10 code (e.g., H66.002) supports the problem-oriented E/M (99212–99215) with modifier-25

Critical Rule

The abnormal finding code must appear as an additional diagnosis linked specifically to the E/M service — not to the preventive service. Z00.121 replaces Z00.129 as the preventive service's principal diagnosis.

The Distinction That Drives Denials

The difference between these two codes is a single digit in the sixth character position: 9 (without abnormal findings) versus 1 (with abnormal findings). That single digit controls whether a payer's adjudication engine recognizes that the encounter produced an acute clinical event requiring separately billable work.

ICD-10-CM Official Guidelines for Coding and Reporting, Section IV.K instructs: "When a patient presents for a routine examination and a condition is discovered during the examination, the code for the routine examination should indicate that an abnormal finding was identified. A code for the abnormal finding should be listed as an additional diagnosis."

This means:

  1. Z00.129 becomes Z00.121 — the preventive visit code must reflect the discovery.

  2. The specific abnormal finding (e.g., H66.002) must be reported as an additional code.

  3. If a separate E/M service is warranted and documented, modifier-25 is appended to the E/M CPT code per AMA CPT guidelines.

For the full ICD-10-CM code reference and documentation guidelines, see Z00.129 — Encounter for routine child health examination without abnormal findings; Z00.121 — Encounter for routine child health examination with abnormal findings.

The "Abnormal Finding" Trap: Why Well-Child Visits Generate the Highest Denial Rates in Pediatrics

If a doctor finds an ear infection during a well-check, they must document the "Transition to Acute Care" to justify billing both the preventive service (now supported by Z00.121 rather than Z00.129) and an E/M code. This is the Abnormal Finding Trap — and it catches experienced pediatricians and new residents alike because the clinical workflow feels continuous while the billing workflow demands discontinuity.

Why the Trap Exists

The trap is structural, not clinical. Pediatricians are trained to manage the whole child. When they discover otitis media during an ear exam that is part of the standard well-child protocol, there is no cognitive "switch." The physician examines, identifies, diagnoses, and treats in a single fluid movement. But billing requires that switch to be explicitly documented with enough granularity to satisfy three distinct adjudication checkpoints.

The Three Adjudication Checkpoints

  1. The preventive visit was complete and medically necessary in its own right. The well-child visit (99393 for a 9-year-old established patient) must stand alone with all age-appropriate components documented per AAP Bright Futures periodicity schedule.

  2. A distinct, separately identifiable problem was discovered. The abnormal finding must be clearly noted — not just in the assessment, but with enough clinical detail to justify that additional work was performed beyond the preventive service scope.

  3. The additional work is documented with its own history, exam, and medical decision-making (MDM). This is the E/M component (99212–99215 with modifier-25). It must have its own clinical narrative demonstrating that the physician performed work above and beyond the preventive visit template.

The Documentation Chain That Must Exist

Step

Required Element

Common Failure Mode

1

Complete preventive visit documentation (growth, development, anticipatory guidance, immunization review)

Preventive template left partially incomplete when physician transitions to acute issue

2

Time-stamped notation: "Transition to Acute Care" or equivalent clinical statement

No transition statement exists; assessments blended into single note section

3

Z00.129 replaced with Z00.121 as principal preventive diagnosis

EHR retains Z00.129 because diagnosis array not manually re-ordered

4

Acute ICD-10 code (e.g., H66.002) added as additional diagnosis

Acute code added but not linked to E/M service line

5

Separate E/M documentation: HPI for acute complaint, focused exam, MDM

Exam findings embedded within preventive template without distinct E/M narrative

6

Modifier-25 appended to E/M CPT code

Modifier applied but documentation insufficient to support "separately identifiable" standard

7

Diagnosis-to-CPT linkage: Z00.121 → 99393; H66.002 → 99213-25

Both diagnoses linked to preventive service only; E/M has no supporting diagnosis pointer

When any link in this chain breaks, the E/M claim fails. Per HHS Office of Inspector General audit criteria, the most common finding in pediatric post-pay audits is the absence of documentation supporting modifier-25 — specifically, the lack of a clear delineation between preventive and problem-oriented services within the same encounter.

Scribing.io Clinical Logic: Real-Time Scenario — AOM During a 9-Year-Old's Well Visit

This section walks through the exact clinical scenario that generates the highest volume of pediatric split-visit denials — and demonstrates how Scribing.io resolves every documentation failure point in real time.

The Scenario

A 9-year-old established patient presents for a routine well-child visit (CPT 99393). During the ear exam — a standard component of the preventive visit — the physician identifies a left acute otitis media (AOM). The physician prescribes amoxicillin and provides return-visit instructions.

Without Scribing.io: The $146 Loss

  1. The chart retains Z00.129 as principal diagnosis because the EHR's diagnosis picker defaults to "without abnormal findings" for the well-child encounter type.

  2. No explicit, time-stamped Transition to Acute Care statement exists in the note.

  3. The physician adds H66.002 to the problem list but does not link it to a separate E/M service line.

  4. The billing team appends 99213-25 based on the treatment plan, but the note lacks a distinct E/M narrative.

  5. The payer denies 99213-25 on initial adjudication (reason: "documentation does not support a separately identifiable E/M service").

  6. On post-pay audit, the practice loses $146 (average allowed amount for 99213 in Medicaid CHIP programs, 2025–2026 fee schedules).

With Scribing.io: The Complete Fix in Six Automated Steps

Step

Scribing.io Action

Clinical/Billing Outcome

1

Real-time NLP detects physician's documentation of abnormal ear findings (e.g., "TM erythematous, bulging, decreased mobility left ear")

Triggers Abnormal Finding protocol

2

Auto-inserts time-stamped Transition to Acute Care statement: "10:22 AM — Transition to Acute Care for left AOM"

Creates the audit-defensible delineation between preventive and problem-oriented services

3

Flips principal preventive diagnosis from Z00.129 to Z00.121 in the FHIR Encounter.diagnosis array (rank = 1, use = "principal")

Claim now correctly signals to payer that abnormal findings were identified during preventive encounter

4

Links H66.002 (Acute suppurative otitis media, left ear, unspecified recurrence) as additional diagnosis with explicit pointer to E/M service line (99213-25)

Diagnosis-to-CPT linkage satisfies payer adjudication logic for medical necessity

5

Preserves 99393 with Z00.121 as its supporting diagnosis; verifies all Bright Futures components remain documented in the preventive section

Preventive service stands independently; no "double-dipping" audit flag

6

Applies payer-specific modifier-25 rules (checks carrier's separately-identifiable-service threshold; validates MDM level supports 99213; flags if documentation is thin)

Claim transmits clean; both services adjudicate on first pass

The Granular Logic Breakdown

Step 2 is the critical intervention. The time-stamped Transition to Acute Care statement does three things simultaneously:

  • Creates temporal separation. Auditors reviewing split-visit claims need to see that the physician recognized the encounter nature changed at a specific point. "10:22 AM" proves the preventive visit was underway (and partially or fully complete) before the acute care began.

  • Establishes medical necessity. The statement "Transition to Acute Care for left AOM" names the condition, establishing that the physician made a clinical determination that a new, separately identifiable problem required evaluation beyond the preventive protocol.

  • Prevents the "double-dipping" flag. Payer fraud algorithms look for modifier-25 claims where the documentation suggests the acute work was simply part of the preventive exam (e.g., "ears normal" crossed out and replaced with "left AOM"). The explicit transition statement creates a clean boundary that satisfies both human auditors and automated prepayment review systems.

Step 3 solves the FHIR gap. When Scribing.io changes Z00.129 to Z00.121 in the encounter's diagnosis array, it does so at the data architecture level — not just in the visible note. This means the 837P claim file transmits with the correct principal diagnosis regardless of how the EHR's claim scrubber processes the encounter. The Encounter.diagnosis resource is updated with:

  • condition.reference pointing to Z00.121

  • use.coding.code = "AD" (admission diagnosis / principal)

  • rank = 1

Step 4 closes the linkage loop. H66.002 is not merely "on the chart" — it is explicitly linked as the supporting diagnosis for the E/M service line. In the FHIR Claim resource, this appears as item.diagnosisSequence pointing to the acute diagnosis entry rather than the preventive entry. Without this linkage, many payer systems cannot match the E/M service to a covered diagnosis and default to denial.

FHIR R4 Interoperability: Why Your EHR's Diagnosis Array Is Costing You Revenue

The HL7 FHIR R4 Encounter resource defines Encounter.diagnosis as a backbone element containing condition (reference to the diagnosis), use (role of the diagnosis — admission, discharge, billing, etc.), and rank (integer determining sequence). This structure was designed to eliminate ambiguity in diagnosis ordering. In practice, most EHR implementations populate this array at encounter creation and never update it during the clinical workflow.

The Technical Failure

When a well-child encounter is opened, the EHR creates:

  • Encounter.diagnosis[0].condition → Z00.129

  • Encounter.diagnosis[0].use → "billing"

  • Encounter.diagnosis[0].rank → 1

When the physician later adds an acute finding (H66.002), most systems append it:

  • Encounter.diagnosis[1].condition → H66.002

  • Encounter.diagnosis[1].use → "billing"

  • Encounter.diagnosis[1].rank → 2

Z00.129 remains at rank 1. The system never changes it to Z00.121. The claim file reflects Z00.129 as principal. The payer's adjudication engine reads: "preventive visit without abnormal findings" — and denies the E/M code that claims an abnormal finding was managed.

How Scribing.io Resolves This

Scribing.io operates at the FHIR resource level through certified EHR integrations. When the Abnormal Finding engine fires:

  1. Encounter.diagnosis[0].condition is updated: Z00.129 → Z00.121

  2. Encounter.diagnosis[0].use is confirmed as "billing" with principal role

  3. Encounter.diagnosis[1] (H66.002) is tagged with use = "billing" and explicitly linked to the E/M Claim.item

  4. A Provenance resource is generated documenting the change, the timestamp, the clinical justification, and the user attribution — creating an immutable audit trail

This architecture ensures that regardless of how the EHR renders the encounter visually to the physician, the underlying data transmitted to the payer is structurally correct per USCDI v4 standards.

Modifier-25 Payer Adjudication Matrix: Rules That Change by Carrier

Modifier-25 ("Significant, Separately Identifiable Evaluation and Management Service by the Same Physician on the Same Day of the Procedure or Other Service") is defined by the AMA CPT codebook, but its adjudication criteria vary by payer. This creates a compliance risk for practices that apply a single documentation standard across all carriers.

Payer Category

Modifier-25 Requirement

Documentation Threshold

Common Denial Trigger

Medicare (for reference)

Separately identifiable E/M beyond procedure

Distinct chief complaint, exam, and MDM

No separate HPI; exam findings embedded in procedure note

Commercial (UHC, Aetna, Cigna)

Separately identifiable E/M beyond preventive

Separate problem-focused note section; some require separate page or distinct header

Acute assessment blended into preventive template without delineation

Medicaid (state-variable)

Varies: some states require separate encounter form; others accept embedded documentation with clear transition

Time-stamp and explicit statement of medical necessity for acute evaluation

Z00.129 retained as principal (no Z00.121 switch); no transition statement

CHIP Programs

Generally follows state Medicaid rules; EPSDT guidelines may override

Must demonstrate acute service not included in EPSDT screen components

Treatment documented as part of preventive screen rather than separate evaluation

Blue Cross Blue Shield (plan-specific)

Many BCBS plans require >50% of E/M time or MDM to be attributable to acute problem

Explicit documentation of additional time or MDM elements beyond preventive scope

Low-complexity E/M (99212) denied as "included in preventive"

Scribing.io maintains a continuously updated payer rule engine that applies the correct documentation threshold based on the patient's active coverage. When the system detects a split-visit scenario, it validates the E/M documentation against the specific carrier's modifier-25 requirements and flags insufficiencies before the claim is submitted.

Complete Otitis Media ICD-10 Code Map for Pediatric Well-Visit Transitions

Otitis media is the most common acute finding during pediatric well-child visits, per NIH/NLM epidemiological data. Correct laterality and specificity coding is essential for clean claims. The following table maps the complete acute otitis media code set relevant to well-visit transition scenarios:

ICD-10-CM Code

Description

Laterality

Use Case in Well-Visit Transition

H66.001

Acute suppurative otitis media without spontaneous rupture of ear drum, right ear

Right

Right-sided AOM found during well-child ear exam

H66.002

Acute suppurative otitis media without spontaneous rupture of ear drum, left ear

Left

Left-sided AOM found during well-child ear exam (scenario code)

H66.003

Acute suppurative otitis media without spontaneous rupture of ear drum, bilateral

Bilateral

Bilateral AOM found during well-child ear exam

H66.004

Acute suppurative otitis media without spontaneous rupture of ear drum, recurrent, right ear

Right, recurrent

Right-sided recurrent AOM; requires history documentation

H66.005

Acute suppurative otitis media without spontaneous rupture of ear drum, recurrent, left ear

Left, recurrent

Left-sided recurrent AOM; requires history documentation

H66.006

Acute suppurative otitis media without spontaneous rupture of ear drum, recurrent, bilateral

Bilateral, recurrent

Bilateral recurrent AOM; requires history documentation

H65.191

Other acute nonsuppurative otitis media, right ear

Right

Serous/non-purulent AOM, right

H65.192

Other acute nonsuppurative otitis media, left ear

Left

Serous/non-purulent AOM, left

H65.193

Other acute nonsuppurative otitis media, bilateral

Bilateral

Serous/non-purulent AOM, bilateral

Specificity note: Scribing.io's code-suggestion engine uses the physician's documented exam findings (e.g., "purulent effusion" vs. "serous fluid"; "left" vs. "bilateral") to recommend the maximally specific code. Unspecified codes (H66.009, H65.199) trigger a documentation prompt requesting laterality and type — preventing the 4–7% denial rate associated with unspecified otitis media codes reported in JAMA Otolaryngology coding studies.

Implementation Checklist: Deploying Audit-Proof Well-Visit Documentation Across Your Practice

For Pediatric Medical Directors implementing this workflow across multiple providers — including residents, APPs, and locum physicians — the following checklist operationalizes every concept in this playbook:

Phase 1: Baseline Assessment (Week 1–2)

  • Pull 90-day claims data for all well-child visits (99381–99395) with same-day E/M codes (99212–99215 with modifier-25)

  • Calculate denial rate for modifier-25 E/M claims; benchmark against 12–18% industry average per MGMA data

  • Identify which providers' notes retain Z00.129 when acute findings are documented (chart audit: sample 20 encounters per provider)

  • Determine EHR's current FHIR R4 diagnosis array behavior: does it re-order when acute codes are added?

Phase 2: Documentation Standard Deployment (Week 3–4)

  • Implement mandatory Transition to Acute Care timestamp protocol for all providers

  • Update EHR encounter templates to include a triggered prompt when any acute diagnosis is added to a preventive encounter

  • Train billing team on Z00.129 → Z00.121 switch requirements and diagnosis-to-CPT linkage rules

  • Deploy payer-specific modifier-25 documentation cheat sheets (derived from the matrix in this guide)

Phase 3: Scribing.io Integration (Week 4–6)

  • Connect Scribing.io to EHR via certified FHIR API (supports Epic, athenahealth, eClinicalWorks, Cerner/Oracle Health)

  • Configure Abnormal Finding detection sensitivity thresholds

  • Set payer rules engine with active carrier contracts

  • Run parallel processing on 2 weeks of encounters to validate auto-switch accuracy (target: >99.2% concordance with manual audit)

Phase 4: Ongoing Monitoring (Monthly)

  • Track modifier-25 denial rate (target: <3%)

  • Monitor Z00.129 retention rate on encounters with acute findings (target: 0%)

  • Review Scribing.io audit trail for any overridden suggestions (indicates provider education gaps)

  • Reconcile recovered revenue against baseline: expected lift of $42,000–$168,000/year for 4-provider practice seeing 35 well-visits/provider/week with 20% acute finding rate

Revenue Impact Model

Metric

Before Scribing.io

After Scribing.io

Well-visits with acute findings (annual, 4-provider)

1,456

1,456

E/M claims submitted with modifier-25

1,092 (75% capture rate)

1,456 (100% capture rate)

E/M claims denied

197 (18% denial rate)

29 (<2% denial rate)

Net E/M revenue captured

$130,815

$208,572

Annual revenue recovered

$77,757

These figures use the 2025–2026 national average allowed amount for 99213 ($146) across a blended payer mix. Practices with higher commercial payer ratios or providers who commonly bill 99214-25 for complex acute findings will see proportionally larger recovery.

Bottom line for Medical Directors: The Z00.129/Z00.121 distinction is not a coding curiosity — it is the load-bearing wall of pediatric split-visit revenue. Every encounter where an abnormal finding is identified but the documentation chain breaks represents guaranteed revenue loss. Scribing.io eliminates every failure point in that chain: the diagnosis switch, the timestamp, the FHIR array re-ordering, the payer-specific modifier logic, and the audit trail. Book a 15-minute demo to see it run against your EHR's live encounter data.

Frequently

asked question

Answers to your asked queries

How does the AI medical scribe work?

Does Scribing.io support ICD-10 and CPT codes?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

How do I get started?

Frequently

asked question

Answers to your asked queries

How does the AI medical scribe work?

Does Scribing.io support ICD-10 and CPT codes?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

How do I get started?

Frequently

asked question

Answers to your asked queries

How does the AI medical scribe work?

Does Scribing.io support ICD-10 and CPT codes?

Can I edit or review notes before they go into my EHR?

Does Scribing.io work with telehealth and video visits?

Is Scribing.io HIPAA compliant?

Is patient data used to train your AI models?

How do I get started?

Didn’t find what you’re looking for?
Book a call with our AI experts.

Didn’t find what you’re looking for?
Book a call with our AI experts.

Didn’t find what you’re looking for?
Book a call with our AI experts.