OHDSI GIS
WGWhere the working group’s use cases and dataset requests stand. Use
cases come from issues labeled Use Case in OHDSI/GIS;
dataset requests come from OHDSI/gaiaCatalog
(plus a few older ones in OHDSI/GIS). Status, dates and dependencies are
read from GitHub each time the site is built. Status and rank come from
the GIS project
board, which the working group updates at the weekly meeting.
External owners and links GitHub does not record are kept in status-config.json.
To propose a use case, see Get Started. To request a dataset, open a data source request.
Development is use-case driven. Each use case feeds one or more parts of the toolchain.
| Area | What use cases identify |
|---|---|
| Vocabulary | Missing concepts, mapping gaps, hierarchy needs and synonyms for geospatial and environmental variables |
| CDM extensions | Auxiliary table designs, fields for external_exposure
and related tables, indexing and performance needs, linkage patterns
between clinical data and geospatial sources |
| Analysis | HADES enhancements, custom libraries for geospatial processing, federated analysis protocols, exposure quality validation (see Analysis) |
To propose one, see Get Started. Proposals are reviewed against:
| Criterion | Question |
|---|---|
| Scientific rigor | Is there a clear hypothesis and study design? |
| Generalizability | Does it apply beyond a single institution or dataset? |
| Technical feasibility | Are the required geospatial data sources available? |
| Community benefit | Does it contribute to shared toolchain components? |
| OHDSI principles | Does it support open science, reproducibility and collaboration? |
On Hold), Superseded
(replaced by another use case) and Complete (issue closed) take
precedence.