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

From CCMDB Wiki
Jump to navigation Jump to search
 
(39 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.


=== PL queries ===
<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>
* 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.  
==New change request==
<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>


* fix query ''link_suspect_medicine_*_partner'' - have false positives
{{Todo
** Not everyone from *W needs to come from a ward where we collect;
| who = Tina
** need acceptable delay
| todo_added = 2021-07-15 
** var1/2 etc
| todo_action =
| question =  _dev_CFE
* CCI and ICD10 make button for Pagasa}}


=== L_Log BirthMY ===
=== Move Linked Pairs ===
* BirthMY
{{Todo
** why are there blank BirthMYs?
| who = Tina
** what happens to BirthMY when Pagasa updates Birth?
| todo_added = 2021-07-15 
* {{discussion}} emailed Trish and Julie to see if we can pitch this Ttenbergen 14:02, 2015 August 17 (CDT)
| 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?


=== Preventing inappropriate edits by data processor ===
== Related articles ==
 
{{Related Articles}}
== After go-live ==
* [[Questioning data back to collectors]]
* revisit [[! Automated Data Integrity Checks‏‎]]


[[Category: Development Documentation]]
[[Category: Development Documentation]]
[[Category: 2013 data upgrades]]
[[Category: 2013 data upgrades]]
[[Category: Centralized data front end.mdb]]
[[Category: Centralized data front end.accdb]]

Latest revision as of 16:34, 2021 July 15

see the Development Documentation Category for other development logs

This article contains requested changes for Centralized data front end.accdb. See Centralized data front end.accdb Change Log for it's change log.

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.

New change request

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.

_dev_CFE

  • CCI and ICD10 make button for Pagasa
  • added: 2021-07-15
  • action:
  • Cargo


  • Categories

Move Linked Pairs

_dev_CFE

  • Linked pairs, better storage
  • added: 2021-07-15
  • action:
  • Cargo


  • Categories

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?

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Centralized_data_front_end.accdb_Change_Request&oldid=151263"