![](bg4.png)
architecture because it stores residual information
about all devices (i.e. AETitles) and corresponding
services supported. Moreover, it has accounts from
routers and a list of cloud providers that routers can
use to store temporary information. It needs to be
always available over the Internet because routers
need to write information in the Bridge to provide
communications. It can be deployed in several
places like, for instance, in a private cloud detained
by a medical institution or a public cloud provider.
Due to privacy concerns, we strongly recommend
deployment of this component in a trustable provider
or in-house (i.e. medical institutions).
The management of the diverse Routers is
supported by a temporary information system
located on the Bridge and it is accessible through a
RESTful web service. Only registered users have
access to the DICOM WAN Network. Moreover, the
Bridge is a very important component because it
stores the session key used to cipher DICOM
messages of an association. Thus, it should be
located in a trustable location, to safeguard the
architecture.
The Bridge is considered the main component of
the architecture because it performs the management
of the relay service. It only contains a reduced
amount of information, and during the dataflow it
just store a minimum amount of data, i.e., the
confidential shared key. The remaining information
is transmitted through the cloud in a ciphered mode.
It is used two different cloud services: blobstore and
signalling. The Cloud providers supply, on the one
hand, temporary storage of blinded data (encrypted
DICOM objects/commands) and, on the other hand,
a signalling service that allows establishing
communication in real time between the routers.
4 CONCLUSIONS
The presented solution allows DICOM standard
communication between medical devices located in
distinct institutions. The proposed architecture
allows creating a federated DICOM network across
distinct medical institutions, with a unique view of
all resources.
Our DICOM relay service does not need
complex setups to start communicating with external
repositories, allowing interoperability with any the
DICOM standard device.
With this system, radiologists can work
remotely, in the same way that they do in the
hospital, without changing their methods.
REFERENCES
Dicom-P7 2009. Digital Imaging and Communications in
Medicine (DICOM), Part 7: Message Exchange.
National Electrical Manufacturers Association.
Dropbox. 2011. Dropbox Service [Online]. Available:
www.dropbox.com [Accessed June 2011].
Google. 2011a. Gmail [Online]. Available: www.gmail.
com [Accessed June 2011].
Google. 2011b. Google App Engine (GAE) [Online].
Available: http://code.google.com/appengine/
[Accessed June 2011].
Hajjat, M., Sun, X., Sung, Y.-W. E., Maltz, D., Rao, S.,
Sripanidkulchai, K. and Tawarmalani, M. 2010.
Cloudward bound: planning for beneficial migration
of enterprise applications to the cloud. SIGCOMM
Comput. Commun. Rev., 40, 243-254.
Huang, H. K. 2004. PACS and imaging informatics: Basic
Principles and Applications.
Microsoft. Windows Azure Platform [Online]. Available:
www.microsoft.com/windowsazure/ [Accessed June
2011].
Microsoft. 2011. Microsoft HealthVault [Online].
Available: www.healthvault.com [Accessed May
2011].
Oliveira, D., Bai„O, F. A. and Mattoso, M. 2010. Towards
a Taxonomy for Cloud Computing from an e-Science
Perspective. Cloud Computing, 47-62.
Rimal, B. and Choi, E. A Conceptual Approach for
Taxonomical Spectrum of Cloud Computing.
Ubiquitous Information Technologies & Applications,
2009. ICUT '09. - Proceedings of the 4th International
Conference 2010 Fukuoka. IEEE, 1-6.
Rosenthal, A., Mork, P., Li, M. H., Stanford, J., Koester,
D. and Reynolds, P. 2010. Cloud computing: a new
business paradigm for biomedical information sharing.
J Biomed Inform, 43, 342-53.
S3, A. 2011. Amazon Simple Storage Service [Online].
Available: https://s3.amazonaws.com/ [Accessed June
2011].
Vaquero, L. M., Rodero-Merino, L., Caceres, J. &
Lindner, M. 2008. A break in the clouds: towards a
cloud definition. ACM SIGCOMM Computer
Communication Review, 39, 50-55.
HEALTHINF 2012 - International Conference on Health Informatics
412