Cognos data import: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m (→Background) |
Ttenbergen (talk | contribs) m (→Background) |
||
| Line 14: | Line 14: | ||
== Background == | == Background == | ||
* [[LoadCognos.bat]] calls | * [[LoadCognos.bat]] calls | ||
* [[LoadCognos.vbs]] which calls | * [[LoadCognos.vbs]] which calls | ||
| Line 23: | Line 21: | ||
This next part isn't really part of the import but the explanation needs to live somewhere, so parking here for now. | 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 | * [[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) | * field equivalences (sort of see [[Cognos_import_processor query]] and [[Cognos_integrator query]] for details) | ||
** IPAdmitDtm --> [[Accept DtTm]] (but only if pt is from ER) | ** IPAdmitDtm --> [[Accept DtTm]] (but only if pt is from ER) | ||
** AsgnUnitStartDtm_current --> [[Arrive DtTm]] or [[Boarding Loc]] date and time | |||
** AsgnUnitEndDtm_current --> [[Dispo DtTm]] or [[Boarding Loc]] date and time | |||
** 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. | ** 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. | ||
** AsgnUnit_current --> [[Service/Location]] or [[Boarding Loc]] | |||
** AsgnUnit_Next / IPDischargeDisposition / IPDischargeLocation --> [[Dispo]] | |||
* | * then [[Cognos_integrator query]] draws from [[Cognos_processed table]] and feeds the following: | ||
** [[Cognos_Admitter_FormQuery query]] feeds [[Cognos Admitter]] | ** [[Cognos_Admitter_FormQuery query]] feeds [[Cognos Admitter]] | ||
** [[Cognos_Patient_viewer_tab_FormQuery query]] feeds [[Patient viewer tab Cognos ADT]] | ** [[Cognos_Patient_viewer_tab_FormQuery query]] feeds [[Patient viewer tab Cognos ADT]] | ||
Revision as of 16:24, 2020 July 30
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
- the process will roll out any current changes in the local file; if anything was changed, update log saying it has been rolled out
- save the CCMdb Sample.xlsx file that Chastity sends to the desktop
- double-click on LoadCognos.bat and wait for it to finish (this can take a few minutes)
- 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
- if data is good, click enter in the shell window to proceed with copy
- if copy goes OK, press enter in the next shell window to roll out to all collectors
- 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. |
Background
- LoadCognos.bat calls
- LoadCognos.vbs which calls
- Sub CognosImport for the actual steps performed during import, and ow the queries and tables work together.
|
|
Where should this live? |
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 see Cognos_import_processor query and Cognos_integrator query for details)
- IPAdmitDtm --> Accept DtTm (but only if pt is from ER)
- AsgnUnitStartDtm_current --> Arrive DtTm or Boarding Loc date and time
- AsgnUnitEndDtm_current --> Dispo DtTm or Boarding Loc date and time
- 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.
- AsgnUnit_current --> Service/Location or Boarding Loc
- AsgnUnit_Next / IPDischargeDisposition / IPDischargeLocation --> Dispo
- then Cognos_integrator query draws from Cognos_processed table and feeds the following:
Related articles
| Related articles: |
|