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
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?
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