Service tmp entry: Difference between revisions
Ttenbergen (talk | contribs) |
|||
Line 10: | Line 10: | ||
== Data Collection Instructions == | == Data Collection Instructions == | ||
{{Discuss| | |||
Are we adding the date and time that each service takes over? Where do we find this information on EPR? }} | |||
=== How to enter this === | === How to enter this === | ||
*Use tmp fields: | *Use tmp fields: |
Revision as of 10:47, 19 October 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
Are we adding the date and time that each service takes over? Where do we find this information on EPR? |
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 Cognos SubServices table for a list of applicable services).
- select the appropriate service from the dropdown list, enter the date and time the service first took over e.g. accept time for those coming from ER
- Add a new entry for service, only if the service changes during their stay.
Example: |
|
Loose ends
None of these are show-stoppers, just some notes on future improvements.
|
|
Facilitate viewing and entering Service tmp
The thing is, that tab is getting very full, and I will need to either make fonts smaller or squeeze an area to show even fewer lines. I wonder how best to do that in a way that works for collectors. It’s on the “later” pile for now, but for sure something I want to deal with. Open to suggestions. Ttenbergen 12:24, 2020 October 16 (CDT) |
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.