React Native bindings for HealthKit
npm install @kingstinct/react-native-healthkit
React Native bindings for HealthKit with full TypeScript and Promise support covering about any kind of data. Keeping TypeScript mappings as close as possible to HealthKit - both in regards to naming and serialization. This will make it easier to keep this library up-to-date with HealthKit as well as browsing the official documentation (and if something - metadata properties for example - is not typed it will still be accessible).
| Data Types | Query | Save | Subscribe | Examples |
| ----------------------------|:------|:------|:----------|:---------------------------------------|
| 100+ Quantity Types | ✅ | ✅ | ✅ | Steps, energy burnt, blood glucose etc.. |
| 63 Category Types | ✅ | ✅ | ✅ | Sleep analysis, mindful sessions etc.. |
| 75+ Workout Activity Types | ✅ | ✅ | ✅ | Swimming, running, table tennis etc.. |
| Correlation Types | ✅ | ✅ | ✅ | Food and blood pressure |
| Document Types | ✅ | ❌ | ✅ | CDA documents exposed as Base64 data |
| Clinical Records | ⚠️ | ❌ | ⚠️ | Lab results etc in FHIR JSON format (see Clinical Records) |
This library is provided as-is without any warranty and is not affiliated with Apple in any way. The data might be incomplete or inaccurate.
1. yarn add @kingstinct/react-native-healthkit react-native-nitro-modules
2. Update your app.json with the config plugin:
``json`
{
"expo": {
"plugins": ["@kingstinct/react-native-healthkit"]
}
}
this will give you defaults that make the app build without any further configuration. If you want, you can override the defaults:json`
{
"expo": {
"plugins": [
["@kingstinct/react-native-healthkit", {
"NSHealthShareUsageDescription": "Your own custom usage description",
"NSHealthUpdateUsageDescription": "Your own custom usage description",
"background": true
}]
]
}
}
3. Build a new Dev Client
2.
3. Set and NSHealthShareUsageDescription in your Info.plist
4. Enable the HealthKit capability for the project in Xcode.
5. Since this package is using Swift you might also need to add a bridging header in your project if you haven't already, you can find more about that in the official React Native docsUsage
During runtime check and request permissions with
requestAuthorization. Failing to request authorization, or requesting a permission you haven't requested yet, will result in the app crashing. This is easy to miss - for example by requesting authorization in the same component where you have a hook trying to fetch data right away.. :)Some hook examples:
`TypeScript
import { useHealthkitAuthorization, saveQuantitySample } from '@kingstinct/react-native-healthkit';const [authorizationStatus, requestAuthorization] = useHealthkitAuthorization(['HKQuantityTypeIdentifierBloodGlucose'])
// make sure that you've requested authorization before requesting data, otherwise your app will crash
import { useMostRecentQuantitySample, HKQuantityTypeIdentifier, useMostRecentCategorySample } from '@kingstinct/react-native-healthkit';
const mostRecentBloodGlucoseSample = useMostRecentQuantitySample('HKQuantityTypeIdentifierBloodGlucose')
const lastBodyFatSample = useMostRecentQuantitySample('HKQuantityTypeIdentifierBodyFatPercentage')
const lastMindfulSession = useMostRecentCategorySample('HKCategoryTypeIdentifierMindfulSession')
const lastWorkout = useMostRecentWorkout()
`Some imperative examples:
TypeScript
import { isHealthDataAvailable, requestAuthorization, subscribeToChanges, saveQuantitySample, getMostRecentQuantitySample } from '@kingstinct/react-native-healthkit'; const isAvailable = await isHealthDataAvailable();
/ Read latest sample of any data /
await requestAuthorization({ toRead: ['HKQuantityTypeIdentifierBodyFatPercentage'] }); // request read permission for bodyFatPercentage
const { quantity, unit, startDate, endDate } = await getMostRecentQuantitySample('HKQuantityTypeIdentifierBodyFatPercentage'); // read latest sample
console.log(quantity) // 17.5
console.log(unit) // %
await requestAuthorization({
toRead: ['HKQuantityTypeIdentifierHeartRate']
}); // request read permission for heart rate
/ Subscribe to data (Make sure to request permissions before subscribing to changes) /
const [hasRequestedAuthorization, setHasRequestedAuthorization] = useState(false);
useEffect(() => {
requestAuthorization(['HKQuantityTypeIdentifierHeartRate']).then(() => {
setHasRequestedAuthorization(true);
});
}, []);
useEffect(() => {
if (hasRequestedAuthorization) {
const unsubscribe = subscribeToChanges('HKQuantityTypeIdentifierHeartRate', () => {
// refetch data as needed
});
return () => unsubscribe();
}
}, [hasRequestedAuthorization]);
/ write data /
await requestAuthorization({ toShare: ['HKQuantityTypeIdentifierInsulinDelivery'] }); // request write permission for insulin delivery
saveQuantitySample(
'HKQuantityTypeIdentifierInsulinDelivery',
'IU',
5.5,
{
metadata: {
// Metadata keys could be arbirtary string to store app-specific data.
// To use built-in types from https://developer.apple.com/documentation/healthkit/samples/metadata_keys
// you need to specify string values instead of variable names (by dropping MetadataKey from the name).
HKInsulinDeliveryReason: HKInsulinDeliveryReason.basal,
},
}
);
`$3
In 6.0 you can use HealthKit anchors to get changes and deleted items which is very useful for syncing. This is a breaking change - but a very easy one to handle that TypeScript should help you with. Most queries now return an object containing samples which is what was returned as only an array before. newAnchor` is a base64-encoded string returned from HealthKit that contain sync information. After each successful sync, store the anchor for the next time your anchor query is called to only return the values that have changed.`limit` will indicate how many records to consider when sycning data, you can set this value to 0 indicate no limit.Example:
`TypeScript
const { newAnchor, samples, deletedSamples } = await queryQuantitySamplesWithAnchor('HKQuantityTypeIdentifierStepCount', {
limit: 2,
}) const nextResult = await queryQuantitySamplesWithAnchor('HKQuantityTypeIdentifierStepCount', {
limit: 2,
anchor: newAnchor,
})
// etc..
`Migration to 9.0.0
There are a lot of under-the-hood changes in version 9.0.0, some of them are breaking (although I've tried to reduce it as much as possible).
- The library has been migrated to react-native-nitro-modules. This improves performance, type-safety and gets rid of a lot of boilerplate code that made it harder to maintain and add features to the library.
- Naming conventions have changed - most of the HK-prefixed stuff has been removed to avoid conflicts on the native side and also make the library more beautiful to look at. As an example the type previously called HKQuantityTypeIdentifier is now just QuantityTypeIdentifier.
- Fewer required params - for example calling
without arguments will simply return the last 20 samples.
- Flexible filters that map closer to the native constructs. For example this supports filtering by uuid, multiple uuids as well as on items related to a specific workout.
- deleteObjects replaces all previous deletion methods, using the new flexible filters.
- Workouts are returned as proxies containing not only data but also functions, for example getWorkoutRoutes.
- Object identifiers are now just strings (not enums), but more strictly typed for each use case.
- Units are now just strings. There's a isQuantityCompatibleWithUnit()` helper function. Also, units are never required when querying, it always defaults to the users preferred unit.We're striving to do as straight a mapping as possible to the Native Libraries. This means that in most cases the Apple Documentation makes sense. However, when it comes to the Healthkit Metadata Keys the documentation doesn't actually reflect the serialized values. For example HKMetadataKeyExternalUUID in the documentation serializes to HKExternalUUID - which is what we use.
For accessing Clinical Records use old version (3.x) or use specific branch "including-clinical-records". The reason is we cannot refer to this code natively in apps without getting approval from Apple, this could probably be solved by the config plugin but we haven't had time to look into it yet.
For a similar library for Android, check out react-native-health-connect that works with the new Health Connect. For Google Fit react-native-google-fit seems to be the most popular option, and and another possible option is to work directly with the Google Fit REST API which I've some experience with.
See the contributing guide to learn how to contribute to the repository and the development workflow.
If you're using @kingstinct/react-native-healthkit to build your production app please consider funding its continued development. It helps us spend more time on keeping this library as good as it can be.
At Kingstinct we're also able to provide enterprise-grade support for this package, find us here or drop an email for more information. Also feel free to join our Discord community.
MIT