June 4 2019

Agenda

1. Follow ups from last week
1. MapBox username and password: Can we create a username/password for Thailand? To track data and number of tiles needed in average pilot
• To do: Annie to discuss with Pedro while in country who this should be.
1. Waiting on this person to be assigned
2. To do: Annie to understand total square area after focus mapping is complete (likely this will come mid next week)
• This is not done; working on this as we validate focus areas this week
3. To do: Matt to determine the work involved in making the GeoWidget tile-server-“point” a configurable field.
• Annie to follow up with Matt
4. To do: Annie to follow up with Matt and Ona team around decision on Namibia dates.
• We are okay to move forward
• Annie to be point person for now
• To do: Kickoff call to be scheduled
• Roles
1. CHAI - on the ground support
2. Akros - coordinating Ona, form changes
5. To do: Sameen to send some questions on mop up workflow; in the meantime will start collecting materials (Botswana)
• Sameen and Derek have ongoing conversation on this
2. House-keeping
1. Gates meeting
• Sept 23 - 24
• Confirm blackout dates
1. UCSF: Sept 25 - 27
2. CHAI (Lakshmi):
3. Team Updates
1. Akros/Ona
• Development
1. R2 Progress and Needs
1. R2 v2.0.5 is linked in: Release Narrative
2. R2 v2.0.6 planned for June 14 to address Thai feedback
1. Scope of release is within Thai feedback document
2. *This is significant feedback that to address all, and address ongoing Thailand support, will take about 4-5 weeks of developer time
2. R3 Progress (Scoping)
1. No further scoping done since two weeks given sprints for Thailand
2. Rework of IRS Planning and FI planning timelines (originally end of June)
1. Likely not much wiggle room for IRS planning release
3. Discuss timelines given Thai implementation needs
3. R4 Progress (Scoping)
1. No update
• Thailand
1. Implementation updates to be discussed tomorrow. In short:
1. Enumeration, Foci Mapping, and User testing over the last two weeks with good and extensive feedback
2. Integration work this week - sounds like it is going well and productively, with detailed update tomorrow
3. 6/17 TOT
4. July Pilot
2. Risks between now and TOT
1. Enumeration finishing
2. Imagery quality
3. Finishing all fixes
4. Integration?
• Botswana
1. Visit last week:
1. Productive and Reveal was well received overall
2. Local server hosting
1. Botswana has 32GB RAM server, with 2 processors, already hosting DHIS2 instances.
2. Not enough space to host OpenSRP/Reveal - would need 2 more servers
3. Botswana IT team asked CHAI to procure - Erica was following up with CHAI internally on this
1. Fyi, server cost with import duty is likely $15-20k per server
2. Trying to figure out how CHAI can support this under DSME country budgets

• To do:  Annie to determine what the deadline is for server configuration/setup

1. Way forward. Potential options:
1. Start with server procurement (this can take 6 weeks -  months) and support implementation starting in late 2019, early 2020
2. Negotiate for cloud hosting of pilot
3. Last resort: hosting could be cloud
• Namibia
1. Role definitions - let’s talk through this on a kickoff call, include DiSARM team
1. Need to close the loop with the communications around the change from DiSARM to Reveal or DiSARM to paper in areas so that

• To do: Annie to set up

1. Akros
2. CHAI
1. UCSF
• Likely will want to use these algorithms, especially the clustering algorithm in these implementations.
• If headless versions are not linked to Reveal, ideally use UI - large datasets won’t render
• At this point in time, algorithms are back up and running
1. No need at this time to update documentation around this
2. Tbd if there are more documentation updates needed when we get more feedback from Ona
• UI updates
1. Hugh is updating the UI to include a way to better test with dummy/demo data
• Contract is being sent back to UCSF tomorrow
• To do: Ali to circle back on getting permission to share the M&E reports on DiSARM in Namibia and Bostwana
2. AOB
• None
  
  

June 11 2019

Agenda

1. Follow ups from last week
1. To do: Annie to understand total square area after focus mapping is complete (likely this will come mid next week)
• This is not done; as we have not yet been able to assess that all focus areas are mapped
2. To do: Matt to determine the work involved in making the GeoWidget tile-server-“point” a configurable field.
• No updates on this
3. To do: Namibia kickoff call to be scheduled
• Happened today - will discuss below
4. To do:  Annie to determine what the deadline is for server configuration/setup for Botswana
• End of July - will discuss further below
2. House-keeping
1. Gates meeting
• Sept 23 -24
3. Team Updates
1. Akros/Ona
• Development
1. R2 Progress and Needs
1. June 14 release: Thai feedback document
2. Change to what will be in on Friday
1. Index case confirmation workflow
1. Pre-pilot - won’t be done on Friday
2. Color Coding Hierarchy for the tasks in the mobile client
1. Have different colors display based on business logic
2. Pedro is reviewing this and it’s an ongoing conversation. We will schedule this once the scoping is complete.
3. This was confusing to the Thai team because it turned the structure green
3. Will discuss in detail tomorrow on the Thailand call
2. R3 Progress (Scoping)
1. Rework of IRS Planning and FI planning timelines and IRS feature timelines with Thailand work adding to workload
1. To do: Matt to share timing update
2. To do: Question:
1. Will this affect the Botswana timelines?
2. To focus on Thailand, we cannot scope R3 MDA and ITNs and additional user stories until ……..
3. R4 Progress (Scoping)
1. No update
• Thailand
1. Implementation updates to be discussed tomorrow. TOT next week
• Botswana
1. Visit two weeks ago:
1. Reviewed workplan and conducted validation exercises with NMP, CHAI and HI team.

