Overview
1 of 7Connect consumer wearables, medical devices and IoT platforms to Mediloop. Collect, normalize and integrate real-world data into the patient record using open standards while preserving provenance, data quality and intended-use context.
iOS on-device health-data framework; user-authorized reads/writes.
Android on-device health-data framework and normalized record types.
Provider-cloud integrations for activity, sleep, heart rate and recovery data.
Glucose and CGM integrations subject to provider programs and medical-device context.
Weight, blood pressure, sleep and connected health measurements.
BLE/GATT, vendor APIs, gateways, MQTT and Connector SDK patterns.
Heart rate, blood pressure, SpO₂, respiratory rate and temperature.
Steps, distance, calories, workouts and active minutes.
Sleep stages, duration, HRV, readiness and recovery indicators.
Continuous glucose readings, trends, alerts and metabolic measurements.
Weight, BMI, body composition and other longitudinal measurements.
Device-specific signals, air quality, ambient data and sensor context.
| FHIR resource | Purpose | Typical wearable / IoT use |
|---|---|---|
| Device | Device identity, manufacturer, type and ownership | Register and reference the source device |
| DeviceMetric | Measurement capability / metric metadata | Describe device-specific measurement capabilities |
| Observation | Individual and time-series clinical/wellness measurements | Heart rate, glucose, BP, SpO₂, activity and other readings |
| Provenance | Source and transformation traceability | Preserve provider/device/source and normalization lineage |
| Patient / Encounter / CarePlan | Clinical context | Link measurements to patient, RPM program and care workflow |
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| FHIR | Device, DeviceMetric, Observation, Provenance | Standards-based storage/query and EHR interoperability | FHIR surface |
| BLE / GATT | Services, characteristics, notifications | Direct/local device connectivity | Protocol surface |
| HealthKit / Health Connect | Native on-device APIs | Mobile-platform health-data integration | External platform API |
| Provider cloud APIs | OAuth/API/webhook per provider | Garmin, Fitbit, Oura, Withings, CGM and other vendor integrations | External provider API |
| MQTT / HTTPS / Webhooks | Publish/subscribe or event callbacks | Gateways, IoT sensors and real-time provider events | Protocol/event surface |
| Mediloop Device API / SDK | Register device, ingest measurements, subscribe to events | Simplified Mediloop-native developer surface | Planned contract |
Standards-based FHIR and open integration patterns.
Continuous or periodic data can feed trends and alerts.
MSIS normalizes codes, units and provenance without discarding source values.
Consent, least privilege, audit and data minimization remain explicit.
Connect measurements to patient records, dashboards and care workflows.
Add new providers and device categories without rebuilding the whole application.
Direct BLE, mobile platform, provider cloud, gateway or clinical/local network.
Identify measurements, terminology, units, provenance and clinical context.
Consent, scopes, privacy, medical-device context and retention.
Use standards or the appropriate connector/SDK surface and representative device data.