Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update of CMS Place of Service #525

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update of CMS Place of Service #525

wants to merge 1 commit into from

Conversation

hardhouse
Copy link
Contributor

No description provided.

Copy link
Contributor

@mik-ohdsi mik-ohdsi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Copy link
Member

@Alexdavv Alexdavv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good, except this new concept is missing its "Is a" relationship. We have a very limited number of top-level dogs in this Domain. And this is not the case.

@hardhouse
Copy link
Contributor Author

on what codes do you need to make 'Is a'?

@mik-ohdsi
Copy link
Contributor

Hi @Alexdavv and @hardhouse : as a matter of fact, CMS has just released a new version... there is one new addition and a name update. I also identified the best suitable hierarchically higher concept for the '58' code. The telehealth ones do not have a hierarchy...
The update list should now look like this:

Mode Code Description start date end date "Is a" relationship to concept ID
U 02 Telehealth outside Patient's Home 01.01.2022    
I 10 Telehealth at Patient's Home 01.01.2022    
I 58 Non-residential Opioid Treatment Facility 01.01.2020   38004207

I will attach an updated Excel spreadsheet to the Jira task!

@Alexdavv
Copy link
Member

name update

With the same semantics, right?

The telehealth ones

Hmm. Not sure we even need these 2 being Standard. They both are definitely the subtypes of Telehealth, but the additional context doesn't make a lot of sense in OMOP:

  • "outside Patient's Home" doesn't really tell you whether it's in- or out-patient.
  • "at Patient's Home" sounds like a subtype of Home Visit, but in fact, it's not - nobody comes to the patient Home to provide the medical services.

I'd suggest make them non-Standard and map over to the Telehealth.
@cgreich What do you think?

do not have a hierarchy...

It's pretty much like that for many service-like vocabularies. What we did in this case is building the Frankenstein out of many source vocabularies within the specific Domain. And the hierarchy we build reflects the way we expect this stuff to work in cohorts rather than how it's represented in the sources.

@mik-ohdsi
Copy link
Contributor

map over to the Telehealth.
unfortunately, one of them is already that Telehealth concept, now renamed to "Telehealth provided other than in patient's home", so they made it more specific and stole our nice Standard parent one... I suggest to make them both standard and leave them as they are.

@Alexdavv
Copy link
Member

they made it more specific and stole our nice Standard parent one

Then we need a new universal one for Telehealth in the Visit vocabulary.

I suggest to make them both standard and leave them as they are

Both as the top-level dogs? We have a very limited number of them. These 2 don't deserve it.
And what ETL would do if they don't know whether the telehealth session happened at home or not?

@cgreich
Copy link
Contributor

cgreich commented Sep 30, 2021

The two telehealth concepts are VERY similar. But if we want to keep them I would agree with @Alexdavv and make them children to a common "Telehealth" one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants