eHealth Exchange (eHX) AWS S3 Support
- Aric van Kan
Analytics
The APHL Informatics Project Discovery Document provides APHL Leadership with an overview of a new project to facilitate approval and prepare for project start. This document focuses on the initial what of a new project, not why, how, or when. This document is provided to the Project Manager after approval.
Note: this Discovery Document is to define projects not programs.
This document is not usually updated after the Project Startup.
Project Name | eHealth Exchange (eHX) AWS S3 Support |
Project Type | Development/New Scope Expansion |
Related APHL Program (if any) |
|
APHL Project Owner |
|
Project Manager |
|
Sponsor |
|
Target Audience | Management, Project Manager, Technical Leads |
Created By | Sponsor or APHL Project Owner |
When Created | At project initiation |
Document Date: (MM/DD/YYYY) | Mar 1, 2024 |
Document Status | In Development In Review Final |
Template version # and Date | (v.4) Mar 1, 2024 |
Approved By and Date | Approved by ---, APHL Project Lead, on Mar 27, 2024 (enter date once approved) Approved by ---, Sponsor, on Mar 27, 2024 (enter date once approved) Approved by ---, APHL PMO, on Mar 27, 2024 (enter date once approved) |
1 PROJECT OVERVIEW
In the table below, describe each project characteristic with a brief statement of a couple of sentences, as needed.
Background |
|
Project Purpose |
|
Related Project(s) |
|
Project Scope |
|
Assumptions / Boundaries |
|
Resources |
|
Timeline |
|
Performance Criteria / Success Factors |
|
Issues / Constraints |
|
Risks |
|
Will project need O&M support when development is completed? | Yes No N/A |
Next Steps |
|
2 PROJECT CLASSIFICATIONS
Characteristic | Low | Medium | High |
|---|---|---|---|
Complexity | The deliverables, requirements, and technology are well understood and have been implemented before. It is anticipated that solution will be straightforward to implement and will have minimal to low impact on other systems and services. | There is some uncertainty with regards to the deliverables, requirements, or technology. Or, the solution is of medium technical complexity with moderate impact to other systems and services. | The team may be attempting to implement deliverables, requirements, or technology that is not well understood. Even if these things are well understood, the solution itself may be technically complex, requiring coordination across many systems and services, disciplines and teams. |
Impact | A project may be considered to have a low impact for several reasons. 1) The project will affect a small number of public health partners. 2) It has a low profile or low urgency. 3) It is not a critical dependency for other projects, systems, or services. | A project with a medium impact will affect a moderate number of public health partners; the project may have some urgency or visibility; or it may be a dependency for other projects, systems, or services. | A project may be considered to have a high impact for several reasons. 1) It will affect a large number of public health partners, such as STLTs, CDC programs, HCOs, etc. 2) It has a high visibility and high urgency for the public health community. 3) Many other systems and services are dependent on the project’s success. |
Resources / Interested Parties | A low designation indicates that the project has a limited number of interested parties to coordinate and who will determine the project’s goals and affect its progress. | A medium designation indicates that the project has a moderate number of interested parties to coordinate and whose ideas and input will be important to realizing the project’s goals and deliverables. | A high designation indicates that the project will involve complicated coordination and input from multiple interested parties, such as STLTs, CDC programs, AIMS developers, HCOs, and other vendors or project teams, and that their ideas and input will be critical to realizing the project’s goals and deliverables. |
Alignment | Project at customer request; Not consistent with APHL strategic direction. | Project aligns partially to APHL strategic direction. | Project aligns directly with APHL goals or key initiatives. |
Urgency | Project has no required completion date. | Project has a flexible completion date. | Project has aggressive deadlines. |
Dependency
| Does not rely upon other projects or availability of resources. | Some progress can be made, but completion relies on other projects or availability of resources. | Any progress relies on other projects or availability of resources. |
3 SME/RESOURCE NEEDS
Role | LOE | Notes/Comments |
|---|---|---|
Project Management & Coordination |
|
|
Terminology |
|
|
Data Integration |
|
|
Software Engineer |
|
|
Business Analysis |
|
|
AIMS Integration |
|
|
AIMS Development |
|
|
AIMS DevOps |
|
|
AIMS SecOps |
|
|
AIMS Production Support |
|
|
Other |
|
|
4 KEY INTERESTED PARTIES
APHL Informatics | CDC | ||
APHL Infectious Disease | CSTE | ||
APHL Newborn Screening | PHLs | ||
PHAs | Healthcare Providers | ||
Other: |
|
|
5 DISCOVERY STATE OUTCOMES
Decision | Stage | Comments |
|---|---|---|
Move forward to Planning Stage |
| |
More information requested [come back] |
| |
Cancel |
| |
Hold for some other reason. |
|