Complete Report by Package - Full Details

Tuesday, February 19, 2008, 3:22:27 PM

1. iHRIS Qualify - Core Functional
Actors:
A-PS1 Data Operations Manager
A-PS2 Records Officer
A-PS3 Registration Supervisor
A-PS4 Examination Supervisor
A-PS5 Decision Maker
A-PS6 Any User

1.1. Data Administration
Use Cases:
UC-PS1 Add or update a qualification
UC-PS2 Add or update a cadre
UC-PS3 Add or update a continuing education course
UC-PS4 Add or update a disciplinary action category
UC-PS5 Add or update a reason for disciplinary action
UC-PS6 Add or update a reason for out migration
UC-PS7 Add or update a training disruption category
UC-PS8 Add or update a reason for training disruption
UC-PS9 Add or update an academic level
UC-PS10 Add or update a certificate
UC-PS11 Add or update an identification type
UC-PS12 Add or update a marital status
UC-PS13 Add or update a country
UC-PS14 Add or update a region
UC-PS15 Add or update a district
UC-PS16 Add or update a county
UC-PS17 Add or update a health facility
UC-PS18 Associate a training institution with a health facility
UC-PS19 Add or update a training institution
UC-PS20 Associate a health facility with a training institution
UC-PS21 Add or update a pre-service training program
UC-PS22 Enter inspection information
UC-PS23 Add or update a facility agent
UC-PS24 Add or update a facility type
UC-PS25 Add or update a facility status

1.2. Record Management
1.2.1. General
Use Cases:
UC-PS26 Enter a new record
UC-PS27 Add identification information
UC-PS28 Add demographic information
UC-PS29 Add academic information
UC-PS30 Add contact information
UC-PS31 Record notes
UC-PS32 Upate a record
UC-PS33 Correct data

1.2.2. Training
Use Cases:
UC-PS34 Index a training
UC-PS35 Record a discontinuation
UC-PS36 Record a resumption
UC-PS37 Set a graduation date
UC-PS38 Record exam details

1.2.3. Licensing
Use Cases:
UC-PS39 Issue a registration
UC-PS40 Issue a license
UC-PS41 Renew a license
UC-PS42 Add continuing education credits
UC-PS43 Issue a private practice license
UC-PS44 Document a disciplinary action
UC-PS45 Document a reinstatement
UC-PS46 Update deployment information
UC-PS47 Record out migration verification

1.3. Search
Use Cases:
UC-PS48 Search for a record
UC-PS49 View a record

1.4. Dual Data Entry
Use Cases:
UC-PS50 Check data entry errors
UC-PS51 Check data quality
UC-PS52 Process an unverified record
UC-PS53 Spot-check records

1.5. Requirements
Requirements:
REQ-PS1 Customization
REQ-PS2 Geographical locations
REQ-PS3 Index numbers
REQ-PS4 Upgrades
REQ-PS5 Training location
REQ-PS6 Examination numbers
REQ-PS7 Examination attempts
REQ-PS8 Private practice license numbers
REQ-PS9 Disciplinary action
REQ-PS10 License renewal dates
REQ-PS11 Registration numbers
REQ-PS12 Registration requirements
REQ-PS13 Multiple registrations
REQ-PS14 License numbers
REQ-PS15 License renewals
REQ-PS16 Suspension of license

2. iHRIS Common
Actors:
A-ICE1 System Administrator
A-ICE2 Any User
A-ICE3 Data Analyst

2.1. System-wide
Use Cases:
UC-ICE4 Configure modules
UC-ICE9 Save a record

2.2. User Administration
Use Cases:
UC-ICE1 Add a user account
UC-ICE2 Update a user account

2.3. User Access
Use Cases:
UC-ICE6 Log in
UC-ICE8 Retrieve a password or username
UC-ICE3 Change password
UC-ICE5 Give feedback
UC-ICE7 Log out

2.4. Reporting
Use Cases:
UC-ICE12 Run a preconfigured report
UC-ICE11 Customize a report
UC-ICE13 Save a report
UC-ICE10 Access a saved report

2.5. Offline Tool
Use Cases:
UC-ICE14 Install the offline tool
UC-ICE15 Import data
UC-ICE16 Export data

2.6. Requirements
Requirements:
REQ-ICE1 Cadres
REQ-ICE2 Technology requirements
REQ-ICE3 Multilingual support
REQ-ICE4 Log usage
REQ-ICE5 Leveragability
REQ-ICE6 Integratability
REQ-ICE7 Idle logout
REQ-ICE8 GIS mapping
REQ-ICE9 Extensibility
REQ-ICE10 Data reliability
REQ-ICE11 Compatibility
REQ-ICE12 Caching of report data
REQ-ICE13 Authorization
REQ-ICE14 Auditing
REQ-ICE15 Archival
REQ-ICE16 Authentication
REQ-ICE17 Data import

