5 February 2019

Agenda

1. Review of Previous Week’s Action Items
1. Action item: End of month, Craig deliver narrative for version 2

Ona shared narrative for v2

1. Action:  Bid on reveal.io → waiting to hear back by Feb 23
2. Follow up: Use case tests - Craig is working on this and will get over to VW end of Wednesday (Importing locations and coordinates)

This is done - just waiting on one for Nifi

1. Follow up: CHAI to send the forms Botswana and Namibia are using

Sameen has the forms, Pierre has them too - please share

1. Follow up: Craig to work with Connor to connect Jonathan re algorithm UI

To happen down the line, for R3

1. Team Updates
1. Akros

Thailand forms - need by Tuesday next week latest to not affect dev timelines for R2

1. These need to be added to the data dictionary with field level detail and skip logic
2. We are just waiting on Thailand
3. *Puts the release date and schedule date at risk*

Field testing this week - share full results early next week

Subcontracts coming end of week

Akros to share Narrative, Configuration Doc, and Marvel by end of week

1. Ona

Update

1. V1.2 released yesterday with sync-based bug fixes
1. Cleans up bugs found by Akros and VW during 1.1 testing
2. Shipped documents to Akros:
1. Narrative (Annie to add link)
2. Major UI Changes for Review
3. Configuration Document
3. Field Testing configuration:
1. Added the basemaps to the Android client
2. Added points for three new districts to the mSpray dashboard and Reveal
3. Added locations to OpenMRS and user accounts
4. Craig is finalizing everything this and testing today
4. Scoping continues
1. Filling out data dictionary
2. UI mock-ups shared with Akros (including video)
3. Sam is scoping domain objects and high level engineering changes with the team
4. Conor is beginning work on the Web UI on Monday
5. Development on the family module is beginning tomorrow
5. Need support on forms:
1. We need to create about 8 forms as defined in the high level narrative
6. GeoWidget work:
1. The team is working on integrating the GeoWidget’s sample application with the Common GeoRegistry
2. There are only a few items required

Form configuration - can we confirm when this is scoped for?

1. Not ready to discuss this. Craig needs to discuss this with Matt and the engineering team.
1. UCSF

Update

1. Making progress on thinking through infrastructure and how users would make requests to the API. Started playing with code

UI - is a way to test and access algorithm without code

1. Understanding is that it is not user-facing
2. Could still use just won’t render the full picture in the UI but could export a file with the full output
1. Craig: how often will this be run? In Reveal planning interface we have fields that say we have xxx LOE based on 5 team members hitting 5 structures each in a day
2. Web service needs to be responsive to potential frequent requests. This is an intensive algorithm
3. ***Annie: Good to get information on user expectations on processing time and number of points that they want to cluster/think through the flow of where clustering fits...how often they want to generate cluster, what kind of visual aid to understand that a cluster is processing. Also thinking about hardware investments for this. We could make this faster if there really is a need.
4. Job queue would be important architecturally so we send a request to the queue, query for updates against the process and query for results once they are available→ get something written on what this looks like so Ona can look at for performance etc.

Two f/u questions on specs

1. Minimum number of points per cluster?
1. Every point would be put into a cluster, even a cluster of 1. BUT if you want to exclude clusters based on a minimum, that is possible
2. Second round of clustering possible where you merge small clusters?

DiSARM M&E in Namibia and Botswana

1. DisARM team starting evaluation of tool in Namibia and Botswana. Evaluating
1. User satisfaction of the tool, issues with interface, which pieces most useful
2. Feedback on training of tool
3. Comparison between DisARM and paper-based systems - how disarm has improved, accuracy, completeness, saved time.
1. Only paper based compared to disarm (district level)
2. Also looking at how one person might be doing both paper and disarm (individual level) - does disarm minimize errors?
4. Collecting data in March (1-2 months). Info to share!
1. AOB
1. VW - Oslo meeting last week

Great and productive

Reviewed each user story (priorities, potential ambiguity)

1. Many modified to clarify functionality

Few big buckets of work discussed in detail: task management portion of DHIS2, usage analytics, etc

Going to go through same process with CHAI for user stories with Reveal (Pierre and Annie to do tomorrow)

