Centralized data.accdb: Difference between revisions
TOstryzniuk (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
Centralized.data.mdb is a data | ''see also [[Centralized data.mdb Change Log]] | ||
Centralized.data.mdb is a data repository containing a de-identified copy of all data sent from Critical Care and Medicine. De-identified by excluding chart, phin, names, and by using only month and year of birth. Indentifiers are stored in [[PHI.mdb]]. | |||
Centralized.mdb is linked to other Access databases, such as [[Tasks_1.mdb]], [[Pharmacy.mdb]], [[TmpV2_1.mdb]] by [[Centralized data front end.mdb]] | Centralized.mdb is linked to other Access databases, such as [[Tasks_1.mdb]], [[Pharmacy.mdb]], [[TmpV2_1.mdb]] by [[Centralized data front end.mdb]] | ||
| Line 22: | Line 23: | ||
[[TISS28 Data.mdb]] pulls data from Centralized data.mdb. | [[TISS28 Data.mdb]] pulls data from Centralized data.mdb. | ||
[[Category:Data Repository]] | [[Category:Data Repository]] | ||
[[Category:2013 data upgrades]] | [[Category:2013 data upgrades]] | ||
Revision as of 11:53, 9 February 2014
see also Centralized data.mdb Change Log Centralized.data.mdb is a data repository containing a de-identified copy of all data sent from Critical Care and Medicine. De-identified by excluding chart, phin, names, and by using only month and year of birth. Indentifiers are stored in PHI.mdb.
Centralized.mdb is linked to other Access databases, such as Tasks_1.mdb, Pharmacy.mdb, TmpV2_1.mdb by Centralized data front end.mdb
Only main processing office can link Centralized.data.mdb with PHI.mdb.
The development of this database has been in progress since early this year (2013) and it is currently being run in tandem with current data repository ICU TMSX & Medicine MedTMS.
Location
<file>\\Ad.wrha.mb.ca\wrha\REGIONWRHA\SHARED\ICU_DATA_COLLECTION\Output\Centralized_data.mdb</file>
- See: External Files in regards to what green link means.
How does data get into Centralized data.mdb
version 2012-12-21 implemented sending of data to Centralized_data.mdb.
This is accomplished by queries run at sending time. See sub send_data() for details.
Finding and fixing Errors
Will need to implement tools in centralized_data.mdb to help Pagasa with error checking. All data will be checked. Pagasa will correct "sent" data, for incomplete data she will notify collector. Doing that should probably be facilitated. Possibly in the future we can have a mechanism where Pagasa can just "reject" data that is bad, and where it will be sent back to collectors, either at n&b time, start time, or send time... needs to be thought about. Template:Question IT
Dependencies
TISS28 Data.mdb pulls data from Centralized data.mdb.