OHDSI Home | Forums | Wiki | Github

New Comprehensive Hierarchy for Providers, Visits (and Place of Service, Specialty, Care Site)

(Peter Rijnbeek) #21

For me a consult is not related to overnight stay nor whether this is during inpatient. I can have a consult with any healthcare provider, e.g. I can have a consult with a physiotherapist to decide if we should start treatment etc.

In our country (and i think in many others as well), i do not always have to be “referred” either. I can decide to contact certain healthcare professionals and ask for a consult.

I therefore suggest not to make this a child of either inpatient or outpatient visit.

(Gowtham Rao) #22


Would it be reasonable to create new omop concepts-- inpatient-consult, outpatient-consult/referral. We may also add many parents?

(Christian Reich) #23


This is a different thing you are asking for, Peter. That’s a consultation. We have plenty of procedures for that. A consult is if one doctor is asking another doctor for help. In the inpatient setting, that other doctor usually comes to the patient.

“Referral” is an activity where one doctor sends the outpatient to another doctor, or to the hospital. Whether that is mandatory from an insurance perspective or not is irrelevant. I still don’t think we need an outpatient consult.

(Melanie Philofsky) #24

@Rijnbeek nailed it:

We have many visits within our EHR where a person has one and only one visit with a Provider. This “consult” visit is for the person to seek a 2nd opinion about a condition, course of treatment, etc. This is NOT a referral. This happens regularly for Providers at large academic centers and Children’s hospitals. People seek out an “expert”/2nd opinion.

(Peter Rijnbeek) #25

:slight_smile: i am not asking for anything.

It shows we need to be very clear on the definitions of these types, for example how could I have known this is only between doctors? I can show you examples where the word Consult is used as Visit and this is independent on whether this is coming from request of a doctor, e.g. I pay x amount per consult of my physiotherapist. This can be a language problem sure, but we will have 100 languages in OMOP-CDM. Also, do not miss-understand me, i do not suggest to use “consult” for this but we need to avoid ambiguity by being very clear on what me mean.

Even with this explanation i find the difference between consult and referral still vague (do we need this?). My GP can consult another GP in his group, is this then a referral or consult?

(Gowtham Rao) #26


Maybe it would be useful if the EHR workgroup makes a list of concepts with their descriptions that are important or frequently seen in EHR data, and then the vocabulary workgroup could review and help by proposing solution?

(Christian Reich) #27

There seem to be different understandings what a consult is. I was under the impression a consult or “medical consultation” is a request from one provider to another, not from the patient: https://medical-dictionary.thefreedictionary.com/medical+consultation or https://www.aapc.com/blog/38856-medicare-and-consults-99241-99255/. But from rummaging through the web I realize this may not be clean.

Why don’t we add three concepts:

  1. Provider asks provider for advice (=consult in my understanding, first physician keeps providing care)
  2. Provider sends patient for care to another provider (=referral, second physician takes over)
  3. Patient seeks advice from provider (=2nd opinion or @MPhilofsky’s understanding of consult).

The problem with 3) is that it is hardly distinguishable from a normal patient to doctor visit. But if you have that information we could add.

Another problem is that we need to draw the line between a Visit and a Procedure, e.g. 2514419 or 2514420. A visit is an organizational structure for providing care, not the content. So, I am not sure whether any of these consultations or referrals can be construed as Visits at all.

Let’s think.

(Burrowse) #30

A few concerns:

With the new structure, how do we determine what visits are Urgent Care Visits? In the current structure, we rely heavily on the place_of_service_concept_id (8782 - Urgent Care) in the care_site table to do this. According to the hierarchy, this is being folded in as an outpatient visit (9202). For most of our researchers, because this type of visit is associated with some level of acuity we consider it to be more of an emergency (9203) visit. From a provider perspective, there is no distinct specialty for Urgent Care. The provider may have general pediatrics or emergency care as their speciality designation. We would like to avoid using the visit_source_value to determine these things.

Overall, the idea of eliminating the care site specialty is troubling form a practical standpoint of how the data is stored in our EHR and the governance tied to care sites at our insitutions (for example to attribute the “Oncology Clinic” or “Hematology Clinic” to a visit), with no way of telling what specialty the provider was “acting” in at the time besides looking at the department and the potentially the service at the visit.

As it relates to the vist designations:

For the “Home” visit type does this include Social Work Visits? If so, will there be conventions to clearly state this?

For the “Case Management” At our organization we consider case management to be opened by a discharge planner with the intent of organizing the transition from inpatient to home care for our patients. However, it was stated on a call that this is supposed to represent administrative visits as well. Do we put Emails/Telephones encounters in this category? These are true encounters in our EHR which have providers and information pertaining to the clinical care.

As it relates to the EHR structure, consults are procedures as opposed to actual visits. We would have to manufacture a visit that represents a “consult” type becase these are included in the inpatient visit and occur as outpatient visits.

@bailey Please feel free to elaborate :slight_smile:

(Lmendezboo) #31

I deal with EHR’s,
Patients at our primary care settings have a main provider ‘a family phisician’. When the familly phisician need another specialty field to chime in (for a diagnostic or therapeutic purpose) they order a consultation (to the specialty field, not to a specific person).

This ordering gets treated as any ordering of a procedure (not any different than ordering a ‘CT scan’)

the patient may then get a visit from a person/provider of said specialty.

which is to say that there are 2 sides of these consultations, 1) the fact of ordering it, 2) and the fact of doing the thing ordered (which happens to be a visit).

  1. the ordering: could be placed in the procedures domain (if there is a suitable standard code, say “Consultation/referal to XYZ specialty”).

“the PROCEDURE_OCCURRENCE table contains records of activities or processes ORDERED BY, or carried out by, a healthcare provider on the patient to have a diagnostic or therapeutic purpose.”

  1. the doing of the referal visit may be treated as any omop visit domain fact.

and them both may be linked together by the visit_occurrence_id foreing key in the procedure_occurrence table.

as for our distinction of referals from consultations/consults, when doing a referal it is assumed the new provider will be the main phisician from now on. while a consult is the family phisician asking for diagnosing or therapeutic tasks to be defined or suggested from the other provider but the family phisician remains the main provider.

hope this helps.