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.


Monday, Feb 22, 2021 - 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#‬


  1. Review agenda and add items as needed...
  2. NM migration progress report (Lois and Paul)
    • nmibis-admin
    • nmibis-view
    • Query Modules.
  3. Had to rename IP "Technical Notes" back to "Data Issues".
  4. Interest in meeting(s) to discuss future priorities.
  5. Interest in meeting(s) to Walk through the version 3 apps.
  6. Funding Review. Who is wanting to adopt v3 and when? What features are wanted (initiatives, side by side maps, auto update etc. - see list below)?


  1. Review 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.
  2. Use of conditional includes for sections and dimensions - not using "exclude" in query module.xml to achieve these conditional includes.
    • Exclude will remain for selections only.
    • Include subset of maps and/or customized maps for query modules using localized map definition list (map.xml) file.
  3. Determine how best to deal with chart, map, and grids. Discussion needs to include:
    • Centralized file that contains all (likely large and very confusing for admin editors),
    • Admin app having a general list for users to select from in query and view with ability to enter custom name for the actual view,
    • QMs to include certain chart defs or use the CHART_NAME
  4. Updating the QM fields to make consist with IP datasets.
  5. How you can use saved queries for creating "system" type queries (even if you don't want end user saved queries on your site).
  6. Other advanced usages where IBIS data visualizations can be pulled into other websites and/or into static story pages.
  7. What is possible and how to use other non IBIS data visualization usages within an indicator view.
  8. Follow up meetings for future Version 3.x priorities? Includes:
    • Enhancement Tickets
    • 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 2030).


  • Help Needed. We need help to write appropriate help popup copy and with training videos (see 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?
  • Adopter migration schedule.
  • ICD-10 CM - updates?
  • Discuss the need for web content development. How busy are you? If enough interest we can likely get resource(s) to help cleanup / scrutinize pages. Included in this effort are:
    • Taking inventory of static pages and navigation.
    • How much are these content pages being hit?
    • Why are pages being hit and why they might not be being accessed. Are low hits because it's not needed or because it's not engaging and/or providing any value to the user?
    • Heavily scrutinize page value; 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 ie which pages are simply a required page and we really don't care about usefulness?
    • Can/which 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.
  • All adopters should routinely run a website link checker to verify that their pages do not have broken links. If dead or broken links are found they should be fixed or removed from the page. You should check with your IT group to determine their preferred tool. While not inclusive of your site the W3C's single page validator still provides some basic info that will test your basic menu and footer links
  • Adopter support status and priorities (Paul/adopters).
  • Development Schedule.
  • Review open tickets (Lead by Host, presented by the ticket's author).
  • Discuss related public health websites and/or other related websites/techniques/tools.
  • Short term and long term direction and coordination of funding.


  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)



  • 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.)
Last modified 4 months ago Last modified on 01/27/21 12:44:36