Spaces:
Running
Running
Update README.md
Browse files
README.md
CHANGED
|
@@ -1,5 +1,5 @@
|
|
| 1 |
---
|
| 2 |
-
title:
|
| 3 |
emoji: 📈
|
| 4 |
colorFrom: red
|
| 5 |
colorTo: blue
|
|
@@ -7,4 +7,279 @@ sdk: static
|
|
| 7 |
pinned: false
|
| 8 |
---
|
| 9 |
|
| 10 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
---
|
| 2 |
+
title: AI-POCUS Evidence Hub
|
| 3 |
emoji: 📈
|
| 4 |
colorFrom: red
|
| 5 |
colorTo: blue
|
|
|
|
| 7 |
pinned: false
|
| 8 |
---
|
| 9 |
|
| 10 |
+
# AI-POCUS Evidence Infrastructure Hub for LMICs
|
| 11 |
+
|
| 12 |
+
The **AI-POCUS Evidence Hub** is an LMIC-anchored, globally connected infrastructure initiative advancing the responsible development, validation, synthesis, and policy translation of **AI-enabled point-of-care ultrasound** for low-resource and humanitarian settings.
|
| 13 |
+
|
| 14 |
+
Point-of-care ultrasound can bring real-time, radiation-free imaging to the bedside, primary care clinic, mobile outreach programme, and crisis-affected field setting. When combined with artificial intelligence, POCUS has the potential to support non-specialist health workers with image acquisition, scan quality assessment, interpretation, triage, referral, treatment guidance, and monitoring across high-burden clinical areas.
|
| 15 |
+
|
| 16 |
+
Yet the AI-POCUS evidence base remains fragmented. Studies are difficult to compare across devices, scanning protocols, patient populations, reference standards, validation methods, metadata structures, and implementation contexts. The field lacks the shared evidence infrastructure needed to determine which tools are safe, effective, generalisable, equitable, and implementation-ready for LMIC and humanitarian health systems.
|
| 17 |
+
|
| 18 |
+
The AI-POCUS Evidence Hub addresses this gap by building the common standards, registries, living evidence systems, federated data resources, and collaborative infrastructure needed for AI-POCUS evidence to accumulate into policy-ready knowledge.
|
| 19 |
+
|
| 20 |
+
---
|
| 21 |
+
|
| 22 |
+
## Mission
|
| 23 |
+
|
| 24 |
+
Our mission is to make AI-POCUS evidence **standardised, interoperable, reusable, and decision-ready** for the settings where diagnostic access gaps are greatest.
|
| 25 |
+
|
| 26 |
+
We aim to support equitable AI-POCUS adoption by helping researchers, implementers, ministries of health, global health agencies, humanitarian actors, and clinical partners generate and use evidence that is transparent, comparable, locally relevant, and aligned with real-world decision needs.
|
| 27 |
+
|
| 28 |
+
---
|
| 29 |
+
|
| 30 |
+
## Why AI-POCUS?
|
| 31 |
+
|
| 32 |
+
In low-resource and humanitarian settings, limited access to diagnostics contributes to delayed and missed diagnosis across infectious disease, maternal health, emergency care, chronic disease, trauma, and acute care. Diagnostic systems built around fixed imaging facilities, specialist personnel, and equipment-intensive workflows often fail to reach patients where they first present.
|
| 33 |
+
|
| 34 |
+
POCUS offers a practical alternative. It is portable, reusable, radiation-free, and increasingly deployable through handheld probes connected to tablets or smartphones. It can support frontline decisions across lung, cardiac, abdominal, pelvic, obstetric, emergency, and primary care applications.
|
| 35 |
+
|
| 36 |
+
AI-enabled POCUS addresses one of the major barriers to scale: operator dependence. AI systems can support acquisition guidance, anatomical landmark detection, pathology classification, quality control, decision support, and workflow integration.
|
| 37 |
+
|
| 38 |
+
However, responsible adoption requires more than promising models. It requires shared infrastructure for evidence generation, validation, synthesis, governance, and implementation.
|
| 39 |
+
|
| 40 |
+
---
|
| 41 |
+
|
| 42 |
+
## What We Are Building
|
| 43 |
+
|
| 44 |
+
The Hub is structured around five integrated evidence infrastructure components.
|
| 45 |
+
|
| 46 |
+
### 1. Shared AI-POCUS Taxonomy and Standards
|
| 47 |
+
|
| 48 |
+
We are developing a common taxonomy and reporting framework for AI-POCUS research, validation, and implementation. This includes standard definitions for:
|
| 49 |
+
|
| 50 |
+
- Clinical use cases
|
| 51 |
+
- Scanning protocols
|
| 52 |
+
- Devices and probes
|
| 53 |
+
- AI model classes
|
| 54 |
+
- Annotation schemas
|
| 55 |
+
- Metadata structures
|
| 56 |
+
- Validation designs
|
| 57 |
+
- Reference standards
|
| 58 |
+
- Equity dimensions
|
| 59 |
+
- Implementation settings
|
| 60 |
+
- Dataset, model, and protocol cards
|
| 61 |
+
|
| 62 |
+
This taxonomy acts as the definitional layer that makes future evidence easier to compare, synthesise, and reuse.
|
| 63 |
+
|
| 64 |
+
### 2. Living Evidence Maps and AI-Enabled Living Evidence Synthesis
|
| 65 |
+
|
| 66 |
+
The Hub will maintain continuously updated evidence maps across priority AI-POCUS use cases, including tuberculosis triage, paediatric pneumonia, maternal health, emergency care, and multi-disease deployment.
|
| 67 |
+
|
| 68 |
+
These evidence maps will feed into **AI-enabled Living Evidence Synthesis**, allowing new studies, validation outputs, and implementation signals to be incorporated as the field evolves.
|
| 69 |
+
|
| 70 |
+
This approach is designed to move beyond static reviews toward continuously updated evidence products aligned with policy, procurement, guideline, and implementation timelines.
|
| 71 |
+
|
| 72 |
+
### 3. Federated Data, Model, and Protocol Registry
|
| 73 |
+
|
| 74 |
+
The Hub will support an open, federated registry of AI-POCUS datasets, validated models, and research protocols. The registry will be aligned with FAIR principles, DICOM-compatible data structures, STARD-AI, TRIPOD-AI, and responsible AI reporting practices.
|
| 75 |
+
|
| 76 |
+
The registry will include:
|
| 77 |
+
|
| 78 |
+
- Open ultrasound dataset cards
|
| 79 |
+
- Dataset licensing and access information
|
| 80 |
+
- Model cards
|
| 81 |
+
- Protocol registrations
|
| 82 |
+
- Validation plans
|
| 83 |
+
- Metadata templates
|
| 84 |
+
- Persistent identifiers
|
| 85 |
+
- Federated benchmarking pathways
|
| 86 |
+
|
| 87 |
+
Where appropriate, the Hub will support federated validation and model evaluation without requiring raw patient-level data to leave originating institutions.
|
| 88 |
+
|
| 89 |
+
### 4. Dynamic Policy Question Bank
|
| 90 |
+
|
| 91 |
+
The Hub will maintain a structured, living repository of priority policy questions co-produced with LMIC policymakers, ministries of health, implementation partners, and global health stakeholders.
|
| 92 |
+
|
| 93 |
+
Questions will span:
|
| 94 |
+
|
| 95 |
+
- Diagnostic accuracy
|
| 96 |
+
- Clinical utility
|
| 97 |
+
- Safety and interpretability
|
| 98 |
+
- Equity of access
|
| 99 |
+
- Health system integration
|
| 100 |
+
- Implementation feasibility
|
| 101 |
+
- Training and workflow requirements
|
| 102 |
+
- Cost-effectiveness
|
| 103 |
+
- Budget impact
|
| 104 |
+
- Procurement readiness
|
| 105 |
+
- Humanitarian deployment suitability
|
| 106 |
+
|
| 107 |
+
The goal is to ensure that evidence synthesis outputs are linked to real decision windows, including national strategies, donor investments, guideline cycles, and procurement processes.
|
| 108 |
+
|
| 109 |
+
### 5. Capacity Sharing and Ecosystem Strengthening
|
| 110 |
+
|
| 111 |
+
The Hub is built around an existing multi-country Community of Practice, bringing together researchers, clinicians, implementers, policymakers, data scientists, and evidence synthesis experts.
|
| 112 |
+
|
| 113 |
+
We support:
|
| 114 |
+
|
| 115 |
+
- LMIC-led working groups
|
| 116 |
+
- Open science toolkits
|
| 117 |
+
- Training resources
|
| 118 |
+
- Protocol templates
|
| 119 |
+
- Evidence synthesis methods
|
| 120 |
+
- Dataset and model documentation
|
| 121 |
+
- Responsible AI validation practices
|
| 122 |
+
- Peer exchange across institutions
|
| 123 |
+
- Implementation guidance for frontline settings
|
| 124 |
+
|
| 125 |
+
The Hub prioritises LMIC leadership, equitable governance, and practical capacity building across the AI-POCUS evidence lifecycle.
|
| 126 |
+
|
| 127 |
+
---
|
| 128 |
+
|
| 129 |
+
## Core Outputs
|
| 130 |
+
|
| 131 |
+
The AI-POCUS Evidence Hub will release and maintain:
|
| 132 |
+
|
| 133 |
+
- A standardised AI-POCUS taxonomy
|
| 134 |
+
- AI-POCUS reporting and metadata templates
|
| 135 |
+
- Living evidence maps
|
| 136 |
+
- AI-enabled living evidence syntheses
|
| 137 |
+
- Open ultrasound dataset registries
|
| 138 |
+
- Dataset cards and model cards
|
| 139 |
+
- Federated protocol and validation registries
|
| 140 |
+
- Policy question banks
|
| 141 |
+
- Evidence-to-decision briefs
|
| 142 |
+
- Implementation guidance
|
| 143 |
+
- Training modules
|
| 144 |
+
- Open-source tools and reusable infrastructure
|
| 145 |
+
|
| 146 |
+
---
|
| 147 |
+
|
| 148 |
+
## Priority Use Cases
|
| 149 |
+
|
| 150 |
+
The Hub initially focuses on AI-POCUS applications with high relevance for LMIC and humanitarian settings, including:
|
| 151 |
+
|
| 152 |
+
- Tuberculosis triage and referral
|
| 153 |
+
- Paediatric pneumonia diagnosis
|
| 154 |
+
- Maternal and obstetric risk assessment
|
| 155 |
+
- Emergency and acute care
|
| 156 |
+
- Lung ultrasound for infectious disease
|
| 157 |
+
- Multi-disease frontline diagnostic workflows
|
| 158 |
+
- AI-supported acquisition and scan quality assessment
|
| 159 |
+
- Task-shifted imaging by non-specialist health workers
|
| 160 |
+
|
| 161 |
+
Additional use cases will be incorporated as the Community of Practice expands.
|
| 162 |
+
|
| 163 |
+
---
|
| 164 |
+
|
| 165 |
+
## Governance and Community
|
| 166 |
+
|
| 167 |
+
The Hub is governed through an LMIC-majority, rotating Steering Committee and thematic working groups. Governance is designed to ensure that priorities are shaped by the institutions and health systems generating the evidence and serving the populations most affected by diagnostic gaps.
|
| 168 |
+
|
| 169 |
+
Working groups include:
|
| 170 |
+
|
| 171 |
+
- AI Validation and Safety
|
| 172 |
+
- Clinical Workflows and Training
|
| 173 |
+
- Implementation and Scale-Up
|
| 174 |
+
- Ethics, Equity, and Data Governance
|
| 175 |
+
- Evidence Synthesis and Policy Translation
|
| 176 |
+
- Data Standards and Interoperability
|
| 177 |
+
|
| 178 |
+
The Hub operates through principles of collective impact, responsible AI, open science, FAIR data, equitable partnership, and policy-oriented evidence generation.
|
| 179 |
+
|
| 180 |
+
---
|
| 181 |
+
|
| 182 |
+
## Data and Model Sharing
|
| 183 |
+
|
| 184 |
+
The Hub supports responsible, tiered access to AI-POCUS research outputs.
|
| 185 |
+
|
| 186 |
+
Open resources may include:
|
| 187 |
+
|
| 188 |
+
- De-identified metadata
|
| 189 |
+
- Dataset documentation
|
| 190 |
+
- Model cards
|
| 191 |
+
- Protocols
|
| 192 |
+
- Evidence maps
|
| 193 |
+
- Synthesis datasets
|
| 194 |
+
- Code and analysis pipelines
|
| 195 |
+
- Training materials
|
| 196 |
+
|
| 197 |
+
Restricted resources may include:
|
| 198 |
+
|
| 199 |
+
- Patient-level ultrasound imaging
|
| 200 |
+
- Sensitive clinical metadata
|
| 201 |
+
- Site-specific validation datasets
|
| 202 |
+
|
| 203 |
+
Access to restricted data will depend on local ethics approvals, data use agreements, institutional sign-off, and governance requirements from contributing partners.
|
| 204 |
+
|
| 205 |
+
Where possible, the Hub promotes federated approaches that allow validation and benchmarking without transferring raw clinical data.
|
| 206 |
+
|
| 207 |
+
---
|
| 208 |
+
|
| 209 |
+
## Responsible AI Commitments
|
| 210 |
+
|
| 211 |
+
The AI-POCUS Evidence Hub is committed to responsible, transparent, and context-aware AI development.
|
| 212 |
+
|
| 213 |
+
Our work emphasises:
|
| 214 |
+
|
| 215 |
+
- External validation across sites and populations
|
| 216 |
+
- Equity analysis across sex, age, geography, pregnancy status, displacement status, disease severity, and other relevant dimensions
|
| 217 |
+
- Transparent reporting using STARD-AI and TRIPOD-AI
|
| 218 |
+
- Clear model and dataset documentation
|
| 219 |
+
- Human-centred implementation
|
| 220 |
+
- Interpretable outputs for frontline users
|
| 221 |
+
- Governance for data protection and consent
|
| 222 |
+
- Avoidance of extractive data practices
|
| 223 |
+
- LMIC-led priority setting and authorship
|
| 224 |
+
- Alignment with local regulatory and ethical frameworks
|
| 225 |
+
|
| 226 |
+
---
|
| 227 |
+
|
| 228 |
+
## Relationship to Global Health Priorities
|
| 229 |
+
|
| 230 |
+
The Hub contributes to **SDG 3** by strengthening diagnostic capacity for conditions that drive preventable mortality in low-resource and crisis-affected settings.
|
| 231 |
+
|
| 232 |
+
It also contributes to **SDG 16** by supporting evidence-informed institutions, transparent governance, and resilient decision-making infrastructure in fragile and resource-constrained health systems.
|
| 233 |
+
|
| 234 |
+
The Hub aligns with global priorities for:
|
| 235 |
+
|
| 236 |
+
- Universal health coverage
|
| 237 |
+
- Digital health equity
|
| 238 |
+
- Responsible AI
|
| 239 |
+
- Diagnostic access
|
| 240 |
+
- Humanitarian health response
|
| 241 |
+
- TB elimination
|
| 242 |
+
- Maternal and child health
|
| 243 |
+
- Evidence-informed policymaking
|
| 244 |
+
- Open science and FAIR data infrastructure
|
| 245 |
+
|
| 246 |
+
---
|
| 247 |
+
|
| 248 |
+
## Current Development Areas
|
| 249 |
+
|
| 250 |
+
This organization space will host resources related to:
|
| 251 |
+
|
| 252 |
+
- AI-POCUS dataset registries
|
| 253 |
+
- Open ultrasound dataset cards
|
| 254 |
+
- Model cards
|
| 255 |
+
- Protocol templates
|
| 256 |
+
- Evidence maps
|
| 257 |
+
- Living evidence synthesis outputs
|
| 258 |
+
- Metadata standards
|
| 259 |
+
- Validation frameworks
|
| 260 |
+
- Implementation toolkits
|
| 261 |
+
- Training resources
|
| 262 |
+
- Community of Practice outputs
|
| 263 |
+
|
| 264 |
+
Repositories will be added as Hub infrastructure is developed and released.
|
| 265 |
+
|
| 266 |
+
---
|
| 267 |
+
|
| 268 |
+
## Contact
|
| 269 |
+
|
| 270 |
+
For collaboration, governance, dataset contribution, or Community of Practice enquiries:
|
| 271 |
+
|
| 272 |
+
EPFL LiGHT Laboratory
|
| 273 |
+
Email: mary-anne.hartley@epfl.ch
|
| 274 |
+
|
| 275 |
+
---
|
| 276 |
+
|
| 277 |
+
## Citation
|
| 278 |
+
|
| 279 |
+
If you use Hub resources, please cite the relevant dataset, model, protocol, or evidence product using the citation information provided in each repository.
|
| 280 |
+
|
| 281 |
+
---
|
| 282 |
+
|
| 283 |
+
## License
|
| 284 |
+
|
| 285 |
+
Unless otherwise specified, Hub code and documentation will be released under permissive open-source licenses such as MIT or Apache 2.0. Dataset access and reuse terms will be specified individually according to consent, ethics approvals, data use agreements, and partner governance requirements.
|