Centralized data front end.accdb Change Request: Difference between revisions

TOstryzniuk (talk | contribs)
For Tina
m Text replacement - "[[Category: " to "[[Category:"
 
(48 intermediate revisions by 2 users not shown)
Line 1: Line 1:
''see the [[:Category: Development Documentation | Development Documentation Category]] for other development logs''
''see the [[:Category: Development Documentation | 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.
This article contains requested changes for [[Centralized data front end.accdb]]. See [[Centralized data front end.accdb Change Log]] for it's change log.


== Other change requests ==
<big>'''Generally items should be discussed and flagged for change on their own page, and not here. Only changes that don't have wiki pages yet should be listed here.'''</big>
==RecordStatus Report if Complete in Centralized==
#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.
#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. 
#other suggestion welcomed to catch these babies when there are changes or issues with sending.


=== PL queries ===
==New change request==
* 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.
<big>'''Generally items should be discussed and flagged for change on their own page, and not here. Only changes that don't have wiki pages yet should be listed here.'''</big>


* need to make an  PL query where early and late have short transit times but locations don’t correspond.
{{Todo
| who = Tina
| todo_added = 2021-07-15 
| todo_action =
| question =  _dev_CFE
* CCI and ICD10 make button for Pagasa}}


* fix query ''link_suspect_medicine_*_partner'' - have false positives
=== Move Linked Pairs ===
** Not everyone from *W needs to come from a ward where we collect;
{{Todo
** need acceptable delay
| who = Tina
** var1/2 etc
| todo_added = 2021-07-15 
| todo_action =
| question =  _dev_CFE
* Linked pairs, better storage }}
As discussed with Julie to prevent her having to rerun it and to insure that what Pagasa queries against is same as what Julie uses.
* need to change the query and process from one that re-does all, every time, to one that only updates new.
** How will that work for individual older records that were edited?


=== L_Log BirthMY ===
== Related articles ==
* BirthMY
{{Related Articles}}
** why are there blank BirthMYs?
** what happens to BirthMY when Pagasa updates Birth?


=== collapse autopsy ===
[[Category:Development Documentation]]
what does that even mean? Ttenbergen 17:00, 2015 April 2 (CDT) {{discussion}}
[[Category:2013 data upgrades]]
 
[[Category:Centralized data front end.accdb]]
=== Preventing inappropriate edits by data processor ===
 
== After go-live ==
* [[Questioning data back to collectors]]
* revisit [[:Category:Cleaner.mdb Data Integrity Checks‏‎]]
 
[[Category: Development Documentation]]
[[Category: 2013 data upgrades]]
[[Category: Centralized data front end.mdb]]