• To do: Akros to confirm if room in budget for enumeration

1. Server challenge - the current servers do not support the OpenSRP Stack: they do not have cloud servers, they have machines stored locally in the IT office.
1. Current server is a DHIS2 server. Were hoping to put Reveal on server and run it, but this would slow down DHIS2 which the IT team wanted to avoid this at all costs
2. Procurement - 2 servers (1 for transactional, 1 for reporting).

• To do: share server specs and cost estimate

1. If we move forward with server
1. 1 week in country Ona and tier 2 support in follow-up
2. 1 FTE on country side to maintain
1. Server needs to be in-country by end of June to get it set up in time for implementation (if we do training in August). Local hosting in this timeframe is challenging.
2. Options
1. Start the server purchase process to potentially use Reveal for something other than IRS (RACD) given the timelines associated with procurement and intensive set up. If the timelines draw out past the end of this contract, we'd either a) need to find additional funds to support or b) CHAI would pick up the implementation piece. The latter is not ideal but could be the reality if we go this way and no other funding comes in.
2. Push the country to pilot on a cloud (politically sensitive but maybe tenable if they realise local not possible?). Start server procurement process regardless, with the expectation that post pilot we would host locally.
3. Working assumption is that we will do testing and training on the cloud and then move forward with the server if we get it. Botswana team to confirm if end of August is a workable timeline.
4. To do: Annie to confirm timelines with Matt and Derek for IRS Planning and Botswana planning timelines

• Namibia
1. Call earlier today to kickoff - notes
2. Scope is: 3 village clusters in Oshana
1. CHAI is pushing back on any major changes, but there may be some minor question changes (additions / removal)

• To do: Annie to add UCSF team to Namibia calls

• UCSF
• Updates
1. Preliminary summary for M&E Namibia and Botswana results that has been approved → CHAI team is confirming this is consistent with what they heard.
1. To do: Ali to share what has been compiled today
• Reveal implementation plan (part of Stage-gate deliverables)
1. Was originally focused on DiSARM implementation but this has shifted. Now we want to instead focus the document on the use of the algorithms in the Reveal Consortium
• Algorithm updates
1. UIs can now be run with dummy data that automatically gets added
2. Is now easier to run the headless APIs via the call request
• UCSF contract team follow-up
• AOB
• Superset data
1. There needs to be an ETL process to get the other data into the warehouse as well. To do: We need to scope how the data will get through the ETL process and into supersets (Akros and Ona).
• “Reference Application” for Reveal
1. Developing a generic version of FI application - something to keep in mind for demoing purposes.  We want to have a version of the application that is shareable and we want to have a version of the application that could be WHO-approved.
• To Do:
• Rework of IRS Planning and FI planning timelines and IRS feature timelines with Thailand work adding to workload
1. Matt to share timing update
2. Question:
1. Will this affect the Botswana timelines?
• Matt to determine the work involved in making the GeoWidget tile-server-“point” a configurable field.
1. Intention:
1. Have a different imagery server serve tiles
2. We will not get rid of the mapbox license
• Send a recommended server specification
1. Include a cost estimate
• Annie to add UCSF team to Namibia calls
• We need to scope how the data will get through the ETL process and into supersets (Akros and Ona).

June 19 2019

Agenda

1. Follow ups from last week
1. To do: Annie to understand total square area after focus mapping is complete (likely this will come mid next week)
• This is not done; as we have not yet been able to assess that all focus areas are mapped

• To do: We need to switch the API key over to the Thailand account; currently we are using the Ona API key. Craig is creating ticket

• To do:  We are also using the tiles pulled from DG imagery in Trat to estimate the costs of pulling tiles

1. To do: Can we look at the web tile mosaic service to look at the imagery available in that service. Akros to do.
1. Coverage and quality of imagery needs to be compared (Web tile service is difference and generally of lower quality than the high res tiles that DG has pulled for us)
1. To do: Matt to determine the work involved in making the GeoWidget tile-server-“point” a configurable field. (Intention is to point to another tile server, not necessarily getting rid of MapBox)
• We researched this and found that we just need to add a line to the Mapbox Style in the host application and there is no action in the GeoWidget.
• We are testing this in the Reveal host application with the Digital Globe product. (example)
• PD: Is it possible to toggle between the different base layers? Toggling is a part of the geowidget spec that has been delivered. CA: Host application needs to say which server.
1. To Do: Akros and Ona to discuss later - option to toggle on both the web and client side between multiple layers. Also that we may want to toggle between the layers within one service. May want to set the basemap at the site level.

