Complete Report by Package - Full Details

Main Success Scenario:

1. The user selects the option to manage the list of qualifications.
2. The system displays all qualifications entered in the system.
3. The user adds a new qualification.
4. The user enters the description of the qualification.
5. The user saves the record (UC-ICE2).
6. The system makes the qualification available for selection when adding cadres.

Extensions:

3.a The user selects an existing item.

1. The system opens the item and enables it to be edited.

5.a The system determines that the name of the qualification matches a qualification already entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to update the list of cadres.
2. The system displays all cadres entered in the system.
3. The user adds a new cadre.
4. The user enters the name of the cadre.
5. The user enters the ISCO classification code for the cadre (optional).
6. The user selects the minimum qualification for the cadre.
7. The user saves the record (UC-ICE2).
8. The system displays the new or edited cadre in selection lists of cadres.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

6.a The user enters a new qualification if the correct one does not appear (UC-PS1)

1. The user returns to Step 1 to enter the cadre.

7.a The system determines that the cadre name already exists in the database.

1. The system displays an error message and will not proceed.

Main Success Scenario:

1. The user selects the option to update the list of continuing education courses.
2. The system displays all continuing education courses added to the system.
3. The user adds a new continuing education course.
4. The user enters the name of the course.
5. The user enters the number of credit hours that can be earned by completing the course.
6. The user saves the record (UC-ICE2).
7. The system makes the new course available for selection when adding continuing education information to a record.

Extensions:

3.a The user selects an existing continuing education course name.

1. The system opens the course's details and provides the option to update them.

Main Success Scenario:

1. The user selects the option to update disciplinary action categories.
2. The system displays all disciplinary action categories entered in the system.
3. The user adds a new category.
4. The user enters a description for the category.
5. The user saves the record (UC-ICE2).
6. The system makes the disciplinary action category available for selection when adding disciplinary actions.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the disciplinary action category already exists in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to update the list of disciplinary action reasons.
2. The system displays all reasons entered in the system.
3. The user adds a new reason.
4. The user selects a category for the reason.
5. The user enters a description for the reason.
6. The user saves the record (UC-ICE2).
7. The system makes the reason available for selection when adding disciplinary actions.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

4.a The user adds a new disciplinary action category (UC-PS4).

1. The user returns to Step 1 to add the disciplinary action reason.

6.a The system determines that the disciplinary action reason is already in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage out migration reasons.
2. The system displays all reasons entered in the system.
3. The user adds a new out migration reason.
4. The user enters a description for the out migration reason.
5. The user saves the record (UC-ICE2).
6. The system makes the reason available for selection when recording out migration verification requests.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the out migration reason already exists in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of training disruption categories.
2. The system displays all categories entered in the system.
3. The user adds a new category.
4. The user enters a description for the category.
5. The user saves the record (UC-ICE2).
6. The system makes the training disruption category available for selection when adding training disruptions.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the training disruption category already exists in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to update the list of reasons for training disruption.
2. The system displays all reasons entered in the system.
3. The user adds a new reason.
4. The user selects a category for the reason.
5. The user enters a description for the reason.
6. The user saves the record (UC-ICE2).
7. The system makes the reason available for selection when adding training disruptions.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

4.a The user adds a new training disruption category (UC-PS7).

1. The user returns to Step 1 to add the training disruption reason.

7.a The system determines that the training disruption reason has already been entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of academic levels.
2. The system displays all academic levels entered in the system.
3. The user adds a new academic level.
4. The user enters the description of the academic level.
5. The user saves the record (UC-ICE2).
6. The system makes the academic level available for selection when adding academic information.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing

5.a The system determines that the academic level has already been entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of certificates held.
2. The system displays all certificates entered in the system.
3. The user adds a new certificate.
4. The user selects the academic level to which the certificate belongs.
5. The user enters a description of the certificate.
6. The user saves the record (UC-ICE2).
7. The system makes the certificate available for selection when adding academic information.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

4.a The user adds a new academic level (UC-PS9).

1. The user returns to Step 1 to add the certificate.

