...
| Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|
| 1 |
| Support mCSD profile
|
| High |
| | Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-4188 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-5260 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-5261 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-5262 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-5351 |
|---|
|
|
| 2 |
| OpenLMIS serving mCSD Locations (Care Service Update Provider - Use Case 1)
|
| High |
|
|
| 3 |
| OpenLMIS as a consumer of mCSD Locations (Care Service Update Consumer - Use Case 2) - Update "Facility Admin" screen to support FHIR Location's shared through a Care Services Update Consumer. AKA follow a facility list / read only.
- Support sync of OpenLMIS and FHIR resources
|
| High |
|
|
| 4 |
| Update Reporting stack to use Location instead of OpenLMIS' Facility |
| Med | Esp useful if reporting stack is leveraged in communicating to other systems. e.g. in aggregation phase to DHIS2. |
|
| 5 |
| Update "Facility Admin" screen to support Care Services Update Supplier. AKA create federated "Facilities" / Locations inside OpenLMIS and share. |
| Low | Not needed for simple interop with ERP, Facility Edition, etc so long as the level of definition of "facility" is consistent across systems and nesting isn't needed. |
|
...
Work breakdown of epic and spikes : https://www.lucidchart.com/documents/edit/ce222755-b782-49d2-9c09-f4e6680a9637/0?shared=true&as of 9/12/18:
Image Added
...