Posts by ljaszcza

Marcel,
Can you comment at all on how soon you plan to add finer granularity to the preretreive or forward patient queries?
The feature works well but needs more control. The ability to pull old studies is excellent but the workstation gets bogged down when a single cxr is sent over and forward patient send multiple large CT and MRI examinations on busy patients jackets.
If this is a low priority item, I may pay for a commercial routing program that includes these features, if the features will be included in conquest within 6 months or so, I will probably wait.
Thanks for any answer,
LJJ

I just double checked our configuration. Vitrea 2 3.9.0.0 and Conquest 12c and 13 beta both work without problems.
It really feels like a port problem. Or, do you have windows firewall (or other firewall) enabled?
The machines can check patient names so IP is correct but fail to transfer - port (or AETitle less likely) are wrong or blocked. Make sure that the conquest machine is correctly entered under DICOM in VI communicator.
Other than that, double check for the presence of firewalls or similar thing (both hardware and software) that are blocking the DICOM port traffic. Amazing how many times one of the machines (probably vitria) will have windows firewall running.
Anyhow, I have the above versions of Vitrea 2 and Conquest talking without problem so given that the configuration is ok, it should work.
LJJ

Hmm,
I have vitrea/conquest working without a problem.
Are you sure you added the AEtitles, address, etc correctly to both machines?
LJJaszczak MD

Thank You!
These seem like they would fit the bill. Like you mentioned, finer control would be good.
LJJaszczak MD

Is there a way to set up forwarding so that a comparison study is also sent over? For example, a CR getting forwarded would also echo the most recent (1 or more) CRs? Or a description "Chest" CR prompt forwarding the most recent "Chest" CR?

Does anyone have experience with Osirix and Conquest? I am trying to set up automatic retrieval/hanging of comparison films...

This is a database problem.
Looks you are using the dbase III install. It is telling you the same study instance has inconsistent patient ID with another study instance already in the db. The system cannot reconcile it and so fails on that study instance only.
I am not sure why you would have a duplicate study instance with different patient ID's. Has someone edited within the originating system (fuji) and submitted twice? If so, clear the old exam from the db, either by hand editing the db, or deleting the offending images and reinitializing the db.
My sql has sporadic problems similar to this. The thread is not much help but you can read it at http://www.image-systems.biz/p…&postorder=asc&highlight=
Good luck,
L.J.Jaszczak MD
USA

No errors since my last post.
I am awaiting the full moon for the next errors...
Darn sporadic problems.

Ok, the issue with the Hologic Delphi is definitely a Hologic specific problem. If the technologist leaves the accession field blank, the Delphi generates a malformed key (70918..1) which is duplicate and generates an SQL error because of the duplication.
I am working on the Fuji still. That problem is sporadic...

Here is a similar error but from Fuji Carbon CR. I have had no problems since install two months ago, but on the 7th and 8th Feb, two studies refuse to transfer with the SQL error.

