Latest EFILM V2.1 doesn't work with Pacsone

hyounker · Post by **hyounker** » Thu Dec 15, 2005 1:34 pm

I'm having the same trouble with images from a GE LightSpeed Plus CT Scanner. The error wasn't listed before, but I assume it's:

Unable to display image
Error: ICP_STATUS_FILE_NOT_OPEN

I found Jeff's entries in the eFilm forum showing this error.

Also, if the eFilm screen is set-up to show the first two series in a study, when you first pull up one of these studies, you get the following error usually in the window on the right:

Unable to display image
Error: ICP_STATUS_MC_INVALID_TAG

Attempting to pull up a series afterward, you get the first error.

The registry entry didn't help my problem though. I will email you a screen shot of my registry entry to verify that I did it correctly.

Thanks for any help.

Post by **pacsone** » Thu Dec 15, 2005 2:24 pm

hyounker wrote: Unable to display image
Error: ICP_STATUS_MC_INVALID_TAG

This error suggests eFilm had trouble with one of the tag (Dicom element) in the image. You should contact eFilm tech support to find out exactly which tag it was not able to handle.

hyounker · Post by **hyounker** » Thu Dec 15, 2005 2:45 pm

What about the other error and the previously discussed solution? I suspect that Jeff was getting this same tag error, but because it only lasts until you attempt to view another study, he may have never saw it or failed to mention it.

Do the entries in my email look correct?

Post by **pacsone** » Thu Dec 15, 2005 3:45 pm

Jeff is registered in our forum, so you can look him up and send him email or private messages about the error.

But I think it may be faster to resolve the issue if you contact eFilm tech support directly about the error. They should be able to tell you what the error means and/or which tag eFilm didn't like.

hyounker · Post by **hyounker** » Thu Dec 15, 2005 4:40 pm

Unfortunately, the only method to look at such information in efilm is to click on an image and do a dicom dump. But, as the error states, there is an error opening the file, so doing a dicom dump results in another error stating efilm cannot open the file.

As for the tag error, it is impossible to gather any information about it. After the error appears, you cannot do anything in the image window that the error displays in, because it disappears and the "file not open" error appears.

I have already contacted eFilm several hours ago. They are "looking into it".

In the meanwhile, can you answer the question posted by riteview earlier in this thread.

Thanks,

hyounker

Post by **pacsone** » Thu Dec 15, 2005 5:23 pm

riteview wrote:I think same issue with me for Efilm, I have added the string but is the String value 1.2.840.10008.1.2. (period at the end) or 1.2.840.10008.1.2 (no period at the end).

The transfer syntax uid is 1.2.840.10008.1.2, without the period at the end.

Post by **pacsone** » Thu Dec 15, 2005 5:26 pm

hyounker wrote: As for the tag error, it is impossible to gather any information about it. After the error appears, you cannot do anything in the image window that the error displays in, because it disappears and the "file not open" error appears.

You can try having eFilm Import that raw Dicom image without any network transfer, and see if eFilm can import it.

If my guess is correct, you will run into the same error you got when sending the same image to eFilm, because it does not like certain data element in this image.

Guest · Post by **Guest** » Thu Dec 15, 2005 9:43 pm

I found some ultrasound images, Picker MRI images, and GE ProSpeed CT images on CDs. I imported and displayed these images in eFilm with no problems. I transferred to Pacsone and retrieved. All returned to eFilm without errors.

I burned a CD, to include patients from the LightSpeed scanner that previously caused the errors, from Pacsone and imported those images into eFilm. These images displayed normally without errors. From this, it would appear that the problem is transmit related.

Digging around in eFilm, I found the following error in the error log several times, corresponding with the failed image transfers.

Does any of this help the cause!!?? I have also sent all this info to eFilm support.

(1376) 12-15 11:12:05.07 MC3 W: Error with tag (5404,4904) at byte offset 282565 when parsing file

(1376) 12-15 11:12:05.11 ICPDICOMFile::Open - Could not read data from file "C:\Program Files\Merge eFilm\eFilm\DICOM\\1.2.840.113619.2.55.3.2831170660.3064.1123250097.86\1.2.840.113619.2.55.3.2831170660.3064.1123250097.273\1.2.840.113619.2.55.3.2831170660.3064.1123250097.274.1.dcm"

