Maine HETL 2/12005 1 Experiences in Public Health Laboratory Information Management System Development OTPER Conference February 2005 Authors: John (Jack)

Slides:



Advertisements
Similar presentations
1. 2 August Recommendation 9.1 of the Strategic Information Technology Advisory Committee (SITAC) report initiated the effort to create an Administrative.
Advertisements

The Laboratory Response Network
OAS Accountability Is In Everything We Do OAS DEFINES AND IMPLEMENTS ACCOUNTABILITY ACROSS ALL ORGANIZATION LEVELS THROUGHOUT THE COMPLETE ACQUISITION.
International Conference on Establishment Surveys 1 Everything you wanted to know about Electronic Data Reporting (EDR) at Statistics Canada June 2007.
IT Governance Committee on Research Technology January 11, 2011.
Minnesota Laboratory System for Public Health (MLS-PH) Purpose and Description 1.
North Carolina’s Role in Preparedness. Objectives How you fit into the LRN Describe critical aspects of lab preparedness, surveillance and reporting,
Encouraging Adoption of Enterprise Applications Leadership Challenge Presentation December 3, 2010 Virginia Executive Institute 1.
The Laboratory Response Network
Michael S. Zachowski, Robert D. Walla Astrix Technology Group 1090 King Georges Post Rd Edison, NJ A Successful Approach to a LIMS Upgrade In A Public.
Building Public Health / Clinical Health Information Exchanges: The Minnesota Experience Marty LaVenture, MPH, PhD Director, Center for Health Informatics.
August 12, Meaningful Use *** UDOH Informatics Brown Bag Robert T Rolfs, MD, MPH.
HOMELAND SECURITY and AMERICAN COUNCIL OF INDEPENDENT LABORATORIES An Environmental Sciences Section Perspective Robert Wyeth Severn Trent Laboratories.
Preliminary Assessment Tribal Emergency Response Preparedness Dean S. Seneca, MPH, MCURP Agency for Toxic Substances and Disease Registry Centers for Disease.
Anthony Atkins Digital Library and Archives VirginiaTech ETD Technology for Implementers Presented March 22, 2001 at the 4th International.
Navigating the Maze How to sell to the public sector Adrian Farley Chief Deputy CIO State of California
NGAC Interagency Data Sharing and Collaboration Spotlight Session: Best Practices and Lessons Learned Robert F. Austin, PhD, GISP Washington, DC March.
Client Logo November 2006 GMLoB Pilot Experience and Lessons Learned Grants Applications Status Pilot National Science Foundation (NSF) USDA/Cooperative.
Common Data Elements and Metadata: Their Roles in Integrating Public Health Surveillance and Information Systems Ron Fichtner, Chief, Prevention Informatics.
SWIS Digital Inspections Project (SWIS DIP) Chris Allen, Information Management Branch California Integrated Waste Management Board November 5, 2008 The.
Internet 2 Corporate Value Proposition Stuart Kippelman (J&J) Jeff Lemmer (Ford) December 12, 2005.
Overview of NIPP 2013: Partnering for Critical Infrastructure Security and Resilience October 2013 DRAFT.
06/04/07 Maine HETL Maine HETL Lessons Learned with Environmental/Chemical LIMS Implementation and Data Exchange Jack Krueger, Chief, Maine Health and.
1 Workforce Development: The Role of a Board of Health National Association of Local Boards of Health, 10th Annual Conference July 11, 2002 J. Fred Agel,
U.S. ENVIRONMENTAL PROTECTION AGENCY For Conference Use Only Data Exchanges Using Machine-to- Machine Transfer Technologies System of Registries Conference.
My Resource for Excellence. Canadian Heritage Information Network Creation of the Collections Management Software Review (CMSR) Heather Dunn, CHIN.
Environmental Health Informatics William Sonntag Office of Environmental Information U.S. Environmental Protection Agency.
Public Health Data Standards A View from the Front Lines Bethesda, MD March 17, 2004 Presentation to PUBLIC HEALTH DATA STANDARDS CONSORTIUM 2004 ANNUAL.
“History is a set of lies agreed upon.” Napoleon Bonaparte.
Planning the Future of CDC Secure Public Health Transactions and Public Health Information Network Messaging System (PHINMS) Jennifer McGehee, Tim Morris,
ERLN OPERATIONAL FRAMEWORK EPA Quality Management Conference Presented By: Sean Kolb Schatzi Fitz-James and Terry Smith, OEM Sean Kolb and Lisa Modigliani,
The CMT in an Electronic Environment The CMT in an Electronic Environment Guy Gordon A/ADM Service Manitoba CMT Day Alberta Federal Council Feb
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
NAPHSIS Conference June 4-8, 2006 San Diego, CA The National Environmental Public Health Tracking Program NAPHSIS Conference June 4-8, 2006 San Diego,
Interagency Exchange of Laboratory Test Data University of Nebraska Medical Center Center for Rural Biosecurity, a CDC Public Health Preparedness Collaborating.
Peter B. Bloland, DVM, MPVM Director Division of Public Health Systems and Workforce Development Global Health Leadership Forum November 10, 2011 National.
Guide for Rural Local Officials Evaluating Your Input into the Statewide Transportation Planning Process Developed by the National Association of Development.
Doug Drabkowski Director of Strategic Initiatives and Research The Association of Public Health Laboratories 2025 M Street, NW, Suite 550 Washington, DC.
Public Health Data Standards Consortium
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
The Public Health Laboratory Perspective: readiness to support “meaningful use” PHDSC Annual Meeting November 12th 2009 Mary Shaffran, MPA Senior Director,
Integrating a Federated Healthcare Data Query Platform With Electronic IRB Information Systems Shan He IPHIE 2010.
SWIS Digital Inspections Project Chris Allen, Information Management Branch California Integrated Waste Management Board August 22, 2008.
MG 302: Management Information Systems (MIS)
Laboratory Information Management Systems (LIMS) Reshma Kakkar GAP.
Electronic Clinical Quality Measures – Session #1 ONC Resource Center.
PHDSC Privacy, Security, and Data Sharing Committee Letter to Governors.
A Solution Perspective An Open Source Collaborative and Foundational Solution Targeted at Non-OECD Member Countries February 9, 2016.
U.S. Department of Agriculture eGovernment Program February 25, 2003 USDA Presidential Initiatives Meeting Chris Niedermayer, USDA eGovernment Executive.
Collaborating With Your Health Plan 03/07/05 To paraphrase A. Einstein: We cannot solve today’s problems with the same level of thinking that created them.
NHII 03 Homeland Security Group B Elin Gursky ANSER Institute for Homeland Security Elin Gursky ANSER Institute for Homeland Security This presentation.
Laurie E. Locascio, Ph.D. Director, MML/NIST NIST/MML: Measurement Assurance for Biological Systems.
An Introduction to Financial Management Services in Consumer- Directed Programs Mollie G. Murphy National Resource Center for Participant- Directed Services.
Purchasing Cards. What is a Purchasing Card? It is a type of commercial credit card, used by organizations for payment of goods and services. This tool.
The Health Insurance Portability and Accountability Act of 1996 “HIPAA” Public Law
1 CDC Health Information Exchange (HIE) Accelerating State-wide Public Health Situational Awareness in New York Through Health Information Exchanges August.
Aggregated Energy Data Community Planning December 16, 2015.
What is Interoperability? How Can the LRN LIMS Integration Project Help My Lab Achieve Interoperability? Emory Meeks, CDC Jon Lipsky (Contractor) Jennifer.
Enterprise Solution Services Assessing the IT environment Oversaw 2014 Texas Legacy System Study report (HB 2738, 83R) Identified 4,130 business applications.
FUNDAMENTALS OF PUBLIC HEALTH Joseph S Duren Lopez Community & Public Health - HCA415 Instructor: Adriane Niare November 10, 2015.
Preliminary Assessment Tribal Emergency Response Preparedness
Cindy Vinion (Northrop Grumman Corporation)
BANKING INFORMATION SYSTEMS
Clinical Engineering Lecture (3).
North Carolina’s Role in Preparedness
U.S. EPA e-Manifest Program
Laboratory Information Management System Project January 18, 2012 Presenters: Sean Pearson, Twila Kunde, Tim Elsbrock.
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
North Carolina’s Role in Preparedness A Brief Overview
NM Department of Homeland Security and Emergency Management
Presentation transcript:

