[Insert Project Name]

1. Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC) [Insert Project Name] Preliminary Design Review (PDR) [Insert Date of PDR]

2. Template Instructions This document is a template for the Preliminary Design Review (PDR). Sections should not be removed from the presentation. If a section is not applicable, please indicate as such and provide an explanation. Additional slides may be added to convey information that you feel is important to share that is not addressed by this template. Please ensure that your presentation is Section 508 compliant by following the URL: http://www.hhs.gov/web/policies/checklistppt.html DELETE THIS SLIDE BEFORE FINALIZING YOUR PRESENTATION

3. Template Revision History DELETE THIS SLIDE BEFORE FINALIZING YOUR PRESENTATION

4. Presenters See this slide’s notes pages for slide instructions.

5. High Level Business Concept [Insert graphic providing a high-level overview of the business process from Section 5 of the Business Case.]

6. Project Information Business Need [Insert condensed business need and drivers from the Business Case or from the AR presentation] Goals/Scope/Purpose [Insert condensed goals/scope from the Business Case and the business and functional purpose from the Requirements Document or from the AR presentation] Stakeholders [Insert stakeholder information from the Business Case or from the AR presentation]

7. Proposed System System Scope [Insert condensed system scope from the High-Level Technical Design.] High Level Functional Requirements [Insert high level functional requirements from the High Level Technical Design.] Summary of Changes [Insert condensed summary of changes of the current system from the High-Level Technical Design (if applicable).]

8. AR/PSR Findings [Identify any recommendations and/or findings from the AR/PSR and their resolution.]

9. Records Management [Describe where the system’s data will reside and identify any data exchanges that may occur. Alternatively, you may attach Section 5.1.6 of the project’s Requirements document.] • Inputs: Identify all data (as well as the format of the data—paper, manual input, electronic data) supplied to the system as well as who/what is supplying the data. • Provide instructions on what happens to the manual/electronic inputs after they are entered into the master file/database and are verified. • Master Files – Provide a detailed description of the data maintained in the system/database. • Provide detailed instructions for the retention and disposition of this data (where will the data be maintained, when will the data be deleted or destroyed). • Outputs: List all reports, data sharing with other Agencies/CMS systems, etc. • Provide instructions for how long the reports are needed for Agency business and when they should be destroyed/deleted. • Is this system replacing a paper-based records system or an existing electronic system?  If electronic, has the migration of the legacy data been addressed?

10. Design Considerations [Summarize the design goals and guidelines, development methods and contingencies, and architectural strategies as described in the System Design Document.]

11. System Architecture [Insert the system architecture diagram depicting the overall, integrated structure of the system in terms of presentation, application and data regions including data storage and manipulation, user and external interfaces from Sections 6.4, 7.2, 8 and 12 of the System Design Document respectively.]

12. Response Data • Operational / System Environment • System Interconnection / Information Sharing • System Security Level • E-Authentication Level: See this slide’s notes pages for slide instructions.

13. Test Plan [Insert the testing approach / strategy from Section 5 of the Test Plan.]

14. Release Plan [Insert the release content and schedule from Sections 5.2.1 and 5.2.2 of the Release Plan.]

15. Data Conversion [Insert the data conversion scope from Section 5.1 of the Data Conversion Plan.]

16. Project Management Update:Status [Provide an update on the status of the project.]

17. Project Management Update:Risks & Issues [Provide an update on the project risks and issues, including the probability of occurrence and the mitigation for each risk.]

18. Project Management Update:Cost & Schedule • Cost • Schedule See this slide’s notes pages for slide instructions.

19. Project Management Update:Deliverables Status [Provide an update on the status of the deliverables required for the project as documented in the Project Process Agreement. Also provide an update on the status of your Information Security Certification & Authorization process.]

20. Conclusion of Preliminary Design Reviewfor [insert project name]