Skip Navigation

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%)
AreaPercentage
Hardware1
Software1
Services90
Other8
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.
NameFelicia Kittles
Phone Number770.488.8919
TitleIT Security Project Manager
Emailice8@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 TypePy-1 & Earlier
-2007
PY
2008
CY
2009
BY
2010
Planning Budgetary Resources4.3000.9810.8560.856
Acquisition Budgetary Resources90.6374.7553.8303.830
Maintenance Budgetary Resources4.6806.1766.8316.831
Government FTE Cost10.5471.3392.5422.542
# of FTEs15152222
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.
RowFiscal YearStrategic Goal SupportedMeasurement AreaMeasurement GroupingMeasurement IndicatorBaselinePlanned Improvement to the BaselineActual Results
12005S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories17 State/Sites have integrated disease data repositories (November, 2004)Increase by 323 States have integrated disease data repositories
22005S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats10 States/Sites are reporting to CDC in standard message format (November, 2004)Increase by 313 States/Sites are reporting to CDC in a standard NEDSS compatible message format
32005S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages15 States/Sites can receive standard electronic lab result messages (November, 2004)Increase by 319 States/Sites can receive standard electronic lab result messages
42005S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems21 States/Sites are using web-based disease reporting systems (November, 2004)Increase by 328 States/Sites are using web-based disease reporting systems
52006S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories23 States/Sites have integrated disease data repositories (November, 2005)Increase by 936 States have integrated disease data repositories
62006S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats13 States/Sites are reporting to CDC in standard message format (November, 2005)Increase by 316 States/Sites are reporting to CDC in a standard NEDSS compatible message format
72006S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages19 States/Sites can receive standard electronic lab result messages (November, 2005)Increase by 1035 Sites can receive standard electronic lab result messages
82006S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems28 States/Sites are using web-based disease reporting systemsIncrease by 337 States/Sites are using web-based disease reporting systems
92007S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories36 States/Sites have integrated disease data repositoriesIncrease by 544 States/Sites have integrated disease data repositories
102007S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats16 States/Sites are reporting to CDC in standard message formatIncrease by 319 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.
112007S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages35 States/Sites can receive standard electronic lab result messagesIncrease by 541 States/Sites can receive standard electronic lab result messages
122007S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems37 States/Sites are using web-based disease reporting systemsIncrease by 1044 States/Sites using web-based disease reporting systems
132008S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories44 (EST) States/Sites have integrated disease data repositoriesIncrease by 347 States/Sites have integrated disease data repositories
142008S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats19 (EST) States/Sites are reporting to CDC in standard message formatIncrease by 527 States/Sites are reporting to CDC in a standard NEDSS compatible message format
152008S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages41 (EST) States/Sites can receive standard electronic lab result messagesIncrease by 548 States/Sites can receive standard electronic lab result messages
162008S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems44 (EST) States/Sites are using web-based disease reporting systemsIncrease by 348 States/Sites are using web-based disease reporting systems
172009S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories47 (EST) States/Sites have integrated disease data repositoriesIncrease by 3TBD
182009S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats24 (EST) States/Sites are reporting to CDC in standard message formatIncrease by 10TBD
192009S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages46 (EST) States/Sites can receive standard electronic lab result messages (April, 2005)Increase by 5TBD
202009S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems47 (EST) States/Sites are using web-based disease reporting systemsIncrease by 3TBD
212010S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories50 (EST) States/Sites have integrated disease data repositoriesIncrease by 3TBD
222010S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats34 (EST) States/Sites are reporting to CDC in standard message formatIncrease by 10TBD
232010S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages49 (EST) States/Sites can receive standard electronic lab result messagesIncrease by 3TBD
242010S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems50 (EST) States/Sites are using web-based disease reporting systemsIncrease by 3TBD
252011S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories53 (EST) States/Sites have integrated disease data repositoriesIncrease by 2TBD
262011S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats44 (EST) States/Sites are reporting to CDC in standard message format )Increase by 10TBD
272011S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages52 (EST) States/Sites can receive standard electronic lab result messagesIncrease by 3TBD
282011S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems53 (EST) States/Sites are using web-based disease reporting systemsIncrease by 2TBD
292012S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories55 (EST) States/Sites have integrated disease data repositoriesIncrease by 2TBD
302012S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats54 (EST) States/Sites are reporting to CDC in standard message formatIncrease by 3TBD
312012S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages55 (EST) States/Sites can receive standard electronic lab result messagesIncrease by 2TBD
322012S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems55 (EST) States/Sites are using web-based disease reporting systemsIncrease by 2TBD
332013S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories57 (EST) States/Sites have integrated disease data repositoriesTBDTBD
342013S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats57 (EST) States/Sites are reporting to CDC in standard message formatTBDTBD
352013S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages57 (EST) States/Sites can receive standard electronic lab result messagesTBDTBD
362013S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems57 (EST) States/Sites are using web-based disease reporting systemsTBDTBD
372014S.O. 2.1 - Prevent the spread of infectious diseasesMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of state health departments/sites that have integrated disease data repositories57 (EST) States/Sites have integrated disease data repositoriesTBDTBD
382014S.O. 2.1 - Prevent the spread of infectious diseasesProcesses and ActivitiesParticipationNumber of states/sites reporting to CDC in standard message formats57 (EST) States/Sites are reporting to CDC in standard message formatTBDTBD
392014S.O. 2.1 - Prevent the spread of infectious diseasesCustomer ResultsNew Customers and Market PenetrationNumber of States/sites that can receive standard electronic laboratory result messages57 (EST) States/Sites can receive standard electronic lab result messagesTBDTBD
402014S.O. 2.1 - Prevent the spread of infectious diseasesTechnologyAccessibilityNumber of States/sites that have Web-based disease reporting systems57 (EST) States/Sites are using web-based disease reporting systemsTBDTBD

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.
RowAgency Component NameAgency Component DescriptionService TypeComponentReused Component NameReused UPIInternal or External Reuse?Funding %
1National 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 ManagementKnowledge Capture  No Reuse15
2National 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.VisualizationGraphing / Charting  No Reuse5
3National 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 WorkflowCase Management  No Reuse15
4National 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.ReportingAd Hoc  No Reuse5
5National 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 ManagementInformation Sharing  No Reuse10
6National 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 SchedulingInbound Correspondence Management  No Reuse5
7National 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 ManagementInformation Retrieval  No Reuse10
8National 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 SchedulingOutbound Correspondence Management  No Reuse5
9National 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 ManagementRecord Linking / Association  No Reuse5
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.
RowSRM Component>Service AreaService CategoryService StandardService Specification (i.e., vendor and product name)
1Knowledge CaptureService Interface and IntegrationInteroperabilityData Format / ClassificationLogical Observation Identifier Names and Codes by: Regenstrief Institute, Inc
2Graphing / ChartingComponent FrameworkData ManagementReporting and AnalysisSAS 9.0 by: SAS Institute Inc.
3Graphing / ChartingService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
4Case ManagementComponent FrameworkSecurityCertificates / Digital SignaturesVeriSign SSL Certificates by: Verisign
5Case ManagementService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
6Ad HocComponent FrameworkData ManagementReporting and AnalysisSAS 9.0 by: SAS Institute Inc.
7Information SharingService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
8Information SharingService Interface and IntegrationInteroperabilityData Format / ClassificationHITSP IS02 Biosurveillance by: American National Standards Institute (ANSI)
9Information SharingComponent FrameworkUser Presentation / InterfaceStatic DisplayHyper Text Markup Language by: International Organization for Standardization
10Information SharingService Access and DeliveryService TransportSupporting Network ServicesT3 Carrier by: ANSI
11Information SharingComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
12Information SharingService Access and DeliveryService TransportSupporting Network ServicesT1 Carrier by: ANSI
13Inbound Correspondence ManagementService Interface and IntegrationInteroperabilityData Format / ClassificationSystematized Nomenclature of Medicine Clinical Terms (SNOMED CT) by: International Health Terminology Standards Development Organisation
14Information RetrievalService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
15Information RetrievalComponent FrameworkData ManagementReporting and AnalysisSAS 9.0 by: SAS Institute Inc.
16Outbound Correspondence ManagementService Interface and IntegrationInteroperabilityData Format / ClassificationInternational Classification of Diseases by: World Health Organization
17Outbound Correspondence ManagementService Interface and IntegrationInteroperabilityData Format / ClassificationLogical Observation Identifier Names and Codes by: Regenstrief Institute, Inc
18Outbound Correspondence ManagementService Interface and IntegrationInteroperabilityData Format / ClassificationSystematized Nomenclature of Medicine Clinical Terms (SNOMED CT) by: International Health Terminology Standards Development Organisation
19Record Linking / AssociationService Interface and IntegrationInteroperabilityData Format / ClassificationInternational Classification of Diseases by: World Health Organization
20Record Linking / AssociationService Interface and IntegrationInteroperabilityData Format / ClassificationLogical Observation Identifier Names and Codes by: Regenstrief Institute, Inc
21Record Linking / AssociationService Interface and IntegrationInteroperabilityData Format / ClassificationSystematized 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