Re-platforming: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) m Text replacement - "[[Centralized_data.accdb]]" to "Centralized_data.accdb" |
||
(19 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
CCMDB will eventually outgrow Microsoft Access as a storage format for our [[Centralized_data. | CCMDB will eventually outgrow Microsoft Access as a storage format for our [[Centralized_data.accdb]]. | ||
== Technical considerations == | == Technical considerations == | ||
* | * [[Requirements for Re-Platforming]] | ||
== Administrative and governance considerations == | == Administrative and governance considerations == | ||
Line 16: | Line 14: | ||
** would we be able to access this and report from this via SQL reporting (a system Kym's group uses for real-time available reports for Accuro, which ties into the same type of database system) | ** would we be able to access this and report from this via SQL reporting (a system Kym's group uses for real-time available reports for Accuro, which ties into the same type of database system) | ||
=== Log === | === Log === | ||
* | * [[Task Team Meeting - Rolling Agenda and Minutes 2025#ICU Database Task Group Meeting – June 18, 2025|2025-06-18]] - due to reorganization at the level of central University of Manitoba IT, our plan/hope for [[Re-platforming to UM MedIT undetermined platform]] is on hold for an unknown period. | ||
* 2024-01-24 - [[Re-platforming to UM MedIT undetermined platform]] | |||
* 2023-03 - [[Re-platforming to SalesForce (failed)]] | |||
* | * 2019-08 - [[Re-platforming to CHI (failed)]] | ||
* | * 2019-07-24 - [[Re-platforming to REDCap (failed)]] | ||
* | * 201? - [[Re-platforming to DSS SQL Server (failed)]] | ||
* 201? - [[Re-platforming to CCMDB Server (failed)]] | |||
* | * 2008-ish: [[Re-platforming to Oracle Apex (failed)]] | ||
* | |||
* | |||
* | |||
== Related articles == | == Related articles == | ||
{{Related Articles}} | {{Related Articles}} | ||
[[Category:Re-platforming | *]] | |||
[[Category:eHealth]] | [[Category:eHealth]] | ||
[[Category:Warehouse]] | [[Category:Warehouse]] | ||
[[Category:Data Repository]] | [[Category:Data Repository]] |
Latest revision as of 14:54, 23 July 2025
CCMDB will eventually outgrow Microsoft Access as a storage format for our Centralized_data.accdb.
Technical considerations
Administrative and governance considerations
We now need to work out the following:
- What would be the terms and conditions of us using this repository
- who owns the data?
- how will this be funded?
- how do we navigate giving additional people access to the data?
- will we be able to give partial access to data to people? Technically this is obviously possible, but would we be allowed to do this, and if so, would we be allowed to manage this ourselves?
- would we be able to access this and report from this via SQL reporting (a system Kym's group uses for real-time available reports for Accuro, which ties into the same type of database system)
Log
- 2025-06-18 - due to reorganization at the level of central University of Manitoba IT, our plan/hope for Re-platforming to UM MedIT undetermined platform is on hold for an unknown period.
- 2024-01-24 - Re-platforming to UM MedIT undetermined platform
- 2023-03 - Re-platforming to SalesForce (failed)
- 2019-08 - Re-platforming to CHI (failed)
- 2019-07-24 - Re-platforming to REDCap (failed)
- 201? - Re-platforming to DSS SQL Server (failed)
- 201? - Re-platforming to CCMDB Server (failed)
- 2008-ish: Re-platforming to Oracle Apex (failed)