All integrations
Available in v0.1.0

OMRON data, in your own stack.

Users connect their OMRON account over OAuth through the OMRON Wellness API. Open Health Sync pulls their blood pressure and body measurements on a schedule.

Read the setup guideAbout Open Health Sync
Source
Blood pressure monitors
How the data arrives
Partner API (OMRON Wellness API), OAuth 2.0, scheduled pulls.

What it collects.

Each record maps to the same model as every other source, with the provider, source and device it came from.

  • Blood pressure, systolic and diastolic paired
  • Pulse
  • Possible AFib flag
  • Weight, BMI, body fat and visceral fat

How it works.

  1. 01

    The user connects

    Your server asks for a consent URL and sends the user to OMRON. Tokens are stored encrypted.

  2. 02

    The server pulls

    A first backfill, then scheduled pulls, and webhooks where the provider sends them. Every raw payload is kept.

  3. 03

    You read one model

    Units, time zones and duplicates handled, served over REST, the read-only MCP server and FHIR R4.

Before you start.

  • Apply at omronhealthcare.com/api: staging credentials come first, production after OMRON's approval.
  • Its upload notifications aren't received yet, because their format isn't public.

Set it up.

Register your own OMRON app, set its callback to <OHS_PUBLIC_URL>/oauth/omron/callback and put its credentials in .env. The guide has every step.

Terminal
# .envOHS_OMRON_CLIENT_ID=...OHS_OMRON_CLIENT_SECRET=...OHS_OMRON_ENVIRONMENT=...# Ask for a consent URL, then send the user to authorize_urlcurl -s -X POST $OHS/v1/users/$USER_ID/connections/omron \  -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \  -d '{"redirect_uri":"https://app.example.org/connected"}'# Read what came incurl -s "$OHS/v1/users/$USER_ID/samples?type=blood_pressure_systolic" -H "Authorization: Bearer $KEY"

Questions.

Can I use OMRON with Open Health Sync today?

Yes. The OMRON connector ships in v0.1.0.

Do I need anything from OMRON?

Apply at omronhealthcare.com/api: staging credentials come first, production after OMRON's approval.

Where does the data go?

Only to the server you run. Open Health Sync is self-hosted software, not a service: no account with us and no call home. Each user can be deleted with one call, raw files included.