Visit Ambiguity Primary Thread

[MelaniePhilofsky]

The Visit sub-group made good progress during the Vocabul-a-thon at the OHDSI Symposium. Here is the power point 2 we used to outline the problem statement, delineate the steps to solve the problem, post what we accomplished during the event (see green text), and give us our next steps. If you are interested in collaborating on the Visit domain cleanup, join the Themis MS Teams Visit sub-group channel, and respond to this thread or DM me with your email address and I will set up a doodle poll for meetings.

Accomplishments

• Outlined use cases for Visits

• Historically, Visits have been used as a proxy for severity. Per the group, this is the main use case. Examples:

  a. Inpatient pneumonia vs outpatient pneumonia
  b. Inpatient abdominal surgery vs outpatient abdominal surgery

Reviewed the [definition of an OMOP Visit](https://ohdsi.github.io/CommonDataModel/cdm54.html#visit_occurrence) is this satisfactory?

• Yes, however, there is a need for further disambiguation of Outpatient “Telehealth” visits; real time vs asynchronous
• Define “Telehealth”; does this include emails and messages to providers?

Next steps

• Review the accomplishments, add to Repository name not camel case #1 and Case to store the history of location change in Observation table #2 as needed

• Review standard Visit concepts
  a. Athena has 266 standard visit concepts; what do we have?
  b. Link to the standard concepts in Athena

• Delineate ambiguity, gaps, duplication, etc.

• Create 1 or more proposals to enhance the Visit domain

• Document, document and more documentation on the use cases, decisions made, rationale behind the decision, changes to the CDM (if needed), changes to the Vocabs (if needed), ETL guidance, and end user (analyst/researcher) guidance.