Sunsetting strategy for v4

General
1

For creating studies and improving existing tools, it is difficult to deal with both CDM v4 and v5.

For example adding new measures to Achilles Heel requires making the same code twice. Some features can not be done in v4 since some tables were extended (e.g., provider_id added).

I would like to propose that we officially declare CDM version 4 as unsupported by the tools at some point.

I suggest we no longer support v4 in the tools after Aug 31, 2016 (ok, ok, perhaps by Dec 31, 2016)

1 Like
2

+1. We need to do this, so people start moving to v5.

3

Would this sunsetting strategy include Athena? If that’s the case there would be now vocabulary support beyond December 2016.

4

@Jorge:

Athena is on V5. The V4 is a product of an auto-downgrader. All we have to do is to switch it off.

Weaning them off of V4: I agree, we should make such an announcement, and then give them some extra slack, when the time comes. Kind of like Windows XP or ICD-10.

5

at least one data provider (Optum?) has said they are moving to V5 in Q2 2017 (I believe – don’t quote me, this is hearsay). So, if true, this would not be a surprise to many people.

6

not just moving, but also not providing V4.