WEARABLES & IOT CONNECTORS
Supported Platforms & Provider Integrations
4 of 7Connect leading wearable and IoT platforms using their native frameworks, provider APIs and standard protocols, then normalize incoming data through Mediloop and MSIS for consistent downstream use.
Provider CatalogAuthenticationSupported DataSynchronizationRate LimitsNormalizationImplementation Examples
Provider Catalog
Apple HealthKit
On-device frameworkNative iOS health-data framework
Activity
heart rate
sleep
workouts
Android Health Connect
On-device frameworkAndroid health-data framework
Activity
sleep
vitals
body metrics and cycles
Garmin Connect
Provider cloudFitness and outdoor activity data
Activity
HR
sleep
training
Fitbit
Provider cloudHealth, fitness and wellness data
Activity
sleep
HR
SpO₂
Oura
Provider cloudSleep, readiness and recovery
Sleep stages
HRV
temperature
readiness and activity
Withings
Provider cloud / platformConnected home health devices
Weight
BP
sleep
activity and temperature
Dexcom
Provider/device programContinuous glucose monitoring
Glucose readings
trends and alerts
Abbott FreeStyle Libre
Provider/device programGlucose monitoring
Glucose readings
trends
time-in-range and alerts
Samsung Health
Platform/provider integrationActivity, sleep and wellness
Activity
sleep
heart rate and body metrics
Other Platforms
API / SDK / gatewayCustom / additional providers
BLE devices
provider APIs
home gateways and enterprise integrations
Integration Details
| Platform | Integration model | Authorization | Historical data | Events / sync | Production notes |
|---|---|---|---|---|---|
| Apple HealthKit | On-device framework | User-granted app permissions | Subject to device/app data available locally | App/background synchronization | No generic OAuth/REST cloud contract; use Apple platform APIs |
| Android Health Connect | On-device framework | Android runtime/user permissions | Subject to platform data availability | App/background synchronization | Use Health Connect APIs and permission model |
| Garmin Connect | Provider cloud | Provider program + OAuth flow | Provider-dependent | API/webhook/provider sync | Access and limits depend on Garmin program |
| Fitbit | Provider cloud | OAuth 2.x | Provider-dependent | API/subscriptions where available | Respect scopes, quota and provider terms |
| Oura | Provider cloud | OAuth 2.x | Provider-dependent | API/webhook capabilities vary by program/version | Verify current provider contract |
| Withings | Provider cloud | OAuth 2.x | Provider-dependent | API/notifications where available | Verify medical-device and regional context |
Authentication & Permissions
Use native app permissions for HealthKit / Health Connect rather than treating them as generic REST services.
Use provider OAuth or partner authentication exactly as required by each manufacturer program.
Request minimum necessary scopes and explain why data is requested.
Store provider tokens securely and implement refresh/revocation lifecycle.
Never reuse patient authorization across providers or tenants.
Keep provider connection state visible and auditable.
Supported Data
| Data domain | Examples | FHIR target |
|---|---|---|
| Activity | Steps, distance, active energy, workouts | Observation |
| Vitals | Heart rate, SpO₂, BP, temperature, respiratory rate | Observation |
| Sleep | Duration, stages, sleep score | Observation / component model |
| Metabolic | Glucose, time-in-range and trends | Observation |
| Body metrics | Weight, BMI, body composition | Observation |
| Device metadata | Model, manufacturer, connection/source | Device / DeviceMetric / Provenance |
Synchronization
Incremental sync
Track provider cursors/timestamps and ingest only new/changed records.
Event-driven sync
Use provider events/webhooks where supported, then retrieve authoritative data if required.
Historical backfill
Import historical windows deliberately with rate-limit and deduplication controls.
Offline/mobile sync
Queue local data and upload safely when connectivity returns.
Data Normalization
Preserve provider-native identifiers, original codes, values and units.
Map measurements to FHIR Observation/Device structures where appropriate.
Use LOINC / SNOMED CT and UCUM through MSIS when mappings are validated.
Attach provider/device provenance and mapping version.
Deduplicate overlapping data coming from device, mobile platform and provider cloud.
Do not automatically treat consumer measurements as clinically equivalent to regulated data.
Developer Integration Surface
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| HealthKit | HKHealthStore queries / samples / permissions | iOS health-data integration | External platform API |
| Health Connect | Android records / permissions / changes | Android health-data integration | External platform API |
| Provider cloud APIs | Provider-specific OAuth + REST/webhooks | Garmin, Fitbit, Oura, Withings, CGM and similar | External provider API |
| FHIR | Observation / Device / DeviceMetric / Provenance | Normalized Mediloop/EHR data exchange | FHIR surface |
| Mediloop provider adapter SDK | OAuth handlers, sync cursors, mapping, webhook handlers | Reusable provider connectors | SDK contract evolving |
| Mediloop Wearables API | Provider connections / observations façade | Simplified app integration | Planned contract |
Implementation Example
typescriptCopy
// Illustrative adapter example — provider contract must be verified
const connection = await wearables.providers.authorize({
provider: 'oura',
redirectUri: 'https://app.example.com/callback',
scopes: ['sleep:read', 'activity:read'],
});
const batch = await wearables.providers.sync({
connectionId: connection.id,
since: lastCursor,
});
await wearables.ingest.normalize(batch, {
patientId,
preserveSource: true,
});Rate Limits & Provider Constraints
Do not hard-code quotas from screenshots or old provider documentation; read current provider limits during connector implementation.
Use caching, cursors and incremental sync to reduce unnecessary calls.
Back off on 429/temporary errors and honor Retry-After where provided.
Separate provider API quotas from Mediloop tenant/application limits.
Track API version/deprecation dates and provider certification/program requirements.
Troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| No new data | Permissions revoked, sync cursor stale or provider delay | Check connection status, scopes, cursors and provider health |
| Duplicates | Overlapping mobile/cloud sources or replayed webhook | Deduplicate on provider/source identifiers and provenance |
| Wrong units | Provider-native unit not normalized | Preserve source unit and apply validated UCUM mapping |
| Token failures | Expired/revoked provider authorization | Refresh or re-authorize according to provider flow |
| Gaps in time series | Device offline, app background limits or provider latency | Expose gaps; do not fabricate missing measurements |
Next Steps
1
Review data requirements
Choose provider/device based on actual measurements and intended use
2
Implement authorization
Native permissions or provider-specific OAuth/program onboarding
3
Normalize
FHIR/MSIS mapping, units, provenance and deduplication
4
Test
Real device data, historical sync, retries and revocation
5
Operate
Monitor provider changes, quotas and data completeness