CPT Code 76805 Explained: What It Covers and When to Bill

Most 76805 denials aren't a coder knowledge problem. They're a documentation gap that forms before the note is ever signed, and fixing it requires a different intervention entirely.

The common assumption among practice administrators and billing decision-makers is that the problem is coders not knowing the rules for 76805 well enough, that more training or a better code reference will fix the denial rate. CPT code 76805 sits at the center of one of the highest-volume billing decisions in OB/GYN practice. A practice running 20 anatomy scans per week generates hundreds of that same figure claims per month, and a 10% denial rate on those claims translates directly into thousands of dollars in delayed cash flow and staff rework time.

Most billing leaders respond by investing in coder training. That investment rarely moves the denial rate, and the reason why matters. See our AI medical scribe for how this works in practice.

"Patients are being billed with CPT code 76811 (high-risk/detailed anatomy scan) instead of the standard 76805 (routine OB ultrasound) for routine 20-week anatomy scans, resulting in unexpected out-of-pocket costs, in this case over $338."

— what we hear from OB/GYN billing departments

CPT code 76805 is the standard second and third trimester transabdominal obstetric ultrasound code for a single or first gestation. The code covers fetal and maternal evaluation including fetal number, cardiac activity, placental location, amniotic fluid volume, fetal biometry, and a full anatomic survey. It is distinct from CPT 76801, which applies to first trimester single-gestation scans, and from 76811, which is reserved for high-risk or detailed specialized fetal examinations. The failure point is the space between the clinical note and the submitted claim.

The failure point is not the codebook. It is the space between the clinical note and the submitted claim.

As the AAPC Medical Billing and Coding Forum documents, real-world billing challenges arise at clinical boundaries where a patient presents past the first trimester cutoff but before the physician's preferred gestational age for performing a full anatomy scan. The components of that same figure may have been observed during the encounter, but if the finalized note does not explicitly capture each required element, the coder cannot legitimately bill for them, regardless of what actually happened in the room. "The gap is not effort. The gap is visibility."

iScribe Health's automated coding intelligence operates directly on the clinical narrative in real time, so the mapping from documented findings to the correct code happens before the note is even signed. In a study of ambient-AI-captured OB encounters, real-time coding validation surfaced a 33% overcoding rate across 941 encounters analyzed, with 54.8% provider-AI agreement on anatomy scan claims that had previously passed standard billing review without triggering a denial. The clinical detail that supports that same figure is almost always present in the encounter. Without a system built to bridge the translation gap, it never reliably surfaces at the claim level.

33%

overcoding rate found on anatomy scan claims

Knowing what that same figure covers is only the first gate. The code carries a precise gestational age requirement that functions as a hard claim qualifier, and getting it wrong is the single fastest path to a denial on an otherwise complete, well-documented encounter.

That requirement is where the next section begins.

Key takeaways

• CPT 76805 applies exclusively to transabdominal obstetric ultrasound at 14 weeks 0 days gestational age or later, bill it before that threshold and the claim doesn't just get denied, it was never valid.
• Auditors don't watch the scan; they read the report. Every element observed but not explicitly documented in the finalized note is, from a payer's perspective, an element that never happened.
• The boundary between 76805 and 76811 isn't a training gap, it's a real-time documentation gap. The clinical distinction is almost always present in the note; it just never makes it to the claim.
• Modifier logic, ICD-10 pairing, and payer-specific frequency caps operate independently of whether the code itself was correct. A flawlessly coded 76805 claim can still be denied at any of those layers.
• Denial patterns on 76805 claims are rarely random, when the same rejection reason repeats across a billing cycle, it signals a systemic failure in the documentation-to-claim handoff, not a one-off coder error.
• iScribe Health's Automated E&M Coding reads the ambient clinical narrative directly and surfaces the correct code before the note is even signed, so the 76805 errors that slip through manual review get caught at the source, not after a denial lands.

