Issue with Visualizing 3D Movie After Converting Raw DICOM to Cartesian DICOM in 3D Slice

Support
,
1

I came across information on converting 3D TEE data from raw DICOM to Cartesian DICOM using GE software. I am currently trying to achieve this and would greatly appreciate your insights.

First, I downloaded SlicerHeart in the 3D Slicer 5.9 software.
I then requested access to the Image3dAPI from GE and installed it on my Windows machine. Specifically, I unzipped the downloaded file and copied the bin64 folder of GE_CVUS_Loader-3.39.3 into the bin folder of 3D Slicer 5.9.

Next, I successfully ran the following command with administrative privileges to register the loader DLL in the Windows registry:

regsvr32 Image3dLoaderGe.dll

After that, in the Python console of 3D Slicer, I ran the following code:

import comtypes.client

try:
    loader = comtypes.client.CreateObject("GEHC_CARD_US.Image3dFileLoader")
    print("Loader object created successfully!")
except Exception as e:
    print(f"Failed to create loader object: {e}")

The loader object was created successfully.

Then, the 3D movie is the only one that not appear:

Despite everything working so far, the 3D movie does not appear in 3D Slicer.
However, if I upload the same file in other software like EchoPac or MicroDicom, it works properly.

Has anyone encountered this issue before? Is there an additional step required to visualize the 3D movie in 3D Slicer?

Any help would be greatly appreciated!

Immagine1
Immagine1964×200 72.3 KB

Immagine2
Immagine2964×348 56.1 KB

Immagine3
Immagine3964×495 164 KB

2

To provide more context, here is the link to the raw DICOM data (downloaded from EchoPac) I am trying to load:

3

Everything looks good. You have loaded the 3D volume successfully! The easiest way to show this in 3D is to go to Data module and drag-and-drop the image volume into the 3D view. You can get even nicer results if you use the Echo volume render module of SliceHeart.

Echo volume rendering settings:

image
image1920×999 139 KB

Echo Volume rendering video:

Microdicom and other basic viewers just replay the screenshots of the rendering. That looks nice but has very limited use, because you cannot rotate the view, you cannot do any measurements, analysis, 3D segmentation, etc. The screenshots look like this:

image
image1920×1074 101 KB

2 Likes
4

Thanks so much! It is working properly now

1 Like
5

Are you able to load GE 3D color Doppler data using your technique into 3D slicer? If so, I would appreciate your help.

6

I don’t think Image3dAPI currently supports color Doppler image reading, but your can reach out to be to get the Image3dAPI codec from GE anyway and also ask if they have a version that supports Doppler.

We got temporary license from Philips to a converter that creates readable files from their proprietary 3D color Doppler images (3D+t B-mode and velocity data) and we implemented a reader for these in Slicer. However, it took about two years from starting initial discussions to actually getting the converter.

7

Thats great to hear. I am able to use 3D-TEE color datasets obtained form Philips machines. do you have a set of instructions on how to import such files into 3D slicer? any help would be appreciated (do I have to save/convert them first in QLab etc). Thank you.

8

The QLab route only works for bmode. You can import those images into Slicer using SlicerHeart.

For color Doppler images you need to get another converter from Philips, which required some paperwork and took quite a bit of time for us.