Exhibit 300 (BY2010) - PHIN: National Electronic Disease Surveillance System

PART ONE

OVERVIEW

1. Date of Submission:: 2009-04-10

2. Agency:: 009

3. Bureau:: 20

4. Name of this Capital Asset:: CDC PHIN: National Electronic Disease Surveillance System

5. Unique Project Identifier:: 009-20-01-03-01-0362-00

6. What kind of investment will this be in FY2010?: Mixed Life Cycle

7. What was the first budget year this investment was submitted to OMB?: FY2002

8. Provide a brief summary and justification for this investment, including a brief description of how this closes in part or in whole an identified agency performance gap.: NEDSS (National Electronic Disease Surveillance System) is an Internet-based infrastructure for public health surveillance data exchange that uses specific PHIN (Public Health Information Network) Data Standards. NEDSS also relies heavily on industry standards (e.g., LOINC, SNOMED, HL7), and policy-level agreements on data access/ protection of confidentiality. NEDSS represents an ongoing close collaboration between the CDC and its public health partners. NEDSS is a system of interoperable subsystems, components & systems modules that include software applications developed & implemented by: the CDC; State & Local health depts; and those created by commercial services & vendors. During FY07, CDC's NEDSS Project strategically realigned its funding & long range planning to better address changing information technology capabilities & to meet emerging needs in local, state, & national public health surveillance. This realignment will support standards-based PHIN & and American Health Information Community (AHIC)-approved, electronic message exchange between public health stakeholders. When NEDSS began in 2001, no state had integrated public health surveillance systems as articulated in the NEDSS vision; today over 35 states have implemented surveillance systems based on this vision. Initially, CDC responded to requests from states seeking assistance to obtain NEDSS software solutions, often based on local and state information technology resource constraints. The CDC NEDSS Base System (NBS) was developed by CDC to meet those needs. Today, 16 states use the NBS. Additionally, the NEDSS project will increase the resources, technical support, and training required to accelerate successful adoption of the NEDSS Message Subscription Service (MSS). The MSS is based on two major software components: Orion Rhapsody, a Enterprise Application Integration (EAI) engine, and the NEDSS Brokering Tool (NBT), a CDC-built web component. A CDC strategic mission critical area supported by NEDSS includes: "People Prepared for Emerging Health Threats": 1. Detection & Reporting-Communications: Improve the timeliness and accuracy of communications regarding threats to public health. 2. Investigation: Decrease the time to identify causes, risk factors and appropriate interventions for those affected by threats to the public's health. In 2008, includes $11M for extramural activities that is not part of this Case, but is on a seperate Ex53.

9. Did the Agency's Executive/Investment Committee approve this request?: yes

9.a. If "yes," what was the date of this approval?: 2008-07-11

10. Did the Project Manager review this Exhibit?: yes

11.a. What is the current FAC-P/PM certification level of the project/program manager?: Waiver Issued

11.b. When was the Program/Project Manager Assigned?: 2008-06-02

11.c. What date did the Program/Project Manager receive the FACP/PM certification? If the certification has not been issued, what is the anticipated date for certification?: 2009-07-31

12. Has the agency developed and/or promoted cost effective, energy-efficient and environmentally sustainable techniques or practices for this project.: yes

12.a. Will this investment include electronic assets (including computers)?: yes

12.b. Is this investment for new construction or major retrofit of a Federal building or facility? (answer applicable to non-IT assets only): no

13. Does this investment directly support one of the PMA initiatives?: yes

If yes, select the initiatives that apply:

Initiative Name
Expanded E-Government

13.a. Briefly and specifically describe for each selected how this asset directly supports the identified initiative(s)? (e.g. If E-Gov is selected, is it an approved shared service provider or the managing partner?): The expanded E-Government initiative is focused on increasing efficiency, controlling IT costs, developing and implementing common solutions. NEDSS has been architected to enable states and public health departments to access records that were only available by paper based reports in the past. The NEDSS initiative provides technical standards to facilitate electronic communications between the CDC and public health state labs, health departments and other health facilities open to the public.

14. Does this investment support a program assessed using the Program Assessment Rating Tool (PART)?: no

15. Is this investment for information technology?: yes

