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 every morning as early as possible, usually before 8. The data is then imported into CCMDB.accdb and provided to collectors via regular roll-out and news and backup.

Data import instructions

1. the process will roll out any current changes in the local file; if anything was changed, update log saying it has been rolled out
2. save the CCMdb Sample.xlsx file that Chastity sends to the desktop
3. double-click on LoadCognos.bat and wait for it to finish (this can take a few minutes)
4. at some point it will list the current date/time and the newest Cognos record's date/time; the newest record should be from late last night. If it is not, you may not have saved the file right, or there may have been problems with the ETL that drives Cognos. If so, press ctrl-c to stop the process
5. if data is good, click enter in the shell window to proceed with copy
6. if copy goes OK, press enter in the next shell window to roll out to all collectors
7. the process will have automatically started 1 or possibly 2 emails; send them

Currently this process lives on Tina's laptop, and Tina is the only one who can do it. We need a better solution.

• SMW

• Cargo

• Categories

Background

• Cognos EPR Report
• LoadCognos.bat
• LoadCognos.vbs
• Sub CognosImport
• Cognos_dispo_translator_additions_needed query

• the process imports into Cognos_import table and then uses Cognos_import_processor query to populate Cognos_processed table with data that has been transformed for our use (e.g. Cognos does dates down to the second, we only do them to the minute... )
• Cognos_dispo_translator_additions_needed query runs automatically; if it finds new entries, an email is started to a collector to find out what should be added to Cognos_dispo_translator table to map the new entries to entries of s_dispo table

I need to make a similar thing for Cognos SubServices table.

• SMW

• Cargo

• Categories

This next part isn't really part of the import but the explanation needs to live somewhere, so parking here for now.

• Cognos_integrator query then tries to match up the data from Cognos to records currently or previously on the laptop; it uses Cognos_dispo_translator table and Cognos_SubServices table for the mapping
• field equivalences (sort of)
  • IPAdmitDtm --> Accept DtTm (but only if pt is from ER)
  • AsgnUnit_Prior --> Previous Location (but it's more complicated, when pt comes from ER or other site there is info in field "EmergencyDepartment" or "ReferringLocation"; I try to summarize this in Cognos_import_processor query, but not yet good enough for automation.

needs more detail.

• SMW

• Cargo

• Categories

• it feeds forward as follows:
  • Cognos_Admitter_FormQuery query feeds Cognos Admitter
  • Cognos_Patient_viewer_tab_FormQuery query feeds Patient viewer tab Cognos ADT
  • Cognos_Discharger_FormQuery query feeds Cognos Discharger