Custom DICOM Archive Solutions
Fast track to an archive solution using this
DICOM PACS mini-archive.
Mercury™ is the core of a robust, fully functional mini-archive.
Customize Mercury to be a departmental archive,
store and forward cache, or a temporary archive. Its configurable database
indexes, retrieves and
manages the DICOM tags and workflow fields that you specify.
Use Mercury as the archive for any persistent datasets you have or receive. It is as easy as pointing Mercury to the location of the datasets and Mercury does the rest, automatically importing all of the DICOM datasets it finds at that location.
Mercury's makes it easy to customize and extend how it interacts with the Database Management System (DBMS), DICOM PACS and other persistent storage, while the administrative interfaces allowing you to leverage your existing infrastructure. Mercury will use its own, preconfigured database, or you can customize it to point to your own existing DBMS. Mercury even makes it easy to target multiple persistance locations. And for developers looking for customizable look and feel, Mercury's public APIs allow you to quickly deliver a look and feel that is consistent with your organization.
Mercury capitalizes on the world class
performance of the DICOM Connectivity
Framework (DCF). It takes full advantage of the rich set
of logging and configuration features available for
support and management of DICOM services.
Mercury must be customized for your needs and requires purchase of a DCF Toolkit plus additional
services. At the end of this process you have an archive solution that you deploy and maintain.
- Mercury core software code base
- DCF Toolkit (Purchase or Subscription)
- Development - System Requirements Specification
- Development - Customize Database, Workflow, and Admin User Interfaces
- Enterprise DCF Run-Time License(s) for each deployed instance
Selecting or switching Mercury between the various pluggable modules is simple: a configuration change is all that is needed and no code modifications or recompilations are necessary.
Mercury Features
- Modularity - Pluggable module architecture allows easy swapping of engine modules; predefined module implementations allow you to get started immediately.
- Configurable schema - Configurable database engine schema allows easy DICOM tag additions/deletions/modifications.
- Standard archive functionality - DICOM support for standard DICOM PACS and archive functions is built-in: Store SCP, Query/Retrieve SCP, Storage Commitment SCP, and Verification SCP/SCU.
- Non-image SOP classes - Full support for non-image sop classes, such as storage of Structured Reports, Radio Therapy, and GSPS objects.
- Transfer syntax handling - Configurable transfer syntax support allows datasets to be converted to and stored to a DICOM PACS or archive in any specified transfer syntax; optionally datasets can be stored in the transfer syntax that they were received, e.g. ILE, ELE, JPEG Lossless, JPEG 2000, etc.
- DICOM tag filtering - Powerful rule-based DICOM tag filtering (add/replace/modify) with optional change tracking in DICOM header.
- Chapter 10 support - Datasets can optionally be stored to a DICOM PACS in DICOM Chapter 10 media exchange format.
- Control of session settings - Configurable session settings allow fine-grained control of associations, AE titles, filters, and logging.
- Easy logging and monitoring - Logging or monitoring of all DICOM transactions in a user-friendly, human-readable format.
- Unlimited clients - No artificial limit on modalities or SCU clients.
- HIPAA logging - Includes HIPAA compliant logging for tracking access to the archive.
- High performance - Fully multi-threaded implementation assures high-performance of the engine.
- Event triggering - Supports triggers to allow scheduled events, including automatic or scheduled forwarding of datasets.
Mercury provides OEMs or medical service providers the opportunity to rapidly implement their own custom archive solution or DICOM PACS backend that supports their business model and exhibits their own look-and-feel. The responsibility for managing compliance with the DICOM standard is off-loaded to the archive engine, greatly simplifying on-going support issues.
Related Information
Mercury Product Description
Request product infoDetails
- Robust, fully functional core platform for building a custom DICOM PACS or Store archive.
- Suitable for building a departmental archive, store and forward cache, or simply a temporary archive.
- Can be the basis for a custom archive solution for any persistent datasets you have or receive.
- Facilitates importation of DICOM datasets from a variety of sources.
- Supports DICOM Query/Retrieve (Q/R) functionality.
- Provides fully configurable DICOM PACS features.
- Custom solutions available, requires DCF Toolkit.
Testimonials
"With no trouble at all, Switchboard handled a throughput of over 29,000 daily transactions, peaking at approximately 1,600 transactions per hour."
-Large Teleradiology Customer
"The Compass™ DICOM router is working great. We are extracting and analyzing patient exam data from select DICOM tags for research purposes."
-Leading University Medical Center Research Department
"The DCF software just works."
-Rich Edwards, Lead Software Engineer, Codonics, Inc.