1. iHRIS Qualify - Core Functional

iHRIS Qualify - Core Functional

 File: PowerSupply.ucd
Description
iHRIS Qualify is a health worker training, licensing and certification tracking system.
Related Documents and URLs
https://launchpad.net/ihris-qualify
http://www.capacityproject.org/hris/suite/ihris_qualify.php
Notes Date Added
This documentation refers to the core version of the Training, Certification and Licensure database (working title: PowerSupply) 8/2/2006
This documentation was based on specifications gathered for Uganda UNMC release and also serves as documentation for that release. (UNMC release version 1.0) 7/13/2006

iHRIS Qualify - Core Functional actors:

A-PS1

Data Operations Manager

Parent: iHRIS Qualify - Core Functional
Description
This person is responsible for managing data entry and data entry roles, including verifying and correcting data and updating standard lists in the system.
Goals
Create or update standard lists of data within the system.
Check for, correct and report on data entry errors.
Notes Date Added
Can perform any use case that a Records Officer, Examination Supervisor or Registration Supervisor can. 7/13/2006


A-PS2

Records Officer

Parent: iHRIS Qualify - Core Functional
Description
This person is responsible for basic data entry, including initial indexing and upgrades of health professional students entering training programs, tracking out migration verifications and demographic data entry.
Goals
Create a new record for a health worker or student.
Add information to or update a record with demographic, contact, identification or academic information.
Add training program information to a health student's record.
Record out migration verification requests and deployments in a health worker's record.
Add notes to a record.
Re-enter a record to ensure data quality.
Notes Date Added
Can enter examination results when they are not required and the Examination Supervisor role is not activated. 6/4/2007


A-PS3

Registration Supervisor

Parent: iHRIS Qualify - Core Functional
Description
This person is responsible for data entry related to licensing updates, including entering initial registration, issuing new licenses and license renewals, issuing and renewing private practice licenses, and registering and licensing foreign-trained health care professionals applying to work in the country.
Goals
Issue registrations and licenses to a health worker.
Record continuing education credits in a health worker's record.
Record disciplinary actions in a health worker's record.
Record deployment information in a health worker's record.
Notes Date Added
Can perform any use cases that a Records Officer can. 7/13/2006


A-PS4

Examination Supervisor

Parent: iHRIS Qualify - Core Functional
Description
This person is responsible for data entry related to national exams, including verifying applications to take exams and recording results. This is an optional role, used only when entering examination results is required for the system.
Goals
Record information about national exam applications and results.
Notes Date Added
Can perform any use case that a Records Officer can. 7/13/2006
The Examination Supervisor will not be a role in the core release system. 6/11/2007


A-PS5

Decision Maker

Parent: iHRIS Qualify - Core Functional
Description
This person runs reports in order to view and analyze data, and make health workforce policy and planning decisions. This person does not perform any data entry tasks.
Goals
Generate reports to analyze data entered in the system.


A-PS6

Any User

Parent: iHRIS Qualify - Core Functional
Description
A generic user (applies to all users of the system).
Goals
Search for and view a record.

1.1. Data Administration

Data Administration

Description
Create and update standard lists of data for selection in system menus.
Notes Date Added
Access is limited to System Administrators and Data Operations Managers. 10/15/2007
Locate these functions via the Configure System / Administer Database link on the main menu. 10/15/2007

Data Administration use cases:

UC-PS1

Add or update a qualification

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds or edits the list of qualifications that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new qualification is saved and available for selection in various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.
Open Issues AssignedTo ResolveBy
For all Data Administration actions, the Data Operations Manager should be able to access these via the Configure System menu option. LD 3.0 release


UC-PS2

Add or update a cadre

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager enters or edits a cadre for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
Each cadre, as applied by the health professionals, is defined within the system and available for selection in various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.


UC-PS3

Add or update a continuing education course

 P2
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager enters valid continuing education courses for selection when renewing a license.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new continuing education course is saved and available for selection in appropriate use cases.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

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-ICE9).
  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.


UC-PS4

Add or update a disciplinary action category

 P2
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds a new broad category to contain reasons for disciplinary action.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The category is successfully added to the system and is available for selection in applicable use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

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-ICE9).
  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.


UC-PS5

Add or update a reason for disciplinary action

 P2
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds or edits a reason for disciplinary action for display in selection menus.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The reason is successfully added to the system and is available for selection whenever its parent category is selected.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

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-ICE9).
  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.


