OHDSI / OncologyWG

Oncology Working Group Repository
https://ohdsi.github.io/OncologyWG
Apache License 2.0
56 stars 24 forks source link

Procedure relation hierarchies #583

Open rtmill opened 1 year ago

rtmill commented 1 year ago

https://github.com/OHDSI/OncologyWG/discussions/484

golozara commented 1 year ago

@mgurley to bring the proposal in

kzollove commented 12 months ago

From #484:

Problem Space

It is usually burdensome or impossible to query for procedures with specific context when creating a phenotype. Those include:

Proposed Solutions

Create standard hierarchies of concepts that can be used relationally to identify procedures based on context. These concepts would be leveraged similarly to how "site" and "histology" are related to ICDO3 concepts, i.e. "has site", "has histology" in the concept relationship table.

An aside, one of the difficulties that has slowed this down classifying procedures is the existence of data that contains 'high level' treatments, such as just the term "Chemotherapy", e.g. within tumor registries. This solution would have those concepts map to procedures (i.e. Chemotherapy, nos) but also have these same relational concepts (i.e. "has cancer procedure type: chemotherapy") associated with them.

Diagram from @mgurley showing a mock-up of a "Procedure type" hierarchy: image

Additional questions from @mgurley

1) Can we build or steal? If so from where? 2) How many levels should be within the Treatment Hierarchy above existing procedure codes? 3) What domain? Procedure or something different? 4) Can we eliminate the Regimen domain and use Procedure for all? 5) Are we ok with cross-domain hierarchical relationships?

kzollove commented 12 months ago

From #484:

Some example use cases:

Give me all the standard procedure concepts, across all vocabularies, that....