April 3 2019

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

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

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

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

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