WearOpenWearable data accountability

Independent accountability campaign · physician-led · evidence-linked

Your body made the data. The platform should not control it.

Wearable companies can measure us around the clock—then delay, limit, or gate access to the results. That can stop patients, clinicians, caregivers, and independent builders from using the data when it matters. WearOpen exposes those barriers, ranks them publicly, and pushes every manufacturer to open its platform.

No platform currently earns an Open rating.Ten leading platforms. Not one meets the standard for complete, user-directed access without added delay. This should be the baseline—not a premium feature.

10 platforms · 6 criteria · timing reviewed August 25, 2026

The 10-second accountability check

Where your data gets stopped.

Can it reach another app, a person or doctor, and an independently built tool? Read across each row for the answer.

Noneare fully open
Open and direct Delayed, conditional, or sync-dependent Approval or commercial gate No documented route
PlatformAnother appPerson or doctorBuild with itMain wait
Apple WatchApple Health + HealthKit
79
Another appDirectUsually seconds–minutes*
Person or doctorMixedPerson: minutes* · provider ≈24 h
Build with itSelf-serve$99/year to publish
Main waitApps/person: minutes* · provider ≈24 h
Google HealthFitbit + Pixel Watch
78
Another appAvailableUsually minutes after sync*
Person or doctorNo built-in viewA separate app is required
Build with itGated at scale100-user cap before review
Main waitUsually minutes* · hours if offline
Oura RingOura + Cloud API
75
Another appAvailableUsually a few minutes after sync*
Person or doctorReport onlyNot a live care view
Build with itApproval requiredAfter 10 users
Main waitUsually a few minutes after sync*
PolarPolar Flow + AccessLink
72
Another appAvailableWaits for watch upload
Person or doctorCoach viewNot a medical dashboard
Build with itSelf-serveFree public API
Main wait≈30–60 min
Samsung HealthGalaxy Watch + Galaxy Ring
67
Another appHealth ConnectUsually minutes after watch sync*
Person or doctorNo live viewNo follower or doctor route
Build with itPartial accessHealth Connect open · SDK gated
Main waitUsually minutes* · hours if app sleeps
WHOOPWHOOP 5.0 + Developer Platform
63
Another appAvailableUsually minutes after processing*
Person or doctorNo live viewNo follower or doctor route
Build with itApproval requiredAfter 10 users
Main waitUsually minutes after processing*
DexcomG7 + Clarity + Follow
61
Another appDelayedHealth apps: ≈3 h
Person or doctorFast follower≈5 min · clinic ≈3 h
Build with itLicensedApproval + commercial deal
Main waitFollower ≈5 min · other routes ≈3 h
GarminGarmin Connect + Health API
53
Another appAvailableManual sync: usually minutes*
Person or doctorNo native viewAn integration is required
Build with itCommercialApproval + undisclosed fee
Main waitManual: minutes* · auto: hours possible
FreeStyle LibreLibreView + LibreLinkUp
53
Another appNo broad routeNo Apple or Google health export
Person or doctorFast follower≈1 min · clinic usually minutes*
Build with itNo public APIAbbott apps and portals only
Main waitFollower ≈1 min · clinic usually minutes*
LingoAbbott consumer CGM
29
Another appDelayedApple / Google health: exactly 3 h
Person or doctorNo continuous viewNo follower or doctor route
Build with itNo public APISpreadsheet export only
Main waitExactly 3 h

The campaign

Open the platforms. Give people control.

Not eventually. Not through screenshots. Not only for approved corporate partners. People should be able to direct the data their bodies generate—to a clinician, caregiver, app, or tool they choose—completely and without an added holding delay.

01

Send it now.

Make new data available to authorized recipients as soon as the platform receives it.

02

Let the user choose.

People should be able to grant and revoke continuous access for a clinician, caregiver, or app.

03

Open the door to builders.

Useful production APIs should be self-serve—not reserved for companies with a private deal.

04

Give the whole record.

Provide complete, machine-readable exports and publish every delay, limit, fee, and omission.

The company built the device. You generated the data. You should decide where it goes.

The accountability scoreboard

Who gives you control—and who holds it back.

This is evidence for change, not a product recommendation. Each row separates what the wearer sees from what reaches an outside app, follower, or clinician. Open it to see the exact route and documentation behind the finding.

1 · Wearer view

How quickly the person sees data on the wearable or in the company’s own app. This is often the fastest clock.

2 · Another app

How quickly data reaches Apple Health, Health Connect, an API, or an independently built app after the wearable sends it onward.

3 · Another person

How quickly a follower, caregiver, or clinician can actually see it. A platform connection alone does not answer this.

