Requirements for Re-Platforming: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) Created page with "This is an index for content relevant to the U of M IT team in proposing a solution for hosting our database. * 15-20 users on laptops * 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) * Approximately 1.1GB (core) + 200MB (PHI) + (1.2+0.36GB) (Labs) + est 500MB assorted legacy data * CCMDB_D..." |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 13: | Line 13: | ||
* Who will be allowed to program and implement changes on this system, and what would the timelines be? | * Who will be allowed to program and implement changes on this system, and what would the timelines be? | ||
[[Category: | [[Category: UM MedIT Re-platforming]] | ||
Revision as of 13:58, 13 March 2025
This is an index for content relevant to the U of M IT team in proposing a solution for hosting our database.
- 15-20 users on laptops
- 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)
- Approximately 1.1GB (core) + 200MB (PHI) + (1.2+0.36GB) (Labs) + est 500MB assorted legacy data
- CCMDB_Data_Structure
- number of fields not necessarily relevant because of Entity–attribute–value model of the L Tmp V2 table
- Auto Data Dictionary
Our questions:
- How would collectors enter the data, and would we be able to have the same high level of cross checks and fine-tuning of their environment as we do now? (ask us for examples)
- Who will be allowed to program and implement changes on this system, and what would the timelines be?