Page tree
Skip to end of metadata
Go to start of metadata

The Source Code of dcm4chee-2.x is separated into 10 modules:

dcm4jboss-all
|-- dcm4che14
|-- dcm4jboss-arr
|-- dcm4jboss-build
|-- dcm4jboss-cdw
|-- dcm4jboss-ejb
|-- dcm4jboss-hl7
|-- dcm4jboss-sar
|-- dcm4jboss-wado
|-- dcm4jboss-web
`-- dcm4jboss-xds

dcm4che14

contains v1.4.x of the DICOM library, on which all other modules depends:

dcm4jboss-build

contains the master Ant build script, for Building dcm4chee, but does not contain itself any (Java) source code.

dcm4jboss-arr

contains the Audit Record Repository. It's a self-contained JBoss application, which has no dependencies - beside on the DICOM library - to other modules. It may be also used as standalone application - without the DICOM archive components. Even if the archive components are deployed in the same JBoss instance as the Audit Record Repository, they will use UDP messages to log audit records in the Audit Record Repository.

dcm4jboss-cdw

contains the Media Creation Server, responsible for the composition of DICOM File-Sets, creation of the ISO image and burning them on CD or DVD media. It's a self-contained JBoss application, which has no dependencies - beside on the DICOM library - to other modules. It may be also used as standalone application - without the DICOM archive components. Even if the archive components are deployed in the same JBoss instance as the Audit Record Repository, they will use DICOM Storage and DICOM Media Creation Management Service to initiate the Media Creation.

dcm4jboss-ejb

contains all Entity and Stateless Session EJBs and Data Access Objects, encapsulating any database access from archive components.

dcm4jboss-hl7

contains HL7 specific MBean Services for processing received HL7 messages for Procedure Scheduled (ORM^O01), Patient Update (ADT) and Reports (ORU^R01), but also for emitting HL7 messages, in particular forwarding received messages to other HL7 receiver. Processing of HL7 is widely defined by XSLT Stylesheets, which allows adaption to HL7 messages form various RIS systems without modfications on the Java sources. dcm4jboss-hl7 make use of general MBean Services provided by dcm4jboss-sar.

dcm4jboss-sar

contains all DICOM specific MBean Service, but also common MBean Services used by dcm4jboss-hl7, dcm4jboss-wado and dcm4jboss-web.

dcm4jboss-wado

contains an implementation of DICOM's Web Access to DICOM Persistent Objects (WADO) and IHE's Retrieve Information for Display (RID) and Retrieve ECG for Display (ECG).

dcm4jboss-web

contains the Web Application for the Archive Administration. It's build using the Web Application Framework Maverick, with XSLT as view technology. Therefore page layout is mainly specified by XSLT stylesheets, which can be customized, without need for modfications on the Java sources.

dcm4jboss-xds

contains an implementation of an IHE XDS repository. Makes internally use of the RID service for returning a requested document.

  • No labels

1 Comment

  1. Unknown User (mmesser314)

    Here are a few class diagrams, courtesy of Harris Corp and Johns Hopkins .These are from dcm4chee 2.17.1, which includes the dcm4che14 toolkit.

    The only reason you would be interested in dcm4che14 is if you are working with dcm4chee source code. If you are using the dcm4chee toolkit for your own projects, you will very likely be using dcm4che2 instead.

    There are 3 formats. The vsd files are the original, editable, MS Visio files. The png and pdf files are viewable files for people without Visio.

    dcm4che14.vsd

    dcm4che14.pdf, dcm4che14_1.png, dcm4che14_2.png, dcm4che14_3.png

    qrscp.vsd

    qrscp.pdf, qrscp.png