Cognos Report Integrator: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m (cleanup done) |
||
| Line 1: | Line 1: | ||
This page is about how [[Cognos EPR Report]] | This page is about how [[Cognos EPR Report]] is integrated into CCMDB. | ||
== Overview == | == Overview == | ||
Latest revision as of 14:13, 2022 June 14
This page is about how Cognos EPR Report is integrated into CCMDB.
Overview
- Cognos EPR Report is the data source
- Cognos data import is the process to get the data into CCMDB.accdb
- Cognos2 is the set of tools data collectors use in CCMDB.accdb to interact with and enter the data from Cognos into profiles
Data
- field equivalences (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