Centralized data front end.accdb Change Request: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →Other change requests: unique patient IDs are now implemented see L_Person |
Ttenbergen (talk | contribs) m →Other change requests: highest_pseudo was already gone, and confirmed with Pagasa that no longer needed. |
||
| Line 5: | Line 5: | ||
== Other change requests == | == Other change requests == | ||
=== PL queries === | |||
* 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. | ||
| Line 14: | Line 15: | ||
** var1/2 etc | ** var1/2 etc | ||
=== L_Log BirthMY === | |||
* BirthMY | * BirthMY | ||
** why are there blank BirthMYs? | ** why are there blank BirthMYs? | ||
** what happens to BirthMY when Pagasa updates Birth? | ** what happens to BirthMY when Pagasa updates Birth? | ||
* data issues? | * data issues? | ||
** collapse autopsy... | ** collapse autopsy... | ||
=== Preventing inappropriate edits by data processor === | === Preventing inappropriate edits by data processor === | ||
Revision as of 15:46, 2 April 2015
see the Development Documentation Category for other development logs
This article contains requested changes for Centralized data front end.mdb. See Centralized data front end.mdb Change Log for it's change log.
Other change requests
PL queries
- 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 PL query where early and late have short transit times but locations don’t correspond.
- fix query link_suspect_medicine_*_partner - have false positives
- Not everyone from *W needs to come from a ward where we collect;
- need acceptable delay
- var1/2 etc
L_Log BirthMY
- BirthMY
- why are there blank BirthMYs?
- what happens to BirthMY when Pagasa updates Birth?
- data issues?
- collapse autopsy...
Preventing inappropriate edits by data processor
other spot that might contain requirements...
TMSX MedTMS to Centralized go-live