Best practices for connecting medical devices to the cloud

1. Guy Vinograd, CEO
Best Practices for
Connecting Medical Devices to the Cloud

2. Users and Components of a Typical Medical IoT Solution
Patient
Factory worker
Technician
Clinical Manager
System Admin
Logistics
3rd
Party Saas
CRM, ERP,
EMR, EDC, ..
HMO
Physician
Medical
Device
Sensor
Core Backend
Platform

3. IoT Design Dilemmas

4.  Cloud – the ideal
◦ Protects IP
◦ Data privacy (raw signal = less risk)
◦ Lower TCO
◦ High availability/durability
 Gateway ("fog") – the reality
◦ Offline
◦ True real time
◦ Data BW is large
#1 – Where is the Logic & Data?

5. #2 – Where is my IoT Gateway
 Cost, Energy, Ease of use, Control
 Human-sensor proximity?
 SLA for real-time response? Regulation?
 # of sensors per location?

6. #3 – Gateway & Cloud RF Connectivity
 Availability
 Monthly cost
 Complexity - who is the user?
 Location - business? IT friendliness

7.  Questions
◦ Message size/velocity
◦ NW environment
◦ Ability of device processing
 Encryption
 Too much?
◦ Value of each message? Value of the action taken
◦ Temporal stream compression. 1/40
◦ Offline training of ML - identify the right metrics. Training period
#4 – What are the Messages?

8. #5 – What is the Protocol?

9.  Unexpected - will surely happen
◦ Thing 2 Cloud
◦ Users
 Expected
◦ Sub-thing 2 Thing 2 Cloud
◦ Factory 2 Cloud
#6 – Mitigating Offline Scenarios
Consumer
Factory worker
Technician
Support
System Admin
Logistics
3rd
Party Saas
CRM, ERP,
EMR, ..
Distributor
Advisor
Thing
Sub
Thing
Core Backend
Platform

10.  Minimum Viable Product
 Not too thin
 HIPAA/GDPR
 Logs / Analytics
 Firmware updates
#7 – What’s in v1.0?

11. The Shortest Way to Build an
IoT Solution

12. The Goal
REST
IoMT Cloud
Gateway
3rd SaaS
CRM, ERP, EMR, …

13. DIY? The Long, Expensive Way
Cloud-Mobile-WebOur Device
Internet product analysisPhysicians
Web-scale SW architectureBiomed engineering
Mobile, web apps devClinicians
Cloud backend devMechanics
Cloud devops - scalability, HA, ..Hydraulics
IoT connectivity, device mgmt, FW updates, ..Electronics
Billing and “As a service” modelsAlgorithms
EHR/EMR integrationsIndustrial design
Cloud HIPAA, GDPR, ISORegulation

14. IoT Platforms – Leveraging the Common Denominator
 User management – patient-physician-caregiver-HMO
 Real time analytics – data analysis, rules, actions,
notifications
 Medical protocol management – adherence,
compliance, notifications
 Device management – inventory & certificates, firmware
updates, personalized configuration
 Security and privacy - HIPAA and GDPR, auditing
 Million scale

15. Platforms? Ownable or 3rd Party?
REST
Gateway
Medical Device
Platform

16. For Manufacturers Ownable Beats 3rd Party
 No Locking – Have the code. No gambling
 Transparent security
◦ Devices may need security updates for 2 decades!!
 Cost performance – Pay tenth OPEX
 No data sharing and deployment limits
 No IP issues – Own it all
 No Technology limits – Lead your roadmap, algorithms, UI and API

17. TBBTM – An Ownable Platform by Softimize
3rd SaaS
CRM, ERP, EMR, …
MQTT, HTTP REST
Web Socket
HIPAA/GDPR Security
Device & User Analytics
Integrations
Monetization
Access Control – laaS, SaaS
Audit
Billing & Payment
Licensing – per Tenant. Trial license
Real-time | Batch | Compliance
Smart Rule Engine | Workflow
Devices | Registry | FOTA | Cfg
Users | RBAC | Tenant isolation
Notifications – Apps, Emails
REST API, SDKs
Device Simulator
Saves $$$ at Scale
Cloud Cost and Bandwidth optimizations
Native while Multi Cloud

18. Guy Vinograd, CEO
guy@softimize.co
The Quickest Path to Your Own Medical Device Cloud
Thing Building Blocks