Intended1stSrvc: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ttenbergen (talk | contribs) |
||
| Line 16: | Line 16: | ||
== Data Collection Instructions == | == Data Collection Instructions == | ||
* Code it as the ICU service that the patient '''SHOULD HAVE BEEN under upon initial admission to the ICU Service in this hospital''', i.e. at the start of [[Definition of a Critical Care Program Admission | this record]] | |||
*Code it as the ICU service that the patient '''SHOULD HAVE BEEN under | ** Leave it blank if the very first day in ICU in that hospital, the patient was, in fact under the "correct" ICU service, i.e. the service that ''should have'' been taking care of the patient -- and as this is the majority of all ICU records, this variable will usually be left blank. | ||
**Leave it blank if the very first day in ICU in that hospital, the patient was, in fact under the "correct" ICU service, i.e. the service that ''should have'' been taking care of the patient -- and as this is the majority of all ICU records, this variable will usually be left blank. | {{Ex | | ||
* | * Patient with acute MI admitted via ED. He should have been under the ACCU service in ACCU but ACCU was full. So he was admitted to ICMS instead '''''under the ICMS Service'''''. Thus here [[Intended1stSrvc]] = ACCU. }} | ||
=== Transfer to Another ICU Service === | === Transfer to Another ICU Service === | ||
*This is important regarding this variable as a new ICU database record is created when a patient goes from one ICU service to another, but not if the patient goes from one ICU to another while staying under the same service. | *This is important regarding this variable [[Definition of a Critical Care Program Admission | as a new ICU database record is created]] when a patient goes from one ICU [[Service tmp entry | service]] to another, but not if the patient goes from one ICU [[Boarding Loc]] to another while staying under the same service. | ||
====Instructions relating to coding this variable when a patient transfers from one ICU service to another==== | |||
*For ICU-to-ICU transfers ''between hospitals'' (inter-facility), code this variable anew at the receiving hospital | *For ICU-to-ICU transfers ''between hospitals'' (inter-facility), code this variable anew at the receiving hospital | ||
*For ICU-to-ICU transfers ''within a single hospital'' (intra-facility), carry over the value of this variable from the prior ICU record | *For ICU-to-ICU transfers ''within a single hospital'' (intra-facility), carry over the value of this variable from the prior ICU record | ||
***continuation of above example: While he was in ICMS under the ICMS service he developed cardiogenic shock and emergently went for bypass surgery, after which he went to CICU under the CICU service. As he stayed in the same hospital and went ICU-to-ICU within it, the new CICU profile would begin when he went to the CICU service, the [[Intended1stSrvc]] = ACCU, as carried over from his first ICU profile at SBGH | ***continuation of above example: While he was in ICMS under the ICMS service he developed cardiogenic shock and emergently went for bypass surgery, after which he went to CICU under the CICU service. As he stayed in the same hospital and went ICU-to-ICU within it, the new CICU profile would begin when he went to the CICU service, the [[Intended1stSrvc]] = ACCU, as carried over from his first ICU profile at SBGH. | ||
{{DiscussTask | | |||
* If this patient then moves to ACCU, do you still code [[Intended1stSrvc]] = ACCU, so they would be in ACCU with this tag? | |||
* What if they move to a Medicine service and then back to CC? This is only for ''continuous'' CC admission, right? | |||
}} | |||
*We note that the ICU service that a patient ''should be under'' can change, and so simply carrying over the [[Intended1stSrvc]] from the first day in any ICU can misrepresent where the patient "should be". But we discussed and are OK with that, as such changes represent only a fraction of a fraction of patients, and trying to keep better track of what service ''should be'' on throughout their episode of ICU care is difficult and very confusing. | *We note that the ICU service that a patient ''should be under'' can change, and so simply carrying over the [[Intended1stSrvc]] from the first day in any ICU can misrepresent where the patient "should be". But we discussed and are OK with that, as such changes represent only a fraction of a fraction of patients, and trying to keep better track of what service ''should be'' on throughout their episode of ICU care is difficult and very confusing. | ||
*Use tmp fields: | *Use tmp fields: | ||
* Project: {{PAGENAME}} <!-- leave this, it resolves to page name --> | * Project: {{PAGENAME}} <!-- leave this, it resolves to page name --> | ||
* Item: | * Item: | ||
** | {{Discuss | | ||
* How do we want to do this, we could use the currently active entries for CC in [[s_dispo table]]: | |||
* HSC_IICU | |||
* HSC_MICU | |||
* HSC_SICU | |||
* STB_ACCU | |||
* STB_CICU | |||
* STB_MICU | |||
or the full possible names under the CC services in [[S Cognos Services table]] that we actually use (in the last 2 months we had): | |||
Item | |||
* GH Critical Care / ACSS | |||
* GH Critical Care / General | |||
* GH Critical Care / General ICU | |||
* HSC Critical Care - MICU | |||
* HSC Critical Care / A Medicine | |||
* HSC Critical Care / A Non Teaching Med | |||
* HSC Critical Care / D Medicine | |||
* HSC Critical Care / D Non Teaching Med | |||
* HSC Critical Care / General | |||
* HSC Critical Care / H Medicine | |||
* HSC Critical Care / H Non Teaching Med | |||
* HSC Critical Care / Intermediate | |||
* HSC Critical Care / Medicine | |||
* HSC Critical Care / Neurosurgery | |||
* HSC Critical Care / Obstetrics | |||
* HSC Critical Care / Orthopedics | |||
* HSC Critical Care / Otolaryngology | |||
* HSC Critical Care / Plastics | |||
* HSC Critical Care / Respiratory | |||
* HSC Critical Care / Trauma | |||
* HSC Critical Care / Vascular | |||
* HSC Surgery / Neurosurgery | |||
* SBGH Cardiac / Cardiac Surgery | |||
* SBGH Cardiac / Crit Care Cardiology | |||
* SBGH Critical Care / Acute Care Surgery | |||
* SBGH Critical Care / B Service | |||
* SBGH Critical Care / C Service | |||
* SBGH Critical Care / Cardiac Surgery | |||
* SBGH Critical Care / Crit Care Cardiology | |||
* SBGH Critical Care / General | |||
* SBGH Critical Care / Medicine | |||
or we could use only the part before the "/" for the CC services in [[S Cognos Services table]]: | |||
* GH Critical Care | |||
* HSC Critical Care / Intermediate (this wouldn't be captured without the post-/ part) | |||
* HSC Critical Care | |||
* (but what would actually signify SICU, or would we again still need [[Service/Location]] for that? | |||
* SBGH Cardiac | |||
* SBGH Critical Care | |||
* SBGH Cardiac / Cardiac Surgery (this wouldn't be captured without the post-/ part) | |||
* SBGH Cardiac / Crit Care Cardiology (this wouldn't be captured without the post-/ part) | |||
=== Things to resolve === | === Things to resolve === | ||
| Line 45: | Line 96: | ||
* We need to move the change-related parts of what Allan wrote in [[Intended1stSrvc]] to [[2025-05 Revision of concept around ICUotherService]] to keep this page on target and keep the explanation in one place. [[User:Ttenbergen|Ttenbergen]] 15:05, 26 September 2025 (CDT) | * We need to move the change-related parts of what Allan wrote in [[Intended1stSrvc]] to [[2025-05 Revision of concept around ICUotherService]] to keep this page on target and keep the explanation in one place. [[User:Ttenbergen|Ttenbergen]] 15:05, 26 September 2025 (CDT) | ||
** I think I have done that, mostly, but someone should have a look at [[2025-05 Revision of concept around ICUotherService]] to confirm that the change is explained fully enough to make sense of the before and after data [[User:Ttenbergen|Ttenbergen]] 23:03, 28 September 2025 (CDT). | |||
}} | }} | ||
Revision as of 23:03, 28 September 2025
| Projects | |
| Active?: | proposed"proposed" is not in the list (active, planned, legacy, aborted in planning) of allowed values for the "ProjectActive" property. |
| Program: | CC |
| Requestor: | |
| Collection start: | |
| Collection end: | |
|
This project is not live yet, do not follow the instructions to stop the old collection yet. I hope to have this set up to start collecting with the new instructions Oct 1. For now, continue to use the instructions in ICUotherService. Ttenbergen 14:27, 26 September 2025 (CDT) |
Background
The Critical Care Program Quality Indicator Report
|
is that the right report? I have added this new data to that report's dependencies. If it's the wrong one it will need to be taken out of there. If other reports also use this, it will need to be added to them. If only that report you can remove this comment. Ttenbergen 15:20, 26 September 2025 (CDT) |
contains information about patients who are taken care of by a critical care service other then the one that normally would have taken care of them, generally due to capacity limitations. The actual service taking care of the patient is encoded in Service tmp entry, this variable encodes which service should have taken care of a patient initially upon admission, but did not. Along with Boarding Loc and Service tmp entry, this data allows keeping track of every type of boarding (also called bed borrowing) and "double-boarding" bed-days reported.
Data Collection Instructions
- Code it as the ICU service that the patient SHOULD HAVE BEEN under upon initial admission to the ICU Service in this hospital, i.e. at the start of this record
- Leave it blank if the very first day in ICU in that hospital, the patient was, in fact under the "correct" ICU service, i.e. the service that should have been taking care of the patient -- and as this is the majority of all ICU records, this variable will usually be left blank.
| Example: |
|
no parameters for Example template, some text may be hidden |
Transfer to Another ICU Service
- This is important regarding this variable as a new ICU database record is created when a patient goes from one ICU service to another, but not if the patient goes from one ICU Boarding Loc to another while staying under the same service.
Instructions relating to coding this variable when a patient transfers from one ICU service to another
- For ICU-to-ICU transfers between hospitals (inter-facility), code this variable anew at the receiving hospital
- For ICU-to-ICU transfers within a single hospital (intra-facility), carry over the value of this variable from the prior ICU record
- continuation of above example: While he was in ICMS under the ICMS service he developed cardiogenic shock and emergently went for bypass surgery, after which he went to CICU under the CICU service. As he stayed in the same hospital and went ICU-to-ICU within it, the new CICU profile would begin when he went to the CICU service, the Intended1stSrvc = ACCU, as carried over from his first ICU profile at SBGH.
|
{{{1}}} |
- We note that the ICU service that a patient should be under can change, and so simply carrying over the Intended1stSrvc from the first day in any ICU can misrepresent where the patient "should be". But we discussed and are OK with that, as such changes represent only a fraction of a fraction of patients, and trying to keep better track of what service should be on throughout their episode of ICU care is difficult and very confusing.
- Use tmp fields:
- Project: Intended1stSrvc
- Item:
{{Discuss |
- How do we want to do this, we could use the currently active entries for CC in s_dispo table:
- HSC_IICU
- HSC_MICU
- HSC_SICU
- STB_ACCU
- STB_CICU
- STB_MICU
or the full possible names under the CC services in S Cognos Services table that we actually use (in the last 2 months we had): Item
- GH Critical Care / ACSS
- GH Critical Care / General
- GH Critical Care / General ICU
- HSC Critical Care - MICU
- HSC Critical Care / A Medicine
- HSC Critical Care / A Non Teaching Med
- HSC Critical Care / D Medicine
- HSC Critical Care / D Non Teaching Med
- HSC Critical Care / General
- HSC Critical Care / H Medicine
- HSC Critical Care / H Non Teaching Med
- HSC Critical Care / Intermediate
- HSC Critical Care / Medicine
- HSC Critical Care / Neurosurgery
- HSC Critical Care / Obstetrics
- HSC Critical Care / Orthopedics
- HSC Critical Care / Otolaryngology
- HSC Critical Care / Plastics
- HSC Critical Care / Respiratory
- HSC Critical Care / Trauma
- HSC Critical Care / Vascular
- HSC Surgery / Neurosurgery
- SBGH Cardiac / Cardiac Surgery
- SBGH Cardiac / Crit Care Cardiology
- SBGH Critical Care / Acute Care Surgery
- SBGH Critical Care / B Service
- SBGH Critical Care / C Service
- SBGH Critical Care / Cardiac Surgery
- SBGH Critical Care / Crit Care Cardiology
- SBGH Critical Care / General
- SBGH Critical Care / Medicine
or we could use only the part before the "/" for the CC services in S Cognos Services table:
- GH Critical Care
- HSC Critical Care / Intermediate (this wouldn't be captured without the post-/ part)
- HSC Critical Care
- (but what would actually signify SICU, or would we again still need Service/Location for that?
- SBGH Cardiac
- SBGH Critical Care
- SBGH Cardiac / Cardiac Surgery (this wouldn't be captured without the post-/ part)
- SBGH Cardiac / Crit Care Cardiology (this wouldn't be captured without the post-/ part)
Things to resolve
|
|
Things we need to resolve:
|
Log
- 2025-09-25 - change of ICUotherService to this way of coding the concept was first discussed, page generated for Allan to update.
- See 2025-05 Revision of concept around ICUotherService for decisions leading up to implementation
Data Integrity Checks (automatic list)
none found