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

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
→QAInf missing: question for Pagasa
m Text replacement - "[[Category: " to "[[Category:"
 
(105 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.


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''']]


==Fix needed==
==New change request==
===QAInf missing===
<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>
{{Potential Change}}
QAInf missing from centralized - Pagasa ID'd one patient from CON that in acq DX VAP, but centralized front end not seeing the VAP date. She checked TMPV2.mdb and VAP dates is there.  Not sure if there are others.[[User:PTorres|PTorres]] 12:03, 2014 June 20 (CDT)
* is the DATA missing, or are there just things that aren't displayed the way you would want to? What is the D_ID? Ttenbergen 16:25, 2014 June 23 (CDT) {{discussion}}


== Other change requests ==
{{Todo
=== preventing edits in borrowed data ===
| who = Tina
Pagasa now uses push/pull scripts to pull data to a specific location. That is the only place where data should be edited. Update front end to colour code or lock if file is not in that location. IE, allow views, but not edits.
| todo_added = 2021-07-15 
* I can lock down editing in forms (eg in the patient list and viewer) but not directly in queries or tables. Will do that. Ttenbergen 11:12, 2014 May 22 (CDT)
| todo_action =  
| question = _dev_CFE
* CCI and ICD10 make button for Pagasa}}


=== Preventing inappropriate edits by data processor ===
=== Move Linked Pairs ===
*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?
{{Todo
** 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.  
| who = Tina
* 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?
| todo_added = 2021-07-15 
* 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.
| 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?


===Temp Studies - multiple rows ===
== Related articles ==
* see [[L TmpV2 multi-entry clean-up]]
{{Related Articles}}


=== other spot that might contain requirements... ===
[[Category:Development Documentation]]
[[TMSX MedTMS to Centralized go-live]]
[[Category:2013 data upgrades]]
 
[[Category:Centralized data front end.accdb]]
== update process ==
see [[Update process for use of Centralized data front end.mdb]]
 
== 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]]

Latest revision as of 10:32, 30 July 2025

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=166111"