Outstanding HR Module Tasks for GSOC and Beyond
ID | Priority | Description | Dep. | Sub of | Who | Status |
---|---|---|---|---|---|---|
1 | M | Develop tests |
|
| SM |
|
2 | H | Prepare Jasper reports for all basic reports | 16 |
| RF |
|
3 | H | Figure out strategy for module deployment |
|
| SM+ | Started |
4 | H | Implement strategy for module deployment | 3 |
| SM | Due Mon v.1 |
5 | H | Document module features and deployment | 2, 4, 8, 15 |
| SM | 1st draft Thu |
6 | H | Clear up permissions -- what is needed, what is implemented |
|
| RF, SM | Started |
7 | L | Voiding/Purging of Post History, Assignment |
|
| DF |
|
8 | H | Make look and feel uniformly OpenMRS-like |
|
| SM, DF | Done |
9 | F | Implement education and certification |
|
|
|
|
10 | F | Implement leave |
|
|
|
|
11 | F | Implement competency, notes, evaluations |
|
|
|
|
12 | F | Implement training |
|
|
|
|
13 | F | Implement web services (data exchange resources) |
|
|
|
|
14 | F | Implement web services (other resources) |
|
|
|
|
15 | M | Implement person-centric business logic |
|
| SM | Done |
16 | H | Implement report selection/generation |
|
| SM | Done |
17 | L | Setting of staffatributetodisplay from edit staff attributes |
| 8 | SM | Done |
18 | H | Deal with edit pages for personnel transaction buttons |
| 8 | SM | Won't change |
19 |
|
|
|
|
|
|
20 |
|
|
|
|
|
|
21 |
|
|
|
|
|
|
Installation Package
With data only possible if 7777xxx series is available in Person, Concept
| W/O | With |
---|---|---|
HR Table Structure | Liquibase | Liquibase |
Isco_Code Data | Liquibase | Liquibase |
Status concepts | Metadata | Liquibase |
Location tag | Metadata | Liquibase |
Concept Maps | Metadata | Liquibase |
Test Concepts |
| Liquibase |
Test Locations |
| Liquibase |
Test Persons |
| Liquibase |
Test HR Tables |
| Liquibase |
Global Properties | Liquibase | Liquibase |
Report Templates | Installer | Installer |
Report Tables if used | Liquibase | Liquibase |
|
|
|
Installation Screen
Roles and Privileges
Post-centric uses Weak Clerk role
Person-centric uses Strong Clerk role
Both use manager; Weak/Strong differ based on OpenMRS knowledge
Weak manager could also be used by clerk during initial data load
Privilege | Weak | Strong | Weak | Strong | Admin |
---|---|---|---|---|---|
Create loc tag/staff property |
|
|
|
| X |
Set global var |
|
|
|
| X |
Create/Edit loc |
|
| X | X | X |
Create/Edit person |
|
| X | X | X |
Create/Edit staff | X | X | X | X | X |
Edit concept map |
|
|
| X | X |
Create/Edit concept |
|
| X | X | X |
Create/Edit job title |
| X | X | X |
|
Create/Edit post |
| X | X | X |
|
Create/Edit post history | X | X | X | X |
|
Create/Edit assignment | X | X | X | X |
|
Void/Purge HR Tables |
|
|
| X | X |
Manage BIRT |
|
|
| X | X |
Run BIRT | X | X | X | X | X |
Reporting
Create a static web page for the reports
Create our own call to Jasper reports
Document use of Jasper reports in documentation