BioSense Program Going Forward: HIMSS10 Conference


Published on

As mandated in the Public Health Security and Bioterrorism Preparedness and Response Act of 2002, CDC’s BioSense program was launched in 2003 with the aim of establishing an integrated system of nationwide public health surveillance for the early detection and prompt assessment of potential bioterrorism-related illness. Over the following several years, as awareness grew about the limits of syndromic and related automated surveillance systems, including BioSense, in providing early and accurate epidemic alerts, increased emphasis was placed on their use in providing timely situation awareness throughout the course of public health emergencies. In practice, a key application of these systems has been their use in tracking the course of seasonal influenza and, in 2009, the impact of the H1N1 influenza pandemic. While retaining the original purpose of BioSense of early event (or threat) detection and characterization, we believe the most efficient and effective approach to achieve the program’s long-term business case is to build on existing systems and programs. This will have additional public health benefits that can improve the nation’s health at all times, including: 1. Public health situation awareness, 2. Routine public health practice, 3. Improving health outcomes and public health; and 4. Monitoring healthcare quality

Published in: Health & Medicine, Technology
  • Be the first to comment

  • Be the first to like this

BioSense Program Going Forward: HIMSS10 Conference

  1. 1. BioSense Program: Going Forward <ul><li>Taha A. Kass-Hout, MD, MS </li></ul><ul><li>Deputy Director for Information Science (Acting) </li></ul><ul><li>Division of Healthcare Information (DHI) (proposed) </li></ul><ul><li>Public Health Surveillance Program Office (proposed) </li></ul><ul><li>Office of Surveillance, Epidemiology, & Laboratory Services (OSELS) (proposed) </li></ul><ul><li>Centers for Disease Control & Prevention (CDC) </li></ul><ul><li>Thursday March 04, 2010 </li></ul>HIMSS10 Conference Atlanta, GA, USA 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.
  2. 2. Session Objectives <ul><li>Background </li></ul><ul><li>Provide update on BioSense in the past year </li></ul><ul><li>Discuss what we learned from stakeholders </li></ul><ul><ul><li>Provide background on the historical development of the BioSense program </li></ul></ul><ul><ul><li>Review past opportunities for stakeholder and other input </li></ul></ul><ul><ul><li>Discuss what we learned from these opportunities </li></ul></ul><ul><li>Present some options for paving the way forward </li></ul>
  3. 3. History of BioSense <ul><li>Launched in 2003 as a nationwide “integrated system” for early detection and assessment of potential BT-related illness </li></ul><ul><ul><li>VA/DoD clinical info systems automated data feeds— 2005 </li></ul></ul><ul><ul><li>Hospital direct reporting to CDC— Dec 2005 </li></ul></ul><ul><ul><li>State HDs ED-based syndromic surveillance— Dec 2006 </li></ul></ul><ul><ul><li>Additional sources </li></ul></ul><ul><ul><ul><li>Anti-infective prescription data— Oct 2007 </li></ul></ul></ul><ul><ul><ul><li>Laboratory (LabCorp and Quest)— Dec 2007 </li></ul></ul></ul>
  4. 4. BioSense: Facilities (N ≈ 2,000)
  5. 5. BioSense: Pharmacies (N ≈ 27,000)
  6. 6. BioSense: 2009 <ul><li>Tracking Novel A(H1N1) </li></ul><ul><ul><li>Collaboration with ISDS/Distribute and PHII </li></ul></ul><ul><ul><li>Flu Module </li></ul></ul><ul><li>Extramural Research </li></ul><ul><ul><li>Centers of Excellence (CoEs) </li></ul></ul><ul><ul><li>Health Information Exchanges (HIEs) </li></ul></ul><ul><ul><li>Regional Collaboratives </li></ul></ul><ul><ul><li>BioSense Evaluation Cooperative Agreement project </li></ul></ul><ul><li>Research Prototypes </li></ul><ul><ul><li>Geocoded Interoperability Population Summary Exchange (GIPSE) Specification </li></ul></ul><ul><ul><li>NHIN Connect </li></ul></ul>
  7. 7. Collaboration with Distribute <ul><li>BioSense contributes ED data from 9 jurisdictions (303 EDs) </li></ul><ul><ul><li>4 jurisdictions with HDs SS systems </li></ul></ul><ul><ul><li>5 jurisdictions with direct reporting hospitals </li></ul></ul><ul><li>Temperature and Disposition from a subset of reporters </li></ul>
  8. 8. Stakeholder Engagement <ul><li>First BioSense stakeholder meeting— May 2005 </li></ul><ul><li>Information Technology: Federal Agencies Face Challenges in Implementing Initiatives to Improve Public Health Infrastructure, GAO-05-308— Jun 2005 </li></ul><ul><li>BioSense roundtable— Jun 2007 </li></ul><ul><li>Senate Subcommittee on Bioterrorism and Public Health Preparedness— Sep 2007, Mar 2008 </li></ul><ul><li>BioSense roundtable— Nov 2007 </li></ul><ul><li>BioSense roundtable— Apr 2008 </li></ul><ul><li>BioSense strategic plan working group— Aug, Sep 2008 </li></ul><ul><li>Health Information Technology: More Detailed Plans Needed for the Centers for Disease Control and Prevention's Redesigned BioSense Program, GAO-09-100— Nov 20, 2008 </li></ul><ul><ul><li>Further Recommendations for Executive Action— Jul, Sep 2009 </li></ul></ul>
  9. 9. What We’ve Heard <ul><li>Incorporate State and Local public health partner input into the program </li></ul><ul><li>Make use of clinical care or EHR records/ interconnect with Health IT systems </li></ul><ul><li>Promote a proactive, collaborative, and transparent community </li></ul><ul><li>Move towards an open, distributed computing model </li></ul><ul><li>Improve the utility of the data/data sources </li></ul>
  10. 10. BioSense Next Options for your Consideration
  11. 11. <ul><li>Start with updating the purpose of BioSense program objectives </li></ul><ul><ul><li>In-depth review and analysis of findings and recommendations from various GAO reports and stakeholder meetings </li></ul></ul><ul><li>Use a model that </li></ul><ul><ul><li>Accepts inputs (e.g., alerts) from existing surveillance systems </li></ul></ul><ul><ul><li>Reduces processing and collection burden </li></ul></ul><ul><li>Complement and strengthen existing systems </li></ul><ul><li>Keep technology simple and unobtrusive </li></ul><ul><li>Apply agile development to define outcome measures, be more responsive to users’ needs, and control costs </li></ul>BioSense Next: Proposed Strategy Options
  12. 12. BioSense Next: Purpose Options <ul><li>Expand beyond early event detection and provide value in timely data for </li></ul><ul><ul><li>Public health situational awareness </li></ul></ul><ul><ul><li>Routine public health practice </li></ul></ul>
  13. 13. <ul><li>Provide a collaborative environment for all stages of PH preparedness and response activities </li></ul><ul><li>Help improve the effectiveness of the interactions between HDs electronic surveillance systems and human analysts, decision makers and responders </li></ul>BioSense Next: Utility Options
  14. 14. <ul><li>Reduce collection and maintenance of raw clinical data </li></ul><ul><ul><ul><li>De-emphasize direct reporting from hospitals to CDC </li></ul></ul></ul><ul><ul><ul><ul><li>shift flow from hospitals to HDs if desired by jurisdictions </li></ul></ul></ul></ul><ul><ul><ul><ul><li>keep going in a few places as R&D type project to develop strategies for using such data </li></ul></ul></ul></ul><ul><ul><ul><li>Shift towards appropriate national aggregation of data from state/local syndromic systems </li></ul></ul></ul><ul><ul><ul><li>Make existing warehouse open for mining and research (subject to legal, DUA, confidentiality, de-identification, etc.) </li></ul></ul></ul>BioSense Next: Approach Options
  15. 15. BioSense Next: Approach Options <ul><li>Rationale for de-emphasizing direct reporting from hospitals to CDC </li></ul><ul><ul><li>Typical PH reporting structure: Local  State  Federal </li></ul></ul><ul><ul><li>Response happens at jurisdiction level, no need for a federal agency to maintain detailed data </li></ul></ul><ul><ul><li>Jurisdictions own the relationships with hospitals </li></ul></ul><ul><ul><li>Jurisdictions did not receive the detailed data in a timely way from CDC that would have allowed them to take any action </li></ul></ul><ul><ul><li>Jurisdictions make the decision on what level to share their information (aggregate, psuedonimyzed, maps, etc.) </li></ul></ul>
  16. 16. BioSense Next: Approach Options
  17. 17. <ul><li>Provide a common operating picture </li></ul><ul><ul><li>Aggregate national view </li></ul></ul><ul><ul><li>More detailed S&L views and functionalities </li></ul></ul><ul><ul><ul><li>View neighboring localities and departments </li></ul></ul></ul><ul><ul><ul><li>View contextualized alerts and assessments </li></ul></ul></ul>BioSense Next: Approach Options <ul><ul><ul><li>Accept new data sources </li></ul></ul></ul><ul><ul><ul><li>Create an ad-hoc team (e.g., epidemiologists, physicians, nurses, veterinarians, computer scientists, statisticians, water quality specialists, biologists, microbiologists) </li></ul></ul></ul>
  18. 18. <ul><li>Start with the PH community and other experts </li></ul><ul><ul><ul><li>Focus on the business and workflow needs at the local, state, and federal levels </li></ul></ul></ul><ul><ul><ul><li>Let the PH community drive the direction of BioSense </li></ul></ul></ul><ul><ul><ul><li>Create and support communities of interest </li></ul></ul></ul><ul><ul><ul><li>Align the scope of BioSense to best complement and strengthen existing surveillance systems that support emergency preparedness programs </li></ul></ul></ul>BioSense Next: Approach Options
  19. 19. <ul><li>Start with the PH community and other experts </li></ul><ul><ul><ul><li>New charter and governance structure </li></ul></ul></ul><ul><ul><ul><ul><ul><li>CDC and partners at the table, working collaboratively </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Joint steering committee (balanced representation of participants and CDC) </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Develop problem escalation/resolution process </li></ul></ul></ul></ul></ul><ul><ul><ul><li>Requirements and development priorities set by the PH community </li></ul></ul></ul>BioSense Next: Approach Options
  20. 20. <ul><li>Adopt Open Source/Access development when feasible </li></ul><ul><ul><ul><li>Provides maximum transparency to community </li></ul></ul></ul><ul><ul><ul><li>Encourages community to contribute resources and capabilities </li></ul></ul></ul><ul><ul><ul><li>Leverage informatics expertise and innovation from the community </li></ul></ul></ul>BioSense Next: Approach Options
  21. 21. BioSense Next: Approach Options <ul><li>Use an Agile methodology </li></ul><ul><ul><li>Focuses on delivering tangible benefit for the PH community at each step </li></ul></ul><ul><ul><li>PH community defines scope, outcome measures, and creates a reliable benchmark for future cost estimation and prediction for each step </li></ul></ul><ul><ul><li>Allows community input throughout the development timeline– not annually </li></ul></ul>
  22. 22. Are there other options YOU might like to present? BioSense Next: What Are Your Thoughts?
  23. 23. BioSense Next: What Are Your Thoughts? <ul><li>Flesh out options based on feedback from prior stakeholder engagement for your reaction and comments </li></ul><ul><ul><ul><li>Provide communication channels (Twitter, Facebook, blog, press releases, etc.) </li></ul></ul></ul><ul><ul><ul><li>Create a community of interest by Spring 2010 </li></ul></ul></ul><ul><ul><ul><li>Host periodic fora </li></ul></ul></ul>
  24. 24. Parting Thoughts… <ul><li>Aug 2009 </li></ul><ul><ul><li>“ The Committee strongly supports the new direction being taken by the BioSense program, in particular the movement towards an open, distributed computing model . An open, distributed model encourages collaboration among geographically distributed organizations and provides a very efficient framework for creating mutually beneficial solutions. The Committee urges the CDC to ensure that biosurveillance systems interconnect with electronic medical record [EMR] systems effectively ” </li></ul></ul><ul><ul><li>Senate Report 111-066 - DEPARTMENTS OF LABOR, HEALTH AND HUMAN SERVICES, AND EDUCATION, AND RELATED AGENCIES APPROPRIATION BILL, 2010 </li></ul></ul>
  25. 25. Questions <ul><li>Taha A. Kass-Hout, MD, MS </li></ul><ul><li>Deputy Director for Information Science (Acting) </li></ul><ul><li>Division of Healthcare Information (DHI) (proposed) </li></ul><ul><li>Public Health Surveillance Program Office (proposed) </li></ul><ul><li>Office of Surveillance, Epidemiology, & Laboratory Services (OSELS) (proposed) </li></ul><ul><li>Centers for Disease Control & Prevention (CDC) </li></ul><ul><li>Thursday, March 03, 2010 </li></ul>