Freshness uses clock 2 or 3—never clock 1 alone. Care-team scoring uses the follower or clinician route specifically. A current reading in your own app does not prove that anyone else has received it. Each timing labels without an asterisk are documented manufacturer timings. An asterisk marks a practical range inferred from the documented sync behavior—not a promised service level. Those estimates assume the wearable, phone, and receiving service are connected; offline devices or sleeping apps can extend them.

01Apple WatchApple Health + HealthKitWearer sees itWatch: current · Apple Health varies by metricOthers receive itPerson/app: usually seconds–minutes* · provider: ≈24 h79/100
Who else can get itShare with people + connect apps

Apple Health is the native store. A wearer can authorize outside apps, share selected topics with people, and connect to participating health systems.

How long others waitPerson/app: usually seconds–minutes* · provider: ≈24 h

The shorter range is a practical estimate for an online phone after Apple Health records the measurement, not an Apple guarantee. Participating-provider uploads run about once daily.

Barrier that remains

An individual physician cannot simply turn on Apple’s provider view unless their health system participates, and no broad Samsung Health route is documented.

79/100 · Gated. Useful sharing or APIs exist, but delays, omissions, approvals, or clinical gaps remain.

See every route, score detail, cost, and source

Data lands natively in Apple Health and can be authorized to apps, people, and participating providers.

  • Native health store
  • HealthKit access
  • Person sharing
Biggest friction

Provider sharing uploads approximately every 24 hours. Person and app sharing starts after Apple Health records the measurement, but Apple does not guarantee one maximum across every recipient.

Access modelSelf-serve + institutional gate
Meaningful data route$0 personally · US$99/year to publish

Health-platform routes

Portability · 25 points
Apple HealthNative

Automatic first-party health store.

Google / Health ConnectVia Apple Health

Google Health can import Apple Watch data through Apple Health; this is not a direct Health Connect route.

Samsung HealthNo verified route

No documented outbound Apple Watch-to-Samsung Health pathway was found.

Route-by-route time

Freshness · 10 points
Watch → Apple HealthVaries by measurement

The wearer sees each supported measurement when Apple Watch and iPhone add it to Apple Health. The timing differs by data type.

Apple Health → person / appUsually seconds to minutes after Health updates*

This is a practical range for an online phone and active authorization, not an Apple guarantee. A sleeping receiving app or interrupted connectivity can make the wait longer.

Apple Health → provider≈24 hours

New data is uploaded to Apple’s Health Sharing Cloud approximately once every 24 hours.

Health-platform portability25/25
Care-team parity15/25
Automated access & terms18/20
Complete self-export12/15
End-to-end freshness5/10
Transparency & control4/5

Who can actually use the data?

Wearer
Health data is available in Apple Health, with built-in person sharing and a full XML export.
Clinician
Only participating healthcare organizations can use Apple’s provider view; an individual physician cannot simply switch it on.
Developer
HealthKit is user-authorized and self-serve for app development. Public app distribution generally requires Apple Developer membership.
Cost
Wearer access is included. Apple Developer Program: US$99/year. Provider-integration pricing is not publicly listed.
02Google HealthFitbit + Pixel WatchWearer sees itWatch: current · phone waits for watch syncOthers receive itOutside app: usually minutes* · hours if offline · no follower78/100
Who else can get itConnect apps + build through API

Health Connect can feed another app on the same Android phone after the data arrives there. Google’s server can feed an authorized outside app or dashboard once Google receives the wearable data.

How long others waitOutside app: usually minutes* · hours if offline · no follower

Google sends an immediate webhook once data reaches its API. The practical end-to-end wait is usually minutes while connected, but the earlier watch sync can make it hours.

Barrier that remains

Health Connect is local app-to-app sharing, not person-to-person sharing. A clinic or follower needs a separate application built on top of Google’s tools.

78/100 · Gated. Useful sharing or APIs exist, but delays, omissions, approvals, or clinical gaps remain.

See every route, score detail, cost, and source

Fitbit and Pixel Watch data can feel current to the wearer, while outside access waits for the wearable to send data to the phone or Google’s server and still requires an authorized app.

  • OAuth access
  • Webhooks
  • Broad data types
Biggest friction

Google alerts an outside app after the watch data reaches its server. The unbounded step is the earlier watch-to-phone-or-server sync, and there is no built-in follower or clinician view.

Access modelSelf-serve pilot · security review at scale
Meaningful data route$0 through 100 users

Health-platform routes

Portability · 25 points
Apple HealthImport-led