The Gestational Age Requirement That Makes or Breaks a 76805 Claim

14 Weeks 0 Days - The Hard Floor Below Which 76805 Does Not Exist

CPT 76805 applies exclusively to transabdominal obstetric ultrasound performed at 14 weeks 0 days gestation or later. A scan performed at 13 weeks 6 days does not qualify, regardless of how complete the encounter was.

When a patient presents at 15 weeks 5 days and the scan report doesn't explicitly pin the gestational age to a specific date, the coder faces an ambiguous claim. The 14-week rule is clear; the upstream documentation never handed them the information needed to apply it.

Key takeaway: 14 weeks 0 days is a hard technical gate, and ambiguity at that edge can translate into $1,000 or more in unexpected out-of-pocket cost for a single patient encounter.

The coding error is frequently a documentation failure that forces the coder into a defensive, higher-acuity code because gestational age was never anchored clearly in the note.

Rather than leaving gestational age capture to the clinician's end-of-day charting session, iScribe Health's ambient AI listens at the point of care and drafts the encounter summary at the point of note completion, before documentation gaps harden into billing problems.

Transabdominal Approach Is Non-Negotiable

The approach used during the scan carries direct coding consequences. A transvaginal scan maps to a different code family entirely, most commonly 76815 for a limited study or 76801 for a first-trimester complete scan, as MedibillMD details.

In practices running a supported EHR, iScribe Health's EHR Integration means the ambient AI-drafted note flows directly into the existing workflow, so the approach used, and the order in which it was used, is captured in real time rather than reconstructed from memory hours later. iScribe Health's Real-Time Denial Alerts then surface any downstream mismatch between the documented approach and the submitted code before the claim leaves the practice.

Single vs. Multiple Gestations and the Coding Path Forward

When multiple gestations are present, that same base code still applies to the first fetus, but each additional fetus requires a separate add-on code.

Accurate, compliant coding across high patient volumes, with every qualifying add-on captured and every claim reflecting the complexity actually delivered, is a core outcome iScribe Health is built to support.

Documentation Requirements for CPT 76805 That Auditors Actually Check

That distinction matters more than most billing teams realize, because the clinical record is the only artifact a payer or auditor ever evaluates, and every element that was observed but not explicitly stated in the finalized note is, from their perspective, an element that never happened.

ACOG's Committee Opinion No. 656 makes this precise: prenatal ultrasonography must be performed and documented according to established standards, with the clinical record reflecting each specific component assessed, including fetal anatomy, biometric measurements, placental location, and amniotic fluid evaluation. That standard applies at the level of individual report elements, not the encounter as a whole.

The Mandatory Anatomy Checklist Auditors Run Line by Line

Auditors expect the finalized report to confirm assessment of the fetal head and neck, face, chest (including four-chamber cardiac view), abdomen (stomach, kidneys, bladder, abdominal wall), spine, and extremities. Each structure must be named individually, and any that were not visualized must be accounted for rather than silently omitted.

Gestational Age, Fetal Number, and Cardiac Activity as Header Fields

A compliant report for that same figure must open with three encounter-level confirmations: gestational age, fetal number, and fetal cardiac activity. These are treated as header-level fields by most auditors, meaning their absence near the top of the report, even if inferable from other content, is itself flagged as a deficiency.

How to Document Obstructed Views Without Creating Audit Exposure

When maternal habitus or fetal position prevents full visualization of a required structure, the report must name the specific structure that could not be adequately assessed, identify the reason, and confirm that the attempt was made. A vague phrase such as "limited study" without structure-level specificity does not satisfy this requirement and routinely triggers downcoding or denial.

Required Element: Gestational age (≥14w0d)

• Must Be Explicitly Stated In Report: ✅ Named date/week value
• Common Omission Risk: High, often implied, not stated

Required Element: Fetal number

• Must Be Explicitly Stated In Report: ✅ Confirmed in header
• Common Omission Risk: Medium

