OnePacs Forums

The workstation software works great for everything except CR. I can display the CR using the jpg viewer but not in the workstation.
Thanks,
Steve

Steve,

Sorry for the delay. Off the top of my head I'm not sure what would be causing this problem. We have radiologists that regularly view CR studies without issues. Do the CR studies appear in the list of studies available in the workstation? Or do they not store to the workstation at all? You can check this in your download manager.

Also, can you attempt to view a CR study in the workstation and then capture the study downloader logs? You can do so by pressing the debug... button at the bottom or the download manager.

Thanks,

Justin

The study is downloaded from the logger and I can view it using the jpg viewer. I had the same problem with the Clear Canvas Workstation. I am sending the images from a efilm station.

Steve,

Could you send me a sample of such an image? We use CR all the time without problems so I suspect that it's something unique in your DICOM images.

Thanks,

Justin

Justin,

I have reloaded the onepacs gateway and workstation onto different hardware. I still cannot view the CR images. I have attached the log file and the image. It looks like the workstation doesnot accept the study ID length. Can this be changed?
Thanks,
Steve

2010-03-26 09:23:15,875 [Retrieve from xraymri/OPWEB_CMH-355H9:4104] INFO - Preparing to connect to AE OPWEB_CMH-355H9 on host xraymri on port 4104 for move request to OPW.
2010-03-26 09:23:16,000 [DicomClient: 172.16.22.33:4104 [28]] INFO - Association Accepted from OPW to remote AE OPWEB_CMH-355H9:172.16.22.33:4104
2010-03-26 09:23:16,046 [DicomServer: 172.16.22.33 [32]] INFO - Received association:
Application Context: ==DICOM Application Context Name
Implementation Class: 1.2.40.0.13.1.1
Implementation Version: dcm4che-1.4.19
Local Maximum PDU Size: 116794
Remote Maximum PDU Size: 16352
Called AE Title: OPW
Calling AE Title: OPWEB_CMH-355H9
Presentation Contexts: 2
Presentation Context 1 [Accept] Abstract: Computed Radiography Image Storage Transfer: Explicit VR Little Endian
Presentation Context 3 [Accept] Abstract: Computed Radiography Image Storage Transfer: JPEG 2000 Image Compression

2010-03-26 09:23:20,734 [Pool:3] ERROR - Exception thrown
System.Exception: The file cannot be inserted into the Data Store (.\dicom_interim\ixhscvvc.gpj.dcm). The file has been moved to C:\onepacs\workstation\badfiles\44qlofox.lmq ---> OnePacs.Dicom.DataStore.DataValidationException: The specified value exceeds the maximum length (column=StudyId_:16, value='0402056110032537114').
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidateStringValue(Column column, Object sourceObject, PropertyInfo info)
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidatePersistentObject(Object obj)
at OnePacs.Dicom.DataStore.DataAccessLayer.DicomPersistentStoreValidator.Validate(DicomFile dicomFile)
at OnePacs.ImageViewer.Shreds.LocalDataStore.LocalDataStoreService.DicomFileImporter.ParseFile(ImportJobInformation jobInformation)
--- End of inner exception stack trace ---
2010-03-26 09:23:25,359 [Pool:14] ERROR - Exception thrown
System.Exception: The file cannot be inserted into the Data Store (.\dicom_interim\i4dkytts.ym3.dcm). The file has been moved to C:\onepacs\workstation\badfiles\5vrvk0cl.3e3 ---> OnePacs.Dicom.DataStore.DataValidationException: The specified value exceeds the maximum length (column=StudyId_:16, value='0402056110032537114').
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidateStringValue(Column column, Object sourceObject, PropertyInfo info)
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidatePersistentObject(Object obj)
at OnePacs.Dicom.DataStore.DataAccessLayer.DicomPersistentStoreValidator.Validate(DicomFile dicomFile)
at OnePacs.ImageViewer.Shreds.LocalDataStore.LocalDataStoreService.DicomFileImporter.ParseFile(ImportJobInformation jobInformation)
--- End of inner exception stack trace ---
2010-03-26 09:23:25,484 [Pool:3] ERROR - Exception thrown
System.Exception: The file cannot be inserted into the Data Store (.\dicom_interim\z4yxedub.wec.dcm). The file has been moved to C:\onepacs\workstation\badfiles\na1z0dxf.jvq ---> OnePacs.Dicom.DataStore.DataValidationException: The specified value exceeds the maximum length (column=StudyId_:16, value='0402056110032537114').
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidateStringValue(Column column, Object sourceObject, PropertyInfo info)
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidatePersistentObject(Object obj)
at OnePacs.Dicom.DataStore.DataAccessLayer.DicomPersistentStoreValidator.Validate(DicomFile dicomFile)
at OnePacs.ImageViewer.Shreds.LocalDataStore.LocalDataStoreService.DicomFileImporter.ParseFile(ImportJobInformation jobInformation)
--- End of inner exception stack trace ---
2010-03-26 09:23:25,593 [Pool:14] ERROR - Exception thrown
System.Exception: The file cannot be inserted into the Data Store (.\dicom_interim\h21ohfm0.1gi.dcm). The file has been moved to C:\onepacs\workstation\badfiles\rhol5u5r.ws0 ---> OnePacs.Dicom.DataStore.DataValidationException: The specified value exceeds the maximum length (column=StudyId_:16, value='0402056110032537114').
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidateStringValue(Column column, Object sourceObject, PropertyInfo info)
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidatePersistentObject(Object obj)
at OnePacs.Dicom.DataStore.DataAccessLayer.DicomPersistentStoreValidator.Validate(DicomFile dicomFile)
at OnePacs.ImageViewer.Shreds.LocalDataStore.LocalDataStoreService.DicomFileImporter.ParseFile(ImportJobInformation jobInformation)
--- End of inner exception stack trace ---
2010-03-26 09:23:25,734 [Pool:3] ERROR - Exception thrown
System.Exception: The file cannot be inserted into the Data Store (.\dicom_interim\tsg2gjej.oil.dcm). The file has been moved to C:\onepacs\workstation\badfiles\th50s3xe.klj ---> OnePacs.Dicom.DataStore.DataValidationException: The specified value exceeds the maximum length (column=StudyId_:16, value='0402056110032537114').
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidateStringValue(Column column, Object sourceObject, PropertyInfo info)
at OnePacs.Dicom.DataStore.PersistentObjectValidator.ValidatePersistentObject(Object obj)
at OnePacs.Dicom.DataStore.DataAccessLayer.DicomPersistentStoreValidator.Validate(DicomFile dicomFile)
at OnePacs.ImageViewer.Shreds.LocalDataStore.LocalDataStoreService.DicomFileImporter.ParseFile(ImportJobInformation jobInformation)
--- End of inner exception stack trace ---
2010-03-26 09:23:25,734 [DicomServer: 172.16.22.33 [32]] INFO - Received association release request from OPWEB_CMH-355H9 to OPW.
2010-03-26 09:23:25,734 [DicomServer: 172.16.22.33 [32]] INFO - <Statistics Type="TransmissionStatistics" Context="Transmission" Description="DICOM association from OPWEB_CMH-355H9 [172.16.22.33:2753] to OPW [172.16.20.14:44104]" MessageRate="0.52 msg/s" Speed="517.39 KB/s" IncomingBytes="4.90 MB" OutgoingBytes="780 bytes" OutgoingMessages="5 msg" IncomingMessages="5 msg" />
2010-03-26 09:23:25,781 [DicomClient: 172.16.22.33:4104 [28]] INFO - Success status received in Move Scu!
2010-03-26 09:23:25,796 [DicomClient: 172.16.22.33:4104 [28]] INFO - Association released from OPW to OPWEB_CMH-355H9
2010-03-26 09:23:36,109 [DicomServer: 127.0.0.1 [31]] INFO - Received association:
Application Context: ==DICOM Application Context Name
Implementation Class: 1.2.40.0.13.1.1
Implementation Version: dcm4che-1.4.17
Local Maximum PDU Size: 116794
Remote Maximum PDU Size: 131072
Called AE Title: OPW
Calling AE Title: ONEPACSPOLLER
Presentation Contexts: 1
Presentation Context 1 [Accept] Abstract: Verification SOP Class Transfer: Implicit VR Little Endian: Default Transfer Syntax for DICOM