6.a The system determines that the certificate already exists in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of identification types.
2. The system displays all identification types entered in the system.
3. The user adds a new identification type.
4. The user enters the description or name of the item.
5. The user saves the record (UC-ICE2).
6. The system makes the identification type available for selection when adding identifications.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the identification type already exists in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of marital statuses.
2. The system displays all marital statuses entered in the system.
3. The user adds a new marital status.
4. The user enters a description for the marital status.
5. The user saves the record (UC-ICE2).
6. The system makes the marital status available for selection when adding demographic information.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the marital status was already entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage lists of countries.
2. The system displays all countries entered in the system.
3. The user adds a new country.
4. The user enters the two-letter country code.
5. The user enters the ISO numeric code for the country (optional).
6. The user selects whether the country is the primary country for the system.
7. The user selects whether the country is used for location selection.
8. The user saves the record (UC-ICE2).
9. The system makes the country available for selection whenever adding geographical locations or nationalities/citizenships.

Extensions:

3.a The user selects an existing country

1. The system opens the item for editing.

6.a The user selects the country as the primary country.

1. The system displays the country first in all country selection menus.

6.b The user selects more than one country as the primary country.

1. The system displays all primary countries at the top of selection menus in alphabetical order.

7.a The user selects that the country is used for location selection.

1. The system makes the country available for selection when a location, such as an address, is being specified.

8.a The system determines that the country and country code are already in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage lists of regions.
2. The system displays all countries entered in the system.
3. The user selects the country where the region is located.
4. The system displays all regions entered for that country.
5. The user adds a new region.
6. The user selects the name of the country inside which the new region is located.
7. The user enters the name of the region.
8. The user enters the code for the region.
9. The user saves the record (UC-ICE2).
10. The system makes the region available for reporting.

Extensions:

2.a The user does not select a country.

1. The system provides only the option to add a new region.
2. Skip to Step 5.

6.a The user adds a new country (UC-PS13).

1. The user returns to Step 1 to add the region.

6.b The system detects that the country was previously selected.

1. The system fills in the selected country.

7.a The system determines that the region and its parent are the same as a location previously entered in the database.

1. The system displays an error message and will not continue.

Main Success Scenario:

1. The user selects the option to manage lists of districts.
2. The system displays all countries entered in the system.
3. The user selects the country where the district is located.
4. The system displays all regions entered for that country.
5. The user selects the region where the district is located.
6. The system displays all districts entered for that region.
7. The user adds a new district.
8. The user selects the name of the country and region inside which the new district is located.
9. The user enters the name of the district.
10. The user enters the code for the district.
11. The user saves the record (UC-ICE2).
12. The system makes the district available for selection when adding geographical locations.

Extensions:

3.a The user does not select a country.

1. The system provides the option to add a new district only.
2. Skip to Step 7.

7.a The user selects an existing district.

1. The system displays its information for editing.

8.a The system detects that the country and region were previously selected.

1. The system fills in the selections for the district.

9.a The systerm determines that the district and its parents are the same as a location previously entered in the database.

1. The system displays an error message and will not continue.

Main Success Scenario:

1. The user selects the option to manage lists of counties.
2. The system displays all countries entered in the system.
3. The user selects the country where the county is located.
4. The system displays a list of regions for that country.
5. The user selects the region inside which the county is located.
6. The system displays all districts entered for that region.
7. The user selects the district where the county is located.
8. The system displays all districts entered for that county.
9. The user adds a new county.
10. The user selects the country, region and district where the county is located.
11. The user enters the name of the county.
12. The user saves the record (UC-ICE2).
13. The system makes the county available for selection whenever geographical locations are added.

Extensions:

2.a The user does not select a country.

1. The system provides the option to add a new county only.
2. Skip to Step 9.

9.a The user selects an existing county.

1. The system displays all information entered for that county and provides the option to update that information.

10.a The system detects that the country, region and district were previously selected.

1. The system fills in the previous selections for the county.

11.a The system determines that the county and its parents are the same as a location previously entered in the database.

1. The system displays an error message and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of health facilities.
2. The system displays all health facilities entered in the system.
3. The user adds a new health facility.
4. The user enters the name of the health facility.
5. The user enters a health facility identification code.
6. The user adds contact information (UC-PS31).
7. The user selects the country where the health facility is located.
8. The system displays a list of districts in that country.
9. The user selects the district where the health facility is located.
10. The system displays a list of counties in that district.
11. The user selects the county where the health facility is located (optional).
12. The user selects the facility agent.
13. The user selects the facility type.
14. The user selects the status of the health facility.
15. The user saves the record (UC-ICE2).
16. The system makes the health facility available for selection.
17. The system provides the option to update the health facility.

Extensions:

3.a The user selects an existing health facility.

1. The system displays the health facility's record with options to edit any of the information.