Required Element: Fetal cardiac activity

• Must Be Explicitly Stated In Report: ✅ Confirmed as present or absent
• Common Omission Risk: Medium

Required Element: Fetal presentation

• Must Be Explicitly Stated In Report: ✅ Stated (e.g. cephalic, breech)
• Common Omission Risk: High

Required Element: Placental location

• Must Be Explicitly Stated In Report: ✅ Named and described
• Common Omission Risk: Very High

Required Element: Amniotic fluid volume

• Must Be Explicitly Stated In Report: ✅ Qualitative or quantitative value stated
• Common Omission Risk: Very High

Required Element: Biparietal diameter (BPD)

• Must Be Explicitly Stated In Report: ✅ Numeric value in report text
• Common Omission Risk: High

Required Element: Head circumference (HC)

• Must Be Explicitly Stated In Report: ✅ Numeric value in report text
• Common Omission Risk: High

Required Element: Abdominal circumference (AC)

• Must Be Explicitly Stated In Report: ✅ Numeric value in report text
• Common Omission Risk: High

Required Element: Femur length (FL)

• Must Be Explicitly Stated In Report: ✅ Numeric value in report text
• Common Omission Risk: High

Required Element: Fetal head/neck survey

• Must Be Explicitly Stated In Report: ✅ Each structure named
• Common Omission Risk: Medium

Required Element: Fetal face survey

• Must Be Explicitly Stated In Report: ✅ Noted
• Common Omission Risk: Medium

Required Element: Four-chamber cardiac view

• Must Be Explicitly Stated In Report: ✅ Confirmed
• Common Omission Risk: Medium

Required Element: Fetal abdomen (stomach, kidneys, bladder, wall)

• Must Be Explicitly Stated In Report: ✅ Each structure noted
• Common Omission Risk: Medium

Required Element: Fetal spine

• Must Be Explicitly Stated In Report: ✅ Confirmed with any limitations noted
• Common Omission Risk: High

Required Element: Fetal extremities

• Must Be Explicitly Stated In Report: ✅ Noted
• Common Omission Risk: Low

Required Element: Maternal uterus and adnexa

• Must Be Explicitly Stated In Report: ✅ Assessment noted
• Common Omission Risk: High

Required Element: Obstructed views

• Must Be Explicitly Stated In Report: ✅ Structure named + reason stated
• Common Omission Risk: High

Related Reading

• Cpt Code 76817
• Cpt Code 57454
• Cpt Code 58150

How 76805 Differs From 76811 and the Adjacent Codes That Cause Undercoding

76805 vs 76811 Routine Evaluation vs High-Risk Specialized Examination and Why the Line Matters Financially

The financial stakes of confusing the two run in both directions.

This is precisely where iScribe Health's ambient AI documentation closes the gap.

The Gestational Age Boundary That Makes a 16-Week Claim Instantly Unbillable

That boundary is absolute.

The gestational age either qualifies or it does not. iScribe Health's Real-Time Denial Alerts flag this mismatch at the point of note completion, before the claim is submitted, so a correctable data point does not become a processed denial.

CPT 76810 - the Multiple-Gestation Add-On Practices Routinely Omit or Misapply

CPT 76810 is the add-on code for each additional fetus beyond the first in a second- or third-trimester multiple-gestation ultrasound. Its misuse takes two equally costly forms.

Either 76810 is omitted entirely on twin or higher-order gestation encounters, leaving per-fetus reimbursement uncaptured, or it is misapplied to single-gestation encounters where it does not belong, creating an overcoding exposure.

In high-volume practices where clinicians regularly chart two or more hours outside of patient care time, the ambient documentation burden itself contributes to compressed review cycles. iScribe Health's Ambient Listening captures fetal count and gestational context conversationally during the encounter, so that by the time the AI drafts the encounter summary, the detail that triggers 76810 is already surfaced, improving coding consistency across every provider on the schedule, not just the ones who happen to catch it on a given day.

