Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-block-list.php on line 199

Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 133

Deprecated: Return type of Pimple\Container::offsetGet($id) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 98

Deprecated: Return type of Pimple\Container::offsetSet($id, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 79

Deprecated: Return type of Pimple\Container::offsetUnset($id) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 143

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 60

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 66

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 72

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 76

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/lockout/execute-lock/abstract-context.php on line 56

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 578

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 585

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 606

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 613

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/lib/class-itsec-lib-distributed-storage.php on line 620

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 395

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 387

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 381

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 399

Deprecated: Return type of WPCF7_Validation::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 78

Deprecated: Return type of WPCF7_Validation::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 72

Deprecated: Return type of WPCF7_Validation::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 59

Deprecated: Return type of WPCF7_Validation::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/contact-form-7/includes/validation.php on line 82

Deprecated: Automatic conversion of false to array is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/better-wp-security/core/modules.php on line 137

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/script-loader.php on line 348

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 22

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 28

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/wilbul4/maxoutofpocket.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp.php on line 173

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/wp-db.php on line 3030

Warning: Cannot modify header information - headers already sent by (output started at /home/wilbul4/maxoutofpocket.com/wp-includes/class-wp-theme.php:9) in /home/wilbul4/maxoutofpocket.com/wp-includes/feed-rss2.php on line 8
76801 Archives - Max Out of Pocket https://www.maxoutofpocket.com Where personal finance meets healthcare. Mon, 28 Dec 2020 14:30:21 +0000 en-US hourly 1 https://wordpress.org/?v=5.7.11 https://i1.wp.com/www.maxoutofpocket.com/wp-content/uploads/2020/12/cropped-Max_OOP_Profile_Photo.png?fit=32%2C32&ssl=1 76801 Archives - Max Out of Pocket https://www.maxoutofpocket.com 32 32 157852510 How Much Does An Obstetric Ultrasound Cost In The First Trimester!?! https://www.maxoutofpocket.com/how-much-does-an-obstetric-ultrasound-cost-in-the-first-trimester/?utm_source=rss&utm_medium=rss&utm_campaign=how-much-does-an-obstetric-ultrasound-cost-in-the-first-trimester https://www.maxoutofpocket.com/how-much-does-an-obstetric-ultrasound-cost-in-the-first-trimester/#comments Mon, 28 Dec 2020 14:30:18 +0000 https://www.maxoutofpocket.com/?p=9070 I suppose the time has come to let the cat out of the bag. The Max Out of Pocket crew is expecting! We are really excited! But more on that later. First things first, how much does an obstetric ultrasound cost in the first trimester? Let’s be real. I am probably the last person the healthcare finance industry wants going through this process. As healthcare pricing and surprise medical bills have become a hot topic...

The post How Much Does An Obstetric Ultrasound Cost In The First Trimester!?! appeared first on Max Out of Pocket.

]]>

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-includes/wp-db.php on line 3030

Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /home/wilbul4/maxoutofpocket.com/wp-content/plugins/jetpack/class.jetpack.php on line 4222
I suppose the time has come to let the cat out of the bag. The Max Out of Pocket crew is expecting! We are really excited! But more on that later. First things first, how much does an obstetric ultrasound cost in the first trimester?

Let’s be real. I am probably the last person the healthcare finance industry wants going through this process. As healthcare pricing and surprise medical bills have become a hot topic in recent years, more and more expecting parents are asking questions about how much things are going to cost them.

They should. Some of the wild pricing swings I have witnessed throughout my career in healthcare finance are almost unexplainable. But you need to know what questions to ask.

One of the early expenses during the pregnancy process will be an ultrasound. This is often initially done during the first trimester to both confirm the pregnancy and estimate how far along the mother is. The first trimester is generally considered the period of time when the mother is less than 14 weeks pregnant.

But how much does an obstetric ultrasound cost in the first trimester?

