BioSense 2.0 IntroductionBuilding a Community-Controlled and Shared PH Surveillance Environment<br />Patients Like Me<br /...
Objectives<br />Background<br />BioSense Redesign Goals<br />BioSense 2.0 Shared Environment<br />Key players<br />
Background<br />
History of BioSense<br />Mandated in the Public Health Security and Bioterrorism  (BT) Preparedness and Response Act of 20...
BioSense Redesign Goals<br />
Nationwide and regional situation awareness for all hazards (health-related events beyond bioterrorism)<br />86% of stakeh...
BioSense 2.0 Distributed Environment<br />
Distributed Environment<br />Cloud technology is used to remove the need to physically manage storage locally, and also pr...
Distributed Data Sharing<br />Co-locating data enables state and local authorities to share data with cooperating regions ...
Distributed Analytics<br />Common analysis tools are shared across the community of PHAs<br />Addition or modification of ...
Value Add<br />Meaningful-Use ready environment<br />New capabilities developed by users can be promoted to the system lev...
Collaborative Space<br />
Collaborative Space: ILI Example<br />
Collaborative Space: ILI Example<br />
Collaborative Space: ILI Example<br />
Collaborative Space: ILI Example<br />
Collaborative Space: ILI Example<br />
Collaborative Space: ILI Example<br />
Collaborative Space: ILI Example<br />
Key players<br />
Selected Stakeholders<br />
Thank You!<br />BioSense Redesign<br />http://biosenseredesign.orgbiosense.redesign2010@gmail.com<br />Any views or opinio...
Upcoming SlideShare
Loading in...5
×

BioSense 2.0

1,122

Published on

