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 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
• the Service may start after the first Boarding Loc, since a patient may well already be in a location when a service takes over ( see Boarding_Loc#Why_do_we_use_the_actual_unit_start_dttm_rather_than_the_time_they_became_our_pt_on_a_unit for more info)

Add a new 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

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

Occasionally Cognos may list several services with the same dttm. That should not happen, see Process for bad data in Cognos.

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