The ETL process loads a special "not recorded" provider record in the event that provider data is not loaded, because i2b2 requires that every fact have an associated provider. This special record is loaded with an update date, even when it is loaded the first time. This is inconsistent with the rest of the ETL, which does not set an update date unless a record has actually been updated.
The ETL process loads a special "not recorded" provider record in the event that provider data is not loaded, because i2b2 requires that every fact have an associated provider. This special record is loaded with an update date, even when it is loaded the first time. This is inconsistent with the rest of the ETL, which does not set an update date unless a record has actually been updated.