Skip Navigation

Exhibit 300 (BY2010) - Public Health Information Network (PHIN)

PART ONE


OVERVIEW


1. Date of Submission:
2009-04-10
2. Agency:
009
3. Bureau:
20
4. Name of this Capital Asset:
CDC Public Health Information Network (PHIN)
5. Unique Project Identifier:
009-20-01-03-01-0908-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.
The Public Health Information Network (PHIN) is CDC's vision for advancing fully capable and interoperable information systems to enhance public health preparedness across federal, state and local government and improve electronic exchange of health data and information between clinical health care and all levels of public health. The PHIN investment coordinates with Nationwide Health Information Network (NHIN), a critical portion of the health IT agenda intended to provide a secure, nationwide, interoperable health information infrastructure to connect providers, consumers, and others involved in supporting health and healthcare. PHIN supports the following HHS departmental and CDC agency goals: Supports the HHS Secretary's priorities in three areas: Terrorism Defense, Healthcare Delivery Improvement, and IT Enhancements, Contributes to the CDC goal of People Prepared for Emerging Health Threats, Supports People 2010 campaign to ensure that public health agencies have adequate infrastructure to provide essential public health services. To achieve these goals, PHIN's programmatic approach includes the following: * Supporting the exchange of critical health information between all levels of public health and healthcare, * Developing and promulgating requirements, standards, specifications, and an overall architecture in a collaborative, transparent, and dynamic way, * Monitoring the capability of state and local health departments to exchange information, * Advancing supportive policy, * Providing technical assistance to allow state and local health departments to implement PHIN requirements, * Facilitating communication and information sharing within the PHIN community, * Providing public health agencies with appropriate and timely information to support informed decision making, and * Harmonizing PHIN with other federal initiatives. A core technical component of PHIN is the PHIN Vocabulary Access and Distribution System (VADS), promotes standards-based vocabulary to support consistent information exchange.
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?
2006-12-01
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?)
PHIN supports Expanded e-Government by collaboratively developing standards for the development of fully interoperable information systems to enhance public health preparedness across all levels of government. PHIN supports HHS/CDC goals for Terrorism Defense, Healthcare Delivery Improvement, IT Enhancements, People Prepared for Emerging Health Threats, and the Healthy People 2010/20 campaigns to improve public health agency infrastructure to provide essential public health services.
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 2
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
20. What is the percentage breakout for the total FY2009 funding request for the following? (This should total 100%)
AreaPercentage
Hardware5
Software10
Services80
Other5
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?
n/a
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 Resources0.0000.0000.0000.000
Acquisition Budgetary Resources25.4591.7001.1401.700
Maintenance Budgetary Resources2.1272.2131.6392.371
Government FTE Cost1.7050.8671.3981.440
# of FTEs10101010
2. Will this project require the agency to hire additional FTE's?
no
3. If the summary of spending has changed from the FY2008 President's budget request, briefly explain those changes.
PHIN has now been planned to FY2014. The scope of work for this investment has also been redefined due to a need to expand the focus beyond preparedness to include response. To this end CDC has restructured PHIN Requirements to provide standards needed to exchange vital data to support the mission of improving the public's health. In FY2007, PHIN VADS was upgraded to improve access, search, and distribution capability for Public Health Partners' use. PHINMS was upgraded to enhance secure and rapid data delivery of sensitive health information over the Internet to other local, state, and federal organizations including the CDC. Information such as HIV records, pandemics, and bioterrorism can be transmitted using a variety of methods, including text, graphics, or other file types. These enhancements provide assurance to patients that public health organizations are protecting their privacy and health information.

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
12006S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partners' systems that successfully exchange data using the PHIN data exchange component or systems that comply with the specification52 systems75% increase of partners' systems that successfully exchange data using the PHIN data exchange component or systems that comply with the specificationMet Target
22006S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of new systems adopting the PHIN Functional Requirements. These systems will support a healthier population.TBD20% increase in adoption of the specifications or systems within the PHIN Functional AreasMet Target
32006S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of communication activities or events141 sessions75% increase in communications and education activitiesMet Target
42006S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of new or previously certified systems undergoing certification61 systems100% increase in new or previously certified systems undergoing certificationMet Target
52007S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirements00Undergoing Restructured PHIN Requirements development
62007S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business day70%5% increase5,310
72007S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms produced1025% increase in outreach mechanisms18
82007S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirements00Undergoing Restructured PHIN Requirements development
92008S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirements0Increase by 20 systems9 - lower than expected participation based on restructured PHIN Requirements adoption
102008S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business day5,3105% increase7,284 requests responded to according to measure
112008S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms produced1825% increase in outreach mechanisms25
122008S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirements0Increase by 20 systems0 - Certification evaluation mechanism delayed due to organizational restructuring. Release planned for August 2008
132009S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirements9Increase by 20 systemsTBD
142009S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business day7,2845% increaseTBD
152009S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms produced2525% increase in outreach mechanismsTBD
162009S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirementsTBD based on FY2008Increase by 20 systemsTBD
172010S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirementsTBD based on FY2009Increase by 20 systemsTBD
182010S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business dayTBD based on FY20095% increaseTBD
192010S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms producedTBD based on FY200925% increase in outreach mechanismsTBD
202010S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirementsTBD based on FY2009Increase by 20 systemsTBD
212011S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirementsTBD based on FY2010Increase by 20 systemsTBD
222011S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business dayTBD based on FY20105% increaseTBD
232011S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms producedTBD based on FY201025% increase in outreach mechanismsTBD
242011S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirementsTBD based on FY2010Increase by 20 systemsTBD
252012S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirementsTBD based on FY2011Increase by 20 systemsTBD
262012S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business dayTBD based on FY20115% increaseTBD
272012S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms producedTBD based on FY201125% increase in outreach mechanismsTBD
282012S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirementsTBD based on FY2011Increase by 20 systemsTBD
292013S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirementsTBD based on FY2012Increase by 20 systemsTBD
302013S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business dayTBD based on FY20125% increaseTBD
312013S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms producedTBD based on FY201225% increase in outreach mechanismsTBD
322013S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirementsTBD based on FY2012Increase by 20 systemsTBD
332014S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryCustomer ResultsNew Customers and Market PenetrationNumber of partner systems that successfully exchange data based on the restructured PHIN requirementsTBD based on FY2013Increase by 20 systemsTBD
342014S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryMission and Business ResultsPopulation Health Management and Consumer SafetyPercentage of requests for technical assistance responded to within one business dayTBD based on FY20135% increaseTBD
352014S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryProcesses and ActivitiesParticipationNumber of publications, exhibits, and outreach mechanisms producedTBD based on FY201325% increase in outreach mechanismsTBD
362014S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recoveryTechnologyExternal Data SharingNumber of systems certified to send/receive messages based on restructured PHIN requirementsTBD based on FY2013Increase by 20 systemsTBD

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 Public Health Information Network (PHIN)
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 %
1Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Data ManagementExtraction and Transformation  No Reuse5
2Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Data ManagementData Exchange  No Reuse5
3Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Content ManagementSyndication Management  No Reuse5
4Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Development and IntegrationEnterprise Application Integration  No Reuse2
5Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Management of ProcessesQuality Management  No Reuse5
6Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Customer Initiated AssistanceOnline Help  No Reuse10
7Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Routing and SchedulingOutbound Correspondence Management  No Reuse5
8Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Investment ManagementPortfolio Management  No Reuse5
9Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Data ManagementData Classification  No Reuse2
10Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Investment ManagementStrategic Planning and Mgmt  No Reuse5
11Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Routing and SchedulingInbound Correspondence Management  No Reuse5
12Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Customer Initiated AssistanceOnline Tutorials  No Reuse5
13Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Development and IntegrationData Integration  No Reuse2
14Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.ReportingAd Hoc  No Reuse5
15Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Content ManagementContent Publishing and Delivery  No Reuse5
16Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Management of ProcessesRequirements Management  No Reuse5
17Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Management of ProcessesProgram / Project Management  No Reuse5
18Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Data ManagementMeta Data Management  No Reuse2
19Public Health Information Network (PHIN) (908)PHIN will converge, under a common architecture, strategic public health systems that focus on building national public health IT infrastructure capacity for the exchange, analysis, and leveraging of public health data and information between public health partners and particularly between federal, state, and local jurisdictions.Customer Relationship ManagementContact and Profile Management  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)
1Extraction and TransformationComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
2Extraction and TransformationComponent FrameworkData InterchangeData ExchangeCommon Alerting Protocol by: Organization for the Advancement of Structured Information Standards
3Extraction and TransformationService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
4Data ExchangeService Access and DeliveryService TransportSupporting Network ServicesDirectory Service Markup Language by: Organization for the Advancement of Structured Information Standards
5Data ExchangeService Access and DeliveryService RequirementsLegislative / ComplianceHIPAA by: Federal Department of Health and Human Services
6Data ExchangeService Access and DeliveryService TransportSupporting Network ServicesT1 Carrier by: ANSI
7Data ExchangeComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
8Data ExchangeService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
9Data ExchangeService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
10Data ExchangeService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
11Data ExchangeComponent FrameworkData InterchangeData ExchangeCommon Alerting Protocol by: Organization for the Advancement of Structured Information Standards
12Data ExchangeService Access and DeliveryService TransportSupporting Network ServicesT3 Carrier by: ANSI
13Data ExchangeService Access and DeliveryAccess ChannelsWireless / PDABlackberry by: Research in Motion, LTD.
14Syndication ManagementService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
15Enterprise Application IntegrationService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
16Enterprise Application IntegrationComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
17Quality ManagementService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
18Quality ManagementComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
19Quality ManagementService Access and DeliveryService TransportSupporting Network ServicesDirectory Service Markup Language by: Organization for the Advancement of Structured Information Standards
20Online HelpService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
21Online HelpService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
22Outbound Correspondence ManagementService Access and DeliveryAccess ChannelsWireless / PDABlackberry by: Research in Motion, LTD.
23Outbound Correspondence ManagementService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
24Portfolio ManagementService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
25Data ClassificationComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
26Data ClassificationService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
27Strategic Planning and MgmtService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
28Strategic Planning and MgmtService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
29Inbound Correspondence ManagementService Access and DeliveryAccess ChannelsWireless / PDABlackberry by: Research in Motion, LTD.
30Inbound Correspondence ManagementService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
31Online TutorialsService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
32Online TutorialsService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
33Data IntegrationService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
34Data IntegrationComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
35Ad HocService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
36Ad HocService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
37Content Publishing and DeliveryService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
38Content Publishing and DeliveryService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
39Requirements ManagementService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
40Program / Project ManagementService Access and DeliveryAccess ChannelsWireless / PDABlackberry by: Research in Motion, LTD.
41Program / Project ManagementService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
42Meta Data ManagementComponent FrameworkData InterchangeData ExchangeElectronic Business using XML by: Organization for the Advancement of Structured Information Standards
43Meta Data ManagementService Interface and IntegrationInteroperabilityData Format / ClassificationHealth Level 7 (HL7) by: Health Level Seven, Inc.
44Contact and Profile ManagementService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer 6.0 by: Microsoft Corporation
45Contact and Profile ManagementService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Synchronous Optical Networking by: ANSI
46Contact and Profile ManagementService Access and DeliveryAccess ChannelsWireless / PDABlackberry by: Research in Motion, LTD.
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.
PHIN is an integration architecture for the exchange of public health information among federal, state, and local public health partners. It prescribes requirements for connectling laboratory systems, early event detection, outbreak management, countermeasure and response administration, partner communications and alerting, and cross functional components. Optimal use of government funds is achieved by providing PHIN vocabulary and messaging services to other CDC investments and by using shared CDC IT infrastructure services. PHIN leverages the Federal Health Architecture.

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

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?
no