Mark Herringer edited this page Apr 24, 2018 · 33 revisions

Healthsites is a framework for capturing, publishing and sharing baseline health facility data to help make these facilities more accessible and relevant to the communities they serve.

Vision

To build a curated, open data commons of health facility data with OpenStreetMap

Supporting objectives

  • Our objective is to publish accessible health sites data to OpenStreetMap that is accurate and complete
  • Accessible data
  • People must be able to access accurate health care information in their area through a spatial lookup
  • Healthsites.io must be interoperable with other systems
  • The data is available from a link on the web site
  • The data is available under an open license (ODBL)
  • The data is available for download in accessible formats like .csv, shp, kml etc.
  • The data is available through an API
  • healthsites.io uses the OpenStreetMap data infrastructure to store the data

Accurate

  • The data is up to date and accurate
  • The data is part of a lifecycle
  • The data is validated by users
  • The data has provenance so it is traceable back to its source

Complete

  • We've managed to fill all the attributes for a location
  • We've managed to engage with all the major health care data sources and organizations

In scope development

Currently we are working towards the development of the following functionality:

Overview

For an overview please see our concept note

In scope development

Template update

Location upload tool

Government Health Ministries and health care organizations who wish to make their facilities available under an open data license will be able to upload health care locations to healthsites.io The tool will allow the user to check the upload and perform trial uploads before proceeding.

Location Validation Framework

We will use a reputation system where each healthsite is awarded points that speak to the credibility of the data at that healthsite.

Points are awarded based on interactions with the site, and lost when no interactions occur. For example if 100 people validate a site as being correct over a year, we will score the data highly. If nobody validates a site over a time period, it may lose credibility points. Validators will be pluggable and we invite software developers to create new validators.

Exporter

Organizations wishing to download data will be able to do this in accessible formats such as GEOJSON, SHP, CSV

API

Developers wishing to include healthsites.io data in their application will be able to make use of the API and associated documentation to do so.

Synchronise with OpenStreetMap (OSM)

The data curated on healthsites.io will be sychronised with OpenStreetMap. The Healthsites data curation process will improve the quality of health care location data and feed this impoved data back into OpenStreetMap. This will be the healthsite value add to the health location data lifecycle.

Data model

We use a key value store to provide a conceptual model like this (subject to revision):

In this model:

  • A domain defines a domain (e.g. 'clinics')
  • The list of properties that can be configured for a particular domain are defined in the attributes table.
  • The list of spatial entities that are related to a domain are store in the locality table.
  • A value defines the particular state for a given attribute for a single locality.

Conceptual-mappings

In order to import data into the data model, you need to provide a conceptual mapping between the source dataset and the Healthsites domain (group) schema.

https://github.com/healthsites/healthsites/wiki/Healthsite-attributes

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.