Service tmp entry: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
mNo edit summary
mNo edit summary
Line 20: Line 20:
None of these are show-stoppers, just some notes on future improvements.
None of these are show-stoppers, just some notes on future improvements.
{{DT |  
{{DT |  
* 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.}}
* 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.
}}
}}
{{DT |  
{{DT |  
Line 45: Line 45:
[[Category:Project]]
[[Category:Project]]
[[Category:Overflow]]
[[Category:Overflow]]
[[Category:EMIP]]
[[Category:PatientFollow Project]]
[[Category:PatientFollow Project]]

Revision as of 21:02, 15 October 2020

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 to GRA Med, HSC Med, STB Med Service Location 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

Lose 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

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)

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

Data Use

Critical care and Medicine programs want to know this to better understand patient flow and bed utilization.

SAS Program

Background

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Service_tmp_entry&oldid=146393"