Centralized data front end.accdb Change Request
see the 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.
see
Other change requests
preventing edits in borrowed data
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.
- 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)
Preventing inappropriate edits by data processor
- 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.
Temp Studies - multiple rows
other spot that might contain requirements...
TMSX MedTMS to Centralized go-live
vetting
- fix queries in Centralized_data_Vetting_Process#Check_for_problems
orphans
See: Orphans in Centralized data.mdb-- Ttenbergen 11:16, 2014 May 22 (CDT)
update process
see Update process for use of Centralized data front end.mdb