15 January 2019

Agenda

1. Review of Previous Week’s Action Items
1. Action: Laurie to link Derek w/ Craig w/ Answers from Slack re: DG imagery.

• Ona has access to imagery in Zambia for demo

1. Derek sent to CHAI instructions on how to get imagery
2. Follow up questions on imagery from Arnaud:
1. Context: CHAI’s work with imagery has been around enumeration. Enumeration has been done in many DSME countries, through OSM, often by recruiting students. Gates has contracted DG to do remote enumeration; further projects to enumerate with DG and HOT OSM projects. Outcome of work is household enumeration. That is how Gates has DG access.
2. Why does Reveal require access to satellite imagery?
3. What do we say to Gates about access to DG.
4. If we have HH enumeration shape file, will the image used for this help with navigation, even if it is 2017 imagery? Is it better to have new imagery with old enumeration? Or the same enumeration file layered on top of the old imagery?
5. Anna says that DG says that when we know which countries the pilot is happening in and Gates also knows, so DG ensures that enumeration and imagery is made available.
6. Follow up: Arnaud to ask about this, does Gates have access to imagery, can we have access to any type of imagery.
7. Would PMI be willing to extend their license to CHAI in countries where they are? CHAI has just started discussions with PMI in some countries.

1. Team Updates
1. Akros

Contract - Modifications from CHAI responded to, added IP similar to geowidget; returned to CHAI last week

1. Ona

No major updates since last week

Sam started on Reveal v1.1, working with Pierre to close out test cases

1. Timeline for the end of the week on this
1. UCSF

Confirm - Hugh is writing up scope for algorithms

• Follow up: Ali to follow up and confirm if Hugh can get by end of week

No major updates

1. AOB
1. Reminders

Reimbursements for trip

• Follow up: Annie to send reimbursement form to all

Reports

• Follow up: send quarterly reports to Annie by Thursday please. Annie to double check what was sent.

1. Thailand Timing

Integration - update from Ona? Matt had said last Friday. Follow up : need to pin down the integration number/cost.

Budget - CHAI to review and respond later today/tomorrow

Discussions with Dr. Prayuth: Inessa is letting him know that the budget is coming, what he needs to budget from GF, confirm we still have the green light. Have asked him to pin down 2 provinces for pilot, haven’t heard back but it is a top priority.

Enumeration - HOT mapping reached out to offer services probono IF we can pin down the provinces ASAP.

Activities in Feb-March

1. Enumeration in Feb (HOT or Akros+CHAI) plus digitization of maps (foci)
2. Data Import* is dependent on the tool being ready
3. Action item: once we have info from Dr. Prayuth, Annie to work with Chris and Pedro to try to finalize workplan and in country visit timing

Reveal release 2

1. How can we keep Thailand engaged with the application through the end of March?
1. Mockups will come in before end of month and we can include Thailand on this → make sure these reflect the discovery process from Thailand
2. Team is reviewing and determining what is MVP, then we will know what is in scope. Focus will be more of the android client than the web UI. Could potentially test a beta version with them in March?
1. Action item: we (Annie and Craig) need to discuss scope for version 2. Will pull in Pedro and Chris as well. After these decisions are made, let’s write a narrative for what is expected in March.
2. One risk is Dr. Prayuth’s expectations for the first version.

• Action item: End of next week, deliver narrative for version 2.

1. Need to make sure we are including what Thailand wants but also that we include user stories → this is a balance, but prioritizing Thailand.
1. Foci areas in Thailand- how defined are they?
1. Could initial step be to work with country team to define these more clearly?
2. Getting the country team engaged in visualization of data
1. CHAI: Panama OpenSRP questions

(early) Interest from Panama in using Reveal. Panama is not a grant country. Interested in Reveal for response work. Contracted in country dev company to build out case notification tool/app. Should we encourage them to build with OpenSRP in case they choose Reveal down the line?

Experience with 3rd party developers building on OpenSRP? → A few have done this; some contribute back to code, some don’t. Regular community dev calls weekly and slack channels. Ona is technical partner for OpenSRP, scientific partners are Harvard and WHO. When a company goes off on their own for 2+ years, they may develop in a may that is misaligned with Ona code base and thus is costly to realign.

1. **Recommendation is to work together from the beginning. Have them join and contribute to community