• To do: Annie to provide timing updates on planning module timing and Namibia and Botswana planning need timelines

• To discuss when we reach that section of the agenda
1. To do: Akros to confirm if room in budget for enumeration for Botswana
• To discuss this tomorrow
2. To do: Send Bostwana server specs and cost estimate
• To discuss this tomorrow
3. To do: We need to scope how the data will get through the ETL process and into Superset (Akros and Ona).
• Annie to loop Pierre into those conversations
• Implications in what it means to put in “all of the data”
• Handling health data versus data for analytics → need to have this conversation

• To do: Annie to schedule this conversation

1. VA: What info do we need from the Thai/Biophics teams to inform these conversations?
2. Current state
1. Data submitted from web automatically gets to the OpenSRP database. Right now this pushes to the maps and Reveal dashboards.
2. To Confirm: Which data are pushed through to the warehouse - is form data pushed through and accessible via Superset?
3. The WebUI and Superset data comes from the data warehouse

• To do: Add UCSF team to Namibia calls

• done
1. House-keeping
1. Team Updates
1. Akros/Ona
• High level timelines
• Development
1. R3 Progress
1. IRS Planning (end of July) and FI planning (mid August timelines and IRS feature timelines
1. How should we adjust these
1. CHAI to let Annie
2. MDA and ITN scoping
1. Propose to pick this up in August
2. R4 Progress (Scoping)
1. Propose to start this up in August
1. August scoping meeting
1. Who needs to be there and where
2. Annie to start planning
3. R2 Progress and Needs
1. 2.0.8 and 2.0.9 releases
2. Pre July 1 release (tentative aims):
1. Index registration workflow*
2. Colors for tasks*
3. Automation of plan(focus investigation)*
4. Marking structures as ineligible*
5. Editing tasks: net distribution data, ento data, other tasks*
6. Deleting family members
7. Deleting/Resetting tasks to not be done: net distribution data, ento data, other tasks
3. Planning
1. MB: Ona can set up a website very quickly to allow for planning to be done easily
2. Separate team working on Planning. Current team working on the WebUi will be switched to work on FI planning
3. Little bit more than a month to get the planning finished
4. Ona can provide what they would need to load in the plans - this is what Ona is doing now and they have a good data model for this. Underlying architecture is all there
5. Team assignment is new, but plan model is there
6. If there are 12 districts it will be manageable to help them do the planning
7. MB: Team Assignment will happen only a week or so before implementation ‘which device goes to which area’ which data downloaded to app. Vivek to check with country teams when this needs to be done.
8. FI Planning - Thai team would like to see thi
1. SHould this be prioritised? : AL - want to hear from team in Thailand. Prayuth really wants to see this, and to see data coming through to the warehouse. Some frustration that this is not available. AM: agree that planning is a high priority VA: Data warehouse integration is high priority, FI Planning - not sure how extreme the requirement is for Prayuth. Team will find out this week and report back AL: if Prayuth wants to prioritise FI planning then it may make sense to reshuffle. Any other frustrations? VA: Last day of training cancelled as team needed to work on translations and sessions were not critical. If IRS and FI planning switched would FI be ready by the end of July? - Akros Ona to scope
2. How much flexibility will there be to deliver FI planning rather than IRS planning (as there is some common work done between the two) : MB - would prefer to continue with IRS but possible  to switch teams if the decision is made now
4. New product management tool - Confluence
1. Storage space for documentation and project notes
2. Ticketing through Jira
5. Reference Application
• Thailand
1. Botswana




• Namibia




• 
  




• Data warehouse - this is important
• Matt shared a link, Craig is moving this to the wiki.
• UCSF
• M&E preliminary summary shared. Key recommendations:
1. “Provide more in-depth, practical training for tool users.
2. “Increase collaboration between the national malaria programs, local implementing partner, and tool developers to ensure the digital tool used better reflects the paper-based data collection resources currently being used by the programs.
3. “Implement additional field testing of the DiSARM tool and relevant equipment prior to launch of IRS campaign to determine if issues are related to logistics (e.g. network connectivity), equipment (e.g. tablets and sim cards) or software glitches of the tool itself.
4. “Consider additional functional changes in future iterations of the DiSARM tool based on identified programmatic needs.
5. “Incorporate the DiSARM tool into the planning processes of more management levels (i.e. district, regional, and national) to improve internal alignment of the information communicated through the tool.”
• Algorithm use questions
• Connect Jonathan w/ Ephraim re GPS points
• UCSF contract team follow-up
• AOB