Great. Is Max going to take one of the hallmark moments of pregnancy and financially dissect it? Absolutely. But now, I have good reason to.

Two Approaches to the Ultrasound Exam

The first thing to know is there are two approaches to the obestetric ultrasound exam: the transabdominal approach and the transvaginal approach.

The transabdominal approach is typical of what you might see on a TV commercial or in the movies.

Another approach is transvaginal. My understanding is the transvaginal approach is mostly used early in the pregnancy when transabdominal ultrasound did not provide enough information.

In my experience, depending on the clinic, I sometimes see these both ordered together right from the start. Physician preference or protocol might have something to do with how these are ordered, but I am not an expert on ordering patterns. So as always, talk through this with your provider if you have questions about the appropriate approach.

Today, I will be covering the traditional transabdominal approach during the first trimester where a transducer is moved over the abdomen. The mother is asked to present with a full bladder to help get clearer images. The transducer produces ultrasonic waves directed at the fetus, pregnant uterus, and surrounding pelvic structures of the mother.

And just like that, hopefully, you have an image of a fetus. Here is ours from back in September.

How Much Does An Obstetric Ultrasound Cost? This image would cost me about $500 at my local hospital.
I am told that’s a fetus somewhere in there

Obstetric Ultrasound CPT Code

In healthcare, we represent almost every little service with a five digit code.

The CPT code that represents this first ultrasound is 76801. It is an abdominal ultrasound of a uterus that has been pregnant for less than 14 weeks. There is both a fetal and maternal evaluation done during this service. The radiologist reviews the images of the fetus, pregnant uterus, and maternal pelvic structures and provides a written interpretation of the images back to the OBGYN and midwife.

The “consumer-friendly” description of this service is “an abdominal ultrasound of a pregnant uterus“.

If the mother happens to have a second routine ultrasound done in the first trimester, 76801 is used as well. As you might expect, she will be charged again for the service. 

I should mention, a separate ultrasound where they measure some fluid near the fetal neck is also often ordered at some point, but we will learn more about that in another post.

Facility Fee vs. Professional Fee

There are often two separate fees for an ultrasound. This is one of the harder concepts for patients to understand.

The facility fee represents the equipment, supplies, and trained technician performing the actual ultrasound. You might also hear this called the “technical” component of the service. Unlike what you might have seen on daytime television or Dr. House, the obstetrician or midwife normally wouldn’t do the official ultrasound where measurements are taken. It is often farmed out to a trained sonographer.  

This equipment, room, and table are just a few of the things that make up the facility fee

Then there is the professional fee. This fee is for a trained radiologist to write a written report of his or her interpretation of the image. The radiologist should not be confused with the sonographer as these are two separate skill sets. This is sometimes called a “read fee” for “reading” the image. Again, generally, the obstetrician or midwife wouldn’t necessarily do the formal interpretation of the image.

If the service is provided in a clinic or imaging center, both the facility fee and radiologist interpretation are often combined into one charge. This is sometimes referred to as a global charge.

However, if the service is provided in a hospital imaging department, the radiologist interpretation will often be a completely separate charge/claim from the hospital facility fee.

How Much does an Obstetric Ultrasound Cost in the Hospital?

Sometimes, the OBGYN office will be conveniently located on a hospital campus not too far from the imaging department. A short walk down the hall will take you out of the clinic setting and into the hospital setting. It might even be right across the street.  

In my experience, unless it is an emergency, this convenient walk will cost you. The second you walk into that hospital you are subject to the inflated prices that come along with it.

I have personally seen hospital pricing for this ultrasound range anywhere from $250 – $1,200. The hospital I would likely have this service charges about $925. But let’s hope Max never needs to report to imaging to have an obstetrical ultrasound.

Of course, that is the retail price. I would get mine on sale with a discount through my insurance. My insurance negotiates that $900 hospital price down to $475. That entire $475 balance would hit my deductible and come right out of my pocket.

