OpenELIS Open Source LIS. APHL Annual Meeting - May 16, St. Louis

Transcription

1 OpenELIS Open Source LIS APHL Annual Meeting - May 16, St. Louis

2 Today s Agenda History of the LIMS Collaborative The Beginning of OpenELIS OpenELIS Architecture Open Source Principles Status of OpenELIS Global Collaboration Brief Demo page 2

3 History of the LIMS Collaborative APHL / PHII / Public Health Laboratories

4 History of the LIMS Collaborative 2002 Building the Foundational Community APHL, PHII, and 25 Public Health Laboratories Robert Wood Johnson Foundation funding 6 State workgroup defines PHL business processes 2003 Recognizing Similarities Frequent Review and approval of Stakeholders Published LIMS Requirement Document detailing 16 business processes 2004/2005 Next Step Project Completed logical design 1 & 2 What We Learned Collaboration is an efficient and economically viable manner to address public health IT needs Collaboration continues to be a focal point in addressing emerging standards such as PHLIP page 4

5 The Beginning of OpenELIS Design and Development

6 The Beginning of OpenELIS Began in September IA, KS, MN collaboration In-Person at the APHL Annual Meeting Regular video conference meetings Webex sessions for demo s Database Model Completed Inclusion of all core lab functions Documentation on data elements and relationships Development Define the IT technical architecture Design and programming activities Continuation of collaborative activities page 6

7 OpenELIS Architecture Design Goals and Open Source Technology

8 Overview Enterprise wide system Single LIMS that can manage clinical, newborn, environmental, and animal samples (incorporates all 16 business processes from Requirements document) Clients will use a web browser interface to order tests, monitor samples, and download their results Robust, flexible architecture - future sample information needs can be easily accommodated without a redesign Samples from multiple domains can be entered e.g. environmental & SDWIS sample information; PT and environmental or clinical sample information Animal SDWIS Environ mental Core PT Neonatal Disease page 8

9 Architecture and Design Database Design Flexible to meet new requirements Database Independent (Triggers & Rules) Oracle, Postgres, Informix Operating System Operating System Independent Unix, Linux Application Architecture JAVA Programming Language Open source tools (Eclipse, Hibernate, Jasper) Security built into the application (test level) User Interface Design Follow Web design principles Browser Independent page 9

10 Architecture and Design Eclipse Development Environment Best Java development environment Java Programming Language Operating system independent Windows, Unix, Linux, Apple, etc Strong application security Access rights to the test level, user controlled Standard browser interface No client software to install and maintain Accessed through a local network, the Internet Jasper Reports & Open Reports Reports created in PDF, HTML, Excel format Flexible report scheduling page 10

11 Open Source Principles A Primer on Open Source and Free Software

12 Some Facts about Open Source Open source is a model for software development that emphasizes collaboration among a community of people who share a common (business) interest Distribution of the software is free (with certain restrictions for redistribution). Consulting and support organizations can charge for support activities or additional software Open source is supported by a community thru contributions of time, knowledge, and skill, whether application and database design, programming, or subject matter expertise. page 12

13 OpenELIS Goals Design and develop a collaborative open source LIMS for public health laboratories Create an open source developer community around OpenELIS Create a common data model by bringing IT staff and laboratorians together Make it affordable and sustainable Make it flexible and scalable Make interfaces open and available to vendors Create opportunities for vendors and consultants to provide support services page 13

14 Reality Check! Nothing is ever free Not everyone wants to collaborate, some will have concerns about contributing or compromising individual requirements To take advantage of open source, PHL s will need IT expertise, whether staff, centralized, or contracted resources, in order to install the system and make code contributions Each PHL will be responsible for updating and maintaining their version of the software as new modules and functionalities are released There are political considerations, not all states welcome the use of open source We need a governance structure page 14

15 Status of OpenELIS

16 MN Status User Acceptance Testing Flu HIV/AIDS, STI s BT Next Steps Uncover requirement / functionality gaps Transition from IT tasks to user tasks User schedule for production PHLIP Rhapsody & PHIN MS installed Flu test scenarios sent to CDC page 16

17 Multi-State, Country Collaboration MN & Iowa Collaboration Newborn Screening Testing Short-Term, and Long-Term Follow-up Patient Master Index (Vital Records, etc) Environmental Other Partners Two state PHL s and a major university are evaluating OpenELIS CDC / GAP Interest for global LIS requirements page 17

18 Future Collaborative Activities Continue to Enhance the System Technology improvements (handheld devices) New business requirements Create an OpenELIS Developer Community to Leverage Open Source Concepts Don t have to do everything individually Benefit from other people s experience and expertise Diverse needs and perspectives will provide better software Create a User Community Collaborate on business requirements Share expertise Benefit from Other Open Source Projects Open Medical Record System (OpenMRS) Open source HL7 interface engines like Mirth or IBM s public health reporting framework Data visualization packages like STEM page 18

19 Global Collaboration Vietnam

20 Global Collaboration July 2006 Meeting with CDC Gap Collaboration on global LIS requirements CDC Support for global milestones July 2007 Vietnam Visit to MN Testing and training Linux and Postgres infrastructure Jan 2007 VN Implementation Two hospital laboratories page 20

21 60% of Respondents to the most recent APHL Informatics survey said they would be interested in a collaboratively developed Open Source LIMS page 21

22 Want More Information? APHL can get you in the loop! Project information Ways to get involved Possible August collaborators meeting!! (more info to come!) Michelle Meigs page 22