Healthcare workers in low- and middle-income countries needed current, evidence-based medical guidance despite limited connectivity, scarce localized content, language barriers, and heavy frontline workloads.
↗17,000+ healthcare practitioners supported across 19 countries
↗26% gain in context recall compared to OpenAI
↗32.5% gain in latency compared to the MedLLaMA3-v20 model with NVIDIA Tesla T4 GPU
↗Improving care for 20 million people each year
Reported impact
Business outcome
CMES-AI now supports more than 17,000 healthcare practitioners across 19 countries and improves care for 20 million people each year, while cutting query time from 5 minutes to 2 seconds and increasing token throughput 22x so clinicians can make faster decisions at the point of care.
Customer Experience
Productivity Improvement
Scalability
Solution
Techies Without Borders built CMES-AI as a medical knowledge assistant that combines generative AI with NVIDIA edge and inference tooling to deliver answers inside resource-constrained clinics. The team began by training and fine-tuning clinical LLMs on an NVIDIA T4 Tensor Core GPU, then deployed the runtime to the NVIDIA Jetson Nano Developer Kit so clinics could run the assistant locally even when connectivity is poor. TWB added a preferred orchestration of NVIDIA NIM inference microservices and powered retrieval and response quality with NVIDIA Nemotron Rerank, Embed, and Instruct NIM microservices. That stack lets clinicians ask natural-language questions against a continuously updated knowledge base, receive evidence-based answers in their own language, and use the system as a practical point-of-care assistant instead of relying on slow manual search or tag-based workflows.
Data flow
A clinician submits a natural-language question to CMES-AI, the platform retrieves relevant medical knowledge, NVIDIA Nemotron Rerank, Embed, and Instruct NIM microservices refine and answer the request through NVIDIA NIM, and the Jetson-based clinic deployment returns an evidence-based response locally.
Solution architecture
5 components · 2 layers
Compute
NVIDIA T4 Tensor Core GPUHandles model training and fine-tuning for the clinical LLM stack.
Serving
CMES-AIProvides the clinician-facing assistant and knowledge access workflow used in training centers and clinics.
NVIDIA Jetson Nano Developer KitRuns the assistant locally in clinics so care teams can use it even with limited connectivity.
NVIDIA NIMSupplies the inference microservice layer that speeds up query execution and response delivery.
NVIDIA Nemotron Rerank, Embed, and Instruct NIM microservicesPower retrieval, ranking, embedding, and answer generation for natural-language medical queries.
Architecture clues
CMES-AI is being tested in six sites across The Gambia, Papua New Guinea, and Ecuador.
The clinic deployment uses Jetson hardware so the assistant can keep running even in limited-connectivity environments.
The system moved from tag-based processing to natural-language queries after the NVIDIA acceleration work.
Evidence from the source
By minimizing latency while maximizing referential accuracy, CMES-AI moved from “tag-based processing” to “natural language queries,” enabling caregivers to access richer insights at the point of care.
CMES supports over 17,000 healthcare practitioners across 19 low- and middle-income countries, improving care for 20 million people each year.
Powered by NVIDIA NIM™, query response time dropped from 5 minutes to just 2 seconds.
Powered by NVIDIA Nemotron™ Rerank, Embed, and Instruct NIM microservices, CMES slashed query processing time from 5 minutes to just 2 seconds.
Token processing speed also jumped 22x—from 0.83 to 18.23 tokens per second—delivering faster, richer medical insights.
Review how this reference was scored and trace each normalized claim back to its documented source.
01
Scoring methodology
How scores are calculated
Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.
Customer reference value100/100
Problem clarity20/20
Measures whether the customer's operational problem is specific enough to compare.
Implementation depth25/25
Rewards named components, data flow, integrations, and architecture detail.
Outcome specificity20/20
Measures whether the reported benefit is concrete rather than a generic claim.
Quantified impact25/25
5 metrics describe measurable impact.
Deployment scale10/10
Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
Source authority20/25
The main evidence is an official vendor-published customer story.
Claim traceability23/25
11 of 12 key fields link to a named source.
Direct evidence20/20
5 direct source quotes retained.
Date provenance10/10
The publication date comes from the source page or publisher.
With your OK, we use Google Analytics cookies to see which pages and searches are useful. No ads, no profiling, and
nothing is loaded until you accept. You can change this any time under “Cookie settings” in the footer.