SUMMARY of discussion today 2/8/23 am.
Thank you to all participants to our 1 hour discussion to help with developing our cohort defintion. @Gowtham_Rao @Azza_Shoaibi @fabkury and others (sorry didn’t catch everyone who attended)
We agreed to prioritize the unanimity algorithm with and without meds.
These were tweaked in real-time on the Atlas-Demo site (since my local instance of OMOP-CDM is not yet up and running):
The Unaminity phenotypes are on Atlas-Demo, tag [Pheb2023]
- ID: 1781748
- ID: 1781760
Paper referencing these algorithms: Optimizing algorithms to identify Parkinson's disease cases within an administrative database - PubMed
OHDSI team will help clean up/review logic of the Atlas Demo cohorts and check the concept sets in readiness for a network study.
The tiered consensus logic is challenging to adapt. The cohort definition post included a outline of how this COULD be implemented in Atlas. It is also challenging to use specialty as a criterion when we suspect different OMOP-CDM instances may vary in how this is loaded/coded.
I believe it is worth attempting an implemenation of the tiered consensus algorithm (a) because it has a promise of improved sensitivity, specificity, PPV and (b) may help identify gaps in OMOP-CDM implementations.
Also, need to consider the Phea SQL builder for more complex logic that tiered consensus algorithm may be able to utilize.