Difference between revisions of "BingBong"

From mn/ifi/inf5750
Jump to: navigation, search
(added kanban board)
(Kanban board)
Line 62: Line 62:
 
|Grid skeleton for app
 
|Grid skeleton for app
 
|
 
|
 +
|
 +
|
 +
|-
 +
|Add basic navbar
 +
|A
 
|
 
|
 
|
 
|

Revision as of 12:41, 9 November 2016

Group members

  • August Haug Hem
  • Åvald Åslaugson Sommervoll
  • Mahasty Assi

Summary of requirements

A Cleaning and Deduplication of Events

The DHIS2 Tracker module allows people to collect individual level data. These come in two forms:

1) “Singelton” cases that are recorded only once without registration or follow-up (e.g. Outpatient data). DHIS2 calls this a single event.

2) Events linked to a person (the DHIS2 term is a Tracked Entity Instance - TEI) where you first look up a person (or register a new) who is enrolled in a health program and then follow the patient over a period, with each visit to the doctor recorded as an event, linked to the program (e.g. a TB patient). However, patients often go to different clinics for the same thing, and a lot of data is collected offline, without the possibility to check if the patient is already in the system. Therefore, there is a need to A) identify duplicate people and B) reconcile the data belonging to the same person.

The task is to make a webapp which helps administrators to easily identify clear and potential duplicates (e.g. slight misspellings) and mark them for reconciliation (which the app could also assist in). A combination of automated and manual filtering/navigation. You can initially assume the number of persons and events is small enough to be handled in the client. For more advanced functionality, it is also interesting to link to server side procedures.

Understanding

We are to clean the DHIS2 Tracker module. This will be done by finding possible duplicate entries of a patient, and presenting these findings to an admin, who can then choose to mark them for reconciliation or dismiss the finding. We see that we can also assist in the reconciliation.

This app will basically be a 2-in-1, with one functionality to find duplicate TEIs, and one functionality for finding duplicate single events. The Tracked Entity Instances have identificators like name, birth date, village and so on in order to be identified, so using those parameters we should be able to find duplicates for that instance type. Single events however, do not have these identificators, and are mainly used for statistics and follow-up on a more general basis for the database. These are noted down from paper and due to basic human errors a single event may be documented multiple times. Our job in this case is to find such single events and list them up. For both functionalities a list of results will be shown in order for the admin to mark them for reconciliation.

To present the results we have discussed and planned on setting up a single page front-end UI consisting of multiple react components, and depending on the complexity and reusability of the data at hand we might introduce a flux structure to the project as well.

Architecture

- react

- flux (redux/alt.js)

- html, css, and javascript (ofc)

(-Bootstrap)

(-http://www.material-ui.com/#/)

Planning

  • Time schedule Group session: Thursday 10-12 Work time: planned hours that fit all three participants
  • Tasks Wiki start: Åvald
  • Screenshots and screen flows TBA
  • Documented learning during project TBA
  • Suggested improvements to APIs etc TBA
  • Sample web app TBA

Kanban board

Tasks In progress Tested Finished
UI design M
Grid skeleton for app
Add basic navbar A
Split TEI and Single events in app
OrgUnit dropdown A

M

Program dropdown A

M

Date dropdown
Results area
Update Wiki A M Å

Link to repository

https://github.com/lax1n/INF5750-Project