In OHDSI we perform studies across our network of databases generating results. The way we currently disseminate these results is through papers such as our recent paper on treatment pathways for chronic diseases. However, the idea of a static PDF of eight pages as our end product does not fit OHDSI’s tendency to doing large-scale analyses and building informatics solutions rather than performing studies.
How should we disseminate OHDSI results? Some ideas to put one the table:
- We could have a database server that just houses all results from each study in its own database, without trying to harmonize across studies.We briefly tried that in the past.
- We could create a single database of all OHDSI results, and define a unified data model that could hold all of that. FYI: I proposed something like that several years back, and called it FLOC (Formalized Latent Observational Characteristics). It was a nightmare we abandoned, since the model become more complex than the process for generating the data.
- We could build interactive apps per study for navigating the result set. I’ve recently converted to shiny-ism, and we could easily make interactive apps like this example using CDC data. What I like about this particular example is that it is continually updated. There is no publication date after which the data collection stops.
These options aren’t mutually exclusive. I think all options still requires a paper to accompany the result set or app, for one because peer review ‘validates’ the science behind the data. (Insert your snarky comment on peer review here )
I already discussed these ideas with @Rijnbeek. I’m looking forward to what other people have to say!