7.a The user adds the country, district or county.

1. The user returns to Step 1 to add the health facility.

12.a The user adds the facility agent (UC-PS23).

1. The user returns to Step 1 to add the health facility.

13.a The user adds the facility type (UC-PS24).

1. The user returns to Step 1 to add the health facility.

14.a The user adds the facility status (UC-PS25).

1. The user returns to Step 1 to add the health facility.

16.a The system determines that the health facility name already exists in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of health facilities.
2. The system displays all health facilities entered in the system.
3. The user selects the health facility to edit.
4. The user selects the option to associate a training institution.
5. The user selects the training institution(s) associated with the health facility.
6. The user saves the record (UC-ICE2).
7. The system displays the training institution with the health facility's record.

Extensions:

5.a The user adds a training institution (UC-PS19).

1. The user returns to Step 1 to associate the training institution with the health facility.

Main Success Scenario:

1. The user selects the option to manage the list of training institutions.
2. The system displays all training institutions entered in the system.
3. The user adds a training institution.
4. The user enters the name of the training institution.
5. The user enters the training institution's identification code (optional).
6. The user adds contact information (UC-PS31).
7. The user selects the country where the training institution is located.
8. The system displays a list of districts within that country.
9. The user selects the district where the training institution is located.
10. The system displays a list of counties within that district.
11. The user selects the county where the training institution is located (optional).
12. The user selects the agent under which the training institution belongs.
13. The user selects the status of the training institution.
14. The user saves the record (UC-ICE2).
15. The system displays the training institution information and provides the option to associate a health facility with a training institution (UC-PS20), add a cadre offered by a training institution (UC-PS21) or add inspection information for a training institution (UC-PS22).
16. The system provides the option to update the training institution information.

Extensions:

3.a The user selects an existing training institution.

1. The system displays the training institution's record and provides options to update the information.

7.a The user adds a new country, district or county.

1. The user returns to Step 1 to add the training institution.

12.a The user adds a new facility agent (UC-PS23).

1. The user returns to Step 1 to add the training institution.

13.a The user adds a new facility status (UC-PS25).

1. The user returns to Step 1 to add the training institution.

14.a The system determines that the training institution has already been entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage training institutions.
2. The system displays all training institutions that have been entered in the system.
3. The user selects a training institution.
4. The system displays the training institution's record.
5. The user selects the option to associate a health facility.
6. The user selects the health facility or facilities associated with the training institution.
7. The user saves the record (UC-ICE2).
8. The system displays the health facility with the training institution's record.

Extensions:

6.a The user adds a new health facility (UC-PS17).

1. The user returns to Step 1 to associate the health facility with the training institution.

Main Success Scenario:

1. The user selects the option to update a training institution.
2. The system displays all training institutions entered in the system.
3. The user selects a training institution to edit.
4. The system displays the training institution's record with all training programs entered for that institution.
5. The user selects the option to add a training program or select an existing training program to edit.
6. The user selects the cadre.
7. The system displays today's date for the program's start date.
8. The user changes the start date for the program, if necessary.
9. If the program is no longer being offered, The user selects an end date for it.
10. The user enters the recommended number of students for the program.
11. The user saves the record (UC-ICE2).
12. The system displays the program information with the training institution's record and provides the option to add another program or edit the existing programs.

Extensions:

5.a The user selects an existing training program.

1. The system displays all of the training program's information and enables any field to be changed.

6.a The user adds a cadre (UC-PS2).

1. The user returns to Step 1 to add the training program.

6.b The system determines that a cadre has already been added for that training institution.

1. The system removes the cadre from the selection list.

10.a The user does not enter a recommended number of students.

1. The system saves 0 by default.

Main Success Scenario:

1. The user selects the option to manage the list of training institutions.
2. The system displays all training institutions entered in the system.
3. The user selects the training institution to edit.
4. The system displays the training institution's record.
5. The user selects the option to add inspection information.
6. The system displays today's date for the inspection date.
7. The user changes the date of the inspection, if necessary.
8. The user enters any notes about the inspection.
9. The user selects whether the training institution passed or failed inspection.
10. The user saves the record (UC-ICE2).
11. The system saves the inspection information and displays it with the training institution's record.
12. The system saves the previous inspection information as historical data and displays it in the inspection history.
13. The system provides the option to view the training institution's inspection history and update the current inspection information.

Extensions:

9.a The user does not select any inspection results.

1. The system selects Pass by default.

Main Success Scenario:

