1 / 11

Feasibility Analysis for Web-Based Reporting System will include:

kat
Télécharger la présentation

Feasibility Analysis for Web-Based Reporting System will include:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architectural Challenges in Developing a Web-Based Public HealthReporting System Workshop on Evaluating Software Architectural Solutions - 20009 May 2000Donna NowellTechnology Information Systems Program (TISP)Engineering DirectorateLawrence Livermore National Laboratorynowell1@llnl.gov (925) 422-1515FAX (925) 424-5054

  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. 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 (Quality, Timeliness, Consistency, Standard Definitions, Reduce Data Duplication) • General consensus that new system must be Web-based

  4. Sys 1 DHS Sys 1 DHS Sys n Doctors Multiple Info Sys Legacy Sys Sys n Description of Current Reporting Structure Local County State National Paper Paper Not Linked Not Linked Fax Modem Upload Electronic (For info mgn sys, report data is either manually or electronically derived)

  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. 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. 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. Architecture Must be Flexible & Adaptable to Support and Benefit from Work of Others Emerging Standards • 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

  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. 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. 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

More Related