Status

For IRS Planning MVP, by end of July, CHAI is expecting the following:

• Ona will manually upload shapefiles (note that Akros has a copy for both Namibia and Botswana)
• CHAI to select operational areas (OAs) in Reveal interface (worst case scenario if CHAI provides OA IDs, Ona can do it)
• CHAI or MOH team create users and teams in OpenMRS interface (eventually this will be built into OpenSRP) 
• CHAI to assign team leads in Reveal interface
• For Namibia, CHAI to provide the denominator targets as a CSV and Ona will load it (rather than have people individually click through and edit each target)
• Everything that Matt showed in IRS planning mock-ups on June 27, except risk and resource estimate

Mockups: https://marvelapp.com/project/3801200/

Notes on UI behavior

• By default all districts will be selected - user will have to deselect them to remove them from the plan, can also unselect OAs under the selected districts
• Once team assignment done - there would be a "Save Plan" or "Publish Plan" that would generate the tasks and assign to team members

• Teams are created in the OpenMRS interface - will need to provide clear documentation on how to do this, until the OpenSRP teams UI is ready

Namibia Denominator 

• Denominator will be a manually entered target for all sprayable rooms, which has already been determined by Namibia NMCP in May during microplanning, and will be provided by CHAI in CSV and uploaded by Ona
• Numerator should be the sum of all sprayable rooms, as collected in a field within the form submitted per structure, or from all forms submitted for a given structure, if multiple forms are submitted (e.g., 1 structure may have 5 rooms; the numerator for the structure should then be 5 – progress is measured against the # of rooms)

Other key considerations

• Data will be siloed per county - will not be able to see team members from other countries

Outstanding Questions (under review by Matt Berg)

1. Editing a plan that has already been published is complex - need to figure this out (e.g., how to remove tasks, reassign tasks)
2. Another complicating factor: mop ups - different team members might be deployed on different days to the same op area - do we add new teams?
3. Program might add additional teams if they realize add'l resources are needed

Post-MVP Requests:

1. Hierarchies are currently districts and OAs. Note that we will eventually want this to aggregate up into regions, etc.
2. Would want a mouse over or label on the map.
3. Could allow through UI the ability to upload a CSV (with district OA IDs in each row) that has additional attributes (e.g., resource estimate, # of structures) and display those attributes in the planning UI. Matt indicated that in the longer term these attributes could be used to present the user with color sliders as a layer on top of the planning OA maps (if the attributes are numeric)
4. Eventually countries should have the ability to enter their own manual denominators – either by uploading a CSV as long as it’s a user friendly enough template, or have them edit each target directly in the planning interface

Workflow

0.1.0 Release

Log in and navigate to IRS:

Scroll down and select "Create new plan". Enter settings/details on the New IRS Plan  and select "Select Jurisdictions":

On the Plan screen, view the area for the plan:

Selecting 'edit' allows you to change the name of the plan.

The following steps are currently described without screenshots as the web pages were having perfomance issues when loading maps.

If you scroll below the map, you see a table that allows you to check boxes on or off, effectively, selecting the areas below national level that you want to spray.

Each of these levels below national level is a hyper link - if you click it you are taken to that level and can select the areas at the unit below that level for selection.

You can continue to drill down until you reach the level of the operational area. 

Team selection is still being finished, so you will not be able to interact with the teams listed against the units in the organizational heirarchy.