1. The user selects the option to manage facility agents.
2. The system displays all facility agents entered in the system.
3. The user adds a new facility agent.
4. The user enters a description for the facility agent.
5. The user saves the record (UC-ICE2).
6. The system makes the facility agent available for selection when adding facilities.

Extensions:

3.a The user selects an existing facility agent.

1. The system opens the item for editing.

5.a The system determines that the facility agent already exists in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of facility types.
2. The system displays all facility types entered in the system.
3. The user adds a new facility type.
4. The user enters a description or name for the facility type.
5. The user saves the record (UC-ICE2).
6. The system makes the facility type available for selection when adding facilities.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the facility type has already been entered in the database.

1. The system displays an error message and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of facility statuses.
2. The system displays all facility statuses entered in the system.
3. The user adds a new facility status.
4. The user enters a description or name for the facility status.
5. The user saves the record (UC-ICE2).
6. The system makes the facility status available for selection when adding facilities.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the facility status has already been entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of verification changes.
2. The system displays all verification changes entered in the system.
3. The user adds a new verification change.
4. The user enters a description or name for the verification change.
5. The user saves the record (UC-ICE2).
6. The system makes the verification change available for selection when recording verifications.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the verification change has already been entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to manage the list of personal titles.
2. The system displays all titles entered in the system.
3. The user adds a new title.
4. The user enters a description or name for the title.
5. The user saves the record (UC-ICE28).
6. The system makes the title available for selection when adding personal information.

Extensions:

3.a The user selects an existing item.

1. The system opens the item for editing.

5.a The system determines that the title has already been entered in the database.

1. The system displays an error and will not continue.

Main Success Scenario:

1. The user selects the option to add a new record.
2. The user selects the title for the person (optional).
3. The user enters the name of the person:
1. surname (required)
2. first name (required)
3. any other names
4. suffix
4. The user selects the person's nationality / citizenship (required).
5. The user selects the country where the person resides (required).
6. The system displays all districts in the country.
7. The user selects the district where the person resides (the home district; required).
8. The system displays all counties within that district.
9. The user selects the county where the person resides (the home county), if known.
10. The user selects the person's home (permanent) country.
11. The system displays all districts in that country.
12. The user selects the person's home (permanent) district.
13. The system displays all counties within that district.
14. The user selects the person's home county.
15. The user saves the record (UC-ICE2).
16. The system validates that the name does not already exist in the system.
17. The system logs the system date as the entry date for the index.
18. The system displays the new record and the option to add additional information.
19. The system provides the option to update the name or other information.

Extensions:

15.a The system determines that the surname and first name combination match a record that is already in the system.

1. The system prompts the user to compare the two records and determine whether they are the same.
2. The user selects the matching record and edits it, or continues editing the new record, if it is different.

19.a The user selects the update option and changes the person's name.

1. The system saves the former name in the person's name history.
2. The system provides the option to view the name history.

Main Success Scenario:

1. The user selects the option to add an identification to a person's record.
2. The user selects a type of identification.
3. The user enters the identification number.
4. The user saves the record (UC-ICE2).
5. The system displays the new identification information in the person's record.
6. The system provides the option to update the identification.
7. The user repeats Steps 1-6 for each required type of identification.

Main Success Scenario:

1. The user selects the option to add demographic information to a person's record.
2. The user sets the date of birth.
3. The user selects the gender.
4. The user selects the marital status.
5. The user selects the country of birth.
6. The system displays all districts in that country.
7. The user selects the district of birth.
8. The system displays all counties within that district.
9. The user selects the county of birth for the person, if known.
10. The user saves the record (UC-ICE2).
11. The system displays the demographic information in the record.
12. The system provides the option to update the demographic information.

Main Success Scenario:

1. The user selects the option to add secondary education information to a person's record.
2. The user enters the name of the secondary school that the person attended.
3. The user selects the highest academic level achieved.
4. The system displays all certificates for that academic level.
5. The user selects the certificate that the person holds.
6. The user enters the grade obtained (optional).
7. The user enters the certificate number (optional).
8. The user saves the record (UC-ICE2).
9. The system displays the academic information in the person's record.
10. The system provides the option to update the academic information.

Main Success Scenario:

1. The user selects the type of contact to add to a record.
2. The user enters the full mailing address.
3. The user enters the telephone number.
4. The user enters the alternate telephone number.
5. The user enters the fax number.
6. The user enters the email address.
7. The user enters notes about the contact.
8. The user saves the record (UC-ICE2).
9. The system displays the contact information in the record.
10. The system provides the option to update the contact information.
11. The user repeats Steps 1-10 for each contact.

