> For the complete documentation index, see [llms.txt](https://docs.thryve.health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thryve.health/further-resources/technology-overview.md).

# Technology overview

Thryve enables you to access health data. But how does the technology look like that makes this happen?

Thryve's service consists of 5 main building blocks:

1. **SDKs** for native (Android & iOS) and cross-platform (Flutter & React Native) enable you to integrate Thryve with any mobile application. Functionalities to enable your users to connect their wearables allow you to get first data in a matter of minutes from web data sources and native data sources, with the SDK taking care of everything.
2. The **data warehouse** stores all your users’ data from all data sources in the highest granularity possible in a harmonized data format. Mechanisms for data privacy make sure only the data that you really need is stored, helping you to achieve maximum compliance for your (medical) applications. All user data is linked to a fully pseudonymized Thryve user token, giving Thryve no information on who your user is.
3. When new data is flowing in, the **analytics platform** calculates relevant scores and biomarkers based on state-of-the-art medical research in real-time. We strive to have as much data available as possible for a user and often enrich data by deriving information that is not directly provided by the data sources and devices.
4. **Webhook notifications** keep your backend informed when users connect or disconnect their data sources as well as inform you about new or updated epoch and daily data. This allows you to draw data effiently from our data warehouse.
5. The **Wearable API** allows you to access all data stored in our data warehouse for your users. By specifying the timeframes, data sources, and data types you are interested in, you can access data without any clutter, allowing you to directly understand your users' fitness and health and build great, digital experiences.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thryve.health/further-resources/technology-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
