1 / 60

New Mexico IBIS Training

New Mexico IBIS Training. Lois M. Haggard, PhD Tong Zheng, MS Utah Department of Health. Some of the Key Utah IBIS Players. Lois Haggard – Director of the Office of Public Health Assessment, IBIS Project and Product Manager

murphye
Télécharger la présentation

New Mexico IBIS Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New Mexico IBIS Training Lois M. Haggard, PhD Tong Zheng, MS Utah Department of Health

  2. Some of the Key Utah IBIS Players • Lois Haggard – Director of the Office of Public Health Assessment, IBIS Project and Product Manager • Tong Zheng – Senior SAS programmer and data analyst, manager for Utah’s IBIS-Q implementation. Develops and maintains most of Utah’s SAS code and XML module files. • Zhiwei Liu – Senior SAS and C++ programmer. Developed IBIS-Q backend. Working on UDOH Web-based query solutions since 1994. • Garth Braithwaite – Web designer, Java programmer, database & XML designer, and XSLT programmer for the IBIS-View and Admin system.

  3. IBIS Goals • Dissemination of public health data via the Web. • Able to evolve as needs and technology change. • Minimal software licensing cost. • Minimal software developer expertise and reliance. • Distributed data workload and ownership.

  4. Goals of Visit • Provide realistic overview • Show the IBIS capabilities • IBIS is not a silver bullet • IBIS does provide benefits but requires effort and resources • Provide training and a basic understanding for the query portion of the IBIS system using New Mexico’s Birth Certificate data as an example.

  5. IBIS Capabilities • Displays general static web site content with a consistent look and feel without having to code the entire web page. • Displays Indicator Reports (aggregated data values with associated contextual data). • Provides Web-based interface for distributed maintenance of Indicator Profile data. • Provides realtime SAS dataset queries. • Allows DOH to define the query interfaces without having to know the Web technologies (HTML, CSS, Javascript).

  6. What IBIS Is • Set of evolving open-source, license-free applications based on the Web’s request/response paradigm that runs on virtually all modern-day hardware and operating systems. • Culmination of 14 years of experience and knowledge from hundreds of health data analysts and users. • Simple in design, complex in details. The applications are data-driven using loosely-coupled interfaces which makes for a fairly agile system able to be extended as needed. • A lot of work (getting it to where it is today, and for an agency to implement).

  7. What IBIS Is NOT • Canned, plug-in appliance type application. • Applications need to be “hand” installed and maintained with TLC. • Effortless. • IT Support • IBIS Champion • Committed data stewards • SAS analysts • Some Web programming skills

  8. What IBIS Is NOT • Silver Bullet • IBIS applications have advantages, but for every design decision there are trade-offs. • All systems will meet resistance somewhere, none will meet all users’ needs. • All systems will, however, require effort to implement. Different systems require different types of effort.

  9. What IBIS Is NOT • Free of software licenses • SAS must be licensed. • Supported by a large team of developers and tool-free support technicians. • We hope to meet needs through the Community of Practice.

  10. The IBIS Community of Practice Lois M. Haggard, PhD Utah Department of Health

  11. Purpose • Our purpose with this section is introduce the notion of a Community of Practice for those of use using the IBIS-PH software.

  12. Problem • Software is expensive to develop. The industry changes so quickly. Utah cannot maintain IBIS into the future without the generous federal funding we have been so fortunate to have received.

  13. Proposed Solution • Systems that were supported by federal $$ are essentially “open source,” although not technically part of the Open Source Initiative.

  14. Partial Definition of Open Source: • Free Redistribution No royalties or fees • Source Code Must include source code • Derived Works Allow modifications, derived works, and distribution of such • . . . From Open Source Initiative website: http://www.opensource.org/docs/definition.php

  15. NCHS

  16. Community of Practice • “The current environment for organizations is one that is characterized by uncertainty and continuous change. This rapid and dynamic pace of change is forcing organizations that were accustomed to structure and routine to become ones that must improvise solutions quickly and correctly… Knowledge Networks: Innovation through Communities of Practice. Paul Hildreth and Chris Kimble (Eds.) (2004) <http://www.cs.york.ac.uk/mis/knicop.html>

  17. Community of Practice • “…To respond to this changed environment organizations are moving away from the structures of the past that are based on hierarchies, discrete groups and teams and moving towards those based on more fluid and emergent organizational forms such as networks and communities.”

  18. Community of Practice • How does it function? • People become members of a CoP through shared practices; they are linked to each other through their involvement in certain common activities. It is mutual engagement that binds members of a CoP together as a social entity (Wenger, 1998).

  19. Community of Practice • Common Purpose / Motivation • The CoP members will have some sort of common goal or common purpose and it is often the case that the CoP is internally motivated i.e. driven by the members themselves as opposed to some external driver.

  20. Community of Practice • Relationships • Relationships are a key part of a CoP and is what makes it possible for a team to become a CoP - as the informal relationships develop the source of legitimation in the group shifts in emphasis. These relationships are key to the issues of trust and identity in a CoP.

  21. Community of Practice • Formal or Informal? • In many cases, a CoP is not a formally constituted group and membership is entirely voluntary. In some cases, the organization might not even be aware of its existence.

  22. Community of Practice • What is produced? • The members of a CoP build up an agreed set of communal resources over time. This "shared repertoire" of resources represents the material traces of the community. Written files can constitute a more explicit aspect of this common repository although more intangible aspects such as procedures, policies, and specific idioms may also be included (Wenger, 1998).

  23. IBIS Community of Practice • Maintain source code (use staff talent or share contractual talent) • Develop features, functionality • Share ideas, developments • Provide mutual technical assistance

  24. Benefits • Share strength, development resources • E.g., Average .5 FTE in each of 18 states: 9 FTEs working on developing and maintaining the software. • Share ideas for use, training • Provide mutual technical support

  25. Community of Practice Website www.ibisph.org • Source code repository • Web forum

  26. What’s In It for New Mexico? • Health programs, policy-makers, community members gain greater data insight (evidence-based decision-making). • Analysts are freed of some tedious data reporting tasks. • Leverage Utah’s 14 years of development. • Little out-of-pocket software and hardware costs for enterprise class applications. • Can deploy additional system features over time.

  27. What’s In It for Utah? • IBIS will benefit from additional perspectives, knowledge and experience. • After 2007, Utah will not be able to afford a full-time, dedicated developer. As IBIS is open source, it is hoped that others will enhance and share their enhancements with the community, thus allowing the applications to continue to evolve – which benefits everyone.

  28. Purpose • Our purpose with this section is to provide a brief but thorough overview of the IBIS system, from an end user’s point of view. • In other words, what can IBIS offer to your organization and constituents?

  29. Overview of IBIS-PH Lois M. Haggard, PhD Utah Department of Health

  30. http://ibis.health.utah.gov Utah’s IBIS-PH homepage provides access to all areas of the website and information on new features. This is a standard home page template, but states adopting IBIS can either modify the content only, or the whole page.

  31. IBIS Information Dissemination Model: Most frequently-asked questions are answered in paper (.pdf) publications and in our Indicator Profile reports. Users who’d like more detailed analysis or sub-populations can use the interactive query system. If none of those systems answer their question, they must go to the “old” system of calling us on the phone.

  32. web <html> <head> <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title> IBIS-PH Welcome to IBIS-PH; Utah's Public Health Data Resource</title> . . . …sends request (URL)… Client / Internet User… … to Web server. …sends response (HTML)… …to Client / Internet User. Web server Web Basics http://ibis.health.utah.gov

  33. IBIS Indicator Reports System html IBIS-Admin IBIS-View IBIS-Q

  34. Custom Data Query • Allows users to query health data sets directly • General audience • User-friendly GUI interface • Sound epidemiology • Help descriptions & instructions • Bullet-proof – can’t confuse or give misleading answers, can’t allow users to do “stupid” things The IBIS Query system allows members of the general public to access several public health data sets and generate query results based on their specifications.

  35. 1. Select a dataset.

  36. 2. Select a measure.

  37. 3. Use “QueryBuilder” page to select query parameters and submit query.

  38. html IBIS-Q Custom Query System IBIS-Admin IBIS-View IBIS-Q

  39. Results include query filter criteria, a data table...

  40. And query meta-data.

  41. The user can also produce a graph of the data in the table.

  42. The IBIS query system can also produce map views of data. Maps provide mouse-over information and zooming if the user has Adobe’s SVG viewer installed.

  43. html html html html IBIS-Q Custom Query System IBIS-Admin IBIS-View IBIS-Q

  44. IBIS Indicator Reports • Allows users to view a report of data that have already been tabulated. • For more novice users, easier, more user-friendly. • Webpage CONTENT MANAGEMENT system, not a query system.

  45. Utah has 140 indicator profiles currently published. They are indexed in an alphabetical index (pictured here) and also in a categorical index that allows indicators to be placed in any of several categorization schemes, such as by program, by data source, or HP2010 focus area, etc.

  46. Each indicator has a default graph that comes up on the indicator main page and a message on why it is an important construct in public health.

  47. The main page also allows navigation to a table of numbers for the current graph, as well as access to additional graphs (if they exist). We also include the measure definition.

  48. Numerator* Denominator* Important facts about each measure include a number of fields. Not all fields are mandatory – mandatory fields are shown here with an asterisk. Definition* Data Interpretation Issues Why Is This Important?* Other Objectives How Are We Doing? Utah Versus U.S. What Is Being Done? Other Program Information HP 2010 Objectives*

  49. The IBIS indicator profiles allow users to see how the current measure might be related to other measures.

More Related