Service Sending to ICU: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Data Collection Instructions: refactoring, there was some duplication
Line 6: Line 6:


== Data Collection Instructions ==
== Data Collection Instructions ==
=== for which patients to code ===
When you enter a new ICU patient a "Srv to ICU" will be automatically generated with item '''zz_enter'''. This item has to be changed to one of the following before you can check the tmp checkbox.  
For each patient who meets the following conditions:
:* '''critical care''' patient
:* was an '''inpatient''' before coming to ICU (even if arrived via temp location such as ER, procedure suite, OR or RR)
:* doesn't arrive from another ICU (i.e. not an inter or intra transfer)
:*The service is consulted in emergency, an OR or procedure is planned and an ICU stay is planned post-op but the patient was not on an inpatient ward.We need to know are we including patients from emergency or not in these cases? Collectors are doing this differently so we need to know.
:** If the patient had been accepted to a service, ie admitted and therefore now an inpatient, even if they were still physically in the ER, then '''yes, do'' code Service Sending with the specific service. However, if the pt was in ER but not accepted by any service and then they are sent up to the ICU, (or to another ICU in the city), then put in "not an inpatient" in service sending. --[[User:LKolesar|LKolesar]] 13:35, 2015 December 14 (CST)
**For patients moving from one ICU to another ICU, use only the "z_not applicable" in the service sending tmp. --[[User:LKolesar|LKolesar]] 13:35, 2015 December 14 (CST)
***for patients moving from CCU or CICU to another ICU, use the "z_not applicable" in the service sending tmp  - not 'Cardiology' or 'Cardiac Surgery'.
**For patients coming from a ward, use any in the ITEM except "z_not applicable", "z_not an inpatient", "zz_enter" in the sending service tmp.
**For patients coming from HOME, use "z_not an inpatient" in the sending service tmp.
***Admit from Home is most common to patients admitted to CCU.
**** Wouldn't the patients who went from home to angio and had +/-stent be under cardiology service? Like when they are accepted to a service in emergency with the intent to admit?


=== how to code ===
* one of the sending services if applicable
add a '''single''' tmp entry with the following:
* '''z_not an inpatient''' - if the patient was not an inpatient, eg came from home, usually only happens in CCU
:* '''Project''': '''Srv to ICU'''
* '''z_not applicable''' - pt moving from one ICU to another (including from CCU, '''don't use cardiology'' for this)
:* '''item''': the sending service, in case of OR, the service of the OR physician:
* '''z_other''' - any others such as EENT surgery at STB
:** Cardiac surgery
* '''z_unknown''' - if unknown service for patients coming from ward or OR or RR
:** Cardiology
* - the entry automatically put in for new CC patients, not accepted as final entry when checking tmp checkbox
:** Family Medicine (only relevant at sites that have family medicine)
:** General surgery (including ACSS and Trauma surgery)
:** Medicine
:** Neurosurgery
:** Ob/Gyne
:** Ortho surgery
:** Plastic surgery
:** Psych
:** Thoracic surgery
:** Urologic surgery
:** Vascular surgery
:** Nephrology  (added 21 March 2016)
:** '''z_not an inpatient'''  
:** '''z_not applicable''' - in this case an entry to the comment field in tmp will be required. (z_ to sort to bottom)
:** '''z_other''' - any others such as EENT surgery at STB
:** '''z_unknown''' - if unknown service for patients coming from ward or OR or RR
:** '''zz_other''' - the entry automatically put in for new CC patients, not accepted as final entry when checking tmp checkbox


The other tmp fields are '''not used''' (except in "not applicable" scenario)
The other tmp fields are '''not used''' (except in "not applicable" scenario)
=== special case - ER -> OR -> ICU ===
* Scenario: The service is consulted in emergency, an OR or procedure is planned and an ICU stay is planned post-op but the patient was not on an inpatient ward.
* Collection: If the patient '''had been accepted to a service''', ie admitted and therefore now an inpatient, even if they were still physically in the ER, then code Service Sending with the specific service. 
{{discussion}} Would pt ever go to OR without having been accepted? Ttenbergen 17:39, 2016 March 21 (CDT)


