# 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;

We strongly recommend an iterative project implementation process.  When using an iterative process, implementation teams should designate an initial scope for a project and consider phases.  For example, the vision may be to have all patients in the country or region listed in the client registry, this may not be practical or necessary for the first implementation of the registry. You will want to clearly state the vision and the goals for each phase of the project.  For example, the first phase of a project might simply be to prove that data can be electronically shared between two systems.  &#x20;

One of the main objectives for a governance structure is to determine the scope of use cases and user stories that will be supported by each  iteration of the component or data exchange project and to determine how each subsequent iteration moves the team toward the larger goal for that project.  For example, If you have selected to implement a Client Registry, then you may need to determine which point-of service providers or national ID systems will interact with the client registry in the initial implementation.  Or, you may determine that only the women of childbearing age will be included.  Each project team will need to work with the governance structure to  set the scope based upon the HIE strategy, goals and priorities for the project.  An ideal initial scope is large enough to prove that some part of the project technically works and small enough to do that in the specified context and still add value to the health providers, health system and / or patients.  &#x20;

In an initial implementation, many teams limit scope by one or more factors such as:&#x20;

* Patient population&#x20;
* Region&#x20;
* Number of facilities&#x20;
* Number of indicators or data points&#x20;
* Number of features included&#x20;


---

# 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-1-component-and-data-exchange/phase-1-governance-value-and-scope/determine-project-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.
