Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Pay down some CIE tech debt #34805

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions products/health-care/checkin/engineering/rfc-tech-debt-payoff.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# RFC: Time to pay down some debt

**To be Reviewed By:** All Check-in Experience (CIE) contributors

**Authors:** Patrick Bateman;

**Status:** **Draft** | Discussion | Active | Dropped | Superseded

Superseded by: N/A

Related: N/A

## Problem
The speed at which CIE has been developed has led to under-investment in some key reliability and stability areas. Continued pushes for additional feature development preclude making these investments. The CIE does not have the capacity to take on feature development and make the necessary reliability and stability investments at the same time.

### Anti-Goals
Attempt to correct the reliability or stability of systems or processes beyond the CIE team's control or influence.

## Solution
Pause feature development for two weeks and focus all CIE efforts on the following areas:

### Increase system-level integration test coverage
- need to decrease frequency of breaking changes making it any env
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- need to decrease frequency of breaking changes making it any env
- need to decrease frequency of breaking changes making it into any environment


### Health check endpoints
- simple ping to monitor availability and alert immediately if component is not reachable

### Cross system traceability
- each transaction should be positively traceable across all parts of the system

### True `dev` and `staging` environments
- need separate VistAs?
- need appropriate env parity with VSE clinical app

### Improve local development tooling
- run various CIE components locally

### Establish load testing protocol and run before scaling
- load test across all possible components

### Enhance testing availability and access
- need more appointment slots / different way of creating new appointments for testing
- how will we handle when lots of people are testing