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.