Service tmp entry

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? (blezak) Good point. The data is in the Cognos Admitter; what was the "Accept DtTm equiv" and only visible if pt came from ER is now the Service Start DtTm, and always visible. Change is in v2020-10-21-1. If that answers the question, please remove the discussion. If not, please elaborate. Ttenbergen 18:15, 2020 October 21 (CDT)

• SMW

• Cargo

• Categories

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
    • 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.

Add a new entry for service only if the service changes during their stay.

Example:

E.G. patient X is in the ER and is accepted by HSC A medicine on Oct 15,2020@0900, On Oct 17,2020 @1500 HSC H medicine takes over his care in the TMP select Project Service, Item choose HSC A medicine, column E enter Oct 15,2020, Column M enter 0900 second entry in TMP would be project Service, Item choose HSC H medicine, Column E enter Oct 17,2020, Column M enter 1500

Which service to use when several are listed for the same timeframe

I am trying to enter my first critical care patient at HSC. There are multiple choices (dozens) for HSC critical care, and it is not evident which one I should be choosing. I think that it would be a lot more intuitive if the choices are limited to Critical Care-surgical, Critical Care-medical, and Critical care-Intermediate.Mlagadi 09:01, 2020 October 16 (CDT) I'd like that, too. The problem is SICU - AFAIK they are an "open unit" so all sorts of services play there, and therefore show up in Cognos. I made a list that reflects Cognos. We should bring this up to Julie to see what she needs, we might be able to get away with what you suggest. I will flag this for Julie, but if it isn't dealt with by the time the next task meeting comes around, please bring it up then. Ttenbergen 23:32, 2020 October 18 (CDT) Further, I don't think we should introduce our own, fake service to replace the Cognos ones. Ttenbergen

• SMW

• Cargo

• Categories

Michelle said she is using "Hsc critical care/medicine" for MICUs – Michelle, can you confirm that this is always one of the several services that may be listed for an MICU patient? If so then using always the same would be a good idea. I could probably facilitate that in ccmdb to make it easier. Ttenbergen 09:18, 2020 November 5 (CST) As far as I can see, the only service that admits to MICU and the extension unit JKL3, is "Critical Care/Medicine". It is SICU that has multiple different services. As a second thought to this, if there are services that are only ever used as a secondary entry, I would be able to filter those out so they don't clutter things. But we would want to be really sure they are always only a secondary, or we might miss patients. Ttenbergen 09:22, 2020 November 5 (CST) Sorry, I don't understand what you mean as a secondary entry.

• SMW

• Cargo

• Categories

This is probably also an issue for other than HSC CC: where else gets multiple listings for the same timeframe, and what have they chosen to enter consistenly? Ttenbergen 09:18, 2020 November 5 (CST)

• SMW

• Cargo

• Categories

Loose ends

None of these are show-stoppers, just some notes on future improvements.

This project does might eventually replace ICUotherService; we will still need this item in the event that both the bed and the service are both borrowed. Administration at STB want this data.

• SMW

• Cargo

• Categories

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

added: no added date action: no action date

• Cargo

• Categories

data checks

add a cross check to make sure this is not left as "no service entered"

• SMW

• Cargo

• Categories

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.

SAS Program

Background

Related articles