510 likes | 654 Views
IBIS-PH Community of Practice Meeting. Monday , May 23, 2011 1:00 – 3:00 PM EDT ( 11:00 AM – 1:00 PM MDT). Connection Information. 1. Please join the meeting at. https://www2.gotomeeting.com/join/863973810
E N D
IBIS-PH Community of Practice Meeting Monday, May 23, 2011 1:00 – 3:00 PM EDT (11:00 AM – 1:00 PM MDT) National IBIS-PH Community of Practice
Connection Information • 1. Please join the meeting at. https://www2.gotomeeting.com/join/863973810 • 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. • Dial +1 (512) 400-4969 Access Code: 863-973-810 Audio PIN: Shown after joining the meeting • Meeting ID: 863-973-810 National IBIS-PH Community of Practice
Agenda for Today’s Call • Introductions • Brief discussion on the need for coordination/governance. • Review list of version2 enhancements (quickly!) • Review list of potential new enhancements • Discussion of prioritization process • Who will have support agreements in place next year to support Garth’s efforts? • How do we coordinate with individual states’ enhancement efforts (e.g., MA & WEAVE) • STG/Garth’s ability to track efforts for individual states. Should we have a 60/40 rule, where 60% of the support agreement amount goes toward enhancements that are community priorities and 40% is for efforts completed for individual states? • Next steps: • What decisions were made during the call? • What decisions need to be made soon? • Review of action items assigned during the call. National IBIS-PH Community of Practice
Coordination/Governance • None of us is remunerated for it, but we all benefit from it. • UT/NM have taken the lead. So far we’ve footed the IBIS development bill and made all the decisions. • We’re a community for a reason – strength in numbers, input from multiple stakeholders makes for a more useful/robust software application. National IBIS-PH Community of Practice
Critical Definitions • View Application • Creates all the interface pages. This is what a user “sees” when they go to an IBIS website. • Admin Application • Web interface allows DOH staff to create/ update/ modify their IBIS indicator reports. NOT a query system. Indicator reports are relatively static. • Admin Database • Stores indicator page content and security settings/logins, etc. • IBIS-Q Application (a.k.a. hi_iq_func.exe) • Information broker between View and SAS. Sole purpose is to write SAS program based on user criteria, submit program to SAS, retrieve data from SAS, format data to xml for IBIS View to display. National IBIS-PH Community of Practice
National IBIS-PH Community of Practice IBIS View Pages NJ Home Page MO Query Builder Page
National IBIS-PH Community of Practice IBIS AdminApplication NM Admin Interface Page UT Indicator Report Page (from View app)
National IBIS-PH Community of Practice IBIS-PH Admin Database Supports both Indicator page content (text and numeric/graph data points) Indicator Indicator View Indicator View Values Graph Category Graph Series Related Indicators Data Sources Org_Units Etc. AND Security tables: User Authority User to authority Role User to role Role to authority
New Mexico’s Architecture (example) National IBIS-PH Community of Practice
Version 2 Enhancements – Completed Enhancements from V1.8.0.1 to 2.0 National IBIS-PH Community of Practice
Version 2 Enhancements • What do we mean by Version 2? • Version 1.8.0.1 (View app numbering system) was the last officially released version • Version 2 is found on the CoP repository, here: • http://www.ibisph.org/trac/browser/trunk/src/main/webapps/ibisph-view • New Mexico is running V2.n in production. • Utah is installing it. • All new adopters will want to use it. National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH Admin Application • Completely rewritten to conform to the same programming standards as the newer IBIS-View application (Spring framework) • Secure login page was developed and integrated with the Admin DB to control access to indicator DB records for Indicator report developers AND to allow login and password protection of sensitive data in any IBIS Webpage (URL-based). • Excel cut and paste - from Excel spreadsheet directly into the Admin data entry page (has made users very happy) • Controllers were written to use/display/publish the new indicator report DB fields in published IBIS indicator xml files. • Indicator reports may use any static image in an indicator report page National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH Admin Application • Completely rewritten to conform to the same programming standards as the newer IBIS-View application (Spring framework) • Secure login page was developed and integrated with the Admin DB to control access to indicator DB records for Indicator report developers AND to allow login and password protection of sensitive data in any IBIS Webpage (URL-based). • Excel cut and paste - from Excel spreadsheet directly into the Admin data entry page (has made users very happy) • Controllers were written to use/display/publish the new indicator report DB fields in published IBIS indicator xml files. • Indicator reports may use any static image in an indicator report page National IBIS-PH Community of Practice
IBIS-PH Admin Login Page and Security System National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH Admin Application • Completely rewritten to conform to the same programming standards as the newer IBIS-View application (Spring framework) • Secure login page was developed and integrated with the Admin DB to control access to indicator DB records for Indicator report developers AND to allow login and password protection of sensitive data in any IBIS Webpage (URL-based). • Excel cut and paste - from Excel spreadsheet directly into the Admin data entry page (has made users very happy) • Controllers were written to use/display/publish the new indicator report DB fields in published IBIS indicator xml files. • Indicator reports may use any static image in an indicator report page National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH Admin Database • New DB tables to support role-based security for IBIS and EPHT programs. This allowed us to lock down our IBIS-Admin application so only authorized DOH staff are able to modify IBIS indicator pages. It will also support secure query modules. This will be used by both general IBIS queries (e.g., secure queries that allow identification of American Indian tribes) and EPHT queries (e.g., ability to drill down to small numbers without cell suppression). • DB tables to support the new community reports. We isolated the measurement period so we can use that information in multiple places (previously the date information was buried in the graph subtitle). New fields were added to allow the gauge images to correctly indicate "good" versus "poor" community values compared to the state (is a high value good or bad?) • Fields were added for graph and supplemental image narratives. National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH View Application • General (security, stylesheets, charting, etc.) • View security hooked into Admin DB. The View application is now able to secure URLs behind a login and password. • A “proxy” pass-through application was written for IBIS-View for IBIS sites that do not use a proxy server. This will allow NM to put the View application behind their firewall if they’d like to. AS I understand it, this was more difficult than Garth had anticipated, and it is not ready for prime time. • A publishing mechanism was programmed, to create a .WAR file to allow for simpler IBIS View deployments (for content updates, not for application build/installation process). • Site-Specific stylesheet changes. This will make it easier to make site-specific mods to the xslts and have them persist after updating to a new version of the application. National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH View Application • General (security, stylesheets, charting, etc.) • View security hooked into Admin DB. The View application is now able to secure URLs behind a login and password. • A “proxy” pass-through application was written for IBIS-View for IBIS sites that do not use a proxy server. This will allow NM to put the View application behind their firewall if they’d like to. As I understand it, this was more difficult than Garth had anticipated, and it is not ready for prime time. • A publishing mechanism was programmed, to create a .WAR file to allow for simpler IBIS View deployments (for content updates, not for application build/installation process). • Site-Specific stylesheet changes. This will make it easier to make site-specific mods to the xslts and have them persist after updating to a new version of the application (needed for easier application version updates). National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH View Application • Indicator Reports • A confidence interval display “toggle-button” was programmed. Users may toggle the confidence interval (Y error bars) off and on for every graph in indicator reports and on query results pages National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH View Application • Community Reports • New Community Health Highlights reports allow a community to view a set of published indicators for their own community. This effort included programming a new version of the graphic, logic that allows the appropriate gauge graphic to appear dynamically, based on community data, and other features • Reformat the Community Snapshot reports to clean them up. • Program printer-friendly versions of the above community reports. (Still needs work - too much white space, plus, I think I have blown it up in NM with too many pages.) National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH View Application • Community Reports • Community Health Highlights reports allow a community to view a set of published indicators for their own community. This effort included programming a new version of the graphic, logic that allows the appropriate gauge graphic to appear dynamically, based on community data, and other features • Reformat the Community Snapshot reports to clean them up. • Program printer-friendly versions of the above community reports. (Still needs work - too much white space, plus, I think I have blown it up in NM with too many pages.) National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH View Application • Community Reports • Community Health Highlights reports allow a community to view a set of published indicators for their own community. This effort included programming a new version of the graphic, logic that allows the appropriate gauge graphic to appear dynamically, based on community data, and other features • Reformat the Community Snapshot reports to clean them up. • Program printer-friendly versions of the above community reports. (Not completed - Still needs work - too much white space, plus, I think I have blown it up in NM with too many pages.) National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-PH View Application • Graphs • J-Free charts was added to the software as an option for adopters to use. But this code has not been fully implemented - none of us has seen them. National IBIS-PH Community of Practice
Version 2 Enhancements • IBIS-Q Application (a.k.a. hi_iq_func.exe) • Cell suppression refinement • Capability was programmed to allow adopters to specify which variables should be suppressed in the results table when a suppression rule gets tripped. • Option to use data stability/reliability as an option for cell suppression (UT uses the RSE/CV option). National IBIS-PH Community of Practice
Version 2.x and Beyond: Priorities for Future Enhancements National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • General (security, stylesheets, charting, etc.) • Build/install process • File repository: Need to make decisions on whether to continue to use Utah's - how will the community use it? • Hot links and formatting on indicator report and query result pages. (Ticket #52) • DOCUMENTATION, DOCUMENTATION, DOCUMENTATION • Data-driven news and updates sections. (Ticket #23) • Proactive View security (i.e., if I want to show user x a list of ONLY what is available to her, and user a list of ONLY what is available to him) we’ll need a special handler that will interact with the Spring stuff, then we’ll need a controller that will bottle stuff up and send it to the user. This is more involved than just a simple controller. National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • Indicator Reports • Maps for indicator reports (see "Maps" section, below...) • Capacity for multiple PHOM reports - not just one for the state. E.g. reports on different topics, datasets, etc. (Ticket #86) • Garth: simplify RELATEDS and INDICATOR_VIEWS within the INDICATOR structure. “What I want to do is only provide the NAME and then open the approp file to get the title info. This will allow templates to be used to determine what to display and not rely on the TITLE values populated by the java code at the time of XML creation.” • Categorized index display, how should it work, where should overviews be stored? National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • Community Snapshot Report • Community snapshot report - could use better graphic displays - more of a real dashboard type look to it. • Community snapshot report - we had talked about providing better user control over the content - wiring it up more like the query interface, where the user could choose from lists of indicators from a menu. Currently they can choose from multiple sets of indicators - but just one set at a time. National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • Community Health Highlights Report • Need to decentralize the identification of indicators for the community snapshot versus the community health highlights reports. Currently, both reports use the same set of indicators. • Community Health Highlights (CHH) reports - graph options. Horizontal bar graph of all communities? Or vertical bar graph of only current community, state, and U.S. • Can we put a target bar or line on the graph? • Table of contents subheadings on BOTH CHH and Snapshot reports (Ticket #105) National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • Community and Indicator Reports • Output to PDF – or much more printer friendly National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • Query Interface • POPULATE_MISSING_DIMENSION_VALUES. These are records that are not in the dataset that View gets from IBIS-Q, but need to be displayed anyway (e.g., display all counties for maps) (Ticket #87) • Fix bypass of "User data use agreement" • Content developer control over whether section elements initially display expanded. • xsltto turn stored <QUERY_APPLICATION_URL> back into query builder page. This would be useful for storing commonly-used queries. (ticket #104) • Sort order for query module dimension file so that we can code “other” as “-999” and it won’t appear at the top of the list (Ticket #108) – and we can make the total appear at the bottom of the table National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • Maps • What to do with the mapping for the query results? Keep SVG? What is the best way to go, now? Open layers? WEAVE? • What to do for maps in the indicator report pages? • Updated series/categories structure to match IBIS-Q (which could handle maps and match module dimensions and could be more useful for community profiles etc). Includes changes to the view system XSLTs and publishing system. National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH View Application • Graphs • Graphics software. J-Free charts? Convert graphs to xslts? • Other graphing issues: • dynamic sorting of bars, • different color for study area bar, • different colors for state and US bars, • state value, perpendicular line for target value • How graphs handle certain displays, including value labels, ** • Control over Y-axis - should it always start at zero? National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH Admin Application • Data driven cat index - pick list of categories for indicator authors/editors to use – to assign their indicator to one or more cat index headings • Publish cat index. There is currently no publish button for the cat index. (May be fixed already?) National IBIS-PH Community of Practice
Potential Future Enhancements • IBIS-PH Admin Application • Cascading delete: Add ability through Admin App to Delete an Indicator (with confirmation). • Add delete record buttons back (Ticket #93) • Dependent views for graph categories, data sources, etc. (Ticket #94) • IP user/editors page (so we don't have to modify editors directly in the DB) • Update the Admin DB to use the IBIS-Q ‘data warehouse ‘type structure. This also helps with 2-d+ type data (e.g., trend graphs for counties) and community profiles as multiple measures are possible. It also helps with using the query system to populate IP views and getting interactive maps into the indicator reports. (Ticket #33) (This is a big effort, but probably worth it.) National IBIS-PH Community of Practice