Oh. I see. We need to figure out something. Otherwise you will deviate increasingly from the standard, which will put your ability at risk to do network studies. This is a big deal.
That's what folks do who don't update continuously. A full job on all the data. Are you going to run into infrastructure problems, or why would you not want to do that?
Well, "break" also means "being fixed". Goes both ways.
But yes, we need to think about a mechanism to update a query. I think that can be automated.
The problem is we don't control that. Most of our content comes from the sources. If SNOMED updates concepts or links we cannot just ignore that.
Exactly. So, the solution is that we need to string the CDM data along and update the queries. No way around it.
What's the use case? Why would we need to know it's no longer in use? The only case I can think of is for purposes of debugging cohort definitions trying to identify the reasons for change over time. Is that it?
I also a lot of "where sysdate between start_date and end_date" notations. We will have to do a THEMIS convention.