Requested CCMDB changes for the next version: Difference between revisions
Ttenbergen (talk | contribs) →Help to manage Serial numbers: feedback needed from collectors please |
Ttenbergen (talk | contribs) |
||
| Line 73: | Line 73: | ||
**This may not work as planned as there are times when the data collector assigns a number to a patient file in her log book but is unable to use it immediately and must use numbers out of order (even though the numbers are assigned in the right order).--[[User:CMarks|CMarks]] 08:39, 30 November 2010 (CST) | **This may not work as planned as there are times when the data collector assigns a number to a patient file in her log book but is unable to use it immediately and must use numbers out of order (even though the numbers are assigned in the right order).--[[User:CMarks|CMarks]] 08:39, 30 November 2010 (CST) | ||
==== Possible Solution 2 === | ==== Possible Solution 2 ==== | ||
If we are not able to provide the next number on the list, we could at least suggest it, and then do error checking on what is chosen. | If we are not able to provide the next number on the list, we could at least suggest it, and then do error checking on what is chosen. | ||
Scenario: When the "Add Patient" button is clicked on the Patient List, the msg box could default to (highest serial currently on the laptop)+1. If a different number is desired, the collector could change it. This would be followed by the existing checks for a blank ID and for an existing ID. The program would then check if the ID was '''smaller''' than the largest ID already present (since some collectors use multiple indices, this error would be ignorable). The program could also check if the new Patient ID is more than “X” greater than the previous max(Pat_ID) (what would be a reasonable "X"?) (again, this error would be ignorable). | Scenario: When the "Add Patient" button is clicked on the Patient List, the msg box could default to (highest serial currently on the laptop)+1. If a different number is desired, the collector could change it. This would be followed by the existing checks for a blank ID and for an existing ID. The program would then check if the ID was '''smaller''' than the largest ID already present (since some collectors use multiple indices, this error would be ignorable). The program could also check if the new Patient ID is more than “X” greater than the previous max(Pat_ID) (what would be a reasonable "X"?) (again, this error would be ignorable). | ||