OHDSI / OHDSI/WebAPI

Case Cohort Builder

Open
#2,397 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
151
Forks
183
Avg merge
14m
Merged PRs (30d)
2

Description

Expected behavior

Similar to the ability for the HADES tools in Cohort Incidence package where cases of cohort O are identified from an underlying target cohort (T). This identified cohort is then a numerator to either a persons at risk or person-time denominator. There should be a way in cohort definitions to start with a cohort add a time at risk (index to cohort exit or index to fixed number of days) and identify those with membership in an outcome cohort whilst at risk to instantiate this numerator cohort for profile review or additional characterization activities.

Actual behavior

Current state requires rebuilding the entire target cohort with a condition of inclusion being the presence of the outcome in a time at risk. Which if left as a main feature would lead many users to potentially build in immortal time using features aka membership in cohorts post index to define baseline cohort conditions.

Steps to reproduce behavior

None. This would be a new feature. In theory this process would create a blue underlined hyperlink of the cases in the Incidence Rates tab that could build the .json cohort definition to fully instantiate the cohort of cases T with O in TAR.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the cohort definitions and the Incidence Rates tab described in the issue, including how HADES identifies cases from a target cohort. Define the required behavior for time-at-risk and outcome-cohort membership, then determine how the cases link should produce a complete JSON cohort definition; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.