# Identify Stakeholders

## <img src="https://3631092837-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MaFTi2cXYF3MOUIP8lR%2F-MdYls9CkkDh2cynBcsD%2F-MdYlzEPG_Vvb_uRJ4n3%2Fbrand-myspace.svg?alt=media&#x26;token=8d1a130d-98b6-45d9-a983-ac6e83bb2dd6" alt="" data-size="line"> **Identify Stakeholders**                                   &#x20;

To establish the architecture, the stakeholders may be a bit broader than they are for a typical data exchange or component project.   \
\
To identify stakeholders, ask questions such as: &#x20;

* *Who is impacted by these architectural standards and who are the other interested  parties?* &#x20;
* *Is there a larger governmental architecture, standards body or ICT infrastructure that the health architecture needs to align with?*    &#x20;
* *Are there advocacy groups that can help?*

### Stakeholders to Consider &#x20;

* Organizations or people that support software solutions&#x20;
* Key architects or developers&#x20;
* Key or influential project leads&#x20;
* Other government of MOH architects that the health architecture may need to align with
* Government ICT organizations that support health projects or infrastructure&#x20;
* Organizations driving the project
* Ministry of Health representatives
* Technical and infrastructure support teams (e.g. help desk personnel, system hosting and connectivity providers) that may end up supporting the component(s), the bandwidth or other technology needed for the project to be successful. &#x20;

### **Identifying Stakeholder Motivations**

Once potential stakeholders are identified, it is helpful to understand high-level stakeholder motivations and challenges. Understanding these motivations will help teams engage and recruit the individuals that will represent the organizational stakeholders in:&#x20;

* Defining the architecture project scope &#x20;
* Vetting and prioritizing key use cases and user stories that the architecture needs to support
* Moving toward alignment on architecture standards

Ask questions such as: &#x20;

* *Are there different/varying motivations among interested and impacted parties?*&#x20;
* *What might be the success criteria for different stakeholders?*


---

# 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/untitled/identify-stakeholders.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.
