One migraine record.
Not one closed ecosystem.
Clea is designed to connect to the health data people already have. Direct APIs where they exist. Health-platform permissions where the operating system requires them. FHIR and user-authorised exports where an app does not expose an API.
Open connections. Proprietary value.
Clea does not need to own every sensor, tracker or record system. It needs to become the migraine-specific layer that can organise authorised data from all of them.
Interoperability is open. The Clea longitudinal migraine model, provider graph, workflows, outcomes and product IP remain Clea assets.
Members retain control over connection permissions and exports. Importing data never grants a clinic automatic access.
Build once. Add sources as adapters.
Apple Health
Native sync code implemented · device build pending. Clea's native sync layer requests read-only health permissions and sends selected health metrics into the same source-attributed Clea ingestion model. It still needs a native iOS build with the required Apple HealthKit entitlement and purpose-string configuration before device testing/release.
Android Health Connect
Native sync code implemented · device build pending. The Clea native sync layer is implemented for Android health data through the same read-only adapter. A native Android build and final least-privilege Health Connect manifest/privacy configuration are still required before device testing/release.
FHIR / clinical records
Import live. Members can already import a FHIR R4 JSON Bundle into Clea with source provenance preserved.
Migraine Buddy
Export import live. Members can import a structured Migraine Buddy CSV or JSON export. Clea will add a direct partner connection if Migraine Buddy exposes or agrees an API.
Other health & migraine apps
Structured import live. Clea can ingest structured CSV or JSON exports now, with a source-agnostic adapter layer for future APIs.
ChatGPT
MCP + events live in code. Clea exposes public migraine knowledge, treatment context, Australian care navigation and public proactive events through MCP. Private member tools remain gated until a dedicated OAuth 2.1 layer is provisioned.
ChatGPT Health
Companion architecture. Clea can be used alongside ChatGPT Health in ChatGPT. OpenAI does not currently expose a direct third-party feed of a user's private Health store to Clea.
If your health, migraine or clinical product can export or expose authorised data, Clea should be able to meet it at the boundary.
APIs, FHIR, structured exports and future partner adapters.
For partnership or technical integration conversations, contact hello@cleamigraine.com.au.
Clea will not claim a direct partner integration until the source API, permissions and data flow are actually live.