2020-07-31: First Analytics Squad Call this Friday: Kick-off and phase 1 work discussion

Our first Analytics Squad call will be this Friday at 6:30pm IST | 4pm Nairobi | 3pm Cape Town | 1pm UTC | 9am Boston | 6am Seattle.

:white_check_mark: Agenda: Specific questions we would like to address in the kickoff meeting are:

  • Our prototype goals (phase 1)
  • How often we meet
  • Where we collaborate digitally
  • Data environment: Cloud vs On Premise; Centralized server with unified sample dataset that we can use to do development and analysis

:link: Helpful links for this squad:

:calling: Join info:

https://iu.zoom.us/j/94119314896 Meeting ID: 941 1931 4896

One tap mobile: +13126266799,94119314896# US or +13462487799,94119314896# US

Looking forward to seeing you there! @akimaina @bashir @ibacher @dkayiwa @spkabugo1 @jayasanka @insookwa @wyclif @aojwang @ccwhite23 @willa


Thank you to all who joined for our first Analytics Squad call today! A couple follow-up items:

  • Notes and recording: https://wiki.openmrs.org/display/projects/Analytics+Squad+Notes
  • Key strategy moving forward: ~20% of squad calls to be a demo from an implementer, to ground us in on-the-ground implementations’ experiences and requirements
  • Requirements are in flux and we welcome input!!
  • Meeting cadence will be at least weekly for now
  • TODO: Grace to send out doodle re. wednesday availability for requirements or demo session

A general strategic comment: what do people think about updating the squad name from Analytics Squad to Analytics Engine Squad?

  • Clarifies that instead of creating miscellaneous analytics projects, this squad aims to build tooling that will allow implementations to build the analytics they need.
  • Meets our strategic objective as a community of having an Analytics Engine for OpenMRS that runs in parallel to the EMR, which will make reporting much easier for Implementers (asap) and will enable Clinical Decision Support (in the not-too-distant future).
  • Means that this squad will also be addressing the work for integrating this engine with OMRS (both directions) and supporting downstream data science tools.

Do people have any thoughts or concerns with this approach?

@wanyee @burke @dkayiwa @bashir @akimaina @ccwhite23 @mksd @jayasanka @jdick @mseaton @jennifer @tsandifer

1 Like

Oh I missed :smile. Will make sure to join from the next one.