How to store the reason of drug discontinuation in DRUG_EXPOSURE.stop_reason field
@clairblacketer がすでに取り組んでいます。
2024年4月12日 から。
評価
この issue はまだ評価されていません。
説明
How to store the reason of drug discontinuation in DRUG_EXPOSURE.stop_reason field
CDM or THEMIS convention?
THEMIS
Table or Field level?
Field
Is this a general convention?
No
Summary of issues
-
In OHDSI Forum, someone want to store drug discontinuation reason in CDM v6.0 but found the DRUG_EXPOSURE.stop_reason is deprecated. Then how to store the stop reason now?
-
How to store the "drug suspension due to unknown reason" and "drug suspension due to adverse effect" in DRUG_EXPOSURE.stop_reason field?
Summary of answer
-
Now the active version is v5.4. Can use the stop_reason field in DRUG_EXPOSURE table.
For "drug suspension due to unknown reason" situation: need to fix the drug_exposure_end_date. If there is no reason, don't populate stop_reason field (rather than saying "no reason").
For "drug suspension due to adverse effect" situation: Christian says it's better not to store adverse effect reason into stop_reason field. Because the idea of the OMOP CDM and the expectation of the analyst, is to store the medical fact, not some intensions of some doctors.
For example, the patient stopped mesalazine due to nausea. Although there is a reason given here, but its value is low: Whether or not the nausea is due to the drug or something else - neither the patient nor the doctor knows. It’s a guess. At the end of the day it is not possible to know if something is an adverse effect. Only statistics of a population can tell us if there is a risk. Which means, it is the outcome of the research, not the input.
Bottom line: Write Nausea into CONDITION_OCCURRENCE at the date the drug was stopped and be done with it. Feel free to add it as a stop reason, but probably nobody will ever pick it up for research.
- For fixing the drug_exposure_end_date, if we only know the decision (datetime) to stop the treatment was taken, but it does not specify when the action was applied? Christian suggests, typically, if the decision is taken it takes effect immediately.
Related links
OHDSI Forum: https://forums.ohdsi.org/t/alternative-to-v6-0-deprecation-of-cdm-drug-exposure-stop-reason-column/20905
Other comments/notes
Although Chtistian suggests not to store "adverse effect" reason into stop_reason field, he also says feel free to add it as a stop reason but probably nobody will ever pick it up for reasearch. In my opinion, some people/institutions may want to store stop reason for their own use. Thus, if we create THEMIS convension, I think we can say: although it is not suggested to store adverse effect into stop_reason field, it also depends on their own decision whether want to store adverse effect into stop_reason field.
A good idea is also to store the stop reason: adverse effect (e.g. Nausea) into the CONDITION_OCCURRENCE table.
- 主要言語
- HTML
- スター
- 1.1k
- フォーク
- 513
- 平均マージ
- 8日 3時間
- マージ済み PR(30日)
- 4
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
OHDSI/CommonDataModel のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 74/100
OHDSI/CommonDataModel#802 · コメント 1 件 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
OHDSI/CommonDataModel#799 ·
-
fix: mark cohort_definition_id as primary key in cohort_definition table for v5.3 and v5.4対応中かも @rtmalikian が 138 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
OHDSI/CommonDataModel#787 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
OHDSI/CommonDataModel#784 ·
-
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
OHDSI/CommonDataModel#823 ·