Software and architecture patterns
| HCL_SUS3. Does your organization monitor workload activity and remove or refactor components that are no longer necessary? |
|---|
Analyze demand on workloads to identify components that can be removed or refactored. Then, engage component owners and stakeholders to redesign clinical workflows, and decrease workload infrastructure
Some healthcare delivery systems and large independent software vendors (ISV) have sprawling IT footprints with numerous siloed systems. Identifying and removing or refactoring components with little or no use can simplify workflows, decrease cost, and improve sustainability. Cloud archives can minimize the cost of retaining data from retired components.
| HCL_SUS4. How do you optimize the impact of and applications and the equipment that run them? |
|---|
Evaluate the overall impact of applications, devices, and equipment
As documented in the Sustainability pillar of the AWS Well-Architected Framework, it is recommended to optimize impact on customer devices and equipment. For example, as new features are released for a healthcare application, build those features as backward compatible, minimizing the need for new hardware. Additionally, evaluate the potential impact of new or upgraded hardware requirements to minimize the overall impact when architecting new workloads or features.
