OHDSI / Vocabulary-v5.0

Build process for the OHDSI Standardized Vocabularies. Currently not available as independent release.
The Unlicense
219 stars 75 forks source link

Missing CPT4 Modifier '21' #648

Closed Piper-Ranallo closed 1 year ago

Piper-Ranallo commented 2 years ago

CPT4 modifier '21' (inactivated in 2009) seems to be missing from the concept table. Should this be added?

Original defintion:

WARNING: Code Deleted 2009-01-01 21 - Prolonged Evaluation and Management Services: When the face-to-face or floor/unit service(s) provided is prolonged or otherwise greater than that usually required for the highest level of evaluation and management service within a given category, it may be identified by adding modifier 21 to the evaluation and management code number. A report may also be appropriate.Toggle Dictionary Definitions

cgreich commented 2 years ago

We could, @Piper-Ranallo, but is there the slightest shadow of a use case here?

Piper-Ranallo commented 2 years ago

I guess my assumption is that each vocabulary contains all historical concepts (active and inactive) so we can capture the meaning of data at the time it was encoded. The use case for having the complete set of modifiers is two-fold. One, it allows us to capture this aspect of services provided. Two, it allows us to identify when we have non-industry standard modifiers applied to procedures encoded using HCPCS or CPT codes. This modifier appeared in the set of "invalid modifiers" (based on a join to modifier concepts in the concept file) but in fact it's not (it's just missing in omop).

Does that make sense?

mik-ohdsi commented 2 years ago

My assumption: this concept comes from a version that simply never made it to OMOP. I think we can safely assume that for many vocabularies we do not go back in the past up to a certain point, one reason being that there is less data to analyze that would fall into that timeframe... So: what is an acceptable cutoff date, @Piper-Ranallo and @cgreich ?

cgreich commented 2 years ago

We could use a cutoff date or squeaky wheel-based criterion.

Which is why I was asking @Piper-Ranallo: Do you want to analyze data with those modifiers for anything in particular? Right now, the modifier essentially says "took longer than normal". I get it. But apart of having a home for this data item, do we actually need it?

Piper-Ranallo commented 2 years ago

Hi @cgreich and @mik-ohdsi,

This request is came out of a data quality assurance use case (v a specific research use case). We were trying to identify source data with potentially invalid modifiers.

I may have made the erroneous assumption that omop vocabulary tables contain all historically valid codes for each of the vocabularies. However, I do think there's value in OMOP including these, as any industry standard code seems to be created for a reason - and therefore has potential value to researchers.

I've since loaded the complete set of modifiers into our teminology server and am using that (rather than omop vocabulary) fiels as the 'source of truth' for what represents a valid v. invalid HCPCS or CPT modifier.

Piper

cgreich commented 2 years ago

I may have made the erroneous assumption that omop vocabulary tables contain all historically valid codes for each of the vocabularies.

You made the right assumption. OMOP never forgets. But we may not have all historical codes. We need the community (you) to tell us.

The problem is not in the code. We are abolishing the other modifiers as well. They are not a thing. Some of them modify the procedure, some of them a condition, some of them are justifications for payment, some of them are care settings of the visit. We will map them where they belong.

A "took longer than usual" modifier - I don't know where that fits, to be honest. Do you?

mik-ohdsi commented 2 years ago

Hi @Piper-Ranallo and @cgreich - from the discussion I take that a) this is a claims related modifier probably justifying a higher price tag b) we have not a clear use case nor do we know if anyone really has this in their source data AND wants it to appear in the OMOP CDM - are you okay with closing this ticket?

Piper-Ranallo commented 2 years ago

@mik-ohdsi , yes, let's close it. The juice isn't worth the squeeze (as they say) on this one. We have it in our source data, but have a lot more work to do figuring out which modifiers carry any useful clinical information and therefore are worth keeping and mapping.

Thanks, Piper