Common Denial Reasons for 76805 Claims and What Auditors Flag First

Denial patterns on CPT that same figure claims are not random. The common assumption among practice administrators and billing decision-makers is that coders don't know the rules for that same figure well enough, and that more training or a better code reference will fix the denial rate. When the same rejection reason appears across multiple claims in a single billing cycle, it signals a systemic failure in the documentation-to-claim workflow, and payers notice that pattern before most billing teams do. Ensuring accurate, compliant medical coding across high patient volumes to maximize reimbursement and minimize claim denials requires addressing that systemic gap, not just correcting individual coders.

1. Incomplete Fetal Anatomy Documentation - The #1 Reason CPT Code 76805 Claims Get Denied

The most common denial trigger for that same figure is a claim that cannot demonstrate a complete fetal anatomic survey. According to DataRovers, missing or incomplete documentation of required fetal anatomy elements ranks as a top denial driver for this code, alongside gestational age errors and wrong code selection. The failure is rarely that the sonographer skipped structures. More often, the provider observed every required element during the scan but the finalized note captured only a subset. The claim then reflects incomplete documentation, and the payer denies on that basis alone.

The clinical detail exists. It just never made it to the claim.

Through Ambient Listening and Conversational AI, iScribe captures the full clinical narrative as the encounter unfolds. At the point of note completion, after the AI drafts the encounter summary, iScribe's E&M Coding Intelligence surfaces any missing fetal anatomy elements before the note is signed. The documentation deficiency is caught inside the clinical workflow, not discovered weeks later on a remittance advice. For high-volume OB practices where clinicians regularly chart two or more hours outside of patient care time, closing this gap at the source meaningfully reduces both denial volume and physician burnout.

2. Wrong Gestational Age or Trimester on the Claim - A Coding Mismatch Auditors Catch Immediately

CPT that same figure is valid only at 14 weeks 0 days or later. A claim submitted with a gestational age that falls before that threshold, or paired with a first-trimester ICD-10 code, produces an automatic mismatch that auditors flag on the first pass. DataRovers notes that incorrect gestational age on the claim is one of the discrete, systemic failure modes driving that same figure denials. The fix sounds simple, but when individual providers document gestational age inconsistently across a high-volume OB practice, the error compounds quickly.

iScribe's Real-Time Denial Alerts flag gestational age conflicts at the point of note completion, before the encounter moves downstream into the billing queue. Because iScribe integrates directly with supported EHRs, the alert appears inside the existing clinical environment, with no separate worklist and no secondary review step. The conflict is resolved while the encounter is still in front of the provider, collapsing the distance between what was documented and what the claim will reflect.

3. Payer Frequency Limitations and Medicare Coverage Gaps - Billing Without Knowing the Rules

Medicare does not cover routine prenatal ultrasound as a screening benefit. A Medicare patient billed for a routine that same figure encounter without a covered diagnostic indication receives a denial regardless of how complete the documentation is. DataRovers confirms that some payers apply frequency limitations on routine OB ultrasound, and billing without understanding those payer-specific policies adds a denial vector that code-level training alone cannot resolve. Commercial payers frequently cap covered scans at one per pregnancy, requiring documented medical necessity for any additional encounter billed under 76805.

This is where ambient documentation compounds its value. When iScribe captures the full conversational record of an encounter, the clinical rationale for an additional scan, fetal position, suspected anomaly, interval growth concern, is preserved in the note as it was spoken, not reconstructed after the fact. The medical necessity that justifies the claim is built into the documentation from the moment the encounter concludes.

4. Inconsistent Code Selection Across Providers in the Same Practice - The Pattern That Triggers Audits

When one provider bills that same figure for an encounter that a colleague bills as 76811, payers detect the variance across the practice's claims data. DataRovers identifies this directly: inconsistent coding across providers in the same practice creates payer pattern flags, and those flags trigger audits regardless of individual coder knowledge. The practice has no standardized decision point where the that same figure versus 76811 distinction gets applied consistently. That inconsistency reads as a compliance signal.

