Transfer Tracker.mdb: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m '''automatic overnight updates''' now implemented. also '''transfer date''' added
Line 4: Line 4:
:: [[Regional Server]]\Output\Transfer_Tracker.mdb
:: [[Regional Server]]\Output\Transfer_Tracker.mdb


It gets its content from the backup files.  
It gets its content from the backup files. Data is updated from the backup files each night, and you can update it to the most current data including today by pressing the update button.


When you open the program, it displays the data that was in the most recent data backup from the last time someone has clicked the "update" button it, and the date of that update in the top left corner.  
When you open the program, it displays the data that was in the most recent data backup from the last time someone has clicked the "update" button it, and the date of that update in the top left corner.  
== Automating Updates ==
It would be nice to have the tracker update automatically rather than having collectors push that button. I decided not to do this automatically because the update can take about 2 minutes. Didn't want to force you to wait when the most recent data might be good enough.
I can not think how I would do this in the current configuration. It's an access program, and someone has to run it to make it do something. Having said that, if this becomes commonly used we might be able to do this on a rotational basis or something. Let's see how many people are using it.


== Bugs ==
== Bugs ==
Please let me know if there are problems or the program doesn't work as expected. [[User:Ttenbergen|Ttenbergen]] 11:22, 5 October 2011 (CDT)
Please let me know if there are problems or the program doesn't work as expected. [[User:Ttenbergen|Ttenbergen]]
* "I do not know if this is a glitch-but I changed the discharge location for serial #5150 VM noticed that there are two files on the tracker for him now." (Marie Laporte )
** Well, its not so much a glitch as that the transfer tracker has to decide which records to keep and which to discard. Since it gets updated every time it is run, and keeps records for patients who have been discharged, and since those patients can then be admitted again and have to keep showing up, the TT can’t distinguish a patient with a changed value from one who has been re-entered. I had not thought of this special case, and I appreciate you bringing it up. I can’t think of a good way to filter out that patient that would deal with other special case scenarios. Can you think of one? Maybe I am overthinking something and there really is an easy solution. [[User:Ttenbergen|Ttenbergen]] 09:09, 14 December 2011 (CST)


== Requested Changes ==
== Requested Changes ==
Please let me know if you would like to see things changed or added. [[User:Ttenbergen|Ttenbergen]] 10:59, 5 October 2011 (CDT)
Please let me know if you would like to see things changed or added. [[User:Ttenbergen|Ttenbergen]]
* add transfer dates [[User:Ttenbergen|Ttenbergen]] 09:54, 6 December 2011 (CST)


=== self-updating directory listing ===
=== self-updating directory listing ===

Revision as of 13:34, 2012 July 18

Transfer_Tracker.mdb is a repository of all discharges on our ward within the last 2 weeks.

You can find the transfer tracker at

Regional Server\Output\Transfer_Tracker.mdb

It gets its content from the backup files. Data is updated from the backup files each night, and you can update it to the most current data including today by pressing the update button.

When you open the program, it displays the data that was in the most recent data backup from the last time someone has clicked the "update" button it, and the date of that update in the top left corner.

Bugs

Please let me know if there are problems or the program doesn't work as expected. Ttenbergen

Requested Changes

Please let me know if you would like to see things changed or added. Ttenbergen

self-updating directory listing

note for Tina only use self-updating directory listing to import rather than a static list (this doesn't affect functionality while things work, it just makes the program a bit more resilient. Right now there is an error if any site can't be found, and if a new site is added and the hard-code is not amended the site just won't import) Ttenbergen 11:33, 1 March 2011 (CST)