> For the complete documentation index, see [llms.txt](https://open-data-institute.gitbook.io/data-governance-playbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-data-institute.gitbook.io/data-governance-playbook/play-two-understanding-and-mapping-health-data-ecosystems/mapping-the-data-ecosystem.md).

# Mapping the data ecosystem

[Data ecosystem maps](https://theodi.org/article/data-ecosystem-mapping-tool/) can be applied to multiple contexts and frameworks. There are two main approaches to mapping a data ecosystem:

* **Understanding the current state.** For example, mapping out the key actors and data exchanges related to an existing health data project, to evaluate how and where use of data creates value.
* **Identifying a future state.** For example, mapping out the relationships, data and value exchange you are aiming for, to communicate the ambition, and influence and build relationships with key actors to realise that ambition.

The following two use cases illustrate how data ecosystem mapping can be used to visualise interactions between different actors and ideas in a system and, in addition, how it can generate useful insights and communicate these to stakeholders.

For practical advice on how to draw an ecosystem map, the ODI’s [data ecosystem mapping tool ](https://theodi.org/article/data-ecosystem-mapping-tool/.)provides a logical approach, and a way to visualise interactions.


---

# 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://open-data-institute.gitbook.io/data-governance-playbook/play-two-understanding-and-mapping-health-data-ecosystems/mapping-the-data-ecosystem.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.