Cognos data import

This page explains how to get data from the Cognos EPR Report into CCMDB.accdb and rolled out to collectors.

Process

Tina receives the data in a scheduled, automated email from Chastity Cleofas every morning as early as possible, usually before 8. The data is then imported into CCMDB.accdb master on Regional server and provided to collectors via regular roll-out and news and backup.

Outlook Rule in Tina's profile to get data to Pagasa

Decision Support Services sends a report to Tina. The report needs to go to Pagasa so we can schedule the automated import on a machine that sits on WRHA network at all times. So, there is an outlook rule "Cognos to Pagasa" in Tina's Outlook profile to forward the email to Pagasa from Chastity.

Scheduled Task on Pagasa's PC

There is a scheduled task on Pagasa's PC that calls LoadCognos.bat early each morning.

• LoadCognos.bat calls
• LoadCognos.vbs which calls
• CCMDB.accdb.Sub CognosImport for the actual steps performed during import, and how the queries and tables work together and the email to collectors is generated.
• process then returns to LoadCognos.bat which copies CCMDB.accdb to the Regional Server and then calls Updt all.bat to roll it out to all collectors

Fallback process

The import can also be manually run on any laptop that has CCMDB.accdb using the Cognos2_Service_Starter#Cognos_Import_Button and the data can be manually sent out to collectors following the same process as Rolling out changes.

When run on Tina's computer the process will roll out any current changes in the local file; if anything was changed, update log saying it has been rolled out!

newly encountered units

If a unit is encountered that isn't in s_Cognos_Units table, an email will be sent to Tina. The new unit then needs to be added to s_Cognos_Units table with the other fields filled in appropriately. Boarding Loc and Level of care hierarchy/s_level_of_care table entries need to be considered to see if they need to be updated.

newly encountered services

If a service is encountered that isn't in S Cognos Services table an email will be sent to Tina. The new service then needs to be added to s_Cognos_Services table with the other fields filled in appropriately. Service tmp entry entries need to be considered to see if they need to be updated.

Known problems with data import

Shared Health Re-boots

The task requires the user be logged in. If Shared Health re-boots the computer over night, the task won't run until Pagasa logs on.

CFE or TISS28.accdb left open on Pagasa's PC

CFE and TISS28.accdb needs to be closed at the end of the work day on Pagasa's computer. The update process needs to download the newest version of CCMDB.accdb from the Regional Server before it runs so that it doesn't overwrite the master version with an older version from Pagasa's PC. This download of the newest version is blocked when CFE is open.

Problem Log

detailed log

2020-Nov-10 - email was delayed to 9:17, then rolled out ok 2020-Nov-09 - Pagasa is away and the updater task has failed on her PC; Tina will do it manually until Pagasa comes back 2020_Oct_23 - Chastity report came late @ 08:46, Run manually cognos. 2020_Oct_21 - Chastity email -ETL failed last night so there will be no report today. No new cognos. 2020_Oct_9 - task was stuck because CFE was open 2020_Oct_8 - Task schedule did not run because computer were rebooted by EHealth overnight. Pagasa changed the Task schedule so it does not run on weekends. Concern will be this long weekend and the task may hang because data from email not deleted before it runs on Tues AM. 2020-Oct-6 & 7 - Tuesday - ran at 0740. No issues.