Keep outdated standard concepts active and standard

[clairblacketer]

link to original forum post

We reviewed the logic of standards concepts deprecation.
So far when the source removes the concept from list of the active concepts, we deprecate it, and it doesn't matter what is the reason of deprecation:
incorrect concept - duplicate, having wrong description (e.g. wrong drug dosage), some weird classification branch, etc.
correct, but outdated for the other reasons
for example CPT4 in the last release makes "76645 | Ultrasound of breasts" concept outdated (maybe it's not a billing code anymore, because you need to specify some other details), or this one: "97001 | Physical therapy evaluation", and also there are more granular concepts.
But the thing is that these procedure really happened and these codes exist in a patient data for a years and might be included in a protocols, concepts sets, etc. So it's totally OK to have them in a data as a standard concepts.

The proposal is to keep these concepts standard and active for CPT4, HCPCS and other vocabularies with the same out-dating principles. And "resurrect" them in our vocabularies making invalid_reason = null and standard_concept ='S'

March 6 Decision
For a HCPCS and CPT4 concepts deprecated because of the source withdrawal, we make the Standard_concept = 'S' and invalid_reason = null, but valid_end_date reflects the withdrawal date.
This makes possible to use these concepts as standard and fill up the CDM, and also CDM builders can easily check the consistency of the data ensuring that event date is between concept's valid_stard_date and valid_end_date.

Once we have resources available, we'll implement these changes

Note, we make this for HCPCS and CPT4 only. In the future we'll analyze the other vocabularies, understanding why the source deprecates the concepts and then we'll make a decision whether we need to deprecate them or just change the valid_end_date but not affect Standard_concept and invalid_reason values.

[clairblacketer]

added in v6.0