Service tmp entry

From CCMDB Wiki
Jump to navigation Jump to search
Projects
Active?: active
Program: CC and Med
Requestor: internal
Collection start: 2020-10-15
Collection end:

This data encodes which service is taking care of a patient. See Definition of a Critical Care Laptop Admission / Definition of a Medicine Laptop Admission for info on when a new profile should be started.

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.

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
  • Use tmp fields:
    • project: Service
    • item: no service entered is added by default to each new profile entered
    • select the appropriate service from the dropdown list

DtTm to use

Template:First Service and Boarding Loc same

Code Blue

See Definition_of_a_Critical_Care_Laptop_Admission#From_Code_Blue for when a profile should start in case of a code blue.

Specifically for STB Critical Care

Special rules apply to STB CICU Admissions start at Arrive DtTm

  • at StB, the Service tmp date and 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 Service tmp date and time is the same time as the Boarding Loc time
  • if the patient is coming from the Cath Lab, or the OR, the time is obtained from the ICU flowsheet

Item - Special instruction for HSC Critical Care

HSC Critical Care services (except "HSC Critical Care / Intermediate", which is entered as is) should be entered as "HSC Critical Care - MICU", "HSC Critical Care - SICU".

For HSC MICU, COGNOS generally lists the service as Critical Care Medicine, on occasion other services will be listed eg. Critical Care internal medicine A, or Critical care Respiratory etc but this is usually followed by a second entry that is Critical Care Medicine. These should be changed to HSC Critical Care-MICU.

For HSC SICU, COGNOS generally lists the service as "Critical Care" followed by a surgical service, for eg. Critical Care Acute Care Trauma, Critical Care Neurosurgery, Critical Care Thoracic Surgery, Critical Care Orthopedics etc. These should be changed to HSC Critical Care - SICU.

There are a few services that can be mapped to either HSC Critical Care MICU or HSC Critical Care SICU

  • 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

These will require further investigation by reading through the chart or EPR documents before you make the decision to map it to HSC Critical Care-MICU or HSC Critical Care-SICU

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 Admit DtTm shown in Patient Viewer Tab Cognos ADT2. You can use the "VA" button to fill it in.

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)

 AppStatus
Query check CCI vs LOS count days picklistCCMDB.accdbimplemented
Query check tmp 2 BL TR S same tmCCMDB.accdbimplemented
Query check CCI TISS Pharm VasoactiveCCMDB.accdbimplemented
Check duplicate patientCCMDB.accdbimplemented
Query s tmp Boarding Loc date itemCCMDB.accdbimplemented
Query check CCI DateCCMDB.accdbimplemented
Query check ICD10 dateCCMDB.accdbimplemented
Query check no consecutive same BL or ServiceCCMDB.accdbimplemented
Query check minimal data set incompleteCCMDB.accdbimplemented
Query check CCI vs LOS count days componentCCMDB.accdbimplemented
Query check tmp Boarding Loc Service first sameCCMDB.accdbimplemented
Query check CCI TISS NrDays LT LOSCCMDB.accdbimplemented
Query check CCI TISS NrDays GT LOSCCMDB.accdbimplemented
Query check tmp Service and Boarding Loc during admission timeframeCCMDB.accdbimplemented
Query check tmp service and program consistencyCCMDB.accdbimplemented
Query check tmp service or location duplicateCCMDB.accdbimplemented
Query check CCI CXR vs LOSCCMDB.accdbneeds review

Data Use

This data is used to facilitate Using Cognos2 to keep track of patients.

Legacy / Background

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. We initially planned to change to a single profile per program collection mode, but then gradually reverted to a single profile per service for all critical care profiles.

Related articles

Related articles: