# OHDSI - and openEHR

**URL:** https://discourse.openehr.org/t/ohdsi-and-openehr/308
**Category:** OHDSI OMOP
**Tags:** standards
**Created:** [4 February 2020 08:15 UTC](https://discourse.openehr.org/t/ohdsi-and-openehr/308 "2020-02-04T08:15:56Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![erik.sundvall](https://discourse.openehr.org/user_avatar/discourse.openehr.org/erik.sundvall/32/1961_2.png) [@erik.sundvall](https://discourse.openehr.org/u/erik.sundvall)
#### Post date: [12 February 2020 08:08 UTC](https://discourse.openehr.org/t/ohdsi-and-openehr/308/10 "2020-02-12T08:08:51Z")

</div>

Thanks for the interesting response!

> [@lvxd](#):
>
> Did you have experience of working with Ohdsi? Could you also share them if possible? Let’s see how we can work together in this line.

No, I have not worked with OHDSI but got very interested after hearing Georg Hripcsak’s keynote at the Medinfo 2019 conference. I would guess that a lot of “openEHR2OHDSI” integration can be done by designing good AQL-queries combined with some transformation/translation/formatting code. Probably some kind of two-way flow where parameters from OHDSI requests are used in the AQL etc. You have probably looked deeper into this than me, what do you think will be needed?

Right now we (Region Östergötland) are busy doing a proper openEHR procurement (see [Swedish openEHR procurements & RFIs](https://discourse.openehr.org/t/swedish-openehr-platform-procurement-q1-2020/247/)) and will then install and implement that in suitable parts of our healthcare organization and tackle som prioritized development needs. So we’ll likely not be doing any serious “openEHR2OHDSI” until at earlieast Q4 2020, more likely some time in 2021. But at a “discussion” level we’d be interested in looking at this, so please keep this thread updated with thoughts and findings if possible.

---

_[View the full topic](https://discourse.openehr.org/t/ohdsi-and-openehr/308)._