Maine HETL 2/ Experiences in Public Health Laboratory Information Management System Development OTPER Conference February 2005 Authors: John (Jack) Krueger, Chief Maine HETL Ken Pote PhD, Senior Scientist, Maine HETL (Presenter) James Curlett, Organic Chemistry Supervisor, Maine HETL With Assistance from: Public Health Informatics Institute APHL MIS Committee

Maine HETL 2/ In order to operate as a first line of defense to protect the public against diseases and other health hazards, every public health lab must be supported by a sophisticated laboratory information management system (LIMS). Sophisticated public health LIMS technology infrastructure assures that high volumes of specimens can move seamlessly from hundreds of different sources as the needs of each situation change.

Maine HETL 2/ LIMS enable PHLs to continue daily operations supporting state programs as customers, while always being ready to join as part of the larger national protection network. Finally, sophisticated public health LIMS technology assures the flow of information necessary to inform both governmental policy makers and business leaders about health threats.

Maine HETL 2/ Being prepared to respond to health threats today means that PHLs must maintain infrastructure that meets minimum national standards, enabling seamless interconnection with other PHLs. It also requires developing partnerships and interconnectivity with numerous federal agencies (e.g., CDC, EPA, USDA, FDA, Department of Homeland Security, FBI, etc.), and other health partners across the nation, as well as with international health agencies.

