

- Conquest and weasis install#
- Conquest and weasis update#
- Conquest and weasis archive#
- Conquest and weasis code#
- Conquest and weasis series#
The server supports a wide range of databases with ODBC (Windows) or without (Windows/Linux), including DbaseIII, MySQL, Postgres and SqLite. Some features added by the Conquest project are:įast error free and transparent compression (>2x) of image data on disk with NKI private, JPEG or JPEG2000 compression.Ī database browser and slice viewer integrated in the PACS system with options for: viewing DICOM header, creating BMP files (ideal for slides), sending selected images, printing, database fix tools such as changing patient IDs, deleting and anonymizing studies and series, and splitting and merging series. Use drag and drop to load ZIP, DICOM and HL7 files.Ī simple query/move user interface for diagnostic purposes, to improve your knowledge of DICOM, and to grab missing data from another server.Įlementary DICOM print server and client - prints to the default printer. JPEG, JPEG2000 compression and decompression (thanks to Bruce Barton) and RLE decompression supported.įlexible configuration of JPEG and NKI private compression with optional (de)compression of incoming, dropped, transmitted and archived files.Ī simple DICOM Modality Worklist implementation with HL7 import with configurable translation.Ī CGI WEB interface with several possible viewers (also on the Linux version with does not have a GUI). The server can act as an advanced (Lua) scriptable DICOM image forwarder, processor and/or DICOM image cache. The server integrates a small web client that also acts as a viewer.
Conquest and weasis code#
Integration between ZeroBraneStudio, a lean and mean Lua IDE and Conquest to unleash Lua scripting in the Conquest DICOM serverĭownload dicomserver150b.zip (23 MB, DICOM server + documentation + sample data + source + IDE integration)īrowse dicomserver150b release source code on GitHubīrowse latest Conquest dicomserver source code on GitHubĬontact, ConQuest DICOM server and extensions to MicroPACS The server and its webserver operation can be scripted in Lua for any type of processing and extension. Please check first our new FORUM (kindly hosted by the K-PACS team). Technical Contact, original MicroPACS (no longer active)Īdministrative / Licensing Contact, original MicroPACSĬopyright (c) 2020 University of Manchester.ĭeveloped by Marcel van Herk, Lambert Zijp and Jan Meinders the Netherlands Cancer Institute Radiotherapy Department maintained by Marcel van Herk, University of Manchester.Ĭopyright (c) 1995 Regents of the University of California.
Conquest and weasis update#
My question is that do i need to update both files as i have no idea about the queries and fields on which on queries are made or if i simply update the dicom-dcm4chee.properties the connector file will work for me.All rights reserved.ĭeveloped by: Mark Oskin, University of California, Davis Medical Center Department of Radiology with a Solaris port done and maintained by: Terry Rosenbaum Michigan State University Department of Radiology. # For dcm4chee-arc-light 5: =$/dcm4chee-arc/aets/DCM4CHEE/wado # Base URL of the WADO server (Mandatory property)
Conquest and weasis archive#
# AET, hostname and port of the archive (Mandatory properties)Īnd replace this portion with conquest wado I updated this portion with my configuration
Conquest and weasis series#
In db-dcm4chee.properties, should i replace this portion with available table namesĪrc.db.query.patientbirthdate=pat_birthdateĪrc.db.=VARCHAR2Īrc.db.=yyyyMMddĪrc.db.riesinstanceuid=series_iuidĪnd these with fields on which we run the searchĪrc.db.lect=select pa.pat_id, pa.pat_name, pa.pat_sex, pa.pat_birthdate, st.study_iuid, st.study_id, st.study_datetime, st.accession_no, st.ref_physician, st.study_desc, se.series_iuid, se.modality, se.series_desc, se.series_no, im.sop_iuid, im.inst_no from instance im, series se, study st, patient pa

There are two files db-dcm4chee.properties and dicom-dcm4chee.properties. Everything is fine but i am facing some problems in the configuration of weasis pacs connector file.
Conquest and weasis install#
Now i am trying to install and configure Weasis 2.6.1 and Weasis PACS Connector 6.1.0 with conquest PACS Server. My setup is Windows with tomcat as webserver. I am using weasis old version with conquest and its working fine.
