Theme | Feature | O3 Status | Priority | Notes/Comments |
|---|
Registration | No nickname (only first, middle, last) and no ability to configure order of name fields (last, first) vs (first last)
| | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | To Config |
|---|
|
| | This is stored behind the scenes as middle name, and is possible because the O1/O2 user interfaces are both built to support/respect the name template configuration, which is not yet built into O3. This has been ticketed here: | Jira Legacy |
|---|
| server | OpenMRS Issues |
|---|
| serverId | 45c5771b-fa4b-3e43-b34a-c19dc45ccc95 |
|---|
| key | O3-2115 |
|---|
|
Fiona Anderson / David DeSimone to check whether either of these are actually requirements for SL, or if they were only inherited as requirements from initial Haiti configuration. |
| Registration | Retrospective registration. If a registration encounter is configured, the user must be able to specify a retrospective registration date, rather than always recording the entry date. | | | See | Jira Legacy |
|---|
| server | OpenMRS Issues |
|---|
| serverId | 45c5771b-fa4b-3e43-b34a-c19dc45ccc95 |
|---|
| key | O3-1835 |
|---|
|
|
| Registration | Editing patient details fails to properly handle text-based obs. This is needed for editing the Birthplace obs that is captured in SL registration. | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | To Config |
|---|
|
| | See: | Jira Legacy |
|---|
| server | OpenMRS Issues |
|---|
| serverId | 45c5771b-fa4b-3e43-b34a-c19dc45ccc95 |
|---|
| key | O3-2116 |
|---|
|
|
| Registration | Address Hierarchy does not work correctly. There are a number of bugs and issues that have been identified with the address hierarchy widget which need to be addressed. | | | See: | Jira Legacy |
|---|
| server | OpenMRS Issues |
|---|
| serverId | 45c5771b-fa4b-3e43-b34a-c19dc45ccc95 |
|---|
| key | O3-2098 |
|---|
|
(primary ticket), and associated tickets O3-1834, O3-1753, O3-1754, O3-2097 |
| Registration | Registration needs to support collection obs groups. This is needed for capturing the patient's "contact person", which is stored as an obs group with contact "name, relationship, address, phone number" | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | To Config |
|---|
|
| | See: | Jira Legacy |
|---|
| server | OpenMRS Issues |
|---|
| serverId | 45c5771b-fa4b-3e43-b34a-c19dc45ccc95 |
|---|
| key | O3-2102 |
|---|
|
|
| Registration | Additional Identifiers: In PIH SL, user can add an additional identifier e.g. if they are one clinic (like Wellbody) they can enter in the id the patient has for another clinic (KGH) In O3, user can add additional identifiers by clicking "configure" but the UI needs to be worked on and the functionality needs to be tested | | Status |
|---|
| colour | Yellow |
|---|
| title | To Config |
|---|
| Status |
|---|
| colour | Yellow |
|---|
| title | Medium |
|---|
Registration | ID Card Printing | | |
| | Registration | Add Relationship: in O3, relationship types appear multiple times in the dropdown | | Status |
|---|
| |
|---|
| colour | Yellow |
|---|
| title | To Config |
|---|
|
| |
|
| Edit Details | When editing patient details, not all fields can be edited. | | |
|