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

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

5 March 2019

Agenda

1. Review of Previous Week’s Action Items
1. To do: Anne to confirm with Sameen any other needs for demo for Bots and Namib. - Form changes/Rename of Op areas discussed last week are sufficient. 20-30 d configuration a fair estimate.

Craig: (additional time for sat imagery/user acct setup/ servers needed, up 6 weeks, Craig had shared these time estimates with Annie previously).

1. To do: share client-side Rv2 mock-ups by Thursday Feb 28

Target is end of Day Thursday

Sent 1 Mar

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

Derek P to have this to share by March 8 (Anna to check with Derek P on this tomorrow)

1. To do: User story scheduling - Annie or Anna to confirm availability  Mar 14, 13:00 - 15:00 EST and Mar 15, 9:00 - 11:00 EST

Agreed to move ahead with meeting; Anna & Pierre will connect prior to scheduled calls to review slide deck.

1. To do: Contracts - Waiting on sub signatures. Craig will message Matt.
2. To do: Feedback by now on FI dashboards

Input by next week’s call

CHAI feedback: https://docs.google.com/document/d/13hu-Utl5_1xxeoxBNVl_WI-0S8ucpi_Ne5JXX0ZbBng/edit

1. To do: Annie to circle back on if we are making apk public or not. - Outcome: this will be linked to Revealprecision.com, Parysa is preparing an email address
2. To do: Imagery update - doc with options/recommendations to be finalized.
3. To do: Anna to submit ASTMH symposium by 27th Feb (DONE)
1. Team Updates
1. Akros

Christina now in Lusaka, in field this week seeing mSpray/MDA campaign

Interest in Reveal for RCD in Zambia (Lusaka Prov)

Reveal website undergoing revisions, will share in next week / 2 weeks

DiSARM

contracts and grants department is still reviewing the subcontract. We’ll keep tracking it and let you know if they have any issues that require input.

No other major DiSARM updates from this past week.

CHAI. (CHAI-Anne): Travel plans for Thailand in discussion - dates still up in the air. Dr. Prayuth communicated yesterday with Pedro -- early march kick-off meeting will not work as Dr. Prayuth out of country. Week of March 25th may work for Pedro to meet with Prayuth regarding implementation dates and budgets. Still tentative.

1. No earlier than end of April may be most realistic for user testing etc.
2. Prayuth has given some indication that he’d like to see the ‘tool in action’ prior to further commitment.
1. Ona

Scoping:

1. Android client is complete
2. Had FI reporting scoping meeting with Derek last week. Roger, Conor and Kelvin are working on the UX and comparing how the feedback from Derek compares to what was originally created and sent by Roger a few weeks ago.
3. Working on the data model for Focus Investigations and the relationship between Intervention and sub-interventions (FI vs. Campaign vs. Case)

Dev:

1. Family Module integration is complete
2. Implementing the add point feature with multiple point types
3. Working on Namibia and Botswana IRS forms

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.
3. Needs: Sample org hierarchy from Namibia & Bots for Demo Prep. Anne L will check with Sameen and provide to Craig.

Questions:

1. Update - on track for March 8 Namib and Bots apks?
1. Yes. Planning for delivery on Friday
2. Release 2 dot releases - can we still expect schedule for this by mid week this week?
1. No,
2. Can update on Weds however (6 March) -
1. AOB
1. User Story Review Scheduling (Pierre) - Will maintain current dates, Anna & Pierre will connect.

12 March 2019

Agenda

1. Review of Previous Week’s Action Items
1. To do: Craig: (additional time for sat imagery/user acct setup/ servers needed, up 6 weeks, Craig had shared these time estimates with Annie previously).
• Craig will share directly with Anne Liu and Pierre Dane - for preparation for Pedro//readiness for Thailand
2. To do: share R2 dot release schedule
• R2 release is very large - breaking into individual releases
• 2.0: focuses on Android client with lite view in web UI. Tasks in map view, list view. Different interventions with different forms as defined in data dictionary. Various icons in map view. Family registration process available (allow user to register // register family). Allow track interventions at operational level and structural level. Interventions of focus: Larval, ITN distribution, case confirmation RCD.
• 2.1: Case confirmation from DHIS2 shifted to 2.1.
1. Must understand better of what DHIS2 or Thai’s system will provide for case confirmation.
• Further detailed schedule by COB today (Craig).
3. To do:  Akros to get sense of what additional customization needed for DiSARM training documentation and getting that to Ona.

• Derek P working on this now. Must complete by Friday for discussion with Craig. Derek will schedule with Craig to discuss.

1. To do: Review descoping suggestions with CHAI: scheduled for Thursday.
2. To do: Contracts - Waiting on sub signatures from UCSF
3. To do: Feedback by now on FI dashboards
• Dashboards: https://docs.google.com/document/d/13hu-Utl5_1xxeoxBNVl_WI-0S8ucpi_Ne5JXX0ZbBng/edit
• Web: Comments in Marvel
• App: By email. (will share here).
4. To do: Revealprecision.com, Parysa is preparing an email address. Akros ready to receive inputs on this website.
5. To do: Imagery update - doc with options/recommendations to be finalized. - complete by Christina, submitted to CHAI last week.
• Free imagery list

https://gisgeography.com/free-satellite-imagery-data-list/

1. Imagery summary: https://docs.google.com/document/d/1IVXKpfJ6ibnAmVCFbGC0256e-x-c7TtxE9apCoEGw_E/edit?usp=sharing

• Team Updates
1. Akros
1. Revealprecision.com ready for inputs
2. Akros ready to help  redefine some of the FI mockups based on chai’s input. Can do this throughout this week and into next
1. Ona

Scoping:

1. Finalizing the data model for plans this week
2. We will continue working with the web UI mock-ups
1. Feedback may have an impact on dev timeline

Dev:

1. Namibia and Botswana forms updated, tested and released
2. Working on task list by OA

Demo Prep:

1. Namibia and Botswana APKs and Operational areas are scheduled - Delivered to Akros on Monday
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.




1. Thailand
• Pedro meeting with Thailand in next week. Will provide mockups to Dr. Prayuth.
• Prayuth would like to see tool & walk through further. Pedro (March 28/29th with Dr. Prayuth) to walk through mockups on Android phone.
• Pedro will also discuss pilot areas - moving from 2 to 3 districts (likely). Still not defined which districts for pilot. Pedro will also discuss enumeration process with Prayuth to ensure he understands process, outcomes and benefits. (including that he will need to allow staff to provide enumeration support).
• Thai translation to also be discussed as well as general integration needs
• Pedro may be in contact with Craig to understand other input needed from Thailand.
• This will be a go//no-go decision from Prayuth at this meeting.
• Potential interest in collaborative publication
• Timeline challenging - User testing in May, first visit in May. Enumeration training in April (potentially). (Craig recommends pushing dev of Reveal out - get link from Anne for proposed timeline)
• Pedro’s Reveal slide deck for Prayuth in prep: Derek P will send comments to Pedro this week.
• Budget - CHAI discussing with Prayuth who would pay for Biophics integration with Reveal. This is still up in the air.





1. FI workflows / mock-up feedback
• Discussed above
• FI app comments from CHAI copied below with this meetings minutes embedded.
1. Key decision makers - what will they be using primarily? App or web UI?
2. Field staff do need historic information to drive field based intervention - hence they do need some historic field information
1. Determine exactly what information this is. Keep it as simple as possible. This is unclear to CHAI. Did Akros get a clear answer from Thailand on this?
3. Craig: good next step, define data dictionary of what Thailand indicates should be @ field level past what is current data dictionary forms.
• Anne Liu will be poc for CHAI feedback on FI, including dashboards - Derek P will link with Anne about a time for discussion regarding dashboard comments.
2. AOB
• User Story Review Scheduling (Pierre) - Will maintain current dates, Anna & Pierre will connect Wednesday prior to Thursday’s call re descope//user stories.
• DHA: Digital Health Atlas - Reveal has been added as well as CGR and Geowidget. WHO’s vision is to grow the picture of digital health projects out there. Consortium’s role: update geography of
• Improve feedback process to consolidate & ensure tool is fit for purpose for countries. Also, how to dev Reveal in general area which also makes fit for purpose for countries - add as point for future discussion.
• Craig and Matt offline in Mauritania 18-22nd.
• Anne offline week of 18th; on Asia hours week of 25th






General comments:

• Overall the FI app looks very slick and captures interventions that happen during FI well, however what is not clear is how the “investigation” and “classification” components come through. Part of the challenge could be that sometimes interventions happen same time as investigation, but definitely want to make sure we don’t miss the investigation portion before jumping straight into interventions.
• As a reminder from the Thai manual: “the objectives of FI are to 1) confirm malaria case, 2) confirm result of primary case investigation, 3) identify details and additional determinant factors that cause disease, and 4) confirm transmission and identify characteristics of transmission.” Currently I think 1 and potentially 2 come through, but 3 and 4 are a bit unclear in how all the data from the FI comes together to help the focus investigator make a decision.
• To that end a few suggestions below! We’re certainly open to various solutions to the challenges indicated below, but put down some initial suggestions as a starting point.

