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

You can use the "Make Service" button in Patient Viewer Tab Cognos ADT2 to generate and populate these entries.

How to enter this

Add an additional entry for service only if the service changes during their stay.

ExpandExample:

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

• 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

DtTm to use

• date: Service Start DtTm date as per collector best estimate
• time: Service Start DtTm time as per collector best estimate
  • the first Service Start DtTm must be the same as Accept DtTm, if that field is required to be filled for this profile

• set as per Definition of a Critical Care Laptop Admission or Definition of a Medicine Laptop Admission
• Enter the Service Start DtTm in the Patient Viewer Tab Cognos ADT2; you can click on this DtTm to automatically populate it into the Accept_DtTm field
• Template:First Service and Boarding Loc same

Are the following actually specific to STB or are they general instructions? Are some of them still required now that we are unifying the definition of the two fields? : at the last task meeting I was at, it was agreed that each hospital would enter the dates/times that are most accurate. We were asked to say on the WIKI what we are doing at each site, so this is what is written here. It is my belief that HSC still uses Cognos for their date/time entries. And yes, these instructions would be required for the single field entries. Accept time eq service start time & arrive time eq boarding location time at StB, the accept time for ICU patients coming from ER is taken from the orders. If the time is written after the patient has already arrived to the ICU, the accept time is the same time as the arrive time at STB, the ICU team is considered as having accepted the patient when they arrive on the scene if the patient is successfully resuscitated and goes to a unit at STB, if the patient is coming from the Cath Lab, or the OR, the accept time and arrive time will be the same as this is when they are considered to have assumed care of the patient. This time is obtained from the ICU flowsheet.

• SMW

• Cargo

• Categories

Direct Admissions/Transfers

For patients who have been accepted from another hospital but have a wait time in ER (who used to be called Direct Admissions/Parked in ER), use the visit ID date and time for the Service tmp entry as it is clearly marked in the EPR.

Is the Visit ID date and time in EPR the same as the Visit Admit DtTm? If so, that's already available in ADT2 tab, so would be easiest to grab from there. I could even set up CCMDB to have a button in the tmp lines to drag the time in from that field. Yes, the same thing, but not sure what you mean by dragging the time, could collectors click on it?

• SMW

• Cargo

• Categories

When does collection start?

see

• Definition of a Critical Care Laptop Admission
• Definition of a Medicine Laptop Admission

Item - Special instruction for HSC Critical Care

There are two extra options "HSC Critical Care - MICU" and "HSC Critical Care - SICU" that should be used...

When should the new options be used rather than the other service entries for HSC? if I understand it correctly, when the list of these services appear in Cognos, since they do not map well to MICU or SICU, the DC must specified which service is appropriate : MICU or SICU. In reporting, I need to separate the data belonging to MICU and SICU service. If you would like to add "HSC Critical Care - MICU" and "HSC Critical Care - SICU", we need to add them to s_Cognos_Services.xlsx HSC Critical Care / Adult General HSC Critical Care / Amputee HSC Critical Care / General HSC Critical Care / Intensive Care HSC Critical Care / Obstetrics HSC Critical Care / Oncology - --JMojica 14:18, 2021 April 6 (CDT) if you mean S Cognos Services table then I am not sure we really need to add them there... that is the list of services that come in from Cognos, and these don't come in from Cognos. Actually, what we would need to do is make sure we remove the ambiguous items that came via Cognos into the s_tmp table that we don't want people to use any longer, so that people are forced to instead use our made up ...SICU and ...MICU ones. Julie and Tina might need to discuss this in our questions meeting on Thursday. Are we using the new options for all HSC CC now, or are we still entering some Services as per Cognos? Ttenbergen 15:27, 2021 April 15 (CDT)

• SMW

• Cargo

• Categories

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

Occasionally Cognos may list several services with the same dttm. See Process for bad data in Cognos.

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