# Determine Project Scope

## <img src="https://3308277642-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MaFTi2cXYF3MOUIP8lR%2F-MdXpu1aMJmDJvBtb41V%2F-MdXr_U6dG7gdQHPslVG%2Ftelescope.svg?alt=media&#x26;token=4a1c3d68-1d9b-4ef7-87d8-b8c1d34e91a7" alt="" data-size="line"> **Determine Project Scope**                            &#x20;

The scope of the architecture can be a bit challenging.  One perspective is to think about the systems and data sharing transactions that are in the purview of the ministry of health.  However, there may be other health data and health transactions that are in the jurisdiction of other ministries.  Examples of this may include the health supply chain and / or health medications and insurance coverage practices may be important even if these are not directly in the purview of the MOH.  To help move forward, you can begin with the architecture under a specific jurisdiction.  However, you may want to include other branches as appropriate in the stakeholders. You may want to use any existing health strategy documentation, examples from other countries and / or the OpenHIE Architecture Specification and Diagram to help think about scope of the architecture.  Ultimately, you will need to understand the systems that are needed to support the data sharing goals of the country.  To begin to identify these needs, use the DIIG (Chapter 3). &#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"> **References:**&#x20;

* [Digital Implementation Investment Guide](https://www.who.int/publications/i/item/9789240010567): (Chapter 3: Identify Health System Challenges and Needs)&#x20;
* OpenHIE Architecture Specification<br>
  {% 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/untitled/scope.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.