> ## Documentation Index > Fetch the complete documentation index at: https://docs.junction.com/llms.txt > Use this file to discover all available pages before exploring further. # Providers and Resources > Changelog of wearable provider updates including Health SDK Explicit Connect mode, sync progress logs, and provider-specific improvements. ### Sleep summary extension: `recovery_readiness_score` (April 2026) The Sleep summary now includes `recovery_readiness_score`, a value between 0 and 100 representing the provider's recovery or readiness proxy. * Currently sourced from Oura readiness score, WHOOP recovery score, and Ultrahuman recovery. * Available as a regular column in Continuous Query: `Sleep.col("recovery_readiness_score")` / `{ "sleep": "recovery_readiness_score" }`. ### Samsung Health via Junction Health SDK (March 2026) Junction Health SDK now supports Samsung Health as an SDK-based connection on Android phones. Samsung Health uses the same Sync On App Launch and opt-in Background Sync model as Health Connect. On Expo and React Native, the Health SDK now accepts an optional `provider` argument throughout the entire API surface. Health Connect remains the default provider, so you must pass `"samsung_health"` explicitly to target Samsung Health. Check out the [Samsung Health guide](/wearables/guides/samsung-health) for the Samsung Health setup requirements and details. Check out the [Junction Health SDK overview](/wearables/sdks/health/overview) for documentation on the shared API surface. This feature is available on Android SDK 5.0.0+ and React Native SDK 6.0.0+. ### Health SDK: Explicit Connect mode (Sep 2025) The Health SDK now supports an opt-in **[Explicit Connect mode](/wearables/sdks/health/connection-policies#explicit-connect-mode)**, which enables your application to explicitly control the moment of Health Connect connection creation and disconnection. The opt-in Explicit Connect mode also allows remote disconnection through the [Deregister Connection](/api-reference/user/deregister-a-provider) endpoint, which was not supported in the default [Auto Connect](/wearables/sdks/health/connection-policies#auto-connect-mode-default) mode. If your device connection management UX is built upon an explicit notion of connecting and disconnecting Apple HealthKit and Health Connect connections — as if they are like their cloud-based counterparts — you might find the [Explicit Connect](/wearables/sdks/health/connection-policies#explicit-connect-mode) mode more appealing. Check out the [Health SDK Connection Policies](/wearables/sdks/health/connection-policies) documentation for further details. This feature is available on iOS SDK 1.8.0+, Android SDK 4.2.0+, React Native SDK 5.4.0+ and Flutter SDK 4.6.0+. ### Health Connect sync progress logs in Junction Dashboard (Sep 2025) Health Connect integrations using Android SDK 4.2.0 or above now report client-side sync progress regularly to the Junction Dashboard. Similar to the iOS SDK equivalent, this report includes metadata of any exception that had disrupted a sync attempt. We hope that this brings more visibility into Health Connect sync issues. This feature is available on Android SDK 4.2.0+, React Native SDK 5.4.0+ and Flutter SDK 4.6.0+. ### Expanded Apple HealthKit data type coverage (April 2025) Junction iOS SDK 1.6.0 has expanded the HealthKit data type coverage: | Type | Remarks | `VitalResource` | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- | | Workout Stream timeseries | Workout Distance — including cycling, swimming, rowing, cross-country skiing, downhill snow sports, paddle sports, skating sports, walking, running, and wheelchair.
Workout Swimming Stroke | As part of `Workout` | | Timeseries | Heart Rate Recovery One Minute | `HeartRateRecoveryOneMinute` | Workout Stream timeseries data always have [Workout ID](/wearables/providers/data-attributions#workout-id) and [Sport](/wearables/providers/data-attributions#sport) attributions. For more information, check out: #### Data Events * the [Workout Distance data events](/event-catalog/daily.data.workout_distance.created) in the Event Catalog; * the [Workout Swimming Stroke data events](/event-catalog/daily.data.workout_swimming_stroke.created) in the Event Catalog; * the [Heart Rate Recovery One Minute data events](/event-catalog/daily.data.heart_rate_recovery_one_minute.created) in the Event Catalog; #### Data access API * the [Get Workout Distance](/api-reference/data/timeseries/workout-distance) endpoint documentation; * the [Get Workout Swimming Stroke](/api-reference/data/timeseries/workout-swimming-stroke) endpoint documentation; and * the [Get Heart Rate Recovery One Minute](/api-reference/data/timeseries/heart-rate-recovery-one-minute) endpoint documentation. ### Summary Ingestion Timestamps (April 2025) Activity, Body, Sleep, Sleep Cycle, Workout, Meal and Menstrual Cycle now expose ingestion timestamps: | Field | Remarks | | ------------ | --------------------------------------------------------------------------- | | `created_at` | The time at which Junction first ingested this summary. | | `updated_at` | The time at which Junction ingested the most recent update to this summary. | For more information, check out: #### Data Events * the [Activity data events](/event-catalog/daily.data.activity.created) in the Event Catalog; * the [Body data events](/event-catalog/daily.data.body.created) in the Event Catalog; * the [Sleep data events](/event-catalog/daily.data.sleep.created) in the Event Catalog; * the [Sleep Cycle data events](/event-catalog/daily.data.sleep_cycle.created) in the Event Catalog; * the [Workout data events](/event-catalog/daily.data.workouts.created) in the Event Catalog; * the [Menstrual Cycle data events](/event-catalog/daily.data.menstrual_cycle.created) in the Event Catalog; and * the [Meal data events](/event-catalog/daily.data.meal.created) in the Event Catalog. #### Data access API * the [Get Activity](/api-reference/data/activity/get-summary) endpoint documentation; * the [Get Body](/api-reference/data/body/get-summary) endpoint documentation; * the [Get Sleep](/api-reference/data/sleep/get-summary) endpoint documentation; * the [Get Sleep Cycle](/api-reference/data/sleep-cycle/get-summary) endpoint documentation; * the [Get Workout](/api-reference/data/workouts/get-summary) endpoint documentation; * the [Get Menstrual Cycle](/api-reference/data/menstrual-cycle/get-summary) endpoint documentation; and * the [Get Meal](/api-reference/data/meal/get-summary) endpoint documentation. ### Expanded Apple HealthKit data type coverage (March 2025) Junction iOS SDK 1.5.0 has expanded the HealthKit data type coverage: | Type | Remarks | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Profile summary | Wheelchair Mode usage | | Activity summary | Wheelchair Mode support (distance and push count) | | Body summary | Lean Body Mass, Body Mass Index, Waist Circumference | | Timeseries resources | Lean Body Mass, Body Mass Index, Waist Circumference, Wheelchair Push, Distance (Wheelchair Mode support), Stand Hour, Stand Duration, Sleep Apnea Alert, Sleep Breathing Disturbance, FEV1, Forced Vital Capacity, Peak Expiratory Flow Rate, Inhaler Usage, Fall, UV Exposure, Daylight Exposure, Handwashing, Basal Body Temperature | For more information, check out: #### Data Events * the [Profile data events](/event-catalog/daily.data.profile.created) in the Event Catalog; * the [Activity data events](/event-catalog/daily.data.activity.created) in the Event Catalog; * the [Body data events](/event-catalog/daily.data.body.created) in the Event Catalog; * the [Lean Body Mass data events](/event-catalog/daily.data.lean_body_mass.created) in the Event Catalog; * the [Body Mass Index data events](/event-catalog/daily.data.body_mass_index.created) in the Event Catalog; * the [Waist Circumference data events](/event-catalog/daily.data.waist_circumference.created) in the Event Catalog; * the [Wheelchair Push data events](/event-catalog/daily.data.wheelchair_push.created) in the Event Catalog; * the [Distance data events](/event-catalog/daily.data.distance.created) in the Event Catalog; * the [Stand Hour data events](/event-catalog/daily.data.stand_hour.created) in the Event Catalog; * the [Stand Duration data events](/event-catalog/daily.data.stand_duration.created) in the Event Catalog; * the [Sleep Apnea Alert data events](/event-catalog/daily.data.sleep_apnea_alert.created) in the Event Catalog; * the [Sleep Breathing Disturbance data events](/event-catalog/daily.data.sleep_breathing_disturbance.created) in the Event Catalog; * the [FEV1 data events](/event-catalog/daily.data.forced_expiratory_volume_1.created) in the Event Catalog; * the [Forced Vital Capacity data events](/event-catalog/daily.data.forced_vital_capacity.created) in the Event Catalog; * the [Peak Expiratory Flow Rate data events](/event-catalog/daily.data.peak_expiratory_flow_rate.created) in the Event Catalog; * the [Inhaler Usage data events](/event-catalog/daily.data.inhaler_usage.created) in the Event Catalog; * the [Fall data events](/event-catalog/daily.data.fall.created) in the Event Catalog; * the [UV Exposure data events](/event-catalog/daily.data.uv_exposure.created) in the Event Catalog; * the [Daylight Exposure data events](/event-catalog/daily.data.daylight_exposure.created) in the Event Catalog; * the [Handwashing data events](/event-catalog/daily.data.handwashing.created) in the Event Catalog; and * the [Basal Body Temperature data events](/event-catalog/daily.data.basal_body_temperature.created) in the Event Catalog. #### Data access API * the [Get Profile](/api-reference/data/profile/get-summary) endpoint documentation; * the [Get Activity](/api-reference/data/activity/get-summary) endpoint documentation; * the [Get Body](/api-reference/data/body/get-summary) endpoint documentation; * the [Get Lean Body Mass](/api-reference/data/timeseries/lean-body-mass) endpoint documentation; * the [Get Body Mass Index](/api-reference/data/timeseries/body-mass-index) endpoint documentation; * the [Get Waist Circumference](/api-reference/data/timeseries/waist-circumference) endpoint documentation; * the [Get Wheelchair Push](/api-reference/data/timeseries/wheelchair-push) endpoint documentation; * the [Get Distance](/api-reference/data/timeseries/distance) endpoint documentation; * the [Get Stand Hour](/api-reference/data/timeseries/stand-hour) endpoint documentation; * the [Get Stand Duration](/api-reference/data/timeseries/stand-duration) endpoint documentation; * the [Get Sleep Apnea Alert](/api-reference/data/timeseries/sleep-apnea-alert) endpoint documentation; * the [Get Sleep Breathing Disturbance](/api-reference/data/timeseries/sleep-breathing-disturbance) endpoint documentation; * the [Get FEV1](/api-reference/data/timeseries/forced-expiratory-volume-1) endpoint documentation; * the [Get Forced Vital Capacity](/api-reference/data/timeseries/forced-vital-capacity) endpoint documentation; * the [Get Peak Expiratory Flow Rate](/api-reference/data/timeseries/peak-expiratory-flow-rate) endpoint documentation; * the [Get Inhaler Usage](/api-reference/data/timeseries/inhaler-usage) endpoint documentation; * the [Get Fall](/api-reference/data/timeseries/fall) endpoint documentation; * the [Get UV Exposure](/api-reference/data/timeseries/uv-exposure) endpoint documentation; * the [Get Daylight Exposure](/api-reference/data/timeseries/daylight-exposure) endpoint documentation; * the [Get Handwashing](/api-reference/data/timeseries/handwashing) endpoint documentation; and * the [Get Basal Body Temperature](/api-reference/data/timeseries/basal-body-temperature) endpoint documentation. ### Improved LibreView practice connection process (Jan 2025) You can now connect LibreView patients in [46 regions in the EU environment](/wearables/guides/abbott-libreview#-junction-eu-region) and [8 regions in the US environment](/wearables/guides/abbott-libreview#-junction-us-region). Previously, the Link API and Link Widget listed only the regions to which our practice account was registered. However, these practice accounts can often connect to patients in a larger geographical area beyond the region of registration. For example, patients in most EMEA countries can connect through our Netherlands practice account. Therefore, we have now changed: 1. Link Widget to display an exhaustive list of regions which our practice account can reach; and 2. Link API to accept any ISO 3166-1 code that is on the list. In other words, say if you have a patient domiciled in Belgium, it is no longer necessary to teach them to choose "Netherlands" when connecting through the Link Widget. They can now intuitively choose "Belgium" when asked by the Link Widget. Check out the [Abbott LibreView](/wearables/guides/abbott-libreview) guide and the [Connect Email Provider](/api-reference/link/link-email-provider) endpoint for more information. ### Electrocardiogram, Heart Rate Alert and AFib Burden (Dec 2024) Junction now supports collecting Electrocardiogram (ECG) data and a couple of related data points from a set of providers: | Resource | Apple HealthKit \[3] | Fitbit | Withings | Kardia | | ------------------------------------------------------- | ------------------------------- | ----------------- | ----------------- | ----------------- | | Electrocardiogram Summary
`electrocardiogram` | ✅ | - | ✅ | ✅ | | ECG Voltage timeseries
`electrocardiogram_voltage` | ✅ | - | ✅ | ✅ | | Heart Rate Alert
`heart_rate_alert` | ✅ \[1] | ✅ \[2] | ✅ \[2] | ✅ \[2] | | AFib Burden
`afib_burden` | ✅ | - | - | - | \[1] Irregular rhythm alerts, high heart rate alerts and low heart rate alerts.
\[2] Irregular rhythm alerts only.
\[3] Requires Junction iOS SDK 1.3.0+, Junction Flutter SDK 4.4.0+ or Junction React Native SDK 5.1.0+. For more information, check out: * the [Get Electrocardiogram](/api-reference/data/electrocardiogram/get-summary) endpoint documentation; * the [Get Electrocardiogram Voltage](/api-reference/data/timeseries/electrocardiogram-voltage) endpoint documentation; * the [Get Heart Rate Alert](/api-reference/data/timeseries/heart-rate-alert) endpoint documentation; * the [Get AFib Burden](/api-reference/data/timeseries/afib-burden) endpoint documentation; * the [Electrocardiogram data events](/event-catalog/daily.data.electrocardiogram.created) in the Event Catalog; * the [Electrocardiogram Voltage data events](/event-catalog/daily.data.electrocardiogram_voltage.created) in the Event Catalog; * the [Heart Rate Alert data events](/event-catalog/daily.data.heart_rate_alert.created) in the Event Catalog; and * the [AFib Burden data events](/event-catalog/daily.data.afib_burden.created) in the Event Catalog. ### Sleep Cycle Summary Type (Nov 2024) We are introducing a new Sleep Cycle summary type (`sleep_cycle`) which captures the detailed hypnogram of a sleep session. The existing hypnogram timeseries type is deprecated in favor of this new summary type. Check out the [Get Sleep Cycle](/api-reference/data/sleep-cycle/get-summary) endpoint and the [Sleep Cycle data events](/event-catalog/daily.data.sleep_cycle.created) in the Event Catalog for more information. ### Body Summary model extension (Nov 2024) The Body Summary model now includes 4 new fields: * `water_percentage` - The percentage of water in the body. * `muscle_mass_percentage` - The percentage of muscle mass in the body. * `visceral_fat_index` - Provider's score of visceral fat levels. * `bone_mass_percentage` - The percentage of bone mass in the body. At the time of writing, all four are only available from the Withings provider. Check out the [Get Body Summary](/api-reference/data/body/get-summary) endpoint and the [Body Created](/event-catalog/daily.data.body.created) event for more information. ### Sleep Type (Nov 2024) Sleep summaries now have a new *Sleep Type* field. Junction maps the Sleep Type from the source provider whenever possible. If this is unavailable at source, Junction infers the Sleep Type based on the sleep session duration. | Sleep Type | Description | | ------------------ | -------------------------------------------------------- | | `long_sleep` | >=3 hours of sleep | | `short_sleep` | \<3 hours of sleep | | `acknowledged_nap` | User-acknowledged naps, typically under 3 hours of sleep | | `unknown` | The sleep session recording is ongoing. | Check out the [Get Sleep endpoint](/api-reference/data/sleep/get-summary) and the [Sleep data events](/event-catalog/daily.data.sleep.created) in the Event Catalog for more information. ### Apple HealthKit data sync improvements (Aug 2024) An overhauled Apple HealthKit sync engine is now available across all Junction Mobile SDK platforms. The changes bring historical data sync incrementality, prioritization, network resiliency and reduced resource usage. 1. Most resources now use a resumable sync & upload process. * This enables the SDK to make constant forward progress, especially when you have specified a very large historical pull stage (60-365 days) through the [Team Data Pull Preferences](/api-reference/org-management/team-data-pull-preferences/upsert-team-data-pull-preferences) API. 2. The SDK now prioritizes syncing of summary types over timeseries data. * During the historical pull stage, all timeseries resources would be suppressed until all the summary types have been successfully uploaded. * After the historical pull stage, the SDK would make forward progress on summary types, before it proceeds to deal with the more CPU-time-consuming timeseries data that are more prone to operating system throttling. 3. With an updated iOS App Target configuration, the SDK would now self-register as a `BGProcessingTask` or `BGHealthResearchTask` (iOS 17+) to the iOS BackgroundTasks framework. * This would provide the SDK an additional opportunity to complete any resource sync that is not able to complete during normal HealthKit background delivery. * Please refer to the [Apple HealthKit guide](/wearables/guides/apple-healthkit#1-setup-app-entitlements) on how to update your iOS App Target configuration in Xcode. | Platform | Release Note | | ------------ | ------------------------------------------------------------------------------------------------- | | Native iOS | [vital-ios 1.2.2](https://github.com/tryVital/vital-ios/releases/tag/1.2.2) | | Flutter | [vital-flutter 4.2.1](https://github.com/tryVital/vital-flutter/releases/tag/vital_health-v4.2.1) | | React Native | [vital-react-native 4.2.1](https://github.com/tryVital/vital-react-native/releases/tag/4.2.1) | ### Menstrual Cycle Tracking (July 2024) Menstrual cycle tracking data can now be collected through the Apple HealthKit and Android Health Connect integrations. Ask for data permission on the `MenstrualCycle` resource from the user through the Junction Health SDK. Check out the [Get Menstrual Cycles](/api-reference/data/menstrual-cycle/get-summary) endpoint and the [Menstrual Cycle data events](/event-catalog/daily.data.menstrual_cycle.created) in the Event Catalog for more information. ### Steps count in workouts (May 2024) Workouts now include the total steps count during the session (if available). Check out the [Get Workouts](/api-reference/data/workouts/get-summary) endpoint and the [Workout Created](/event-catalog/daily.data.workouts.created) event for more information. ### New Abbott LibreView integration (May 2024) Junction has introduced a new Abbott LibreView provider (`abbott_libreview`). It uses password authentication, accepting LibreView patient account credentials. This is an alternative option to our practice-based Freestyle Libre provider (`freestyle_libre`). With `abbott_libreview`, Junction uses the provided LibreView patient account credentials to connect directly to LibreView. There is no involvement of a LibreView practice in this integration. Note that both practice-based and patient-based connections would continue to be supported in parallel. The `abbott_libreview` integration does not replace the `freestyle_libre` integration. Check out the [Abbott LibreView / Freestyle Libre](/wearables/guides/abbott-libreview) guide for more information. ### Removed Fitbit and Oura required scopes (May 2024) The Fitbit profile scope and Oura email scope are no longer required for establishing connections. For Fitbit specifically, please be aware of the [updated Fitbit Time Zone resolution precedences](/wearables/guides/fitbit#time-zone-resolution). When your user refuses to grant both the activity and the profile scope, Fitbit data are more likely to be timestamped incorrectly on a UTC time basis due to inaccurate or unavailable time zone information. We have now updated our Fitbit and Oura integrations not to depend on these scopes to be **minimally functional**. If you are interested in requiring your users to grant certain scopes when connecting an OAuth provider, check out the [Team Scope Requirements](/changelog/wearables/api#team-scope-requirements-apr-2024) changelog entry and the [Set Team Scope Requirements](/api-reference/org-management/team-scope-requirements/upsert-team-scope-requirements) endpoint for more information. ### Freestyle Libre: India region (Apr 2024) Our Freestyle Libre integration now supports the LibreView India region. Check out the [Abbott LibreView](/wearables/guides/abbott-libreview#bring-your-own-practice) documentation for more information. ### Health Connect Background Sync (Mar 2024) Junction Mobile SDK now includes an experimental Background Sync feature for Android Health Connect. The feature is available through the following Junction Mobile SDK releases: | Platform | Version | | -------------- | ------- | | Native Android | 2.0.0+ | | Flutter | 3.2.0+ | | React Native | 3.1.0+ | Check out the following documentation for information, integration guidance, as well as caveats of the experimental Background Sync: * [Junction Health SDK: Automatic Data Sync](/wearables/sdks/health/overview#automatic-data-sync) for a general overview * [Android Health Connect integration guide](/wearables/guides/android-health-connect#background-sync), which includes guidance on the experimental Background Sync feature. ### Expanded Source Type attribution (Feb 2024) Data from Fitbit, Oura, Garmin and Freestyle Libre now comes with Source Type attributions. Check out the [Data Attributions](/wearables/providers/data-attributions#source-type) documentation for more information.