We saw the 20 year lookback criteria also impacted our numbers. Russ
From: Gpc-dev <gpc-dev-boun...@listserv.kumc.edu> on behalf of James Campbell <campb...@unmc.edu> Date: Thursday, August 9, 2018 at 12:17 PM To: "GPC-DEV@LISTSERV.KUMC.EDU" <gpc-dev@listserv.kumc.edu> Subject: Fw: C4UN - death table records data curation I wonder if this accounts for the record discrepancies that Phillip was reporting? Frankly, I looked at our own stats and didn't much worry about numbers of validated records from Duke Jim ________________________________ From: Allison Haufler <allison.hauf...@duke.edu> Sent: Wednesday, August 8, 2018 7:31 AM To: Campbell, James R Subject: C4UN - death table records data curation Non-UNMC email Hi James, I apologize for following up w/ this after the approval of Nebraska’s data curation submission – but we noticed something in the code that was changed between last cycle and this cycle that is affecting the death table (and a few other tables) records/patients. Since a date is not required in the death table a “lookback date” of 20 years was applied this time to restrict the amount of work the query has to do searching. Unfortunately, this is causing records w/ no death date and also records with a death date greater than 20 years ago to be dropped by the time is gets to the DEATH_L3_N query. This will be remedied for the next package release, but at this point, you technically do have more than a 5% decrease in records and patients in the death table between last refresh and this refresh. So, I’m asking if you please document that in the ETL ADD on the data persistence page for the question that asks if any tables lost more than 5% of records and/or patients. Your explanation can be that the lookback period introduced in this query caused a number of patients fall out. Please let me know if you have any questions. Thanks, Alli The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender.
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