So, I am already out-of-pocket $475, and the radiologist has not even read my image yet. I would get a separate bill for that. I believe my insurance would get the “read” fee down to about $70, all of which would hit my deductible.

$475 facility fee + $70 read fee = $545 out-of-pocket

I wonder how many ultrasound images a radiologist can read per hour? Could make for some good cash flow.

A Few Examples

I thought sharing a few examples of hospital pricing might be helpful.

You might remember, I defended Hudson Hospital in Wisconsin last year against NPR on a little billing mishap they had with nitrous oxide. I called that one Midwife Crisis, $5,000 nitrous. The midwife was clearly trying to stir the pot.

Since we happen to be talking about the pregnancy process again, I was wondering what Hudson Hospital charges for the abdominal ultrasound. According to their chargemaster, they charge $502. Their price comes in about $400 less than the local hospital I would go to.

The University of Michigan charges a little more.

How much does an obstetric ultrasound cost at the University of Michigan? $775.00

Johnson Memorial in Indiana charges $679. I love their chargemaster because they went above and beyond by including the CPT code.

How much does an Obstetric Ultrasound Cost in a Clinic/Imaging Center?

If you receive this service in an actual clinic or imaging center, we would be looking at a much more reasonable price of $150 – $325 for the entire service. The 50th percentile would come in at around $220. If you have insurance, it would likely negotiate that price down even further.  

My own insurance has negotiated this down to about $170 for everything at a clinic in my market. That includes the procedure itself and the professional interpretation.

For us, that’s $375 cheaper than having it in the hospital.

So, unless you have already hit your max out-of-pocket for the year, I would try to have the ultrasound in a clinic setting. It might even make sense to drive to an imaging center if your clinic/OBGYN does not offer an ultrasound within the clinic walls.

How much does the Government Pay?

I always like to compare what government payers like Medicare might pay for the same service. They have the ultimate pricing power and are a good indicator of what it actually costs to provide a service. State Medicaid programs often pay less than cost.

How much does an obstetric ultrasound cost the Medicare program? Although not a lot of Medicare patients are having babies, they will pay about $118 for the entire service in the clinic setting in 2021. That covers both the ultrasound ($73) and professional interpretation ($45). That rate would be adjusted slightly depending on where in the country the service is provided.

If the service was provided in a hospital, Medicare would pay the hospital $109 in 2021. Another $45 or so would be paid for the professional interpretation. That’s about $154 out the door.

North Carolina Medicaid would pay a clinic $107.22 for the full global charge according to their most recent fee schedule from 12/21/2020. It is not uncommon for the state Medicaid programs to come in under Medicare rates like this.

North Carolina Medicaid fee-schedule

Take-Home

As you can see, the pricing differences for a relatively simple service can be stark. If you are lucky enough to have insurance, you have even more work to do because you need to find out how much they have negotiated the price down to. That goes for both the clinic and hospital setting.

My recommendation for most consumers would be to have the ultrasound done at a clinic or imaging center, assuming it’s not an emergency. It would save the Max Out of Pocket crew about $375 to drive to an imaging center for this service.

That said, if you know you are going to meet your max out-of-pocket for the year, pricing starts to go out the window. If you are due late in the year, odds are you will hit your max out-of-pocket and your insurance will start picking up all the bills. That makes all this a moot point and convenience might come more into play.

This is our out of-pocket-max, you will want to keep an eye on this number

But it is worth keeping an eye on things, particularly if your services are going to be split up over two calendar years. These early tests can really add up as they all hit your deductible. Then, the deductible will re-set again for you in January. Keeping pricing in check and going to a clinic or imaging center might save you some serious money.

Homework: How much does an obstetric ultrasound cost at your local hospital?

The post How Much Does An Obstetric Ultrasound Cost In The First Trimester!?! appeared first on Max Out of Pocket.

]]>
https://www.maxoutofpocket.com/how-much-does-an-obstetric-ultrasound-cost-in-the-first-trimester/feed/ 6 9070