| 15 | | [[BR]]b. The date fields should be loaded with previously stored dates for the patient, if any.[[BR]]c. The date input fields should be coupled to a number of sanity checks: apart from normal checks for date syntax, future dates should not be allowed, and for items with both a sent and received date, the latter should not be allowed to be earlier than the sent date.[[BR]]d. A "`Cancel`" and a "`Register`" button should appear below the form. When the "`Register`" button is clicked, the data in the date fields should be stored in annotations for the patient.[[BR]]e. When a registration with all seven dates values filled in is made, "`RetractStatus`" for the patient item is set to "`ReadyForDestruction`", while if any date value is missing, it is set to `null`. |
| | 15 | [[BR]]b. The date fields should be loaded with previously stored dates for the patient, if any.[[BR]]c. The date input fields should be coupled to a number of sanity checks: apart from normal checks for date syntax, future dates should not be allowed, and for items with both a sent and received date, the latter should not be allowed to be earlier than the sent date.[[BR]]d. A "`Cancel`" and a "`Register`" button should appear below the form. When the "`Register`" button is clicked, the data in the date fields should be stored in annotations for the patient.[[BR]]e. When a registration with all seven date values filled in is made, "`RetractStatus`" for the patient item is set to "`ReadyForDestruction`", while if any date value is missing, it is set to `null`. |
