OHDSI Home | Forums | Wiki | Github

Visit concepts - snomed-ct procedures

Vocabulary Users
#1

@Christian_Reich

Would it be possible to assign some of the procedure concepts in SNOMED that refer to patient encounters to the visit domain - i.e., some of the child concepts of 308335008 | Patient encounter procedure (procedure) | ?

Here’s a partial list of concepts where vocabulary is SNOMED, domain is procedure, and concept name includes the term ‘encounter’ or ‘visit’.

Concept highlighted in yellow are some we have in our source data. Some of these (telephone encounter) are high volume encounters for which no OMOP visit concept exists.

image
image1072×553 21.7 KB

1 Like
#2

Do you want to put these guys into the visit_source_concept_id, and in visit_concept_id you put Telehealth?

#3

Hmm… I think that may require more discussion with the broader OHDSI community.

Our team ultimately decided to use the non-standard SNOMED telephone encounter concept id in both fields when we got push back from folks arguing that telephone encounters were not telehealth.

Note - there a lots of visits in the SNOMED procedure hierarchy that aren’t telehealth related that also need to be sorted…

Piper

#4

All good. I would collect the analytical use cases (“Compare outcomes of telephone vs video calls for patients…”) and then develop the desired semantic space. And then we shop it around with the OHDSI community and put it in.

Do I have to scold, or is the fear of that already sufficient to have you stop sinning? :slight_smile:

#5

Yes, you have to scold! Just not me - I went down kicking, but was over-ruled nonetheless. :woozy_face:

#6

I’m here to discuss :slight_smile:

and

I’ve been in this position. I lost the argument and we went with non-standards. Then we participated in a network study which utilized the OMOP CDM. The study coordinators came back and scolded us for using non-standard concept_ids in the standard concept_id fields. And we redid our ETL to use only standard concept_ids in the standard concept_id fields. This was a fabulous decision! When we need to use the non-standards, they are available in the source concept_id fields and when we participate in a collaborative study, the standard concept_ids are available for use. Win for our internal use cases and win for all collaborative studies :trophy:

1 Like
#7

@MPhilofsky thank you for putting this in writing! :wink:

I’m too new to OMOP to know when it’s okay to break the rules and when it’s not - so tend to want to stick close to recommended best practices. Why suffer for mistakes that others have already suffered for and learned from! :joy:

1 Like
#8

Exactly! Let’s share best practices and learn from one another :slight_smile:

1 Like
t