4. Implementation Model

The core component of dcm4che DICOM Archive 5 is a Java Enterprise Application deployed in WildFly AS, which provides DICOM services over the DICOM Upper Layer protocol (DUL) and HTTP, HL7 v2 services over the Minimal Lower Layer Protocol (MLLP), various proprietary RESTful services and a Web UI accessable by HTML 5 compliant web browsers.

Conceptually the HL7 network services may be modeled as the following separate HL7 applications, though they may share one HL7 Application name, or one HL7 Application may have multiple instances identified by different HL7 Application names, with different configuration.

  • Patient Management Service, which processes ADT messages received from remote HL7 Applications, updating the patient information of archived DICOM objects, and send ADT messages to remote HL7 Applications on patient information changes initiated via the Web UI or proprietary RESTful services of dcm4che DICOM Archive 5.

  • Procedure Management Service, which processes HL7 order messages from remote HL7 Applications, updating order information in the provided DICOM Modality Worklist and already archived DICOM objects, and send HL7 order messages to remote HL7 Applications on procedure status updates.

  • Observation Reporting Management Service, which converts HL7 ORU messages received from remote HL7 Applications to DICOM Text SR objects, to make them accessible via the DICOM query/retrieve services.

  • HL7 Forward Service, which forwards HL7 message received from one remote HL7 application to another remote HL7 application according configurable rules.

_images/application-data-flow-diagram.svg

Fig. 4.1 Application Data Flow Diagram