# Play two: Understanding and mapping health data ecosystems

## Purpose of this play

As a project leader, you will need to engage with stakeholders and data assets from across the health data ecosystem, and explain where and how the use of health data creates value. Understanding these value exchanges can help in creating, and building support for, robust data governance frameworks beyond organisational boundaries. This guide will help you map your health data ecosystem and identify the actors, data and value exchanges.

## Who should read this play

* Non-technical leaders with strategic responsibilities who are working on a data project and need to understand actors and data value flows.
* Stakeholders on healthcare data projects who need to: understand and engage with their health data ecosystem; have conversations with strategic leaders and partners relating to accessing and sharing data; and increase collaboration between projects and organisations.

## When to use this play

* When designing a health data project that will involve accessing, using and sharing data.
* When there is a need to understand the ecosystem in which health data is accessed, used and shared. 
* When identifying key stakeholders in a health data project and building partnerships, alliances or coalitions. 
* When identifying new opportunities for sharing, using and accessing data.

{% hint style="warning" %}
Please note that this guidance is **not legal advice** and if you are uncertain, you should seek support from a legal professional.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://open-data-institute.gitbook.io/data-governance-playbook/play-two-understanding-and-mapping-health-data-ecosystems.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.