Google Health can read Apple Health data; outbound Google-to-Apple coverage is not yet documented as a complete route.

Google / Health ConnectNative

Google Health reads and writes supported Health Connect data types.

Samsung HealthVia Health Connect

Supported records can move between Google Health and Samsung Health through Health Connect.

Route-by-route time

Freshness · 10 points
Wearable → wearer’s Google appUsually within minutes while connected*

Google says Fitbit devices sync automatically throughout the day. This practical range assumes the watch and phone are connected; an offline watch can hold data for hours.

Health Connect → another app on the same phoneUsually seconds to minutes after phone sync*

Once the record reaches Health Connect, another authorized app on the same phone can read it without an added company hold. The receiving app may still need to run.

Google server → authorized outside appImmediate alert after server receipt; usually minutes end to end*

Google sends the webhook immediately when data becomes available in its API. The practical end-to-end range is usually minutes while connected, but the earlier wearable sync can make it hours.

Google → follower / clinicianNo built-in route

Another company must build the receiving app or dashboard. Google does not provide one universal follower or clinician view.

Health-platform portability24/25
Care-team parity8/25
Automated access & terms18/20
Complete self-export15/15
End-to-end freshness8/10
Transparency & control5/5

Who can actually use the data?

Wearer
A user can authorize supported Fitbit and Pixel Watch data to outside apps and download account data.
Clinician
There is no universal physician dashboard; a clinic needs an app or integration built on top of the API.
Developer
A Google Cloud project and OAuth client are self-serve. Unverified clients are capped at 100 users; broader use requires a third-party security review.
Cost
No public per-call Health API price is listed. Google charges no review fee, but an independent assessor may charge a negotiated amount.
03Oura RingOura + Cloud APIWearer sees itPhone updates after ring sends dataOthers receive itHealth apps/API: usually a few minutes after sync*75/100
Who else can get itConnect apps + build through API

Supported metrics can move to both major phone health stores, and outside apps can use Oura’s OAuth API and webhooks.

How long others waitHealth apps/API: usually a few minutes after sync*

Oura says the ring-to-app sync can take a few minutes. Outside transfers follow that sync; background restrictions or inactive apps can extend the wait.

Barrier that remains

The native clinician option is a shareable report, not a continuously refreshed view matching the member’s app.

75/100 · Gated. Useful sharing or APIs exist, but delays, omissions, approvals, or clinical gaps remain.

See every route, score detail, cost, and source

Broad health-platform connections plus OAuth and webhooks make authorized reuse unusually practical.

  • Apple Health
  • Health Connect
  • OAuth + webhooks
Biggest friction

Every outside route waits for the ring to sync with the Oura app first. Clinician sharing is mainly a static report rather than a continuously refreshed view.

Access modelFree API · approval after 10 users
Meaningful data routeUS$69.99/year

Health-platform routes

Portability · 25 points
Apple HealthDirect

User-authorized transfer, with only supported metrics sent.

Google / Health ConnectDirect

User-authorized Android integration for supported metrics.

Samsung HealthVia Health Connect

Indirect relay; coverage depends on overlapping Health Connect data types.

Route-by-route time

Freshness · 10 points
Ring → Oura appUsually a few minutes when the app syncs*

Oura says the sync process can take a few minutes. The ring must be near the phone, with Bluetooth active, before any outside route can update.

Oura → health platformsUsually a few minutes after app sync*

This practical range assumes background sharing works normally. Oura advises opening the relevant apps at least daily to prevent missed or stalled transfers.

Oura → API alertUsually a few minutes after app sync*

The API alert follows the server update. The estimate starts with a normal ring-to-app sync and is not a guaranteed Oura maximum.

Oura → clinicianManual snapshot

The native care route is a shareable report rather than a continuously refreshed physician view.

Health-platform portability23/25
Care-team parity9/25
Automated access & terms18/20
Complete self-export14/15
End-to-end freshness6/10
Transparency & control5/5

Who can actually use the data?

Wearer
Members can send broad metrics to Apple Health or Health Connect and export CSV or shareable reports.
Clinician
The native clinician route is a static shareable report, not continuous dashboard access.
Developer
OAuth and webhooks are public and free, but each app is limited to 10 users until Oura approves it.
Cost
API access is free. Current-ring API access depends on an active membership: US$69.99/year or €69.99/year in the EU.
04PolarPolar Flow + AccessLinkWearer sees itWatch: current · Flow: ≈30–60 minOthers receive itHealth apps/API: waits for ≈30–60 min watch upload72/100
Who else can get itConnect apps + build through API

Polar Flow can send supported metrics to phone health stores, while AccessLink provides a public OAuth API and webhooks.