Launch page / Summary of the focus:

• Suggestion 1: on a launch page for focus investigation, capture the following (similar to what’s on web as well):
• Focus area / boundaries - this will just be the operational areas
• Current Classification (which informs the interventions) (currently in web UI; does not change often, hence was not placed in android client. This needs to be defined further in Thailand. Akros’ understanding was this was an occasional desk review to change classification; (Anne L) field worker should not be able to change classification, but must see what classification is.)In Jan 2019, removed classification data element from android client. We may need to pull this back into the client, however (Craig) this is heavier as will need to sync additional data.
• For mockup purposes - easy to add to launch page (as previous Marvel mockup, Nov 2018)
• Use this as a point of conversation with Prayuth in March meeting with Pedro.
• Launch screen (static report) not the interactive sync data wizard from Nov
• Updated mockup able
• CHAI expects there is some summary of focus needed to be visualized on field side.
• A1: active focus
• A2: residual non-active focus
• B1: cleared focus and receptive
• B2: cleared focus but not receptive
• Previous driver of transmission (from last FI): free text
• (Optional: the reason why it is being prompted – could come through from the MIS or be something that is manually entered by the focus investigator. Reasons why would be:
• A case was classified as “A” during case investigation in a B1 or B2 village (see page 15-16)
• A case was classified as “B” during case investigation (to confirm – in any village type?)
• Routine focus assessment

Investigation / Intervention:

• Suggestion 2: Part of the investigation requires understanding results of past interventions. While this is captured nicely on web, to help give the focus investigator some minimal information to inform their investigation, can some of that previous investigation history / summary come through on the app? Perhaps on the suggested launch page described above? In terms of flow, users would need to know the foci characteristics and past history before commencing a focus investigation.
• Note that we’d have to specify amount of historical data to sync with the MIS with Thailand and balance that with app performance
• Questions for Thailand:
• What information does Thailand need in the field? (vs on web)
• From what timeframe - just last FI? Multiple years of information?
• Suggestion 3: While the Thai protocols do combine some of the investigation with intervention activities, it’d be helpful to make sure that the investigation data is still captured and outputted into a form for review in order to determine driver of transmission. Separate the investigation pieces from the intervention pieces – even if by color. OR have “investigate foci” be a response activity in itself. E.g:
• When a malaria case is detected in an A1/A2 village, FI protocol is (pg 20):
• Investigation: [one color box for actions]
• Repeat case investigation if necessary (EP 1 form)
• Take blood from all family members and all neighbors (at least 50 people or at least 10 HH within 1KM radius) (Blood record form of CDCU/SRRT)
• Describe potential drivers of transmission (this should be free text based on the focus investigator’s time in the field)
• Intervention: [second color box for actions]
• Vector control – treat mosquito nets or distribute LLIN. OR if LLIN not possible, do IRS. (VC4 form)
• BCC (form?)
• Reporting à on the web side, there should also be a “classification” action here as well (see classification feedback below)
• Suggestion 4: the location of the focus activity depends on the location of the index case. While it somewhat comes through in the map in the mock-ups that there should be a radius around that index case, it could come through clearer that an index case was found and that is what defines the “within 20m.” This should be represented both as a clear marker of index case on the map, and potentially on the list of activities as well (where you say “within 20m” – it should be clear that the index case is what defines the 20m radius).
• Also, will this index case be able to be imported through the MIS from CN/CI?
• Alternatively, if the index case is just by the focus investigator who then registers in Reveal, then once registered, does the circle then move locations (and thus the structures within it)?
• Suggestion 5: Interventions should change based on the focus classification of the village (see pages 20-23 for how this maps out)

Classification:

• Suggestion 6: Ideally there should be a recommended to reexamine classification based on the results of the investigation (based on two factors: is there an indigenous case, and in what time frame). Would it be possible to have some flag that classification or reclassification is needed based on the information reported through the app? Either can be manually inputted by a focus investigator that classification should be revisited (a trigger then to higher ups to re-examine in the web platform), or a flag that automatically appears based on the new information collected in the app. The reclassification action itself should come up in web (which I don’t recall seeing in the web mock-ups).

Family member registration:

• Suggestion 7: can we make sure the family member registration only comes up if someone clicks “record index” (which should probably be changed to “Detect Case”)? I think it does based on the titles of each mock-up slide but wanted to confirm.
• Suggestion 8/9: To be validated with Thailand
• One thing we will need to validate with Thailand is the amount of individual level case information that is collected – which should only come up for RACD and MBS. While some of the forms do indicate patient level data, this may conflict with what was mentioned during discovery – where an aggregate # of blood drawn and # positive may be sufficient.
• To this end, we may want to consider the following:
• Suggested change 8 (to be validated): Before registering individuals, there should be an aggregate recording of aggregate # of people who got blood drawn and # positive (# of positive may need to be populated later on after lab results)
• Suggested change 9 (to be validated): If there are any positive registrations, only then should individual case registration occur - which should be optional]
• Wanted to flag this ahead of time and get your thoughts on LOE, though this particular question still needs to be validated with Thailand.