Maine HETL 2/ Examples of Different Public Health- Related Data Exchange Efforts That PHL’s Participate In: National Environmental Information Exchange Network (NEIEN) Drinking Water Security Integrated Public Health Information System (IPHIS) Bio& Chemical- Terrorism Environmental Public Health Tracking (EPHT) Food Contamination Threat Reporting

Maine HETL 2/ State laboratories uniquely support separate data exchange networks for Centers for Disease Control, Environmental Protection Agency, and the Food and Drug Administration. The networks are called PHINMS (Public Health Information Network Messaging System), NEIEN (National Environmental Information Exchange Network), and eLEXNET (electronic laboratory exchange network) respectively.

Maine HETL 2/ Food Related Analytical Issue? If it’s the Ketchup, Mayo, Bun send the data to FDA If it’s the Hamburger or Lettuce send the data to USDA Did someone eat it? Test it at the Public Health Lab and report to CDC/State EPI If Water or Environment Related Report to EPA The Lab’s role uniquely brings together different State and Federal Organizations

Maine HETL 2/ Each reporting entity potentially requires unique security, data standards, message formats, message protocols, administrative system support, and hardware and software. The current state of PHLs is typified by a variety of locally developed, community developed (e.g., LITS Plus), and vendor products implemented on a lab-by-lab basis when funding has been available.

Maine HETL 2/ Percentage of states using multiple LIMS (APHL survey, 2003)

Maine HETL 2/ Sources of states’ public health LIMS solutions (APHL survey, 2004)

Maine HETL 2/ Subsequent survey data were collected in November 2004, with 44 to 48 of the 56 PHLs responding. 90% are planning to improve their LIMS by upgrading a portion of the system or purchasing a new LIMS.

Maine HETL 2/ It also shows that less than half (40%) of the PHLs have what they would consider to be an enterprise LIMS systems that covers all technical functions of the PHL.

