· · 13 min read

Can Algorithms Save Lives Where Doctors Are Scarce?

AI triage in low-resource settings is one of the most promising ideas in global health — and one of the most dangerous if we get it wrong. The technology is improving rapidly. The data it learns from is not.

SK
Safiya Khan
CS Student · CAPM® · HealthTech Researcher

There is a number that stops me every time I encounter it: according to the World Health Organisation, the world faces a projected shortfall of 10 million health workers by 2030, with the deficit concentrated overwhelmingly in low- and middle-income countries [1]. In Sub-Saharan Africa, there are regions where a single physician serves tens of thousands of patients. In rural South Asia, maternal mortality rates remain catastrophically high not because the knowledge to prevent those deaths does not exist, but because the human capacity to deliver care consistently does not.

Into this gap, artificial intelligence has arrived with considerable promise. AI triage systems — algorithms trained to assess symptom severity, prioritise patients, and flag urgent cases — are increasingly being piloted in low-resource settings as a partial answer to this workforce crisis. I want to engage with that promise seriously, because I think it is real. But I also want to be honest about something the technology press rarely says clearly: we are a long way from deploying these systems equitably. And until we confront why, the gap between promise and reality will widen, not narrow.

What AI Triage Can Do

Let us start with what is genuinely impressive. Modern AI triage systems built on large language models, decision tree ensembles, and symptom-checking neural networks have demonstrated meaningful clinical accuracy in controlled settings. Tools like Ada Health and Babylon Health have been evaluated against clinical benchmarks with results that, for common conditions, approach the diagnostic accuracy of a general practitioner [2]. In community health worker programmes — where frontline health workers with limited formal training conduct initial assessments — AI-assisted decision support has been shown to increase the accuracy of referral decisions and reduce dangerous undertriage [3].

The use case that excites me most is not replacing clinicians but extending them. A community health worker in a rural clinic, equipped with an AI-assisted triage tool on a basic smartphone, can systematically screen patients against a broader differential than memory and training alone would allow. The AI does not make the decision. It surfaces possibilities, flags red flags, and creates a structured record. The human makes the call. That division of labour is both clinically sound and ethically defensible — and in settings where the alternative is no screening at all, the marginal value is enormous.

⚙ Technology: LLM-based Symptom Checkers ⚙ Technology: Decision Tree Ensembles ⚙ Technology: Neural Network Classifiers ✦ Tool: Ada Health ✦ Tool: Babylon Health ✦ Tool: WHO SMART Guidelines ◎ Use Case: Community health worker decision support ◎ Use Case: Rural primary care triage ◎ Use Case: Maternal health risk stratification

"An algorithm trained on data that does not include you will not serve you well. It will serve the population it learned from — and call that universal."

The Problem Nobody Wants to Name

Here is where I need to say something uncomfortable. The datasets on which most clinical AI systems are trained are not representative of the populations in low-resource settings that these systems are now being asked to serve. They are drawn overwhelmingly from high-income, predominantly white patient populations in North American and European healthcare systems [4]. The result is a set of models that encode, with mathematical precision, the biases of the data they learned from.

This is not a hypothetical risk. It has been documented repeatedly. A landmark 2019 study published in Science found that a widely used clinical algorithm systematically underestimated the health needs of Black patients relative to white patients with identical clinical profiles — because the algorithm used historical healthcare spending as a proxy for health need, and Black patients had historically been given less care [5]. The bias was not in the intention. It was in the data. And the data reflected a healthcare system that had been inequitable for generations.

Extend this logic to AI triage in low-resource settings and the implications become serious. A model trained on the clinical presentations of patients in Boston or Berlin will have learned patterns that do not generalise to patients in Lagos or Dhaka — where disease burden, presentation timing, comorbidity profiles, and access to prior care are fundamentally different. Deploying that model as though it were universal is not neutral. It is a choice to embed existing inequity into algorithmic infrastructure.

⬡ Guiding Principle: Algorithmic Fairness ⬡ Guiding Principle: Representative Data Collection ⬡ Guiding Principle: Community-Centred Design ◈ Operating Model: Human-in-the-Loop AI ◈ Operating Model: Participatory AI Development ⚖ Framework: WHO Ethics & Governance of AI for Health ⚖ Legislation: EU AI Act — High-Risk AI (Annex III)

Systemic Bias Is Not a Bug to Be Patched