(1376) 12-15 11:16:55.97 ICPDICOMFile::GetImageParams - GetTagToString() Error retrieving MC_ATT_ROWS (0x00280010) "C:\Program Files\Merge eFilm\eFilm\DICOM\\1.2.840.113619.2.55.3.2831170660.3064.1123250097.86\1.2.840.113619.2.55.3.2831170660.3064.1123250097.92\1.2.840.113619.2.55.3.2831170660.3064.1123250097.93.1.dcm"

(1376) 12-15 11:16:56.54 ICPDICOMFile::GetImageParams - GetTagToString() Error retrieving MC_ATT_ROWS (0x00280010) "C:\Program Files\Merge eFilm\eFilm\DICOM\\1.2.840.113619.2.55.3.2831170660.3064.1123250097.86\1.2.840.113619.2.55.3.2831170660.3064.1123250097.92\1.2.840.113619.2.55.3.2831170660.3064.1123250097.93.90.dcm"

(1376) 12-15 11:16:56.66 ICPDICOMFile::GetImageParams - GetTagToString() Error retrieving MC_ATT_ROWS (0x00280010) "C:\Program Files\Merge eFilm\eFilm\DICOM\\1.2.840.113619.2.55.3.2831170660.3064.1123250097.86\1.2.840.113619.2.55.3.2831170660.3064.1123250097.273\1.2.840.113619.2.55.3.2831170660.3064.1123250097.274.59.dcm"

(1376) 12-15 11:20:46.20 ICPDICOMFile::GetImageParams - GetTagToString() Error retrieving MC_ATT_ROWS (0x00280010) "C:\Program Files\Merge eFilm\eFilm\DICOM\\1.2.840.113619.2.55.3.2831170660.3064.1123250097.86\1.2.840.113619.2.55.3.2831170660.3064.1123250097.92\1.2.840.113619.2.55.3.2831170660.3064.1123250097.93.1.dcm"

(1376) 12-15 11:20:46.70 ICPDICOMFile::GetImageParams - GetTagToString() Error retrieving MC_ATT_ROWS (0x00280010) "C:\Program Files\Merge eFilm\eFilm\DICOM\\1.2.840.113619.2.55.3.2831170660.3064.1123250097.86\1.2.840.113619.2.55.3.2831170660.3064.1123250097.92\1.2.840.113619.2.55.3.2831170660.3064.1123250097.93.90.dcm"

(1376) 12-15 11:20:46.71 ICPDICOMFile::GetImageParams - GetTagToString() Error retrieving MC_ATT_ROWS (0x00280010) "C:\Program Files\Merge eFilm\eFilm\DICOM\\1.2.840.113619.2.55.3.2831170660.3064.1123250097.86\1.2.840.113619.2.55.3.2831170660.3064.1123250097.273\1.2.840.113619.2.55.3.2831170660.3064.1123250097.274.59.dcm"

Post by **pacsone** » Thu Dec 15, 2005 10:05 pm

Anonymous wrote: (1376) 12-15 11:12:05.07 MC3 W: Error with tag (5404,4904) at byte offset 282565 when parsing file

Technically the data elements burned in the CD may not be exactly the same as the elements transferred through the network, depending on what application you use to burn the CD.

The error above actually indicated which data element was having trouble with. Another test you can try is to send the same image from the source AE directly to eFilm (without going through PacsOne), and see if eFilm can receive it successfully.

hyounker · Post by **hyounker** » Fri Dec 16, 2005 2:02 pm

I am working in a test environment at my company's offices, not at an imaging facility. I have one server with PACSONE on it, and a laptop acting as the eFilm workstation. This simulates conditions from the site that I am building this server for. All the images I am using were transferred directly to eFilm from the source modality at another site, burned to CD, then brought here for testing purposes with eFilm and PACSONE. We don't have any problems on-site with eFilm with any of the modalities.

No word from eFilm yet.

hyounker · Post by **hyounker** » Wed Apr 12, 2006 3:30 pm

Pacsone,

I never resolved this issue because the customer at the time was removing a GE CT scanner and replacing with Toshiba. No problems to date.

However, I have a new customer that is planning to use the PACSONE Server with a GE LightSpeed Plus CT Scanner.

Have you experienced any other issues similar to the before-mentioned problems with GE CT Scanners? Any resolutions?

I will be building this server soon and will test with GE images asap.

Thanks,

hyounker

Post by **pacsone** » Thu Apr 13, 2006 12:20 am

We have not received any problem report from users with the GE LightSpeed CT scanner.