Posts by ClinisysPACS
-
-
Hi Sir,
I connect a CARDIOPOINT Modality with Conquest and i have a problem in worklist, only with this modality and this is the log on the Modality:
<HisRequest Version="1">
<Sender Meaning="CardioPoint">1</Sender>
<SenderProductName>MEW.Main</SenderProductName>
<SenderProductVersion>2.41.474.0</SenderProductVersion>
<ControlID>17b0b6e9-0a18-4484-b060-68ec350ffb8f</ControlID>
<Receiver Meaning="DICOMService">7</Receiver>
<Request Meaning="ProcedureResults">4</Request>
<ReceivedDateTime>2023-03-03 11:29:59.4623966</ReceivedDateTime>
<FailedDateTime>2023-03-03 11:30:00.1656918</FailedDateTime>
<ExaminationGUID>7a15e8ce-75e3-45b3-83d9-ce6408adb705</ExaminationGUID>
<ExaminationAnalysisStatus>4</ExaminationAnalysisStatus>
<ReportPDFPath>C:\ProgramData\BTL\DicomService\ClientQueueStorage\17b0b6e9-0a18-4484-b060-68ec350ffb8f.pdf</ReportPDFPath>
</HisRequest>
-
Hi there,
How to connect Myrian dicom viewer to retrieve dicom images from Conquest server.
Thanks
-
Hi
I have this problem with standard machine.
Please what's the solution.
Thanks
-
this script will change all UIDs only for the Refused exam?
Without affecting the old exam?
-
this error is occurred in server status log
Importconverter0.0: sets preferred storage to MAG8
11/11/2022 09:12:22 [CLINISYS23] ***Inconsistent PatientBir in DICOMStudies: PatientID = '22G53671' StudyInsta = '360.1.2206370', Old='19870112', New='19760815'
11/11/2022 09:12:22 [CLINISYS23] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '22G53671' StudyInsta = '360.1.2206370', Old='22E04926', Refused='22G53671'
11/11/2022 09:12:22 [CLINISYS23] ***Error saving to SQL: 22G53671\1.3.76.6.1.2.5.2.6479.3.44876032202180741_0002_000001_16681543421abd.dcmThe exam with PatientID = '22G53671' is stored but is not saved to sql because it has the same studyinsta of an Old PatientID ='22E04926
so I can't see to the exam's images with viewer.
how can I solve this problem
-
Here I want to regenerate the exams who has the same studyinsta and here is the log:
All functions of this page are optional.
------------------- Regen device MAG9 --------------------
[CLINISYS23] ---------- Start archival operation -----------
[CLINISYS23] Regen single device: MAG9
[CLINISYS23] [Regen] I:\recup\22E04524\1.3.76.6.1.2.5.2.6479.3.44571064975061798_0001_000001_1641834953dfaf.dcm -SUCCESS
[CLINISYS23] [Regen] I:\recup\22E04524\1.3.76.6.1.2.5.2.6479.3.44571064997061805_0002_000001_1641834953dfb0.dcm -SUCCESS
[CLINISYS23] [Regen] I:\recup\22E04524\1.3.76.6.1.2.5.2.6479.3.44571065011061810_0003_000001_1641834954dfb1.dcm -SUCCESS
[CLINISYS23] [Regen] I:\recup\22E04524\1.3.76.6.1.2.5.2.6479.3.44571065037061817_0004_000001_1641834955dfb2.dcm -SUCCESS
[CLINISYS23] ***Inconsistent PatientBir in DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='19960229', New='20040404'
[CLINISYS23] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='22E04524', Refused='22G53330'
[CLINISYS23] ***[Regen] I:\recup\22G53330\1.3.76.6.1.2.5.2.6479.3.44875047297211350_0001_000001_166808251103ff.dcm -FAILED: Error SQL Add
[CLINISYS23] ***Inconsistent PatientBir in DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='19960229', New='20040404'
[CLINISYS23] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='22E04524', Refused='22G53330'
[CLINISYS23] ***[Regen] I:\recup\22G53330\1.3.76.6.1.2.5.2.6479.3.44875047297211350_0001_000001_16680838070b4f.dcm -FAILED: Error SQL Add
[CLINISYS23] ***Inconsistent PatientBir in DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='19960229', New='20040404'
[CLINISYS23] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='22E04524', Refused='22G53330'
[CLINISYS23] ***[Regen] I:\recup\22G53330\1.3.76.6.1.2.5.2.6479.3.44875047297211350_0001_000001_16680844980f35.dcm -FAILED: Error SQL Add
[CLINISYS23] ***Inconsistent PatientBir in DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='19960229', New='20040404'
[CLINISYS23] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='22E04524', Refused='22G53330'
[CLINISYS23] ***[Regen] I:\recup\22G53330\1.3.76.6.1.2.5.2.6479.3.44875047297211350_0001_000001_16680851800f36.dcm -FAILED: Error SQL Add
[CLINISYS23] ***Inconsistent PatientBir in DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='19960229', New='20040404'
[CLINISYS23] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='22E04524', Refused='22G53330'
[CLINISYS23] ***[Regen] I:\recup\22G53330\1.3.76.6.1.2.5.2.6479.3.44875047297211350_0001_000001_166808749112e7.dcm -FAILED: Error SQL Add
[CLINISYS23] ***Inconsistent PatientBir in DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='19960229', New='20040404'
[CLINISYS23] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = '22G53330' StudyInsta = '360.1.2205933', Old='22E04524', Refused='22G53330'
[CLINISYS23] ***[Regen] I:\recup\22G53330\1.3.76.6.1.2.5.2.6479.3.44875047297211350_0001_000001_16681497781958.dcm -FAILED: Error SQL Add
[CLINISYS23] Regeneration Complete
[CLINISYS23] ---------- End of archival operation -----------
-
the two exams have the same studyinsta.
One is stored and the other is blocked
-
Hi,
I have a different exams that have some studyinsta so it cannot be stored.
So I would like to change the studyinsta for the old exam and regenerate it.
How to change the studyinsta for the old exam?
Best regards
-
Hi,
I have this problem in the CT Modality when i try to retrieve the worklist:
-
Hi,
Sometimes the doctor does an exam without worklist, which causes an archiving problem and below the server status:
***Inconsistent PatientBir in DICOMStudies: PatientID = 'IU19007910' StudyInsta = '305.1038', Old='19740101', New='19620514'
***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = 'IU19007910' StudyInsta = '305.1038', Old='IU19012069', Refused='IU19007910'
***Error saving to SQL: IU19007910\1.2.392.200036.9125.3.446825321101107.657575107.175235_1001_001001_16567496940271.dcm
UPACS THREAD 3755: ENDED AT: Sat Jul 02 09:14:54 2022
how can i resolve this problem?
So i want to eliminate archive blocking when the doctor work without worklist.
Thanks.
-
i changed the value of 'reqcontras' in 'dicomworklist' to null
-
Thanks Marcel
I set 'ContrastAllergies' as nulle and it works
-
-
-
Hi,
I have many services on this server. So i will share all dicom file Sir.
The content cannot be displayed because it is no longer available. The content cannot be displayed because it is no longer available. The content cannot be displayed because it is no longer available. The content cannot be displayed because it is no longer available. The content cannot be displayed because it is no longer available. The content cannot be displayed because it is no longer available. -
-
-
Hi,
when I want to retrieve an exam. I get an "Host 'MRWP57319' will not accept image" error. Below is the log report from Conquest Server:[CLINISYS] Sending file: F:\Data07-2021\I2201832\1.3.46.670589.11.82221.5.0.8804.2021070111343707000_0202_000001_164544324703b3.dcm
[CLINISYS] [recompress]: recompressed with mode = un (strip=1)
[CLINISYS] Host 'MRWP57319' will not accept image
[CLINISYS] Sending file: F:\Data07-2021\I2201832\1.3.46.670589.11.82221.5.0.10652.2021070111321802299_0101_000001_164544324603a6.dcm
[CLINISYS] [recompress]: recompressed with mode = un (strip=1)
[CLINISYS] Sending file: F:\Data07-2021\I2201832\1.3.46.670589.11.82221.5.0.20120.2021070111390605000_0502_000001_164544325303ca.dcm
[CLINISYS] [recompress]: recompressed with mode = un (strip=1)
[CLINISYS] Host 'MRWP57319' will not accept image
[CLINISYS] Host 'MRWP57319' will not accept image
-
Hi there,
This error appears when i send an exam from the irm machine:
***[CompressJPEG]: No image VR
is there any probleme here???