OB Ultrasound Billing 2026: CPT 76801-76817 & BPP Codes

A mid-size OB/GYN practice running 400-500 deliveries a year typically performs 1,800-2,300 OB ultrasounds across the same period, and runs roughly $400,000 to $750,000 through ultrasound CPTs every single year. The single most common coding error on that line — confusing a 76805 standard fetal anatomy scan with a 76811 detailed anatomy scan — costs the practice on the order of $70-$90 per misbilled Medicare claim and more on commercial. Across a couple thousand ultrasounds annually, even a 10% error rate compounds into tens of thousands of dollars walking out the door.

That is before you count multiple-gestation add-ons that never get billed, professional-vs-technical modifier mistakes that get clawed back six months later, and biophysical profile (BPP) claims that get denied because the documentation never recorded the component score. OB ultrasound is the cleanest single line item to audit in an OB/GYN practice – and the one most worth fixing first.

Here is the 2026 framework our AAPC-certified coding team uses to keep this line clean.

The OB Ultrasound CPT Family (76801-76817): What Each Code Actually Covers

The 76801-76817 family is split by gestational age, complexity of the scan, and approach (transabdominal vs. transvaginal). Pick the wrong axis and the claim either gets denied or – worse – gets paid and recouped six months later. Here is the working map:

• 76801 – OB ultrasound, less than 14 weeks 0 days, transabdominal, complete; single or first gestation
• 76802 – Each additional gestation, less than 14w0d (add-on to 76801)
• 76805 – OB ultrasound, 14w0d or greater, transabdominal, complete fetal and maternal evaluation; single or first gestation
• 76810 – Each additional gestation, 14w0d or greater (add-on to 76805)
• 76811 – Detailed fetal anatomic exam, 14w0d or greater; requires a specific high-risk indication and is reported once per pregnancy
• 76812 – Each additional gestation, detailed (add-on to 76811)
• 76813 – First-trimester nuchal translucency measurement; single or first gestation
• 76814 – Each additional gestation, nuchal translucency (add-on to 76813)
• 76815 – Limited ultrasound (a quick-look evaluation – fluid, fetal heartbeat, placental location)
• 76816 – Follow-up ultrasound to re-evaluate a known or suspected fetal abnormality
• 76817 – Transvaginal obstetric ultrasound

A few rules that trip up otherwise-experienced coders:

• 76815 is not a substitute for an incomplete complete scan. If the sonographer attempted a 76805 and could not visualize the full anatomy (fetal position, maternal habitus), the correct code is 76805 with modifier 52 (reduced services) – not 76815.
• 76817 can stack with 76801 or 76805 on the same encounter when both transabdominal and transvaginal approaches are clinically warranted. Append modifier 59 (or XU) to the transvaginal code.
• 76811 is generally once per pregnancy. 76816 is a focused follow-up on a previously identified abnormality — it is not the code for a repeat full detailed survey. If a true repeat detailed anatomy scan is clinically warranted (e.g., the first 76811 could not visualize key structures), the correct path is a second 76811 with modifier 76 (repeat procedure same provider) or 77 (different provider), plus payer authorization — not 76816 in place of it.

The Biophysical Profile (BPP) Family: 76818 vs. 76819 vs. Adding NST

The BPP family is small but routinely miscoded. Two codes, one rule that determines which you pick:

• 76818 – Fetal biophysical profile with non-stress test (NST). The NST is bundled.
• 76819 – Fetal biophysical profile without NST.
• 59025 – Fetal non-stress test, reported separately when the NST is performed but a BPP is not, or when payer policy allows separate reporting outside of 76818.

Two documentation requirements that drive denials:

• The BPP component score must be in the chart. Auditors expect the standard five-component scoring (fetal breathing, gross body movement, tone, amniotic fluid volume, NST). A BPP claim without a documented score does not survive a records request.
• Do not unbundle 59025 inside a 76818. If you report 76818 and then separately bill 59025 for the same encounter, expect a CO-97 denial. 76819 + 59025 is acceptable when the NST is genuinely a separate service – but the documentation has to support that.

Professional vs. Technical Component: Modifier 26 and Modifier TC

This is where in-house ultrasound revenue quietly walks out the door. The rule is simple, but the operational discipline is not:

• Practice owns the equipment AND interprets the images: bill the global code (no modifier).
• Practice owns the equipment, outside radiologist interprets: practice bills the technical component (e.g., 76805-TC); radiologist bills the professional component (76805-26).
• Practice does not own the equipment but interprets: practice bills 76805-26; the facility bills the -TC.

Place of service matters here too. POS 11 (office) supports global billing for practice-owned equipment. POS 22 (on-campus outpatient hospital) generally splits the components automatically – the facility takes the -TC. Mid-pregnancy transfers compound the problem: if a patient transfers at 22 weeks and the receiving practice does not realize the prior anatomy scan was already read and billed globally by an outside radiologist, the receiving practice can re-bill the same code and create a duplicate-service denial. Confirm the read source on every new OB chart.

Medical Necessity: Matching ICD-10 to Each Ultrasound Code

The ICD-10 pairing is the single biggest first-pass denial driver on ultrasound claims. Here is the practical pairing map:

• Z34.0x / Z34.8x – Supervision of normal pregnancy. Pairs with 76801 and 76805 for routine screening scans. Does not support 76811.
• Z3A.xx – Weeks of gestation. Required on virtually every OB claim. Missing Z3A is a common front-end rejection.
• O09.xxx – Supervision of high-risk pregnancy. Justifies 76811 when paired with a specific high-risk indication (advanced maternal age, prior obstetric history, etc.).
• O36.xxx – Maternal care for known or suspected fetal problem. Justifies 76816 follow-up scans.
• O30.xxx – Multiple gestation. Justifies the 76802 / 76810 / 76812 / 76814 add-on codes.