iScribe's Automated E&M Coding and AI Customization create that standardized decision point at scale. This is most impactful in high-volume practices and health systems where coding variance accumulates across dozens of daily encounters and multiple clinicians charting in parallel.

5. The Hidden Cost of Rework - Why Each Denied 76805 Claim Costs Far More Than the Remittance Shows

A single denied CPT code 76805 claim is rarely just a lost payment. Staff time spent pulling records, writing appeals, and resubmitting can cost $25-$50 per claim in labor alone, and cash flow delays compound across a high-volume OB practice. Recurring denial patterns on 76805 can escalate to a focused medical review, putting the entire OB ultrasound billing program under scrutiny. The tradeoff: investing in front-end coding audits reduces rework volume but requires dedicated compliance resources.

Billing Guidelines and Reimbursement Considerations for CPT 76805

What Medicare and Private Payers Actually Reimburse for 76805 and Where the Gap Lives

Medicare's 2024 Physician Fee Schedule places the global reimbursement for CPT that same figure at approximately $125 to $130 per encounter, depending on geographic locality and the applicable conversion factor. Private payers routinely reimburse at 110% to 150% of the Medicare allowable for obstetric ultrasounds, a spread that holds broadly across the contracting market, which means the revenue at stake on every commercial claim is meaningfully higher than the Medicare floor.

Modifier 26 and TC - How Splitting the Bill Between Facility and Professional Changes What You Collect

When the scan is performed in a hospital outpatient or independent imaging facility setting, billing splits into two distinct components. There, the facility bills the technical component under modifier TC, and the physician bills the professional interpretation under modifier 26. Omitting modifier 26 in that context does not produce a reduced payment, it produces no payment at all for the professional work performed.

Key takeaway: The professional component (modifier 26) typically represents roughly 40%–45% of the global allowable. Losing it to a modifier error on a high-volume obstetric service is a compounding revenue leak, not a one-time miss.

The technical component carries the remaining 55% to 60% of the global allowable.

ICD-10 Pairing and Frequency Rules That Determine Whether a Second Scan Gets Paid

Codes in the Z34 series support routine anatomy scans, while higher-acuity clinical scenarios require more specific diagnosis codes, including:

• Z36.1 for nuchal translucency screening
• O26- or O35-range codes for maternal or fetal complications
• O30- codes for multiple gestation

Most commercial payers cover one anatomy scan per pregnancy as a routine benefit. A second scan requires documented medical necessity tied to a covered indication.

iScribe Health's AI medical scribe reads the ambient clinical narrative at the point of documentation and surfaces the correct code, modifier, and diagnosis pairing before the claim is built, so the full allowable is captured on first submission rather than recovered after a denial.

Why Automated Coding Catches the 76805 Errors Your Billing Team Misses

The 33% Overcoding Finding - Why a Complete Note Doesn't Guarantee a Correct Code

Audit data on ambient-AI-captured encounters shows a 33% overcoding rate that neither the provider nor the practice knew existed, because the errors never generated a denial.

Key takeaway: Overcoding and undercoding both persist silently inside a correctly documented note. A billing team measuring only denial rates is blind to the majority of its revenue risk.

Undercoding to 76816 to avoid denials is equally invisible, because a claim that pays at the lower rate never flags as wrong. The AAPC Medical Billing and Coding Forum frames this precisely: billing errors in OB ultrasound coding often stem not from coder ignorance of the rules, but from clinical detail that exists in the documentation never making it onto the claim.

How Real-Time Coding Validation Closes the Gap Between the Clinical Narrative and the Claim

• Gestational age threshold confirmed at 14 weeks 0 days or later
• Transabdominal approach documented as the primary approach
• Fetal count captured and add-on code applicability evaluated
• Required anatomy checklist elements present in the note

