Conquest DICOM Server - A Scriptable and Configurable DICOM Solution

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:Fast error free and transparent compression (>2x) of image data on disk with NKI private, JPEG or JPEG2000 compression.A 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.A simple query/move user interface for diagnostic purposes, to improve your knowledge of DICOM, and to grab missing data from another server.Elementary DICOM print server and client - prints to the default printer.JPEG, JPEG2000 compression and decompression (thanks to Bruce Barton) and RLE decompression supported. Flexible configuration of JPEG and NKI private compression with optional (de)compression of incoming, dropped, transmitted and archived files.A simple DICOM Modality Worklist implementation with HL7 import with configurable translation.A 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.The server and its webserver operation can be scripted in Lua for any type of processing and extension.A partial DICOMWeb interface is provided that works well with OHIF

For lua: I installed lua5.1 and lua 5.3 side by side. Since conquest and its extensions are all based on lua5.1 I would suggest to so the same. Nothing has been tested against Lua5.3., such as web server and anonymisation.

download conquest dicom server free

All selected tools are easy to install by following a step-by-step installation wizard. Additionally, some require other supporting applications, frameworks, or runtime environments to be pre-installed, depending on what type of programming language in which they were developed. Toolkits developed using Java will need a Java Runtime to be pre-installed. A NET framework is needed for applications that are developed using C#. Some toolkits require other, more specific, applications to be pre-installed to support the complete process of reading or processing the DICOM files. For example, Tudordicom and CTP also require additional Java ImageIO Tools [27] to be present on the system to be able to read and process the compressed DICOM files. The GDCM installation under Microsoft Windows requires a Win32 OpenSSL [28] to be pre-installed, while YAKAMI needs DirectX to be present. All required pre-installations are available freely from the web from their respective manufacturers.

The DICOM Library is an online service to share images. It is developed mainly for educational and scientific purposes [15]. Its output data were well de-identified and downloadable. However, the uploading of images to be de-identified by the service should be considered further since the process is done outside the domain of the sender. This means that even though the source files are claimed to be de-identified at the client side, the implementation of an unsupervised process involving uploading to a third party should be utilized with care and checked with hospital security regulations. Using this kind of service may cause a security breach due to the possibility that unmodified parts of data still contain sensitive information. It might, thus, not be allowed according to the security policies of most institutions since it is unknown what exactly happens with the uploaded files at the server side. Furthermore, the files could be retained at the server for some unknown period of time without the uploading party being aware of this storage. Even though online, web-based anonymization services are not ideal for the transfer of such confidential data using standard transfer protocols, there are still possibilities to make such methods acceptable, either by moving the services to a more secure line or transfer only data without burnt-in information within the images. However, although the transfer is claimed to be secure, information that is not processed by such service, i.e., burnt-in information within the images themselves, can still reveal patient identity. We suggest that the use of online services without full control from the user should be avoided as much as possible.

How to install conquest dicom server on windows

Conquest dicom server tutorial and documentation

Conquest dicom server features and benefits

Conquest dicom server web interface and viewers

Conquest dicom server image compression and decompression

Conquest dicom server modality worklist and hl7 import

Conquest dicom server source code and github repository

Conquest dicom server lua scripting and automation

Conquest dicom server database configuration and management

Conquest dicom server printing and image editing

Conquest dicom server query and retrieve functions

Conquest dicom server image format conversion and export

Conquest dicom server support and forum

Conquest dicom server license and disclaimer

Conquest dicom server comparison and review

Conquest dicom server troubleshooting and error fixing

Conquest dicom server performance and speed test

Conquest dicom server security and encryption

Conquest dicom server customization and integration

Conquest dicom server backup and restore

Conquest dicom server linux version and installation guide

Conquest dicom server for veterinary images and research

Conquest dicom server for teaching and training purposes

Conquest dicom server for demonstration and presentation

Conquest dicom server for clinical and diagnostic use cases

Conquest dicom server for image archiving and storage

Conquest dicom server for image processing and filtering

Conquest dicom server for image forwarding and caching

Conquest dicom server for image anonymization and deletion

Conquest dicom server for image splitting and merging

Conquest dicom server for image browsing and viewing

Conquest dicom server for image slide making and printing

Conquest dicom server for image selection and sending

Conquest dicom server for image header viewing and editing

Conquest dicom server for image quality improvement and enhancement

Conquest dicom server for image analysis and measurement

Conquest dicom server for image annotation and markup

Conquest dicom server for image sharing and collaboration

Conquest dicom server for image access control and authorization

Conquest dicom server for image metadata extraction and indexing

