<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
    <front>
        <journal-meta>
            <journal-id journal-id-type="publisher-id">JMIR</journal-id>
            <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
            <journal-title>Journal of Medical Internet Research</journal-title>
            <issn pub-type="epub">1438-8871</issn>
            <publisher>
                <publisher-name>Gunther Eysenbach</publisher-name>
                <publisher-loc>Centre for Global eHealth Innovation, Toronto, Canada</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="publisher-id">v1i2e8</article-id>
            <article-id pub-id-type="pmid">11720917</article-id>
            <article-id pub-id-type="medline">21577982</article-id>
            <article-id pub-id-type="doi">10.2196/jmir.1.2.e8</article-id>
            <article-categories>
                <subj-group subj-group-type="article-type">
                    <subject>Original Paper</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Borderless Teleradiology with CHILI</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes" id="contrib1" xlink:type="simple">
                    <name name-style="western">
                        <surname>Engelmann</surname>
                        <given-names>Uwe</given-names>
                    </name>
                    <address>
                        <institution xlink:type="simple">Deutsches Krebsforschungszentrum</institution>
                        <institution>Abteilung Mediziniscdhe und Biologische Informatik</institution>
                        <addr-line>ImNeuenheimer Feld 280</addr-line>
                        <addr-line>D-69120 Heidelberg</addr-line>
                        <country>Germany</country>
                        <email>U.Engelmann@DKFZ-Heidelberg.de</email>
                    </address>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib2" xlink:type="simple">
                    <name name-style="western">
                        <surname>Schroeter</surname>
                        <given-names>A</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib3" xlink:type="simple">
                    <name name-style="western">
                        <surname>Schwab</surname>
                        <given-names>M</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff2">2</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib4" xlink:type="simple">
                    <name name-style="western">
                        <surname>Eisenmann</surname>
                        <given-names>U</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib5" xlink:type="simple">
                    <name name-style="western">
                        <surname>Vetter</surname>
                        <given-names>M</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib6" xlink:type="simple">
                    <name name-style="western">
                        <surname>Lorenz</surname>
                        <given-names>K</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib7" xlink:type="simple">
                    <name name-style="western">
                        <surname>Quiles</surname>
                        <given-names>J</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff3">3</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib8" xlink:type="simple">
                    <name name-style="western">
                        <surname>Wolf</surname>
                        <given-names>I</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib9" xlink:type="simple">
                    <name name-style="western">
                        <surname>Evers</surname>
                        <given-names>H</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
                <contrib contrib-type="author" id="contrib10" xlink:type="simple">
                    <name name-style="western">
                        <surname>Meinzer</surname>
                        <given-names>HP</given-names>
                    </name>
                    <xref ref-type="aff" rid="aff1">1</xref>
                </contrib>
             </contrib-group>
            <contrib-group>
                  <contrib contrib-type="reviewer" xlink:type="simple">
                    <name name-style="western">
                        <surname>Rodrigues</surname>
                        <given-names>Roberto J</given-names>
                    </name>
                </contrib>
                <contrib contrib-type="reviewer" xlink:type="simple">
                    <name name-style="western">
                        <surname>Keevil</surname>
                        <given-names>Stephen</given-names>
                    </name>
                </contrib>
            </contrib-group>
            <aff id="aff1" rid="aff1"><sup>1</sup>
                <institution xlink:type="simple">Deutsches Krebsforschungszentrum</institution>
                <addr-line>Abteilung Mediziniscdhe und Biologische Informatik</addr-line>
                <addr-line>ImNeuenheimer Feld 280</addr-line>
                <addr-line>D-69120</addr-line>
                <addr-line>Heidelberg</addr-line>
                <country>Germany</country>
            </aff>
            <aff id="aff2" rid="aff2"><sup>2</sup>
                <institution xlink:type="simple">Steinbeis-Transferzentrum Medizinische Informatik</institution>
                <addr-line>Heidelberg</addr-line>
                <country>Germany</country>
            </aff>
            <aff id="aff3" rid="aff3"><sup>3</sup>
                <institution xlink:type="simple">University of Santiago de Compostela</institution>
                <addr-line>Department of Radiology</addr-line>
                <country>Spain</country>
            </aff>
            <pub-date pub-type="collection">
                <season>Oct-Dec</season>
                <year>1999</year>
            </pub-date>
            <pub-date pub-type="epub">
                <day>13</day>
                <month>12</month>
                <year>1999</year>
            </pub-date>
            <volume>1</volume>
            <issue>2</issue>
            <elocation-id>e8</elocation-id>
            <history>
                <date date-type="received">
                    <day>30</day>
                    <month>7</month>
                    <year>1999</year>
                </date>
                <date date-type="rev-request">
                    <day>4</day>
                    <month>10</month>
                    <year>1999</year>
                </date>
                <date date-type="rev-recd">
                    <day>23</day>
                    <month>11</month>
                    <year>1999</year>
                </date>
                <date date-type="accepted">
                    <day>21</day>
                    <month>11</month>
                    <year>1999</year>
                </date>
            </history>
            <copyright-statement>&#xA9; Uwe Engelmann, A Schroeter, M Schwab, U Eisenmann, M Vetter, K Lorenz, J Quiles, I Wolf, H Evers, HP Meinzer.  Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 13.12.1999.  Except where otherwise noted, articles published in the Journal of Medical Internet Research are distributed under the terms of the Creative Commons Attribution License (http://www.creativecommons.org/licenses/by/2.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited, including full bibliographic	details and the URL (see "please cite as" above), and this statement is included.</copyright-statement>
            <copyright-year>1999</copyright-year>
            <self-uri xlink:href="http://www.jmir.org/1999/2/e8/" xlink:type="simple"/>
            <abstract>
                <p>Teleradiology is one of the most evolved areas of telemedicine, but one of the basic problems which remains unsolved concerns system compatibility. The DICOM (Digital Imaging and Communications in Medicine) standard is a prerequisite, but it is not sufficient in all aspects. Examples of other currently open issues are security and cooperative work in synchronous teleconferences. Users without a DICOM radiological workstation would benefit from the ability to join a teleradiology network without any special tools. Drawbacks of many teleradiology systems are that they are monolithic in their software design and cannot be adapted to the actual user's environment. Existing radiological systems currently cannot be extended with additional software components. Consequently, every new application usually needs a new workstation with a different look and feel, which must be connected and integrated into the existing infrastructure.</p>
                <p>This paper introduces the second generation teleradiology system CHILI. The system has been designed to match both the teleradiology requirements of the American College of Radiology (ACR), and the functionality and usability needs of the users. The experiences of software developers and teleradiology users who participated in the first years of the clinical use of CHILI's predecessor MEDICUS have been integrated into a new design. The system has been designed as a component-based architecture. The most powerful communication protocol for data exchange and teleconferencing is the CHILI protocol, which includes a strong data security concept. The system offers, in addition to its own secure protocol, several different communication methods: DICOM, classic e-mail, Remote Copy functions (RCP), File Transfer Protocol (FTP), the internet protocols HTTP (HyperText Transfer Protocol) and HTTPS (HyperText Transfer Protocol Secure),and CD-ROMs for off-line communication. These transfer methods allow the user to send images to nearly anyone with a computer and a network. The drawbacks of the non-CHILI protocols are that teleconferences are not possible, and that the user must take reasonable precautions for data privacy and security.</p>
                <p>The CHILI PlugIn mechanism enables the users or third parties to extend the system capabilities by adding powerful image postprocessing functions or interfaces to other information systems. Suitable PlugIns can be either existing programs, or dedicated applications programmed with interfaces to the CHILI components. The developer may freely choose programming languages and interface toolkits.</p>
                <p>The CHILI architecture is a powerful and flexible environment for Picture Archiving and Communications Systems (PACS)and teleradiology. More than 40 systems are currently running in clinical routine in Germany. More than 300,000 images have been distributed among the communication partners in the last two years. Feedback and suggestions from the users influenced the system architecture by a great extent. The proposed and implemented system has been optimized to be as platform independent, open, and secure as possible.</p>
            </abstract>
            <kwd-group>
                <kwd>Teleradiology</kwd>
                <kwd>Telemedicine</kwd>
                <kwd>Remote Consultation</kwd>
                <kwd>Diagnostic Imaging</kwd>
                <kwd>Computer-Assisted Image Interpretation</kwd>
                <kwd>PACS</kwd>
                <kwd>Middleware</kwd>
                <kwd>TLS</kwd>
                <kwd>Security</kwd>
                <kwd>Plugin</kwd>
                <kwd>Visualization</kwd>
            </kwd-group>
        </article-meta>
    </front>
    <body>
        <sec sec-type="intro">
            <title>Introduction</title>
            <p>The American College of Radiology (ACR) defined teleradiology in <italic>ACR Standard for Teleradiology</italic> [<xref ref-type="bibr" rid="ref1">1</xref>] as the following:</p>
            <disp-quote>
                <p>Teleradiology is the electronic transmission of radiological images from one location to another for the purposes of interpretation and/or consultation. Teleradiology may allow even more timely interpretation of radiological images and give greater access to secondary consultations and to improved continuing education. Users in different locations may simultaneously view images. Appropriately utilized, teleradiology can improve access to quality radiological interpretations and thus significantly improve patient care.</p>
            </disp-quote>
            <p>In this paper we want to introduce the current state of our development in teleradiology. CHILI (tm) is a general purpose radiology workstation with additional functions for teleradiology. The task of the system is the transmission of radiological images to different locations for interpretation and consultation. The transmitted images can be simultaneously viewed at different locations and examined cooperatively. The development of the system was based on experience with the successful teleradiology project MEDICUS-2, which was a dedicated teleradiology system [<xref ref-type="bibr" rid="ref2">2</xref>]. The second generation teleradiology system CHILI has been designed to match the teleradiology requirements of the ACR and the needs of MEDICUS users [<xref ref-type="bibr" rid="ref3">3</xref>]. The experiences of software developers and teleradiology users who participated in the first years of clinical use have been integrated into the architecture [<xref ref-type="bibr" rid="ref4">4,5</xref>]. This paper describes the general system design and application areas.</p>
        </sec>
        <sec sec-type="methods">
            <title>Methods</title>
            <sec>
                <title>Principal Functionality</title>
                <p>The principal functions of the system are the following:</p>
                <list list-type="bullet">
                    <list-item>
                        <p>The system receives images from different sources, such as imaging modalities, radiological viewing stations, digital archives, video cameras, etc., and stores them in a local database management system.</p>
                    </list-item>
                    <list-item>
                        <p>The image viewing functionality allows the user to display and analyze the images in several ways (e.g. level/windowing, measurements, ROI analysis).</p>
                    </list-item>
                    <list-item>
                        <p>Images can be transmitted to other sites with a number of (vendor-independent) protocols. Security measures are taken into account. The network protocol is TCP/IP and independent of the physical network layer. Different protocols are available.</p>
                    </list-item>
                    <list-item>
                        <p>Images can be compressed using wavelet-based algorithms.</p>
                    </list-item>
                    <list-item>
                        <p>Users at remote locations can work on the images simultaneously in teleconferences with synchronized images, functions, and mouse pointers.</p>
                    </list-item>
                    <list-item>
                        <p>Exporting images to hard disk, floppy, or CD-ROM is possible, and hardcopies of the images can be printed on inexpensive, ordinary PostScript printers. Also, the DICOM protocol can be used to perform printing management in combination with DICOM compliant print servers.</p>
                    </list-item>
                </list>
            </sec>
            <sec>
                <title>Component Architecture</title>
                <p>The software architecture of CHILI is based on the results of the European Project HELIOS, in which concepts for distributed, object-oriented software systems were developed [<xref ref-type="bibr" rid="ref6">6</xref>]. The core of the HELIOS software engineering environment is the HELIOS Unification Bus (HUB), a middleware technology. Independent and distributed software components communicate by means of the HUB. The middleware of CHILI is based on the same concepts as HELIOS, but has been redesigned in several aspects to match the specific requirements of an image communication environment that has parts which are linked by low bandwidth networks and are not permanently reachable. Security enhancements have been added to fulfill the legal requirements for data security and privacy. The middleware supports the security standards SSL/TLS (Secure Sockets Layer/Transport Layer Security) for authentication and secure communication [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
                <p>
                    <xref ref-type="fig" rid="figure1">Figure 1</xref> shows the main components of the architecture:</p>
                <fig id="figure1" position="float">
                    <label>Figure 1</label>
                    <caption>
                        <p>shows the main components of the architecture</p>
                    </caption>
                    <graphic xlink:href="jmir_v1i2e8_fig1.gif" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
                </fig>
                <list list-type="bullet">
                    <list-item>
                        <p>The <italic>Viewer</italic> is the graphical interface for the user. Nearly all functions are controlled by the viewer, including viewing images, transmission of images, teleconferences, and system configuration.</p>
                    </list-item>
                    <list-item>
                        <p>The <italic>Message System</italic> is used as the communication channel (middleware) between the software components.</p>
                    </list-item>
                    <list-item>
                        <p>The <italic>Database Service</italic> component stores the data for the system and delivers it to other software components. It provides an abstract interface which hides the specific SQL database management system (DBMS). Thus, it is independent of a specific DBMS implementation. DICOM (Digital Imaging and Communications in Medicine) archives can be accessed through this interface as well. This is a great advantage both for users and programmers.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <italic>Send and Receive Services</italic> are used to exchange data between the CHILI systems via the CHILI protocol. Other protocols are available as well and allow data exchange with non-CHILI systems (see Cross-Platform Communication). An optional wavelet module (MT-Wice, MeVis Technology, Bremen, Germany) can be employed to compress the image by a factor of 10-100 to speed up the transmission process.</p>
                    </list-item>
                    <list-item>
                        <p>The <italic>Import and Export Services</italic> are needed to get the data into the system and to export data to the local disk or an archive medium. DICOM is the most relevant image format for this purpose. The older ACR/NEMA 1.0 and 2.0 standards; industry standards; and public domain formats such as GIF, TIFF, PostScript, PPM, JPEG, M-JPEG are supported as well. Vendor specific formats, like SOMATOM, MAGNETOM, and GENESIS, can also be processed.</p>
                    </list-item>
                    <list-item>
                        <p>The <italic>DICOM Server</italic> receives image data via the DICOM protocol as a Storage Class Provider from other DICOM devices, such as CT or MRI scanners.</p>
                    </list-item>
                    <list-item>
                        <p>The <italic>Query Service</italic> is based on the DICOM protocol to retrieve image data from Picture Archiving and Communications Systems (PACS) archive systems.</p>
                    </list-item>
                    <list-item>
                        <p>The <italic>Multiplexer</italic> manages connection requests between the different components and starts modules when necessary.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <italic>The World Wide Web (WWW) Server</italic> is the gateway between the CHILI database and internet technology (see WWW: Independent of Hardware and Operating System).</p>
                    </list-item>
                </list>
                <p>This overall design allows a very flexible configuration of the system which can easily be adapted to any specific environment. The different services and modules can be combined in different ways to provide custom solutions. Examples of typical configurations (in clinical use) are:</p>
                <list list-type="bullet">
                    <list-item>
                        <p>
                            <italic>CHILI Classic</italic>, with full functionality ranging from DICOM image database to printing and teleconferencing.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <italic>CHILI Video</italic> is a package without connections to modalities or databases but with on-line communications using digital images which are grabbed from a video source.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <italic>Send and Receive systems</italic> can be used to perform one-way communications setups.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <italic>Client/Server</italic> configurations use a central PACS archive or CHILI database and allow the transmission of data to remote sites as well as teleconferences. The server can either be a CHILI Classic (with or without viewer) or a database server (SQL and/or DICOM). The clients can either be viewers or complete systems which share a central database. All clients have the complete functionality of a CHILI Classic configuration in connection with a server. Other dedicated systems can be realized depending on the actual user needs.</p>
                    </list-item>
                </list>
            </sec>
            <sec>
                <title>Security Concept</title>
                <p>The most powerful communication protocol for data exchange (and the only protocol that allows teleconferencing) is the CHILI protocol, which includes a strong data security concept [<xref ref-type="bibr" rid="ref8">8</xref>]. This includes all measures which are necessary to comply with German and European requirements and laws. As a result of the data security concept, it is possible to restrict the rights of the receiver on the image data. The following restrictions are possible:</p>
                <list list-type="order">
                    <list-item>
                        <p>Only viewable in a teleconference with the sender.</p>
                    </list-item>
                    <list-item>
                        <p>Not exportable.</p>
                    </list-item>
                    <list-item>
                        <p>Not printable.</p>
                    </list-item>
                    <list-item>
                        <p>Automatic removal after the teleconference.</p>
                    </list-item>
                </list>
                <p>All data packets to be transmitted are encrypted with the PGP (Pretty Good Privacy) public key encryption system [<xref ref-type="bibr" rid="ref9">9</xref>]. The public key of the receiver is used for the encryption. A checksum of the data is calculated and signed with the digital signature of the sender. This protects data integrity, and allows for authentication of the sender and privacy. Furthermore, all local data are encrypted with a symmetric key encryption method. Transmitted and received images are logged in special log files which are protected with a checksum.</p>
                <p>The communication between the CHILI components via the middleware can optionally be protected using the TLS standard [<xref ref-type="bibr" rid="ref7">7</xref>]. This ensures authentication and privacy.</p>
            </sec>
            <sec>
                <title>Cross-Platform Communication</title>
                <p>It cannot be expected that all communication partners have the same teleradiology system. Thus, CHILI offers additional communication methods (<xref ref-type="fig" rid="figure2">Figure 2</xref>):</p>
                <list list-type="bullet">
                    <list-item>
                        <p>The <italic>DICOM protocol</italic> allows the exchange of images with all other DICOM compliant systems. The following service classes are supported: storage class user, storage class provider, and print management classes for both user and provider. Find and Move are also supported.</p>
                    </list-item>
                    <list-item>
                        <p>Classic <italic>e-mail</italic>(SMTP protocol) can be used to send images encoded in either DICOM or JPEG formats.</p>
                    </list-item>
                    <list-item>
                        <p>
                            <italic>File Transfer Protocol</italic>(FTP) and <italic>Remote Copy functions</italic>(RCP) are available to transmit image data to other hosts where the data is processed with other software tools.</p>
                    </list-item>
                    <list-item>
                        <p>Data can be transferred to <italic>portable media</italic>, such as CD-ROMs (DICOMDIR). The CD-ROMS are suitable for archiving purposes as well. The database stores a reference to the CD-ROM where the data are actually stored. The media can be handled manually or automatically with a jukebox. Non-archive CD-ROMs can be given to other medical institutions, referring physicians, or even the patient. The standardized DICOMDIR format ensures that the data can be viewed with different programs which are compliant to the standard.</p>
                    </list-item>
                    <list-item>
                        <p>Images or image sequences can be acquired from <italic>Video</italic> sources, such as video camera, video recorder, and ultrasound devices. The system converts the analog video signal into DICOM compliant image files. Demographic data is acquired as well to facilitate data-handling in the patient-oriented database and long-term PACS archives.</p>
                    </list-item>
                    <list-item>
                        <p>Data from document or film scanners can be imported in different formats and converted to the DICOM standard for further processing.</p>
                    </list-item>
                    <list-item>
                        <p>The WWW server (see Component Architecture) translates the internal SQL or DICOM representation of the data to the HTTP protocol. Thus, the data can be accessed with any web browser in the network. The advantage of this solution is that the clients do not need any special hardware or software. Authenticity of users and privacy are ensured by different measures, such as user accounts, passwords, restricted group access, and the secure protocol TLS.</p>
                    </list-item>
                </list>
                <p>The user of the CHILI system is not confronted with the various protocols directly. The definition of the protocol to be used is configured for each communication partner. It has to be defined if the partner is connected via LAN, Internet, or ISDN lines. The ISDN zone is defined as well to be able to estimate the transfer costs depending of the transmission time, duration, distance, and compression rates.</p>
                <fig id="figure2" position="float">
                    <label>Figure 2</label>
                    <caption>
                        <p>CHILI offers additional communication methods</p>
                    </caption>
                    <graphic xlink:href="jmir_v1i2e8_fig2.gif" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
                </fig>
                <p>The broad set of transfer methods enables the CHILI user to send images to nearly anyone with access to a computer and a network. The limitations are that teleconferences are possible with the CHILI protocol only, and that the user has to take reasonable precautions for data privacy and security when he does not use the secure CHILI protocol.</p>
            </sec>
            <sec>
                <title>Explicit Transmissionand Auto-routing</title>
                <p>Image data can be transmitted manually by the user or automatically by the auto-routing component which is activated by the import service. Certain data fields of the image header are used to determine if and to whom the incoming data should be transmitted automatically.</p>
            </sec>
            <sec>
                <title>Functional Openness</title>
                <p>A typical problem in radiology is that nearly every application needs its own computer. Console computers are necessary to operate the imaging modalities. Viewing stations are used for reporting or further analysis of the image data. Radiology Information System (RIS) terminals are used to manage and organize the patient information flow. Additional Personal Computers (PCs) are used for word processing (e.g. reports, publications). New computers for teleradiology are now entering the radiology department.</p>
                <p>Developers of new medical image analysis applications face the problem that the current computer applications (e.g. viewing stations) are not open enough. Every developer must consider the connection to the modality or viewing station, file formats, data storage of files on the disk or in a data base system, and the display of 12-bit images on 8-bit screens. For the radiologist, the development a new method means the invention of many wheels a second or third time before the real problems can be addressed. Most of the manufacturers of the existing viewing stations do not allow the installation of additional software. Usually the customers do not get the root password of the systems. An additional computer with different user interfaces and additional interfaces to the rest of the world has to be introduced, therefore, to get the new functionality to the users.</p>
                <p>The result of the depicted problem is that it takes a lot of effort for developers to implement and introduce new methods; this is most of the time very costly for the end user. Therefore, we designed the CHILI PlugIn mechanism [<xref ref-type="bibr" rid="ref10">10</xref>]. Users can extend the system by adding powerful image postprocessing functions [<xref ref-type="bibr" rid="ref11">11</xref>] or interfaces to other information systems. PlugIns can be either existing applications or new modules with interfaces to the existing CHILI components (<xref ref-type="fig" rid="figure3">Figure 3</xref>).</p>
                <p>The PlugIn developers' Application Programming Interface (API) includes interfaces to all software components and the message system [<xref ref-type="bibr" rid="ref10">10</xref>]. The developer is free to choose programming languages and interface toolkits (e.g. C, C++, Tcl/Tk). The Java Virtual Machine [<xref ref-type="bibr" rid="ref12">12</xref>] is a PlugIn itself; thus, Java programs can easily be integrated to communicate with CHILI.</p>
                <fig id="figure3" position="float">
                    <label>Figure 3</label>
                    <caption>
                        <p>PlugIns can be either existing applications or new modules with interfaces to the existing CHILI components</p>
                    </caption>
                    <graphic xlink:href="jmir_v1i2e8_fig3.gif" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
                </fig>
                <p>Several existing applications have successfully been integrated into CHILI as useful additions to the main system. One example is a terminal window (xterm) which is connected to a RADOS-M RIS. This enables the user to see both the image data and RIS information on the same screen (<xref ref-type="fig" rid="figure4">Figure 4</xref>). Another example of such a simple PlugIn is a WWW browser, which allows the user to explore, for example, reference cases on the intra- or internet. The user manual of the system is integrated with the same mechanism.</p>
                <fig id="figure4" position="float">
                    <label>Figure 4</label>
                    <caption>
                        <p>This enables the user to see both the image data and RIS information on the same screen</p>
                    </caption>
                    <graphic xlink:href="jmir_v1i2e8_fig4.gif" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
                </fig>
                <p>Examples for ongoing PlugIn development projects are a general purpose 3D volume segmentation and visualization project [<xref ref-type="bibr" rid="ref13">13</xref>] (<xref ref-type="fig" rid="figure5">Figure 5</xref>), a tool for the planning of liver surgeries [<xref ref-type="bibr" rid="ref14">14</xref>], and a 3D ultrasound doppler project [<xref ref-type="bibr" rid="ref15">15</xref>].</p>
                <fig id="figure5" position="float">
                    <label>Figure 5</label>
                    <caption>
                        <p>Examples for ongoing PlugIn development projects are a general purpose 3D volume segmentation and visualization project</p>
                    </caption>
                    <graphic xlink:href="jmir_v1i2e8_fig5.gif" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
                </fig>
            </sec>
            <sec>
                <title>Hardware and Operating Systems</title>
                <sec>
                    <title>Unix-Workstations and Personal Computers with Linux</title>
                    <p>CHILI has been developed under the UNIX operating system in ANSI C. The most important reasons were portability, reliability, and data security. The realized system is not dependent on vendor-specific UNIX dialects or hardware features. It is available on workstations running IRIX, Solaris, Ultrix, and Linux. The most economically priced and powerful system is a PC running the Linux operating system [<xref ref-type="bibr" rid="ref16">16</xref>].</p>
                </sec>
                <sec>
                    <title>Personal Computers with Microsoft Windows</title>
                    <p>CHILI clients are running under Microsoft Windows under the eXceed system (Hummingbird). The latter allows the original code to run and provides a X Window-based user interface. It offers the same functionality as the Unix client, including teleconferences.</p>
                    <p>A complete CHILI Classic configuration has been realized using Interix (formerly known as OpenNT, by Softway Systems, Inc.) on Windows NT systems, with all components for data exchange and teleconferencing operational.</p>
                </sec>
                <sec>
                    <title>WWW: Independent of Hardware and Operating System</title>
                    <p>The Web Interface is the most hardware and operating system independent solution. The CHILI WWW Server is a frontend to the CHILI database. Users can access it with any web browser. The user interface is nearly the same as the standard CHILI Viewer. Data can be retrieved from CHILI databases, or DICOM archives which are accessed through the CHILI database interface. The images can be displayed with 8-bit screens in GIF or JPEG format, and DICOM encoded for the Java/DICOM viewer. The compression rate of the JPEG images can be defined in different quality steps.</p>
                </sec>
            </sec>
            <sec>
                <title>From Teleradiology to PACS</title>
                <p>Over time, the system has become a PACS component which can be used as an interface to DICOM compliant archives, and also for DICOM printing and reporting. Images can be distributed in-house, and light-weight clients running on PCs can be used to view or process the images in teleconferences. Clients for MS Windows are available, in addition to web-based interfaces which can be accessed from any hardware or operating system with a web browser. The CHILI database can be configured to act as a cache for the PACS archive (<xref ref-type="fig" rid="figure6">Figure 6</xref>). A storage hierarchy can be configured to reduce the traffic on the archive and to optimize image transfers on the network. The user is released from the load of knowing where the data are actually stored.</p>
                <p>The CHILI Viewer with the multi-head option and diagnostic monitors is suited for image reporting. Filmless radiology can be realized with this technology.</p>
                <fig id="figure6" position="float">
                    <label>Figure 6</label>
                    <caption>
                        <p>The CHILI database can be configured to act as a cache for the PACS archive</p>
                    </caption>
                    <graphic xlink:href="jmir_v1i2e8_fig6.gif" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
                </fig>
            </sec>
        </sec>
        <sec sec-type="results">
            <title>Results</title>
            <p>The CHILI project is a cooperation between the German Cancer Research Center and a technology transfer company Steinbeis-Transferzentrum Medizinische Informatik (STZ-MI), both located in Heidelberg, Germany. The STZ-MI is an outgrowth of the cancer center where scientific results are converted into products for market. Concepts and research are done by the research group at the cancer center, and the technology transfer company implements the research into products and brings the results to the market. Marketing and sales is also done by OEM partners, system integrators, and consulting firms.</p>
            <p>More than 40 systems are running in daily routine in private practices, small hospitals, university clinics, and research institutes. The system is in use in research projects, in medical image analysis, and even surgery planning systems. It is the basic platform of the German research project Sonderforschungsbereich 414 <italic>Information Technology in Medicine: Computer and Sensor Supported Surgery</italic> [<xref ref-type="bibr" rid="ref17">17</xref>].</p>
            <fig id="figure7" position="float">
                <label>Figure 7</label>
                <caption>
                    <p>shows the current network (July 1999)</p>
                </caption>
                <graphic xlink:href="jmir_v1i2e8_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
            </fig>
            <p>
                <xref ref-type="fig" rid="figure7">Figure 7</xref> shows the current network (July 1999). More than 300,000 images have been processed by the network, and the program has been invoked nearly 20,000 times in the last 3 years. More than twenty modalities from different vendors are connected via DICOM or proprietary solutions [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
            <p>The system is in use in different application scenarios, such as image delivery to referring physicians, interdisciplinary discussions, remote reporting, de-centralized radiology departments, resource sharing, data transfer for radiotherapy planning, scientific cooperation, quality control, and research.</p>
        </sec>
        <sec sec-type="discussion">
            <title>Discussion</title>
            <sec>
                <title>Comparison with Work of Others</title>
                <p>An overview about the state of teleradiology in the United States has been published by Grigsby in 1994 [<xref ref-type="bibr" rid="ref19">19</xref>]. Regular telephone lines and modems were normally used at that time in the US. Most of the systems developed were based on PCs using video cameras with PC frame grabber cards or scanners to capture the images, e.g [<xref ref-type="bibr" rid="ref19">19</xref>,<xref ref-type="bibr" rid="ref20">20</xref>].. Oft-discussed topics in the field of teleradiology were spatial resolution and grayvalue depth of the video images or scanners. However, these problems do not exist when the original digital images are processed; the receiver gets the images in original quality. Such advanced teleradiology systems based on digital data and digital telephone lines (ISDN) have been developed and used in Europe since 1994, e.g [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref24">24</xref>]..</p>
                <p>A prototype of a dedicated teleradiology system has been developed by Gomez and co-workers in a research project funded by the EU AIM Programme [<xref ref-type="bibr" rid="ref21">21</xref>]. The system has been evaluated in two hospitals in Spain. One imaging modality was connected to one of two teleradiology workstations. Handels describes another German teleradiology system, called KAMEDIN, which has been used in a field test for several months but has never gone to clinical routine [<xref ref-type="bibr" rid="ref22">22</xref>].</p>
                <p>All major image modality vendors in the field of radiology have been talking about teleradiology since 1994 or 1995. The main difference of the industrial solutions is that they simply extend the local area network of the radiology department by an ISDN link to another location. Images are then sent with proprietary protocols (sometimes with DICOM) to a remote machine. Teleconferences with two users at different locations who work together on the same images are not possible. Security aspects are missing as well.</p>
                <p>CHILI (and its predecessor MEDICUS) seems to be the only system which has a complete data security concept [<xref ref-type="bibr" rid="ref8">8</xref>]. A great advantage of the system, compared to others, is the direct connection with the imaging modalities of different vendors. The DICOM protocol can be used to receive the images, or proprietary solutions can be enabled for older modalities without DICOM interfaces.</p>
                <p>A major feature of CHILI is that it is not a dedicated teleradiology system, such as its prototype MEDICUS or the KAMEDIN system [<xref ref-type="bibr" rid="ref22">22</xref>]. Instead, it is a general purpose multimodality workstation with strong teleradiology and security features. Cross-platform communication, vendor independence, and extensibility are major distinctive features in comparisons. The system is also used for advanced image analysis functions and image reporting.</p>
                <p>New teleradiology systems are currently under development in the programming language Java [<xref ref-type="bibr" rid="ref12">12</xref>]. This makes the systems independent of the operating system and hardware used. Examples are the CYPRIS system which is under development by Klaiber [<xref ref-type="bibr" rid="ref25">25</xref>] or the Jive system by Kleber [<xref ref-type="bibr" rid="ref26">26</xref>]. Both systems are not yet mature enough to be compared with the CHILI environment. They lack basic image analysis functions, cooperative teleconferences, strong security features, and the full spectrum of vendor and system independent communications. The performance drawback of Java is another aspect which has to be taken into account; but independence from the operating system and the hardware are fascinating features.</p>
            </sec>
            <sec>
                <title>Conclusion and Outlook</title>
                <p>CHILI is not just a research project where the system has been used for some test cases. It is integrated in the clinical routine in many different locations and institutions. The accounting numbers and the feedback of the users are proving that the CHILI architecture provides a powerful and flexible environment for PACS and teleradiology. PlugIn modules will also extend the multimodality workstation for teleradiology by providing advanced image analysis and therapy planning functionality.</p>
                <p>In the future, development will continue on the Java implementation of the complete CHILI architecture to offer the most flexible and hardware/software independent environment for PACS and teleradiology. The feedback and suggestions of the users has influenced the system architecture by a great extent. Our own experience is that the differences between PACS and teleradiology components will vanish. This observation is supported by a recent market investigation by Frost&amp;Sullivan [<xref ref-type="bibr" rid="ref27">27</xref>]. The "tele" aspect will become a natural feature of radiological workstations. Radiologists will profit from better performance; and as a consequence, the patients will receive better treatment.</p>
            </sec>
        </sec>
    </body>
    <back>
        <ack>
            <p>CHILI is a registered trademark of Steinbeis-Transferzentrum Medizinische Informatik, Heidelberg, Germany.</p>
            <p>
                <ext-link ext-link-type="uri" xlink:href="http://www.chili-radiology.com/" xlink:type="simple">http://www.chili-radiology.com/</ext-link>
            </p>
        </ack>
        <fn-group>
            <fn fn-type="conflict">
                
                <p>The concepts of the CHILI system have been developed at the German Cancer Research Center in cooperation with the technology transfer company Steinbeis Transferzentrum Medizinische Informatik (STZ-MI) Heidelberg, Germany, which develops and markets the CHILI Software. Some of the authors are working as employess or consultants for that company.</p>
            </fn>
        </fn-group>
        <ref-list>
            <ref id="ref1">
                <label>1</label>
                <nlm-citation citation-type="web" xlink:type="simple">
                    <source>American College of Radiology: ACR Standard for Teleradiology. Res. 35-1998</source>
                    <access-date>1999 Jul 27</access-date>
                    <comment><ext-link ext-link-type="uri" xlink:href="http://www.acr.org/departments/stand_accred/standards/html_standards/html_files/diag/telerad.html" xlink:type="simple">http://www.acr.org/departments/stand_accred/standards/html_standards/html_files/diag/telerad.html</ext-link></comment>
                </nlm-citation>
            </ref>
            <ref id="ref2">
                <label>2</label>
                <nlm-citation citation-type="book" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>HJ</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Werner</surname>
                            <given-names>O</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schwab</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Wolsiffer</surname>
                            <given-names>K</given-names>
                        </name>
                        <name name-style="western">
                            <surname>G&#xF6;ransson</surname>
                            <given-names>B</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Bor&#xE4;lv</surname>
                            <given-names>E</given-names>
                        </name>
                        <name name-style="western">
                            <surname>M&#xFC;ller</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>HP</given-names>
                        </name>
                    </person-group>
                    <person-group person-group-type="editor">
                        <name name-style="western">
                            <surname>Lemke</surname>
                            <given-names>HU</given-names>
                        </name>
                    </person-group>
                    <article-title>Teleradiology System MEDICUS</article-title>
                    <source>CAR '96: Computer Assisted Radiology. 10th International Symposium and Exhibition; Paris</source>
                    <year>1996</year>
                    <publisher-loc>Amsterdam</publisher-loc>
                    <publisher-name>Elsevier</publisher-name>
                    <fpage>537</fpage>
                    <lpage>542</lpage>
                </nlm-citation>
            </ref>
            <ref id="ref3">
                <label>3</label>
                <nlm-citation citation-type="book" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Werner</surname>
                            <given-names>O</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schwab</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>M&#xFC;ller</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Bahner</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>HP</given-names>
                        </name>
                    </person-group>
    <person-group person-group-type="editor">
        <name name-style="western">
            <surname>Lemke</surname>
            <given-names>Heinz U</given-names>
        </name>
        <name name-style="western">
            <surname>Vannier</surname>
            <given-names>MW</given-names>
        </name>
        <name name-style="western">
            <surname>Inamura</surname>
            <given-names>Kiyonari</given-names>
        </name>
    </person-group>
                    <article-title>Second Generation Teleradiology</article-title>
                    <source>CAR '97 - Computer Assisted Radiology and Surgery</source>
                    <year>1997</year>
                    <month>9</month>
                    <day>1</day>
                    <publisher-loc>Amsterdam</publisher-loc>
                    <publisher-name>Elsevier Science Pub Co</publisher-name>
                    <fpage>632</fpage>
                    <lpage>637</lpage>
                </nlm-citation>
            </ref>
            <ref id="ref4">
                <label>4</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Werner</surname>
                            <given-names>O</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schwab</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>M&#xFC;ller</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>H P</given-names>
                        </name>
                    </person-group>
    <article-title>A Three-Generation Model for Teleradiology</article-title>
                    <source>IEEE Trans Inf Technol Biomed</source>
                    <year>1998</year>
                    <month>3</month>
                    <volume>2</volume>
                    <issue>1</issue>
                    <fpage>20</fpage>
                    <lpage>5</lpage>
                    <pub-id pub-id-type="medline">20184422</pub-id>
    <pub-id pub-id-type="doi">10.1109/4233.678530</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref5">
                <label>5</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Bahner</surname>
                            <given-names>ML</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>HP</given-names>
                        </name>
                        <name name-style="western">
                            <surname>van Kaick</surname>
                            <given-names>G</given-names>
                        </name>
                    </person-group>
                    <article-title>Design necessities for future teleradiology systems - Conclusion from a field test</article-title>
                    <source>Eur Radiol</source>
                    <year>1997</year>
                    <issue>7 Suppl</issue>
                    <fpage>S17</fpage>
                </nlm-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
<nlm-citation citation-type="journal" xlink:type="simple">
    <person-group person-group-type="author">
        <name name-style="western">
            <surname>Engelmann</surname>
            <given-names>U</given-names>
        </name>
        <name name-style="western">
            <surname>Schr&#xF6;ter</surname>
            <given-names>A</given-names>
        </name>
        <name name-style="western">
            <surname>G&#xFC;nnel</surname>
            <given-names>U</given-names>
        </name>
        <name name-style="western">
            <surname>Demiris</surname>
            <given-names>A M</given-names>
        </name>
        <name name-style="western">
            <surname>Makabe</surname>
            <given-names>M</given-names>
        </name>
        <name name-style="western">
            <surname>Evers</surname>
            <given-names>H</given-names>
        </name>
        <name name-style="western">
            <surname>Meinzer</surname>
            <given-names>H P</given-names>
        </name>
    </person-group>
    <article-title>The HELIOS Image Related Services</article-title>
    <source>Comput Methods Programs Biomed</source>
    <year>1994</year>
    <month>12</month>
    <volume>45 Suppl</volume>
    <issue>45 Suppl</issue>
    <fpage>S65</fpage>
    <lpage>78</lpage>
    <pub-id pub-id-type="medline">95188543</pub-id>
</nlm-citation>
            </ref>
            <ref id="ref7">
                <label>7</label>
                <nlm-citation citation-type="web" xlink:type="simple">
                    <source>IEFTF-TLS Working Group</source>
                    <access-date>1999 Jul 27</access-date>
                    <comment><ext-link ext-link-type="uri" xlink:href="http://www.consensus.com/ietf-tls/ietf-tls-home.html" xlink:type="simple">http://www.consensus.com/ietf-tls/ietf-tls-home.html</ext-link></comment>
                </nlm-citation>
            </ref>
            <ref id="ref8">
                <label>8</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>H J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Saurbier</surname>
                            <given-names>F</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>H P</given-names>
                        </name>
                    </person-group>
                    <article-title>How to deal with security issues in teleradiology</article-title>
                    <source>Comput Methods Programs Biomed</source>
                    <year>1997</year>
                    <month>5</month>
                    <volume>53</volume>
                    <issue>1</issue>
                    <fpage>1</fpage>
                    <lpage>8</lpage>
                    <pub-id pub-id-type="medline">97268199</pub-id>
                    <pub-id pub-id-type="pii">S0169260796017981</pub-id>
                    <pub-id pub-id-type="doi">10.1016/S0169-2607(96)01798-1</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref9">
                <label>9</label>
                <nlm-citation citation-type="book" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Garfinkel</surname>
                            <given-names>S</given-names>
                        </name>
                    </person-group>
                    <source>PGP: Pretty Good Privacy</source>
                    <year>1995</year>
                    <publisher-loc>Cambridge (MA)</publisher-loc>
                    <publisher-name>O'Reilly &amp; Associates Inc</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref10">
                <label>10</label>
                <nlm-citation citation-type="book" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schwab</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Werner</surname>
                            <given-names>O</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Makabe</surname>
                            <given-names>MH</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>HP</given-names>
                        </name>
                    </person-group>
    <person-group person-group-type="editor">
        <name name-style="western">
            <surname>Lemke</surname>
            <given-names>HU</given-names>
        </name>
        <name name-style="western">
            <surname>Vannier</surname>
            <given-names>MW</given-names>
        </name>
        <name name-style="western">
            <surname>Inamura</surname>
            <given-names>K</given-names>
        </name>
        <name name-style="western">
            <surname>Farman</surname>
            <given-names>AG</given-names>
        </name>
        <name name-style="western">
            <surname>Doi</surname>
            <given-names>K</given-names>
        </name>
        <name name-style="western">
            <surname>Reiber</surname>
            <given-names>JHC</given-names>
        </name>
    </person-group>
                    <article-title>Openness in (Tele-) Radiology Workstations: The CHILI PlugIn Concept</article-title>
                    <source>CAR '98 - Computer Assisted Radiology and Surgery</source>
                    <year>1998</year>
                    <month>6</month>
                    <day>1</day>
                    <publisher-loc>Amsterdam</publisher-loc>
                    <publisher-name>Elsevier Science Pub Co</publisher-name>
                    <fpage>437</fpage>
                    <lpage>442</lpage>
                </nlm-citation>
            </ref>
            <ref id="ref11">
                <label>11</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Evers</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Mayer</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Wolsiffer</surname>
                            <given-names>K</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>H P</given-names>
                        </name>
                    </person-group>
                    <article-title>Extending a teleradiology system by tools for 3D-visualization and volumetric analysis through a plug-in mechanism</article-title>
                    <source>Medinfo</source>
                    <year>1998</year>
                    <volume>9 Pt 2</volume>
                    <issue>9 Pt 2</issue>
                    <fpage>1033</fpage>
                    <lpage>5</lpage>
                    <pub-id pub-id-type="medline">99312611</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref12">
                <label>12</label>
                <nlm-citation citation-type="book" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Flanagan</surname>
                            <given-names>David</given-names>
                        </name>
                    </person-group>
                    <source>Java in a Nutshell (Nutshell Handbook)</source>
                    <year>1996</year>
                    <month>2</month>
                    <day>1</day>
                    <publisher-loc>Cambridge (MA)</publisher-loc>
                    <publisher-name>O'Reilly</publisher-name>
                </nlm-citation>
            </ref>
            <ref id="ref13">
                <label>13</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Evers</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Mayer</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Wolsiffer</surname>
                            <given-names>K</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>HP</given-names>
                        </name>
                    </person-group>
                    <article-title>Volume visualization and interactive tools plugged into a teleradiology system. Proceedings of Conference on Medical Imaging; 1998; San Diego, USA</article-title>
                    <source>SPIE</source>
                    <year>1998</year>
                    <fpage>20</fpage>
                </nlm-citation>
            </ref>
            <ref id="ref14">
                <label>14</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Glombitza</surname>
                            <given-names>G</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Lamad&#xE9;</surname>
                            <given-names>W</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Demiris</surname>
                            <given-names>A M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>G&#xF6;pfert</surname>
                            <given-names>M R</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Mayer</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Bahner</surname>
                            <given-names>M L</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>H P</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Richter</surname>
                            <given-names>G</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Lehnert</surname>
                            <given-names>T</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Herfarth</surname>
                            <given-names>C</given-names>
                        </name>
                    </person-group>
                    <article-title>Virtual planning of liver resections: image processing, visualization and volumetric evaluation</article-title>
                    <source>Int J Med Inform</source>
                    <year>1999</year>
                    <month>3</month>
                    <volume>53</volume>
                    <issue>2-3</issue>
                    <fpage>225</fpage>
                    <lpage>37</lpage>
                    <pub-id pub-id-type="medline">99208234</pub-id>
    <pub-id pub-id-type="doi">10.1016/S1386-5056(98)00162-2</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref15">
                <label>15</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>De Simone</surname>
                            <given-names>R</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Glombitza</surname>
                            <given-names>G</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Vahl</surname>
                            <given-names>C F</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Albers</surname>
                            <given-names>J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>H P</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Hagl</surname>
                            <given-names>S</given-names>
                        </name>
                    </person-group>
                    <article-title>Three-dimensional color Doppler for assessing mitral regurgitation during valvuloplasty</article-title>
                    <source>Eur J Cardiothorac Surg</source>
                    <year>1999</year>
                    <month>2</month>
                    <volume>15</volume>
                    <issue>2</issue>
                    <fpage>127</fpage>
                    <lpage>33</lpage>
                    <pub-id pub-id-type="medline">99236284</pub-id>
                    <pub-id pub-id-type="pii">S1010794098003121</pub-id>
                    <pub-id pub-id-type="doi">10.1016/S1010-7940(98)00312-1</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref16">
                <label>16</label>
                <nlm-citation citation-type="book" xlink:type="simple">
    <person-group person-group-type="author">
        <name name-style="western">
            <surname>Siever</surname>
            <given-names>Ellen</given-names>
        </name>
    </person-group>
    <source>Linux in a Nutshell, 2nd Edition (O'Reilly Nutshell)</source>
    <year>1999</year>
    <month>2</month>
    <day>2</day>
    <publisher-loc>Cambridge (MA)</publisher-loc>
    <publisher-name>O'Reilly &amp; Associates</publisher-name>
</nlm-citation>
            </ref>
            <ref id="ref17">
                <label>17</label>
                <nlm-citation citation-type="web" xlink:type="simple">
                    <source>Sonderforschungsbereich 414: Information Technology in Medicine: Computer and Sensor Supported Surgery</source>
                    <access-date>1999 Jul 27</access-date>
                    <comment><ext-link ext-link-type="uri" xlink:href="http://mbi.dkfz-heidelberg.de/mbi/sfb414/index.html" xlink:type="simple">http://mbi.dkfz-heidelberg.de/mbi/sfb414/index.html</ext-link></comment>
                </nlm-citation>
            </ref>
            <ref id="ref18">
                <label>18</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Engelmann</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schr&#xF6;ter</surname>
                            <given-names>A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Baur</surname>
                            <given-names>U</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Schwab</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Evers</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>HP</given-names>
                        </name>
                    </person-group>
                    <person-group person-group-type="editor">
                        <name name-style="western">
                            <surname>Piqueras</surname>
                            <given-names>J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Carreno</surname>
                            <given-names>JC</given-names>
                        </name>
                    </person-group>
                    <article-title>Teleradiology: Not always Plug &amp; Play. A Case Report</article-title>
                    <source>Proceedings of the 16th EuroPACS Annual Meeting</source>
                    <year>1998</year>
                    <publisher-loc>Barcelona</publisher-loc>
                    <publisher-name>Vall d'Hebron</publisher-name>
                    <fpage>159</fpage>
                    <lpage>162</lpage>
                </nlm-citation>
            </ref>
            <ref id="ref19">
                <label>19</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Grigsby</surname>
                            <given-names>J</given-names>
                        </name>
                    </person-group>
                    <article-title>Current status of domestic telemedicine [review]</article-title>
                    <source>J Med Syst</source>
                    <year>1995</year>
                    <month>2</month>
                    <volume>19</volume>
                    <issue>1</issue>
                    <fpage>19</fpage>
                    <lpage>27</lpage>
                    <pub-id pub-id-type="medline">7790803</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref20">
                <label>20</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Reponen</surname>
                            <given-names>J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>L&#xE4;hde</surname>
                            <given-names>S</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Tervonen</surname>
                            <given-names>O</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Ilkko</surname>
                            <given-names>E</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Rissanen</surname>
                            <given-names>T</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Suramo</surname>
                            <given-names>I</given-names>
                        </name>
                    </person-group>
                    <article-title>Low-cost digital teleradiology</article-title>
                    <source>Eur J Radiol</source>
                    <year>1995</year>
                    <month>3</month>
                    <volume>19</volume>
                    <issue>3</issue>
                    <fpage>226</fpage>
                    <lpage>31</lpage>
                    <pub-id pub-id-type="medline">95324605</pub-id>
                    <pub-id pub-id-type="pii">0720048X94006029</pub-id>
    <pub-id pub-id-type="doi">10.1016/0720-048X(94)00602-9</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref21">
                <label>21</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>G&#xF3;mez</surname>
                            <given-names>E J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Del Pozo</surname>
                            <given-names>F</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Quiles</surname>
                            <given-names>J A</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Arredondo</surname>
                            <given-names>M T</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Rahms</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Sanz</surname>
                            <given-names>M</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Cano</surname>
                            <given-names>P</given-names>
                        </name>
                    </person-group>
                    <article-title>A telemedicine system for remote cooperative medical imaging diagnosis</article-title>
                    <source>Comput Methods Programs Biomed</source>
                    <year>1996</year>
                    <month>1</month>
                    <volume>49</volume>
                    <issue>1</issue>
                    <fpage>37</fpage>
                    <lpage>48</lpage>
                    <pub-id pub-id-type="medline">96230983</pub-id>
                    <pub-id pub-id-type="pii">0169260795017062</pub-id>
                    <pub-id pub-id-type="doi">10.1016/0169-2607(95)01706-2</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref22">
                <label>22</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Handels</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Busch</surname>
                            <given-names>C</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Encarna&#xE7;&#xE3;o</surname>
                            <given-names>J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Hahn</surname>
                            <given-names>C</given-names>
                        </name>
                        <name name-style="western">
                            <surname>K&#xFC;hn</surname>
                            <given-names>V</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Miehe</surname>
                            <given-names>J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>P&#xF6;ppl</surname>
                            <given-names>S I</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Rinast</surname>
                            <given-names>E</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Rossmanith</surname>
                            <given-names>C</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Seibert</surname>
                            <given-names>F</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Will</surname>
                            <given-names>A</given-names>
                        </name>
                    </person-group>
                    <article-title>KAMEDIN: a telemedicine system for computer supported cooperative work and remote image analysis in radiology</article-title>
                    <source>Comput Methods Programs Biomed</source>
                    <year>1997</year>
                    <month>3</month>
                    <volume>52</volume>
                    <issue>3</issue>
                    <fpage>175</fpage>
                    <lpage>83</lpage>
                    <pub-id pub-id-type="medline">97203769</pub-id>
                    <pub-id pub-id-type="pii">S0169260796017907</pub-id>
                    <pub-id pub-id-type="doi">10.1016/S0169-2607(96)01790-7</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref23">
                <label>23</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Binkhuysen</surname>
                            <given-names>F H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Ottes</surname>
                            <given-names>F P</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Valk</surname>
                            <given-names>J</given-names>
                        </name>
                        <name name-style="western">
                            <surname>De Vries</surname>
                            <given-names>C</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Algra</surname>
                            <given-names>P R</given-names>
                        </name>
                    </person-group>
                    <article-title>Remote expert consultation for MRI procedures by means of teleradiology</article-title>
                    <source>Eur J Radiol</source>
                    <year>1995</year>
                    <month>1</month>
                    <volume>19</volume>
                    <issue>2</issue>
                    <fpage>147</fpage>
                    <lpage>50</lpage>
                    <pub-id pub-id-type="medline">95228700</pub-id>
                    <pub-id pub-id-type="pii">0720048X9400573U</pub-id>
                    <pub-id pub-id-type="doi">10.1016/0720-048X(94)00573-U</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref24">
                <label>24</label>
                <nlm-citation citation-type="journal" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Maclean</surname>
                            <given-names>JR</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Brebner</surname>
                            <given-names>JA</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Norman</surname>
                            <given-names>JN</given-names>
                        </name>
                    </person-group>
                    <article-title>A review of Scottish telemedicine [review]</article-title>
                    <source>J Telemed Telecare</source>
                    <year>1995</year>
                    <volume>1</volume>
                    <issue>1</issue>
                    <fpage>1</fpage>
                    <lpage>6</lpage>
                    <comment>(review)</comment>
                    <pub-id pub-id-type="medline">9375111</pub-id>
                </nlm-citation>
            </ref>
            <ref id="ref25">
                <label>25</label>
                <nlm-citation citation-type="book" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Klaiber</surname>
                            <given-names>HC</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Handels</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>P&#xF6;ppl</surname>
                            <given-names>S</given-names>
                        </name>
                    </person-group>
                    <person-group person-group-type="editor">
                        <name name-style="western">
                            <surname>Evers</surname>
                            <given-names>H</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Glombitza</surname>
                            <given-names>G</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Lehmann</surname>
                            <given-names>T</given-names>
                        </name>
                        <name name-style="western">
                            <surname>Meinzer</surname>
                            <given-names>HP</given-names>
                        </name>
                    </person-group>
                    <article-title>Bilddatenaustausch und radiologsiche Telekooperation auf der Basis von Java</article-title>
                    <source>Informatik Aktuell - Bildverarbeitung f&#xFC;r die Medizin 1999 - Algorithmen, Systeme, Anwendungen. Berlin, Heidelberg</source>
                    <year>1999</year>
                    <publisher-loc>New York</publisher-loc>
                    <publisher-name>Springer</publisher-name>
                    <fpage>226</fpage>
                    <lpage>230</lpage>
                </nlm-citation>
            </ref>
            <ref id="ref26">
                <label>26</label>
                <nlm-citation citation-type="web" xlink:type="simple">
                    <person-group person-group-type="author">
                        <name name-style="western">
                            <surname>Kleber</surname>
                            <given-names>K</given-names>
                        </name>
                    </person-group>
                    <collab collab-type="authors">Universitaet Witten/Herdecke, Institute for microtherapy</collab>
                    <source>Jive: A Java based DICOM Image Viewer</source>
                    <access-date>1999 Jul 27</access-date>
                    <comment><ext-link ext-link-type="uri" xlink:href="http://www.microtherapy.de/e/imt/fi/medinf/jive.html" xlink:type="simple">http://www.microtherapy.de/e/imt/fi/medinf/jive.html</ext-link></comment>
                </nlm-citation>
            </ref>
            <ref id="ref27">
                <label>27</label>
                <nlm-citation citation-type="book" xlink:type="simple">
                    <collab xlink:type="simple">Frost and Sullivan</collab>
                    <source>European Telemedicine Markets. Report #3596-48</source>
                    <year>1999</year>
                    <publisher-loc>London</publisher-loc>
                    <publisher-name>Frost &amp; Sullivan</publisher-name>
                </nlm-citation>
            </ref>
        </ref-list>
    </back>
</article>