1. Maybe we should split Reveal user stories into Android and Web/Core
1. Mostly splitting between the two? Or not? → some were split but many were already separated into one or the other (in UiO this makes sense because there are many different product groups and understanding backend need for user story to see what is actually achievable from a timing perspective)

Rescoping and descoping based on case notification and investigation → likely many involve Reveal tool

1. Roadmap Check-in

Alignment of R2 functional roadmap and Roadmap user stories

1. Annie, Pierre, Craig to discuss

12 February 2019

Agenda

1. Review of Previous Week’s Action Items
1. Action:  Bid on reveal.io → waiting to hear back by Feb 23
2. Action: Akros to share Narrative, Configuration Document, Marvel mock-ups by end of week

Done

1. Action: Akros team to get information on user expectations on clustering algorithm

In progress

1. Team Updates
1. Akros

Mocked up ento forms

1. Forms needed for FI
   
   

• Still waiting on hearing back from Dr. Prayuth. Pedro is looking at the data model to see if we can get any more specific.
• How much of a delay will not having the forms have? We will have placeholders in for now; we could release un-updated forms and then do another dot release with more specific forms. The indicator reporting is going to be the biggest thing that is slowed down, DHIS2 integration (not relevant)
• Reveal release 2 might have a few release - a “big” one with the client view and then a staggered release into April
• Integration budget approved
• Workplanning session two weeks back → likely these timelines will shift since we are still waiting on Thailand, would be good to pin down dates for first visit
• March visit for CHAI team to touch base and confirm timelines
• Visit after that will be larger team

Field testing was delayed one week - will share documents first thing next week

Desk testing updates - now on Rv1.3

Demo video in progress

1. Demo walk through for Bots/Namibia context
1. Is goal of demo to sell either country on Reveal?
1. Screen by screen walk through (video?)
2. plus documentation to walk through, catered to their forms
3. Access to test demo test instance
2. High level demo  useful for other countries
3. What is the difference between Botswana and Zambia forms
1. Unit of capture
2. Data fields
4. It is fine to demo just with the demo fields updated
5. To do: Annie to cross compare fields for Namibia and Botswana
6. Would want to make decisions in Q1 to pilot in Q2 - would be best to do this before the data review meeting in early March. Prioritize Namibia. Botswana timing will fall around DisARM M&E timelines which are tbd.

User Story review

1. Annie and Pierre reviewing this week
2. Pierre documenting notes/justifications in test cases -> How would we like this presented to all?
1. Pierre to set up slide deck with slide per user story with thoughts/notes/motivations for any changes
2. Changes - descoping or editing language
3. ONce we come to consensus, move to roadmap as source of truth

Subcontracts sent

1. Ona

Rv2 scoping update

1. Scoping is expected to be completed by Friday this week.
2. Roger and Craig have clarified mock-ups that were shared.
3. Finalizing forms this week
1. FI screens mostly done, need to define flow → how do users get in and out of family module?

Development

1. Reveal Web UI is actively under development
1. GitHub repository is now out → project on ona
2. Supported and released Reveal v1.3 - Sync based bug fixes (to do: share apk)
1. Also configuring new operational areas for testing
3. Working on integrating family module this week
1. Adding head of family, adding members to family, button to collect form against family member (form itself still in works)
2. Archive individual or archive family
4. Working on adding different location types to the map
1. Residential structures, larval breeding sites (point, but polygon possible), mosquito collection point, temporary location (community meeting point)
2. What about temporary sleeping location (e.g., that could be linked with a permanent residence)? Could be necessary in the future, would have to add icon, entity, add to maps. May be down the line.
5. GeoWidget:
1. Scope defined for next release
2. Drawing arrows between index cases
1. Core GW requirement → Reveal queries database to return location ids in date time order and then passes to GW, then GW draws arrows
3. Drawing radius around my location at varying zoom levels
1. As user zooms in, the 75m radius is zoomed at the scale/zoom level

User story alignment for Rv2

1. No major updates here
1. UCSF

API update from Hugh - will check in next week

Finalizing M&E protocols with CHAI, Sameen getting in-country feedback, orienting NMCPs to protocols. End of April/May results.

1. Action: Evaluation questions - Ali to share protocol.

Annie to loop in Ali into contract conversations

1. AOB
1. RVLv1 Sign-off

Run through all user stories with CHAI → two that are outstanding