2010-03-26 09:23:36,109 [DicomServer: 127.0.0.1 [31]] INFO - Received association release request from ONEPACSPOLLER to OPW.
2010-03-26 09:23:36,109 [DicomServer: 127.0.0.1 [31]] INFO - <Statistics Type="TransmissionStatistics" Context="Transmission" Description="DICOM association from ONEPACSPOLLER [127.0.0.1:4101] to OPW [127.0.0.1:44104]" MessageRate="0.00 msg/s" Speed="0 bytes/s" IncomingBytes="0 bytes" OutgoingBytes="0 bytes" IncomingMessages="0 msg" />

I dont see the image attached to the issue. Could you email it to support@onepacs.com?

Also in your workstation check the following value:


Go to the Tools menu, then select Tools > Utilities > Configure settings.

There is an item: OnePacs.ImageViewer.StudyManagement.ValidationSettings, click on that

The item which says "DisableSOPValidation", check if it's currently set to true or false. If it's set to false, change it to "True". Then, try to view the CR and let us know what happens.

Tom,
I emailed it to you. It appears that the Konica CR units produce a Study ID that is 19 characters and the workstation maximum characters is set to 16. How could I change the setting?

Thanks, Steve

Essentially the issue is that the DICOM 3.0 standard restricts study UIDs to 16 characters, whereas as you mention this device is generating 19 character UIDs. Not all DICOM devices are in compliance with the standards, though officially they're supposed to be. Currently the workstation will not accept DICOM store or import of studies with technically invalid study UIDs.

In tools > utilities > configure settings, there is a setting called OnePacs.ImageViewer.StudyManagement.ValidationSettings.DisableSopValidation.
This applies currently only to viewing images, not importing or storing them.

It is possible to view the DICOM file you sent us by setting the above described value to TRUE, then finding the file in the file explorer, right-clicking, and selecting "Open". It will display the image but not import it into the database.

Since there are some DICOM devices out there which generate invalid DICOM (Such as the CR device you mention), we agree it would be reasonable to allow users who need to work with such images to store them/import them. We'll make this change in the next version of the workstation, as an option to allow invalid UIDs to be stored/imported, for users who want to do that. That is expected to be out by the end of June.

Until then, you could use an alternative viewer to view the plain films, if you like, as OP can store to more than one destination at a time. For example, it sounds like you may have eFilm available, you could set the study retriever to store to both OPW and to eFilm, and use eFilm to view the CRs for now.

Thanks, I have figured out that I can change the CR to produce a 16 character Study ID. I will make the change and that should fix the issue.