1 / 10

High-Level Overview

High-Level Overview. 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. IBIS Capabilities.

vernon-rowland
Download Presentation

High-Level Overview

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. High-Level Overview

  2. 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.

  3. 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).

  4. 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).

  5. 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

  6. 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.

  7. What IBIS Is NOT • Free of costs and software licenses • SAS must be licensed. • IBIS professionals at STG must be compensated for their time. • Supported by a large team of developers and tool-free support technicians. • We have one developer and one support person. • We hope to meet needs through the Community of Practice.

  8. IBIS-PH CoP • National Community of Practice (CoP) guides IBIS-PH development. • Individual adopter states contribute to software application maintenance and fund site-specific feature development, customization. • New Mexico get “big bang for buck” because of support from CoP.

  9. Federal Agencies: CDC, NCHS – Hospital Discharge Survey IHS: Nashville Area/USET

  10. Community of Practice Website www.ibisph.org • Source code repository • Web forum • Wiki “How-To” pages

More Related