Requirements for Re-Platforming

This is an index for content relevant to the U of M IT team in proposing a solution for hosting our database.

Repeated failure points we should address before going too far

We have had many failed attempts at re-platforming. The technical change would be tedious but doable, the sticking points have always been around the following, so we should discuss these before planning too much further.

governance of any implemented system
data ownership
support model
our team's continued ability to change this as needed

Relatively Hard Facts

15-20 users on laptops, sometimes working from home, sometimes not connected to the network due to lack if wifi
About 2-2.5GB of data altogether as stored in various MS Access DBs (size may vary on other platforms)
Has several highly customized front-ends that facilitates efficient and low-error data entry
- facilitates data entry from a daily dump received from ADT
Data we need to store is in Auto Data Dictionary
- it is currently stored in CCMDB Data Structure - this structure could be stored differently but would cause large changes
We have (and continuously improve) Data Integrity Checks

Current Implementation

system of intermittently linked MS Access databases with a fair bit of automation
facilitated interfaces with Shared Health systems (we request and receive data in files that we import as either temporary or permanent data)
number of fields not necessarily relevant because of Entity–attribute–value model of the L Tmp V2 table