Intended1stSrvc

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:

Data Collection Instructions

• This variable was first created in October 2025. Along with Boarding Loc and Service tmp entry, it allows keeping track of every type of boarding (also called bed borrowing) and "double-boarding" bed-days reported quarterly for each ICU.
• With the initiation of this new variable, the old variable ICUotherService is retired/discontinued.
• Code it as the ICU service that the patient SHOULD HAVE BEEN ON on their very first day in any ICU while in that hospital
  • Leave it blank if the very first day in ICU in that hospital was, in fact on the "correct" ICU service, i.e. the one they should have been on -- and as this is the majority of all ICU records, this variable will usually be left blank.
  • e.g. Patient with acute MI admitted via ED. He should have been on ACCU service in ACCU but ACCU was full. So he got admited to ICMS instead on the ICMS SERVICE. Thus here Intended1stSrvc = ACCU

Transfer to Another ICU Service

• This is important regarding this variable as all the ICU-specific reporting relates primarily to the ICU service, not the ICU physical location -- thus a new ICU database record is created when a patient goes from 1 ICU service to another, but not if the patient goes from 1 physical ICU to another and stays on the same service.
• Instructions relating to coding this variable when a patient transfers from 1 ICU service to another:
  • For ICU-to-ICU transfers between hospitals, code this variable anew at the new hospital
  • For ICU-to-ICU transfers within a single hospital, just carry over the value of this variable from the prior ICU
    • continuation of above example: While he was in ICMS on the ICMS service he had an acute MI and had emergent bypass surgery, after which he went to CICU on the CICU service. As he stayed in the same hospital and just went ICU-to-ICU within it, for the new database record begun when he went to the CICU service, again Intended1stSrvc = ACCU, as carried over from his first ICU record at St. B.
• We note that the ICU service that a patient should be on 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, AND keeping better track of what service should be taking care of them would be difficult and very confusing.

Use tmp fields:

• Project: Intended1stSrvc
• Item:

Things to resolve

Things we need to resolve: We need to review anything that links to ICUotherService, and anything that page lists to. The "anything that links there" can be accessed by expanding the "related articles (expand)" at the bottom of ICUotherService. Ttenbergen 10:59, 25 September 2025 (CDT)

• SMW

• Cargo

• Categories

Log

• 2025-09-25 - change of ICUotherService to this way of coding the concept was first discussed, page generated for Allan to update.

See also STB Cardiac Care patients

Data Integrity Checks (automatic list)

none found

Related articles