Intro & Level Setting

• Introductions

• Set ground rules

• Level set with all participants reviewing the purpose of the meeting and expected outcomes

Clay and Craig Leading

1 hour

Overview of Requirements

• Current state of reporting

• Project plan

• Overview of the current source material that has been reviewed

•  

  • Industry indicators

  • 13 Gap reports

  • Ashraf’s presentation (eLMIS source reports)

• Share trends that we have identified

Clay Presenting

@Muhammad Ahmed (Unlicensed)

2 hour

Lunch

1 hour

Group Discussion User Profiling

• Define different users and needs

•  

  • Job function

  • What do they look at?

  • How?

  • How often?

  • Self-service?

• Using this as starting point: https://openlmis.atlassian.net/wiki/spaces/OP/pages/112138662/Reporting+and+Analytics

Session Output:

• Wiki page created with defined user profile outline to be completed after the meeting.

@Clay Crosby (Unlicensed)

@Craig Appl (Unlicensed)

@Ashraf

@Muhammad Ahmed (Unlicensed)

@Mary Jo Kochendorfer (Deactivated)

@Wendy

@Christine Lenihan (Malawi experience)

1 hour

Zambia and Tanzania Lessons Learned

• How is this different that what was just presented?

• What are the pain points?

• Critical success factors

• Describe core users and journeys

• Reporting needs that differ

• Reporting gaps

Session Output:

• Notes from meeting

Clay and Craig Moderating

1 hour

Group Discussion of Cross Cutting Functional Requirements based on eLMIS experience

• Moderated group discussion determining cross-cutting functional requirements:

•  

  • Role Based Access Controls

  • Data Restrictions

  • Exports/Printing

  • Embedding Reports

  • Others

Session Output:

• High level list of cross-cutting features

• For each feature, a link to existing functionality in eLMIS for further research

• Notes documenting each feature based on discussion

Clay and Craig Moderating

1 hour

Gap Brainstorming

• What was not possible in eLMIS reporting and what could now be possible?

• Operational gaps

•  

  • New indicators?

• Technical gaps

•  

  • Visualization

  • Distribution

  • Feedback loop

Session Output:

• Wiki page created with team notes

Clay and Craig Moderating

@Muhammad Ahmed (Unlicensed)

1 hour

Review

Recap of the day

Clay and Craig Moderating

0.5 hours

Recap of Previous Day and Level Setting

Clay and Craig Moderating

0.5 hour

Technical Report Analysis

Report-by-report review (12 reports total)

• Purpose of report

• Indicators in report

•  

  • Data elements

• Visualization style

• Distribution method

•  

  • Who, where / how

• Is the report actionable for the user? Under what conditions, and how?

Session Output:

• Each wiki page has been updated

• New wiki pages created as needed streamlining reporting needs

Clay and Craig Moderating

@Muhammad Ahmed (Unlicensed)

2.5 hours

Lunch

1 hour

Malawi, Mozambique Lessons Learned

• Review of implementation

• Reporting needs

• Reporting gaps

• Successes

• Pain points

Session Output:

• Session Notes

Ashraf, @Muhammad Ahmed (Unlicensed) (Optional), Christine

1 hour

Indicator Review

Detailed review of indicators from multiple sources.

• Which prescriptive indicators should we consider beyond the 12 reports?

Clay Moderating

@Muhammad Ahmed (Unlicensed)

1 hour

Gap Brainstorming

• What was not possible in eLMIS reporting and what could now be possible?

• Operational gaps

•  

  • New indicators?

• Technical gaps

•  

  • Visualization

  • Distribution

  • Feedback loop

Session Output:

• Wiki page created with team notes

Clay and Craig Moderating

@Muhammad Ahmed (Unlicensed)

1 hour

Wrap up

• Review findings

• Plan next steps

Clay and Craig Moderating

1 hour