IoT Sanitario: Monitor LTE-M, Vacuna NB-IoT
· 7 min read · Case Studies
Parche cardiaco 30s: LTE-M. Logger vacuna: NB-IoT. HIPAA ambos.
La IoT sanitaria se divide en dos dominios de conectividad con requisitos opuestos. Dispositivos portados por el paciente —monitores cardiacos, sensores de glucosa, detectores de caidas— se mueven con el paciente, necesitan alertas casi en tiempo real y se conectan via LTE-M para movilidad y latencia inferior a 100ms.
Dispositivos Portados por el Paciente —Por Que LTE-M
Un parche de telemetria cardiaca usado por un paciente dado de alta transmite datos ECG cada 30 segundos. Si se detecta un evento de fibrilacion auricular, la alerta debe llegar al cardiologo en menos de 100ms —antes de que el paciente sienta sintomas. Esto requiere LTE-M: handover de movilidad completo, latencia de 50-150ms y contexto PDP siempre activo.
Preguntas frecuentes
LTE-M or NB-IoT for a wearable medical device?
LTE-M. Patient-worn devices move, need sub-150ms alert latency, and may require firmware updates over the air. NB-IoT does not support mobility handover and has latency of 1,500-10,000ms — unacceptable for cardiac or glucose alerts. LTE-M also supports VoLTE for devices with emergency call capability.
Is there such a thing as a HIPAA-compliant SIM card?
No. A SIM supports technical safeguards (encryption, authentication, private APN) that HIPAA requires. Compliance is in the architecture — how data flows, where it is encrypted, who has access — not in any single component. Specify private APN, TLS/DTLS encryption, and SIM-based device authentication. Do not accept "HIPAA-compliant SIM" as a substitute for architectural compliance.
Can one SIM SKU serve both patient monitors and cold chain loggers?
Technically yes, but it will be suboptimal for one domain. LTE-M SIMs work for cold chain but waste power on mobility features the logger does not need. NB-IoT SIMs work for wearables but cannot support mobility handover. Procure separate SIM SKUs per device class — manage both from a single CMP.