
AMR Project for Ukirine
A national-level AMR surveillance project
designed to standardize data, strengthen laboratory capacity, and implement real-time antimicrobial resistance monitoring using AI and ontology-driven infrastructure—supporting global health security during crisis and recovery.
[ TIMELINE ]
In progress
[ CLIENT ]
WHO GLASS & こうせいろうどうしょう
[ INDUSTRY ]
Government
Medical
[ CHALLENGE ]
Why AMR Projects Are Urgently Needed During the Ukraine War
Collapse of Medical Infrastructure and Rising Infections
The war in Ukraine has severely damaged hospitals, clinics, and laboratories, leading to deteriorated hygiene conditions and a sharp increase in infections such as wound infections, post-surgical complications, and community-acquired diseases.Widespread and Unregulated Use of Antibiotics
In war zones, antibiotics are often overused for infection prevention. Without proper prescription control, this creates an ideal environment for the rapid emergence and spread of antimicrobial-resistant organisms.Mass Displacement and Cross-Border Transmission
Millions of refugees have fled Ukraine, increasing the risk of cross-border spread of resistant bacteria across Europe and neighboring regions.Lack of Real-Time Surveillance
Ukraine currently lacks sufficient AMR surveillance infrastructure, posing a risk not only to the country but to global and regional health security as well.Laying the Groundwork for Post-War Recovery
AMR surveillance and response systems must be built now to support post-war reconstruction and establish sustainable infectious disease management systems for the future.
Challenges in Developing an AMR Surveillance System
In conclusion, the AMR project is not merely a public health initiative—it is a critical element of wartime response, post-conflict recovery planning, and the protection of European and global health security.
1. Data fragmentation and lack of standardization
Health facilities often use different formats and coding systems for reporting AST results, microbial names, antibiotic abbreviations, and diagnoses. Many rely on paper-based records, making integration across regions extremely difficult. Unstructured text reports further complicate automated processing and analysis.
2. Inconsistent laboratory capacity and quality
Laboratories vary widely in terms of diagnostic equipment, microbiological techniques, and technician skill levels. This leads to non-uniform data quality, poor reproducibility, and unreliable national-level surveillance outcomes.
3. Lack of real-time surveillance and integrated analytics
AMR reporting in many low-resource or post-conflict regions is retrospective, manual, and disconnected. There is limited capacity to monitor resistance trends as they emerge or respond to them in real-time at a national scale.
4. No unified semantic layer or domain-specific ontology
The absence of a structured semantic framework hinders the meaningful linking of data across hospitals, labs, and regions. Without standard definitions of organisms, drugs, sample types, and resistance interpretations, data aggregation and AI-driven analytics remain inaccurate.
5. Antibiotic consumption data is not linked with resistance data
Prescription records are often siloed from resistance test results, making it difficult to analyze the correlation between drug usage patterns and rising resistance. Additionally, there's limited differentiation between treatment, prophylaxis, and empirical use.
6. Shortage of trained technical and interdisciplinary staff
Running an AMR surveillance system requires expertise in microbiology, health informatics, data governance, and epidemiology—roles that are in short supply, especially in fragile or transitioning health systems.
7. Weak feedback loops between surveillance and public health action
Even when resistance data is collected, it is rarely translated into timely policy, regulation, or clinical interventions. The system often fails to inform antibiotic stewardship, procurement strategies, or infection control policy.
[ SOLUTION ]
Solutions for AMR Surveillance System Development
1. Implement data standardization using international protocols
Use HL7 FHIR for system interoperability, LOINC for lab results, and GLASS-compatible formats for resistance reporting. Digitize paper records using OCR and define structured reporting templates to ensure uniformity across sites.
2. Establish a tiered laboratory certification and support system
Designate regional AMR reference labs and implement national EQA (External Quality Assessment) programs. Equip labs with standardized SOPs, automated diagnostics, and targeted training to elevate and harmonize testing capabilities.
3. Build a real-time, cloud-based surveillance architecture
Develop a centralized digital platform with automated data ingestion, real-time dashboards, and analytics pipelines. Integrate APIs between hospitals, labs, and national authorities to allow live reporting and visualization of resistance trends.
4. Develop an AMR-specific ontology and semantic mapping layer
Create a unified ontology for bacterial taxonomy, antibiotics, sample types, and resistance outcomes. Map this ontology to existing hospital EMRs and lab systems, and apply NLP tools to structure free-text lab reports into analyzable formats.
5. Integrate antibiotic usage data with surveillance indicators
Collect ATC-coded prescription data and link it to AST results and clinical diagnoses (ICD-10 codes). Use correlation models and time-series analysis to identify relationships between drug usage trends and emerging resistance patterns.
6. Build local technical capacity through training and centralized support
Establish a national AMR analytics hub staffed with specialists who can support regional systems remotely. Simultaneously, implement national training programs to build a new generation of professionals skilled in digital surveillance and AMR data interpretation.
7. Strengthen data-to-policy pathways through automated reporting and alerts
Develop role-specific dashboards for decision-makers at the Ministry of Health and local health offices. Integrate threshold-based alert systems to trigger investigations or stewardship interventions. Generate automated monthly and quarterly reports for policy engagement.
[ RESULTS ]
In progress
Now