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

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
 
(128 intermediate revisions by 3 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.


see
<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>
* [[Validating Data Sending | Validating Data '''Sending''']]
* [[Validating Data Importing | Validating Data '''Importing''']]


== Other change requests ==
==New change request==
=== Preventing inappropriate edits by data processor ===
<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>
*Currently if processor not careful, will be able to accidentally add ADL or TASK for ICU patients.  Other than being careful, how do we avoid?
** I kept the editing interface as wide open as possible for the data processor to make sure that whatever unexpected things we may ask her to do, she can do. If we want something tighter, we will need to decide what that would be.
* ICU variables should be unavailable for med records and vice versa. Easiest would be to change the patient viewer and put program-specific data into their own tab. Could leave both tabs available for editing or hide one depending on value in r_location. Thoughts?
* Could apply the same error checks to e.g. Apache entries. Problem is that these are usually applied at bulk when setting patient to complete. To do them earlier has led to problems and repeat-triggers with some checks, especially ones that compare entries in different fields.  


=== Where should s-tables live ===
{{Todo
* consider logical solution for where s_tables should live: see [[Spin-out of common data]]
| who = Tina
| todo_added = 2021-07-15 
| todo_action =  
| question = _dev_CFE
* CCI and ICD10 make button for Pagasa}}


===Temp Studies - multiple rows ===
=== Move Linked Pairs ===
*Listing multiple rows of information when looking in Tmp studies via the binoculars. email sent to tina and Brad. Feb 25.14.
{{Todo
** see [[L TmpV2 multi-entry clean-up]]
| who = Tina
 
| todo_added = 2021-07-15 
=== other spot that might contain requirements... ===
| todo_action =
[[TMSX MedTMS to Centralized go-live]]
| question = _dev_CFE
 
* Linked pairs, better storage }}
== update process ==
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.  
When Trish and Pagasa edit front end queries, they put the .mdb at X:\CCMDB\centralized_FRONT_End with a different name starting with a "!". The queries will then be imported on the master next time it is updated. We will need to put a reference, likely into the requested changes for front end article to tell which queries need importing.  
* 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?
== After go-live ==
=== Email Generator ===
* provide automation for generating email with particulars for collector to correct data for Pagasa to use
* Trish sent Tina several example emails
* revisit [[:Category:Cleaner.mdb Data Integrity Checks‏‎]]


== Related articles ==
{{Related Articles}}


[[Category: Development Documentation]]
[[Category: Development Documentation]]
[[category:2013 data upgrades]]
[[Category: 2013 data upgrades]]
[[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:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Centralized_data_front_end.accdb_Change_Request&oldid=151263"