Now I have enough from the two primary WHO pages. Let me compose the brief from the JSON context plus the browser-verified content.

---

Monthly Global Health Data Governance Brief — May 2026

🔴 HIGH PRIORITY — 3 developments + 3 papers

1. PHEIC declared: Bundibugyo virus (Ebola) in DRC + Uganda — IHR Emergency Committee issues temporary recommendations

What changed: On 17 May 2026, the WHO DG determined that the Bundibugyo virus disease (BVD) epidemic in DRC and Uganda constitutes a PHEIC under Article 12 of the amended IHR (2005), but not a pandemic emergency. The first Emergency Committee meeting followed on 19 May, issuing detailed temporary recommendations on 22 May. Risk assessment: "Very high" for DRC, "High" for Uganda, "High" regionally, "Low" for all other states. Source: WHO (www.who.int/news/item/22-05-2026)

Why it matters: This is the first PHEIC declaration whose temporary recommendations explicitly invoke the amended IHR Article 12 framework (PHEIC vs pandemic emergency distinction), making it a live case study for your PhD. The data-governance content is unusually rich:

• Daily notification obligation: report suspected/probable/confirmed BVD cases daily to WHO via the IHR Contact Point
• Line lists and contact registries: establish and maintain registers of alerts, line lists of suspected/probable/confirmed cases, and contact lists with 21-day monitoring
• Performance indicators: establish mechanisms to monitor contact-tracing performance indicators
• Cross-border data sharing: international contact tracing with airline/conveyance operator data sharing, border-area surveillance coordination, personal data sharing with destination states
• No approved vaccines/therapeutics: unlike Ebola Zaire, no approved countermeasures exist — control relies entirely on surveillance, contact tracing, IPC, and community engagement
• Research governance: expedited regulatory/ethics reviews, pharmacovigilance, data sharing, and equitable access arrangements for clinical trials

My take: This is a strong candidate for a case-study chapter or journal article on IHR data obligations in practice. The temporary recommendations specify operational data flows (alerts → line lists → daily notification → contact tracing → performance monitoring) with explicit temporal requirements (24h investigation, daily reporting, 21-day monitoring). The cross-border contact-tracing provisions involving airline data sharing and cross-border personal-data transfer are novel compared to previous Ebola PHEIC recommendations. Worth comparing systematically against the 2019 DRC Ebola PHEIC and 2022 Uganda Ebola PHEIC temporary recommendations to map the evolution of IHR data obligations.

Use decision: Add to research journal as PHEIC case study. Save the full temporary recommendations text. Plan a structured comparison with prior Ebola PHEIC data provisions.

---

2. Pandemic Agreement: PABS annex negotiations extended — finalization pushed to 2027

What changed: The resumed sixth IGWG meeting (27 Apr–1 May) made progress but could not finalize the PABS annex. WHA79 (May 2026) will be asked to extend the mandate to May 2027 or authorize a special WHA session in 2026. The seventh IGWG meeting is set for 6–17 July 2026. Source: WHO (www.who.int/news/item/01-05-2026)

Why it matters: PABS is the "last piece of the puzzle" for the Pandemic Agreement — without it, signature and ratification cannot proceed. The PABS system governs the core data-governance bargain: rapid pathogen sharing (including genetic sequence data) in exchange for fair and equitable benefit sharing (vaccines, diagnostics, therapeutics). The negotiation extension signals unresolved disagreements on the data–benefit equation, likely around: (1) whether GSD sharing is mandatory or voluntary, (2) the trigger and scope of benefit-sharing obligations, (3) IP/access provisions for products developed from shared pathogens.

My take: The PABS deadlock is a PhD-relevant governance failure. The inability to close the pathogen-data–benefit loop after multiple negotiating sessions reflects deeper structural tensions between sovereign control over biological data, equitable access to countermeasures, and pharmaceutical IP regimes. If WHA79 extends to 2027 (as appears likely), this becomes a slow-burn issue — track but don't expect resolution soon. The July 2026 IGWG meeting is the next inflection point.

Use decision: Track for research journal. Monitor WHA79 outcome for the mandate decision. Flag the July 2026 IGWG meeting for the next monthly brief.

---

3. Hantavirus cruise-ship cluster: WHO DG direct community message + coordinated IHR response

What changed: A cluster of 8 hantavirus cases (3 deaths, 5 confirmed Andes virus) linked to the MV Hondius cruise ship triggered a WHO-coordinated multi-country response, a DG personal message to the people of Tenerife, and a separate WHO response briefing (7 May). WHO assessed the public health risk as "low." Source: WHO (www.who.int/news/item/07-05-2026) and (www.who.int/news/item/09-05-2026)

Why it matters: This is a minor but instructive IHR coordination case: a multi-country event (cruise ship with international passengers) triggering cross-border contact tracing, conveyance operator data sharing, and port-state coordination — all without a PHEIC declaration. The DG's unusual direct message to a community reflects lessons from COVID-era trust crises. The response model (assessment → coordination → communication → monitoring) is an example of IHR Article 6–9 notification and verification operating below the PHEIC threshold.

My take: Useful as a contrast case to the BVD PHEIC: same IHR architecture, different threshold. It shows the "everyday" IHR data machinery (notification, verification, contact tracing across jurisdictions) operating without emergency powers. Less analytically rich than the PHEIC case but good for illustrating the spectrum of IHR data obligations.

Use decision: Save as minor contrast case. Not a priority citation target, but useful for mapping the IHR data-governance spectrum.

---

📄 RELEVANT PAPERS

1. Participation of Civil Society Organisations and Academia in COVID-19 Governance: Insights from a Six Country Study

Health Policy and Planning, 16 May 2026. Source: HPP (doi.org/10.1093/heapol/czag063)

Analyses CSO and academic participation in COVID-19 governance mechanisms across six countries. Directly relevant to your governance-domain framework (organizational/institutional, political/legal, ethical/social). Best practices and strategies for non-governmental engagement in epidemic governance. Add to scoping review consideration list.

2. Governing Patient-Facing AI-Generated Video in Digital Health: A Risk-and-Ethics Matrix

Journal of Medical Internet Research, 8 May 2026. Source: JMIR (doi.org/10.2196/91940)

Proposes operational, lifecycle-based governance for AI-generated patient-facing video (synthetic clinician avatars, text-to-video explainers) embedded in institutional review pathways. Relevant to digital health governance and AI accountability. Less directly relevant to PHEIC/IHR work but useful for the broader digital-health-governance literature. Save for digital health governance references.

3. Health Information Adoption Among Patients With Chronic Disease in China: Patient–Platform Coshaping

Journal of Medical Internet Research, 20 May 2026. Source: JMIR (doi.org/10.2196/85229)

Theorizes health information adoption as a dynamic, platform-mediated process shaped by algorithmic curation and platform governance. Relevant to the intersection of platform governance and health data, but the chronic-disease framing and China-specific context limit direct applicability to the PHEIC/emergency focus. Marginal relevance; skip unless the platform-governance angle becomes central to your framework.

Other journal hits with partial relevance (not recommended for immediate action):

• BMJ GH: One Health rabies process mapping — more about outbreak response methodology than data governance
• BMJ GH: Infectious disease outbreaks and VAWG — outbreak impacts, not governance
• IJHPM: Medical device registries and real-world data surveillance — regulatory data governance, partially relevant
• JMIR: Patient acceptance of AI in healthcare — adoption/attitudes, not governance
• JMIR: The Digital Exposome framework — conceptual, tangentially relevant
• IJMI: Digital health maturity assessment (São Paulo) — operational, not governance-analytical
• PLOS GPH: Global Health Diplomacy competencies — partially relevant to institutional governance
• PLOS GPH: TB notification PDSA (India) — surveillance improvement, not governance analysis

---

🔗 FRAMEWORK MAPPING

Mapping the BVD PHEIC temporary recommendations to your lifecycle × governance-domain framework:

Lifecycle Phase	Political/Legal	Technical/Standards	Cross-Border/Global
Collection	Mandatory daily notification to WHO (IHR obligation)	Case definitions, line-list standards, RT-PCR validation	Cross-border contact tracing with airline data
Processing/Analysis	—	Contact-tracing performance indicators, alert registers	International contact tracing operations
Sharing	Personal data transfer to destination states	Data-sharing protocols for clinical trials	Bilateral border surveillance arrangements
Access/Use	Expedited ethics/regulatory review for research	Equitable access arrangements for countermeasures	—
Accountability	Quarterly reporting to WHO on implementation	Standardized monitoring tool	—

