Service tmp entry: Difference between revisions
Ttenbergen (talk | contribs) →Data Collection Instructions: removing an old discussion that was likely answered; if still a question please post it back with clarification how it's still a question. |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 10: | Line 10: | ||
== Data Collection Instructions == | == Data Collection Instructions == | ||
You can use the [["Make Service" button]] to generate and pre-populate these entries. | You can use the [["Make Service" button]] in [[Patient Viewer Tab Cognos ADT2]] or [[Patient Viewer Tab Cognos ADT]] to generate and pre-populate these entries. | ||
=== How to enter this === | === How to enter this === | ||
| Line 21: | Line 21: | ||
** time: '''Service Start DtTm''' time as per [[Cognos EPR Report]] | ** time: '''Service Start DtTm''' time as per [[Cognos EPR Report]] | ||
*** for pts coming from ER this dttm will be the same as [[Accept DtTm]], but we want it for non-ER pts as well | *** for pts coming from ER this dttm will be the same as [[Accept DtTm]], but we want it for non-ER pts as well | ||
{{Discuss | | |||
*** the '''first''' entry for [[Boarding Loc]] and for [[Service tmp entry]] need to have the same date and time because we only care about the portion of time in that earliest location that was under our service. So, e.g. if in ER the pt is accepted initially by surgery we don't care about the unit start date and time until our service takes over. | *** the '''first''' entry for [[Boarding Loc]] and for [[Service tmp entry]] need to have the same date and time because we only care about the portion of time in that earliest location that was under our service. So, e.g. if in ER the pt is accepted initially by surgery we don't care about the unit start date and time until our service takes over. | ||
* flagged this in [[Boarding Loc]], whatever is answered there, this must become consistent. Ttenbergen 13:25, 2020 November 9 (CST)}} | |||
Add a new entry for service only if the service changes during their stay. | Add a new entry for service only if the service changes during their stay. | ||
Revision as of 13:25, 9 November 2020
| Projects | |
| Active?: | active |
| Program: | CC and Med |
| Requestor: | internal |
| Collection start: | 2020-10-15 |
| Collection end: | |
This isn't so much a project as a change to Service/Location collection to allow us to collect more than one Service/Location per patient-program-stay. See Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry for why we needed to change to this.
Data Collection Instructions
You can use the "Make Service" button in Patient Viewer Tab Cognos ADT2 or Patient Viewer Tab Cognos ADT to generate and pre-populate these entries.
How to enter this
- Use tmp fields:
- project: Service
- item: no service entered is added by default to each new patient entered
- change this to the applicable service; this will be the service as listed in the Cognos Report Integrator tools (see s_Cognos_Services table for a list of applicable services).
- select the appropriate service from the dropdown list
- date: Service Start DtTm date as per Cognos EPR Report
- time: Service Start DtTm time as per Cognos EPR Report
- for pts coming from ER this dttm will be the same as Accept DtTm, but we want it for non-ER pts as well
|
|
Add a new entry for service only if the service changes during their stay.
| Example: |
|
Which service to use when several are listed for the same timeframe
|
|
|
|
Loose ends
None of these are show-stoppers, just some notes on future improvements.
|
Facilitate viewing and entering Service tmp
It might be easier to enter these if we were able to see Cognos data for Service tmp entry separately from Boarding Loc. I am working on a Cognos2 setup for this, more to come.
|
when I get Cognos2 set up I will need to clean this out |
|
data checks
Data Integrity Checks (automatic list)
| App | Status | |
|---|---|---|
| Query check minimal data set incomplete | CCMDB.accdb | implemented |
| Query check tmp service or location duplicate | CCMDB.accdb | implemented |
| Query check tmp service and program consistency | CCMDB.accdb | implemented |
| Query check tmp Service and Boarding Loc during admission timeframe | CCMDB.accdb | implemented |
| Query check CCI TISS NrDays GT LOS | CCMDB.accdb | implemented |
| Query check CCI TISS NrDays LT LOS | CCMDB.accdb | implemented |
| Query check tmp Boarding Loc Service first same | CCMDB.accdb | implemented |
| Query check CCI vs LOS count days component | CCMDB.accdb | implemented |
| Query check CCI vs LOS count days picklist | CCMDB.accdb | implemented |
| Query check no consecutive same BL or Service | CCMDB.accdb | implemented |
| Query check ICD10 date | CCMDB.accdb | implemented |
| Query check CCI Date | CCMDB.accdb | implemented |
| Query s tmp Boarding Loc date item | CCMDB.accdb | implemented |
| Check duplicate patient | CCMDB.accdb | implemented |
| Query check CCI TISS Pharm Vasoactive | CCMDB.accdb | implemented |
| Query check tmp 2 BL TR S same tm | CCMDB.accdb | implemented |
Data Use
Critical care and Medicine programs want to know this to better understand patient flow and bed utilization.