How long others waitHealth apps/API: waits for ≈30–60 min watch upload

Many watches upload about hourly; Polar 360 and Loop use roughly 30-minute cycles. Every outside route must wait for that upload.

Barrier that remains

The free coach view is useful for training but is not a medical dashboard that stays close to the wearer’s current view, and account exports omit some derived data.

72/100 · Gated. Useful sharing or APIs exist, but delays, omissions, approvals, or clinical gaps remain.

See every route, score detail, cost, and source

A self-serve OAuth API, signed webhooks, and broad health-platform connections make Polar unusually reusable.

  • Self-serve OAuth
  • Royalty-free API
  • Signed webhooks
Biggest friction

Many Polar watches upload automatically about once per hour, while Polar 360 and Loop use roughly 30-minute cycles; outside access cannot update before that upload.

Access modelSelf-serve + royalty-free license
Meaningful data route$0 public API

Health-platform routes

Portability · 25 points
Apple HealthDirect

One-way Polar Flow export for selected activity, heart-rate, sleep, and body metrics.

Google / Health ConnectDirect

Polar Flow sends a broad but incomplete set of supported metrics.

Samsung HealthVia Health Connect

Indirect relay; only mutually supported Health Connect types can move onward.

Route-by-route time

Freshness · 10 points
Watch → Polar Flow≈30–60 minutes

Polar 360 and Loop upload about every 30 minutes; many current watches upload about once per hour, plus some event-triggered uploads.

Polar Flow → cloud / APIAvailable only after the watch uploads

Polar’s server and API cannot expose readings until the watch has sent them to Polar Flow.

Polar Flow → health platformsSent only after Polar Flow receives it

Apple Health and Health Connect wait for the same watch-to-Polar Flow upload, which is typically about 30–60 minutes.

Health-platform portability21/25
Care-team parity12/25
Automated access & terms20/20
Complete self-export8/15
End-to-end freshness6/10
Transparency & control5/5

Who can actually use the data?

Wearer
A wearer can send selected data to Apple Health or Health Connect and request an account export, although derived activity and sleep data are excluded from that export.
Clinician
Polar Flow for Coach is a free, ongoing training-data view after the user joins a coach, but it is not a general medical dashboard that stays close to the wearer’s current view.
Developer
Any registered Polar Flow user can create an AccessLink client. OAuth, JSON, webhooks, and continuous-heart-rate events are publicly documented without a small-user approval gate.
Cost
AccessLink is offered under a royalty-free API license. Polar Flow for Coach is free; no per-call data fee is published.
05Samsung HealthGalaxy Watch + Galaxy RingWearer sees itWatch: current · phone updates after watch syncOthers receive itHealth Connect: usually minutes after watch sync* · no follower67/100
Who else can get itConnect Android apps

Galaxy data can move from Samsung Health on the phone into Health Connect, where supported outside apps can read it.

How long others waitHealth Connect: usually minutes after watch sync* · no follower

Samsung writes to Health Connect immediately after its phone record changes. The practical end-to-end estimate is minutes while connected; reconnection or a sleeping app can make it hours.

Barrier that remains

No broad Apple Health route or wearer-equivalent clinician view is documented, and an outside app must be open and active to read Health Connect.

67/100 · Gated. Useful sharing or APIs exist, but delays, omissions, approvals, or clinical gaps remain.

See every route, score detail, cost, and source

Core Galaxy data can flow through Health Connect, while richer direct SDK access remains controlled by Samsung.

  • Health Connect
  • Broad data types
  • Personal download
Biggest friction

Samsung writes to Health Connect immediately after its phone record changes. The variable step is the watch-to-phone sync, and continuous heart rate is not sent to the phone immediately.

Access modelOpen platform route · gated direct SDK
Meaningful data route$0 public platform route

Health-platform routes

Portability · 25 points
Apple HealthNo verified route

The reviewed Galaxy workflow does not provide a broad outbound Apple Health route.

Google / Health ConnectDirect

Samsung Health writes new or updated supported data to Health Connect on the phone.

Samsung HealthNative

First-party store for Galaxy Watch and Galaxy Ring data.

Route-by-route time

Freshness · 10 points
Galaxy wearable → phoneUsually within minutes while connected*

This practical estimate assumes the wearable is connected and Samsung Health can run. A sleeping app, reconnection, or manual refresh can extend the wait to hours; continuous heart rate is intentionally batched.

Samsung Health → Health ConnectImmediate after the phone record updates

Samsung says it inserts or updates Health Connect as soon as Samsung Health creates or changes the phone-side record. The usual end-to-end estimate is minutes while the watch stays connected.

