Centralized data.accdb
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 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:
- "Send_Centralized_update" (update existing records to data currently in the collector's ccmdb_data.mdb)
- "Send_Centralized_append" (append new records from the collector's ccmdb_data.mdb)
preventing fixed data from being re-written
I will change the "Send_Centralized_update" query to not touch records that have recordstatus = "sent" in repository; the other query only deals with records not yet present so doesn't need to be changed
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.