> For the complete documentation index, see [llms.txt](https://docs.bcbi.brown.edu/codiac-for-health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bcbi.brown.edu/codiac-for-health/foundations/dikw-model.md).

# DIKW Model

> In the context of health, the DIKW framework can be used to bridge formal, basic, and applied sciences toward a single purpose – to improve the diagnosis, care, and treatment of illness. [\[1\]](#references)

<mark style="background-color:orange;">"Data is not information, information is not knowledge, knowledge is not understanding, understanding is not wisdom." Clifford Stoll and Gary Schubert</mark>

<mark style="background-color:orange;">"Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" T.S.Eliot</mark>

<mark style="background-color:orange;">Update figure</mark>

<figure><img src="/files/579uY026xjEPXPghX1Np" alt=""><figcaption></figcaption></figure>

## References

## Resources

### Books

### Articles

### Links


---

# 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://docs.bcbi.brown.edu/codiac-for-health/foundations/dikw-model.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.