Health Connect → outside appOutside app must be open to read it

An authorized Android app can read Health Connect data only while that app is open and active.

Health-platform portability23/25
Care-team parity5/25
Automated access & terms15/20
Complete self-export13/15
End-to-end freshness6/10
Transparency & control5/5

Who can actually use the data?

Wearer
A user can authorize Samsung Health data to Health Connect and download a copy of personal Samsung Health data.
Clinician
The reviewed consumer workflow does not provide an individual physician with a live view matching the wearer’s Samsung Health app.
Developer
Health Connect offers a user-authorized route to common data. Samsung’s richer Data SDK can be tested locally, but public distribution requires a Samsung partnership and app registration.
Cost
Samsung Health and its downloadable SDK are free. Samsung does not publish a data-access fee for partner approval or production distribution.
06WHOOPWHOOP 5.0 + Developer PlatformWearer sees itContinuous while the strap stays connectedOthers receive itOutside app: usually minutes after processing* · no follower63/100
Who else can get itConnect apps + build through API

Selected summaries can move to both phone ecosystems, and approved outside apps can use OAuth and webhooks.

How long others waitOutside app: usually minutes after processing* · no follower

WHOOP sends the integration alert after it calculates an eligible update. Most connected flows should complete within minutes, but a disconnected strap or longer processing can extend the wait.

Barrier that remains

Some proprietary metrics stay inside WHOOP, and the normal membership does not include a universal live clinician view.

63/100 · Gated. Useful sharing or APIs exist, but delays, omissions, approvals, or clinical gaps remain.

See every route, score detail, cost, and source

OAuth and webhooks are excellent foundations, but important data and care-team access remain incomplete.

  • OAuth access
  • API alerts after calculation
  • Apple Health
Biggest friction

WHOOP alerts an integration after it finishes calculating an update. The outside app still waits for the strap upload and WHOOP processing to finish first.

Access modelFree API · approval after 10 users
Meaningful data routeUS$199–$359/year

Health-platform routes

Portability · 25 points
Apple HealthDirect

Broad two-way transfer, but WHOOP Age, Pace of Aging, ECG, and blood-pressure insights stay out.

Google / Health ConnectDirect

Broad two-way transfer, with proprietary and medical-grade metrics excluded.

Samsung HealthVia Health Connect

Indirect relay; Samsung receives only overlapping Health Connect records.

Route-by-route time

Freshness · 10 points
WHOOP → mobile appUsually seconds to minutes while connected*

WHOOP streams while connected, but background restrictions or lost connectivity can interrupt the upload and extend the wait.

WHOOP → API alertUsually within minutes after processing*

WHOOP sends a webhook when the workout, sleep, or recovery record is processed. This estimate is not a guarantee and processing-heavy records can take longer.

WHOOP → health platformsUsually within minutes after processing*

Supported summaries transfer automatically after WHOOP receives and processes them. A disconnected strap or delayed calculation can extend the wait.

Health-platform portability18/25
Care-team parity6/25
Automated access & terms16/20
Complete self-export11/15
End-to-end freshness7/10
Transparency & control5/5

Who can actually use the data?

Wearer
Members see recovery, strain, sleep, and health metrics in WHOOP; selected data can flow to Apple Health.
Clinician
There is no general live clinician view with wearer parity in the standard membership workflow.
Developer
The OAuth API is free and self-serve for small projects. More than 10 members requires app approval, and some data remains excluded.
Cost
Developer API: free. Wearer data requires a WHOOP membership, typically US$199–$359/year by current U.S. tier.
07DexcomG7 + Clarity + FollowWearer sees itNew reading about every 5 minOthers receive itFollow: ≈5 min · other routes: ≈3 hours61/100
Who else can get itFollower updates + clinic sharing

Invited people can use Dexcom Follow, clinics can connect through Clarity, and glucose can reach Apple Health or Health Connect.

How long others waitFollow: ≈5 min · other routes: ≈3 hours

A connected follower can receive each new five-minute reading. Clarity and Apple/Google health-platform data are about three hours behind.

Barrier that remains

The fastest route stays inside Dexcom’s follower ecosystem; production access for independent apps requires approval and a licensing agreement.

61/100 · Gated. Useful sharing or APIs exist, but delays, omissions, approvals, or clinical gaps remain.

See every route, score detail, cost, and source

Follow and Clarity are useful continuous sharing tools, but most of the value stays inside Dexcom’s ecosystem.

  • ≈5-minute follower updates
  • Clinic sharing
  • Raw CSV export
Biggest friction