76811 specifically requires a documented high-risk indication – advanced maternal age, prior fetal anomaly, abnormal screening result (MSAFP, cfDNA), pre-gestational or gestational diabetes, suspected fetal growth restriction, or another payer-recognized risk factor. Routine pregnancy does not qualify.

The Three Biggest Denial Traps

Trap #1: Billing 76811 with a routine pregnancy diagnosis (Z34). The detailed fetal anatomy scan is reserved for high-risk pregnancies with a specific clinical indication. Payers expect O09, O36, or another high-risk ICD-10 attached to 76811. Practices that perform a “detailed” scan on every patient as policy and bill 76811 across the panel see denial rates well into the 40-60% range on the code. Fix: implement an EHR rule that locks 76811 selection behind one of the qualifying ICD-10 prefixes.

Trap #2: Missing the add-on codes for multiple gestations. A twin pregnancy ultrasound at 20 weeks is 76805 plus 76810 – one base code, one add-on. Practices that bill only 76805 for a twin scan leave half of the ultrasound revenue on the table. Fix: a chart-review checkpoint – any pregnancy with an O30 ICD-10 must have an add-on code (76802 / 76810 / 76812 / 76814) on every applicable ultrasound claim.

Trap #3: Billing the global ultrasound code when the practice does not own both components. The practice owns the machine, the tech runs the scan, and the read goes to an outside radiologist. The practice should bill 76805-TC; the radiologist bills 76805-26. Practices that bill the global code get paid initially – then clawed back when the radiologist’s -26 claim hits the same payer. Fix: confirm during onboarding whether reads are in-house or outsourced, and lock the modifier into the EHR’s ultrasound order set.

When Ultrasound Is Bundled Into the Global OB Package vs. Billed Separately

This is the single most misunderstood part of OB billing. The global OB package (59400, 59510, 59610, 59618) does not include ultrasounds. Ultrasounds are separately billable throughout the pregnancy. What is bundled into the global package: routine fetal heart tones recorded with a handheld Doppler during antepartum visits.

Mid-pregnancy transfers add complexity. When a patient transfers between practices, antepartum-only care is reported with 59425 (4-6 visits) or 59426 (7 or more visits), and any ultrasounds performed during that antepartum care attach to those codes separately. A receiving practice that absorbs a transferred patient at 30 weeks and performs an anatomy reassessment should report the ultrasound as a discrete claim, not roll it into a global package the practice cannot legitimately bill.

A practical self-audit: pull your last 50 ultrasound claims, line up each CPT against the documented gestational age, the linked ICD-10, and the read source. Any mismatch on any of those three axes is a coding rework opportunity. For more on how this fits into a broader RCM playbook, see our overview of best practices for revenue cycle management.

What This Looks Like in Practice: A 6-Provider OB/GYN Group

A 6-provider OB/GYN group in suburban Dallas-Fort Worth runs about 480 deliveries a year and roughly 2,100 OB ultrasounds annually. Before engagement, their baseline looked like this:

• 76811 denial rate of about 47% – the EHR template was attaching 76811 to routine Z34 visits
• Multiple-gestation add-on capture of 38% – the 76810/76812 add-ons were being missed on most twin scans
• Inconsistent -TC vs. -26 modifier handling on outside-read claims
• Ultrasound line revenue: approximately $612,000 per year

Ninety days into the engagement, after we locked the 76811 ICD-10 rule in the EHR, added a pre-bill scrub for multiple-gestation add-ons, and audited the outside-read claims for modifier accuracy:

• 76811 denial rate dropped from 47% to approximately 9%
• Multiple-gestation add-on capture rose from 38% to 92%
• Modifier -TC / -26 accuracy corrected across all outside-read claims
• Net ultrasound line revenue: ~$612K to ~$748K – roughly a 22% lift, about $136,000 annualized

The lift is in the published AAPC audit-result range for OB ultrasound optimization. The math is conservative and the rate of return is mostly about coding what was already clinically performed – not about coding more aggressively.

The AMS Approach to OB Ultrasound Billing

AMS Solutions has been a Dallas-based medical billing partner since 1992. Our AAPC-certified coding team processes more than 3 million claims a year, maintains a 95%+ clean claim rate, a 30 to 35-day A/R, and a sub-6% denial rate. On OB ultrasound specifically, that translates into pre-bill scrub rules that catch code-to-indication mismatches before submission, monthly ultrasound-line audits per provider, and payer-policy tracking for the BPP family so a quiet local-coverage-determination update does not turn into a denial wave.

If you want to go deeper, our OB/GYN medical billing overview lays out the full service-line approach, the 2026 OB/GYN CPT Cheat Sheet is a one-page reference your coders can pin up at their workstations, and our full billing services page covers what end-to-end RCM looks like with an AMS partnership.

Want a free OB ultrasound coding audit? We will pull a sample of recent ultrasound claims, score them against the 2026 CPT and ICD-10 rules, and tell you in plain numbers where the line is leaking revenue. Book a 30-minute consultation and we will walk you through what we find.

2026 Medicare PFS values referenced in this article are approximate national figures. Verify reimbursement against your MAC and payer mix before relying on any number for budgeting.

– Madison Gardner, President, AMS Solutions