Skip to content
WHO/AFRO HIS Review

Search is only available in production builds. Try building and previewing the site to test it out locally.

3 · Objectives and scope

Owner: Steven Uggowitzer · Editors: Pallavi Dani (structural), Stephanie Berrada (legal-adjacent review) Effort: ~0.5 person-day · Due: v0.5 EOD Fri 2026-09-04 · v0.8 Fri 2026-09-11

What WHO expects here

A short, tight chapter that closes the interpretive gap between what the RFP said and what the team will actually do. WHO reviewers use this chapter to check that we have not silently narrowed or widened scope. Every paragraph traceable to an RFP paragraph number.

Ultimate contents

Objectives (as accepted)

Three sub-sections mapping one-to-one to the RFP objectives. Each sub-section: verbatim RFP text -> IQVIA’s interpretation -> what “success” looks like for that objective.

What is in scope

Named platforms known at RFP time (iAHO, Regional Health Data Hub, ESPEN, DPC Portal, EPR Hubs, Polio GIS, Mental Health). Named categories where discovery will surface additional platforms (shadow-IT layer, partner-hosted, country-hosted). Sampled country offices (rubric in Chapter 6). The eight-dimension inventory schema.

What is deliberately out of scope

Personal-scale spreadsheets and email-attachment reporting (out because unmanageable within the ten-week envelope). Non-AFRO WHO regions except as benchmarks. Detailed cybersecurity audit of individual platforms (out because it needs a specialised sub-engagement). WHO HQ platforms except where they intersect with AFRO workflows.

Rationale for the scope boundary

Half a page on why the scope is drawn where it is. This is where the RFP reviewer looks for evidence that we have thought about scope, not just accepted it.

Change-control mechanism

One paragraph: if scope needs to move during the engagement (either narrow or widen), the change control log (T25 in the master plan) captures the request, the reasoning, and the WHO/IQVIA joint agreement.

Evidence to draw on

  • RFP/AFRO/013/2026 (paragraph-level citation)
  • IQVIA Technical Approach (workspace/extracted/IQVIA_Technical_Approach.md)
  • WHO/AFRO Approach draft (workspace/extracted/WHO_AFRO_Approach.md)
  • Boucher briefing on the shadow-IT hypothesis

Complementary effort triggered

Line-by-line mapping to RFP paragraphs. Where we’ve narrowed or widened scope, the reasoning is written out. Legal-adjacent chapter; Stephanie reviews.