How are you storing or modelling your visits/episodes?

Implementation
1

In the context of mapping openEHR into OMOP we want to be as exhaustive as possible and provide as many alternatives to generate visits from openEHR data as possible. If your organization is supporting this kind of grouping of the data, what is a visit/episode* for your organization?

As an example, some of you may be using CKM Episode of care Admin entry. Other repositories such as Highmed contain Admin entry archetypes that deal with this, and seems like Apperta also developed an Inpatient admission, etc.

*While technically they are not the same, there is probably places that are doing either/both

2 Likes
2

I think using FOLDERs is the way to go to model episodes. But I could see a COMPOSITION with DV_EHR_URI work as well. @chunlan.ma and @sebastian.iancu have different implementations.

There’s been some previous discussions on this topic. Probably on discourse, but also on Jira/confluence. Would be good to include that.

Be careful that the term ‘episode’ is very overloaded.
So a generic mapping of all episodes to OMOP episode seems dangerous. How well defined is the concept in OMOP? Does it vary per study?

1 Like
3

OMOP distinguishes visits (when patient got admitted/discharged) and episode (e.g. a diseases, chemo treatments). We are mainly interested on the first ones right now, as second ones usually imply data curation and/or folders as you say. In principle, every condition, observation, etc. in OMOP can be related to the visit.
Omop visits have a high level abstraction (inpatient, outpatient, ER, etc.) so realistically should be dependent of the context of the data. Our idea is to add a new “visit” type of OMOCL mapping that could extract the relevant start and end dates from existing data, being that admin_entry, context, etc. I can see that info available in the folder structure (there are no folder archetypes in any CKM, but they could potentially exist now in local installations)

1 Like