Service tmp entry: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Line 33: Line 33:


=== Which service to use when several are listed for the same timeframe ===
=== Which service to use when several are listed for the same timeframe ===
{{Discuss |  
{{DT |  
* 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.[[User:Mlagadi|Mlagadi]] 09:01, 2020 October 16 (CDT)
Several services being listed for the same timeframe was due to a problem with the Cognos extract. We now have new data that fixes this, but when I put it into CSS and CE there will be a lot of records to deal with, so still testing this before rolling it out. [[User:Ttenbergen|Ttenbergen]] 20:48, 2020 December 30 (CST)
** I'd like that, too. The problem is SICU - AFAIK they are an "open unit" so all sorts of services play there, and therefore show up in Cognos. I made a list that reflects Cognos. We should bring this up to Julie to see what she needs, we might be able to get away with what you suggest. I will flag this for Julie, but if it isn't dealt with by the time the next task meeting comes around, please bring it up then. Ttenbergen 23:32, 2020 October 18 (CDT) Further, I don't think we should introduce our own, fake service to replace the Cognos ones. Ttenbergen
*** I need to distinguish the MICU and SICU patients because that is how being reported and/or being requested.  --[[User:JMojica|JMojica]] 14:24, 2020 November 9 (CST)
**** Would reporting on "Hsc critical care/medicine" on one side, and "everything else in CC" on the other side, come close enough to the distinction you need? Ttenbergen 10:30, 2020 November 10 (CST)
***** is this what is really happening? Can the DC confirm if this is so - i.e. for those who are truly MICU patients, DC are manually putting the service as "HSC critical care/medicine" even though that is not the service showing in Cognos for that patient.  we don't want to give inaccurate data.  --[[User:JMojica|JMojica]] 11:53, 2020 November 10 (CST)
***** keeping in mind that I haven't done ICU collection for a while, I can say that when I look at all MICU patients in MICU, JKL3, JJ3 the service listed for them all is Critical Care Medicine,  SICU is a mixed bag but all have (HSC/Surgery) followed by a surgical service including but not limited to /trauma/orthopedics/plastics/vascular/neurosurgery/thoracics etc [[User:Lkaita|Lisa Kaita]] 18:50, 2020 November 19 (CST)}}
{{Discuss |
* Michelle said she is using "Hsc critical care/medicine" for MICUs – '''Michelle, can you confirm that this is always one of the several services that may be listed for an MICU patient? If so then using always the same would be a good idea. I could probably facilitate that in ccmdb to make it easier. Ttenbergen 09:18, 2020 November 5 (CST)
***As far as I can see, the only service that admits to MICU and the extension unit JKL3, is "Critical Care/Medicine". It is SICU that has multiple different services.
**** are the patients having CRRT at MICU not Critical Care/Nephro patients? -- I have been reporting CRRT from MICU and I am in the assumption they are nepro patients.  The big question to me is how helpful/useful these detailed services if we can't identify who went to MICU and SICU at HSC?  Who can help?  Allan?  --[[User:JMojica|JMojica]] 14:24, 2020 November 9 (CST)
** As a second thought to this, if there are services that are only ever used as a secondary entry, I would be able to filter those out so they don't clutter things. But we would want to be really sure they are '''always''' only a secondary, or we might miss patients. Ttenbergen 09:22, 2020 November 5 (CST)
***Sorry, I don't understand what you mean as a secondary entry.
**** In Cognos, patients often have more than one service listed for the same time frame. That's what I meant by secondary. I am trying to find out from Chastity why we would ave such additional services, since I had always understood it as if a pt is under only one service at a time. Ttenbergen 10:32, 2020 November 10 (CST)}}
 
{{Discuss |
* This is probably also an issue for other than HSC CC: where else gets multiple listings for the same timeframe, and what have they chosen to enter consistenly? Ttenbergen 09:18, 2020 November 5 (CST)  
}}
}}


Revision as of 21:48, 30 December 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 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
    • 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 first entry for Boarding Loc and for Service tmp entry need to have the same date and time because we only care about the portion of time in that earliest location that was under our service. So, e.g. if in ER the pt is accepted initially by surgery we don't care about the unit start date and time until our service takes over.
  • flagged this in Boarding Loc, whatever is answered there, this must become consistent. Ttenbergen 13:25, 2020 November 9 (CST)
  • SMW


  • Cargo


  • Categories

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

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

Several services being listed for the same timeframe was due to a problem with the Cognos extract. We now have new data that fixes this, but when I put it into CSS and CE there will be a lot of records to deal with, so still testing this before rolling it out. Ttenbergen 20:48, 2020 December 30 (CST)

  • 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

Facilitate viewing and entering Service tmp

It might be easier to enter these if we were able to see Cognos data for Service tmp entry separately from Boarding Loc. I am working on a Cognos2 setup for this, more to come.

when I get Cognos2 set up I will need to clean this out

  • added: no added date
  • action: no action date
  • 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=148353"