Follow can receive each new five-minute reading when everyone is connected, but Apple Health, Health Connect, and the latest Clarity clinician data lag by about three hours.

Access modelFree sandbox · partnership for real users
Meaningful data routePrivate production quote

Health-platform routes

Portability · 25 points
Apple Health3-hour delay

Glucose reaches Apple Health after a stated three-hour delay.

Google / Health Connect3-hour delay

Glucose reaches Health Connect after a stated three-hour delay.

Samsung HealthVia Health Connect

G7 can relay glucose through Health Connect; the initial Dexcom delay still applies.

Route-by-route time

Freshness · 10 points
Sensor → wearer appNew reading every ≈5 minutes

G7 sends a new glucose reading to the compatible display device every five minutes.

Dexcom Share → Follow≈5-minute updates

A connected follower can receive each new five-minute glucose reading. This is close to the sensor cadence, not zero-second delivery.

Dexcom → Clarity clinician≈3 hours

Continuous clinic sharing is automatic, but the latest cloud data shown in Clarity is about three hours old.

Dexcom → Apple / Google3 hours

Apple Health and Health Connect deliberately display glucose after a three-hour delay.

Health-platform portability6/25
Care-team parity22/25
Automated access & terms8/20
Complete self-export13/15
End-to-end freshness7/10
Transparency & control5/5

Who can actually use the data?

Wearer
Follow can show each new five-minute glucose reading to invited people when the phones are online; Clarity and CSV provide retrospective access.
Clinician
A clinic can receive continuous Clarity data after the patient enters a clinic code, but it is delayed and not the wearer’s live app view.
Developer
Registration and sandbox data are free. Even a five-user real-data prototype needs Dexcom approval and a data-licensing agreement.
Cost
Sandbox: free. Production and commercial licensing prices are not public; full access requires technical and commercial review.
08GarminGarmin Connect + Health APIWearer sees itWatch: current · Connect waits for uploadOthers receive itManual sync: usually minutes* · automatic: hours possible53/100
Who else can get itConnect apps; API needs approval

Selected data can reach Apple Health or Health Connect after the watch sends it to Garmin Connect; richer feeds require approval for Garmin’s Health API.

How long others waitManual sync: usually minutes* · automatic: hours possible

Every outside route begins only after the watch uploads to Garmin Connect. A connected manual sync generally completes within minutes; automatic sync intervals vary and can be separated by hours.

Barrier that remains

There is no simple native clinician view, and commercial Health API use requires an undisclosed license fee.

53/100 · Limited. Portals and exports dominate; neutral continuous access is weak.

See every route, score detail, cost, and source

Garmin exposes rich health data, but its strongest access route is built for approved commercial integrations.

  • Health API
  • Push or pull
  • Apple Health export
Biggest friction

API access requires approval and commercial use carries a fee; Apple Health transfer waits until the watch has uploaded to Garmin Connect while the app is open.

Access modelApproval + paid commercial license
Meaningful data routeCommercial fee · amount undisclosed

Health-platform routes

Portability · 25 points
Apple HealthGarmin Connect must be open

One-way export starts only after watch data reaches the open Garmin Connect app.

Google / Health ConnectWaits for Garmin Connect

One-way export on Android 14+ starts after watch data reaches Garmin Connect.

Samsung HealthVia Health Connect

Indirect relay after Garmin Connect receives the data; proprietary metrics do not all transfer.

Route-by-route time

Freshness · 10 points
Wearable → Garmin ConnectManual sync: usually a few minutes*; auto sync: hours possible

A manual connected sync is generally completed within minutes. Automatic frequency varies by device; Garmin documents modes ranging from several attempts per day to only once or twice daily.

Garmin Connect → Apple / GoogleUsually minutes after manual sync*; hours on auto sync

The watch must upload to Garmin Connect first. Apple Health also requires Garmin Connect to be open, so background-only use can wait longer.

Garmin Connect → Health APIUsually minutes after manual sync*; hours on auto sync

The API can begin delivery once Garmin Connect receives the upload. The variable watch-sync schedule dominates the end-to-end wait.

Health-platform portability17/25
Care-team parity4/25
Automated access & terms11/20
Complete self-export12/15
End-to-end freshness4/10
Transparency & control5/5

Who can actually use the data?

Wearer
Garmin Connect can send selected metrics to Apple Health only after the watch data reaches Garmin Connect while the app is open.
Clinician
There is no simple native physician view; care use generally depends on an approved integration.
Developer
The Health API exposes rich JSON feeds, but the evaluation environment is available only after approval.
Cost
Garmin states that commercial use requires a license fee, but does not publish the amount.
09FreeStyle LibreLibreView + LibreLinkUpWearer sees itLibre 3: new reading about every 1 minOthers receive itLibre 3 follower: ≈1 min when online53/100
Who else can get itFollower updates + clinic sharing

