Openmrs hr module usecases

Use Cases for openMRS HR Module

These use cases are extracted from the iHRIS Manage Use Cases.

Competency

Defines successful job performance in the organization and enables the organization to assess employee's competencies in various skills.

Use Case: CM-1 Create A Competency Model

---

The Training Manager updates a list of competency categories or competencies.

Primary Actor	Training Manager? HR Manager?
Pre-Conditions	The user must be logged in to the system.
Success Guarantee	The new competency is saved and linked to any selected parent category, and it is available for selection in various use cases.
Main Success Scenario	The user selects the option to update the competency model. The system displays a list of competencies organized by category. The user adds a new competency. The user selects whether the item is a parent category. The user enters the name of the item. The user enters a definition for the competency. The user saves the record The system makes the competency available for selection when adding competencies to a record.
Extensions	3.a The user selects an existing competency. The system opens the competency for editing. 3.b The user selects an existing parent category. The system provides the option to add competencies underneath the parent category. 4.a The user designates the competency as a parent category. The system enables competencies to be added beneath the parent category. 7.a A system determines that the competency with the same parent categories already exists in the database. The system displays an error and will not continue.

Other Resources: iHRIS Competency Model

Use Case: CM-2 Add or update a competency evaluation

---

The user updates the competency evaluations for selection within the system.

Primary Actor	Training Manager? HR Manager?
Pre-Conditions	The user must be logged in to the system.
Success Guarantee	The new competency evaluation is saved and available for selection when evaluating a course completed by an employee.
Main Success Scenario	The user selects the option to manage the list of competency evaluations. The system displays all evaluations entered in the system. The user adds a new competency evaluation. The user enters the description or name of the item. The user saves the record The system makes the competency evaluations available for selection when evaluating employees who have completed training courses.
Extensions	3.a The user selects an existing competency evaluation. The system opens the item for editing.

Use Case: CM-3 Assess an employee's competencies

---

The user adds to or updates the list of competencies obtained by an employee.

Primary Actor	Training Manager? HR Staff?
Pre-Conditions	The person has a record in the system. The user must be logged in to the system. The competency and competency evaluation must be added to the system.
Success Guarantee	The employee's competencies are saved and displayed with their record, the evaluation history for each competency is updated, and the competencies are available for searching.
Main Success Scenario	The user selects the option to add competencies to a person's record. The system displays the competency model. The user selects the competency to add. The user selects the competency evaluation (optional). The user selects the date of the evaluation. The user enters a date when the assessment expires or should be re-evaluated (optional). The system sets a flag to appear on the person's record when the date has passed that reminds the user that the person needs reassessment. The user saves the record The system saves the competency information and displays it in the record. The system provides the option to update the competency or view the evaluation history for any competency.
Extensions	3.a The system detects that the competency is a parent category. The user checks the category to add all subcategories and competencies within that category to the record. The user expands the category to select subcategories or competencies within the category for addition to the record. 5.a The user does not select an evaluation date. The system enters today's date by default.

Disciplinary Action

Not written.

Leave Tracking

Not written.