-
And what are you going to lose if you don’t know it came from a proc field?
Will lose provenance. Is provenance important? Was important enough that the ability to track it has been maintained from OMOP v3 until now. -
How do you know know it came from a proc field?
Cannot think of an ETL we have done where column in the source does not indicate that the expected value should be a procedure, condition, or medication. -
it goes into a DRUG_EXPOSURE table you cannot use a Procedure Type Concept on it.
Why not? Because of convention? And the proposal is to change the convention.
This is not the first time this topic has been discussed see New Observational Types? Here @Patrick_Ryan says “If we’re talking about a claims database, then the origin of the data is from an inpatient/outpatient medical claims diagnosis codes and/or procedure codes. In which case, the existing _TYPE values, as they are used for CONDITION and PROCEDURE domain should be used in the OBSERVATION table when the _CONCEPT_ID has that domain.”
I think the Themis proposal is simply moving this from an obscure forum post to ETL guidance.