16. What is the level of the IT Project (per CIO Council's PM Guidance)?: Level 3

17. What project management qualifications does the Project Manager have? (per CIO Council's PM Guidance): (1) Project manager has been validated as qualified for this investment

18. Is this investment identified as high risk on the Q4 - FY 2007 agency high risk report (per OMB memorandum M-05-23)?: no

19. Is this a financial management system?: no

19.a.1. If yes, which compliance area:: N/A

19.a.2. If no, what does it address?: Public Health Surveillance

20. What is the percentage breakout for the total FY2009 funding request for the following? (This should total 100%)

Area	Percentage
Hardware	1
Software	1
Services	90
Other	8

21. If this project produces information dissemination products for the public, are these products published to the Internet in conformance with OMB Memorandum 05-04 and included in your agency inventory, schedules and priorities?: yes

22. Contact information of individual responsible for privacy related questions.

Name	Felicia Kittles
Phone Number	770.488.8919
Title	IT Security Project Manager
Email	ice8@cdc.gov

23. Are the records produced by this investment appropriately scheduled with the National Archives and Records Administration's approval?: no

24. Does this investment directly support one of the GAO High Risk Areas?: no

SUMMARY OF SPEND

1. Provide the total estimated life-cycle cost for this investment by completing the following table. All amounts represent budget authority in millions, and are rounded to three decimal places. Federal personnel costs should be included only in the row designated Government FTE Cost, and should be excluded from the amounts shown for Planning, Full Acquisition, and Operation/Maintenance. The total estimated annual cost of the investment is the sum of costs for Planning, Full Acquisition, and Operation/Maintenance. For Federal buildings and facilities, life-cycle costs should include long term energy, environmental, decommissioning, and/or restoration costs. The costs associated with the entire life-cycle of the investment should be included in this report. All amounts represent Budget Authority Note: For the cross-agency investments, this table should include all funding (both managing partner and partner agencies). Government FTE Costs should not be included as part of the TOTAL represented.

Cost Type	Py-1 & Earlier -2007	PY 2008	CY 2009	BY 2010
Planning Budgetary Resources	4.300	0.981	0.856	0.856
Acquisition Budgetary Resources	90.637	4.755	3.830	3.830
Maintenance Budgetary Resources	4.680	6.176	6.831	6.831
Government FTE Cost	10.547	1.339	2.542	2.542
# of FTEs	15	15	22	22

2. Will this project require the agency to hire additional FTE's?: no

PERFORMANCE

In order to successfully address this area of the exhibit 300, performance goals must be provided for the agency and be linked to the annual performance plan. The investment must discuss the agency's mission and strategic goals, and performance measures (indicators) must be provided. These goals need to map to the gap in the agency's strategic goals and objectives this investment is designed to fill. They are the internal and external performance benefits this investment is expected to deliver to the agency (e.g., improve efficiency by 60 percent, increase citizen participation by 300 percent a year to achieve an overall citizen participation rate of 75 percent by FY 2xxx, etc.). The goals must be clearly measurable investment outcomes, and if applicable, investment outputs. They do not include the completion date of the module, milestones, or investment, or general goals, such as, significant, better, improved that do not have a quantitative measure.

Agencies must use the following table to report performance goals and measures for the major investment and use the Federal Enterprise Architecture (FEA) Performance Reference Model (PRM). Map all Measurement Indicators to the corresponding Measurement Area and Measurement Grouping identified in the PRM. There should be at least one Measurement Indicator for each of the four different Measurement Areas (for each fiscal year). The PRM is available at www.egov.gov. The table can be extended to include performance measures for years beyond FY 2009.

Row	Fiscal Year	Strategic Goal Supported	Measurement Area	Measurement Grouping	Measurement Indicator	Baseline	Planned Improvement to the Baseline	Actual Results
1	2005	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	17 State/Sites have integrated disease data repositories (November, 2004)	Increase by 3	23 States have integrated disease data repositories
2	2005	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	10 States/Sites are reporting to CDC in standard message format (November, 2004)	Increase by 3	13 States/Sites are reporting to CDC in a standard NEDSS compatible message format
3	2005	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	15 States/Sites can receive standard electronic lab result messages (November, 2004)	Increase by 3	19 States/Sites can receive standard electronic lab result messages
4	2005	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	21 States/Sites are using web-based disease reporting systems (November, 2004)	Increase by 3	28 States/Sites are using web-based disease reporting systems
5	2006	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	23 States/Sites have integrated disease data repositories (November, 2005)	Increase by 9	36 States have integrated disease data repositories
6	2006	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	13 States/Sites are reporting to CDC in standard message format (November, 2005)	Increase by 3	16 States/Sites are reporting to CDC in a standard NEDSS compatible message format
7	2006	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	19 States/Sites can receive standard electronic lab result messages (November, 2005)	Increase by 10	35 Sites can receive standard electronic lab result messages
8	2006	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	28 States/Sites are using web-based disease reporting systems	Increase by 3	37 States/Sites are using web-based disease reporting systems
9	2007	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	36 States/Sites have integrated disease data repositories	Increase by 5	44 States/Sites have integrated disease data repositories
10	2007	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	16 States/Sites are reporting to CDC in standard message format	Increase by 3	19 States/Sites are reporting to CDC in a standard NEDSS compatible message format. 50 States agreed to adoption of NEDSS-compatiblility public health surveillance systems.
11	2007	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	35 States/Sites can receive standard electronic lab result messages	Increase by 5	41 States/Sites can receive standard electronic lab result messages
12	2007	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	37 States/Sites are using web-based disease reporting systems	Increase by 10	44 States/Sites using web-based disease reporting systems
13	2008	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	44 (EST) States/Sites have integrated disease data repositories	Increase by 3	47 States/Sites have integrated disease data repositories
14	2008	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	19 (EST) States/Sites are reporting to CDC in standard message format	Increase by 5	27 States/Sites are reporting to CDC in a standard NEDSS compatible message format
15	2008	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	41 (EST) States/Sites can receive standard electronic lab result messages	Increase by 5	48 States/Sites can receive standard electronic lab result messages
16	2008	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	44 (EST) States/Sites are using web-based disease reporting systems	Increase by 3	48 States/Sites are using web-based disease reporting systems
17	2009	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	47 (EST) States/Sites have integrated disease data repositories	Increase by 3	TBD
18	2009	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	24 (EST) States/Sites are reporting to CDC in standard message format	Increase by 10	TBD
19	2009	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	46 (EST) States/Sites can receive standard electronic lab result messages (April, 2005)	Increase by 5	TBD
20	2009	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	47 (EST) States/Sites are using web-based disease reporting systems	Increase by 3	TBD
21	2010	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	50 (EST) States/Sites have integrated disease data repositories	Increase by 3	TBD
22	2010	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	34 (EST) States/Sites are reporting to CDC in standard message format	Increase by 10	TBD
23	2010	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	49 (EST) States/Sites can receive standard electronic lab result messages	Increase by 3	TBD
24	2010	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	50 (EST) States/Sites are using web-based disease reporting systems	Increase by 3	TBD
25	2011	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	53 (EST) States/Sites have integrated disease data repositories	Increase by 2	TBD
26	2011	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	44 (EST) States/Sites are reporting to CDC in standard message format )	Increase by 10	TBD
27	2011	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	52 (EST) States/Sites can receive standard electronic lab result messages	Increase by 3	TBD
28	2011	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	53 (EST) States/Sites are using web-based disease reporting systems	Increase by 2	TBD
29	2012	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	55 (EST) States/Sites have integrated disease data repositories	Increase by 2	TBD
30	2012	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	54 (EST) States/Sites are reporting to CDC in standard message format	Increase by 3	TBD
31	2012	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	55 (EST) States/Sites can receive standard electronic lab result messages	Increase by 2	TBD
32	2012	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	55 (EST) States/Sites are using web-based disease reporting systems	Increase by 2	TBD
33	2013	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	57 (EST) States/Sites have integrated disease data repositories	TBD	TBD
34	2013	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	57 (EST) States/Sites are reporting to CDC in standard message format	TBD	TBD
35	2013	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	57 (EST) States/Sites can receive standard electronic lab result messages	TBD	TBD
36	2013	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	57 (EST) States/Sites are using web-based disease reporting systems	TBD	TBD
37	2014	S.O. 2.1 - Prevent the spread of infectious diseases	Mission and Business Results	Population Health Management and Consumer Safety	Number of state health departments/sites that have integrated disease data repositories	57 (EST) States/Sites have integrated disease data repositories	TBD	TBD
38	2014	S.O. 2.1 - Prevent the spread of infectious diseases	Processes and Activities	Participation	Number of states/sites reporting to CDC in standard message formats	57 (EST) States/Sites are reporting to CDC in standard message format	TBD	TBD
39	2014	S.O. 2.1 - Prevent the spread of infectious diseases	Customer Results	New Customers and Market Penetration	Number of States/sites that can receive standard electronic laboratory result messages	57 (EST) States/Sites can receive standard electronic lab result messages	TBD	TBD
40	2014	S.O. 2.1 - Prevent the spread of infectious diseases	Technology	Accessibility	Number of States/sites that have Web-based disease reporting systems	57 (EST) States/Sites are using web-based disease reporting systems	TBD	TBD

Enterprise Architecture

In order to successfully address this area of the business case and capital asset plan you must ensure the investment is included in the agency's EA and Capital Planning and Investment Control (CPIC) process, and is mapped to and supports the FEA. You must also ensure the business case demonstrates the relationship between the investment and the business, performance, data, services, application, and technology layers of the agency's EA.

1. Is this investment included in your agency's target enterprise architecture?: yes

2. Is this investment included in the agency's EA Transition Strategy?: yes

2.a. If yes, provide the investment name as identified in the Transition Strategy provided in the agency's most recent annual EA Assessment.: CDC PHIN: National Electronic Disease Surveillance System (NEDSS)

3. Is this investment identified in a completed (contains a target architecture) and approved segment architecture?: no

4. Identify the service components funded by this major IT investment (e.g., knowledge management, content management, customer relationship management, etc.). Provide this information in the format of the following table. For detailed guidance regarding components, please refer to http://www.whitehouse.gov/omb/egov/. Component: Use existing SRM Components or identify as NEW. A NEW component is one not already identified as a service component in the FEA SRM. Reused Name and UPI: A reused component is one being funded by another investment, but being used by this investment. Rather than answer yes or no, identify the reused service component funded by the other investment and identify the other investment using the Unique Project Identifier (UPI) code from the OMB Ex 300 or Ex 53 submission. Internal or External Reuse?: Internal reuse is within an agency. For example, one agency within a department is reusing a service component provided by another agency within the same department. External reuse is one agency within a department reusing a service component provided by another agency in another department. A good example of this is an E-Gov initiative service being reused by multiple organizations across the federal government. Funding Percentage: Please provide the percentage of the BY requested funding amount used for each service component listed in the table. If external, provide the funding level transferred to another agency to pay for the service.

Row	Agency Component Name	Agency Component Description	Service Type	Component	Internal or External Reuse?	Funding %
1	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Knowledge Management	Knowledge Capture	No Reuse	15
2	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Visualization	Graphing / Charting	No Reuse	5
3	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Tracking and Workflow	Case Management	No Reuse	15
4	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Reporting	Ad Hoc	No Reuse	5
5	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Knowledge Management	Information Sharing	No Reuse	10
6	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Routing and Scheduling	Inbound Correspondence Management	No Reuse	5
7	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Knowledge Management	Information Retrieval	No Reuse	10
8	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Routing and Scheduling	Outbound Correspondence Management	No Reuse	5
9	National Electronic Disease Surveillance System (NEDSS) (362)	NEDSS and the electronic communications systems which support it support the creation of integrated public health information and surveillance systems. It will tie together the current myriad, separate systems into a comprehensive solution that facilitates the efficient collection, analysis, and use of data and the sharing of computer software solutions across disease-specific program areas.	Records Management	Record Linking / Association	No Reuse	5

5. To demonstrate how this major IT investment aligns with the FEA Technical Reference Model (TRM), please list the Service Areas, Categories, Standards, and Service Specifications supporting this IT investment. FEA SRM Component: Service Components identified in the previous question should be entered in this column. Please enter multiple rows for FEA SRM Components supported by multiple TRM Service Specifications. Service Specification: In the Service Specification field, Agencies should provide information on the specified technical standard or vendor product mapped to the FEA TRM Service Standard, including model or version numbers, as appropriate.

Row	SRM Component	>Service Area	Service Category	Service Standard	Service Specification (i.e., vendor and product name)
1	Knowledge Capture	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes by: Regenstrief Institute, Inc
2	Graphing / Charting	Component Framework	Data Management	Reporting and Analysis	SAS 9.0 by: SAS Institute Inc.
3	Graphing / Charting	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0 by: Microsoft Corporation
4	Case Management	Component Framework	Security	Certificates / Digital Signatures	VeriSign SSL Certificates by: Verisign
5	Case Management	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0 by: Microsoft Corporation
6	Ad Hoc	Component Framework	Data Management	Reporting and Analysis	SAS 9.0 by: SAS Institute Inc.
7	Information Sharing	Service Platform and Infrastructure	Hardware / Infrastructure	Wide Area Network (WAN)	Synchronous Optical Networking by: ANSI
8	Information Sharing	Service Interface and Integration	Interoperability	Data Format / Classification	HITSP IS02 Biosurveillance by: American National Standards Institute (ANSI)
9	Information Sharing	Component Framework	User Presentation / Interface	Static Display	Hyper Text Markup Language by: International Organization for Standardization
10	Information Sharing	Service Access and Delivery	Service Transport	Supporting Network Services	T3 Carrier by: ANSI
11	Information Sharing	Component Framework	Data Interchange	Data Exchange	Electronic Business using XML by: Organization for the Advancement of Structured Information Standards
12	Information Sharing	Service Access and Delivery	Service Transport	Supporting Network Services	T1 Carrier by: ANSI
13	Inbound Correspondence Management	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) by: International Health Terminology Standards Development Organisation
14	Information Retrieval	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0 by: Microsoft Corporation
15	Information Retrieval	Component Framework	Data Management	Reporting and Analysis	SAS 9.0 by: SAS Institute Inc.
16	Outbound Correspondence Management	Service Interface and Integration	Interoperability	Data Format / Classification	International Classification of Diseases by: World Health Organization
17	Outbound Correspondence Management	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes by: Regenstrief Institute, Inc
18	Outbound Correspondence Management	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) by: International Health Terminology Standards Development Organisation
19	Record Linking / Association	Service Interface and Integration	Interoperability	Data Format / Classification	International Classification of Diseases by: World Health Organization
20	Record Linking / Association	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes by: Regenstrief Institute, Inc
21	Record Linking / Association	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) by: International Health Terminology Standards Development Organisation

