National Electronic Disease Surveillance System (NEDSS ...

More documents

Recommendations

Info

NEDSS Phase II, Deliverables 1 and 2 VIII. Summary Summary The implementation of the NEDSS Base System will provide the electronic processes needed for a superior notifiable disease surveillance and analysis system, replacing the functionality currently supported by the National Electronic Telecommunications System for Surveillance (NETSS) and the Tuberculosis Information Management System (TIMS). Additionally, it will provide an environment for increased data quality, timeliness and reporting of laboratory data. Though this NEDSS Base System implementation is not intended to represent the complete NEDSS solution, it will provide the foundation upon which further BOH program needs, data collection, processing and reporting can be built. The plan presented in this document proposes several essential components of implementing a complex disease reporting system—Organization, Managerial Process Plans, Technical Process Plans, Support Process Plans and Migration and Training Plans and several key appendices. These documents along with the eBusiness Plan, also attached, were completed with the understanding that the state will be using, at least in the first phases of implementation, the Base System to be provided by CDC. The implementation plan presented in this document, and its associated methodology, serve to provide a structured and proven framework to ensure successful deliverables and to meet business objectives. More specifically, this plan provides the following benefits: • Reduced risk of project failure • Consideration of system and data requirements throughout the entire life of the system • Early identification of technical and management issues • Realistic expectations of what the systems will and will not provide • Information to better balance programmatic, technical, management, and cost aspects of proposed system development or modification • Measurements of progress and status to enable effective corrective action • Information that supports effective resource management and budget planning • Consideration of meeting current and future business requirements Once the CDC Base System is received it will be necessary to develop a more detailed implementation plan as part of the implementation process since the parameters of CDC’s Base System and the software that comes are not known at this time. However the planning processes described in this document will permit the state to move forward with implementation more swiftly and take a giant leap forward in its ability to access, transmit and report both disease data for the residents of Maine and soon after that bring many of the related datasets in the BOH into the system. PHRG Page 17 of 35 September 28, 2001
NEDSS Phase II, Deliverables 1 and 2 Appendix A – Configuration Management Plan Guideline Introduction Provide a brief statement that introduces the Configuration Management (CM) plan and describes, in general terms, its use in managing the configuration of the specific project, or system. Purpose Describe why this CM plan was created, what it accomplishes, and how it is used. Scope Define the scope of CM planning. System Description Briefly describe the system, its history, and the environment in which the project operates. Describe the system architecture, operating system, and application languages. Definitions Define the terms that appear in the CM plan. Reference Documents List the documents that are referenced to support the CM process including any project or standards documents referenced in the body of the CM plan. Organization Identify the organization in which CM resides and all organization units that participate in the project. Define the functional roles of these organizational units within the project structure. CM Activities Identify all CM functions required to manage the configuration of the system. CM Responsibilities List CM responsibilities in supporting this project. Configuration Identification Explain that Configuration Identification is the basis on which the configuration items (CIs) are defined and verified; CIs and documents are labeled; changes are managed; and accountability is maintained. Define the automated tools that will be used to track and control the configuration baselines. Configuration Item Identification Identify the CIs to be controlled and specify a means of identifying changes to the CIs and related baselines. PHRG Page 18 of 35 September 28, 2001
Page 1 and 2: Phase II Deliverables #1, 2 and 3 f
Page 3 and 4: NEDSS Phase II, Deliverables 1 and
Page 17: NEDSS Phase II, Deliverables 1 and
Page 37 and 38: Phase II, Task #3 Deliverable: NEDS
Page 39 and 40: PHASE II Task 3 Deliverable Nationa
Page 41 and 42: PHASE II Task 3 Deliverable on-line
Page 43: PHASE II Task 3 Deliverable impleme

National Electronic Disease Surveillance System (NEDSS ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?