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

From CCMDB Wiki
Jump to navigation Jump to search
Preventing inappropriate edits by data processor: need clarification on tasks, and confirmation if other fields hidden as wanted now
Line 10: Line 10:
== Other change requests ==
== Other change requests ==
=== Preventing inappropriate edits by data processor ===
=== 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?
==== Tasks ====
** 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.  
The tasks are a specific diagnosis, not a field I could just hide. I could eliminate them from the drop-down but it would complicate several forms. Considering adding a task would be a multi-step process I don't think it's very likely to do this accidentally. If you agree, pls take this out. If you still want this in place, pls stick it into [[Change Priorities]] at an appropriate level. Ttenbergen 21:43, 2014 June 23 (CDT) {{discussion}}
* 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.
==== Other program specific fields ====
I have hidden most depending on program determined by r_location field. If all is as you wanted, pls delete this. If more changes needed, pls describe here and link from [[Change Priorities]]. Ttenbergen 21:43, 2014 June 23 (CDT) {{discussion}}


===Temp Studies - multiple rows ===
===Temp Studies - multiple rows ===

Revision as of 20:43, 23 June 2014

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

Fix needed

Other change requests

Preventing inappropriate edits by data processor

Tasks

The tasks are a specific diagnosis, not a field I could just hide. I could eliminate them from the drop-down but it would complicate several forms. Considering adding a task would be a multi-step process I don't think it's very likely to do this accidentally. If you agree, pls take this out. If you still want this in place, pls stick it into Change Priorities at an appropriate level. Ttenbergen 21:43, 2014 June 23 (CDT) Template:Discussion

Other program specific fields

I have hidden most depending on program determined by r_location field. If all is as you wanted, pls delete this. If more changes needed, pls describe here and link from Change Priorities. Ttenbergen 21:43, 2014 June 23 (CDT) Template:Discussion

Temp Studies - multiple rows

other spot that might contain requirements...

TMSX MedTMS to Centralized go-live

update process

see Update process for use of Centralized data front end.mdb

After go-live