Centralized data front end.accdb Change Request

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.

RecordStatus Report if Complete in Centralized

1. Reconnect button: could it also include count of COMPLETE? Would like to ID this issues sooner in process so I notify there is a problem.
2. When I click Vetted, I would also like you to include count that are marked COMPLETE in record status. This would be helpful in the case I missed fixing all COMPLETE in RecordStatus in centralized.
3. other suggestion welcomed to catch these babies when there are changes or issues with sending.

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?

collapse autopsy

what does that even mean? Ttenbergen 17:00, 2015 April 2 (CDT) Template:Discussion

After go-live

• Questioning data back to collectors
• revisit Category:Cleaner.mdb Data Integrity Checks‏‎