Skip to content

3. Stakeholder Analysis

Stakeholder analysis identifies individuals and entities that influence, are affected by, or have authority over the Sillah system.

Understanding stakeholder interests and influence helps prioritize requirements and manage potential conflicts during elicitation.

3.1 Stakeholder Identification

  • Families

    Primary users who interact with hereditary-health records and preventive alerts.

  • Healthcare Providers

    Clinical stakeholders who evaluate medical relevance and workflow fit.

  • System Administrators

    Operational stakeholders responsible for governance and integrity.

  • Legal / Regulatory Authorities

    External authorities shaping privacy and compliance requirements.

  • Public Health Authorities

    Future strategic stakeholders for integration and scale.

Only family members and healthcare providers participated directly in interviews. Regulatory and public-health perspectives were captured through document analysis.

3.2 Stakeholder Mapping

Stakeholder Role in System Primary Interest Influence Level Engagement Method
Families (Primary Users) End users of the platform Early detection, usability, privacy High Interview + Survey
Healthcare Providers Validate screening logic and recommendations Clinical accuracy High Interview
System Administrators Manage access control and platform integrity Secure system management Medium Document Analysis
Legal / Regulatory Authority (PDPL) Enforce data protection compliance Protection of sensitive health data High Document Analysis
Public Health Authority (Future) Potential system integration partner Preventive health scalability Medium Document Analysis

3.3 Stakeholder Classification

  • Primary Stakeholders

    Families and healthcare providers.

  • Secondary Stakeholders

    System administrators.

  • External / Regulatory Stakeholders

    PDPL-related authorities and compliance actors.

  • Future Strategic Stakeholders

    Public health authorities and integration partners.

Primary stakeholders were prioritized during elicitation to ensure alignment with user needs and preventive-health objectives.

3.4 Stakeholder Impact on Requirements

  • Families

    Drove usability, bilingual interface, and alert transparency requirements.

  • Healthcare Providers

    Shaped risk-detection logic clarity and recommendation structure.

  • Regulatory Authorities

    Influenced security, privacy, and consent-management requirements.

  • Public-Health Stakeholders

    Informed scalability and future integration considerations.