Health-Informatics-UoN / Carrot-Mapper

Carrot: Convenient And Reusable Rapid Omop Transformer.
https://carrot4omop.ac.uk
MIT License
12 stars 3 forks source link

Support for auxiliary OMOP tables #625

Open thomgiles opened 5 months ago

thomgiles commented 5 months ago

Currently CaRROT only supports a limited number of the clinical tables in its data model. Ideal it would support more of the auxiliary tables for OMOP conversion of data similar to usagi.

image

One table of specific interest is the FACT_RELATIONSHIP table.

The FACT_RELATIONSHIP table contains records about the relationships between facts stored as records in any table of the CDM. Relationships can be defined between facts from the same domain, or different domains.

Examples of Fact Relationships include:

All relationships are directional, and each relationship is represented twice symmetrically within the FACT_RELATIONSHIP table. For example, two persons if person_id = 1 is the mother of person_id = 2 two records are in the FACT_RELATIONSHIP table (all strings in fact concept_id records in the Concept table:

Ie. Person, 1, Person, 2, parent of Person, 2, Person, 1, child of

There are two stages to this.

  1. Support for FACT_RELATIONSHIP conversion in CaRROT CDM
  2. Support for the generation of FACT_RELATIONSHIP rules in CaRROT ccom.
spco commented 5 months ago

This does need support, (all tables, not just FACT_RELATIONSHIP). PhilQ made the point that this might best be implemented as a standalone script after CaRROT-CDM, with CaRROT-Mapper only used to map the type of relationship. More exploration is required.

thomgiles commented 5 months ago

the FACT_RELATIONSHIP stuff (especially for MIREDA) should be do-able post ETL. Its more about CaRROT be suitable for conversion of larger clinical cohorts (that may contain a lot more information than is required for cohort discovery activities) into OMOP.