Maine HETL 2/ One-fourth (26.7%) of respondents say they cannot report electronically to clients, and almost half (47.7%) say their LIMS system does not incorporate any of the national data standards (HL7, LOINC, or SNOMED)

Maine HETL 2/ Together these survey data paint a picture of public health LIMS in distress. The majority of labs are expending hundreds of thousands of dollars on LIMS, but still have unmet needs.

Maine HETL 2/ PHLs need LIMS tools that: 1.can evolve over time, 2. do so within the context of a mission that is expanding at a rate faster than their budgets are growing, and 3.provide the best possible return for tax payers.

Maine HETL 2/ Additional goals for LIMS, as stated by PHL leaders, include:  improving PHL information capabilities,  strengthening the network of national PHL capability, and  encouraging every PHL to adopt a continuous enhancement approach to their LIMS, in effect an evolving transition to a new and more capable LIMS.

Maine HETL 2/ a. Single PHL implementation of a COTS LIMS. (Implement commercial off-the-shelf (COTS) product and pay for enhancements needed to comply with evolving standards and work needs.) b. Collaborative COTS LIMS. (Work with a consortium of PHLs, COTS product implemented through collaborative approach to make decisions about how a product is configured.) c. Homegrown LIMS, single state. d. Multiple LIMS in one PHL. (Mix of COTS and/or homegrown.) e. LITS Plus (Continue to enhance and evolve LITS Plus, the first LIMS developed specifically with the needs of PHLs in mind.) LIMS Procurement Options:

Maine HETL 2/ MAINE’S EXPERIENCE Maine has Two Legacy Systems Environmental and Forensic are Managed with a Product partly COTS and partly Homegrown system written in Fortran 77 and using outdated Unix Hardware Includes chemical terrorism, radiation, drinking water, drug testing Clinical Microbiology are managed with LITS Plus Includes all clinical testing, bioterrorism, blood lead

Maine HETL 2/ The RFP Process Having no funds assures that a lab can not request a new LIMS Having funding, such as Federal BT Funding and a high level mandate does not mean that is will be “easy” to purchase a LIMS The RFP process can take so long that the Funding will go away Even with a Thorough Scope of Work and detailed User Requirement Specifications the process of choosing a vendor can still be a crap shoot. Without Dedicated IT staff to defend your needs or customize the COTS product, there are many pressures to change your lab to fit the product.

Maine HETL 2/ CollaborationHelps APHL offers several “templates” for States to use to help with the SOW development process Collaborative efforts with the Public Health Informatics Institute and APHL are helpful However as the saying goes “If you know one Public Health Lab, you know one Public Health Lab” No two labs are the same and user requirements vary significantly

Maine HETL 2/ Maine’s Purchase Process Maine declared that its oldest Legacy System was in an emergency need for replacement. The hard drives literally can not be turned off, as they will not start and hard drives are no longer made- we raid the “junk yards” for parts! Even with this “emergency” declaration it still took 6 months to get a sole source vendor approved. Maine has purchased Star Lims to replace the environmental/forensic systems We are just coming on line after 9 months of intensive implementation efforts. The process to replace the clinical package still is undecided- will we need an RFP to add to our existing system?

Maine HETL 2/ Lessons Learned (1) 1. Clearly established business rules a must 2. Consideration of needs for electronic imports to and exports from the system 3. Ease of creation of imports/exports ie do they need to be hard coded? Easily customized. 4. Accounting system needs 5. Inventory tracking requirements 6. Ease of query and report customization

Maine HETL 2/ Lessons Learned (2) 7. QA/QC needs – do you want to track everything and get rid of your paper system? This will require a lot of materials data populating and that means time 8. Accurate assessment of how much customization is needed 9. To do 8, Recommend the vendor send a person for each of your groups with an agreed- upon questionnaire to fill out- and spend a few days in each area. Areas such as accounting, login, receiving, prep, analytical, data entry, QC 10. Data approval levels 11. Report printing and mailing issues

Maine HETL 2/ Remember: for LIMS implementation: The “Devil is in the Details”