# Unable to load Philips/GE 3D Ultrasound in Slicer

**URL:** <https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072>\
**Category:** Support\
**Tags:** dicom, ultrasound, slicerheart\
**Created:** [August 9, 2023, 5:36pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072 "2023-08-09T17:36:39Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nihar\_Parikh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/nihar_parikh/32/67062_2.png) [@Nihar\_Parikh](https://discourse.slicer.org/u/Nihar_Parikh)\
**Post date:** [August 9, 2023, 5:36pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/1 "2023-08-09T17:36:39Z")

</div>

I am trying to load 3D Philips/GE Ultrasound DICOM datasets in Slicer 5.2.2 and facing issues with that. It is not able to render the volume from these datasets. I have installed SlicerHeart extension. On using the Examine option in slicer for these dataset I get this error  
“Multi-frame image. If slice orientation or spacing is non-uniform then the image may be displayed incorrectly. Use with caution.Reference image in series does not contain geometry information. Please use caution.”

I can share these datasets for your troubleshooting. Also it would be of great help if you can share a valid 3D Ultrasound dicom datasets which can be loaded in Slicer with all volumetric data in the standard dicom fields.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 9, 2023, 5:38pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/2 "2023-08-09T17:38:12Z")

</div>

Each vendor implements 3D ultrasound storage completely differently, mostly in proprietary formats. All supported formats, capabilities and limitations for each are described in detail [here](https://github.com/SlicerHeart/SlicerHeart/blob/master/Docs/ImageImportExport.md#importing-dicom-files).

---

<div class="post-metadata">

**Author:** ![Nihar\_Parikh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/nihar_parikh/32/67062_2.png) [@Nihar\_Parikh](https://discourse.slicer.org/u/Nihar_Parikh)\
**Post date:** [August 9, 2023, 6:47pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/3 "2023-08-09T18:47:30Z")

</div>

Thank you for the documentation link. So as I understand 3D Slicer does not natively support any 3D US format from Philps/GE? It relies on Image3D API library from each vendor?

When I am trying to examine these datasets I dont see ultrasound plugin being used. What does it mean?

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/a/0/a03132770871eabd76704ab0e0b0cad43383e4b3.png)

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 9, 2023, 7:24pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/4 "2023-08-09T19:24:09Z")

</div>

Both Philips and Siemens uses several different formats for 3D ultrasound. Slicer can use Image3dAPI and other methods to read them.

What data do you have?

---

<div class="post-metadata">

**Author:** ![Nihar\_Parikh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/nihar_parikh/32/67062_2.png) [@Nihar\_Parikh](https://discourse.slicer.org/u/Nihar_Parikh)\
**Post date:** [August 9, 2023, 7:48pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/5 "2023-08-09T19:48:08Z")

</div>

Not sure If I will able to correctly answer that. I can share the datasets if that helps.

GE  
Manufacturer Model name - Vivid E95  
Private tag group - GEMS\_Ultrasound\_MovieGroup\_001

Philips  
Manufacturer Model name - EPIQ CVx  
Private tag group - Philips Imaging DD XX series

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 9, 2023, 8:31pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/6 "2023-08-09T20:31:49Z")

</div>

GE cardiovascular 3D ultrasound images can be read using the Image3dAPI interface. It is natively supported by Slicer and all you need to do is to get the codec from GE.

The situation is worse with Philips cardiac ultrasound business. They want to control the data _you_ acquire. Currently, the only way they allow getting access to their 4D images (but only basic B-mode data, no Doppler flow, no ECG, …) is via QLab Cartesian export as described [here](https://github.com/SlicerHeart/SlicerHeart/blob/master/Docs/ImageImportExport.md#import-philips-4d-cardiac-images).

Philips seems to abuse its position as an ultrasound image acquisition device manufacturer to suppress competition in ultrasound processing software market. We’ll probably start a petition to raise awareness of this issue, but if hospitals keep buying Philips then they may keep ignoring the complaints.

---

<div class="post-metadata">

**Author:** ![Nihar\_Parikh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/nihar_parikh/32/67062_2.png) [@Nihar\_Parikh](https://discourse.slicer.org/u/Nihar_Parikh)\
**Post date:** [August 9, 2023, 8:58pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/7 "2023-08-09T20:58:49Z")

</div>

Thanks for that information. Yeah that does not sound great if QLab Cartesian export is the only way to render US echo 3D studies from Philips. Is it the case that Philips don’t make Image3DAPI interface public or they just don’t implement it?  
SlicerHeart extension has couple of Philips plugins to read private data. Do they support any particular format ?

---

<div class="post-metadata">

**Author:** ![Nihar\_Parikh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/nihar_parikh/32/67062_2.png) [@Nihar\_Parikh](https://discourse.slicer.org/u/Nihar_Parikh)\
**Post date:** [August 10, 2023, 5:29pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/8 "2023-08-10T17:29:57Z")

</div>

Few questions if you can help to understand how to deal with Philips datasets

1. SlicerHeart extension has couple of Philips plugins to read private data. Do they support any particular format or manufactures?
2. Is it possible to reverse engineer Philips 3D ultrasound images and build decoder for reading volumetric data if there is no support from them ?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [August 10, 2023, 10:32pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/9 "2023-08-10T22:32:00Z")

</div>

There are a multiple of groups, who partially reverse-engineered the non-Cartesian (not-QLab-converted) Philips 4D ultrasound image file format. I’ll try to convince them to be nice and share what they have figured out so far.

---

<div class="post-metadata">

**Author:** ![Nihar\_Parikh](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/nihar_parikh/32/67062_2.png) [@Nihar\_Parikh](https://discourse.slicer.org/u/Nihar_Parikh)\
**Post date:** [August 10, 2023, 11:01pm UTC](https://discourse.slicer.org/t/unable-to-load-philips-ge-3d-ultrasound-in-slicer/31072/10 "2023-08-10T23:01:27Z")

</div>

Thanks that would help. I believe decoder for 3D image will be different than 4D image or we can use the same mechanism to decode 3D image as well?

I could see from the source code of DicomUltrasoundPlugin that it supports PhilipsAffinity 3D US image. Possible to share PhilipsAffinity 3D US image files just to see how a valid dataset looks like ?