OHDSI
Working Group ActivitiesThis site has two aims: transparency (what each OHDSI working group (WG) is doing, and where to find it) and collaboration (where groups are working on the same thing and might want to talk). It is compiled automatically from public sources, plus a small amount of hand-collected MS Teams counts, and it is refreshed by hand for now (the Overview page shows the last refresh). It measures visible activity, not the quality or importance of a group’s work: a WG that meets weekly and works in Teams will look quiet here.
| Page | What it shows |
|---|---|
| Overview | The last complete week at a glance, and a heatmap whose rows can be groups (each expands into its projects), projects or topics. |
| Groups | Every working group, then a page per group: projects, outputs and recent activity, who it works with, and opportunities. |
| OKRs | The objectives and key results each working group presented, by year
(2025 and 2026 so far): on the February community calls and in the decks
on ohdsi.org/workgroups, with links to the recording and slides. Written
down by hand from the slides and recordings
(config/okrs.yml, config/okrs_2025.yml), not
reviewed by the groups; groups with none found are listed so leads can
send theirs. |
| Projects | Software and specifications between a group and its repositories: repos, releases, activity, and which projects adapt which. |
| Topics | Subjects that cut across groups, over time and at each Global Symposium, plus shared terms not yet curated. |
| Connections | A network of groups with evidence of shared work, the evidence behind each pair, and similar work in different groups. |
| Activity | A week’s digest, a calendar of upcoming meetings, or outputs over the last year. Download as CSV, copy as a forum post, follow the RSS feed, or subscribe to the calendar (.ics). |
| Source | What is counted | Notes |
|---|---|---|
| GitHub | Commits, pull requests opened and merged, issues opened, issue and PR comments, and releases in repositories assigned to the group, plus items in other groups’ repositories whose title matches a cross-tagging rule (below). Bot activity is left out. | Repository assignments are a draft made from repository names and descriptions. |
| Forums | New topics and replies on forums.ohdsi.org. | The forum has no working group categories, so each topic is matched to a group by keywords in its title, then its tags, then its category. About a third of topics are community-wide announcements, and about a fifth match no group. |
| Community calls | Weekly community calls whose title names the group (for example, “Workgroup Spotlight”). | About two thirds of calls are community-wide and count for no single group. |
| Conference | Global Symposium working group sessions (2024 to 2026) and tutorials (2024 to 2026), plus Collaborator Showcase entries (2020 to 2026). Regional events are included too: Europe (2020, 2022 to 2026), APAC (2020, 2022 to 2026), India 2024, Africa (2025, 2026), Latin America 2026 and OHDSI UK 2026. All are counted in the week the event starts. | Sessions are matched by their heading, so they are reliable. Tutorials and showcase entries are matched by title (and authors for showcase entries), so many matches are by topic: a poster about oncology counts for Oncology even if the group was not involved. Tutorials that fit no single group count as community-wide. Regional items that match no group count under “Regional chapters”. Not every regional event publishes a list: for India, Latin America, UK and Africa 2026 there is only the event itself (one linked entry), Europe 2022 to 2026 also include their weekend workshops and workgroup meetings, read from the agenda PDFs (Europe 2026 has a few typed in where the two-column layout could not be read), and APAC 2022 to 2025 lists only items with a linked poster or slides. |
| Teams | Channel posts and replies, and meeting counts, collected by hand for some groups. | Counts only. Messages and transcripts are never published. Hatched cells were not collected. |
config/item_rules.yml
adds an item to a second group when its title says it is about that
group’s work: today, titles with geo, geospatial, geographic, GIS,
PostGIS or LSOA also count for GIS, so a geospatial pull request in the
Achilles or Ares repository shows up in GIS’s activity as well as in the
repository owner’s. It is one item wherever groups are compared, and it
counts on Connections as joint work between the two groups.config/projects.yml, a first draft for
maintainers to correct (see Projects and confirmation); every
other repository is a project of its own, under the group it is assigned
to. A project can record that it extends another (for example,
copies of HADES packages that read the GIS extension tables): that is
shown as an opportunity, because support upstream would help both.
Projects are counted from GitHub only.config/collab_themes.yml. An item counts for a topic when
its title matches; commits and comments are left out, and items tagged
to more than four groups do not count toward any one group.The multi-repo groupings are proposed from repository names and the group-to-repository map, not by the projects’ maintainers. Each one is marked Draft grouping until a maintainer confirms it, and Confirmed (with the date) afterwards. The Projects page counts how many are confirmed and can filter to the drafts.
To confirm or correct a grouping, use the link on the project’s page
(it opens a pre-filled issue), or edit config/projects.yml
and add a line such as reviewed: 2026-11-20 by Ann Lee to
that project. A project is not marked confirmed by anything else: the
site only reads that line.
Each refresh checks every source: whether its newest item is recent
enough, and whether its collector ran (collectors are allowed to fail
without stopping the refresh, so this is where a failure shows). The
ohdsi.org meetings page is edited by hand; the calendar shows a notice
when it has not been updated for more than 10 days. The Overview page
links here when anything is out of date. The same checks run on every
pull request (scripts/validate_config.py and the tests in
scripts/).
Working-group meetings come from ohdsi.org’s Upcoming Working Group Calls page, which lists about four weeks ahead and each group’s usual schedule; it is read at each refresh. Community calls are on Tuesdays at 11am ET: past ones show their title and recording, later ones are listed as expected until announced. Symposium dates come from the conference list. Join links are not copied: “Join details” opens the ohdsi.org page, which always has the current link. Meeting lengths are not published, so calendar apps show one hour.
The Connections page flags places where groups may want to talk. Pairs of groups use three signals, all from item titles and links (never Teams content):
config/collab_themes.yml)
that titles from two or more groups match. “Not yet linked” pairs are
groups active on a topic with no item naming both.Planned collaborations come from the OKRs
(with: in config/okrs.yml): when one group’s
2026 OKRs say it plans to work with another, the pair is listed under
Connections, and drawn as a dotted blue line when you tick “Show
collaborations planned in the 2026 OKRs”. They are hand-read, never part
of a score, and a pair that already has evidence just gets a “planned in
OKRs” tag.
Similar work looks for the same subject in different groups’ items over the last year: named things (FHIR, DuckDB, BigQuery, CDM v5.5) and two-word phrases (“episode table”, “incidence rate”) that appear in issue, pull request, forum, call and symposium titles. A subject is listed when at least two groups each have an item of their own about it, and pairs that no item names together are marked “not yet connected”; those are drawn as dashed orange lines in the network.
Matching is by keyword, so some leads are false alarms (a word like “vocabulary” in an ATLAS pull request), and groups that collaborate without writing it in a title are missed. The topic list is a first draft for the groups to correct.
Collectors, matching rules and this site are in jshoughtaling/WGActivities.
Mapping rules live in config/working_groups.yml,
config/forum_mapping.yml, config/projects.yml
and config/collab_themes.yml; if a repository, project or
topic is assigned to the wrong group, open an issue or a pull request
there.