UC-PS6

Add or update a reason for out migration

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds or edits a reason for out migration to the system and makes it available for selection.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The out migration reason is saved to the system and is available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.


UC-PS7

Add or update a training disruption category

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds a new broad category to contain reasons for training disruption.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The category is successfully added to the system and is available for selection in applicable use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE29).
  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.


UC-PS8

Add or update a reason for training disruption

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds or edits a reason for training disruption for display in selection menus.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The reason is successfully added to the system and is available for selection whenever its parent disruption category is selected.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.


UC-PS9

Add or update an academic level

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds or edits the list of academic levels that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new academic level is saved and available for selection in various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.


UC-PS10

Add or update a certificate

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager updates the list of certificates that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The certificate is added to the system and available for selection when its parent academic level is selected.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.


UC-PS11

Add or update an identification type

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager updates a list of identification types that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new identification type is saved and available for selection when adding an identification.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.
Notes Date Added
This use case is identical for both iHRIS Manage and Qualify. 10/31/2007


UC-PS12

Add or update a marital status

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds a new marital status to the system that is available in selection lists.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The marital status is added to the system and is available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.
Notes Date Added
This use case is the same for both iHRIS Manage and Qualify. 10/31/2007


UC-PS13

Add or update a country

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager updates the list of countries available for selection in the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed country is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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 saves the record (UC-ICE9).
  8. 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 system determines that the country and country code are already in the database.
  1. The system displays an error and will not continue.
Referenced Requirements Type ID
Geographical locations Business Rule REQ-PS2
Notes Date Added
This use case is the same for iHRIS Manage and iHRIS Qualify. 10/31/2007
Geographical locations are tied together from largest to smallest: country --> region --> district, state or province --> county or sector. 10/31/2007
The country list also displays nationalities for selection. 10/31/2007


UC-PS14

Add or update a region

 P9
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager updates the list of regions available for selection in the system and establishes the region's parent country.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed region is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.
Referenced Requirements Type ID
Geographical locations Business Rule REQ-PS2
Open Issues AssignedTo ResolveBy
Redesign needed: If a new parent location is added from a link on the new location's page, the Return button should go back to the original location being added. Not implemented. 153037 n/a
Notes Date Added
This use case is identical for iHRIS Manage and iHRIS Qualify. 10/31/2007


UC-PS15

Add or update a district

 P9
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager updates the list of districts available for selection in the system and establishes the district's parent region.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed district is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.
Referenced Requirements Type ID
Geographical locations Business Rule REQ-PS2
Open Issues AssignedTo ResolveBy
Redesign needed: If a new parent location is added from a link on the new location's page, the Return button should go back to the original location being added. Not implemented. 153037 n/a
Notes Date Added
This use case is identical for iHRIS Manage and iHRIS Qualify. 10/31/2007


UC-PS16

Add or update a county

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager updates the list of counties available for selection in the system and establishes the county's parent district.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed county is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-ICE9).
  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.
Referenced Requirements Type ID
Geographical locations Business Rule REQ-PS2
Notes Date Added
The use case is the same for iHRIS Manage and iHRIS Qualify. 10/31/2007


UC-PS17

Add or update a health facility

 P1
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager adds a new health facility or updates an existing health facility in the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The health facility is added to the system and is available for selection from lists in various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

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-PS30).
  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-ICE9).
  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.
Notes Date Added
The health facility identification code is optional and is numbers only. 8/23/2006


UC-PS18

Associate a training institution with a health facility

 P2
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager selects one or more training institutions that are associated with a particular health facility.
Preconditions:
The user must be logged in to the system. The health facility's record must have been previously created.		 Success Guarantee:
The health facility is successfully associated with the training institution.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

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-ICE28).
  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.


UC-PS19

Add or update a training institution

 P2
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager enters identifying information about a training institution so that it may be used within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The training institution is successfully entered into the database and is available for selection in other use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

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-PS30).
  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-ICE9).
  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.
Notes Date Added
The institution/centre code is numbers only and is optional. 8/23/2006


UC-PS20

Associate a health facility with a training institution

 P2
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal
The Data Operations Manager selects one or more health facilities that are associated with a particular training institution.
Preconditions:
The user must be logged in to the system. The training institution's record must have been previously created.		 Success Guarantee:
The training institution is successfully associated with the health facility.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

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-ICE28).
  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.


UC-PS21

Add or update a pre-service training program

 P2
Parent: Data Administration
Primary Actors: Data Operations Manager Supporting Actors:
Brief Description/Goal