Stream Medisafe measurements. No Medisafe API needed.
Medisafe is a medication-reminder app, and it “keeps track of your measurements and syncs them to HealthKit” — blood glucose, blood pressure, weight, pulse, and temperature — which Sahha’s SDK reads into your app as normalized biomarkers, alongside every other source. The measurements are what crosses; the medication log stays in Medisafe.
- On-device
- Apple Health
- iOS
- HIPAA
- GDPR
Free for 30 days · No credit card
- Blood pressure
- 124/81 mmHg
- Blood glucose
- 5.6 mmol/L
- Weight
- 78.2 kg
Identical schema across 500+ sources
Your users connect Medisafe. Sahha does the rest.
This is your user’s side of the story — one screen, once. Sahha ingests every Medisafe signal, normalizes, deduplicates, and delivers it to your service — raw, or as refined intelligence your product can act on.
A Allow "your app"
On-device and permissioned
Medisafe data is read on the user’s own device, only after they grant Apple Health permission — nothing syncs without consent.
One integration, every source
Permission is per data type, not per brand. Anything that writes to Apple Health — Medisafe today, a new watch next year — flows through the same SDK with no extra prompt and no new code.
What Medisafe syncs through Apple Health.
Request only what you need
You choose exactly which of these signals to request from Apple Health — users are only ever prompted for those, which keeps opt-in rates high.
One schema, every source
Medisafe, Apple Watch, and Oura all return the same fields and units.
What crosses the bridge
Blood glucose, blood pressure, pulse, temperature, and weight pass through Apple Health; some app-exclusive metrics may not.
Heart & vitals
5
HealthKitSahha- bloodGlucoseblood_glucosemmol/L
- bloodPressureSystolicblood_pressure_systolicmmHg
- bloodPressureDiastolicblood_pressure_diastolicmmHg
- heartRateheart_ratebpm
- bodyTemperaturebody_temperature°C
Body
1
HealthKitSahha- bodyMassweightkg
See a real payload
{
"type": "HKQuantityTypeIdentifierBloodGlucose",
"value": 5.6,
"unit": "mmol/L",
"startDate": "2026-06-03T07:45:00Z",
"sourceRevision": { "source": { "name": "Medisafe" } }
// …blood pressure, weight, pulse & temperature samples
}[
{
"category": "vitals",
"type": "blood_glucose",
"value": 5.6,
"unit": "mmol/L",
"periodicity": "manual",
"aggregation": "none",
"startDateTime": "2026-06-03T07:45:00Z",
"endDateTime": "2026-06-03T07:45:00Z"
}
// …5 more normalized logs
]Medication and adherence data never crosses. Medication isn’t writable to Apple Health by third-party apps, and Sahha has no medication biomarker — so if you’re here for adherence, this integration won’t give it to you. What Sahha receives is Medisafe’s measurement tracking: blood glucose, blood pressure, pulse, temperature, and weight. These are user-entered readings, so cadence depends entirely on the user logging them — expect gaps, not a daily stream.
Missing a metric you need? Talk to us in the Sahha Slack — if Medisafe captures it, we can usually add support.
Get more than just raw data
Sahha turns these signals into biomarkers, scores, archetypes, and insights — the modeling done for you.
Reading Apple Health yourself? Here’s the to-do list.
Everything on the left is yours to write, test, and maintain on iOS. Everything on the right, Sahha already did.
- Integrate Apple Health.
- Handle iOS version differences.
- Add Health Connect separately for Android.
One SDK covers Apple Health, Health Connect, and every cloud source.
- Write the HealthKit queries.
- Request the right permissions.
- Wire up background delivery.
The SDK handles queries, permissions, and background sync.
- Dedupe apps writing the same metric.
- Map dozens of HealthKit types.
- Reconcile against your Android sources.
Deduped, typed, one schema — one stream per user.
- Build a sleep model.
- Build an activity model.
- Hire a data scientist.
Scores, archetypes, and insights — built in.
- Apple changes a HealthKit API.
- You find out in production.
We version the SDK. You never notice.
No Medisafe developer account needed — Sahha reads what Medisafe already writes to Apple Health on iOS.
Live in an afternoon, not a sprint.
- # Add the Sahha SDKnpm install sahha-react-native01
Add the Sahha SDK
Drop the Sahha SDK into your iOS app — or React Native or Flutter. The same SDK also covers Health Connect for your Android sources.
- A
Allow “your app”
ConnectSleepActivityHeart rate02Prompt for Apple Health permissions
Call the SDK to show the native Apple Health consent sheet. The user chooses what to share — under your brand. It’s one prompt, ever: permission is per data type, not per brand, so every future source is already covered.
- Your app LIVESleep7h 12mReadiness82Heart rate62 bpm03
Sahha reads and delivers
Once permission is granted, the SDK reads Medisafe data from Apple Health in the background, normalizes it to one schema, and streams it to your app by webhook or API.
Most teams read live Medisafe data the same day they add the SDK. The only per-source prerequisite: your user has Medisafe’s Apple Health sync switched on — most source apps enable it by default.
Route it into your stack.
Sahha streams every update to your webhook — and a step-by-step guide takes it the rest of the way into your database, CDP, or messaging tool.
Medisafe integration questions
How does Sahha get Medisafe data?
Medisafe syncs the measurements a user logs to Apple Health, and Sahha reads them from there with its mobile SDK — no Medisafe API to integrate.
Does Medisafe medication or adherence data come through?
No — and this is the thing to be clear about. Medisafe is a medication-reminder app, but medication data is not writable to Apple Health by third-party apps, and Sahha has no medication or adherence biomarker. Nothing about doses, schedules, or whether a user took a pill reaches Sahha. What Sahha receives is Medisafe’s measurements, not its medication log.
What Medisafe data does Sahha receive?
Blood glucose, systolic and diastolic blood pressure, pulse as heart rate, body temperature, and weight. All of it is user-entered, so a reading exists only when the user logs one — cadence follows their habit, not a schedule.
Does the Medisafe integration work on Android?
Not today. The verified write path is Apple Health, so this is an iOS-only integration and the page claims nothing more. Your users’ other Android sources still flow through the same Sahha SDK.
Is the Medisafe integration HIPAA and GDPR compliant?
Yes. Sahha is HIPAA and GDPR compliant and SOC 2 certified, and Medisafe data flows through the same compliant pipeline as every other source.
One API for every other source, too.
Add another wearable or app and the schema, webhooks, and scores are identical — no new pipeline to build.
Start streaming Medisafe data today.
Connect once. Sahha handles consent, normalization, and real-time delivery — for Medisafe and every other source.
Free for 30 days · No credit card
- One API for Medisafe and every other source
- Real-time webhooks + on-demand REST, one normalized schema
- Scores, archetypes & insights — no modeling required
- HIPAA, GDPR & SOC 2 · your brand on the consent screen