[FAIRLIGHT] UPACS THREAD 56: STARTED AT: Sat Feb 10 17:58:36 2007
[FAIRLIGHT] A-ASSOCIATE-RQ Packet Dump
[FAIRLIGHT] Calling Application Title : "FCR-CSL "
[FAIRLIGHT] Called Application Title : "FAIRLIGHT_SCP "
[FAIRLIGHT] Application Context : "1.2.840.10008.3.1.1.1"
[FAIRLIGHT] Number of Proposed Presentation Contexts: 1
[FAIRLIGHT] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.1"
[FAIRLIGHT] Server Command := 0001
[FAIRLIGHT] 0000,0002 26 UI AffectedSOPClassUID "1.2.840.10008.5.1.4.1.1.1"
[FAIRLIGHT] 0000,0100 2 US CommandField 1
[FAIRLIGHT] 0000,0110 2 US MessageID 89
[FAIRLIGHT] 0000,0700 2 US Priority 0
[FAIRLIGHT] 0000,0800 2 US DataSetType 258
[FAIRLIGHT] 0000,1000 52 UI AffectedSOPInstanceU "1.2.392.200036.9125.9.0.84911893.10687232.2020745846"
[FAIRLIGHT] FreeStore Left 1560849 on G:\
[FAIRLIGHT] ***Failed MYSQLExec : INSERT INTO DICOMImages (SOPInstanc, SOPClassUI, ImageNumbe, ImageDate, ImageTime, AcqDate, AcqTime, AcqNumber, SamplesPer, PhotoMetri, Rows, Colums, BitsStored, ImageType, ImagePat, SeriesInst, AccessTime, ObjectFile, DeviceName) VALUES ('1.2.392.200036.9125.9.0.84911893.10687232.2020745846', '1.2.840.10008.5.1.4.1.1.1', '1001', '20070207', '085811.687', '20070207', '085800.578', '001', '1', 'MONOCHROME1', '3015', '2505', '10', 'DERIVED\\PRIMARY\\POST_PROCESSED\\100000', '33308', '1.2.392.200036.9125.3.1911412011834.64512579345.14523', 1171151904, '33308\\1.2.392.200036.9125.3.1911412011834.64512579345.14523_1001_001001_11711519180027.v2', 'MAG0')
[FAIRLIGHT] ***Error: Duplicate entry '1.2.392.200036.9125.9.0.84911893.10687232.2020745846' for key 1
[FAIRLIGHT] ***Error: 0: :
[FAIRLIGHT] ***Unable to DB.Add()
[FAIRLIGHT] ***SQL: INSERT INTO DICOMImages (SOPInstanc, SOPClassUI, ImageNumbe, ImageDate, ImageTime, AcqDate, AcqTime, AcqNumber, SamplesPer, PhotoMetri, Rows, Colums, BitsStored, ImageType, ImagePat, SeriesInst, AccessTime, ObjectFile, DeviceName) VALUES ('1.2.392.200036.9125.9.0.84911893.10687232.2020745846', '1.2.840.10008.5.1.4.1.1.1', '1001', '20070207', '085811.687', '20070207', '085800.578', '001', '1', 'MONOCHROME1', '3015', '2505', '10', 'DERIVED\\PRIMARY\\POST_PROCESSED\\100000', '33308', '1.2.392.200036.9125.3.1911412011834.64512579345.14523', 1171151904, '33308\\1.2.392.200036.9125.3.1911412011834.64512579345.14523_1001_001001_11711519180027.v2', 'MAG0')
[FAIRLIGHT] ***Error: Duplicate entry '1.2.392.200036.9125.9.0.84911893.10687232.2020745846' for key 1
[FAIRLIGHT] ***Error: 0: :
[FAIRLIGHT] ***Error saving to SQL: 33308\1.2.392.200036.9125.3.1911412011834.64512579345.14523_1001_001001_11711519180027.v2
[FAIRLIGHT] UPACS THREAD 56: ENDED AT: Sat Feb 10 17:58:39 2007
[FAIRLIGHT] UPACS THREAD 56: TOTAL RUNNING TIME: 3 SECONDS

Hmm, in producing the error I stumbled upon something. We do not use accession numbers. If I leave the accession number blank I produce the error. If I include it ("0" or any value), I don't seem to generate an error. I will try to work with this some more and post with info.
LJJ

I can reproduce this problem with the hologic delphi. Here is the debug info.

2/10/2007 4:55:39 PM [FAIRLIGHT] ***Failed MYSQLExec : INSERT INTO DICOMSeries (SeriesInst, SeriesNumb, Modality, Manufactur, ModelName, BodyPartEx, SeriesPat, StudyInsta, AccessTime) VALUES ('1.2.840.113850.70918..1', '1', 'OT', 'HOLOGIC', 'Delphi C (S/N 70918)', 'HIP', '16633', '1.2.840.113850.70918.', 1171148128)
2/10/2007 4:55:39 PM [FAIRLIGHT] ***Error: Duplicate entry '1.2.840.113850.70918..1' for key 1
2/10/2007 4:55:39 PM [FAIRLIGHT] ***Error: 0: :
2/10/2007 4:55:39 PM [FAIRLIGHT] ***Unable to DB.Add()
2/10/2007 4:55:39 PM [FAIRLIGHT] ***SQL: INSERT INTO DICOMSeries (SeriesInst, SeriesNumb, Modality, Manufactur, ModelName, BodyPartEx, SeriesPat, StudyInsta, AccessTime) VALUES ('1.2.840.113850.70918..1', '1', 'OT', 'HOLOGIC', 'Delphi C (S/N 70918)', 'HIP', '16633', '1.2.840.113850.70918.', 1171148128)
2/10/2007 4:55:39 PM [FAIRLIGHT] ***Error: Duplicate entry '1.2.840.113850.70918..1' for key 1
2/10/2007 4:55:39 PM [FAIRLIGHT] ***Error: 0: :
2/10/2007 4:55:39 PM [FAIRLIGHT] ***Error saving to SQL: 16633\1.2.840.113850.70918..1_0001_000001_11711481390020.v2

Hi,
I need some help troubleshooting a **Error saving to SQL message. I sporadically get this message from my Fuji CR and one of several Toshiba GX CT scanners and conquest does not accept the images. I also do see this problem with my Hologic Delphi Dexa unit all the time (used to work and then stopped after a software update).
I am running latest conquest with native SQL (had the problem with mysql odbc too though, upgraded to native a month ago). System is great otherwise, no problems.
I can't find any useful info in the logs. Has anyone dealt with this issue out there?
Thanks,
L.J.Jaszczak MD