Extensions:

1.a The system determines that a contact of that type has previously been added.

1. The system does not provide the option to allow another contact of the same type.

Main Success Scenario:

1. The user selects the option to add a note to a person's record.
2. The user enters any notes or special information about the person.
3. The system displays today's date as the note entry date.
4. The user changes the note entry date, if it is different.
5. The user saves the record (UC-ICE2).
6. The system maintains and displays a log of all notes that were entered in reverse chronological order.
7. The system provides an option to update each note.

Main Success Scenario:

1. The user selects the option to record a verification in a record.
2. The user selects the date of the verification.
3. The user selects any verification changes made.
4. The user saves the record (UC-ICE2).
5. The system saves the verification changes to the person's verification history and displays the latest verification change in the record.

Extensions:

2.a The user does not select a date.

1. The system records today's date by default.

Main Success Scenario:

1. The user selects the option to add a training to a person's record.
2. The user enters the index number for the training.
3. The user selects the date of intake (optional).
4. The user selects the training institution where the student has been admitted.
5. The system displays the cadres offered by the training institution.
6. The user selects the cadre where the student is to be indexed.
7. The user enters the training end (graduation) date if the student has completed training.
8. The user saves the record (UC-ICE2).
9. The system displays the record with the training information and provides the option to document a disruption (UC-PS36), record an application to sit for the exam (UC-PS40) or issue a registration (UC-PS40).
10. The system provides the option to correct the information.

Extensions:

2.a The user selects the option to generate a new index number.

1. The system generates the next index number available upon saving the record.

4.a The user selects the country where the person was trained if the training was outside the country.

1. The user enters the name of the training institution, if known.
2. Continue to Step 6.

7.a The user sets the graduation date for before the intake date.

1. The system displays an error message and will not continue.

7.b The user enters a foreign country where the training took place.

1. The system prompts the user to enter the graduation date.

9.a The user leaves the end date blank.

1. The system marks the training as "in progress."
2. The system provides the option to set a graduation date (UC-PS38).
3. The system does not provide the option to issue a registration.

Main Success Scenario:

1. The user selects the option to update a training in the student's record.
2. The user selects the option to disrupt training.
3. The user selects the disruption category.
4. The system displays a list of specific reasons for disruption in that disruption category.
5. The user selects the specific disruption reason.
6. The user selects the date of disruption.
7. The user saves the record (UC-ICE2).
8. The system displays the record with the updated training disruption information and provides the option to document a resumption. (UC-PS37)

Extensions:

2.a The system determines that a disruption has already been recorded for the training and no resumption has been recorded.

1. The system does not provide the option to disrupt training again.

6.a The user enters a disruption date that comes before the date of intake.

1. The system displays an error and prompts to enter a valid date.

Main Success Scenario:

1. The user selects the option to update a training in a health student's record.
2. The user selects the option to resume training.
3. The user enters the date of resumption.
4. The user saves the record (UC-ICE2).
5. The system displays the record with the new resumption information and provides the option to document a disruption (UC-PS36) as well as the option to set a graduation date (UC-PS38).

Extensions:

3.a The user enters a resumption date that occurred before the disruption date.

1. The system displays an error message and will not continue.

Main Success Scenario:

1. The user selects the option to update a training in a student's record.
2. The user selects the option to set a graduation date.
3. The user enters the graduation date.
4. The user saves the record (UC-ICE2).
5. The system displays the graduation date, marks the training as complete and provides the option to issue a registration to the student (UC-PS40).

Extensions:

2.a The system determines that the training was marked discontinued.

1. The system does not provide the option to set a graduation date.

3.a The user sets a graduation date that falls before the intake date.

1. The system generates an error message and will not proceed.

Main Success Scenario:

1. The user selects the option to update a training in a student's record.
2. The user selects the option to record an exam.
3. The system displays today's date for the application date.
4. The user changes the date, if it is different.
5. The user indicates whether the student's required application materials have been received.
6. The user indicates whether the student's required application materials have been approved.
7. The user enters the endorser information, if known:
1. name
2. date of endorsement
3. qualifications
8. The system displays today's date for the exam date.
9. The user changes the exam date, if it is different.
10. The user selects the number of tries for the exam:
1. First
2. Re-try
3. Final
11. The user selects the examination results:
1. pass
2. fail
3. did not sit for exam
12. The user enters the examination number.
13. The user saves the record (UC-ICE2).
14. The system displays the record with the exam application information.
15. The system provides the option to correct the exam information.

