Use Case and Dataset Status

Where 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 priority 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.

Questions about a use case or dataset that do not need a tracked issue belong in GitHub Discussions. To propose a use case, see Get Started. To request a dataset, open a data source request.


Use cases


Dataset requests


How use cases shape the toolchain

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?


How to read this page

  • Status. The Status of the item on the project board: Idea, Proposed, To do, In progress, Blocked or Complete. Exceptions: On hold (issue labeled On Hold), Superseded (replaced by another use case) and Complete (issue closed) take precedence.
  • Dependencies. Issues listed under “Depends On” or in a task list on the use case (or dataset request) issue, with open or closed state. Progress is the number of those that are closed. A dataset request lists the use cases that depend on it under “Needed by”.
  • Requested. The date the issue was opened.
  • External owner. The person or organization outside the working group that asked for it.
  • WG owner. The working group member assigned to the issue.
  • Candidate data. Datasets from the Data Inventory that fit the use case’s data needs (themes, geography, region), refreshed weekly. They are suggestions until a maintainer replies /confirm <id> on the use case issue; confirmed datasets show with a check mark. Rejected suggestions (/reject <id>) disappear, and /no-data-needed marks a use case that needs no external dataset. The board’s Data match field shows the same state: Suggested, Confirmed, None found or Not needed. Use cases whose data needs have not been filled in yet are not matched.
  • Priority. Now, Next or Later, set by the working group at the weekly meeting (the board’s Priority field). Rows are listed with Now first. The column appears once priorities are set on the board.