1. Architectural Challenges in Developing a Web-Based Public Health Reporting System Workshop on Evaluating Software Architectural Solutions - 2000 9 May 2000 Donna Nowell Technology Information Systems Program (TISP) Engineering Directorate Lawrence Livermore National Laboratory nowell1@llnl.gov (925) 422-1515 FAX (925) 424-5054

2. echnology Information Systems Program T 2 Feasibility Analysis for Web-Based Reporting System will include: Determine High Level System Requirements Inventory Existing Systems and Data Flows Identify Required Supporting Policies and Procedures Conduct Technology Survey Propose Architecture for a Pilot System Identify Risks

3. echnology Information Systems Program T 3 Key Motivators for Development of System Recognition that integration of public health infrastructure must be strengthened to better support public health goals Usability of data must be improved General consensus that new system must be Web-based (Quality, Timeliness, Consistency, Standard Definitions, Reduce Data Duplication)

4. echnology Information Systems Program T 4 Description of Current Reporting Structure LocalCountyStateNational Paper Doctors Multiple Info Sys Legacy Sys Fax (For info mgn sys, report data is either manually or electronically derived) Electronic DHS Sys 1 DHS Sys n Not Linked Sys 1Sys n Not Linked Paper Modem Upload

5. echnology Information Systems Program T 5 Earlier Study Captured Goals for a New System Easy to use Improve amount of clinical cases reported Provide data more timely to state level Improve quality of data Provide feedback to counties and providers Control of access to data and workflow Security and data protection Standards based Provide support during disasters & health crisis situations Provide computer to computer data transfers

6. echnology Information Systems Program T 6 Objectives of New Web-Based System Application solutions that are architecture neutral Zero-maintenance clients to minimize maintenance & support Component-based architecture Robustness Secure computing environment

7. echnology Information Systems Program T 7 Data Sharing is a Key Issue Improved data collection methods and delivery Standard data definitions to facilitate sharing Identification of standard core data sets Able to link data collected in different information systems Support timely access to data -- or data can lose value Support workflows for review & release of data. Allow access to data while still in review. Need policies which address data sharing & confidentiality

8. echnology Information Systems Program T 8 Architecture Must be Flexible & Adaptable to Support and Benefit from Work of Others State projects creating standards National projects creating standards Changing and Future Regulations Other Projects Allow for integration with other systems being developed Re-use components developed by other efforts Emerging Standards

9. echnology Information Systems Program T 9 Elements of Good Software Architecture Should be Incorporated Manage change and complexity Adapt to system extensions Minimize interdependencies among complex modules Allow reasonable cost estimation

10. echnology Information Systems Program T 10 Challenges in Designing the Architecture Determining the most effective abstractions to meet architecture goals System will evolve over time to address all public health functions New and changing requirements Identifying the appropriate levels for application and service objects Keeping it simple. Complex systems tend to be brittle.

11. echnology Information Systems Program T 11 Addressing Architectural Challenges Establish system requirements and constraints Define quality attributes and measurements Propose alternative architectures Identify pros and cons of each proposal Evaluate each proposal against requirements, constraints, quality attributes Continuing Education