Why I built an open source alternative to Terra for wearable data

Описание и применение

Автор создал Open Health Sync – самодостаточный агрегатор данных носимых устройств, который хранит сырые payloads, обеспечивает FHIR R4 и экономит ресурсы, в отличие от платных облачных решений.

Задача

Existing hosted APIs like Terra are expensive, introduce third‑party data paths, lose raw payloads, and do not enforce FHIR R4 standards, making them unsuitable for projects that need cost control, full data retention, and clinical interoperability.

Результат

Open Health Sync achieves 2–3× faster end‑to‑end ingestion than Open Wearables, uses ~22 MB idle memory versus ~494 MB, and stores raw payloads for unlimited retention while providing FHIR R4 and other export formats.

Рабочий процесс

• Clone the repository and set up environment variables
• Generate an encryption key and start the Docker Compose stack
• Run the health‑check command
• Seed synthetic data for demo or import real Apple Health export
• Use the REST API or FHIR endpoints to query merged data
• Delete user data via DELETE /v1/users/{id} if needed

Доказательства

Every wearable speaks its own dialect. Apple Health sends one JSON line per HealthKit sample, with heart rate in count/min and oxygen saturation as a fraction. Withings sends a daily activity object keyed by date and intraday series keyed by Unix epoch. Oura, WHOOP and Fitbit each have their own idea of what a day, a device and a duplicate are.

Источник

It idles at about 22 MB of memory and runs on a Raspberry Pi 5.

Источник

Open Health Sync stored the records 2 to 3 times faster end to end and used about 22 MB of memory idle against about 494 MB, while Open Wearables used 3.4 times less disk.

Источник