If a mismatch exists between what the note supports and what the code requires, it surfaces immediately, while the provider can still act.

iScribe Health's automated coding reads the ambient clinical narrative in real time and validates documented elements against code criteria before the note is signed. A reactive denial workflow becomes a proactive coding integrity layer, catching discrepancies at the source rather than weeks after submission.

Standardizing 76805 vs. 76811 Decisions Across Every Provider in the Practice

Provider-to-provider variation is one of the most persistent sources of coding inconsistency in a group practice.

That consistency protects the practice from both audit exposure and revenue leakage across the full volume of OB ultrasound billing. The next section shows what that looks like in practice for an OB/GYN team billing at volume, and what a concrete first step with iScribe Health actually involves.

Related Reading

• Cpt Code 59409
• Cpt Code 59515

Next steps

If your OB/GYN practice keeps seeing 76805 denials despite thorough documentation, the path forward starts with closing the validation gap between the signed note and the submitted claim, not with additional coder training. Start with our AI medical scribe.

The audit data on ambient-AI-captured encounters shows a 33% overcoding rate that practices had no visibility into, because those errors never generated a denial to investigate. That means denial rate alone is a blind metric for 76805 revenue integrity. At the same time, inter-provider variability in 76805 versus 76811 selection, where one provider codes the same clinical picture differently than a colleague, registers as a statistical anomaly in payer systems and triggers audits that penalize the entire practice. Both failure modes share the same root cause: there is no standardized checkpoint between the clinical narrative and the claim that applies consistent decision logic to every encounter before it leaves the practice.

Start by seeing what that checkpoint looks like in practice. From there, every encounter gets evaluated against the same criteria, gestational age, anatomy checklist, fetal count, and payer-specific modifier logic, at the point of note completion, before the claim is generated.

Frequently Asked Questions

What specific anatomy components does the report need to name for a 76805 claim to hold up in an audit?

Auditors expect the finalized report to confirm assessment of the fetal head and neck, face, chest (including a four-chamber cardiac view), abdomen (stomach, kidneys, bladder, and abdominal wall), spine, and extremities. Maternal uterus and adnexa, placental location, and amniotic fluid evaluation must also appear as explicit line items, not as a general statement that a 'fetal anatomy survey was performed.' Biometric values for BPD, HC, AC, and FL must each be stated as named numeric values in the report text, not stored only in archived images.

If a patient is 13 weeks and 6 days, can I still bill 76805 if the scan was otherwise complete?

No. CPT 76805 applies exclusively to transabdominal obstetric ultrasound performed at 14 weeks 0 days gestation or later. A scan performed at 13 weeks 6 days does not qualify regardless of how complete the encounter was, and scans performed before that threshold must be billed under alternative codes such as 76801 or 76815.

What's the actual difference between 76805 and 76811, and does it matter for what the patient pays?

CPT 76805 covers a standard obstetric ultrasound in the second or third trimester for a single gestation, while 76811 is reserved for a detailed fetal anatomic survey in high-risk pregnancies requiring a more comprehensive evaluation. The financial difference is real and lands on patients: when a standard-risk patient is billed under 76811 instead of 76805, the downstream out-of-pocket charge can exceed $338 or top a $1,000 difference relative to what the patient would have owed under the correct code.

How do I code a twin pregnancy on a second-trimester anatomy scan, do I just bill 76805 once?

No. CPT 76805 covers a single or first gestation only, so it applies to the first fetus. Each additional fetus requires a separate add-on code. Billing 76805 alone on a twin pregnancy both leaves reimbursement on the table and misrepresents the complexity of the service performed.

What should the report say when the sonographer couldn't get a clear view of a required structure?

The report must name the specific structure that could not be adequately assessed, identify the reason (such as fetal position or maternal habitus), and confirm that the attempt was made. A report that simply omits a structure with no explanation gives the auditor no basis to distinguish a missed element from an obstructed one, leaving the claim vulnerable even when the provider made a full attempt.