Published in: Health & Medicine, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,122
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • As mandated in the Public Health Security and Bioterrorism Preparedness and Response Act of 2002 in response to the September 11 and anthrax attacks, CDC’s BioSense program was launched in 2003 with the aim of establishing an “integrated system” of nationwide “biosurveillance” for early detection and prompt assessment of potential bioterrorism-related illness.
  • General BioSense ModelHow will data flow into and within the new environment?
  • New leadership within the BioSense Program has spurred the development of an updated vision for the Program - to contribute to nationwide and regional situation awareness for all hazards health-related events and to support national, state, and local responses to those events.
  • Using the cloud for both data storage and processing is at a tiny tiny fraction of the cost of hosting your own serversYou’re already in the cloud: You use GPS, you monitor the weather – all these are cloud-based services offered to anyone who wishes to use themUsing the cloud offers a COLA model, Compose Once Leverage Anywhere – you only have to create the service one time but it can be used indefinitely
  • One example of these services is data sharing. We will offer this service in the cloud to enable cross-jurisdictional sharing of information in controlled and secured fashion. You control who you share the information with, for what period of time, how long, what granularity you choose to (row-level or aggregate or maps or trends), what format (raw or analyzed)
  • We are offering an open market for analytics tools. We invite collaborators to contribute their tools in the environment as well as challenge grants to help advance the PH practice by practitioners, academics, and hopefully from other disciplines. HDs can also have their own tools if they so choose to and have the expertise to develop these tools and promote their utility to others in the community of practice. Tools or algorithms can be vetted and evaluated by their utility – or lack of.
  • ASTHO working collaboratively over the past 3 months, have been able to narrow down the potential cloud vendors to 3. They have a very strict criteria about the environment, security and privacy are weighted the top in their selection.We’re not only depending on the vendor to make sure security is enforced. We are working with a 3rd trusted party that will constantly be challenging our assumptions and those of the environment. One method includes a penetration test which evaluates the security of a computer system or network by simulating an attack from a malicious source. The process involves an active analysis of the system for any potential vulnerabilities that could result from poor or improper system configuration, both known and unknown hardware or software flaws, or operational weaknesses in process or technical countermeasures.This environment will be Meaningful Use ready based on the ISDS recommendations and the final guide which will be published toward the end of September.
  • The new environment will have shared governance under ASTHOAt a very high level there are 3 Major parts to the new environment-A catcher’s mittVisualization and analysis tools: we hope for this to be an open marketShared spaceCatcher’s Mitt Picture source: http://goo.gl/VdIzJ Google logos: http://goo.gl/kroKmCollaboration: http://goo.gl/gyBfZ
  • Chief Complaint: Influenza: influenza, flu, flulike (visits for influenza inoculation are excluded)fever and cough fever and upper respiratory infection (sore throat, cold, epiglottitis, pharyngitis, nasal congestion, tonsillitis) ICD-9-CM codes for an individual visit in the following combination: Influenza: 487.xFever: 780.6 Cough: 786.2URI: (acute nasopharyngitis [common cold]) 461.x (acute sinusitis) (acute pharyngitis) (acute tonsillitis) 464.x (acute laryngitis and tracheitis) 465.x (acute upper respiratory infections of multiple or unspecified sites)
  • Roles and Responsibilities
  • We’re engaging stakeholders in the requirements and design processes, which also helps us to promote user acceptance of the redesigned system, help address needs and limitations of sites, focus our funding effort, etc. We’re grateful to CSTE’s help putting this webinar today to reach out to you. CSTE will also lend us a hand in the redesign to reach out to HDs to join BioSense 2.0 by signing the proper Data use and share agreement under ASTHO.
  • BioSense 2.0

    1. 1. BioSense 2.0 IntroductionBuilding a Community-Controlled and Shared PH Surveillance Environment<br />Patients Like Me<br />Friday, September9th, from 11:30-1pm<br />Taha A. Kass-Hout, MD, MS<br />Deputy Director for Information Science and BioSense Program Manager<br />Division of Notifiable Diseases and Healthcare Information (DNDHI, Proposed)<br />Public Health Surveillance Program Office (PHSPO)Office of Surveillance, Epidemiology, and Laboratory Services (OSELS)<br />Centers for Disease Control & Prevention (CDC)<br />Any views or opinions expressed here do not necessarily represent the views of the CDC, HHS, or any other entity of the United States government. Furthermore, the use of any product names, trade names, images, or commercial sources is for identification purposes only, and does not imply endorsement or government sanction by the U.S. Department of Health and Human Services. <br />Office of Surveillance, Epidemiology, and Laboratory Services<br />Public Health Surveillance Program Office<br />
    2. 2. Objectives<br />Background<br />BioSense Redesign Goals<br />BioSense 2.0 Shared Environment<br />Key players<br />
    3. 3. Background<br />
    4. 4. History of BioSense<br />Mandated in the Public Health Security and Bioterrorism (BT) Preparedness and Response Act of 2002<br />Nationwide “integrated system” for early detection and assessment of potential BT-related illness<br />Funding provided by Congress to CDC in 2003<br />Development of BioSense infrastructure started in 2003<br />Initially focused on collecting timely data directly from civilian hospital clinical information systems, VA and DoD<br />In 2004, BioSense began recruiting hospitals to provide in-depth clinical data directly to CDC<br />In 2006, BioSense started soliciting more limited data from health departments that had already established automated systems for ED-based syndromic surveillance<br />
    5. 5. BioSense Redesign Goals<br />
    6. 6. Nationwide and regional situation awareness for all hazards (health-related events beyond bioterrorism)<br />86% of stakeholders feel that there is value in viewing a regional or national view to achieve public health situation awareness<br />Support national, state, and local responses to those events <br />Multiple uses to support your public health situation awareness; routine public health practice; and improved health outcomes and population and public health<br />BioSense Redesign Goals<br />
    7. 7. BioSense 2.0 Distributed Environment<br />
    8. 8. Distributed Environment<br />Cloud technology is used to remove the need to physically manage storage locally, and also provide economies of scale<br />States and Local Health Departments can elect to use the hardware, software, databases, and services within the enterprise and save cost while increasing capabilities<br />Savings are realized by accessing low cost computing resources that do not require high up-front capital layout, ongoing recapitalization costs, or full-time computer administration personnel at each site<br />Services and software are available and are proven, tested and available to all members of the enterprise<br />
    9. 9. Distributed Data Sharing<br />Co-locating data enables state and local authorities to share data with cooperating regions and jurisdictions by granting and receiving access data in the enterprise<br />A common simple method of sharing and protecting data is provided by the enterprise<br />Public Health Agencies (PHAs) are able to access data to which they are authorized and use system provided analysis tools (charts, tables, algorithms) in a consistent fashion<br />Consistent tools and services makes analyzing and visualizing data common within the enterprise<br />
    10. 10. Distributed Analytics<br />Common analysis tools are shared across the community of PHAs<br />Addition or modification of system provided analysis tools is done quickly and easily<br />Partners in the enterprise will experience higher quality services and data because of the common nature of the tools.<br />Improvements or fixes to tools and services are automatically available to all members of the enterprise.<br />Algorithms, tools, and capabilities developed by users can be promoted to the system level and shared<br />Enterprise users can develop their own tools and services<br />
    11. 11. Value Add<br />Meaningful-Use ready environment<br />New capabilities developed by users can be promoted to the system level so that they will benefit all members of the enterprise<br />Users are able to download data for which they are authorized for their own use<br />All data that the user is approved to see can be easily downloaded from the enterprise database to their local machine for independent analysis and use in locally owned tools and software<br />
    12. 12.
    13. 13. Collaborative Space<br />
    14. 14. Collaborative Space: ILI Example<br />
    15. 15. Collaborative Space: ILI Example<br />
    16. 16. Collaborative Space: ILI Example<br />
    17. 17. Collaborative Space: ILI Example<br />
    18. 18. Collaborative Space: ILI Example<br />
    19. 19. Collaborative Space: ILI Example<br />
    20. 20. Collaborative Space: ILI Example<br />
    21. 21. Key players<br />
    22. 22. Selected Stakeholders<br />
    23. 23. Thank You!<br />BioSense Redesign<br />http://biosenseredesign.orgbiosense.redesign2010@gmail.com<br />Any views or opinions expressed here do not necessarily represent the views of the CDC, HHS, or any other entity of the United States government. Furthermore, the use of any product names, trade names, images, or commercial sources is for identification purposes only, and does not imply endorsement or government sanction by the U.S. Department of Health and Human Services. <br />

    ×