6. Will the application leverage existing components and/or applications across the Government (i.e., FirstGov, Pay.Gov, etc)?: yes

6.a. If yes, please describe.: NEDSS achieves optimal use of government funds by sharing PHIN vocabulary and messaging services, CDC IT infrastructure, and the CDC Secure Data Network. It maps to the Federal Health Architecture and to the work of the Public Health Surveillance Workgroup.

PART TWO

RISK

You should perform a risk assessment during the early planning and initial concept phase of the investment's life-cycle, develop a risk-adjusted life-cycle cost estimate and a plan to eliminate, mitigate or manage risk, and be actively managing risk throughout the investment's life-cycle.

Answer the following questions to describe how you are managing investment risks.

1. Does the investment have a Risk Management Plan?: yes

1.a. If yes, what is the date of the plan?: 2008-03-01

1.b. Has the Risk Management Plan been significantly changed since last year's submission to OMB?: no

3. Briefly describe how investment risks are reflected in the life cycle cost estimate and investment schedule:: The NEDSS scope and budget planning is based on a work breakdown structure technique that decomposes each work element into its fundamental components. Each component is evaluated based on a risk assessment. This technique helps to clearly define the deliverables to the customer. The budget is determined based on the cost and risk value of the work element. The budget for each element is derived from the most likely scenario that has been risk adjusted. The total of each element comprises the full budget for NEDSS.

COST & SCHEDULE

1. Does the earned value management system meet the criteria in ANSI/EIA Standard 748?: no

2. Is the CV% or SV% greater than ± 10%?: no

3. Has the investment re-baselined during the past fiscal year?: yes

3.a. If yes, when was it approved by the agency head?: 2008-06-10