# 1. Data assets

With any healthcare project, it is important to understand what data assets you are accessing, using and sharing. Knowing what data assets you hold from your own project or organisation, and which are acquired from others, enables you to not only manage risk, but also provides an opportunity to save money. Cost efficiencies can be substantial, for example:

* only collecting or paying for the data you need&#x20;
* reducing duplication in the data held&#x20;
* decommissioning IT systems or applications.

It is important to keep a record of the data assets you are creating, accessing, using or sharing as part of your health data project, so that the whole project team, or key colleagues and stakeholders, have sight of the same information. Creating an inventory to catalogue data assets is a great way to do this.

#### Helpful questions to ask:

* How confident are you in the strategic decisions that are informed by data?&#x20;
* Do you know what data you need to deliver your key project or key organisational outcomes?&#x20;
* Are you creating specific data assets and/or using external sources?&#x20;
* Are you planning to share the data being collected through other platforms or data sharing agreements?

#### A useful resource for data assets is:

* Guidance on [how to create a data inventory](https://gatesopenresearch.org/documents/5-56).


---

# 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-one-implementing-data-governance-in-healthcare/how-to-implement-a-data-governance-framework-for-a-healthcare-organisation-or-project/1.-data-assets.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.
