2. What is MediCloud?
• MediCloud is a cloud computing platform
• MediCloud is the “internet of medical entities”
• What are the “entities”:
– Users: patients, doctors, carers etc
– Devices:
• Terminals: PC, smartphones, tablets
• Sensors: bio medical sensors
– Providers: services for health care
• Tele/remote consultation
• Local consultation
• Medication compliance
copyright Robomotic ltd
3. What is cloud computing?
NIST definition of cloud computing
Cloud computing is a model for enabling ubiquitous, convenient, on
demand network access to a shared pool of configurable
computing resources (e.g., networks, servers, storage,
applications, and services) that can be rapidly provisioned and
released with minimal management effort or service provider
interaction.
This cloud model promotes availability and is composed of five
essential characteristics, three service models, and four
deployment models.
copyright Robomotic ltd
4. What are good examples?
• Pachube: was the first platform for the internet of things
• ThingsSpeak: on the Pachube success but with a better XML
description
• LogMeIn: a syn solution who acquired Pachube
• Funanbol: a sync solution data storage
• Medical Care platforms are developed by large corporations like
AMD global, Philips, Tunstall however they lack the vision of a
global connected care by focusing on short term benefits
• Continua Alliance is a good consortium but is only attempting to
enforce the market position by developing proprietary standards
and not platforms
copyright Robomotic ltd
5. Why MediCloud?
• MediCloud obeys the principle of continuous care:
– Spatial: ability to access data anywhere
– Time: ability to access data anytime
• Ubiquity:
– Any device can be used to read and write data
– Any user must be able to understand and exchange data
• Exchange:
– Exchange data between entities is transparent
• Access:
– Users role and permissions
• Security:
– Data is encrypted
copyright Robomotic ltd
6. What are the benefits?
• Doctors:
– Diagnosis improvements via data mining on patient
– Remote consultation with multiple sensor streams
• Organizations:
– Continuous care for the patient
– Data integrity, security and access
• Finance:
– Bill management: several granularity layers for services
– Tracking of resources:
• device utilisation
• staff allocation
• device/users location
– Optimization: who needs what?
copyright Robomotic ltd
7. API Clients/Servers
• Client API via Thrife:
– Android >= 4.1
– Python
– Javascript
– PHP
– Java
• Server plugins:
– XMPP OpenFire
• Device supported:
– Supports 36 commercially available bluetooth devices
copyright Robomotic ltd
8. A glimpse of the architecture
Event based system based on publish subscribe model
Clients can generate and access data on multiple platforms
copyright Robomotic ltd
9. Patient and medical care
• Patient record
• Sensor network
• Remote care
• Auto diagnosis
copyright Robomotic ltd
10. Want more?
• Remote consultation with multiple sensor streams:
– Video and Audio
– Medical sensors
• Interface to hospitals and organizations:
– EHR via Restful interface
• Device and sensor descriptions:
– XML description for Plug’N’Play
• Support for Continua Alliance?
– Not yet!
copyright Robomotic ltd
12. Team
• The platform was designed as a team effort with the following
people:
• Stefano Norcia : Solution Architect and Developer
• Products developed:
– Jooid: http://www.joooid.com/
– Semantic Web solutions
• Dr. Paolo Di Prodi: Software and Hardware Developer
– Embedded sensors
– Android apps
Confidential, copyright Robomotic ltd
