Requirements for a data sharing solution

Researchers
6

Thanks Nick for sharing that, and sorry I missed Arachne earlier.

I’m worried that we’re starting to mix many different things in this discussion. I started with saying some files are too big for e-mail and we need a solution for that, and now we’re talking about a full research infrastructure.

In my humble opinion, the OHDSI research infrastructure should have roughly these components:

Database Wiki (building on our current single page)

  • One Wiki page per database in OHDSI
  • Each site maintains own Wiki page
  • Need template for these pages, which should include:
  • Country?
  • Nature of database (claims? Hospital EHR?)
  • Contact details
  • With possibility to link to Achilles or Iris results

(This Wiki should be brief in my opinion. Several initiatives like this already exist, relying on huge questionaires. I’m skeptical about the value of those)

Workflow management system

  • Ability to register new study with lead investigator and participating sites
  • Keeps track of requests and files sent
  • Supports web forms
  • Will send reminders

Analysis sharing technology

  • Study R packages (like those in our StudyProtocols repo)
  • SQL
  • Circe / Calypso definitions + Heracles results?

Data sharing technology

  • E-mail
  • FTP?
  • Amazon S3?

Common quality framework

  • Share at least Achilles Heel results on database Wiki?
  • Needs much work!

Common Data Model

  • OMOP CDM

Common software stack

  • WebAPI
  • Atlas
  • R

Common technology stack (for the database sites)

  • Windows, MacOs, or Linux
  • PostgreSQL, Oracle, Sql Server, RedShift, or Microsoft APS
  • Possible tiers of technology stack (e.g. Amazon Cloud able, GPUs available, beefy machines for advanced analytics)

For now, I’d just like to think about a data sharing solution, but I agree we should keep in mind how this will fit together with all the other pieces of the puzzle.

@Frank: How does this fit with the ideas of the Achitecture workgroup?

1 Like