Centralized data front end.accdb Change Request: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) |
||
| Line 5: | Line 5: | ||
== Other change requests == | == Other change requests == | ||
* "...add the “Person_ID” to L_Log_PHI_time_hm - this is the one I am using. I can easily add it now but every time | * "...add the “Person_ID” to L_Log_PHI_time_hm - this is the one I am using. I can easily add it now but every time I made a copy, I will always add it..." | ||
* remove module SHA256 , we will do this differently now | * remove module SHA256 , we will do this differently now | ||
| Line 11: | Line 11: | ||
* I have replaced the med_from query with one called “link_suspect_from_partner_no_match”; now that we are using var1/2 elsewhere it only makes sense. I still need to make the counterpart *to query. This query finds pts where the second record says they should be from a partner site and there is no partner. I also need to make queries for prev encounter comes from a partner site and Var is not marked. | * I have replaced the med_from query with one called “link_suspect_from_partner_no_match”; now that we are using var1/2 elsewhere it only makes sense. I still need to make the counterpart *to query. This query finds pts where the second record says they should be from a partner site and there is no partner. I also need to make queries for prev encounter comes from a partner site and Var is not marked. | ||
* need to make an | * need to make an PL query where early and late have short transit times but locations don’t correspond. | ||
* fix query ''link_suspect_medicine_*_partner'' - have false positives | * fix query ''link_suspect_medicine_*_partner'' - have false positives | ||