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

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

What date and time are we attaching to this? Accept or Arrive? Surbanski 09:16, 2020 October 16 (CDT) It would be better to think of it as "the time the next service started (as per Cognos and also as per EPR)". For the first entry that should be the same as the Accept DtTm, but for any further entries (and those are why we made this), they would NOT be the Accept DtTm. Ttenbergen 09:31, 2020 October 16 (CDT)

• SMW

• Cargo

• Categories

Just to be clear and as an example for STB Med program a generic entry of STB_Med is entered into the Service/Location field on the Dispo page with a service location entry on the Tmp page? Yes. Ttenbergen 09:31, 2020 October 16 (CDT)

• 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

should be able to add something to Cognos Admitter and Patient Viewer Tab Cognos ADT that facilitates entering this; will delay that until we have collected this for a few weeks; if we find these entries to be identical to Cognos data we might not need to enter them at all but instead import them directly, but not until we have checked consistency.

• SMW

• Cargo

• Categories

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)

• SMW

• 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