=== How to determine? ===
=== How to determine? ===
Go and find out. Ask on the ward. Talk to people. And: "in EPR there is a pt provider section that shows what service(s) the pt has been under, as well there is often an indication of service change in the EPR orders section [[User:Lkaita|Lisa Kaita]] 12:22, 2015 July 15 (CDT)"
Go and find out. Ask on the ward. Talk to people. In EPR there is a pt provider section that shows what service(s) the pt has been under, as well there is often an indication of service change in the EPR orders section.


== Start/End Dates ==
== Start/End Dates ==

Revision as of 17:39, 21 March 2016

for tracking which service is taking care of a patient in STB CCU, see CCU Service Tracking instead

Purpose

To identify the "sending service" or "originating service" for those patients's who where already in a prior inpatient location before coming to the ICU. (refer to Task Meeting Minutes April 13,2015). Note: This is different to the "service of the attending" during the patient's stay in ICU.

Data Collection Instructions

When you enter a new ICU patient a "Srv to ICU" will be automatically generated with item zz_enter. This item has to be changed to one of the following before you can check the tmp checkbox.

  • one of the sending services if applicable
  • z_not an inpatient - if the patient was not an inpatient, eg came from home, usually only happens in CCU
  • z_not applicable' - pt moving from one ICU to another (including from CCU, don't use cardiology for this)
  • z_other - any others such as EENT surgery at STB
  • z_unknown - if unknown service for patients coming from ward or OR or RR
  • - the entry automatically put in for new CC patients, not accepted as final entry when checking tmp checkbox

The other tmp fields are not used (except in "not applicable" scenario)

special case - ER -> OR -> ICU

  • Scenario: The service is consulted in emergency, an OR or procedure is planned and an ICU stay is planned post-op but the patient was not on an inpatient ward.
  • Collection: If the patient had been accepted to a service, ie admitted and therefore now an inpatient, even if they were still physically in the ER, then code Service Sending with the specific service.

Template:Discussion Would pt ever go to OR without having been accepted? Ttenbergen 17:39, 2016 March 21 (CDT)

How to determine?

Go and find out. Ask on the ward. Talk to people. In EPR there is a pt provider section that shows what service(s) the pt has been under, as well there is often an indication of service change in the EPR orders section.

Start/End Dates

  • Start: 2015-06-22
  • End: there is no planned end date

Template:CCMDB Data Integrity Checks

When you enter a new ICU patient a "Srv to ICU" will be automatically generated.

  • If that record is missing, you can't checkbox tmp
  • If that record has "enter" or "" as item, you can't checkbox tmp

currently impossible

  • Query s_tmp_Service_Sending_to_ICU - Error if:
    • not admitted from inpatient location ((S AdmitDischarge.inpatient = true)) but has "Srv to ICU" entry
    • admitted from inpatient location and one of
      • no "Srv to ICU" entry
      • has "Srv to ICU" = "z_not applicable" and no comment

Right now our consistency check would not allow someone from other hosp via ER. We won't be able to do this check until we have PrevInptLocation field. I will take that check out for now. Ttenbergen 11:50, 2015 June 24 (CDT)

  • Query s_tmp_Service_Sending_to_ICU_duplicate - error if more than one entry per patient Ttenbergen 15:35, 2015 June 22 (CDT)

SAS Program

  • The data is saved in table L_TmpV2 under project "Srv to ICU" of the centralized_data.mdb
  • The SAS program that reads the data is in X:\Julie\SAS_CFE\CFE_macros\CFE_ServiceSendingtoICU.sas

See also

to do before go live

  • Registry_Patient_Type#C-Cardiac_Type - awaiting confirmation
    • "Once this tmp study section is active we can go back to making the pt type relate to the type of diagnosis." (Laura K)
      • need to look into Ttenbergen 16:58, 2016 March 21 (CDT)

why a STB CC topic?

Template:Discussion why would this be in the STB Critical Care category specifically? Or the Site Specific Collection Guide? If not answered by next review I will remove category. Ttenbergen 16:58, 2016 March 21 (CDT)