Cognos Report Integrator: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m (→Fields: This is an OK place for that info to live) |
Ttenbergen (talk | contribs) m (→Fields) |
||
| Line 10: | Line 10: | ||
== Fields == | == Fields == | ||
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_integrator query]] then tries to match up the data from Cognos to records currently or previously on the laptop; it uses [[S Cognos Units table]] and [[s_Cognos_SubServices table]] for the mapping | ||
* field equivalences (sort of see [[Cognos_import_processor query]] and [[Cognos_integrator query]] for details) | * field equivalences (sort of see [[Cognos_import_processor query]] and [[Cognos_integrator query]] for details) | ||
** IPAdmitDtm --> [[Visit Admit DtTm field]], [[Accept DtTm]] (but only if pt is from ER) | ** IPAdmitDtm --> [[Visit Admit DtTm field]], [[Accept DtTm]] (but only if pt is from ER) | ||
Revision as of 13:06, 2020 November 24
This page is about how Cognos EPR Report will be integrated into CCMDB. This will likely be the replacement for EPR Reports Integrator. For anything not linked directly from this page, also see Cognos Report Integrator.
Overview
- Cognos EPR Report is the data source
- Cognos data import is the process to get the data into CCMDB.accdb
- Cognos Admitter is the tool collectors would use to add ward stay records or Boarding Loc entries to CCMDB.accdb from Cognos
- Cognos Patient viewer tab FormQuery query shows Cognos data for patients currently in CCMDB.accdb
- Cognos Discharger is the tool collectors use to track who is already on CCMDB.accdb and has been discharged or moved
Fields
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 S Cognos Units table and s_Cognos_SubServices table for the mapping
- field equivalences (sort of see Cognos_import_processor query and Cognos_integrator query for details)
- IPAdmitDtm --> Visit Admit DtTm field, 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 (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.FromLoc to facilitate process for collectors but not yet good enough for full automation) --> Previous Location
- AsgnUnit_current --> Service/Location or Boarding Loc
- AsgnUnit_Next / IPDischargeDisposition / IPDischargeLocation depending on story; I try to summarize this in Cognos_import_processor query.ToLoc to facilitate process for collectors but not yet good enough for full automation --> Dispo
Hierarchy of queries
- then Cognos_integrator query draws from Cognos_processed table and feeds the following: