I’m not even sure this topic belongs in this category, but I’ll give it a go…
Thing is phenotypes that share a common ‘root’ are sometimes used for different contexts. E.g. you can think of “myocardial infarction” as a comorbidity (present on a given index date), as an outcome (present after a given index date but not before), or as an indication (e.g. present in a given time window before the initiation of a specific drug, say a statin or a betablocker).
Although one can obviously implement these in a cohort logic simply imposing certain timings, some codes are in principle useful to some of these, but not others. E.g. 4059193 H/O: migraine would be useful to identify a comorbidity/prevalent condition, but not to identify an incident event. This is of course a toy example, but things can get more complicated. E.g. long-term sequelae of a condition would probably also not be useful to identify an incident outcome, and this is not immediately obvious in the concept description, but only implicit in the clinical knowledge underlining the aetiology of the event of interest
Have others in the community looked into this before? Is there an interest to define such ‘phenotype flavours’ (for lack of a better term)?
Cabinet Battle #124,589 is open