wiki:CoPCallAgenda

Version 354 (modified by GarthBraithwaite_STG, 5 weeks ago) (diff)

--

CoP Call Agenda

IBIS-PH is website software that allows public health practitioners access to publicly-owned health data. The IBIS-PH Community of Practice (CoP) is the stakeholder group for the software. Monthly CoP conference calls allow CoP members to communicate with each other and the IBIS-PH contractors who provide software development and support.


CONFERENCE CALL

Monday, August 24, 2020 - 3:00 to 5:00 EST (1:00 to 3:00 PM MST) NM/NJ Hosting.

Dial-in: (‪US‬) ‪+1 (646) 749-3112‬ - Meeting ID/Access Code: 973-631-485#‬


AGENDA ITEMS

  1. Review agenda and add items as needed...
  2. ICD-10 CM - updates?
  3. v3.0 Updates:
    • Saved Query and Self Registered User UI demo.
    • Discuss, and demo, how you can use saved queries for creating "system" type queries (even if you don't want end user saved queries on your site). We can show Lois's COVID pages as one example for using saved queries.
    • Apply query demo. Technical notes when enabled:
      • To turn on no login is needed,
      • Only applied when a new module is loaded from the query/result or query/builder request (so by design is NOT applied to saved queries),
      • Only supplements default values - does not override and replace,
      • Only is able to set values that 100% match the dimension name and value (refer back to this when we discuss the query module cleanup effort below).
    • Review kendo charts and grid. This includes interaction between chart and grid, grid export, copy and paste, grouping, drag and drop columns, column options in general, how the admin app and charts.xml file works, adding custom chart definitions for a query module's default chart, and anything else you'd like to know about.
  4. NM migration progress report (need to discuss effort and time needed dealing with converting content and cleaning up content).
    • nmibis-admin
    • nmibis-view
    • Query Modules.
      • Discuss the minimum effort of migration.
        • MEASURE => MEASURE_NAME,
        • DATA_SOURCE => DATA_SOURCE_NAME,
        • ANCILLARY_VALUEs - if you want confidence limits etc you'll need to implement ANCILLARY_VALUE entries,
        • DIMENSION_VALUEs SORT_ORDER - your dimension values will likely need a SORT_ORDER for data to display in the exact order you want them.
      • All the other effort (which is likely large) is cleanup needed for future integration of IP datasets and QM datasets and for new functionality.
  5. Help Needed. We need help to write appropriate help popup copy and with training videos (see http://ibis.hhdw.org/ibisph-view/ for an example). This includes:
    • Defining the various users.
    • What each of those users would be interested in and what will be their issues with using the site.
    • Videos that help you, the adopter, understand things better.
    • What buttons or page content sections need help popups.
    • What should be the main leading content for those help popups.
    • Should their be more technical definitions that follow the main help content?
  6. Interest in reviewing centralized, decentralized, hybrid query module XML files. This meeting would be a working meeting that walks through the different use cases, and the pros and cons of each.
  7. Interest in reviewing and setting up followup meetings for future Version 3.x priorities? Things like:
    • What is the query to indicator auto update feature and how it should work. There are several use cases like admin based where a user presses a button to run a saved query to update the indicator dataset values. Another is to define an indicator dataset and a link to a saved query definition. This then has questions about caching etc.
    • Side by side maps.
    • Heat map layers to capture different results on a single map.
    • New user interface to allow users ability to control map choropleths, charts, and exporting data.
    • New user interface to allow users the ability define their own indicator reports and save those definitions.
    • User defined comparisons (ie sets of indicators, peer groups etc.).
    • Initiatives (new HP 2020).
  8. Adopter migration schedule.

STANDING AGENDA ITEMS

  • Discuss the need for web content development. Version 3 adopters need to take inventory of their static pages. These pages should be heavily scrutinized with considerations like the value of the page, how much is it being used, why is it not being used, resources needed to make it useful, resources needed to maintain, and website requirements.
  • How much are these content pages being hit?
  • Are low hits because it's not needed or because it's not engaging and/or providing any value to the user?
  • Which pages are simply a required page and we really don't care about usefulness?
  • How busy are most adopters with simply dealing with the data portion of IBIS and their other duties?
  • Can most content pages can be cleaned up once with little maintenance there after?
  • What resources are available? This includes interns, others within the department or state IT, or outsourcing.
  • What can STG help with? STG can provide the technical assistance on how to implement design. STG can also help with usability design, graphic creation if needed, and review.

PARKING LOT - OLD, NOT-TOO-ACTIVE AGENDA ITEMS

  1. Introduction and Training Videos Status Update
    • 4-video playlist for new adopters Describes types of IBIS-PH content and how it's maintained. (Lois)
    • Adding an area labels layer to your map, editing GeoJSON in QGIS (Chris Wenker)
    • Modifying an IBIS map definition - choropleth groups and colors, adding new map definitions (Lois Haggard, Paul Leo)
    • Creating Dynamic Grouping Variables for an IBIS Query (Tong Zheng)
    • Wiki Formatting - When, Where and How It's Used in IBIS-View (Kim Neerings)
    • The Subversion (SVN) file repository - basics (Lois Haggard, Paul Leo)
  2. IBISQ Testing (Lois, Paul, Tong)

IF TIME & INTEREST or FUTURE AGENDA ITEMS


ALL COP MEMBERS: PLEASE BE PREPARED TO DISCUSS YOUR TICKETS.

  • When you submit a ticket, leave the Milestone=Unassigned and Version=Unknown and the ticket will come up on ticket report number 1 New Tickets for CoP Review
  • If you have new or open tickets please review them and be prepared to discuss them on the CoP call. You can run the {1} New Tickets for CoP Review report to see current tickets. The purposes of discussing tickets are to a) communicate an idea to the community, and b) to identify and track IBIS-PH software issues. (Note that once a ticket has been marked to be worked then that ticket is only discussed on the CoP call for the purpose of moving the effort forward.)