I want to push back on a framing that I encounter frequently in AI ethics discussions: the idea that bias in clinical AI is a technical problem with a technical fix. Collect more diverse data, retrain the model, audit the outputs — and the problem is solved. This framing is dangerously incomplete.

Algorithmic bias in healthcare is not primarily a data problem. It is a reflection of structural inequity that predates machine learning by centuries. When a model underserves women, it is because medical research has historically underenrolled women in clinical trials [6]. When it underserves Black or brown patients, it is because those patients have been undertreated, underdiagnosed, and underrepresented in the clinical literature on which training data depends. When it fails in low-income settings, it is because the global health research apparatus has been oriented towards the diseases and presentations of wealthy populations.

More data from marginalised communities helps. But it is not sufficient on its own if the people collecting that data, labelling it, and making deployment decisions remain predominantly from the same demographics that produced the original bias. Equitable AI in healthcare requires equitable participation at every stage of the development process — not just in the dataset, but in the research teams, the clinical advisory boards, the ethics review processes, and the communities whose health is at stake.

Where bias enters the AI triage pipeline:

01 — Training data: sourced from high-income, predominantly white clinical populations — presentations, comorbidities, and disease burden differ significantly in low-resource settings

02 — Label quality: clinical ground truth labels inherit historical diagnostic biases — if physicians historically underdiagnosed conditions in certain groups, the model learns to do the same

03 — Proxy variables: using healthcare utilisation, spending, or prior diagnosis as proxies for health need encodes access inequity as clinical fact

04 — Deployment context: models validated in high-resource settings are applied in low-resource environments without revalidation against local epidemiology

What Responsible Deployment Actually Looks Like

None of this means AI triage should not be developed for low-resource settings. It means it should be developed differently — and that the communities it is intended to serve should be at the centre of that process from the beginning, not consulted at the end.

The most promising frameworks I have encountered treat AI triage not as a product to be exported from high-income to low-income settings, but as an infrastructure to be built collaboratively with local health systems. The WHO SMART Guidelines initiative [7] represents one of the most credible attempts at this — encoding clinical recommendations as computable, context-adaptable logic that can be implemented and validated locally, rather than a monolithic model trained elsewhere and deployed universally.

From a project management perspective — and my CAPM® training is relevant here — the failure mode of most AI health deployments in low-resource settings is not technical. It is structural. Scope is defined by the technology team, not the health system. Stakeholders from the target community are identified late in the process, if at all. Risk registers do not account for the social and political dimensions of deploying algorithmic decision-making in communities with legitimate reasons to distrust institutions. These are not AI problems. They are programme management problems, and they are solvable with the right frameworks applied from the start.

⬡ Framework: WHO SMART Guidelines ⬡ Framework: FAIR Data Principles ⬡ Framework: Responsible AI for Health (RAI4H) ◈ Operating Model: Co-design with local health systems ◈ Operating Model: Continuous local revalidation ✦ Tool: OpenMRS (Open Medical Record System) ✦ Tool: DHIS2 (District Health Information Software) ⚖ Compliance: ISO/IEC 42001 — AI Management Systems ⚖ Legislation: African Union Data Policy Framework 2022 ◎ Use Case: WHO immunisation programme decision support ◎ Use Case: Community health worker training augmentation

The First Step Is Acknowledgement

I want to end on the point I feel most strongly about, because it is the one most frequently skipped in technical discussions of this topic. Before better data, before fairer models, before responsible deployment frameworks — the first step is acknowledging that the problem exists and that it is structural.

The global AI health community has a tendency to frame equity as an optimisation target: something to be improved incrementally, measured in disparity metrics, and reported in evaluation tables. That framing is not wrong, but it is insufficient. It treats the underrepresentation of minority, low-income, and Global South populations in clinical AI as a technical gap to be closed rather than a symptom of a deeper problem — which is that the people building these systems have not, historically, been the people they are intended to serve.

Truly equitable AI triage in low-resource settings will not come from better algorithms alone. It will come from funding research led by scientists in the Global South. From clinical trials that enrol the populations whose lives depend on the results. From regulatory frameworks that require local validation before deployment, not after. From technology teams that reflect the demographic diversity of the patients their systems assess.

The technology is improving. The systems are becoming more capable. But capability is not equity. And until the field confronts the structural roots of its own bias — not just in the data, but in who holds the resources, the publishing power, and the deployment decisions — we will keep building faster, smarter tools that serve the already-served better than anyone else.

That is not good enough. And I think we know it.

Key Takeaways