Invited followers can use LibreLinkUp, clinics can connect through LibreView, and wearers can separately download raw data.

How long others waitLibre 3 follower: ≈1 min when online

A connected Libre 3 / 3 Plus follower can receive each new one-minute reading. Scan-based models share after each phone scan; online phone uploads usually reach LibreView within minutes*, while readers require manual upload.

Barrier that remains

No broad Apple Health, Health Connect, Samsung Health, or public self-service API route was documented.

53/100 · Limited. Portals and exports dominate; neutral continuous access is weak.

See every route, score detail, cost, and source

Family and clinic sharing work well, but continuous access is tied to Abbott apps and portals.

  • Up to 20 followers
  • Clinic sharing
  • Raw download
Biggest friction

With Libre 3 / 3 Plus, LibreLinkUp can receive each new one-minute reading when the phones are online. Abbott does not promise a precise delivery time, and reader-based workflows require manual upload.

Access modelConsumer and clinic portals only
Meaningful data routeNo public developer route

Health-platform routes

Portability · 25 points
Apple HealthNo documented route

The reviewed official workflow centers on LibreLinkUp and LibreView, not Apple Health.

Google / Health ConnectNo documented route

No broad consumer Health Connect export was documented in the reviewed materials.

Samsung HealthNo documented route

No broad consumer Samsung Health export was documented in the reviewed materials.

Route-by-route time

Freshness · 10 points
Libre 3 / 3 Plus → follower≈1-minute updates when online

Libre 3 / 3 Plus creates a new reading every minute, and Abbott calls LibreLinkUp sharing real time. Internet is required, and Abbott does not promise zero-second delivery.

Scan-based Libre → followerAfter each phone scan

A successful smartphone scan triggers sharing; scans made only with an offline reader do not reach followers.

Libre app → LibreView clinicUsually within minutes while online*

The phone uploads automatically to LibreView when connected. This is a practical estimate rather than an Abbott guarantee; offline readings wait until connectivity returns.

Reader → LibreView clinicManual upload

Reader-based data must be uploaded separately and is not a continuous external feed.

Health-platform portability3/25
Care-team parity23/25
Automated access & terms1/20
Complete self-export13/15
End-to-end freshness8/10
Transparency & control5/5

Who can actually use the data?

Wearer
LibreLinkUp provides invited follower access; raw data is downloaded separately through LibreView.
Clinician
Licensed professionals can create a LibreView practice and receive data from connected patients.
Developer
No public, self-service developer API is documented in the official materials reviewed for this score.
Cost
Consumer and clinic portal access is included. Any third-party integration route or price is not publicly documented.
10LingoAbbott consumer CGMWearer sees itCurrent glucose in the Lingo appOthers receive itHealth apps: exactly 3 h · no follower29/100
Who else can get itHealth apps + file download

Five-minute glucose values can move to either major phone health store, and the wearer can download a spreadsheet.

How long others waitHealth apps: exactly 3 h · no follower

Lingo deliberately holds glucose values for three hours before they appear in Apple Health or Health Connect.

Barrier that remains

There is no continuous caregiver or clinician route, and the export omits logged meals and workouts.

29/100 · Closed. Sharing is mostly manual or delayed, with no meaningful public developer or care-team route.

See every route, score detail, cost, and source

A glucose export exists, but timely collaborative access and contextual portability are weak.

  • Spreadsheet export
  • Apple Health
  • Health Connect
Biggest friction

Health-platform glucose arrives after a stated three-hour delay; exports omit logged meals and workouts.

Access modelNo public developer or clinical path
Meaningful data routeNo public developer route

Health-platform routes

Portability · 25 points
Apple Health3-hour delay

Five-minute glucose values arrive after a stated three-hour delay.

Google / Health Connect3-hour delay

Five-minute glucose values arrive after a stated three-hour delay.

Samsung HealthVia Health Connect

An indirect relay is possible; Lingo's three-hour delay remains before Samsung receives it.

Route-by-route time

Freshness · 10 points
Sensor → Lingo appCurrent wearer view

The wearer can see current glucose in Lingo, but speed inside Lingo does not count as fast outside sharing.

Lingo → Apple Health3 hours

Five-minute interstitial-glucose values are deliberately held for three hours before appearing.

Lingo → Health Connect3 hours

The Android health-platform route has the same stated three-hour delay.

