> For the complete documentation index, see [llms.txt](https://4heal.gitbook.io/4heal-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://4heal.gitbook.io/4heal-1/introduction/why-4heal.md).

# Why 4Heal

Modern health data suffers from three structural problems:

#### ① Fragmented Data

Health data lives everywhere:

* Medical check-ups in hospitals
* Sleep data in wearables
* Diet records in apps

Yet no system can truly integrate all of this into a **computable whole**.

***

#### ② Not Interpretable

Most platforms only tell users:

> “Here are your numbers.”

But rarely explain:

* Why are they like this?
* What does this mean for your health?
* What should you do next?

***

#### ③ Not Continuous

* Wearable data is unstable
* Medical check-ups are infrequent
* Health behaviors are hard to quantify

As a result, users struggle to extract **long-term value** from their data.

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://4heal.gitbook.io/4heal-1/introduction/why-4heal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