01
The need is real and urgent. A projected 10 million health worker shortfall by 2030, concentrated in LMICs, creates a genuine case for AI-assisted triage as decision support — not replacement — for frontline health workers.
02
The data problem is structural, not technical. Most clinical AI training data comes from high-income, predominantly white populations. Deploying those models in low-resource settings encodes existing inequity into algorithmic infrastructure.
03
Bias enters at every stage. Training data, label quality, proxy variable selection, and deployment context all introduce inequity. Addressing only one layer is insufficient — the entire pipeline requires scrutiny.
04
Responsible deployment is a programme management challenge. The failure mode of most AI health pilots in LMICs is structural — poorly defined scope, absent community stakeholders, and unaccounted social risk — not technical.
05
Equity requires representation at every level. Better datasets help but are insufficient. Equitable AI in healthcare demands equitable participation in research teams, advisory boards, ethics review, and deployment decisions.
06
Acknowledgement is the first step. The field must name the structural roots of algorithmic bias — not just optimise disparity metrics — before genuinely equitable AI triage becomes possible.

Future Trends

The trajectory of AI triage in low-resource settings over the next decade will be shaped by these converging developments:

01
Federated Learning Across LMIC Health Systems
Training AI models across distributed local datasets — without centralising patient data — allows models to learn from Sub-Saharan, South Asian, and Latin American clinical populations without creating privacy-violating data exports. WHO and partners are actively investing in this infrastructure. [8]
02
Multilingual & Low-Literacy Interfaces
Next-generation triage tools are being designed for voice interaction in local languages, removing literacy as a barrier to AI-assisted self-triage. Projects like Google's Multilingual Health NLP initiative and Masakhane are pioneering this for African languages. [9]
03
Mandatory Equity Auditing in Regulation
The EU AI Act classifies clinical decision support as high-risk AI, requiring bias audits and conformity assessments before deployment. As this framework influences global regulatory norms, mandatory equity evaluation before deployment in LMICs may become standard. [10]
04
Global South–Led AI Health Research
Initiatives like the African Institute for Mathematical Sciences, India's AI for Health programme, and Wellcome Trust's LMIC research funding are beginning to shift the centre of gravity in clinical AI development. The next decade's most impactful triage tools may be built in Nairobi and Chennai, not Silicon Valley. [11]

References

[1]World Health Organisation. Health Workforce 2030: A Global Strategy on Human Resources for Health. WHO, Geneva, 2016. who.int
[2]Razzaki, S. et al. (2018). A comparative study of artificial intelligence and human doctors for the purpose of triage and diagnosis. arXiv:1806.10698. arxiv.org
[3]Mehl, G. et al. (2021). Digital health for the health SDGs: harnessing the electronic health record. Bulletin of the World Health Organisation, 99(4), 313–319. doi.org/10.2471/BLT.20.260281
[4]Gianfrancesco, M.A. et al. (2018). Potential biases in machine learning algorithms using electronic health record data. JAMA Internal Medicine, 178(11), 1544–1547. doi.org/10.1001/jamainternmed.2018.3763
[5]Obermeyer, Z. et al. (2019). Dissecting racial bias in an algorithm used to manage the health of populations. Science, 366(6464), 447–453. doi.org/10.1126/science.aax2342
[6]Liu, K.A. & Mager, N.A.D. (2016). Women's involvement in clinical trials: historical perspective and future implications. Pharmacy Practice, 14(1), 708. doi.org/10.18549/PharmPract.2016.01.708
[7]World Health Organisation. SMART Guidelines: Digital Adaptation Kits. WHO Digital Health & Innovation. who.int/smart-guidelines
[8]Rieke, N. et al. (2020). The future of digital health with federated learning. npj Digital Medicine, 3(1), 119. doi.org/10.1038/s41746-020-00323-1
[9]Nekoto, W. et al. (2020). Participatory Research for Low-resourced Machine Translation: A Case Study in African Languages. Findings of EMNLP 2020. arxiv.org/abs/2010.02353
[10]European Parliament. Regulation on Artificial Intelligence (EU AI Act). Regulation (EU) 2024/1689, Annex III — High-Risk AI Systems. eur-lex.europa.eu
[11]Wellcome Trust. Our Position on AI and Machine Learning in Health Research. Wellcome, London, 2023. wellcome.org
AI Triage Health Equity Algorithmic Bias Low-Resource Settings Global Health Federated Learning WHO Student Perspective
© 2026 Safiya Khan · safiyakhan.io ← Back to Blog