# Inventory Existing Tools

## <img src="https://3308277642-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MaFTi2cXYF3MOUIP8lR%2F-MeQAtSh-tYl-ykSPgMz%2F-MeQEES7YfIt5ZVNk9r0%2Frepair.svg?alt=media&#x26;token=ba77d1a7-8a77-4e13-9258-46f7f60bcdd3" alt="" data-size="line"> **Inventory Existing Tools**&#x20;

When determining your strategy or road map, it may be useful to determine if there are existing tools that can support the desired information exchange use cases.  When conducting the inventory, it may be useful to determine some of the following factors that will help in determining if use of the tool can be expanded to support the desired health information exchange use cases: &#x20;

* Implementation scope ( for example, the number of cases, patients or geographical scope of the implementation)
* Ability to support data sharing through standards-based APIs / creation of standard message specifications (IHE profiles - See [OpenHIE Architecture Specification](https://ohie.org/framework/))&#x20;
* Ability to support the tooling&#x20;
  * Documentation is present and easy to understand&#x20;
  * Source code is accessible and programming languages are understood by developers&#x20;
* Ability to support applicable terminology data standards&#x20;

  &#x20;             &#x20;

{% hint style="success" %} <img src="https://3308277642-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MaFTi2cXYF3MOUIP8lR%2F-Me6FCaymA0hPSnuCVe3%2F-Me6G6QqCYm4wLGJYCDm%2Fbook.png?alt=media&#x26;token=41c72f52-4856-49b2-a201-07e2ca52e137" alt="" data-size="line"> **Tools:** [Digital Health Atlas](https://digitalhealthatlas.org/en/-/)

<img src="https://3308277642-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MaFTi2cXYF3MOUIP8lR%2F-Me6FCaymA0hPSnuCVe3%2F-Me6G6QqCYm4wLGJYCDm%2Fbook.png?alt=media&#x26;token=41c72f52-4856-49b2-a201-07e2ca52e137" alt="" data-size="line"> **Reference:** [Digital Implementation Investment Guide](https://www.who.int/publications/i/item/9789240010567): (Chapter 4.2)
{% 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://guides.ohie.org/getting-started/dev/pathway-2-architecture/phase-2-requirements-and-design/inventory-existing-tools.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.