Home › Capabilities › Vector & Reservoir Surveillance

Vector and reservoir surveillance, in your LIMS

Pooled testing, collection-lot management, species reference data, and the surveillance reporting your ministry actually files. Built for public-health programs that need every mosquito, rodent, and flea in the dataset — not in a parallel spreadsheet.

Try the demo Part of One Health

Why it matters

Vector surveillance — mosquito, rodent, flea, and tick collection programs — is the early-warning system for arboviruses, plague, leptospirosis, and outbreak-prone diseases that don't make headlines until they do. Most lab software has no model for the entities surveillance programs actually work with: collection lots, pools, species hierarchies. OpenELIS adds those as first-class entities in the same LIMS that handles the clinical work — so a positive pool can trigger a reflex follow-up on the same platform.

Key capabilities

Collection-lot management

A trap, a transect, a night's catch — a "lot" is the right abstraction, not a single sample. Collection lots carry method, GPS, time window, weather, and species composition; sub-samples and pools roll up to the lot.

Pooled testing built in

Configurable pool sizes and pooling logic. Track which specimens went into which pool, the dilution ratio, and the rolled-up positivity rate at pool, lot, and site level — with deconvolution to make a positive pool actionable at the specimen level.

Species reference data

Mosquitoes (Aedes aegypti, Anopheles gambiae, Culex), rodents, fleas, ticks. A hierarchical taxonomy (family → genus → species) ships with the module so records use validated names, editable per deployment.

Surveillance reporting

Dashboards plus surveillance report exports for ministry submission, including the Vector Host Index — blood-meal analysis and Human Blood Index — the metrics arbovirus risk assessment actually needs.

Under the hood

Vector & reservoir surveillance reuses the same OpenELIS sample/test/result core, with two additions: the collection lot (a parent grouping specimens) and the pool (a derived sample of multiple specimens with a known dilution ratio). Both are first-class entities; the rest is config.

CollectionLot model. Collection metadata (GPS, time window, trap type, conditions); specimen list with per-specimen species and stage.
Pool entity. Configurable pool size; dilution ratios captured at creation; positivity traceable specimen → pool → lot → site.
Species reference. Hierarchical taxonomy editable in admin; new species addable per deployment.
Lab interoperability. Vector PCR results from connected analyzers flow through the same analyzer integration framework as clinical samples — no parallel pipeline.
Audit trail. Same event model as clinical — chain of custody intrinsic to the design.

Standards: FHIR Specimen resources with extensions for pool/lot abstractions; reportable to DHIS2 and SORMAS via the OpenELIS surveillance integration layer.

Powered by the OpenELIS platform

Vector surveillance runs on the same shared engine as every other domain — the same interoperability, quality control, security, and storage.

Interoperability

Surveillance data flows to DHIS2, SORMAS, and the wider health network automatically. See platform →

Quality control

The same QC engine governs vector PCR and identification methods. See platform →

Security & audit

RBAC, SSO, and full chain-of-custody logging across every specimen. See platform →

Analyzer integration

PCR instruments connect through the same bidirectional interfaces as clinical analyzers. See platform →

Running a vector surveillance program?

OpenELIS already handles the lab side, and the vector-specific surveillance layer is built and ready. Let's talk about deployment.