Abstract:
The invention relates to an apparatus for receiving, storing, sharing and transmitting digital medical image data, comprising a processor, a hard drive, and connectivity means for communicating with a local or global network. The processor comprises means for hosting a server supporting receipt, compression, encryption and data integrity check of the medical image data received from medical modalities, storing of the medical image data on the hard drive of the apparatus, providing access to the apparatus&#39; web based administration and management interface and supporting the query and retrieval of medical image data stored in the apparatus from any modality.

Description:
[0001]    This a regular, non-provisional patent application based upon and claiming the priority of provisional patent application Ser. No. 61/728,543, filed Nov. 20, 2012, now pending, the contents of which is incorporated herein by reference thereto. The present invention relates to a small portable, hand sized “All-in-One” apparatus for securely transferring, sharing and storing of medical images using Internet even with a limited bandwidth. In the following description, this apparatus is referred to as “Apparatus”. 
     
    
       [0002]    The invention also relates to a web portal for accessing the medical images transferred by the apparatus according to the present invention. 
       BACKGROUND 
       [0003]    The Apparatus and solutions that the present inventors have developed up to now are based on the use of the well-known DICOM Standard and are using media like CD, DVD and Bluray for the distribution, sharing and archiving of medical images. The best example is the “Patient CD11, replacing films, used to transfer and share medical images between clinics or radiologists and their patients, referral physicians, specialists and hospitals. DICOM is the acronym for Digital Imaging and Communications in Medicine and is a standard known for the person skilled in the art that describes how medical image data should be handled, stored, distributed or transmitted and printed. 
         [0004]    Today, in Europe and North America, medical image distribution and archiving can be done using Internet due to the significant bandwidth increase, a lowering of the infrastructure costs and network security improvements (VPN, private networks, . . . ). As a result, it makes sense that hospitals may want to replace Patient CDs by a solution to exchange and transfer medical images using the Internet. It makes also sense to provide access for Doctors and even Patients to review their medical images, including the diagnostic report, using a secure WEB-based portal. 
         [0005]    Today, some “Data Centers” are offering secure hosting solutions to archive and share medical images. However, in the medical imaging business, some doctors have some reservations to transfer data across the Internet. Also, even if the Internet bandwidth is continuously increasing, the resolution and as a result hereof the size of the digital medical images are also dramatically increasing. Last but not least, the Internet infrastructure in most emerging countries does not permit to consider using Internet to transfer digital medical images because of the limited bandwidth and reliability of the Internet network. It is obvious that the Internet infrastructure will improve in the coming years but not right away. 
         [0006]    In order to solve the abovementioned problems the present inventors have developed an Apparatus and web portal as set forth in the appended claims. 
       SUMMARY OF THE INVENTION 
       [0007]    Basically, the Apparatus according to the present invention comprises a LINUX based mini-PC with local storage capacity. The Apparatus has been designed to transfer, distribute and archive medical images using the Internet. The Apparatus has been engineered to cope with limited bandwidth Internet connections and is able to manage data flow. interruptions. 
         [0008]    The Apparatus according to the invention comprises an advanced rule-based router for medical images including hardware and software. According to, a preferred embodiment, it includes a high capacity buffer/storage. Thanks to this buffer, the images can be transferred using Internet even with limited bandwidth, interrupted and/or disruptive connections. 
         [0009]    The Apparatus manages compression, encryption and data integrity check of the medical images transmitted across the Internet. 
         [0010]    Optionally, those images can be reviewed by referring physicians and even patients using a WEB portal. 
         [0011]    According to a preferred embodiment, the Apparatus is also capable of replicating its content to a local network storage (e.g. a NAS with a RAID controller and several hard drives) and/or to an external secure “Data Center”. Different options are available. The first is based on the Amazon S3 services (see http://aws.amazon.com) providing a worldwide network of Internet services like data storage hosting and virtual servers. The second option is to use a FTPS server (File Transfer Protocol Secured) or SFTP server (SSH File Transfer Protocol) hosted on the Apparatus itself, by a third-party Internet Service Provider or even by a hospital centralizing the medical images supplied by external clinics or mobile units. 
         [0012]    The Apparatus according to the present invention is capable of performing one or more of the following functions, and as such can be used for a wide variety of applications in the medical field: 
         [0013]    a. Transferring images from Imaging center(s) or Radiology departments to Diagnostic center(s); 
         [0014]    b. Transferring images from several “satellite” clinics or imaging centers to a central hospital for diagnose; 
         [0015]    c. Transferring images from a central hospital or diagnostic center to Radiologist(s) working from a remote facility or home; 
         [0016]    d. Storing DICOM images as a local archive in an imaging center or small clinic; 
         [0017]    e. Archiving DICOM images to an external Secure Data Center; 
         [0018]    f. Sending DICOM images “instantly” from Mobile Radiology equipment traveling to distant cities and villages (e.g. trucks equipped with a CT/MRI scanner or other radiology equipment) using wireless 3G/4G connectivity; 
         [0019]    g. Publishing DICOM images and diagnostic reports using a WEB portal for referring physician and potentially patients; 
         [0020]    h. Polyclinics wishing to send medical images to referring physicians; 
         [0021]    i. Sharing a CD/DVD robot between different facilities from a central location; 
         [0022]    j. Transferring CT images to a shared  3 D printer (e.g. dental modeling). 
       Installation and Maintenance of the Apparatus: 
       [0023]    The installation of the Apparatus of the present invention is extremely simple: prior to shipment to the customer, the Apparatus not only has been preinstalled but also preconfigured based on technical data provided by the end-user (network infrastructure, radiology equipment). The transfer parameters (Amazon or FTPS/SFTP} are also preconfigured. The pre-installation (hardware assembling, operating system installation, installation of our software modules) is performed at manufacturer&#39;s facilities or by its sales/technical partners. The end-user needs only to unpack the Apparatus, plug the power and network cable and he will be ready to go. Obviously, the only requirement is an Internet connection through the LAN (Local Area Network) or a 3G/4G USB module, available as an option. 
         [0024]    Last but not least, the maintenance of the Apparatus is really easy: an encrypted backup of the database and the configuration parameters are automatically saved to an USB stick (provided with the Apparatus). In case of a failure, the customer needs only to insert that USB key in a new Apparatus (provided to the customer under the terms of a maintenance contract). Both database and parameters will automatically be restored. The data (i.e. the images) stored on the local hard drive will also be restored from the local NAS or the external Data Center. It is definitely a great benefit for medical institutions that do not have skilled IT people on site. No need also for resellers and distributors to send a technician or engineer on-site which can be expensive and time consuming in large countries. 
       Fields of Application of the Apparatus 
       [0025]    The Apparatus has been designed to fit all requirements, starting from small clinics with a limited Internet infrastructure and budget up to the largest medical institutions wanting to exchange images with their subcontractors (e.g. acquisition centers, private radiologist). The Apparatus suits also to referring physician, doctors and patients who want to review their images. The Apparatus is appropriate for Europe and North America having fast Internet connections as well as for emerging countries having limited Internet bandwidth not allowing a reliable transfer of large files containing medical images. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0026]      FIG. 1  shows the apparatus with a transparent acrylic U form cover which cover hides the front connectors (USB port, memory card reader, . . . not used) and a round hole in the front for access to the power button. Inside the apparatus includes PC features such as: a processor, a frame for a hard drive, required connectivity, USB ports, memory card reader, Gigabit Ethernet, Wi-Fi interface with built-in antenna, HOMI and VGA video output. 
           [0027]      FIGS. 2 and 3  show computer screen shots with a WEB based remote user interface using HTMLS/JQuery technologies hosted by an Apache Tomcat WEB server directly installed on the Apparatus. 
           [0028]      FIG. 4  shows a series tab with a list of DICOM images sent and received. 
           [0029]      FIGS. 5 ,  6  and  7  show the web based system configuration interface. 
           [0030]      FIG. 8  shows an advanced system configuration. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     Hardware Design 
       [0031]    Referring to  FIG. 1 , the hardware design of the Apparatus according to the present invention is based on a personal computer manufactured by Foxconn and marketed under the brand name “NanoPC”. 
         [0032]    So the Apparatus according to the invention comprises the following features comprises in such PC: an Intel ATOM processor, a frame for a 2.5″ hard drive and all required connectivity: USB 3 ports, memory card reader, Gigabit Ethernet, Wi-Fi interface with built-in antenna, HDMI and VGA video output. 
         [0033]    To this configuration, the present inventors have added 2 GB of RAM which is more than sufficient for performing the functions and applications required under the present invention and the LINUX operating system. The NanoPC is only 19 cm (7.5″) wide, 13 cm (S″) deep and 3 cm (1″) high. The noiseless radial fan allows air circulation from the left to the right side. 
         [0034]    The Nano PC emits limited heat which considerably preserves the lifetime of the internal hard drive. The temperature does not exceed 40° Celsius (104° Fahrenheit) in a 25° Celsius (77° Fahrenheit) room. 
         [0035]    The Apparatus according to the invention only consumes less than 20 W which makes it very environment friendly. 
         [0036]    The high speed heavy duty hard drive is intended to be used for audio and video streaming which dramatically increases the data transfer while extending its lifetime. 
         [0037]    A mobile internet module (2G, 3G and 4G) is also available as an option. It allows transferring images using a wireless connection which is especially useful for mobile radiology trucks or clinics located in place not having a wired Internet connection. 
         [0038]    The Apparatus according to the invention is inserted in a transparent acrylic U form cover with a white painted inside. This cover hides the front connectors (USB port, memory card reader, . . . ) that are not used. Only a round hole in the front provides access to the power button. A pen must be inserted in that hole to push on the button which is on purpose to avoid accidental power off. The Apparatus is supposed to be on 24 h by 24 h. 
         [0039]    In case of a power failure, the Apparatus will reboot automatically when the power is restored. 
         [0040]    Reference is made to  FIG. 1  for illustrative purposes. 
         [0041]    The Apparatus according to the invention further comprises an external USB storage key. The key contains: 
         [0042]    a. The software activation key 
         [0043]    b. The configuration of the different software modules 
         [0044]    c. A daily backup of the local MySQL database 
         [0045]    d. A Network file “template” allowing to change the IP settings of the Apparatus. 
       Extended Configuration of the Apparatus 
       [0046]    In the case of a large number of institutions having to send DICOM images to a central location (e.g. 20 imaging centers to a central diagnostic center), the performance of the Apparatus according to the invention located at the central place may be too slow. For such a situation, an extended configuration of the Apparatus appears to be the right solution. Basically, such can be offered in the form of a Virtual Server (e.g. VMWare} image that can be installed on any server running exactly the same functionality as the Apparatus of the invention but offering more power, responsiveness and increased data storage capacity. 
       Software Architecture of the Apparatus According to the Invention 
     Operating System &amp; Environment 
       [0047]    The Apparatus is Ubuntu LINUX based. Only the UNUXkernel is kept to improve the overall performance. The LINUX graphical user interface is not installed. 
         [0048]    All software modules of the Apparatus are JAVA based and de facto support most operating systems like LINUX {like the Apparatus itself) and Windows (for the WEB portal). 
         [0049]    All software modules are using an open standard database engine (e.g. MySQL) using JDBC (JAVA Database Connectivity). 
         [0050]    The Apparatus also hosts an open standard WEB server {e.g. Apache Tomcat). Its main purpose is to provide access to the Apparatus&#39; WEB based management administration interface. 
         [0051]    a. DICOM Server 
         [0052]    The main module is a genuine DICOM server that runs as a LINUX daemon. It supports: 
         [0053]    a. DICOM Store, i.e. C-STORE (e.g. DICOM modalities sending images to the Apparatus.) 
         [0054]    b. DICOM Query/Retrieve, i.e. C-FIND &amp; C-MOVE (e.g. Query and Retrieve DICOM images stored in the Apparatus from a DICOM modality like a Diagnostic Workstation) 
         [0055]    The DICOM Server can be configured to automatically forward received DICOM images (using C-MOVE) to a different modality (e.g. PACS, Diagnostic Workstation, . . . ). 
         [0056]    According to a preferred embodiment of the invention, the DICOM Server also manages replication of the DICOM images stored in the internal hard drive to a NAS (Network Attached Storage), DAS (Direct Attached Storage) and CAS (Content Addressed Storage). This “secondary” storage device is also used to extend the capacity of the internal HDD. According to a further preferred embodiment of the invention, when the Apparatus, in particular its hard disk is running out of space, the oldest images will automatically be deleted (FIFO) while a copy will remain available from the secondary storage. 
         [0057]    a. DICOM Router 
         [0058]    Depending on some criteria (e.g. the type of modality the images have been sent from), the DICOM router module may apply some changes to the properties of the images (e.g. anonymize the metadata of a series of images) and/or route the images to a defined destination (e.g. a diagnostic workstation). 
         [0059]    Here are the different criteria that may apply: 
         [0060]    a. Value(s) and/or presence of a DICOM tag(s) b. Calling AET (i.e. the modality where the images are sent from) c. Called AET (i.e. the modality where the images are sent to) 
         [0061]    Multiple criteria can be combined. 
         [0062]    Here are the different actions the module may perform: 
         [0063]    a. Change the value of DICOM tag(s) 
         [0064]    b. Add/Remove DICOM tag(s) 
         [0065]    c. Route the image to a defined destination 
         [0066]    d. Change the Transfer Syntax (i.e. compress/decompress the images) 
         [0067]    Multiple actions can be combined. 
         [0068]    a. Transfer Module 
         [0069]    This module is responsible to manage the transfer of DICOM images between two or more Apparatuses. The Transfer Module is the gateway between the DICOM network and the transfer supported technologies i.e. Amazon S3, any FTPS/SFTP server or other proprietary file transfer technologies. 
         [0070]    Optionally a SFTP (Secure File Transfer Protocol) server can be installed on the Apparatus itself allowing “peer-to-peer” secure transfer of DICOM images. Transfer is secured by a SSH tunnel encrypting the exchange of series of DICOM images using FTP servers hosted on the Apparatus. 
         [0071]    a. HL-7 Server Module 
         [0072]    This module is responsible for the reconciliation of the Patient data stored in images received by the Apparatus prior to forward them to a PACS and/or a Diagnostic Workstation. 
         [0073]    a. Email notification module 
         [0074]    As the Apparatus is a “black box” without any display, an email notification is available to warn users in case of an issue. The same module will send a daily report with the list of all the studies that have been sent and received. That report is sent as an encrypted PDF attachment to the email. 
       Management Interface of the Apparatus According to the Invention 
       [0075]    The Apparatus does not have the LINUX graphical user interface (GUI). This is done deliberately to optimize the overall performance of the hardware. Also, it is not supposed to be connected to a keyboard, a mouse and a monitor. 
         [0076]      FIG. 2  shows a WEB based remote user interface using HTMLS/JQuery technologies hosted by an Apache Tomcat WEB server is directly installed on the Apparatus. HTMLS/JQuery user interface makes it compatible with any WEB browser (Internet Explorer, Google Chrome, Safari, . . . ) on all operating systems. 
         [0077]    Before accessing the WEB interface, a user name and password are required. Those can be saved in a cookie. 
         [0078]    Reference is made to  FIG. 2  for illustrative purposes. 
         [0079]    Like the Apparatus&#39; hardware design, the WEB pages are simple and sleek. 
         [0080]    Reference is made to  FIG. 3  for illustrative purposes. 
         [0081]    a. Content of the Apparatus: 
         [0082]    In  FIG. 4 , the “Series” tab shows the list of the series of DICOM images that have been sent and received. It is possible to filter on the date {Today, Yesterday or All). There is also a convenient “Search” field that will filter the list of the series based on some keywords or parts of keywords. 
         [0083]    Reference is made to  FIG. 4  for illustrative purposes. 
         [0084]    a. Multilingual user Interface 
         [0085]    The WEB interface is available is English, French, Dutch, Spanish, Brazilian Portuguese, Chinese, Russian, German, Polish and Italian. Our HTMLS interface has been designed to support any type of characters including Unicode 2-bytes. 
         [0086]    a. System configuration Interface 
         [0087]      FIGS. 5 ,  6  and  7  show the WEB based system configuration interface allows to configure the network parameters (IP address, subnet mask, DNS, . . . ) and AETs (Application Entity Title) identifying all modalities (CT scanner, ultrasound, diagnostic workstation). When two or more Apparatuses have to communicate with each other, the workflow can also be configured in the WEB interface, each Apparatus being identified by its AET. 
         [0088]    Reference is made to FIGS. S,  6  and  7  for illustrative purposes. 
         [0089]    It is also possible to generate activity reports and retrieve error logs. Preferably, one log file per day is created. Those files can be downloaded from the Apparatus for reference and/or analysis. 
         [0090]    Reference is made to  FIG. 8  for illustrative purposes. 
         [0091]    a. Advanced configuration Interface 
         [0092]    All system parameters of the Apparatus can be configured using the WEB based Webmin graphical interface. This tool lets you Apparatus configure a Proxy, manage third backup of the database and file system, update the operating system and much more. 
         [0093]    Reference is made to  FIG. 8  for illustrative purposes. 
       Main Processes 
       [0094]    a. DICOM Image Transfer Between Apparatus. 
         [0095]    The DICOM image transfer mechanism of the Apparatus preferably meets the following requirements: the workflow must be easy to use and implement, work with any kind of Internet connection (even slow and unstable), be highly secure—without the need of using VPN (Virtual Private Network)—slow, expensive and hard to implement—, leased lines or Private Cloud—, be cost effective and can be implemented in the entire world. The Apparatus preferably complies with local legislations related to storage, archiving and sharing of medical and patient data (e.g. HIPAA). 
         [0096]    The first option is using the Amazon WEB Services (AWS) providing a powerful worldwide infrastructure to transfer files, host virtual servers and highly secured databases for a decent price. AWS (see aws.amazon.com) has Data Centers in the US, Brazil, Ireland, Singapore, Australia and Japan. The Apparatus may use the Amazon S3 platform to transfer DICOM images (e.g. from one Apparatus to another one) and Amazon EC2 for virtual servers (e.g. to host our WEB portal for referring physicians to review medical images from their patients online). 
         [0097]    The second option uses a FTPS or SFTP server hosted by an Internet Service Provider (ISP) or directly in the Data Center of a hospital. 
         [0098]    The third option is to host a FTP server on each Apparatus and exchanging series of DICOM images using a SSH secured communication tunnel (equivalent to SFTP). The main benefit is that Apparatuses can transfer DICOM image without the need of a third party Internet Service Provider hosting a FTPS or SFTP server. Also, DICOM images will be transferred directly between Apparatuses without needing a VPN connection (File transfer is much faster using FTP across SSH). 
         [0099]    Amazon S3, FTPS and SFTP (local or remote) technologies offer the same level of security when transferring data from/to their servers. The communication is encrypted using SSL (Secured Socket Layer 256 bit with certificates). However, transferring images using a local FTPS/SFTP server guarantees that the exchanged data will be stored in the same country to comply with some local regulation. 
       a. Transfer Workflow 
     Definitions 
       [0100]    Bucket: it is a folder accessible from the root of a FTPS, SFTP (hosted on the Apparatus or any Data Center) or Amazon S3 account. This bucket may contain files that can be stored, renamed, moved or deleted by participating Apparatuses. 
         [0101]    Order Buckets—Order Files: each Apparatus has a dedicated Order Bucket where “Order Files” will instruct the Apparatus what action it has to perform (e.g. download a series of DICOM images that are ready to be transferred). The name of an Order file contains the Series UID (unique identifier for a series of DICOM images, typically a long chain of digits separated by dots) preceded by the status of the order to be, being or been performed (“download.” means that a series is ready to be downloaded, “ok.” Means that a series has been fully downloaded). 
         [0102]    Series Container: it is a single file which contains DICOM images that belong to the same series of images {e.g. the sagittal series of images from a CT scanner). When adding DICOM images to a Series Container, they are first compressed but without any loss of information (lossless compression). The algorithm used for the compression is ZIP. Optionally, Series Containers can be encrypted using the AES 256 bit algorithm. 
         [0103]    Series Bucket: a group of Apparatuses that have to exchange DICOM images will share one single “Series Bucket” that will contain the “Series Containers” to be transferred. 
         [0104]    AE Title (AET): the externally known name of a DICOM device or program, used to identify a DICOM application to other DICOM applications on the network. It is typically labelled with numbers and uppercase characters only. An AET is always associated with a unique combination of IP address and IP port. 
         [0105]    Called AET: the destination AET i.e. the DICOM device or program receiving DICOM images or instructions. 
         [0106]    Calling AET: the source/origin AET i.e. the DICOM device or program sending DICOM images or instructions. 
         [0107]    Transfer Association (TA): it is the relationship between a Called AET defined on an Apparatus and the Order Bucket of the Apparatus the DICOM images have to be sent to. 
         [0108]    Info file: a text file stored in the Series Bucket that provides information Workflow: about a series of DICOM images including partial Patient information, the Called AET and Calling AET. There is one Info file per Series Container. 
       Workflow 
       [0109]    Here is an extended explanation about the workflow when an Apparatus sends one or more series of DICOM images to one or several Apparatuses.
       1. A Modality (Calling AET) sends DICOM images—using C-Store—to a local Apparatus specifying the target Apparatus based on its Transfer Association (TA) i.e. its Called AET.   2. When getting the images, the DICOM Server of the local Apparatus will store the images on the local hard drive. Images are sorted per study date, study UID and series UID.   3. The DICOM Server will apply a latency time (parameter) before sending the images, series by series to the Transfer Server; including the TA based on the Called AET specified by the Modality.   4. The Transfer Server will compress the DICOM images creating one Series Container per series of images.   5. Optionally the Series Container will be encrypted using AES 256 bit.   6. Once the Series Container is ready, it will be transferred to the common Series Bucket belonging to the group of Apparatuses exchanging DICOM images. The Transfer Server cuts the Series Container in chunks of SMB before transferring them to the Series Container. Once all chunks are uploaded, the Series Container will be consolidated in the Series Bucket.   7. The Transfer Server creates and stores the Info File in the Series Bucket.   8. The Transfer Server will create an Order file to instruct the remote Apparatus(es) that a new Series of images is ready to be downloaded. The Order file will be dropped in all Order Buckets belonging to the remote Apparatus(es) based on the TA defined by the Called AET provided by the source modality. The prefix of the Order file is “download.” followed by the series UID of the set of images.   9. The remote Apparatuses are scanning their own Order Buckets to check for the presence of a “download.” Order file. If one is found, the remote Apparatus will download the Series Container, also in chunks of SMB, from the Series Bucket based on the series UID contained in the Order file. If for any reason, the transfer of a chunk fails, the download of the next chunks in the sequence will start again to avoid the download of the entire Series Container again.   10. Once downloaded, an integrity check of the Series Container will be performed before be decrypted and decompressed by the Transfer Server of the remote Apparatus. Then, it will send the images, one by one, to the DICOM Server of the remote Apparatus.   11. Depending on the Called AET provided by the Info file associated to the Series Container and if forwarding rules have been defined in the DICOM Server, it will send the images to the Called AET.   12. Once all images stored locally on the remote Apparatus and optionally forwarded to a different AET, the Transfer Server will rename the prefix of the Order file from “download.” to “ok.” to instruct the source Apparatus that the transfer is completed.       
 
         [0122]    Encryption of the Apparatus Hard Drive 
         [0123]    The DICOM images of an Apparatus are stored on an encrypted partition of the local hard drive. This partition is encrypted preferably using “Truecrypt”, an open-source disk encryption software for Windows, Mac OS X and Linux. The encryption method requires a private key that is stored on the USB stick of the Apparatus. When booting an Apparatus, the private key is required to access the encrypted partition and de facto the USB key must be plugged. The private key used to encrypt the partition is encrypted using another secret key, the Master Key, that only one person in the Apparatus development team knows. A copy of that Master Key is kept at an escrow. To avoid any access to that Master Key on the Apparatus itself, that key is stored in a compiled batch program responsible to mount the encrypted partition. This batch program can only be compiled by the sole person—having the Master Key. 
         [0124]    If an Apparatus is defective and needs to be sent back to the manufacturer or repair facility, it should be returned without the USB stick. As result, nobody will be able to mount the encrypted partition and access the DICOM images. 
         [0125]    a. Encryption and Compression of the Series Containers 
         [0126]    Series of DICOM images are stored in compressed and encrypted containers prior to be uploaded to a FTPS/SFTP or Amazon S3 server. As result, no single person in the Data Center hosting the FTPS/SFTP server or at Amazon facilities will have access to the DICOM images stored in the encrypted containers. 
         [0127]    The compression algorithm used by the Transfer module of the Apparatus is ZIP. ZIP compression is very efficient on DICOM images. Compression ratios range from 6:1 (e.g. mammography, CT, MRI) down to 2:1 (e.g. thorax). ZIP compression guarantees a 100% lossless compression. 
         [0128]    The compression method includes an intrinsic data integrity mechanism. A CRC checksum is calculated when compressing the container. When decompressing the container a checksum is calculated and compared to the original one. If they do not match, the container is corrupted and an error will be reported. The container may be downloaded again. 
         [0129]    a. Encryption of Access Keys 
         [0130]    When using a FTPS server, a user name and password must be provided. A SFTP server requires a public key and secret key while Amazon 53, needs an “AccessKey” and “SecretKey” (Amazon terminology). All those parameters are stored in configuration files on the Apparatus and a backup copy is also stored on the USB stick. As those parameters are sensitive, they are all encrypted using the Master Key using the compiled batch program described above. 
         [0131]    Containers are encrypted using the AES 256 bits which ensures the highest level of data protection. The secret key used to encrypt a container is generated randomly and stored in the Apparatus database. Before uploading the container to FTPS/SFTP/53 to transfer it to a remote Apparatus, the random password is provided to it using its Order Bucket. The random secret password is also encrypted using the Master Key. 
         [0132]    a. Apparatus Local Data Replication 
         [0133]    The Apparatus is equipped with only one internal large capacity hard drive. Because of the very small size of the Apparatus, there is no extra physical space to put a second hard drive (e.g. building a RAID 1 mirror). The single Apparatus hard drive contains the medical images (on an encrypted dedicated partition. De facto, they are a critical data. Its content can be replicated to a secondary storage device like a NAS system (CIFS/NFS Network Attached Storage or iSCSI) or local external hard drive(s) via USB (Direct Attached Storage—DAS). Most of those NAS/DAS systems have an embedded RAID controller securing the files replicated across several disks. If one hard drive (or even two when using RAID 6) fails, no data will be lost. 
         [0134]    Each time an Apparatus gets a file (i.e. a medical image), it is not only stored on its internal hard drive but also replicated to the NAS/DAS. As result, the Apparatus always retains two copies of each image. The database stores the path of all series of images to the local hard drive and the copy to the secondary storage. 
         [0135]    When the local hard drive is full, oldest images will automatically be deleted (FIFO—First In First Out). In that case, only one copy will remain available from the NAS. The Apparatus keeps access to all images restored either from the local hard drive or from the NAS. When the NAS system is full, an additional unit can be added. Only the path to the new added NAS needs to be updated in the configuration of the Apparatus. 
         [0136]    In case of a crash of the Apparatus hard drive, a swap unit will be provided. The database can be restored from the original USB stick. This database contains the list of the images that were stored on the hard disk before crashing arid also the path to the copy of those files on the secondary storage device. As result, it is possible to recover the original, content of the local hard drive. 
         [0137]    a. Apparatus Off-Site Data Replication 
         [0138]    The DICOM images exchanged between Apparatuses are transiting through external Series Bucket (FTPS/SFTP or Amazon S3 servers). The Series of images are stored and transferred using compressed and encrypted container (one container per series of images). To reduce the storage space on the FTPS server, we keep those container as it without uncompressing them. In case of a disaster causing the loss of all the data locally (i.e. where the Apparatus is located), the ZIP containers can be downloaded from the remote FTPS/SFTP/S3 server and be uncompressed by a new Apparatus locally. 
         [0139]    The transfer of those containers is secured using SSL encryption. 
         [0140]    a. Advanced Routing of DICOM Images 
         [0141]    An Apparatus can automatically forward the received images to an other modality like a PACS or a Diagnostic Workstation. Automated Forwarding rules can be defined based on the Called AET and the TA (Transfer Association). 
         [0142]    Received images can be also be handled by the embedded DICOM Router. Based on different criteria or combination of criteria (Calling AET, Called AET, Tag presence/value), images can be modified (Transfer Syntax, Tag value, . . . ) and/or forwarded to a defined AET. 
         [0143]    a. Patient Data Reconciliation 
         [0144]    The Apparatus includes a reconciliation process avoiding any inconsistency between the metadata of the transferred images (e.g. the patient ID) and the metadata of images stored in a PACS (Picture Archiving and Communication System) of the target hospital. The reconciliation process is managed either by the embedded HL-7 server interacting with a RIS (Radiology Information System) or HIS (Hospital Information System) querying patient information based on his name, birth date and sex. The DICOM Server can also perform a C-Find to query the PACS based on the same information. If the Patient information returned by the RIS, HIS or PACS is matching exactly with the one store in the DICOM images, they will automatically be forwarded to the defined AET (e.g. a PACS). If not, the tags that are not matching (e.g. the Patient ID is different), will be updated accordingly. The reconciliation process may require human intervention if no relationship can be made between the data contained in the images and the data queried from the RIS/HIS/PACS. 
         [0145]    a. Controlled Publishing of Medical Images to a WEB Portal 
         [0146]    The referring physician and sometimes the patients (this depends on the country) must have access to their medical images preferably using a WEB portal. In that case, it is obviously mandatory that patient have only access to their own images and the referring physicians to the images belonging to their own patients. 
         [0147]    Our WEB portal is composed by two modules: the first is used to display the images and the second one is managing the access rights. 
         [0148]    Our WEB portal is based on a Windows 2008 or Linux Server either hosted by Amazon (EC2 virtual server platform) or a Data Center. It runs ApacheTomcat as WEB server and any WADO compatible DICOM Web-based viewer (WEB application to display medical images in a WEB browser and having some basic tools like zooming, windowing and linear measurements). 
         [0149]    DICOM images are rendered by the WADO module and sent as JPEG/PNG files to the client&#39;s WEB browser. Every time a. new change is requested like zooming or change the windowing, the DICOM images will be rendered again and its JPEG/PNG representation will be sent back to the WEB client. This process makes the WEB portal extremely reactive and fast, even with slow Internet connections. 
         [0150]    Reference is made to  FIG. 8  for illustrative purposes. 
         [0151]    Access right management and Patient information protection are managed by two modules and technologies. First, the transfer of the data (i.e. the medical images) is encrypted using SSL (HTTPS) to avoid third parties having access to Patient information. Second, a dedicated module manages access rights depending on the profile of the user (a radiologist has access to all his images, a referring physician is limited to the images of his patients and patients have only access to their own images). While this access control is fully automated, it is possible to assign additional access right manually to extra users like specialists for a second opinion. 
         [0152]    The names of the referring physician and patient are stored in the DICOM images as metadata. This information lets the WEB portal automatically assign access rights. In some cases, the name of either the physician or the patient is missing or is not correctly spelled. In that particular case, access rights must be managed manually. 
         [0153]    Most of the large hospitals and modern clinics own a RIS (Radiology Information System) or a HIS (Hospital Information System) that are management applications to plan examinations including radiology. The name of a referring physician or a patient can also be retrieved from the RIS or the HIS using the embedded HL-7 server. 
         [0154]    Web Portal Workflow 
         [0155]    The Apparatus compresses medical images by series (i.e. images generated by one modality and belonging to one patient) in a Series container before sending it to Amazon S3 where they are securely stored. The WEB server used for our portal is hosted by a Windows 2008/Linux Amazon EC2 virtual server having a storage capacity of 100 GB. We have developed a gateway to transfer images from the S3 storage pool to the EC2 web server. The gateway module scans the S3 and download then newly added ZIP containers that have been uploaded by an Apparatus. The gateway decompresses the images and sends them to a genuine DICOM server also hosted on the virtual WEB server. The images are the stored on the storage space of that server. When the disk space is almost full, the oldest images are automatically deleted to leave space for the newly added images (FIFO). The deleted images are still available from the S3 storage pool. As result, when a user is querying the WEB portal, he will have two options: if the images are still available on the EC2 server, they will be instantly shown. If the images are only available on the S3 platform, our gateway module will get the instruction to download those images from the 53 storage pool, decompress and store them on the EC2 server. 
         [0156]    When images are available for a referring physician, he will be notified by email. This email contains a WEB link pointing directly to the newly added series of images belonging to that referring physician. Obviously, all users getting a link to a series of images must log in using their user name and password that have been provided beforehand by the clinic, radiologist or hospital. 
         [0157]    Reference is made to  FIG. 8  for illustrative purposes. 
         [0158]    a. Automated Backup of the Database and the Configuration 
         [0159]    According to a preferred embodiment, the Apparatus is equipped with an external, detachable data storage device, such as e.g. a USB key. This device is used to backup the configuration files and the database. 
         [0160]    If the Apparatus is using Amazon 53 or a FTPS/SFTP server and/or a secondary storage device, an extra copy of both configuration and database will be stored on those storage platforms. 
         [0161]    a. Disaster Recovery—Recovery of the Database and Parameters 
         [0162]    The maintenance and repair procedures of the Apparatus are straightforward. In case of a failure (e.g. the hard drive is defective), a new Apparatus is sent to the end-user. He only needs to remove the external detachable data storage device such as e.g. the USS key from the defective Apparatus and insert it in the new one. When powering on the new Apparatus, it will automatically recover its configuration and database. If all images stored in an Apparatus are replicated to a local secondary storage, which is highly recommended, the data stored on the defective hard drive will also automatically be restored to the new Apparatus thanks to the database keeping track of the path of all files initially stored on the internal hard drive but having been replicated to the secondary storage. 
         [0163]    In case of a disaster (fire, earthquake, . . . }, the Apparatus and the NAS system(s) being destroyed, it is still possible to recover all the data thanks to the copy of the images, configuration and database stored on Amazon 53 or a FTPS/SFTP server.