Reveal has thought about including case notification and other case surveillance pieces. Reveal is rolling out RACD in Lusaka this year and other case surveillance. May be a chance to bring in USAID PMI funds to help fund the build for that side of the tool to be used. Q1 2019 this should be happening. Anna will keep DSME updated to this conversation once it gets going.

Panama timelines are ASAP and they have committed to in-house group.

What we are seeing in GMS, is countries are early stage thinking about mobile tools, which could be a chance for Reveal

Could RACD app be used for case notification? → tbd on if technically this would be possible

Anne to keep us all posted.

1. Q1 Implementation - covered above in Thailand and R2 scoping conversations.
2. Branding - Logo Fully Finalized

On the app, using as we talk about Reveal. Not technically billed to DSME since it is bigger than just this mechanism, but of course is relevant to tool. Anne to let us know if you’d like access to logos/colour swaps/etc.

1. Marketing & BD

Product Site

Demo/Pitch Deck

1. What is in place to demo Reveal?
2. Working IRS Demo app – make public working demo consisting of
1. Android App to download
2. Corresponding linked dashboard (with dummy data pruned down to a few spray area).
3. Video walk through/Screencast?
3. What is the LOE involved in the above?
1. App is available
2. Need independent dashboard with dummy data, have spoken about having an additional server running which has associated costs
3. Video walk through -

• Follow up: Akros and Ona team to discuss this week

Relationship Building (much in relationship to mSpray but will incorporate and discuss reveal)

1. End January: RollBack Malaria/WHO Vector Control Working Group Presentation
2. April: Seattle visit Ona & Akros
1. Pull in others to this meeting? Meeting could be broader than malaria to discuss other use cases. NTDs.

• Follow up: Akros to put together list of names and potential agenda points or line items of discussion and potential dates

1. Follow up: Anne to discuss with Arnaud and see if it lines up with timing of other meetings with Gates. Time with John Cox even within malaria, to help move along Moz will help
2. UCSF also to be involved - similar discussion in CT
1. Engaging APMEN, Insecticide companies, PEPFAR, NTDs
1. Dates for delivery of mocked-up dashboards from Akros to Ona?

To discuss between Akros - Ona later this week.

1. URL discussion: below are the options that we have reserved/purchased already. Can we decide on one today? Next step/Action:  Akros to port Reveal landing page to url for feedback from consortium.

Revealsystem.com

Revealprecision.com

Revealspatialintelligence

Revealtool.com

Revealsi.com

Revealredefiningprecision.com

Reveal.io

1. If anyone has a strong feeling one way or another, make comments here

22 January 2019

Agenda

1. Review of Previous Week’s Action Items
1. Follow up: Arnaud to ask about this, does Gates have access to imagery, can we have access to any type of imagery? Update on conversation with Gates.

Annie and Derek P to discuss alternative imagery options

1. Follow up: Ali to follow up and confirm if Hugh can proposal for algorithms discussed at meeting by end of last week (Jan 18)

Delivered. Thanks

1. Follow up: Annie to send reimbursement form to all

Done

1. Follow up: Send quarterly reports to Annie by Thursday please. Annie to double check what was sent.

Annie resent template

Done, thanks!

1. Follow up : Craig/Matt need to pin down the integration number/cost and get to Anne

Done, need to discuss.

1. Action item: once we have info from Dr. Prayuth, Annie to work with Chris and Pedro to try to finalize workplan and in-country visit timing

Workplanning meeting set for next week

1. Action item: we (Annie and Craig) need to discuss scope for version 2. Will pull in Pedro and Chris as well. After these decisions are made, let’s write a narrative for what is expected in March.

This will happen at the end of next week.

1. Action item: End of month, deliver narrative for version 2.
2. Follow up: Akros and Ona team to discuss LOE involved in setting up demo

Annie and Craig to discuss this week

• Follow up: Akros to put together list of names and potential agenda points or line items of discussion and potential dates

Anna/Hugh/Matt have started this conversation - aiming for potential April visit

1. Follow up: Anna to discuss with Arnaud and see if it lines up with timing of other meetings with Gates. Time with John Cox even within malaria, to help move along Moz will help

Will do once have a firmer date, for now, month of April is looking like a possibility

1. Action:  Once URL decided, Akros to port Reveal landing page to url for feedback from consortium.

