Requested CCMDB changes for the next version: Difference between revisions
TOstryzniuk (talk | contribs) mNo edit summary |
TOstryzniuk (talk | contribs) |
||
| Line 26: | Line 26: | ||
* 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 centralized data. Is that right? Ttenbergen 14:32, 2013 October 3 (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 centralized data. Is that right? Ttenbergen 14:32, 2013 October 3 (CDT) | ||
**That is correct it remains in centralized. The plan is this: if a data collector DELETES a patient before COMPLETE and it has already been sent as INCOMPLETE to centralized, the collector '''must notify Pagasa by email'''. Pagasa must delete the file from centralized, unless you have other idea.--[[User:TOstryzniuk|Trish Ostryzniuk]] 14:49, 2013 October 3 (CDT) | **That is correct it remains in centralized. The plan is this: if a data collector DELETES a patient before COMPLETE and it has already been sent as INCOMPLETE to centralized, the collector '''must notify Pagasa by email'''. Pagasa must delete the file from centralized, unless you have other idea. Don't know if collector realize at this point that complete and incomplete files are sent to centralized each week when they send. --[[User:TOstryzniuk|Trish Ostryzniuk]] 14:49, 2013 October 3 (CDT) | ||
=== checks for minimal data admit/discharge === | === checks for minimal data admit/discharge === | ||