---

🗺️ SOURCE COVERAGE NOTE

• 31 sources checked across institutional (WHO, WHA, EB, PAHO, ECDC, Africa CDC, World Bank, OECD, OHCHR, UNDP, UNICEF, EU/EHDS, UN Digital Library) and journal (16 journals).
• 15 sources produced candidates; top contributors: WHO news (6), BMJ GH (4), JMIR (4), IJMI (4), PLOS GPH (4), HPP (3).
• 3 sources blocked via script, markdown.new fallback used: OECD health (403), UNDP news (403), UNICEF press releases (403). No Camoufox fallback attempted in this run — markdown.new auto/AI mode was tried per the skill's escalation path. No browser verification attempted for these sources due to cron time budget; recommend flagging for next manual check.
• Journals with zero candidates: Lancet Public Health, Bulletin of WHO, Globalization and Health — explicitly absent, not silently omitted.
• PAHO, ECDC, Africa CDC, OHCHR, EU/EHDS: zero candidates in this window.

---

🎓 SO WHAT FOR MY PHD?

The BVD PHEIC is the big one this month. It gives you a live, well-documented case of IHR Article 12 data obligations in action — daily notification, line lists, contact tracing with performance indicators, cross-border personal-data sharing — all under the amended IHR framework that distinguishes PHEIC from pandemic emergency. This is the kind of operational data-governance artifact that a PhD chapter or journal article can be built around. The PABS deadlock is the structural backdrop: we have refined emergency data machinery but still cannot close the pathogen-data–benefit loop that would make the Pandemic Agreement operational. The CSO/academia participation paper from HPP is a solid governance-participation reference; the JMIR AI-video governance piece is useful for the broader digital-health-governance literature but less central.

---

👀 WATCHLIST FOR NEXT MONTH

• WHA79 (May 2026): PABS mandate decision, any IHR-related resolutions, GPW14 adoption/transition
• BVD PHEIC evolution: second Emergency Committee meeting expected; watch for data-sharing friction, compliance with daily notification, cross-border contact-tracing performance
• IGWG seventh meeting (6–17 July): PABS text progress, fault lines on GSD sharing and benefit obligations
• WHO Results Report 2025 (released 23 April): check for GPW13 data/digital-health indicators and surveillance-strengthening metrics
• Lancet Digital Health, BMJ GH, HPP, JMIR: continue scanning for governance-framed papers

---

✅ RECOMMENDED ACTIONS

1. Add BVD PHEIC to research journal — save the full temporary recommendations, the 17 May DG statement, and the PHEIC determination. Start a structured comparison document vs prior Ebola PHEICs (2019 DRC, 2022 Uganda).
2. Track PABS/WHA79 outcome — the mandate extension decision is PhD-relevant. Check WHA79 proceedings when published.
3. Add HPP CSO/academia COVID-19 governance paper to scoping review consideration list.
4. Save JMIR AI-video governance paper to digital-health-governance reference library.
5. Flag July 2026 IGWG meeting for the next monthly brief.
6. Retry OECD/UNDP/UNICEF during next manual session (or next cron run with Camoufox fallback) — these were blocked this cycle.

Weekly Global Health Data Governance Monitor — 26 May 2026

Bottom line

• A new PHEIC was declared (Bundibugyo virus, DRC/Uganda) — the first under the amended IHR Article 12 with the new "pandemic emergency" distinction explicitly applied (DG determined PHEIC but not pandemic emergency).
• The Emergency Committee's temporary recommendations, issued 22 May, contain dense data-governance obligations: daily case notification to WHO, line-list maintenance, contact-tracing data, cross-border data sharing, quarterly implementation reporting — this is rich material for your scoping review's IHR/PHEIC data-governance framework.

High-signal primary-source items

1. Bundibugyo virus PHEIC determined + Emergency Committee temporary recommendations issued

