OHDSI / OHDSI/Characterization

Strategus Characterization Module - Dechallenge Rechallenge should restrict to one observation period

Open
#27 3 comments 0 reactions 1 assignee View on GitHub

@jreps is already working on this.

Since Apr 26, 2024.

Dominant language
R
Stars
3
Forks
6
Avg merge
2h 11m
Merged PRs (30d)
4

Description

In the Dechallenge/Rechallenge analysis that is included in the Strategus Characterization module, a condition should be added to restrict the analysis to a single observation period. In a recent analysis using Strategus, I had a single patient appear in the "challenge fails" plot which showed an initial period of exposure to the drug-of-interest with an event occurring during exposure time, after which the patient appeared to discontinue the drug-of-interest. This apparent discontinuation was followed by a long (multi-year) gap with no observation of exposure or events. After several years, the plot showed the patient re-initiating the drug (rechallenge) at which point several events occurred during time-on-treatment. Thus, this patient appears to be a compelling example of initial treatment with an event, a dechallenge success followed by a rechallenge fail. However, I inspected the patient profile for this person, I realized that for the entire period of time between discontinuing the initial treatment with the drug-of-interest and re-initiating the drug of interest the patient was not enrolled in the database.

As a solution to this problem, I would advise either 1) restricting the dechallenge/rechallenge analysis to a single observation period or 2) allow multiple observation periods as long as the gap between them is below some threshold (e.g. 30 days).

I am happy to share specific plots and data points that informed the above issue submission. If that would be helpful please reach out to me at mconove1@its.jnj.com.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.