Centralized data.mdb: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
TOstryzniuk (talk | contribs)
mNo edit summary
TOstryzniuk (talk | contribs)
mNo edit summary
Line 1: Line 1:
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.  
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.  
The development of this database has been in progress since early this year and it is currently being run in tandem with current data repository ICU [[TMSX]] & Medicine [[MedTms]].   
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 ==
== Location ==

Revision as of 14:15, 2013 October 30

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. 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>


Template:Discussion Hi, hello, what is a green link above that leads to nowhere? I have seen and few of these being planted around. Thanks. Trish Ostryzniuk 18:20, 2013 October 9 (CDT)

See the answer here: External Files

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.