• What changed: On 17 May the DG declared a PHEIC for Bundibugyo virus disease in DRC and Uganda under IHR Article 12(2). On 19 May an Emergency Committee was convened; temporary recommendations followed on 22 May, tiered by risk level (DRC: very high; Uganda: high; neighbours: high; all others: low). This is the first PHEIC where the amended IHR's distinction between PHEIC and "pandemic emergency" was explicitly invoked — the DG determined it did not meet pandemic emergency criteria.
• Why it matters for your work: The temporary recommendations prescribe detailed data flows — daily notification to WHO IHR Contact Points, alerts registers, line lists of suspected/probable/confirmed cases, 21-day contact monitoring data, cross-border contact-tracing information sharing, and quarterly standardized reporting on implementation. These are live, operational examples of the IHR data-governance obligations your scoping review examines. Additionally, the fact that no approved Bundibugyo-specific vaccines or therapeutics exist means control depends entirely on surveillance, contact tracing, and community engagement — making data quality and flow unusually central.
• Use decision: Archive both the 17 May determination and 22 May temporary recommendations as primary exhibits for your PHEIC data-governance analysis. The quarterly reporting obligation (final section of temp recs) is new and specific — worth tracking whether this becomes a sustained reporting mechanism.
• Source: PHEIC determination (17 May), Temporary recommendations (22 May)

1. Go.Data digitising outbreak investigation in Cox's Bazar — WHO feature story

• What changed: A WHO feature story (3 March, still in monitoring window) documents the transition from paper-based to digital outbreak investigation in the Rohingya refugee camps, where Go.Data enabled near-real-time case registration, transmission-chain visualisation, and faster contact tracing — reducing case registration delays from 3 days to under 24 hours.
• Why it matters: This is a concrete case of surveillance data governance in a humanitarian emergency setting — data sharing across WHO, IOM, MSF, and government partners; local ownership of data systems; interoperability with EWARS. It shows data governance not as abstract regulation but as operational infrastructure determining outbreak outcomes.
• Use decision: Useful as a case example for the scoping review's surveillance-data-governance section (especially the humanitarian/emergency setting angle). Note the 3 March date — it predates the Bundibugyo PHEIC but is newly surfaced in this week's crawl.
• Source: WHO feature story (3 March 2026)

Relevant papers

• Health sector coordination and resilient healthcare systems — European COVID-19 lessons · Globalization and Health, 16 May. Analyses health sector coordination across European systems during COVID-19. Governance-adjacent: coordination mechanisms, institutional resilience, and cross-sector collaboration are relevant to your framework's institutional/governance dimension, though the paper is not primarily about data governance. Accessible open-access. (DOI)

No other journal papers in this window were substantively about health data governance. JMIR papers were digital health but clinical/adoption-focused; PLOS Global Public Health papers were disease-specific; the two Health Policy and Planning papers on COVID-19 governance (civil society participation; bureaucratic autonomy in kit distribution) were paywalled and could not be assessed for full text.

Watch signals / low priority

• Hantavirus cluster on cruise ship — IHR coordination in practice (7 May). DG explicitly cited the IHR as the framework for multi-country coordination. Low public health risk, no governance novelty, but useful as an example of IHR operationalisation for a non-PHEIC cross-border event. Follow-up DG messages to Tenerife on 9 and 14 May. (WHO note)
• PAHO: Dominica DHIS2 surveillance training (21 May). Capacity-building for national surveillance data systems in the Caribbean — modest but relevant to digital surveillance infrastructure governance. (PAHO)
• West Africa outbreak preparedness simulation (INITIATE²) — WHO feature story on regional simulation exercise in Dakar. Preparedness rather than data governance per se, but cross-border coordination relevant. (WHO)

Source coverage

All primary-source classes were checked: WHO news, emergencies, digital health, WHA/EB, IHR topic/Secretariat, and pandemic accord pages; World Bank health; European Health Data Space; ECDC; PAHO; Africa CDC; Health Data Collaborative; DPGA; GDHP; Transform Health; UNAIDS; UN press releases; and UN Digital Library. Journal pool: Lancet Digital Health, BMJ Global Health, The Lancet Global Health, The Lancet Public Health, Bulletin of WHO, PLOS Global Public Health, Globalization and Health, Health Policy and Planning, IJHPM, Journal of Global Health, BMC Public Health, Intl J Medical Informatics, and JMIR. OECD, OHCHR, UNDP, and UNICEF pages were initially blocked (HTTP 403) but successfully accessed via fallback checks — no governance-significant items found on those sources this week. UN documents portal was technically accessible but returned a loading page with no crawlable content. Two Health Policy and Planning papers were paywalled and could not be read in full.