| | Exhibit 300 (BY2009) - Public Health Information Network (PHIN), Centers for Disease Control and PreventionPART ONE
OVERVIEW
- 1. Date of Submission:
- 2008-02-04
- 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 FY2009?
- 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 all levels of government and improve electronic exchange of health data and information between clinical health care and all levels of public health (federal, state, and local.) The PHIN investment also 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 that will connect providers, consumers, and others involved in supporting health and healthcare. In 2005, a change of direction was implemented resulting from a comprehensive review with internal and external stakeholders. Accordingly, PHIN was restructured to support the following HHS departmental and CDC agency goals: o supports the HHS Secretary's priorities in three areas: Terrorism Defense, Healthcare Delivery Improvement, and IT Enhancements, o contributes to the CDC goal of People Prepared for Emerging Health Threats, o supports People 2010 campaign to ensure that public health agencies have adequate infrastructure to provide essential public health services. PHIN defines and disseminates national standards and requirements to achieve capabilities and interconnectedness of systems across public health. PHIN Vocabulary Access and Distribution System (VADS), promotes standards-based vocabulary to support consistent information exchange. PHIN Messaging Service (PHINMS) provides secure and rapid data exchange. Each functional area's impact is addressed is described below: o Early detection of disease reduces the public health burden by allowing earlier countermeasure activities. o Outbreak management allows for the capture and management of data associated with an investigation. o Connecting laboratory systems permits electronic exchange tests and results with partners, leading to improved access to information and greater tracking capability. o Countermeasure and response administration provides the ability to manage and track measures taken to contain an outbreak or event, or to provide protection against a possible outbreak or event.
- 9. Did the Agency's Executive/Investment Committee approve this request?
- yes
- 9.a. If "yes," what was the date of this approval?
- 2007-06-26
- 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?
- Mid/Journeyman-level
- 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?)
- Expanded Electronic Government: PHIN is CDC's vision for advancing fully capable and interoperable information systems to enhance public health preparedness across all levels of government. PHIN is a national initiative to improve the electronic exchange of health data and information between clinical care and all levels of public health (federal, state, and local) and sets the framework for building and enhancing interoperable data systems to improve the public's health.
- 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%)
Area | Percentage |
---|
Hardware | 1 | Software | 1 | Services | 88 | Other | 10 |
- 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.
Name | Alice M. Brown | Phone Number | 770-488-8223 | Title | IT Security Project Manager | Email | AMBrown1@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 -2006 | PY 2007 | CY 2008 | BY 2009 |
---|
Planning Budgetary Resources | 0.000 | 0.000 | 0.000 | 0.000 | Acquisition Budgetary Resources | 23.759 | 1.700 | 1.700 | 1.598 | Maintenance Budgetary Resources | 0.000 | 2.127 | 2.149 | 2.191 | Government FTE Cost | 0.855 | 0.850 | 0.867 | 0.884 | # of FTEs | 4 | 7 | 7 | 7 |
- 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 FY2013. 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.
Row | Fiscal Year | Strategic Goal Supported | Measurement Area | Measurement Grouping | Measurement Indicator | Baseline | Planned Improvement to the Baseline | Actual Results |
---|
1 | 2006 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partners' systems that successfully exchange data using the PHIN data exchange component or systems that comply with the specification | 52 systems | 75% increase of partners' systems that successfully exchange data using the PHIN data exchange component or systems that comply with the specification | Met Target | 2 | 2006 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Number of new systems adopting the PHIN Functional Requirements. These systems will support a healthier population. | TBD | 20% increase in adoption of the specifications or systems within the PHIN Functional Areas | Met Target | 3 | 2006 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of communication activities or events | 141 sessions | 75% increase in communications and education activities | Met Target | 4 | 2006 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of new or previously certified systems undergoing certification | 61 systems | 100% increase in new or previously certified systems undergoing certification | Met Target | 5 | 2007 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partner systems that successfully exchange data based on the restructured PHIN requirements | 0 | 0 | Undergoing Restructured PHIN Requirements development | 6 | 2007 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Percentage of requests for technical assistance responded to within one business day | 70% | 5% increase | Met target | 7 | 2007 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of publications, exhibits, and outreach mechanisms produced | 10 | 25% increase in outreach mechanisms | Met target | 8 | 2007 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of systems certified to send/receive messages based on restructured PHIN requirements | 0 | 0 | Undergoing Restructured PHIN Requirements development | 9 | 2008 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partner systems that successfully exchange data based on the restructured PHIN requirements | 0 | Increase by 20 systems | TBD | 10 | 2008 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Percentage of requests for technical assistance responded to within one business day | TBD based on FY2007 | 5% increase | TBD | 11 | 2008 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of publications, exhibits, and outreach mechanisms produced | TBD based on FY2007 | 25% increase in outreach mechanisms | TBD | 12 | 2008 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of systems certified to send/receive messages based on restructured PHIN requirements | TBD based on FY2007 | Increase by 20 systems | TBD | 13 | 2009 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partner systems that successfully exchange data based on the restructured PHIN requirements | TBD based on FY2008 | Increase by 20 systems | TBD | 14 | 2009 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Percentage of requests for technical assistance responded to within one business day | TBD based on FY2008 | 5% increase | TBD | 15 | 2009 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of publications, exhibits, and outreach mechanisms produced | TBD based on FY2008 | 25% increase in outreach mechanisms | TBD | 16 | 2009 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of systems certified to send/receive messages based on restructured PHIN requirements | TBD based on FY2008 | Increase by 20 systems | TBD | 17 | 2010 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partner systems that successfully exchange data based on the restructured PHIN requirements | TBD based on FY2009 | Increase by 20 systems | TBD | 18 | 2010 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Percentage of requests for technical assistance responded to within one business day | TBD based on FY2009 | 5% increase | TBD | 19 | 2010 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of publications, exhibits, and outreach mechanisms produced | TBD based on FY2009 | 25% increase in outreach mechanisms | TBD | 20 | 2010 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of systems certified to send/receive messages based on restructured PHIN requirements | TBD based on FY2009 | Increase by 20 systems | TBD | 21 | 2011 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partner systems that successfully exchange data based on the restructured PHIN requirements | TBD based on FY2010 | Increase by 20 systems | TBD | 22 | 2011 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Percentage of requests for technical assistance responded to within one business day | TBD based on FY2010 | 5% increase | TBD | 23 | 2011 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of publications, exhibits, and outreach mechanisms produced | TBD based on FY2010 | 25% increase in outreach mechanisms | TBD | 24 | 2011 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of systems certified to send/receive messages based on restructured PHIN requirements | TBD based on FY2010 | Increase by 20 systems | TBD | 25 | 2012 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partner systems that successfully exchange data based on the restructured PHIN requirements | TBD based on FY2011 | Increase by 20 systems | TBD | 26 | 2012 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Percentage of requests for technical assistance responded to within one business day | TBD based on FY2011 | 5% increase | TBD | 27 | 2012 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of publications, exhibits, and outreach mechanisms produced | TBD based on FY2011 | 25% increase in outreach mechanisms | TBD | 28 | 2012 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of systems certified to send/receive messages based on restructured PHIN requirements | TBD based on FY2011 | Increase by 20 systems | TBD | 29 | 2013 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Customer Results | New Customers and Market Penetration | Number of partner systems that successfully exchange data based on the restructured PHIN requirements | TBD based on FY2012 | Increase by 20 systems | TBD | 30 | 2013 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Mission and Business Results | Population Health Management and Consumer Safety | Percentage of requests for technical assistance responded to within one business day | TBD based on FY2012 | 5% increase | TBD | 31 | 2013 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Processes and Activities | Participation | Number of publications, exhibits, and outreach mechanisms produced | TBD based on FY2012 | 25% increase in outreach mechanisms | TBD | 32 | 2013 | S.O. 2.3 - Promote and encourage preventive health care, including mental health, lifelong healthy behaviors, and recovery | Technology | External Data Sharing | Number of systems certified to send/receive messages based on restructured PHIN requirements | TBD based on FY2012 | Increase by 20 systems | 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 Public Health Information Network (PHIN)
- 3. Is this investment identified in a completed (contains a target architecture) and approved segment architecture?
- yes
- 3.a. If yes, provide the name of the segment architecture as provided in the agency’s most recent annual EA Assessment.
- Public Health Information Network
- 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 | Reused Component Name | Reused UPI | Internal or External Reuse? | Funding % |
---|
1 | Inbound Correspondence Management | Defines the set of capabilities that manage externally initiated communication between an organization and its stakeholders. | Routing and Scheduling | Inbound Correspondence Management | | | No Reuse | 5 | 2 | Outbound Correspondence Management | Defines the set of capabilities that manage internally initiated communication between an organization and its stakeholders. | Routing and Scheduling | Outbound Correspondence Management | | | No Reuse | 5 | 3 | Syndication Management | Defines the set of capabilities that control and regulate an organization's brand. | Content Management | Syndication Management | | | No Reuse | 5 | 4 | Content Publishing and Delivery | Defines the set of capabilities that allow for the propagation of interactive programs. | Content Management | Content Publishing and Delivery | | | No Reuse | 5 | 5 | Ad Hoc | Defines the set of capabilities that support the use of dynamic reports on an as needed basis. | Reporting | Ad Hoc | | | No Reuse | 5 | 6 | Data Classification | Defines the set of capabilities that allow the classification of data. | Data Management | Data Classification | | | No Reuse | 2 | 7 | Meta Data Management | Defines the set of capabilities that support the maintenance and administration of data that describes data. | Data Management | Meta Data Management | | | No Reuse | 2 | 8 | Extraction and Transformation | Defines the set of capabilities that support the manipulation and change of data. | Data Management | Extraction and Transformation | | | No Reuse | 5 | 9 | Data Exchange | Defines the set of capabilities that support the interchange of information between multiple systems or applications; includes verification that transmitted data was received unaltered. | Data Management | Data Exchange | | | No Reuse | 5 | 10 | Enterprise Application Integration | Defines the set of capabilities that support the redesigning of disparate information systems into one system that uses a common set of data structures and rules. | Development and Integration | Enterprise Application Integration | | | No Reuse | 2 | 11 | Data Integration | Defines the set of capabilities that support the organization of data from separate data sources into a single source using middleware or application integration and the modification of system data models to capture new information within a single system. | Development and Integration | Data Integration | | | No Reuse | 2 | 12 | Program / Project Management | Defines the set of capabilities that manage and control a particular effort of an organization. | Management of Processes | Program / Project Management | | | No Reuse | 5 | 13 | Quality Management | Defines the set of capabilities that help determine the level that a product or service satisfies certain requirements. | Management of Processes | Quality Management | | | No Reuse | 5 | 14 | Requirements Management | Defines the set of capabilities that gather, analyze and fulfill the needs and prerequisites of an organization's efforts. | Management of Processes | Requirements Management | | | No Reuse | 5 | 15 | Strategic Planning and Mgmt | Defines the set of capabilities that support the determination of long-term goals and the identification of the best approach for achieving those goals. | Investment Management | Strategic Planning and Mgmt | | | No Reuse | 5 | 16 | Portfolio Management | Defines the set of capabilities that support the administration of a group of investments held by an organization. | Investment Management | Portfolio Management | | | No Reuse | 5 | 17 | Online Tutorials | Defines the set of capabilities that provide an electronic interface to educate and assist customers. | Customer Initiated Assistance | Online Tutorials | | | No Reuse | 5 | 18 | Online Help | Defines the set of capabilities that provide an electronic interface to customer assistance. | Customer Initiated Assistance | Online Help | | | No Reuse | 10 | 19 | Contact and Profile Management | Defines the set of capabilities that provide a comprehensive view of all customer interactions, including calls, email, correspondence and meetings; also provides for the maintenance of a customer's account, business and personal information. | Customer Relationship Management | Contact and Profile Management | | | 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 | Data Exchange | Service Access and Delivery | Access Channels | Wireless / PDA | Blackberry | 2 | Inbound Correspondence Management | Service Access and Delivery | Access Channels | Wireless / PDA | Blackberry | 3 | Outbound Correspondence Management | Service Access and Delivery | Access Channels | Wireless / PDA | Blackberry | 4 | Program / Project Management | Service Access and Delivery | Access Channels | Wireless / PDA | Blackberry | 5 | Contact and Profile Management | Service Access and Delivery | Access Channels | Wireless / PDA | Blackberry | 6 | Data Exchange | Component Framework | Data Interchange | Data Exchange | Common Alerting Protocol | 7 | Extraction and Transformation | Component Framework | Data Interchange | Data Exchange | Common Alerting Protocol | 8 | Data Exchange | Service Access and Delivery | Service Transport | Supporting Network Services | Directory Service Markup Language | 9 | Quality Management | Service Access and Delivery | Service Transport | Supporting Network Services | Directory Service Markup Language | 10 | Data Exchange | Component Framework | Data Interchange | Data Exchange | Electronic Business using XML | 11 | Data Classification | Component Framework | Data Interchange | Data Exchange | Electronic Business using XML | 12 | Meta Data Management | Component Framework | Data Interchange | Data Exchange | Electronic Business using XML | 13 | Extraction and Transformation | Component Framework | Data Interchange | Data Exchange | Electronic Business using XML | 14 | Enterprise Application Integration | Component Framework | Data Interchange | Data Exchange | Electronic Business using XML | 15 | Data Integration | Component Framework | Data Interchange | Data Exchange | Electronic Business using XML | 16 | Quality Management | Component Framework | Data Interchange | Data Exchange | Electronic Business using XML | 17 | Data Exchange | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 18 | Data Classification | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 19 | Meta Data Management | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 20 | Extraction and Transformation | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 21 | Enterprise Application Integration | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 22 | Data Integration | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 23 | Quality Management | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 24 | Strategic Planning and Mgmt | Service Interface and Integration | Interoperability | Data Format / Classification | Health Level 7 (HL7) | 25 | Data Exchange | Service Access and Delivery | Service Requirements | Legislative / Compliance | HIPAA | 26 | Data Exchange | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 27 | Inbound Correspondence Management | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 28 | Outbound Correspondence Management | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 29 | Content Publishing and Delivery | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 30 | Ad Hoc | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 31 | Online Tutorials | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 32 | Online Help | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 33 | Contact and Profile Management | Service Platform and Infrastructure | Hardware / Infrastructure | Wide Area Network (WAN) | SONET, Bellsouth | 34 | Data Exchange | Service Access and Delivery | Service Transport | Supporting Network Services | T1 | 35 | Data Exchange | Service Access and Delivery | Service Transport | Supporting Network Services | T3 | 36 | Data Exchange | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 37 | Syndication Management | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 38 | Content Publishing and Delivery | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 39 | Ad Hoc | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 40 | Program / Project Management | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 41 | Requirements Management | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 42 | Strategic Planning and Mgmt | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 43 | Portfolio Management | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 44 | Online Tutorials | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 45 | Online Help | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 | 46 | Contact and Profile Management | Service Access and Delivery | Access Channels | Web Browser | Windows Internet Explorer 6.0 |
- 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.
- This investment leverages: Federal Health Architecture (FHA)
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?
- 2006-05-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?
- yes
- 2. Is the CV% or SV% greater than ± 10%?
- no
- 3. Has the investment re-baselined during the past fiscal year?
- no
|
|
|