Requested CCMDB changes for the next version: Difference between revisions
Ttenbergen (talk | contribs) |
TOstryzniuk (talk | contribs) |
||
| Line 25: | Line 25: | ||
** might be able to use http://bytes.com/topic/access/answers/201218-arrow-down-up-causing-move-between-records to make this happen. Ttenbergen 09:30, 2013 September 25 (CDT) | ** might be able to use http://bytes.com/topic/access/answers/201218-arrow-down-up-causing-move-between-records to make this happen. Ttenbergen 09:30, 2013 September 25 (CDT) | ||
* change tab order so that can tab into ARF properly. Ttenbergen 15:15, 2013 September 25 (CDT) | * change tab order so that can tab into ARF properly. Ttenbergen 15:15, 2013 September 25 (CDT) | ||
* need implement how ccmdb should deal with a patient that was entered, then sent incomplete, then deleted before ever completing. Right now that patient remains incomplete in | * need implement how ccmdb should deal with a patient that was entered, then sent incomplete, then deleted before ever completing. Right now that patient remains incomplete in centralized data. Is that right? Ttenbergen 14:32, 2013 October 3 (CDT) | ||
**That is correct is remains thee. The plan is this: if a data collector DELETES a patient before COMPLETE and it has been sent as incomplete to centralized, the collector '''must notify Pagasa by email'''. Pagasa must delete the file from centralized.--[[User:TOstryzniuk|Trish Ostryzniuk]] 14:49, 2013 October 3 (CDT) | |||
=== checks for minimal data admit/discharge === | === checks for minimal data admit/discharge === | ||