@Ian McNicoll brought up what we could do with OMOP and openEHR.
@Seref Arikan it’s a God schema. Common use case (usually pharma) is FHIR → OMOP, which gets too hard and becomes FHIR → openEHR → OMOP.
@Thomas Beale is an openEHR → OMOP ETL product/tool the end game?
@Ian McNicoll could build a limited exemplar?
@Diego Bosca openEHR + Snomed makes it easier to generate OMOP output. Tables are ‘pretty simple’, so not tooo hard. Relatively clear mapping for procedures, diagnoses, devices etc. We are doing some mapping already. At least some automatic mapping likely to be possible. Idea is to put all your data, even if no clear mapping. Existing approaches are 1-by-1, use case based.
Important: OMOP data is very patient-centric, i.e. based around a ‘patient/person’ object. Demographic related data may be a bit harder since less clear in openEHR. Clinical is however straightforward.
@Jake Smolka OMOP not in HighMed right now, but some project(s) where OMOP implicated - @Birger Haarbrandt for news…
@Seref Arikan look at FHIR-based OMOP mapping approaches, including Vita/EhrBase FHIR-bridge etc which may be a basis to start with.