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

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


* put back the sort buttons for the patient list
==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_to_med_no_partner'' - has false positives
{{Todo
| who = Tina
| todo_added = 2021-07-15 
| todo_action =
| question =  _dev_CFE
* CCI and ICD10 make button for Pagasa}}


* Highest pseudo is used to check “bad PHIN” for incompletes - better solution?
=== Move Linked Pairs ===
** this should be done in CCMDB instead, see [[Requested_CCMDB_changes_for_the_next_version#Important_change_request]]
{{Todo
| who = Tina
| 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?


* "Tina will work to implement this new “HASH” system."
== Related articles ==
 
{{Related Articles}}
* collapse autopsy...
 
* make query to set time part of tmp dateVar to nothing
 
* why are there blank BirthMYs?
 
* what happens to BirthMY when Pagasa updates Birth?
 
=== Preventing inappropriate edits by data processor ===
 
=== other spot that might contain requirements... ===
[[TMSX MedTMS to Centralized go-live]]
 
== After go-live ==
* [[Questioning data back to collectors]]
* revisit [[:Category:Cleaner.mdb 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, 15 July 2021

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: