We keep them all. The real reason is because I haven’t given it too much thought, although I hear your point. That said, let me play devil’s advocate for a bit. Not only can I envision potential use cases built around frequency of telephone encounters as one component of a proxy score for healthcare utilization, but also, if our CDM instance is ever going to serve the purposes of a data warehouse, we need to keep the notes that correspond to these visits - and as far as I know all the telephone encounters have an associated note, even if it’s 'tried to leave vm with pt - wrong #." I don’t want to get into the business of determining what notes are and aren’t useful later on down the line.
In yesterday’s EHR WG meeting we discovered the expansion of the Visit vocabulary. There are now 123 standard concepts of 421 total Visit concepts.
Colorado is working on this. I call it “improper OMOP”. Most of our requestors want custom datasets, so we’ve created extension tables to hold multiple races & procedure modifiers, added extra columns for traceability and source FKs, and created our own vocabulary with relationships and hierarchies to serve the needs of our local community. However, as we have developed our CDM word is starting to get out and more people want the data in proper CDM format.
We’re building a proper OMOP view on top of the improper CDM. This will also allow us to deliver proper CDM datasets to our community and to participate in more OHDSI activities without generating the longest Achilles list ever!
We, @mgkahn and I, are always open to discuss any of the above.
This is a fantastic idea, and we’ve been kicking around something similar, in part by offering adjunct tables to the CDM standard. For example, we include a “MEASUREMENT_LOOKUP” table that offers the equivalencies between how our EHR displays labs and how they are mapped to LOINC codes and thus to CONCEPT on the backend. As I have also mentioned in the past, per @mgkahn we have been putting JSON in the source_value columns and found it invaluable as well. I was hoping to discuss this with you at the symposium but ended up unable to make it - perhaps we can try to find a time at some point.
Hi all,
Our presenter for tomorrow, Steve Lyman, will be traveling. Therefore, I am cancelling the meeting. We will reconvene on Friday, December 14. If anyone has any topics they would like to discuss on 12/14, please email so we can discuss.
The Google Doc with a very short list of issues and goals is here https://docs.google.com/document/d/12ELmThYhw6TJ_FoQpMWVDJ3rMlB5_6BkjPye1W20yUU/edit
Melanie
Friends. I started a new Forum post on this issue. Please discuss there. Haven’t looked your expansion, yet.
The EHR WG will meet tomorrow at 8am PST/11am EST (note the time change). @Christian_Reich will be presenting proposed changes to the Visit, Care Site and Provider domains.
Here’s the Zoom meeting link
EHR WG meeting is tomorrow, Friday, January 11th at 10am EST. Steve Lyman will lead the discussion on incomplete data and the impact of analytics. The Zoom meeting details remain the same as above.
EHR WG meeting is tomorrow, Friday, January 25th at 10am EST. Don Torok will lead the discussion on the different approaches of ETLing from source EHR to the CDM.
Zoom meeting details:
Join from PC, Mac, Linux, iOS or Android: https://ucdenver.zoom.us/j/4984831362
Or iPhone one-tap :
US: +16468769923,4984831362# or +16699006833,4984831362#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 876 9923 or +1 669 900 6833
Meeting ID: 498 483 1362
International numbers available: https://zoom.us/u/9hXjQ
Friends:
Our meeting is cancelled this week. Our next meeting is Feb. 22nd at 10am.
Please get in touch with me if you want to present a topic or lead a discussion!
Our next EHR WG meeting is Friday, February 22nd at 10am EST. Sam Martin and Roger Carlson will “share some of our effort to better document and measure our OMOP ETL and general validation work…Our goal is to receive general feedback before we offer this for internal implementation at other sites and possible incorporation via OHDSI.”
Zoom meeting details:
Join from PC, Mac, Linux, iOS or Android: https://ucdenver.zoom.us/j/4984831362
Or iPhone one-tap :
US: +16468769923,4984831362# or +16699006833,4984831362#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 876 9923 or +1 669 900 6833
Meeting ID: 498 483 1362
International numbers available: https://zoom.us/u/9hXjQ
EHR WG friends,
I am cancelling tomorrow’s call since we do not have an agenda item. If you would like to present or discuss a topic, please send me an email or reply to this forum post. Our next meeting is Friday, April 5th.
@MPhilofsky can you send me the invite when you have a moment.
djb2188@cumc.columbia.edu
All the best,
David Blatt
1 Like
Hi all!
At our last EHR WG meeting we discussed the format and timing for our meetings. The group decided to continue to meet every other Friday. If we don’t have a topic or presentation scheduled, we will still meet that hour and leave the agenda open. Some suggested topics: incremental ETLs, customizing the CDM (blasphemy), ETL mapping, vocabulary mapping, Usagi… Please reply to this thread with any other thoughts or ideas.
Our next meeting is Friday, April 19th at 10am EST. We will discuss “To customize or not”, a discussion on customizing the CDM for internal use cases, the problems it solves and the issues it creates
I have confirmed the presenter for our next EHR WG meeting on May 3rd at 10am EST. @anoop.yamsani from University of Colorado will present “incremental loads & full refreshes from source to OMOP CDM”. I will send an updated meeting invite/reminder the last week of April/first week of May.
Could you please add me avnish@psu.edu /EST time.
1 Like
Hi All,
I am attaching the slides & pathology mappings from @mgurley’s presentation on Friday, May 17th.
omop_surgery_pathology_northwestern_mgurley_05_17_2019.pdf (908.8 KB)
EHR_WG_5-17_prefix_group_TO_snomed.xlsx (11.3 KB)
Hello EHR WG friends 
In tomorrow’s meeting we will discuss the recent Themis Hack-a-thon, @aostropolets’s study, and my proposal to add an additional column to the Device Exposure table. I do not think these 3 topics will take the full hour. Therefore, If we have additional time, I will open the conversation for any other topics.