Centralized data.mdb: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 11: | Line 11: | ||
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) | 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) | ||
== Dependencies == | |||
[[TISS28 Data.mdb]] pulls data from Centralized data.mdb. | |||
[[Category:Data Repository]] | [[Category:Data Repository]] | ||
Revision as of 15:53, 2013 April 8
Data Repository containing:
- Serial number
- Location
- admit, transfer and discharge dates and times
- 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
Template:Discussion 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)
Dependencies
TISS28 Data.mdb pulls data from Centralized data.mdb.