The form should reflect the latest state of the mockup (https://app.moqups.com/symeda/3NUENEwuOE/edit/page/ac9326123)

• Add "nickname" and "mother's maiden name" to Person
• Adjust ui person form
• Adjust app person form
• Change address caption to "Address, landmarks"
• and address details to "Community contact person"
• Find a way to select the occupation health facility based on region, district, community

• add status in sormas-api TaskStatus
• make sure web-ui relfects the changes
• add "not executable" button to TaskEditActivity (see https://app.moqups.com/symeda/3NUENEwuOE/edit/page/af894caab)
• add "not executable" filter tab in TasksActivity

• check account validation mail

The district, community and facility values from the "case data" tab are missing after the following has happened:

• Open the case
• Switch to the symptoms tab
• Wait for a few seconds
• Switch to the patient tab
• Switch to the case data tab

The (likely) reason is that the onResume() method of the case data tab is already called when the patient tab is opened which results in the selectedValue variable for the region spinner to return null (which, in turn, means that no district will be selected).

Grid with visits based on the moqup: https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a83c38300

• New tab for visits
• VisitsGrid with date, status, remarks, temperature, symptoms
• Logic that decides which visits bellong to a contact: All with the same disease and within lastContactDate and followUpUntil
• Method to switch between contact visits and all visits of the person

• Make the data provided in xls-files located in ../SORMAS/Test data available as resource in server
• Import complete data
• Remove data of Abia

When the user taps the caption of a field a pop-up with the field's description should be shown.
This should be implemented for all our custom fields (PropertyField).

• show number of pending tasks in cases grid
• show number of pending tasks in contacts grid
• update moqups

• add classification column and follow-up column
• add "number of visits" column, e.g. "5 (3 missed)"
• add "follow-up days left" column
• fix "Case disease" caption

See https://docs.google.com/spreadsheets/d/1BA_RjM-ZhxFrzpAJdv0UVGhicHXNP6JnPBA-xzdrQKs/edit#gid=466434037

When the user open's a task in the app it should be possible to jump to the associated case.

• Open case on click
• Redesign label to make obvious that it's a link
• Make sure that the user is redirected back to the task when clicking the back button

Sprint 10 review:

• make link method on labelField and give ClickListener as param

• visits tab within ContactEditActivity
• fragment layout for list items (see https://app.moqups.com/symeda/3NUENEwuOE/edit/page/ac88e9649)
• select all visits of the contact's person with the disease that took place between contact.reportDate and contact.followUpUntil
• don't show "save, info" status bar buttons (see #4)
• Order by "date of visit"

• in tasks view set default-filter to pending + not executeable

• "+" create button in case contacts list
• ContactNewActivity, add to hierarchie in manifest
• Create contact form layout based on mockup: https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a824a2bbc
• First and last name are used to search for a matching person afterwards. Find a good way how to hand this over the next step. Have a look at sormas-ui (ContactCreateFrom) as reference.
• Next step: search for matching persons. If existend show selector popup: https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a0953e7fe
• If not existent just create a new person
• Afterwards jump into ContactEditActivity (see #7 )
• validate lastContactDate is before reportDateTime

The current moqup still is mixed with reporting components:
https://app.moqups.com/dta16/J6Y5spmqrH/view/page/ab9bf07f6?ui=0

• Reduce the moqup to what is needed for the prototype
• Define what exactly is shown on the map

This should be shown in the top right of the screen.

• Create this in the moqups
• Set a style for displaying the name
• Show name of active case
• Show name of active contact

• only editable for assigned user

• Copy visit entity from sormas-backend
• Adjust annotations to ORMlite
• Update DatabaseHelper init/update logic, database version++
• DAO service and entity sync

Example: When an officer is assigned to a contact task he needs to get access to the referenced contact as well and this probably also includes the case referenced by the contact.

Solution A would be to give the officer only access to data he is somehow assigned to (as described in the example).

Solution B is to make all data of the officer's regional area (LGA) available on the phone. In this scenario the list of cases, contacts and events should by default filter to the entries of the officer.

Define the rules that define which data is send to a phone for the following items:

• Cases
• Contacts
• Events
• Tasks
• Persons

• case.person should be ManyToOne relation (app & backend)
• remove person.case (app & backend)
• make sure this doesn't cause problems
• new case (app): allow the selection of persons that already have a case

• person in hospital will send lab material physically (probably informant)

• at the same time enters sample data into the system

• UID of system + another UID from the lab form

• lab person receive sample and has to match it to entry in sormas

• enters lab result for the sample

• list of test typs: relevant disease, result options

• list of labs with definition of test types

• possible 2 step process: forward to another lab

• multiple tests per sample

• sample: UID, Text-ID, Sample referral (lab), 2nd level sample referral, kind-of material + other, date+time of sampling (collecting), timestamp of shipment, shipment details, status: Shipped, Received & Pending, Further testing, Referred to other lab, Tested

• test: kind of test, date+time, lab, result (depends on kind of test; can also be text) + text-field, verified (user has to enter verification pin)

• App Sample list in case: https://app.moqups.com/symeda/3NUENEwuOE/view/page/a628db1d7
• App Sample list: https://app.moqups.com/symeda/3NUENEwuOE/view/page/a90a1bc36
• App Sample create/edit: https://app.moqups.com/symeda/3NUENEwuOE/view/page/a780f96e8
• Web-UI Sample list: https://app.moqups.com/symeda/3NUENEwuOE/view/page/adc9a738c
• Web-UI sample list in case: https://app.moqups.com/symeda/3NUENEwuOE/view/page/afc481082
• Web-UI Sample create/edit: https://app.moqups.com/symeda/3NUENEwuOE/view/page/a2a53e848
• Web-UI Sample Tests list: https://app.moqups.com/symeda/3NUENEwuOE/view/page/a2a53e848
• Web-UI Sample Tests create/edit: https://app.moqups.com/symeda/3NUENEwuOE/view/page/a6f3132e2
• DataDictionary Sample, SampleTest

We need custom fields that implement the PropertyField interface (see SymptomStateField for comparison).

• TextField
• DateField (see FormTab.addDateField)
• SpinnerField (see FormTab.makeSpinnerField; the add*SpinnerField methods probably need a better name afterwards)
• RadioGroupField (e.g. for Contact.contactProximity)
• Label (caption + text; e.g. Case ID in case data form)
• Refactor existing layouts to use these fields.
• Would be great to remove FormTab.getModel.
• Refactoring (-> outsource spinner creation methods)
• Replace age and phone fields with number fields
• Bug: age field edit is not saved
• Bug: Districts and communities are selectable no matter which region/district has been chosen in location dialog

Example in case person form:
When you enter the last name field and use the "next" button of the keyboard the spinner for the gender doesn't open and the keyboard stays open.

When opening a task in the app the description needs to be wrapped to multiple lines.

This is basic implementation of the logic that is not complete

• Add status "no follow-up"
• Show follow-up until and status in contact form
• Duration: Ebola, Cholera 21 days, Lassa 6 days
• Leave empty and set follow-up status to "No follow-up" for other diseases
• Reference for calculation is the reporting date (since this is always later than the last contact date and we can't be sure the last contact date is correct)

• Case, home-button, edit links, ...
• Contact

https://developer.android.com/training/swipe/add-swipe-interface.html#AddSwipeWidget

• add pull down to refresh functionality

We should use this issues tracking as well. it would be a great way to keep stakeholders updated

Supervisors should receive notifications for specific events via e-mail so they (1) have a trigger to look into SORMAS and (2) don't miss important news.

Trigger events:

• task is to be started or due (supervisor + national)
• lab result comes in (case & surveillance)
• contact becomes symptomatic (contact & surveillance) - following the same rules as the "symptomatic" column in visits directory
• case classification changed (case, contact & surveillance)

Tasks:

• build a service that can be called when an event happens
• service handles sending an email (and/or SMS later)
• define texts for all events. Ideally these should be short, so they work as SMS as well. OR: Provide a short and a long text (with link).
• call the service from the above triggers (from facade)
• for tasks add a timed method that checks for due tasks (see app for logic)
• create e.g. onCaseChanged method that contains email logic and method calls such as updateInvestigationByStatus etc.

• officer app: reason is required when setting task to not executable

Add listener to update the visibilty of chosen buttons in the statusbar in the cases edit activity.

​https://developer.android.com/guide/topics/ui/menus.html#ChangingTheMenu
​https://developer.android.com/guide/topics/ui/menus.html#groups 

• Contact list component within a new tab for the CaseEditActivity
• ContactListFragment based on moqup: https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a5d505aaa
• Order by "Date of last contact"
• Don't show save- and help-buttons (based on #4)

• define what to do

[api + backend]

• use sormas-api/tools/Fields.xlsx to update SymptomsDto from DataDictonary (copy into "Fields" worksheet)
• update .properties (also from Fields.xlsx)
• use DtoAdoCodeGenerator.generateCopyJava() for SymptomsFacadeEjb.toDto and .fromDto
• add missing members to Symptoms
• use DtoAdoCodeGenerator.generateNotMatchingMembersList to find no longer needed members in Symptoms
• sormas_schema SQL
• use DtoAdoCoderGenerator.generatePropertyConstantsJava

[ui]

• update SymptomsForm; order symptoms as in DataDictionary
• date of onset only required when any symptom
• update SymptomsForm layout

[app]

• update Symptoms entity
• update layout
• date of onset only required when any symptom. should probably be asked last in app (but displayed first in webui)

• Create ContactEditActivity with tabs
• Contact data form based on moqup: https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a766c1c84
• Date, proximity and description are editable
• Refactor CasePersonTab to PersonTab and use it within CaseEditAcitvity and ContactEditActivity (argument should be the person id, not the case)

The ratio has to be set according to the test smartphone

• "source case" for contact in app (https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a766c1c84)
• "visits" -> "follow-up visits"
• possible contact -> unconfirmed contact
• app contact list: "4 days" -> "4 days ago"

• Add followUpUntil to Contact
• Split ContactStatus to FollowUpStatus ("Follow-up", "Follow-up completed", "Follow-up canceled", "Lost to follow-up") and ContactClassification ("Possible contact", "Confirmed contact", "Not a contact", "Converted to case", "Dropped (case disproved)")
• update ContactDto and ContactIndexDto accordingly
• Create visit based on data dictionary with reference to person and relevant disease

• CasesView
• ContactsView
• TasksView
• UsersView/OfficersView
• for each filter use fieldCaption of the filtered column

• CaseClassification: Possible case, Suspect, Probable, Confirmed, Not a Case
• InvestigationStatus: investigation pending, investigation done, discarded
• Update data dictionary

Based on data dictionary: https://docs.google.com/spreadsheets/d/1BA_RjM-ZhxFrzpAJdv0UVGhicHXNP6JnPBA-xzdrQKs/edit#gid=370159711

• Create web ui mockup of case epi data form
• Create app mockup of case epi data form
• Add hospitalization to case data form in web ui
• Add hospitalization to case data form in app
• Add contact relation and contract location to contact mockups
• Complete list of relation types needed

• Copy contact entity from sormas-backend
• Adjust annotations to ORMlite
• Update DatabaseHelper init/update logic, database version++
• DAO service and entity sync

• Add FieldHelper class to components package and add SpinnerField initialization methods
• Merge toItems and addItems methods
• Remove commit method from FormTab and all subclasses

• comment field for the follow-up status (e.g. when lost) or contact description required
• follow-up duration logic: when no visit took place the last day of follow-up, the duration needs to be extended
• edit follow up status: "follow-up", canceled and lost - others are set by the system

• create VisitEditForm for all fields of a visit (see app as reference: https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a4cea690b)
• show form in a popup for a chosen visit
• allow the creation of new visits for a person

See ContactListFragment in CaseEdit for TaskListFragment

• use the case- or contact context for loading from db
• back-navigation from task (edit/create activity) to tasklist inside the case / contact

• Generate task for case with investigation status pending
• Assign to officer or supervisor
• Officer can do task or set it to "not executable"
• Investigation status is updated accordingly (pending, canceled, done)
• Creating a new "investigate case" task will update the case investigation status
• Nobody can change the investigation status manually
• Wrap logic in own service
• Process diagram to visualize what is happening

• "+" create button in contact visits tab
• New visit is assigned to the contact's person and has the same disease as the contact's case
• VisitNewActivity, add to hierarchie in manifest
• Create visit form layout based on mockup: https://app.moqups.com/symeda/3NUENEwuOE/edit/page/a4cea690b
• Afterwards go back to where we came from (e.g. contact visits)
• only contact officer is allowd to create visits

This is caused by the layout auto-focusing the first field and the dateField having a focusListener that shows the pop-up.

Either: Make sure the dateField doesn't show the popup when the focus is set on form enter (see FormTab.addDateField)
Or: Deactivate auto-focus for forms (if possible).