Centralized data.accdb: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
mNo edit summary
m Text replacement - "[[Category: " to "[[Category:"
 
(61 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Data Repository containing:
''see also [[Centralized_data.accdb Change Log]]
* [[Serial number]]
Centralized.data.mdb is a data repository containing a de-identified copy of all data sent from Critical Care and Medicine. Indentifiers are stored in [[PHI.mdb]] which is accessible only to [[:Category:Main Office|main office]].
* [[Location field|Location]]
==Live Date==
* [[Admit%2C_Transfer_and_Discharge_date_and_time#Admit_Date_and_Time | admit, transfer and discharge dates and times]]
May 20, 2014
* [[Survive / Expired]]
* [[Med Var 1 - Admit-from Ward]] you will be able to send without this, but Julie will not get all the data she needs to link patient stays together
* [[Med Var 2 - Discharge-to Ward]] you will be able to send without this, but Julie will not get all the data she needs to link


== How to populate this ==
== Location ==
{{Discussion}}
{{Regionalserver|Output\[[Centralized_data.accdb]]}}
We talked today at the ICU Task Meeting about whether or not to populate this table by push at every send. Julie was concerned that we would still not have as up-to-date data that way as we might be able to. One suggestion was to pull it from the backups instead. This could be done, but would need to happen very regularly to not miss patients who, e.g. arrive and get discharged on Wednesday morning, get entered by the collector, sent and deleted. Might need a multi-prong approach, where this table is push-populaetd when collectors send, '''and''' pull populated whenever Julie needs data. That way no patients would get missed and fresh data would be available when needed. I am planning to populate this table with a pair of queries: first one updating records that are already present, second one adding records that are new. Thoughts? Ttenbergen 17:09, 2012 December 21 (EST)


== Availability ==
[[Centralized_data.accdb]] might not be available at its network location outside of [[Designated sending times]].  See [[Pull down centralized data.vbs]] if it needs to be retrieved locally.
==Password==
Located: {{M:|Passwords_MainOffice_use}}
== How does data get into [[Centralized_data.accdb]] ==
see [[Sending Patients]]
== Dependencies ==
[[TISS28 Data.mdb]] pulls data from [[Centralized_data.accdb]].
== Legacy ==
[[Conversion of Centralized data.mdb to Centralized data.accdb]] - some places refer to a .mdb, same file earlier version
== Related articles ==
{{Related Articles}}


[[Category:Data Repository]]
[[Category:Data Repository]]
[[Category:Password]]
[[Category:Centralized_data.accdb| *]]

Latest revision as of 10:32, 30 July 2025

see also Centralized_data.accdb Change Log Centralized.data.mdb is a data repository containing a de-identified copy of all data sent from Critical Care and Medicine. Indentifiers are stored in PHI.mdb which is accessible only to main office.

Live Date

May 20, 2014

Location

Regional Server\​Output\Centralized_data.accdb\\ad.wrha.mb.ca\WRHA\REGION\SHARED\ICU_DATA_COLLECTION\Output\Centralized_data.accdb

Availability

Centralized_data.accdb might not be available at its network location outside of Designated sending times. See Pull down centralized data.vbs if it needs to be retrieved locally.

Password

Located: M:\​Passwords_MainOffice_use (full address: \\ad.wrha.mb.ca\wrha\HSC\shared\WRHA\WRHA_CCMED\Passwords_MainOffice_use)

How does data get into Centralized_data.accdb

see Sending Patients

Dependencies

TISS28 Data.mdb pulls data from Centralized_data.accdb.

Legacy

Conversion of Centralized data.mdb to Centralized data.accdb - some places refer to a .mdb, same file earlier version

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Centralized_data.accdb&oldid=165972"