Change Description (incl. Benefits)
The eChart table itself can take up a substantial amount of space in the database. It seems to be vestigial from Caisi, and the data in it seems to be redundant.
OSCAR Interaction points
OSCAR writes/reads from the eChart table in several places.
Integration risks
- We will need to make sure removing this table does not render OSCAR unusable or unstable
Risk if not incorporated
- potentially huge amounts of wasted space used up by the eChart table (we have a client that has a DB size of 70GB, 55GB of which are just the eChart).
Minimum testing requirements/process
- Go through regular clinic workflows once eChart is removed, and make sure everything works as expected
- Adding some new unit tests where eChart was removed would be a nice idea
Training requirements to support changes
- none from the users perspective
Time Estimate
10 days