1. Action: List of error messages needs to be sent to VW/CHAI
2. Demoing the sync up to mSpray dashboards, Pierre ran through this today with Kelvin and running through with Anne tomorrow.
1. Great job team!

19 February 2019

Agenda

1. Review of Previous Week’s Action Items
1. Action:  Bid on reveal.io → not an option

Revealprecision.com

Porting to that site by end of week. Will share for feedback

1. Action: Akros team to get information on user expectations on clustering algorithm

In progress - Derek P. has reached out to ministry stakeholders

1. Useful to understand which of those requirements are critical versus nice to have, ie which would prevent the user from using the algorithm versus nice to have.
1. Stratify need
1. Demo,

To do: Annie to cross compare fields for Namibia and Botswana

1. This is done. Need to define next steps
1. Craig - these are in the data dictionary now - can you take a look and see what the effort would be to pull this into an apk.
1. What are we trying to sell? Is the Android piece enough (data collection forms)? Or do we need to take this into the dashboards for the demo.
2. Sameen - we don’t need to prioritize the dashboard. Android components so that could be user tested, fill out the form and see an operational area that is similar to their expectations. Each village has a targeted denominator.

• From an imagery perspective - for demo Zambia imagery is fine.

• Contextualization of tool, renaming of areas, so they can see it aligns with workflow.

1. To do: Sameen to send hierarchy.
1. Immediate needs for demo:
1. Update android client data fields (form)
2. Renaming of Zambia operational area to familiar village names
1. Anything else needed for demo prep? No.
2. Fixed denominator will be required for Namibia. What kind of timelines do we need to take into account for customizations
3. We need to get a sense of what configuration timelines are

• To do: Akros to get sense of what additional customization would be needed for DiSARM and getting that to Ona

1. Country would want tool ready for internal testing in June/July
2. Sameen working on timelines to get decisions by end of April.
3. Will need to be a discussion if we select both countries
4. What needs to be done for DiSARM this year? To what extent will countries be using the app?
1. Should also know in April.

Akros walkthrough document

Akros video

1. Both of these are the generic demos at this point
1. Supported and released Reveal v1.3 - Sync based bug fixes (to do: share apk)

Done

1. Action: Disarm Evaluation questions - Ali to share protocol.

Done

1. Rv1 signoff

Action: List of error messages needs to be sent to VW/CHAI

1. Craig working on template to give to Sam to explain.

Action: Demoing the sync up to mSpray dashboards, Pierre ran through this today with Kelvin and running through with Anne tomorrow.

1. Found a bug in geoJSON. Kelvin identified this and a nifi fix that will be fixed tomorrow
1. Team Updates
1. Akros

Mocked up forms

1. As far as they can get for now, will be modifications once have full feedback from Thai team

FI level setting

1. Need for three years historical data?
2. Out of scope ETL for past three years of data

User Story update

1. We would like to present proposed user story changes to VW and CHAI
2. This will likely take 2 two-hour sessions
3. To do: First can send a spreadsheet and document for review
1. Will share by end of week

1. DiSARM

Waiting to confirm the scope of work, neat initial work on algorithm and UI side

• To do: Akros to respond to SOW clarifications.

1. Ona

Still working on scoping the Android client

The data dictionary is nearly complete with follow-on task actions and forms defined. When we add a location or register a location, we auto-generate tasks based on the campaign type that’s selected.

The family module is integrated internally and we are working on modifying it to fit the new mock-ups.

Working on Add Location form right now

Need help with:

1. Focus Investigation reporting that will need to be in the Web UI
1. What new objects are needed. Some summary data, how its stored/accessed/edited → need to start these conversations now.
2. To do: Derek to share mockup with CHAI side. Anne to solicit feedback
2. Craig will send the Android client mock-ups over the next couple days to Akros with a walk-through. We will need the review process
3. Craig wants to flag the size of this scope and identify that we will need a number of releases with an MVP delivered by the end of March and a number of features in a dot release
1. AOB
1. 8:30: Integration conversation

General Info

1. Get access to a staging environment of DHIS2 for the country
2. (possibly) share any high resolution imagery with DHIS2
3. Need to align the org unit hierarchy with Reveal
4. Need to export the GIS info from DHIS2 and import it into Reveal
5. DHIS2 build
1. Possibly add a different GeoLevel to capture operational area below the current lowest version
2. Forms need to be created
3. Tracked Entity Instances need to be setup to track locations within an operational area
4. Operational areas need to be defined
5. Families, relationships and family members need to be created as tracked entity instances
6. Relationships need to be made available between the location and family TEIs
6. Data Mapping
1. Ensure that the org unit hierarchy aligns
2. Map the field values from the form to