25 March 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Ona: Craig Vital Wave: CHAI: UCSF DiSARM:
Regrets	Vital Wave: UCSF DiSARM: Ona: Akros:

Agenda

1. Review of Previous Week’s Action Items
1. To do: share R2 dot release schedule
• Shared (link)
2. To do:  Akros to get sense of what additional customization needed for DiSARM training documentation and getting that to Ona.
• Need to have a call between Ona and Akros - scheduled for next week.
3. To do: Review descoping suggestions with CHAI
• This was done
4. To do: Contracts - Waiting on sub signatures from UCSF
5. To do: Feedback by now on FI dashboards.
• This was provided by Derek .
6. To do: Pedro’s Reveal slide deck for Prayuth in prep
• Christina, Annie, and Pedro met last week and will touch base again on Wednesday.
2. Team Updates
1. Akros
• Feedback and release process recap
• Usage analytics
• On the calendar this week:
1. Prep for release 2 user and desk testing
2. Release 3 planning
3. Pilot documentation packaging -
2. Ona

Scoping:

1. Roger has continued to work on the Web UI, working with Conor and Kelvin
2. Craig and Sam working on client and server side

Dev:

• Last week:
1. Android Client:
1. Implemented Task Register and ability to open and save forms from the register.
2. Completed Mosquito Collection form and associated card view.
2. Web UI:
1. Worked on UI for focus investigations, finished the UI for historical data
2. Completed drill down capabilities (table views like mSpray dashboards), pulling data from Superset
• Working on this week:
1. Implementing authorization for single sign on
2. Larval breeding site collection forms and card views
3. BCC form
4. Data model and dummy data for plans
• Consortium request
1. What is an appropriate organization hierarchy for the drill downs? Should we target Thailand?
1. Yes - Annie can share a hierarchy (need this April 5)
2. Yes - Akros can share dummy data (need this April 5)

Demo Prep:

• Cambodia CGR - Development has begun. We are on target for delivery on Monday
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. Question:
4. Do we need to do the entire country, or can we just do a single area?
5. One area should be fine - Vivek to confirm tomorrow




1. DiSARM
• Contract Update - pushing but its slow, need by EOM for deliverables due March 31
• Planning on having work ready end of this week
• Release Note Prep/Updates on Algorithms?
1. UI, headless version, repository to be deliver this week
1. Should provide opportunity to see what they do and provide feedback, not a final thing that can be used at scale
2. Provide guidance on specific pieces of feedback
• Latest BMGF Discussions rg Reveal Implementation Timeline/DiSARM stage gate
1. UCSF/DiSARM team had their quarterly check-in call with Jon Cox on March 12. As a follow up, UCSF/DiSARM team would like to have a call with CHAI/Akros/UCSF on April 4 to discuss the Reveal 2019 implementation timeline for Namibia and Botswana.
2. When the UCSF team wrote their DiSARM proposal for BMGF, the initial assumptions were that DiSARM would be used in Namibia and Botswana for 2019. But now that Reveal is replacing DiSARM, UCSF/DiSARM team needs to write/submit a 2019 implementation plan for Reveal instead of DiSARM as part of their BMGF stage gate (due April/May 2019). All stage gate materials need to be submitted in order for the UCSF/DiSARM team to receive their year 2 funding from BMGF. UCSF/DiSARM team will provide more details on April 4 call.
3. Nam & Botswana reviewing APK demos; end of April aimed for decision cut-off
1. Timeline for implementation, landscape, and where UCSF fits into that.
2. Talk through
• LSM/Reveal interest
1. Putting together guidelines/framework around ento surveillance. Standardization around procedures and decision processes. Not yet thinking about digital tools.
• Could you present algorithms on next COP call (theme is algorithms)? April 11 5pm CAT.
1. Yes - UCSF/DiSARM team plans on doing a demo of the DiSARM API for the next COP showcase
2. UCSF/DiSARM also planning on submitting a blurb for the COP newsletter in May and will hopefully include a link to the DiSARM algos explainer video they are creating.




1. Namibia Botswana feedback?
• Discussed on grant partners call that they are testing now
• Touch base on in-country time
2. FI workflows / mock-up feedback
• Incorporations made to android side mockups based on feedback in google doc ; CHAI needs to review that responses are okay.
• Derek P shared feedback on dashboard side today; CHAI needs to review that responses are okay
3. AOB
• CHAI did demo of Reveal IRS version at internal CHAI meeting last week.




April 3 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Anna, Annie, Christina Ona: Craig, Matt Vital Wave: Pierre, Derek T CHAI: Anne, Pedro, Vivek
Regrets	Vital Wave: Ona: Akros:

Agenda

1. Team Updates
1. Akros/Ona
• Contributing factors to delay
• Reveal 2.0 Mid-April Demo Release Candidate Features
1. Annie to do: MBS RCD data dictionary form needs edits so treatment info can be removed from that data dictionary form
2. ITNs
1. Right now Thailand they have a net surveys - number of LLINs and number of HLINS
• Asks for demo prep (discussed later under Thailand conversation)
2. CHAI - Thailand update
• General update from CHAI team
1. Overall went well! They like Reveal and the way it is set up and see a lot of potential value that Reveal can province, especially at household level. Main concern is to actually see the tool! Main concern for WHO is that coverage indicators align with what is in MIS. And translation.
• Akros questions based on Pedro’s notes
1. Any flexibility on enumeration and user testing dates?
1. Timelines - right now this is not exact. Meeting on 17th is to fix the next date from enumeration
1. May 14 - 17 is tentative for enumeration; when Dr. Prayuth is available
2. End of April/First week of May possible for user testing and Ona in country for integration work?
2. Where is targeted for implementation? We will want to make sure enumeration time is enough based on expected structure count
1. Thailand is sharing a list of the provinces/districts and the structure count in these to estimate enumeration timelines
3. Clarification on PMI ask for imagery access?
4. Biophics server - what timelines make sense for Ona team in country?
1. Asking permission from MoH so we can actually test an integration.
2. When we get this back, to see what challenges/issues with enumeration
3. Identify a time for Ona to be in country to sit down with BIOPHICS
4. To do: Akros and Ona to discuss internally re integration timelines
5. Biophic asks for demo prep:
1. The Thailand administrative hierarchy, in both text form and GeoJSON.
1. For foci areas, we need the point files for their locations
1. Thailand is sending for three provinces we are piloting in
2. We need an example drill down of the hierarchy for a few village examples….ie the village and all parents in hierarchy
2. An historical data export of data from BIOPHICS for a few foci for web demo purposes
1. Annie can put this export into the CSV format
3. A sample digital case form from BIOPHICS (JSON or XML) that we will get from their system to show a new case has been sent. I will also ask for this on Slack for DHIS2.
6. What other needs besides the apk itself?
1. User Walkthrough - a less-detailed version
2. But really, if the functionality is there, that is fine.
3. Release 3 tentative schedule/process
2. Review of Previous Week’s Action Items
1. To do: share R2 dot release schedule
• To share after Akros-Ona internal discussions
2. To do:  Akros to get sense of what additional customization needed for DiSARM training documentation and getting that to Ona.
• Scheduled for Thursday, to be worked into R3 scoping