Extensions:

5.a The user does not select an option.

1. The system saves yes by default.

6.a The user does not select an option.

1. The system saves yes by default.

9.a The user sets the exam date for before the application date.

1. The system displays an error and will not continue.

10.a The user selects final.

1. The system does not allow the exam results to be updated.

11.a The user selects fail or did not sit for exam.

1. The system provides the option to update the exam information.
2. When exam performance is re-recorded, the system displays the new results and saves the previous results to an examination history.

11.b The user selects pass.

1. The system does not allow any more updates to the exam information.

Main Success Scenario:

1. The user selects the option to update a training in a student's record.
2. The user selects the option to add a registration.
3. The user enters the registration number.
4. The system displays today's date for the application date.
5. The user changes the application date, if it is different.
6. The system displays today's date for the registration date.
7. The user changes the registration date, if it is different.
8. The user selects whether the practice type is temporary or permanent.
9. The user saves the record (UC-ICE2).
10. The system validates that the registration number does not already exist in the system.
11. The system displays the record with the registration information and provides the option to issue a new license (UC-PS41).
12. The system provides the option to correct the registration information.

Extensions:

3.a The user selects the option to generate a registration number.

1. The system generates the next registration number when the record is saved.

8.a The user does not select a practice type.

1. The system enters permanent by default.

10.a The system determines that the number exists in the database.

1. The system prompts the user to correct the number or generate a new number.

Main Success Scenario:

1. The user selects the option to update a registration in a health worker's record.
2. The user selects the option to add a license.
3. The system displays the registration number for the license number.
4. The user enters a new license number, if it is different.
5. The system displays today's date for the license start date.
6. The user changes the start date for the license, if it is different.
7. The user enters the end date for the license.
8. The user saves the record (UC-ICE2).
9. The system displays the record with the license information and provides these options: Renew a license (UC-PS45); Add a completed continuing education course (UC-PS45); Issue or renew a private practice license (UC-PS45); Document a disciplinary action (UC-PS45).
10. The system provides the option to correct the license information.

Extensions:

4.a The user generates a new license number rather than entering one.

1. The system generates the next license number when the record is saved.

7.a The system determines that the end date entered comes before or is the same as the start date.

1. The system displays an error and prompts the user to enter a different end date.

Main Success Scenario:

1. The user selects the option to update a license in a health worker's record.
2. The user selects the option to renew the license.
3. The system displays the previously issued license number for the license number of the renewal.
4. The system displays today's date for the license start date.
5. The user changes the start date for the renewal, if it is different.
6. The user enters the end date for the renewal.
7. The user saves the record (UC-ICE2).
8. The system saves the previous license to the person's license history.
9. The system displays the record with the latest license and provides an option to display the license history.
10. The system provides the option to correct the license information.

Extensions:

5.a The system determines that the start date entered comes before the end date for a previous license.

1. The system displays an error and prompts the user to correct the date.

6.a The system determines that the end date entered comes before or the same as the start date.

1. The system displays an error message and prompts the user to enter a new end date.

Main Success Scenario:

1. The user selects the option to update a license in a health worker's record.
2. The user selects the option to record a continuing education course.
3. The user selects a continuing education course that was completed.
4. The user enters the number of credit hours that were earned.
5. The user enters the start and end dates for the course.
6. The user saves the record (UC-ICE2).
7. The system displays the completed course information in the person's record.
8. The system provides the option to correct the continuing education information.
9. The user repeats Steps 1-8 for each course that the health worker has completed.

Extensions:

5.a The system determines that the end date comes before the start date.

1. The system displays an error message and prompts the user to enter a new end date.

Main Success Scenario:

1. The user selects the option to update a license in a health worker's record.
2. The user selects the option to issue a private practice license.
3. The system displays the registration number for the private practice license number.
4. The user enters a private practice license number, if it is different.
5. The system displays today's date for the license start date.
6. The user changes the start date for the license, if it is different.
7. The user enters the end date for the license.
8. The user enters the inspection results, if known.
9. The system displays today's date for the inspection date.
10. The user changes the inspection date, if it is different.
11. The user selects the health facility where the person will be practicing.
12. The user saves the record (UC-ICE2).
13. The system displays the record with the private practice license information.
14. The system provides the option to correct the private practice license information.