Lingo → person / clinicianNo continuous route

There is no native caregiver connection or continuously refreshed clinician view.

Health-platform portability7/25
Care-team parity1/25
Automated access & terms0/20
Complete self-export12/15
End-to-end freshness4/10
Transparency & control5/5

Who can actually use the data?

Wearer
A user can export glucose and send 5-minute values to Apple Health or Health Connect after a three-hour delay.
Clinician
Lingo has no caregiver connection or dedicated continuous clinician-sharing workflow.
Developer
No public API or self-service route for authorized third-party access is documented.
Cost
Export and delayed health-platform transfer are included. No commercial data-access product or price is publicly documented.

These scores are meant to create change. Remove a barrier, publish the improvement, and the score rises. Challenge any finding with documentation.

Evidence from the field

Barriers are harder to ignore when they are documented.

Corrections, observed delays, missing routes, and improvement ideas appear here only after editorial review. Approved reports can challenge a finding or show where the published documentation falls short.

Loading approved notes…

The standard

Open means useful outside the company's own walls.

The detailed model uses six weighted criteria, but the principle is simple: the person generating the data should be able to direct it, receive it promptly, and use it without asking a corporation for special permission.

100 means no lock-in.No extra holding delay beyond the device's normal measurement cycle, plus complete exports, self-serve production APIs, and a care-team view that matches the wearer's.
1

What does the wearer see?

We identify the native watch or app timing first—but do not mistake that for external sharing.

2

When does someone else get it?

We follow the full path to the outside recipient. A fast native app does not erase a three-hour or one-day sharing delay.

3

Can you build with it?

Complete data, clear terms, reasonable cost, and production access without a private backend deal score higher.

Read the full scoring rules

Health-platform portability

25%

Do core metrics move into Apple Health, Google Health / Health Connect, and Samsung Health—and is each path direct, automatic, complete, and timely?

Full credit: Broad metrics move automatically across both major phone ecosystems, with a direct or clearly documented Samsung route and no material relay delay.

Care-team parity

25%

Can a person grant continuous access that is close to the view they see themselves?

Full credit: The wearer can grant and revoke a continuous physician view matching what they see themselves.

Automated access & terms

20%

Is useful production access self-serve—or gated by user caps, approval, security review, licensing, or a commercial deal?

Full credit: Real-user production access is self-serve, with no user cap, approval queue, private contract, or data license.

Complete self-export

15%

Can a person promptly download complete, machine-readable data—including important context?

Full credit: A prompt machine-readable export includes raw readings, derived scores, tags, meals, workouts, and relevant context.

End-to-end freshness

10%

How long does it take a new measurement to travel from device to phone, company server, health platform, outside app, follower, or clinician? Speed inside the company’s own app does not count by itself.

Full credit: Supported continuous outside routes pass new data through as soon as the provider receives it, within the device’s normal measurement timing, with no intentional hold or manual refresh.

Transparency & control

5%

Are scopes, limitations, consent, and revocation documented clearly?

Full credit: Scopes, latency, retention, consent, revocation, limits, and every access fee are public and clear.

Freshness scale

10/10Pass-through. No intentional hold: supported outside routes move data as soon as the provider receives it, without user action.
8–9/10Fast, conditional. The final handoff is automatic, but it still waits for an earlier wearable-to-phone sync whose maximum is not guaranteed.
6–7/10Mixed. One outside route is close to the device’s normal measurement timing, while another has a documented delay or a transfer step whose maximum is not guaranteed.
3–5/10Delayed / manual. Opening an app, manually transferring data, a multi-hour hold, or an irregular upload dominates outside access.
0–2/10Retrospective. Only reports, exports, screenshots, or no continuous external sharing route.
Methodology and disclosures →

Hold platforms accountable

Document the barrier. Build the pressure for change.

Report a real-world delay, closed route, missing metric, API gate, correction, or improvement. Every documented barrier makes it harder to dismiss the problem—and easier to demand a fix.

Report a barrier or submit evidence

Screenshots are welcome. They can show timestamps, sharing steps, or a delay that documentation misses. Crop or redact names, birth dates, email addresses, account IDs, and any health details not needed to verify the workflow.

Nothing appears publicly until it is reviewed and approved. Email addresses and uploaded screenshots are never shown in Community notes.

Corrections, experiences, ideas, links, and redacted screenshots are all welcome.

WearOpen is an independent advocacy and accountability campaign.

Created by Dr. Andrew Zimmerman to make wearable-data barriers visible, comparable, and harder to ignore—and to push wearable makers to open their platforms. No manufacturer sponsors the scores. About Andrew →