Service tmp entry: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
→Data Collection Instructions: applied Template:Ex to collapse example so it doesn't clutter the basics but is there if needed. The tweaks and example should address the discussions so I will clear them out. If there are still questions, please put in discussion as needed.
Line 18: Line 18:
**select the appropriate service from the dropdown list, enter the date and time the service first took over e.g. accept time for those coming from ER
**select the appropriate service from the dropdown list, enter the date and time the service first took over e.g. accept time for those coming from ER
**Add a new entry for service, only if the service changes during their stay.
**Add a new entry for service, only if the service changes during their stay.
{{Ex |
*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
*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
*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
*second entry in TMP would be '''project Service''', '''Item''' choose HSC H medicine, Column E enter Oct 17,2020, Column M enter 1500
 
  }}
 
{{Discuss|
* What date and time are we attaching to this? Accept or Arrive? [[User:Surbanski|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)
**I am not clear here - the first entry should be the start date of the current service (same as Accept_DtTm) and not the time of next service start date?  The start of the next service would imply the end of the current (or prior) service. the difference between the next service start and current service start is the LOS  of the current service.  The last service start date will be subtracted to the DISPO date to get the LOS of the last service.  We should make it consistent with the Boarding loc which is based on arrive date. --[[User:JMojica|JMojica]] 10:03, 2020 October 16 (CDT)
*** Yes, first entry is accept dttm, second (if any) is next service start Ttenbergen 15:01, 2020 October 16 (CDT)
}}
{{Discuss |
* At the Grace - for those that move from medicine to medicine do we need to add a new Service entry? I'm assuming no because they're still under the medicine service [[User:Surbanski|Surbanski]] 10:17, 2020 October 16 (CDT)
** Same as other sites: only put a new service entry if the service changes. If only the physical location changes, only enter a [[Boarding Loc]]. That distinction is the whole point of separating the two. Ttenbergen 15:01, 2020 October 16 (CDT)
}}
 
{{Discuss|
* 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)}}


== Loose ends ==
== Loose ends ==

Revision as of 22:01, 18 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 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
    • select the appropriate service from the dropdown list, enter the date and time the service first took over e.g. accept time for those coming from ER
    • 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

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


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

Facilitate viewing and entering Service tmp

  • should be able to add something to Cognos Admitter and Patient Viewer Tab Cognos ADT that facilitates entering and viewing this; will delay that until we have collected this for a little while; 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. And if we can stop entering Accept and Arrive, and service location becomes trivial we can safe space.

The thing is, that tab is getting very full, and I will need to either make fonts smaller or squeeze an area to show even fewer lines. I wonder how best to do that in a way that works for collectors. It’s on the “later” pile for now, but for sure something I want to deal with. Open to suggestions. Ttenbergen 12:24, 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)

 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=146564"