How to store family history in the OBSERVATION table

Aperta
  • Qualcosa non va?
#656 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@MelaniePhilofsky ci sta già lavorando.

Dal 16/4/2024.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Documentation

How to store family history in the OBSERVATION table

CDM or THEMIS convention?

CDM

Table or Field level?

Table

Is this a general convention?

No

Summary of issues

  1. If these is an established best practice for representing family history in the OBSERVATION table? There seems 2 options for this family history.
    Image

Summary of answer

  1. Melanie https://forums.ohdsi.org/t/how-to-represent-family-history/3386/45
    There are 2 ways: The first is the OBSERVATION.observation_concept_id = 4210989 (Family history with explicit context) and the disease/condition is found in the OBSERVATION.value_as_concept_id = 317009 (Asthma).
    Or the data might be the pre-coordinated with 4051241 (Family history of asthma).

  2. Erica Voss https://forums.ohdsi.org/t/how-to-represent-family-history/3386/9
    RECOMMENDATION:
    If we have a matching concept in SNOMED, then use the respective observation_ concept_id.
    If we do NOT have a matching SNOMED code, then observation_concept_id should be ‘4210989 Family history with explicit context’ and value_as_concept_id should be the related procedure, condition etc.

ACTION:
Add as a convention under the OBSERVATION page.

  1. Alexander Davydov https://forums.ohdsi.org/t/how-to-represent-family-history/3386/47
    Be careful with the 4210989 (Family history with explicit context). One of the descendant branch is 4051104 (No family history of). So when you pick the top-level guy you don't actually say whether it's happened or not.
    So it's better to pick more specific, e.g. 4167217 (Family history of clinical finding) or 4051255 (Family history with explicit context pertaining to mother).

Related links

OHDSI Forum: https://forums.ohdsi.org/t/how-to-represent-family-history/3386

Other comments/notes

From my side, I prefer to

  1. Firstly, use specific observation domain standard concept which represent the family history directly, e.g. 4051241 (Family history of asthma).
  2. Secondly, if I cannot find a specific standard concept directly, then use 4167217 (Family history of clinical finding) as OBSERVATION.observation_concept_id and 317009 as OBSERVATION.value_as_concept_id.

We have ETL Conversion projects in our organization. I used this logic for our OMOP CDM database. Yang, Qi is my colleague. I also discussed this logic with him before.

@MelaniePhilofsky, @clairblacketer, I am not sure if there is a convention on Family history data now.
According to the discussion in this OHDSI Forum post, Melanie suggested the logic for how to store family history into OBSERVATION table. But is there any order for which way should be first? And if it is a good choice to replace 4210989 (Family history with explicit context) with 4167217 (Family history of clinical finding)?

Lingua principale
HTML
Stelle
1.1k
Fork
515
Merge medio
8g 3h
PR unite (30g)
4

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OHDSI/CommonDataModel

Tutte le issue di OHDSI/CommonDataModel

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.