Getting Started Guide
OHIE.orgDiscourseWikiAcademy
1.0-Beta
1.0-Beta
  • Getting Started Guide: Paths to Data Exchange
  • Select a Pathway
  • PATHWAY 1: Component and Data Exchange Projects
    • Pathway 1.1 - Governance, Value, and Scope
      • Identify Stakeholders
      • Determine and Document Roles and Responsibilities
      • Establish or Define Governance Structures
      • Determine Project Scope
      • Document the Expected Value of the Project
      • Establish a Project Plan
    • Pathway 1.2 - Requirements and Design
      • Establish Training Programs
      • Determine Resources and Identify Constraints and Environmental Factors
      • Analyze the Environment and Context
      • Identify System Constraints
      • Document Requirements
      • Select Software/Component(s)
      • Testing
    • Pathway 1.3 - Implement, Support, and Scale
      • Establish a Support Plan
      • Implement a Scalability Plan
      • Communication and Roll Out
  • PATHWAY 2: Architecture
    • Pathway 2.1 - Governance, Value, and Scope
      • Identify Stakeholders
      • Determine and Document Roles and Responsibilities
      • Establish or Define Governance Structures
      • Determine Project Scope
      • Define Value of Health System Architecture
      • Establish a Project Plan
    • Pathway 2.2 - Requirements and Design
      • Inventory Existing Tools
      • Document Use Cases
      • Establish Architecture Principles
      • Document the Architecture
      • Establish Architecture Processes
      • Establish Standards
    • Pathway 2.3 - Implement, Support, and Scale
      • Communication and Roll Out
  • How to Provide Feedback / Input
  • Change Log
Powered by GitBook
On this page
  • Identify Stakeholders
  • Stakeholders to Consider
  • Identifying Stakeholder Motivations
  1. PATHWAY 2: Architecture
  2. Pathway 2.1 - Governance, Value, and Scope

Identify Stakeholders

Architecture Level Project

PreviousPathway 2.1 - Governance, Value, and ScopeNextDetermine and Document Roles and Responsibilities

Last updated 3 years ago

Identify Stakeholders

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:

  • Who is impacted by these architectural standards and who are the other interested parties?

  • Is there a larger governmental architecture, standards body or ICT infrastructure that the health architecture needs to align with?

  • Are there advocacy groups that can help?

Stakeholders to Consider

  • Organizations or people that support software solutions

  • Key architects or developers

  • Key or influential project leads

  • Other government of MOH architects that the health architecture may need to align with

  • Government ICT organizations that support health projects or infrastructure

  • 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.

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:

  • Defining the architecture project scope

  • 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:

  • Are there different/varying motivations among interested and impacted parties?

  • What might be the success criteria for different stakeholders?