Transition to Database Server: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
we have a server!
mNo edit summary
Line 1: Line 1:
CCMDB will eventually outgrow Microsoft Access as a storage format. We are investigating storing the data with [[Decision Support Services]].  
CCMDB will eventually outgrow Microsoft Access as a storage format for our [[Centralized_data.mdb]]. We are investigating storing the data with [[Decision Support Services]].  
 
== Technical considerations ==
WRHA Department "Analytics & Business Intelligence" has given us access to a database on their database server where we would be able to store our data. The technical groundwork is in place: we can add/edit/remove tables and access them via an MS Access front end through ODBC.
 
=== Things that would need to work to get started ===
One question that remains is:
* {{Discussion}} Julie, can you confirm that SAS would be able to connect to an MS SQL Server via ODBC? Ttenbergen 22:02, 2018 March 14 (CDT)
 
=== Future Dreams ===
* would we be allowed to run MS Reporting Services reports through this? Kym's group uses these with their Accuro data, it's a decent way to get data to a controlled group of users almost real-time
 
== Administrative and governance considerations ==
We now need to work out the following: {{discussion}}
* 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?
 


*2018-03-14 We have a database on their server now. Trevor is leaving, new contact is Phil Jarman. We may want to decide where this fits on our priority list.
*2016-10-31 Call from Trevor, booked meeting for show-and-tell for Nov 21.
*2016-10-24 sent follow-up email
*2016-10-12 sent follow-up email
*2016-10-03-- Meeting booked for.
*2016-09-22 emailed Trevor with likely structure.
*2016-09-22 sent email about how to get data to Trevor
*2016-09-19 made new structure; asked Trevor how to get it to him.
*2016-09-15 met w Dr Roberts and confirmed it’s ok to go ahead with preliminary testing
*2016-09-08 discussion with Trevor Strome
**ODBC connections should be possible
***Ability write and ? change tables
**Sticking point: auditing
**Terms and conditions changes – spongy answers
**Reporting: sql mgr, then anything that has ODBC connectivity SSRS MS reporting services
*Funding? …if there is a cost we want to keep it reasonable (can’t get better answer)
*Ownership of data? Will others look into our data
**Some should be accessible by all or many, to be discussed with owners
**Research by eg U of M special use of would go back to owners
*2016-08-04 Trevor emailed that things should start in Sept/Oct and we will need to discuss architecture. Asked for scope.
*2016-08-03 emailed for update
*2016-06-12 replied to let me know if I can help
Trevor: “We’ve made some very positive progress in bringing our SQL server on-line and accessing much of our other clinical datamarts (i.e., EDIS, ADT, etc) through direct queries. There are still a few governance/policy annoyances that we’re navigating, but overall things are looking good. If we connect in the next few weeks I should be able to provide you more information, and we can begin to sketch out how an architecture might look.”
*2016-06-02 emailed for follow-up
*2016-05-19 Trevor Strome (DSS) thinks there might be a way to get us a SQL server to store our data; waiting to hear back.


[[Category: eHealth]]
[[Category: eHealth]]
[[Category: Warehouse]]

Revision as of 21:02, 2018 March 14

CCMDB will eventually outgrow Microsoft Access as a storage format for our Centralized_data.mdb. We are investigating storing the data with Decision Support Services.

Technical considerations

WRHA Department "Analytics & Business Intelligence" has given us access to a database on their database server where we would be able to store our data. The technical groundwork is in place: we can add/edit/remove tables and access them via an MS Access front end through ODBC.

Things that would need to work to get started

One question that remains is:

  • Template:Discussion Julie, can you confirm that SAS would be able to connect to an MS SQL Server via ODBC? Ttenbergen 22:02, 2018 March 14 (CDT)

Future Dreams

  • would we be allowed to run MS Reporting Services reports through this? Kym's group uses these with their Accuro data, it's a decent way to get data to a controlled group of users almost real-time

Administrative and governance considerations

We now need to work out the following: Template:Discussion

  • 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?
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Transition_to_Database_Server&oldid=107943"