MB Health Tool.mdb: Difference between revisions
Ttenbergen (talk | contribs) m u |
Ttenbergen (talk | contribs) →Backup: don't need a backup process in addition to what eHealth does and what goes into our log |
||
| Line 15: | Line 15: | ||
M:\MB_Health_Records_Cleaning\MB Health Tool.mdb | M:\MB_Health_Records_Cleaning\MB Health Tool.mdb | ||
== Backup | == Backup == | ||
Daily eHealth backups for this should be sufficient. It's rare-use, so the daily backups should be frequent enough. Also, since the live data gets fed into [[centralized_data.mdb]], the data remaining in this file is low impact, so if it really were to be used we would not loose anything vital. Additionally, the logs in [[Manitoba Health Crosschecking Sending Data]] and [[Manitoba Health Crosschecking Reconciling Returned Data ]] should enable us to recreate anything necessary. | |||
== Legacy == | == Legacy == | ||
Revision as of 08:27, 2014 September 9
The Manitoba Health Tool.mdb facilitates Crosschecking data with Manitoba Health process, specifically:
Starting the program
The Manitoba Health Tool.mdb needs to connect to centralized_data.mdb and PHI.mdb in C:\Centralized_CCMDB as would be put in place by the push pull. So:
- run pull
- open M:\MB_Health_Records_Cleaning\MB Health Tool.mdb
- click the re-connect button
- do your work, e.g. sending request data to MB Health or reconciling returned data
- close the program
- run push
Master File Location
M:\MB_Health_Records_Cleaning\MB Health Tool.mdb
Backup
Daily eHealth backups for this should be sufficient. It's rare-use, so the daily backups should be frequent enough. Also, since the live data gets fed into centralized_data.mdb, the data remaining in this file is low impact, so if it really were to be used we would not loose anything vital. Additionally, the logs in Manitoba Health Crosschecking Sending Data and Manitoba Health Crosschecking Reconciling Returned Data should enable us to recreate anything necessary.
Legacy
Replaces Manitoba Health "Conditioner"