5

...

March 2019

Agenda

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

...

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

...

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

...

UCSF DiSARM:

Ona:

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

...

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.