Extensions:

4.a The user generates a new private practice license number.

1. The system generates the next private practice license number when the record is saved.

7.a The system determines that the end date comes before or is the same as the start date.

1. The system displays an error message and prompts the user to enter a new end date.

13.a The system determines that a private practice license has previously been issued for that person.

1. The system saves the previous license as historical data and provides the option to review the past private practice license history.

Main Success Scenario:

1. The user selects the option to update a license in a health worker's record.
2. The user selects the option to record a disciplinary action.
3. The user selects the disciplinary action category.
4. The system displays a list of specific reasons for that category.
5. The user selects the specific disciplinary action.
6. The system displays today's date for the date of the disciplinary action.
7. The user changes the date of the disciplinary action, if it is different.
8. The user indicates whether the license is suspended (yes or no).
9. The user enters any notes about the disciplinary action.
10. The user saves the record (UC-ICE2).
11. The system displays the record with the updated disciplinary action information.
12. The system provides the option to correct the disciplinary action information.

Extensions:

8.a The user suspends the license.

1. The system does not permit any new actions recorded on the record other than documenting a reinstatement (UC-PS46).

Main Success Scenario:

1. The user selects the option to update a license in a health worker's record.
2. The user selects the option to enter a reinstatement.
3. The user enters the date of the reinstatement.
4. The user enters any notes about the reinstatement.
5. The user saves the record (UC-ICE2).
6. The system displays the record with the new reinstatement information and makes all license options available.

Extensions:

3.a The system determines that the reinstatement date occurred before the suspension date.

1. The system displays an error and prompts the user to change the reinstatement date.

Main Success Scenario:

1. The user selects the option to add deployment information to a health worker's record.
2. The user selects the health facility where the person has been deployed.
3. The user enters the job or post title.
4. The user enters the job or post code, if known.
5. The system displays today's date for the date of deployment.
6. The user changes the date of deployment., if it is different.
7. The user saves the record (UC-ICE2).
8. The system displays the record with the deployment information.
9. The system provides the option to correct the deployment information.

Extensions:

8.a The system determines that a deployment has previously been entered for this health care worker.

1. The system saves the past deployment to the person's deployment history and provides an option to view all past deployments.

Main Success Scenario:

1. The user selects the option to record out migration verification in a person's record.
2. The user selects the country where the request came from.
3. The user enters the worker's new address in the foreign country, if known.
4. The user selects the reason given for out migration.
5. The user records the name of the organization requesting the verification (country board), if known.
6. The system displays today's date for the date of the verification request.
7. The user changes the date of the verification request, if it is different.
8. The user saves the record (UC-ICE9).
9. The system displays the record with the out migration details.
10. The system provides the option to update the out migration details.
11. The user repeats Steps 1-8 for each out migration verification request.

Extensions:

9.a The system determines that a verification request for out migration has previously been recorded for this person.

1. The system saves and displays all out migration verification requests that have been recorded.

Main Success Scenario:

1. The user accesses the configuration screen.
2. The user selects the modules to install.
3. The system installs each selected module.
4. The system enables, or turns on, each new module.
5. The user selects the modules to turn off or disable.
6. The system de-activates the selected modules.
7. The user selects a module to configure.
8. The system displays the configuration options for that module.
9. The user sets the desired options for that module.
10. The user saves the configuration.
11. The system activates the options that the user has selected.

Extensions:

2.a The user does not install any modules.

1. Skip to Step 5.

5.a The system determines that a module is required to be enabled for the system to operate.

1. The system does not allow the module to be disabled.

Main Success Scenario:

1. The system validates that all required fields have been completed.
2. The system displays the data that the user entered.
3. The user corrects any errors.
4. The user confirms that the data are correct.
5. The system saves the data to the database.
6. The system logs the date and the username of the person who filled out the record.
7. The system displays the last modified date with the affected record.

Extensions:

1.a The user does not complete a required field.

1. The system prompts the user to complete the field and will not continue.

3.a The user does not make any corrections.

1. Skip to Step 4.

Main Success Scenario:

1. The user selects the option to search records.
2. The user enters the name to search for.
3. The user selects the type of record to search for.
4. The system displays the matching records.

Extensions:

2.a The user does not enter a name.

1. The system finds all records.

3.a The user does not select a type.

1. The system searches all types.

4.a The system does not find a matching record.

1. The system displays an error message.