April 9 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Anna, Annie Ona: Vital Wave: Pierre CHAI: Vivek
Regrets	CHAI: Anne Vital Wave: Derek Ona: Akros:

Agenda

1. Follow ups from last week
1. Demo prep asks/Thailand follow up
• Thailand to share with Pedro list of areas for implementation
1. geoJsons for these areas *point files for foci*
• An historical data export of data from BIOPHICS for a few foci for web demo purposes
1. Annie can put this export into the CSV format
• A sample digital case form from BIOPHICS (JSON or XML) that we will get from their system to show a new case has been sent. I will also ask for this on Slack for DHIS2.
2. To do: Akros and Ona to discuss internally re integration timelines
2. Team Updates
1. Akros/Ona
• Clarity on R2 timelines and dot releases
1. Walkthrough of document
2. Are we ready for integration (Rv2.1) in May?)
1. It is on track and is pressing for Namibia Botswana
2. Though, this DHIS2 integration is not a huge amount of work?
3. Rv2.2. Is more important than Rv2.1?
4. To do: Vivek to validate these timings with Sameen and Anne
5. Language translation
1. Client - translation requires separate build (CHAI to help with this for Thailand
1. Current work on the toggling between
2. Web
1. Building from the ground up to be translatable
3. Does OpenSRP have a language package where you click a button or are we automatically translating>
1. It is the latter
• Demo/release candidate prep update
1. Thailand demo functionality
2. User walkthrough documentation
• Timeline expectation setting
1. Development and implementation timelines - need to know implementation timelines before we can feel confident committing to R3 timelines
1. How much customization (and when?) can we expect for Thailand, Namibia, and Botswana.
1. Expectation settings with
2. Thailand timelines and expectations
3. Namibia/Botswana timelines and expectations
2. Additional requests affecting dev timelines
1. Central procedure or protocol for tracking issues.
1. See link in next line item
3. R3 tentative timelines/process
1. Akros shared scoping doc with CHAI on April 8
2. CHAI feedback due April 12
3. Ona sharing R3 feature schedule on May 10
4. Akros to present to consortium on May 14
5. Timelines post May 14 are not set - dependent on scoping
• Reminder - Quarterly report due




1. UCSF
• Tested algorithms with test data - identified and fixed an issue
• Timing of building prediction work?
1. Thailand remote satellite enumeration enumeration is happening either week of May 13 or May 20
• Status on demo for COP call - anything needed?
1. Team is ready to go!
2. Plan: show off the docks (headless versions), show the UI and open up for comments and questions, interested in people in COP who want to test, or other interest in geospatial algorithms form COP
• Report
1. Waiting for subcontract. Report would be great 2 days after subk is signed if possible
• DiSARM website updates in prep for showcase
1. To do: Would like to add blurb on participation in Reveal in advance of showcase on Thursday. Get updates to team tomorrow.
2. CHAI
• Implementation updates from last grant partners call
1. Honduras in initial stages, meeting there in a few weeks, with intro session on Reveal. Week of April 22nd.




April 16 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Ona: Craig, Matt Vital Wave: CHAI:
Regrets	CHAI: Vital Wave: Ona: Akros:

Agenda

1. Follow ups from last week
1. To do: Vivek to validate R2 feature release timings with Sameen and Anne
• Follow up questions
• What is more important from timing perspective - DHIS2 integration or IRS Plan?
1. 2.2 (IRS Plan) is more important than DHIS2 → does this shorten timelines for IRS Plan?
1. To do: Ona-Akros team to talk internally around if pushing out integration brings up the IRS Plan date at all
• To do: Review Focus Investigation
1. Is there anything in the mock-up feedback email “FI mock-up feedback” that didn’t make it into the 2.0 release?
2. Team Updates
1. Akros/Ona
• Release Candidate Update: RC5
1. Walkthrough with APK link
2. Bug tracking
3. Known Issues in Release Candidate that will be fixed for 2.0.0
1. Assigning Index Case
2. Index Case circle by operational area
3. Task list view has many blank tasks. We need to clean up the demo tasks that were generated
4. Demo - on Friday morning.
5. Hope is that be EOW we will have final, WHO, sign off
1. Also have firm dates with aim of training at June
6. We need to do some demo data clean-up. Have another operational area that we haven’t worked on. Village 1, Focus 01 is fine for demonstration?
1. To do: Add a few mosquito points before demo
7. Pierre: some issues - some workflow focused and some cosmetic bugs
1. To do: talk through feedback post demo
• Timeline expectation setting
1. R3 tentative timelines/process
1. Akros shared scoping doc with CHAI on April 8
2. CHAI feedback due April 12
3. Ona sharing R3 feature schedule on May 10
4. Akros to present to consortium on May 14
5. Timelines post May 14 are not set - dependent on scoping
1. Also dependent on anything that comes back from Thailand
2. There are roadmap user stories that are not necessarily linked to the functionality.
3. In the chance that we hear different feedback from countries, we can discuss what may need to be descoped given what we need to prioritize for country needs
6. Thailand production release will take time.
1. To do: we need to
2. Demo notes to call out
1. Hierarchy stops at canton level (Tha Luang canton)
1. We split the canton randomly into two villages and two foci
2. The enumeration was also loaded in
• Development Updates
1. Development and iteration on the Android client (5 release candidates completed and reviewed)
2. Web app is up on a demo server, but not yet connected to OpenSRP server. We will continue working on this for the April 30th deadline.
1. Fine to not have for the demo
2. **Note it is a national holiday in Kenya this weekend on Friday and Monday
3. Thailand “pilot:
• 3 districts, fewer than 20 users → small scale, but still real data and real workflows
4. UCSF
• Contracts - should be all set on this side; waiting for redline from UCSF
• Ona feedback on initial release would be great
1. Will be able to release once we have the contract
• M&E of Namibia and Bostwana ongoing
1. Kicked off in Botswana
1. Data collectors are excited about the possibility of clicking on maps and structures in the field!
5. Botswana potential implementation
• Sinka reached out and we (Akros and CHAI) will hopefully meet with him and others in-country in the next few weeks.
6. Namibia is still undecided - end of month yes or no deadline




April 23 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Annie Ona: Craig, Matt Vital Wave: Derek, Pierre CHAI: Anne
Regrets	CHAI: Vivek Vital Wave: Ona: Akros:

Agenda

1. Follow ups from last week
1. To do: 2.2 (IRS Plan) is more important than (2.1) DHIS2 → does this shorten timelines for IRS Plan? Ona-Akros team to talk internally around if pushing out integration brings up the IRS Plan date at all
• Makes it more manageable but still need the full time (June 30) for IRS Plan
• Can we confirm this can be moved out of 2.1? Since there is no confirmed date for DHIS2 integration? And if yes, where should this be moved?
1. This is implementation specific (i.e. data mapping is the hard part, not the technical piece). This need will appear in Botswana - they are expecting integration.
2. Potentially during/end of summer: end of July or end of August?
3. How much time is required for this?
1. One way pull from org hierarchy in DHIS2 followed by push from Reveal into DHIS2
2. Rough estimate is 5 weeks if aggregate
1. Need to confirm if this would be aggregate or event as this would affect the timing
1. AL update 4/24: this would need to be confirmed by the government. If events, one question we would have would be whether it’d be 1 building = 1 event or if mit makes more sense to do 1 HH = 1 event.
4. To do: Annie to add the scoping of this integration to the list of items to work through with Botswana
1. NMEP still needs to do the build for IRS indicators, need to validate
1. AL update 4/24: this would likely be done by the MOHSS IT department (Sinka). Only the NMEP, MOHSS, and their IT consultant have access to the system. Confirmed that no IRS indicators currently exist in their system.
2. Need to have access to the demo server or a full export after the indicator build is complete
1. AL update 4/24: Should include this in asks during the Akros visit to Botswana (CHAI has less insight / involvement in the DHIS2 work in Botswana)
3. Could pull Reveal build into DHIS2 instance to “mock” it up for Botswana
4. Before going anywhere, need to have agreement on the data dictionary fields
1. AL update 4/24: This would need to be finalized by the Botswana vector control team - ideally by May in order to plan in time for IRS season.
5. End of August - is this reasonable to be done by that point?
1. To do: Anne to check with Sameen and as we start conversations with Sinka.
2. To do: Review Focus Investigation. Is there anything in the mock-up feedback email “FI mock-up feedback” that didn’t make it into the 2.0 release?
• Yes, some items that were fed-back were relevant to later release scoping. Those items (planning for FI for example, will be fed into R3 and R4 scoping). All documented here: https://docs.google.com/document/d/13iOe_etxgMrFMj46OMMZE2qSYGWZFG4zMqd7dR_TgQA/edit
• To do: Annie to line this up with this document:https://docs.google.com/presentation/d/1njPF68ZfDlB8zFOGWsWx-3wpnGhKSpTK6YwA9SHfm1g/edit#slide=id.g548738b54b_0_106
• How it generally breaks down: R2 - FI; R3 - FI planning web piece
• Still outstanding is how case confirmation should work: should 3rd party system push to Reveal, Reveal create task and push it to the appropriate team?
• Anything that is not in the mobile client that is major that is not currently developed?
1. In testing document: Ability to touch on location and see all details on that location even if a task is not assigned → expectation from Akros team
3. To do: talk through feedback post demo
• Scheduled call tomorrow - Christina to send agenda, including feedback pulled out from Pedro’s notes
2. Team Updates
1. Akros/Ona
• Thailand
1. 2.0 Schedule with Thailand requested changes
1. 1 -2 added dashboard indicators
2. ~15 form changes to skip logic and data fields
3. 3 major form changes (MBS, Larval, Mosquito)
4. Other feedback
2. This is a significant amount of feedback given we are trying to take this to the field on the 27th for user testing. This means we are developing IRS in parallel to supporting Thailand. There are various other pieces besides coding that need to happen for all of this to come together.
1. Can we confirm how these extra Thailand requests may affect Release 2.0 timing and how  they in term may affect IRS planning timing. To do: Ona to share these thoughts tomorrow.




• To do: Annie and Anne and Sameen to discuss/prioritize IRS Planning mockup.




1. FYI - BIOPHICS and Thailand team dynamics
• R2 release candidate
1. Addressing remaining bugs will this now be a part of next 2.0 release?
1. This is correct.
• R2 Progress and Needs
1. We created the Reveal Web UI & Reporting Data Dictionary
2. Developed the Data Warehouse tables
3. Working on the ETL process now
4. Work will begin on plan definition implementation in the server and Android client starting tomorrow
5. Needs
1. Demo/dummy data would be helpful now that we have a database structure
1. Akros To do: In Web UI data dictionary → define sample data in sample_sheet.
2. Flesh out one or two more villages (A1, A2, B2, B1)
1. Give sample plan and dummy data for each
2. Historical dummy data as well, but not year
• R2.1 Progress and Needs
• R2.2 Progress and Needs
• R3 Progress (Scoping)
1. Akros to respond to all feedback by EOD 24th (tomorrow)
2. Ona sharing R3 feature schedule on May 10
3. Akros to present to consortium on May 14
• R4 Progress (Scoping)
• Miscellaneous
1. Hardware testing - lower level hardware, will need demo data for scalability
2. Akros To Do: check on testing with 1.5gb RAM (Botswana) and 2.0gb RAM (Thailand - TBD, they haven’t purchased but have asked UNOPs for clearance on higher end models but think it’s going to be difficult)
1. UCSF
• Updates
1. Waiting on contract to be finalized (on Akros side)
• Discuss Thai algorithm work
1. DiSARM specific work
1. Talking with Prayuth in the past about need for better forecasting for malaria transmission to use in planning for FI or other intervention campaigns. This was never a specific deliverable but been working on it on the side.
2. Algorithm: case data (daily updated) in raw or aggregate to forecast for the expected incidence next few weeks and whether above or below threshold. No longer have a technical contact there, but could this algorithm be wired into Reveal? To demonstrate that the algorithm could run. Could propose this formally under the DiSARM grant work
1. Q: at what org hierarchy unit does this happen → they are reporting data at the village level. Forecast at the village level (statistically) though this may or may not be accurate
3. DiSARM team in Thailand now - have them discuss with Prayuth.
4. RTI - Darin and Joe were working
2. (in future) Update from Adam on other work ongoing in Thailand







April 30 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Annie Ona: Vital Wave:
Regrets	CHAI: Vital Wave: Ona: Akros:

Agenda

1. Follow ups from last week
1. Integration conversation with Botswana. To do: Anne to check with Sameen and as we start conversations with Sinka.
• This is ongoing. Meeting scheduled 2nd week of May.
2. Akros To do: In Web UI data dictionary → define sample data in sample_sheet.
• Done
3. Akros To Do: check on testing with 1.5gb RAM (Botswana) and 2.0gb RAM (Thailand - TBD, they haven’t purchased but have asked UNOPs for clearance on higher end models but think it’s going to be difficult)
• Preliminary testing with 1.5gb Ram, working fine.
• Comfortable to give Dr. P the heads up with 2.0gb ram
• Testing 1.5gb the week of the 13th week.
4. To do: Annie and Anne and Sameen to discuss/prioritize IRS Planning mockup.
• Annie to send initial email to group on how to segment both IRS and FI Planning (Anne, Sameen, Vivek, Pedro, Pierre, Derek).  
5. To do: Review Focus Investigation.  Annie to line what is being developed with this document: https://docs.google.com/presentation/d/1njPF68ZfDlB8zFOGWsWx-3wpnGhKSpTK6YwA9SHfm1g/edit#slide=id.g548738b54b_0_106
• Web UI for desk review/planning - R3, not May 10th (slides 7-8, 18, 19, 24)
• User management as part of Reveal UI tbd if R3 or R4 (25-26)
1. OpenMRS is an UI for creating users it is just not a part of the OpenSRP WebUI - but it is a complete user interface
• All mobile client workflows captured are in R2
2. Team Updates
1. Akros/Ona
• Development
1. R2 Progress and Needs
1. Release has been pushed to May 10
1. Lusaka-based user testing pushed to week of May 13
2. No other trickle down effects for Thailand timelines (including translation timelines)
2. R3 Progress (Scoping)
1. Annie reaching out to the group around Fi and IRS Planning to prioritize
3. R4 Progress (Scoping)
1. No updates
• Thailand
1. Weekly meetings scheduled for Wednesdays
1. Cancelled this week
2. Enumeration discussion happening between CHAI Akros VW on
2. Translation info sent
1. Data dictionary
2. Transifex
3. Christina sending out workplan tomorrow morning to capture microplanning and discussion of dates so far
1. Please review for feedback and send via email- will review finalized version next week on Thailand planning call
2. Ona team specific questions:
1. Dates and dev resources for in-country build time for integration - target is for a developer in country alongside BIOPHICS team, ideally at their offices.
1. First week of June is the current date
2. Currently trying to see if we can move this up to the last week of May to follow on with user testing
1. Pedro is trying to clarify this right now
3. Assume first week of June to tentatively hold/assign engineer
4. Once decided on team member, will need to do a visa letter.
2. What specific integration pieces can we ask for ahead of time?
1. Best case: access and credentials to staging server
2. Direct db connection is the plan because BIOPHICS doesn’t have an API- need to start to understand this.
3. Several layers to evaluate:
1. Semantically interoperable? BIOPHICS data dictionary is needed
1. Field mapping
2. Indicators have same data definition
2. Technical integration
1. BIOPHICS system has database user to access tables
2. Specific versus transactional database (data sent to a holding area for BIOPHICS to load into live tables)
3. Need to validate/challenge core assumption that no development work to BIOPHICs would be needed
4. Need point of contact
5. Working on credentials and access to test server.
6. **go, no-go decision on sending an engineer**
1. Need access to system by mid month to know
7. What can be done ahead of time?
1. Data mapping.
3. Specific data formatting required of geojsons?
1. Attributes needed?
1. Looking at the fields in the add.point section of the data dictionary (Link)
4. Enumeration discussion happening Thursday
5. Imagery
1. Mapbox licensing
1. NMEP can do negotiation for licensing country-by-country
2. Matt to discuss with PATH to see if we can get some kind of account for Reveal use for governments for malaria
2. Enumeration - have many options for this through osm web tool
3. Reveal app - imagery here requires downloadable tiles which not all services give access to.
4. Need to revisit this conversation to look at costs that are going to come up as part of the structure of this project.
• Botswana
1. Annie to send out internal proposed workplan next week (including all)
1. All to review prior to in-country meetings week of May 13
2. UCSF
• Updates
1. Contracts team sent redline yesterday
1. Annie to schedule final call and discussion with contracts team early next week to finalize any remaining edits.
• Discuss Thai algorithm work
1. Any updates from in-country team time last week?
1. Team in Thailand will follow up with Dr. Prayuth once he returns
• Question
1. Are there any attributes that we can collect from local experts on villages (foci areas) that would be useful for analysis (spatial or otherwise)?
1. Ali to check in with larger team on this.
2. Updates from Namibia and Botswana 2019 implementation discussions?
1. Botswana discussions happening 2nd week of May in country with Akros and CHAI teams for planning
2. Namibia should hear back today, Anne confirming if/what we have heard
3. Stagegate for DiSARM grant requires follow-on planning; due date has been pushed back to May 30th
3. DiSARM M&E feedback
1. Activities underway
1. Done and ongoing interviews in Botswana, to continue over next several weeks
2. Namibia meeting next week to conduct focus groups for feedback on tool
2. Current agreement is that report is shared with CHAI, countries, Gates, DiSARM
1. Would be useful to share with Reveal team
1. To do: Anne to check with country programs to get clearance if they are okay with sharing these reports with Reveal team
2. Preliminary results end of May, hopefully final results in June
3. Range of feedback
1. Suggestions for certain features and capabilities of tool
2. Reflections on trainings





May 7 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Annie, Anna Ona: Craig Vital Wave: Pierre
Regrets	CHAI: Vital Wave: Derek Ona: Matt Akros:






Agenda

1. Follow ups from last week
1. To do: Annie and Anne and Sameen to discuss/prioritize IRS Planning mockup.
• Annie to send initial email to group on how to segment both IRS and FI Planning (Anne, Sameen, Vivek, Pedro, Pierre, Derek).  




• To do: Ali to ask DiSARM team: Are there any attributes that we can collect from local experts on villages (foci areas) that would be useful for analysis (spatial or otherwise)?
• To do: get BIOPHICS database dump, access, and POC




• We have a database dump
• *Note, BIOPHICS is running on SQL so they are paying server fees for other malaria software




• To do: Matt was talking with MapBox about potential license opportunity for Reveal/malaria




1. To do: Anne to check with country programs to get clearance if they are okay with sharing the DiSARM reports with Reveal team
• Can go through CHAI country team (Erica) - she can send if she gets clearance
1. Team Updates
1. Akros/Ona
• Development
1. R2 Progress and Needs
1. Web UI map view
2. Web UI table view - Active FI list and Active FI detail view is set.
3. ETL process from transactional to data warehouse is being finished this week
4. Authentication piece (single sign on for Web UI and mobile client) done and tested yesterday - no major issues
5. Updated client side forms so that all Thai data dictionary changes are in the client
6. Not in R2 release (May 10th)
1. Toggle/hover map view functionality not be ready for May 10th
1. Still need to identify what happens when you click on a point
2. Toggling on layers still needs to be scope
1. E.g. “what if you have four layers toggled on” → Annie to check if this has been designed on the Akros.
2. ETL process to present forest goer and outdoor sleeper indicators - data collection for this is supported, reporting is lagging
7. Need to schedule R2 Thailand release, post May 10th
1. For May 21
1. User testing scenarios (Thailand)
2. Translation (Thailand)
1. See notes below on updates. What translations we have in time for May 21 will be included in a May 21 release.
3. Above functionality in (6)
4. Bugs/fixes identified in desk testing and Lusaka testing (as appropriate)
5. **Risk is translation**
2. For May 27 (potential)
1. Translation fixes
2. R2 Testing Plan
1. Akros team on board for Desk Testing - Monday
1. Based on script shared on 10th
2. Akros team doing user testing in Lusaka on Wednesday
3. Feedback to be collected in the bug tracker
3. R3 Progress (Scoping)
1. Annie and Matt discussing this week (IRS Plan)
2. Need to schedule time to discuss FI Plan and IRS Features
4. R4 Progress (Scoping)
1. May have a team workshop late summer for this scoping
1. Evaluate need for this in June
• Thailand
1. Integration
1. Have database dump (SQL server database)
1. Can start database mapping at the table level
2. Integration diagram
3. Dates for integration added to workplan
1. Can we add dates to these in workplan?
1. Investigate BIOPHICS database
1. Where tables are, where we need to add our data so it makes sense
2. Database engineer tasks
3. Can be done with database dump, can be done prior to going in-country, but will need input from BIOPHICS team
2. Develop NIFI workflows (2,3,4)/// Map Reveal to BIOPHICS Reveal database tables (5, data mapping)
1. Build for one content area at a time (locations, forms, tasks) Can do mapping now into tables and then link BIOPHICS tables to BIOPHICS field when in country
3. Develop BIOPHICS ETL (1, 6)
1. Need BIOPHICS
2. To happen in country
4. Test on staging server
1. To happen in country
5. Gain access to BIOPHICS production
1. To happen in country
6. Implement on BIOPHICS production
1. To happen in country
2. First week of June still is a good week
3. From last week: Need to validate/challenge core assumption that no development work to BIOPHICs would be needed
1. Can we assess this now or not?
1. Yes, definitely, but we have contacts on the Thai side who are resourced to do some of this developement
4. We do have approval for access to server from MoH, just depends on when
5. To do: Craig to review the tasks and add dates to the workplan
2. Translation Dates
1. Data dictionary by 10th
2. Client strings by ?? this probably won’t happen in time for user testing, though if we get this by the 20th, this would be fine for the 21st
1. **Note, Annie misspoke on previous call, this release is just client string translation
2. BVBD is working on hiring another translator to do this
3. BVBD understands the consequences of not delivering this translation




1. Workplan
1. Christina finalizing feedback on this - dates to be considered our working dates. We will be using this workplan as project planning tool moving forward
2. Mapbox license / Imagery  - Anna, Matt, and Anne discussing this week




• Botswana
1. Derek to send out internal proposed workplan end of this week (including all)
1. All to review prior to in-country meetings: pushed to week of May 27
2. No delays anticipated
3. We are planning to discuss the agenda for this meeting next week
• Namibia
1. Response was due end of last week which was not received. CHAI has followed up
1. Giving them two more weeks but it’s looking unlikely (they want to finish DISARM M&E first, but if that takes another month it’ll be very tight for prepping for IRS planning for the summer). Will likely let them know the door is still open for 2020, but we would need to know this week for whether 2019 will happen.
• UCSF
• Updates
1. Annie waiting on contract from UCSF team - please remind contracts team
2. Hugh at NTD meeting and discussing hotspot surveillance
1. Discussion for need for digital tools for doing this
2. Hugh mentioned Reveal and there seems to be interest
• To do: Ali to ask DiSARM team: Are there any attributes that we can collect from local experts on villages (foci areas) that would be useful for analysis (spatial or otherwise)?
1. Ali to ping Adam
• DiSARM M&E is moving forward
1. Microplanning this week
2. May 27th visit for Botswana program
1. Ask about feedback from the M&E




1. AOB
• Workshop @ ASTMH & NNN -- Interest from partners to join with content, use cases?




• To do: Anna to share write-up in the next two days




• PATH-MACEPA open to providing feedback on Reveal // APK, Video
1. PATH waiting to hear on a grant for Senegal & Zambia to use DSME tools
2. PATH has also been liaising with CHAI on understanding the DSME tools better (CHAI has a folder of materials to send to them including APKs, etc)
• PMI greenlight to implement Reveal/mSpray in Zambia, expanded scope





May 14 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Annie Ona: Matt Vital Wave: Pierre, Derek CHAI: Anne UCSF: Ali
Regrets	CHAI: Vital Wave: Ona: Akros:






Agenda

1. Follow ups from last week
1. To do: Annie and Anne and Sameen to discuss/prioritize IRS Planning mockup.
• To do: (specifically around connecting index cases and secondary cases) We’ve scoped IRS Planning features into MVP or feature - please review the proposed IRS and FI feature document (shared later in agenda)




• To do: Ali to ask DiSARM team: Are there any attributes that we can collect from local experts on villages (foci areas) that would be useful for analysis (spatial or otherwise)?
• To do: Matt was talking with MapBox about potential license opportunity for Reveal/malaria




• Issue 1, pointing sdk: Tech side: everything we are using is open source and we have the ability to point at any server we want (MapBox is just one example of a server that hosts tiles). We can point the geowidget SDK at any server. E.g. Digital Globe. There are a few free options out there.
1. How much work is this on the dev side?
1. Changing a parameter path. Default right now is the url path to MapBox. (WTMS server should be fine).
2. This will be tracked as part of GeoWidget work.
• Michel (community lead at MapBox): discussions around use of free or discounted use by MapBox to provide to malaria programs/ministries
1. Call set up to discuss tomorrow
2. GOAL: get a partnership together - ask for minimum 2020, would be great to stretch to 2024.
• Pricing we heard earlier was commercial (~500-600$/month). Non-commercial use is much cheaper.
• Issue 2, imagery: imagery quality can still vary. We need to assess the necessity of high resolution imagery to Reveal
1. As a consortium we need to assess where and when high resolution imagery is critical and where it is less so
2. Assessment
1. To do: Annie to check if this has been designed on the Akros.
• Toggle/hover map view functionality not be ready for May 10th
1. Still need to identify what happens when you click on a point
2. Toggling on layers still needs to be scoped
3. E.g. “what if you have four layers toggled on” →
4. Both designed and reviewed
2. To do: Craig to review Thailand integration tasks and add dates to the workplan
1. Ona workplanning now to confirm dates
2. Have someone installing SQL server and looking at data dump and by next week should have data model figured out and data mapping work started. This will likely be two people.
3. Matt and Craig following up on task in the workplan. Task clarification
1. Data will go from Nifi (Reveal) into holding tables (BIOPHICS) and then business logic script will move to production tables (BIOPHICS)




1. Team Updates
1. Akros/Ona
• Reschedule of next two weeks’ calls - 8 or 9am EST?
1. To do: Annie to each out to reschedule offline
• Development
1. R2 Progress and Needs
1. R2 is out: Release Narrative
2. Bugs: the Reveal 2.0 bug tracker
1. ETL bug → web UI dashboard and supersets not testable
2. Client bugs
1. There are some outstanding pull requests that need to be merged → this will address many of these bugs
3. Plan is still to do a fix release by May 21
4. Ona to: Sample Plan tab of Web UI data dictionary - need these plans and their spatial files loaded (Christina emailed today)
1. For full desk testing so can test all tasks (asap)
2. For user testing in Lusaka/Zambia (end of this week)
3. For user testing in Thailand (May 21)
2. R3 Progress (Scoping)
1. Proposed scheduled feature release for IRS and FI Planning
1. IRS feature release
2. FI feature release
2. TO DO: Anne to share with Pedro and Sameen and confirm no concerns from country perspective
3. R4 Progress (Scoping)
• Thailand
1. Integration
1. Ona: Progress on database dump
1. Downloaded and looking at schema
2. Resource planning to determine specific dates and team assignments now
2. Translation Dates
1. Note
1. We have the data dictionary - plan was to work this translation into the May 21 release
2. Don’t expect client strings in time
• Botswana
1. Call held today between Akros, CHAI, VW teams.
1. Derek to send follow ups
2. Derek/Annie to schedule time with Ona team to align resources
3. Annie to send to Ali
• Namibia
1. No updates at this time - Sameen has a call tomorrow.
2. Ali: We advocate towards pushing towards Reveal as if they go with DiSARM there is additional planning efforts required and the team will adjust.
3. This is a resourcing issue on the Reveal side too if they wanted to use Reveal -->would be 12 users in Oshana province
1. If we went forward, we would have to think about larger scale resource planning
4. What about the other provinces?
1. There is a question if they want to use digital tools at all
5. M&E feedback in focus groups
1. Per focus groups: “paper tools are outdated” → perhaps there is more appetite for digital tools.
2. UCSF
• Updates
1. DiSARM team shared prototype - Akros and Ona reviewing this week
2. Contract update - team in the office of technology transfer still reviewing the IP of the terms. They may come back with another edit/request for review.
3. Hugh and Jonathan are in Oslo meeting with DHIS2 to talk about integration.
1. Will share updates on this next call
4. Re Namibia conversations in using DiSARM or not, are there specific features or modules that the program doesn’t want to use? (This could potentially ease the prep work required)
3. AOB
• None






May 21 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Annie Ona: Matt Vital Wave: Pierre CHAI: UCSF: Hugh, Ali
Regrets	CHAI: Vital Wave: Ona: Akros:






Agenda

1. Follow ups from last week
1. To do: various Botswana follow ups
• Discussed in Botswana section
2. Proposed scheduled feature release for IRS and FI Planning
• TO DO: Anne to share with Pedro and Sameen and confirm no concerns from country perspective
1. FI planning the dates should be fine - yes you can view the focus info
2. IRS planning - Sameen questions on dashboards that we have addressed
1. Annie to send link to current mSpray dashboards




• To do: Annie rescheduled this call
• To do:  Ona to add sample plans for testing




• Added Lusaka plans, added additional testing plan. Adding Thailand user testing plans today
1. Team Updates
1. Akros/Ona
• Development
1. R2 Progress and Needs
1. R2 is out: Release Narrative
2. Bugs: the Reveal 2.0 bug tracker
1. ETL bug → web UI dashboard and supersets not testable last week → this is now testable in ½ plans; supersets still not testable
2. Client bugs
1. Most of these addressed
3. We are testing again tomorrow to prioritize a 2.0.3 release before Monday
1. Hoping to also get translation feedback from BVBD
2. R3 Progress (Scoping)
1. Meeting with Ona to discuss August IRS Feature Release, MDA, ITN tomorrow
2. Akros-Ona-VW meeting 1st week of June
3. R4 Progress (Scoping)
1. No update
• Thailand
1. Enumeration, Foci Mapping this week
2. User Testing
1. 2 areas prepped for user testing
3. Integration
1. Ona: Progress on database dump
1. Dates added to workplan and on track: https://docs.google.com/spreadsheets/d/1yFkTcbszNEzhRLGvJmbi8wxGaMcvJZbXgCiDwgeZfOg/edit#gid=0
2. Ona: personnel assignment
1. Jannette Wambere (Ona) is an integration specialist who will travel to Thailand and she has begun the analysis of the BIOPHICS system
3. In country team
1. Jannette, Pedro, Pierre (first half of week)
4. Translation Dates
1. Form translation was in Sunday’s release
2. Strings - update tomorrow
3. Can start evaluating kinks in
5. Thailand enumeration - is there info we would want at the foci level that is spatial
1. Even if we have this knowledge, can we digitize it and capture it in detail?
2. Actually, we will of course have data like this coming in live from field validation
6. Thailand MapBox
1. Can we create a username/password for Thailand?
1. To do: Annie to discuss with Pedro while in country who this should be.
2. This person would ideally be able to manage this account post 2020 into the next three years (if we get the license)
3. BVBD generic username/email account → this should be a fixed username for the next three years
4. Ideally this account (if we do get access) would be set up prior to piloting so MapBox could see what the map requests would look like per pilot (in terms of volume of requests).
5. 300 tiles/100 sq kilometer = 100 calls; 200,000 tiles is the free user max
1. Need to know total calls




• To do: Annie to understand total square area after focus mapping is complete (likely this will come mid next week)




• Pierre: What is the work involved in making the GeoWidget tile-server-“point” a configurable field?




• To do: Matt to determine




1. Adding this as a user story
• Botswana
1. Imagery update:
1. MapBox conversations happened last week - Mikel and Anne discussed potential for license for 3 countries through 2020. Mikel would like to see usage patterns.
2. Speaking to Alex Fortescue from DG Africa BD. He’s providing costing and options for accessing both imagery and building footprints.
3. Need to update imagery doc to reflect OSM inputs.
2. Follow ups from Botswana call:
1. Plan for next week
1. Derek updating agenda
2. Updating workplan
3. Reviewing data dictionary for presentation
4. Preparing materials (Presentations and validation exercises using walkthroughs)
2. Server setup requirements info
3. Botswana imagery options
• Namibia
1. Resourcing
1. Matt is currently reviewing the several implementation workplans to ensure Ona can plan their resources.
2. Workplan
1. What are items in red?
1. That was an artifact; removed the red
2. Structure versus household level data collection? -
1. Every form corresponds to a HH; without the HH form the information collected is based on structures. E.g. - in 1 HH form, 5 sprayable structures and I sprayed 3
2. Note Namibia calls a room a “structure.” Structures in Namibia are rooms.
3. “Manually entered targets” → are these both for planning and the denominator?
1. For planning - the actual operational areas and hierarchies will be a shapefile similar to an org hierarchy in DHIS2
2. Target structures - the only manual part (so the denominator)
4. Akros support
1. Operational GIS/mapping support needed?
1. If this is enumeration then no
2. The only support needed is reviewing imagery and helping to select imagery




• To do: Annie to follow up with Matt and Ona team around decision on Namibia dates.




1. To do: Sameen to send some questions on mop up workflow; in the meantime will start collecting materials
1. UCSF - Annie touching base with team Thursday re algorithms
2. AOB
• None




June 4 2019





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Annie Ona: Matt Vital Wave: CHAI: Vivek UCSF:
Regrets	CHAI: Vital Wave: Ona: Akros:






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





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Annie Ona: Craig Vital Wave: Pierre CHAI: Anne, Vivek UCSF: Ali, Hugh
Regrets	CHAI: Vital Wave: Ona: Akros:






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





Time	21:00-22:00 East Africa 20:00-21:00 Central Africa 13:00-14:00 Eastern 10:00-11:00 Pacific
Attendees	Akros: Ona: Craig, Matt Vital Wave: Derek CHAI: UCSF:
Regrets	CHAI: Vital Wave: Ona: Akros:






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
2. 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
• 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