Skip to main content

Table 7 Summary of finding for SDSS core functionalities

From: A systematic review of spatial decision support systems in public health informatics supporting the identification of high risk areas for zoonotic disease outbreaks

Characteristic

Description

Most common method

Less common methods

Spatial data management

GIS based management systems that can organize and analyze spatial data

Unspecified (n = 4)

ArcGIS, Google maps, OpenLayers, QGIS, PostgreSQL, hBase, MySQL

Visualization

Visualization through maps, graphs, tables

Choropleth (n = 12)

Point layers, count overlays, panels, buttons, data entry fields, menu

Reports

Summary of scenario or analytical process, may be graphical, maps etc.

Mapping (n = 12)

Map, table, chart, statistic summary, network graph

Interactive problem solving

Environment which allows the user to explore the possible solution space for a given problem, allowing interaction within the problem-solving environment

Select area of study(n = 6)

Select species, timeframe, covariates, color theme, graph views, radius selection, query fields

Spatial modeling capability

Availability of spatial/non-spatial modeling packages

Clustering(n = 5)

Clustering, risk mapping, anomaly mapping, disease spatial distribution, networks of disease

Semi structured problem solving

Problems that are ill defined, but can accommodate imposed restrictions and user preferences

Adjust analysis parameters (n = 12)

Explore disease network, choose summary statistic, user selection of model parameters

Scenario evaluation

Decision support utilities that allow scenario analyses through iterative analyses

Adjust distribution display (n = 12)

Track different species, transmission route or outbreak simulation, generation of actionable suggestion, distribution of cases/clusters

Easy User interface

Interfaces that engage the user, and allow easy interaction

Usability testing (n = 5)

Design consultation, mental mapping of tasks, feedback surveys, pilot study, usability, and usefulness testing