This page contains Legacy Content.
Click Expand to show legacy content.
This used to be done in cleaner. Is it still an issue? If so we should move it to Centralized data front end.accdb. Ttenbergen 10:49, 2015 June 25 (CDT)
Make sure there is only one entry in Tasks.mdb for each ward stay. (As per the contents of "discussion".)
If all parties agree that the following either boils down to the above or just does not make sense, it can be deleted. Tina: Delete Julie: Trish: Duplication when the data file (.csv) is appended more than once by the data processor (ie: same serial w/diff study #). i.e. same serial/location w/diff study#? Yes this happened before but Ed’s program is now catching it bec we brought this up to him . You mean Ed’s program now stores the Tasks? Another case we found is the same patient entered twice with different serial no, same loc and consequently diff study no. (happens when another DC covers for another during vacation or maybe when the DC is really tired). So that is not really Task specific then? I was tempted to say: “The data is sent straight from the DCs CCMDB.accdb to the tasks.mdb that is its repository. There is no .csv stage. The data processors check it in that access db. Am I misinterpreting your check request, or does that information address the issue?“” But now I think you are talking about checking tasks for medicine, not the tasks we are collecting in Medicine. In that case, I actually think some of the previous questions really apply to both as well, e.g. the post-op stuff. Does it not?
I made the following: find counts>1 of (PHIN and admitdate and location) Query Generated and posted