# Document Use Cases

## <img src="/files/-MeQF3O_fopvNf0Wxnbt" alt="" data-size="line"> Document Use Cases

Project teams can use different language to refer to the health business processes or practices for data exchange.  We will use the term "use cases".  As outlined in the digram below, OpenHIE is designed to support broad areas of use cases that cover individual patient care, population and public health and healthcare administration.  Documenting your desired use cases is a step toward establishing the high-level requirements for your health information exchange.  For examples of how countries and project teams are using health information exchange architecture, see the [OpenHIE Impact Stories](https://ohie.org/impact-stories/). &#x20;

&#x20;

![](/files/-Me61_lfpWR_bNfZP3uS)

{% hint style="success" %} <img src="/files/-Me6G6QqCYm4wLGJYCDm" alt="" data-size="line"> **Reference:**  [Digital Implementation Investment Guide](https://www.who.int/publications/i/item/9789240010567): (Chapter 3.1.1)
{% 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/pathway-2-architecture/phase-2-requirements-and-design/document-use-cases.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.