Bid on reveal.io → waiting to hear back

1. Team Updates
1. Akros

Thailand workplanning

Field testing next week - Documents coming to Craig tomorrow with return due on Wednesday next week.

Contracts still tbd.

1. Ona

Progress over last week

1. Post intervention; developers working on developing Reveal 1.1 tickets. Waiting on few pieces of info before we send the tickets over to QA
1. Follow up: Branding question for Anna and Matt to discuss: need final version of text to go at bottom of hamburger menu
2. Follow up: Use case tests - Craig is working on this and will get over to VW end of Wednesday (Importing locations and coordinates)
3. Roger is working on scoping out what is needed for web, client integrations with DHIS2. Craig is mapping what we learned in session re Thailand workflows, user stories, etc. What of this is MVP
1. Follow up: Still on track for this to be done by EOM for sharing with this group (Narrative)
2. **Let CHAI and VW known if there is anything needed from Oslo on DHIS2 integration - they will be there next week**
1. How and where we get case notifications
1. Could query API
2. Receive event if events can be forwarded to web service
2. Indicators and calculations for datasets. What reports for IRS FI do we need to support into DHIS2. Need to develop indicators in Canopy to be able to push them into DHIS2.
1. Best to send through data elements raw if they match up so that DHIS2 can use their own denominators
3. Is it worth setting up a test instance with DHIS2 when we don’t know the actual indicators from Bots and Namibia
4. Question is which country we want to be our meta-data?
1. WHO data elements - for demo
2. We have been trying to get access to country-specific DHIS2 instances. Anne to Follow up: re the indicators Botswana and Namibia are using
3. What about the data dictionary workstream? We aren’t quite there yet, but could get it going quickly.
4. Follow up: Annie to share Thailand forms with Pierre
5. FI integration with DHIS2 is less of a priority that IRS
6. Use Thailand’s forms for now to define data dictionary for FI
7. Sameen bringing Botswana and Namibia data fields for IRS
3. Integration with DHIS2 is non-negotiable for Botswana and Namibia (these are the likely IRS pilot countries)
4. Craig will be in DC Monday and Tuesday of next week and missing meeting
5. BIOPHICS is a separate budget/workstream
1. UCSF

Update

Discuss algorithm specs

LOE for integrating DISaRM UI into Reveal?

1. CA: THis will be done - working of tech solution with Connor and Roger.
2. Algorithm - generate operational area from a submitted shape file

Follow up: Craig to work with Connor to connect Jonathan, Annie to share code info

1. AOB
1. Roadmap Check-in

Testing of R1

1. Craig gave update

3 new requirements (Roadmap link)

1. No new requirements relevant to Reveal today
2. We haven’t reviewed any

Alignment of R2 functional roadmap and Roadmap user stories

1. Pierre’s input could be helpful to figure out which user stories could be incorporated to R2
2. Would be helpful to know about what bandwidth there is which/if there are user stories that don’t obviously fit into the release but could be easy wins or easier wins with a bit of extra work
3. Would be helpful for Pierre to have a sense of how scoping is looking before final narrative is produced

29 January 2019

Agenda

1. Review of Previous Week’s Action Items
1. Action item: we (Annie and Craig) need to discuss scope for version 2. End of month, deliver narrative for version 2.
2. Follow up: Akros and Ona team to discuss LOE involved in setting up demo

This is on the Akros side, once Ona has uploaded test data for mSpray areas, Akros can make the video

1. Action:  Bid on reveal.io → waiting to hear back
2. Follow up: Branding question for Anna and Matt to discuss: need final version of text to go at bottom of hamburger menu

This is done

1. Follow up: Use case tests - Craig is working on this and will get over to VW end of Wednesday (Importing locations and coordinates)
2. Follow up: CHAI to send the indicators Botswana and Namibia are using
3. Follow up: Annie to share Thailand forms with Pierre

Done ***Have added a “Pilot” folder to team gdrive

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

Added to Reveal data dictionary for RACD workflow. Few outstanding questions for Thai team

Also waiting on Ento and VC forms from Thai team

Demo set up steps

1. Ona
2. UCSF
1. AOB
1. Roadmap Check-in

Testing of R1

3 new requirements (Roadmap link)

Alignment of R2 functional roadmap and Roadmap user stories