Namibia

1. API build - who doing from DHIS2 side
2. DHIS2 build
3. Data mapping

Botswana

1. API build - who doing from DHIS2 side
2. DHIS2 build
3. Data mapping

26 February 2019

Agenda

1. Review of Previous Week’s Action Items
1. Demo, Craig to estimate when this can be done based on conversations last week

Immediate needs for demo:

1. Update android client data fields (form)
2. Renaming of Zambia operational area to familiar village names

Team has scheduled in over next two weeks to share by the 8th of March

Anne to confirm with Sameen over next week. CHAI team happy to handle demos for now

1. To do: Akros to get sense of what additional customization would be needed for DiSARM training documentation and getting that to Ona.

Derek P to have this to share at end of next week (March 8)

1. Rv1 signoff

Action: List of error messages needs to be sent to VW/CHAI

1. Delivered today

Action: Kelvin identified bug in JSON and a nifi fix for syncing to work

1. This is fixed now.
1. To do: User story scoping - Annie and Pierre to send a spreadsheet and document for review to Anne DONE
2. To do: Akros to respond to SOW clarifications to DisARM

Done

• To do: Ona to respond to contract

1. To do: Derek P to share FI dashboard mockup with CHAI side. Anne to solicit feedback

Annie to share with DiSARM → done

Input by next week’s call

1. Team Updates
1. Akros

Walkthrough documentation

1. apk v1.4 Username: DSMECOP, Password: Amani123
2. What is the process - VW has a feedback form for capturing issues
1. Akros webpage will have a contact email for an issues with installation
2. We probably need a support channel that is responsive - there is a risk around making this so public..maybe we have a contact line that is a better sales pipeline
3. To do: Annie to circle back on this before putting it live
4. To do: Google Issue Report Form - to discuss when this should be implemented

Focus Investigation Dashboards - feedback needed by this call next week

To do: Imagery update - better update to come by end of next week (March 8)

Testing feedback/final release outputs

1. A final tested and edited release x version
2. An up to date bug tracker with all relevant issues addressed (internal)
3. A post testing edited script for our grant partners to follow
4. An updated 'new user stories' document

Annie on leave March 2 - 16

1. Fully offline first week
2. Partially online second week
3. Anna to back-up and manage while Annie is out
1. DiSARM

Feedback on algorithms discussions

1. Contracts being received by UCSF grants team
2. Looking at ways to structure and document API
3. Derek reached out to people on algorithms

Update on Reveal Seattle trip

1. Concept note ongoing
2. Will circle back to VW to get feedback at a later stage
3. Craig lives in Seattle!

ASTMH

1. To do: Anna to submit symposium tomorrow

1. Ona

Scoping:

1. Final day of UI mock-ups on Android client
2. Data dictionary is set
3. Working on the data model for Focus Investigations and the relationship between Intervention and sub-interventions (FI vs. Campaign vs. Case)
4. Received the FI reporting scope today and are iterating on it

Dev:

1. Finalizing Family Module
2. Updating Circle
3. Reveal 1.4 release and providing data support

Demo Prep:

1. Namibia and Botswana APKs and Operational areas are scheduled - Target delivery is Friday March 8th
2. Cambodia CGR - On our radar, but haven’t yet assigned the team members. Target is to deliver by end of March (29th)
1. Server side OpenSRP and CGR with Nifi integration
2. Stretch goal is if new point is created in Reveal that it would queue to be added to CGR
3. This is a POC integration
4. Cambodia is focus for CGR right now, opportunity to discuss using tools like Reveal as way to interact with CGR.

Questions:

1. Marvel updates? When will client-side Rv2 mock-ups be ready to share?
1. Target is end of Day Thursday
2. Release 2 dot releases - can we schedule these out?
1. Yes, it’s on our to-do list, but has been deprioritized so we could get the developers unblocked on a number of things.
2. Target to have this would be mid-week next week.
1. AOB
1. Rescoping of user stories for Reveal

Want to put some time on the calendar