4.b The system locates more than one matching record.

1. The system displays all records.

Main Success Scenario:

1. The user searches for a record (UC-ICE3).
2. The user selects the record to view.
3. The system checks the role of the user.
4. The system displays the record and all the data entered for it that the user is authorized to view.
5. The system provides options for updating or adding new data depending on the user's role and the level of data already entered in the record.

Main Success Scenario:

1. The user opens the record to update.
2. In the record, the user selects the option to update specific information.
3. The system checks the user's role.
4. The user changes the appropriate fields.
5. The user saves the record (UC-ICE2).
6. The system marks all changed data as "updated."
7. The system saves the previously entered information in that item's history log.
8. The system displays the new data with the record.

Extensions:

3.a The user's role does not allow the user to update the information.

1. The system does not provide the option to update the record.

Main Success Scenario:

1. The user opens a record.
2. The user selects the option to correct information in the record.
3. The system checks the user's role.
4. The user changes the appropriate fields.
5. The user saves the record (UC-ICE2).
6. The system marks all changed fields as "corrected".
7. The system displays the record with the corrected information.
8. The system logs that the record has been checked and the username and date of the person who made the corrections.

Extensions:

3.a The user does not have a role at the data or system administrator level.

1. The system does not provide the option to correct the record.

Main Success Scenario:

1. The user selects the option to create a new user account.
2. The user enters a username for the new user.
3. The user enters the name of the new user, if known:
1. first name
2. surname
4. The user enters an email address for the new user (optional).
5. The user selects the option to generate a random password or enter a new password for the new user.
1. If the password is entered, the user re-enters it to confirm.
6. The user selects the role of the new user.
7. The user saves the record (UC-ICE2).
8. The system enables the user account and permits a log in with that username and password.
9. The system sends an email message to the user with the username and password.

Extensions:

4.a The user does not enter an email address.

1. The system does not email the user information to the user.

5.a The user enters the new password but does not re-enter it.

1. The system prompts the user to re-enter the password and will not proceed.

5.b The system determines that the two passwords do not match.

1. The system displays an error and prompts the user to re-enter the password.

6.a The user does not select a role.

1. The system marks the new user as disabled and does not permit the new user to log in with that username and password.

7.a The system determines that the username is already in the system.

1. The system displays an error message and will not proceed.

Main Success Scenario:

1. The user selects the option to manage user accounts.
2. The system displays all user accounts.
3. The user selects the user account to change.
4. The system displays the user account information.
5. The user makes any changes.
6. The user saves the record (UC-ICE2).
7. The system saves the changes to the user account.

Extensions:

5.a The user selects No Access for the user role.

1. The system disables the account or gives it Guest access.

Main Success Scenario:

1. The user connects to the system.
2. The user enters the username and password.
3. The system validates the username and password.
4. The system determines the user's role and displays that role to the user.
5. The system displays a list of actions the user can perform based on the user's role.

Extensions:

3.a The system determines that the password is incorrect for the username entered.

1. The system prompts the user to re-enter the password.
2. The system provides the option to retrieve a forgotten password.

3.b The system determines that the username does not match a username for any account.

1. The system displays an error message.

4.a The system determines that the user has no role assigned in the system.

1. The system does not allow access.

Main Success Scenario:

1. From the login page, the user selects the option to retrieve a forgotten username or password.
2. To reset the password, the user enters their username.
1. The system emails the new password to the user.
3. To recover the username, the user enters their email address.
1. The system displays the username.

Extensions:

2.1.a The system does not find the user's email address in the database.

1. The system displays an error message.

3.a The system does not find the user's email address in the database.

1. The system cannot recover the username and displays an error message.

Main Success Scenario:

1. The user selects the option to change the password.
2. The user enters the current password.
3. The user enters the desired new password.
4. The user re-enters the new password.
5. The system resets the password.

Extensions:

4.a The system determines that the passwords do not match.

1. The system displays an error and prompts the user to re-enter the passwords.

Main Success Scenario:

1. The user selects the option to give feedback.
2. The system captures the system form that is open.
3. The system captures the username and role of the user who is logged in.
4. The system opens the feedback form.
5. The user enters their name and contact information.
6. The user enters questions or comments.
7. The user indicates whether they would like to be contacted.
8. The user sends the form.
9. The system emails the form to a feedback address including information about the system form the user was working on when they provided the feedback, the username and the user role, plus the date and time the form was submitted.
10. The system logs the contents of the feedback form.