Product: DICOM Connectivity Framework (DCF)


The DICOM Connectivity Framework (DCF) DICOM Toolkit software is an advanced, object-oriented collection of software components implementing the DICOM v3.0 protocol for OEM medical imaging systems. The DCF DICOM software SDK enables a medical imaging system — printer, scanner, archive device, workstation, etc., — to communicate with other devices over a network, using the DICOM protocol. Using the DCF DICOM Toolkit, an OEM can provide DICOM connectivity for their application or device with a minimum of effort. The DCF is designed to:

  • Provide a robust, portable, and high performance implementation of DICOM protocol services.

  • Provide a simple yet powerful API for communicating medical imaging information between the OEM's code and the DCF, such that detailed knowledge of DICOM is not required.

  • Provide an architecture that includes common service components that can be used as is, or can be easily customized by the OEM to fully integrate the DCF into their own software architecture.

The DCF SDK provides support for multiple languages and multiple platforms. The history of the DCF begins in the 1980s, and recounts how it was designed from the ground up to be an object-oriented implementation. It is the only DICOM solution on the market that provides programmers with a consistent API to C++, Java, and Microsoft COM/.Net (C#/C++.Net), providing support for Windows, Linux, Solaris, and other Unix platforms.

Print and read the DCF Product Brochure for more details.


Why Choose the DICOM Connectivity Framework?

The DCF's next-generation framework provides reliable, high-level components to help speed your DICOM interface development and reduce software costs on your platform of choice. Handling all the nuances of DICOM, the DCF allows your programmers to concentrate their efforts on your domain specific application rather than on learning DICOM.

Connectivity — The DCF provides trouble-free, reliable connectivity in diverse environments. It has been tested and proven in and against a wide variety of OEM devices from leading manufacturers.

Flexibility — We balance the opposing requirements of abstracting or encapsulating complexity, yet still provide access to lower level elements, allowing the OEM developer to choose the appropriate level at which to integrate DICOM services.

Reliability — Using our proprietary automated testing software, publicly available DICOM validation tools, memory leak/corruption test tools, and a large test suite, the DCF is rigorously tested.

Performance — The DCF was designed from the start to provide a high performance DICOM interface in a multi-threaded, OO design, capable of handling numerous associations in a single process.

Support — Web-based problem tracking assures that no issue or problem slips through the cracks. Customers receive prompt telephone and e-mail support, and have access to senior developers when appropriate.

Documentation — Most DCF documentation is generated directly from source code, so that low-level interface (API) and class documentation is always up-to-date and available. User, service, design, and higher-level architectural documentation is also provided.

Configurability — The DCF supports configuration on a per-association basis and dynamic reconfiguration of running applications.

Utilities — A rich set of utilities is provided, including web-based test and troubleshooting tools, test image generation, command-line driven clients and servers, data set dump, along with access to a large suite of validation test scripts.

Applications — Other DICOM applications and tools, based on DCF libraries, are available, including tools to support the following functions: message filter, protocol analyzer, message router, store splitter, migration controller and printer simulator.

Cost — The DCF development tools and run-time licenses are competitively priced. The ease of integration of the DCF components using modern OO programming practices provides significant reduction in time-to-market and software development costs, lowering the total cost of ownership and making the DCF the clear choice for new development efforts, as well as for retrofits of existing products.

Adaptability — Customers always have input into our development efforts. The modern design, combined with our rigorous testing processes, allows the DCF to provide robustness without the inflexibility frequently associated commercial software packages. We are extremely responsive to customer needs for new feature requests or bug fixes. Our component model provides for the ability, in many cases, to release a new version of a single component without affecting other components.

Key Features

  • Consistent API across languages and platforms.

  • Support for all SOP classes.

  • Component based framework facilitates rapid application development.

  • Excellent documentation, actively supported SDK, expert developer support.

[Request more info]

More Details

DCF Product Brochure
DCF Product Description

DCF Developers Guide (~2MB)
DCF DICOM Glossary

Pricing Info

Request Quote

Features

  • Advanced, object-oriented, component-based architecture
  • True multi-threaded implementation
  • An advanced component development environment
  • Pluggable common services
  • Multi-language SDK support for programming in Java, C++ and C#.
  • Support for multiple operating systems, most commonly Windows and Linux.
  • Component-based logging and debugging
  • Web-based service/diagnostic interface
  • Automated testing and validation tools
  • Multiple event processing models
  • Rapid application development
  • Per-association configuration management
  • Per-association data validation
  • Support for multiple languages, including C++, COM/.Net (C#/VB.Net/C++.Net) and Java.
  • Support for multiple platforms, including Linux, Windows and Solaris.
  • Support for DICOM modality worklists.
  • DICOM migration / archive migration / PACS migration.
  • Object-oriented, component-based design.
  • True multi-threaded implementation.
  • Comprehensive SOP class support.
  • Example SCU and SCP applications.
  • Optional DICOM DIMSE message validation.
  • Filters that allow for selective insertion, deletion, editing, re-tagging, or encrypting of DICOM attributes
  • Dynamic, per-association configuration and monitoring.
  • Web-based service/diagnostic interface.
  • Real-time monitoring and statistics reporting.
  • Component-based logging and debugging.

Products based on the DCF

DICOM Switchboard™

The DICOM Switchboard acts as an intermediate node between a DICOM client and server, allowing the user to route, monitor, and optionally alter DICOM DIMSE messages in real-time as they are passed between DICOM network devices. Designed primarily for network or PACS administrators, developers, field service engineers, migration specialists, or anyone responsible for integrating DICOM devices, it facilitates interconnection of otherwise incompatible DICOM devices or the movement of otherwise incompatible datasets. The user may configure, monitor, or control the application via any web browser that has network access to the device running the DICOM Switchboard.

[Learn More]



Laurel Bridge Migration
Controller

The Laurel Bridge Migration Controller (LBMC) provides automated facilities and services that allow migration of studies, series and SOP instance data from one DICOM 3.0 compatible physical archive to another. The controller supervises and schedules the transfer of studies, provides for error handling, plus provides verification to ensure that migrated studies are complete and accurate. Migration history is logged and performance statistics are gathered; various levels of reports are provided to summarize the status and progress of a migration. Additional cost options are available to provide site-specific mapping or alteration of DICOM elements that may be required by the migration of study data to a new archive.

[Learn More]

Mercury Archive Engine

The Mercury Archive Engine is a robust, fully functional DICOM store archive which serves as the foundation for a rich set of pluggable, interchangeable modules, allowing an OEM to very rapidly deploy an archive that can leverage their existing databases, persistence mechanisms, and look-and-feel. Switching between various pluggable modules is a snap: a single line in a configuration file is all that needs to be changed; no code modifications and recompilations are necessary. Even the Mercury Archive Engine itself is configurable: OEM’s can specify which DICOM tags should be stored in the database module and which DICOM tags should be available for Query/Retrieve searching by simply changing a configuration file.

[Learn More]



DICOM Store Gateway™

The DICOM Store Gateway (DSG) is an application that acts as a replication device for DICOM C-Store requests. Modalities sometimes want to store to multiple destinations (e.g., an archive and a viewing station) without the hassle of repeatedly resending the same job. With the DSG, this task is simple. Configure the DSG’s powerful mapping rules, specify the desired destinations, and then set up your modalities to send their Store requests directly to DSG. Mapping rules may be selected based on day of week and/or time of day to facilitate institutional scheduling requirements.

[Learn More]