5 5 SECTION 1. INTRODUCTION The MicroPACS is a Windows or Linux (preliminary) based PACS system that has, at it s core, the UCDMC DICOM Network Transport libraries. This system has been combined with a complete user interface (Windows only), which also acts as installation program (written in Borland Delphi) to form the Conquest DICOM server. The Information Definition is designed to be field/run-time programmable. Below the DICOM interface is a database connectivity class that uses a stable built-in DBASEIII driver, talks to ODBC compatible data sources (Windows only), or MySql (Windows only - sofar). This combination permits a PACS system with the following features: Complete DICOM Interface. Including SCP s for run-time programmable storage IOD s, and SCP for DICOM Queries and Retrieves. Programmable SQL Database tables. This user-programmable feature allows the MicroPACS to be custom tailored to a particular Clinical/Research area. For instance, in a CR setting, the PACS system can be programmed to allow users to query on kvp and ma or in a CT setting, the PACS can be programmed to allow queries on slice-distance. The communication to the database is done via a built-in dbaseiii driver (default and advised for small archives of up to images), ODBC (Windows only), or native MySQL (Windows only, use version ). This allows a de-coupling of PACS and SQL technology. ODBC has been tested with (Windows only): Microsoft Access SQL server (most reliable and advised for serious use) Some users have reported successful operation using Interbase and Oracle. Versions and up have a small fix to work with MySql which seems suitable for up to images (see the DoubleBackSlashToDB setting in dicom.ini). Oracle requires simple manual editing of the DICOM.SQL file, where the names of fields rows and columns are changed to, e.g., qrows and qcolumns. See appendix 6 for tests of the various database options. Note: The built-in dbaseiii driver (Conquest addition) is not a full SQL server and poses limitations on query keys: only queries like key = exact match; key* = value starts with key; and *key* = value contains key, are supported, as well as date-range queries and multiple UID matching queries (since 1.4.7). Only common hierarchical queries are supported with fields that are listed in the single de-normalized table for the selected query level (see file DICOM.SQL). Regular queries passing PatientID, StudyUID, and/or SeriesUID will be (very) fast, even for huge archives. Other (image) queries in large archives (> images) may be very slow. Server startup time for huge archives may be long due to in-memory index creation (about 1 minute per images). During indexing the server is read-only and only shows indexed images. For Linux, the built-in driver is advised, however, a Postgres version is included.

6 6 (Conquest addition) Fast and safe (CRC checked) error free compression (>2x) of image data on disk. Do not use this option if you want to read the image files directly from disk yourselves using third party software. (Conquest addition) Easy installation of many servers on a single PC. Servers may run as service(s). (Conquest addition) A database browser and slice viewer (Windows only) integrated in the PACS system with options for: viewing the DICOM information in a slice, creating BMP files (ideal for slides), sending selected images, printing, and database fix tools such as changing patient IDs, and deleting and anonymizing studies and series. Also tools to merge or split series. Drag and drop to load DICOM or HL7 files or directories. (Conquest addition) A simple query/move user interface (Windows only) for diagnostic purposes, to improve your knowledge of DICOM, and to grab missing data from another server. (Conquest addition) Fully integrated functionality in one user interface. (Conquest addition) Simple print server (Windows) - to default printer. (Conquest addition) Log files, which are daily zipped (Windows only). We use the TZipMaster VCL by Chris Vleghert and Eric W. Engler. (Conquest addition) Correct display of JPEG and RLE compressed images in browser (Windows only). (Conquest addition) Flexible configuration of JPEG and NKI private compression with optional (de)compression of incoming, dropped, transmitted and archived files. The actual JPEG (de)compression is done using executables from the OFFIS DICOM toolkit (DCMTK version 3.5.3), developed by Kuratorium OFFIS e.v.. Since version 1.4.7, also a built-in decompression engine is included (Windows only) using the International JPEG group code, and JPEG compression had some fixes. (More conquest additions) Highly improved performance (e.g., using a read-ahead thread), and simple image forwarding/action capability. The archive is well suited as DICOM server for the DICOMWORKS viewer by Phillipe Puech. If the BDE is not installed, we use the MiTeC DBFTable component by MichaL MutL. For other data sources ADO is used (Windows only). Alternatively libmysql.dll may be used to access mysql directly (copy it from mysql server version to the dicom server directory). The server core of version up runs and compiles on Linux and has a preliminary WEB interface. Version up has preliminary DICOM Worklist query functionality with HL7 import and translation to DICOM worklist. Version up has preliminary virtual server functionality: queries and retrieves can be forwarded to up to 10 other servers. (see appendix 7).