2025-05 Revision of concept around ICUotherService: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
We recognized an embarrassingly complicated mesh of meaning between [[ICUotherService]]/[[Service Location]]/[[Boarding Loc]]/[[Service tmp entry]] and decided to stop collecting [[ICUotherService]] and replace it with [[Intended1stSrvc]].
We recognized an embarrassingly complicated mesh of meaning between [[ICUotherService]]/[[Service Location]]/[[Boarding Loc]]/[[Service_tmp entry]] and decided to stop collecting [[ICUotherService]] and replace it with [[Intended1stSrvc]].


[[ICUotherService]] was coding the info as a pair like "ACCU under MICU service", which could become inconsistent with what was collected in the [[Service Location]] in the case when both the service and the location were borrowed. This meant we didn't report on this correctly for a long time. Since location is already conclusively coded in [[Boarding Loc]], and Service in [[Service tmp entry]], we just needed a way to code when the patient was  not being taken care of by the service that "should have" taken care of them on admission. We added [[Intended1stSrvc]] to collect that part and will stop collecting [[ICUotherService]].
[[ICUotherService]] was coding the info as a pair like "ACCU under MICU service", which could become inconsistent with what was collected in the [[Service Location]] in the case when both the service and the location were borrowed. This meant we didn't report on this correctly for a long time. Since location is already conclusively coded in [[Boarding Loc]], and Service in [[Service tmp entry]], we just needed a way to code when the patient was  not being taken care of by the service that "should have" taken care of them on admission. We added [[Intended1stSrvc]] to collect that part and will stop collecting [[ICUotherService]].
We also decided to no longer use the [[Service_tmp entry]] data for [[Critical Care records]]. There are implications for this:
{{DL | {{DJ |
Lose ends:
* [[Definition of a Critical Care Program Admission]] uses the [[Service_tmp entry]]
* [[STB CICU Admissions start at Arrive DtTm]] as linked from [[Service_tmp entry]] - can that go / become legacy?
* someone will need to review the ''108 links from other pages to service_tmp entry'' (link was breaking discuss, see below discussion) to make sure that we are not breaking anything by changing this. [[User:Ttenbergen|Ttenbergen]] 16:55, 27 November 2025 (CST)
}} }}
[https://ccmdb.kuality.ca/index.php?title=Special:WhatLinksHere/Service_tmp_entry&limit=500 108 links from other pages to service_tmp entry]


== Log ==
== Log ==

Revision as of 17:55, 27 November 2025

We recognized an embarrassingly complicated mesh of meaning between ICUotherService/Service Location/Boarding Loc/Service_tmp entry and decided to stop collecting ICUotherService and replace it with Intended1stSrvc.

ICUotherService was coding the info as a pair like "ACCU under MICU service", which could become inconsistent with what was collected in the Service Location in the case when both the service and the location were borrowed. This meant we didn't report on this correctly for a long time. Since location is already conclusively coded in Boarding Loc, and Service in Service tmp entry, we just needed a way to code when the patient was not being taken care of by the service that "should have" taken care of them on admission. We added Intended1stSrvc to collect that part and will stop collecting ICUotherService.

We also decided to no longer use the Service_tmp entry data for Critical Care records. There are implications for this:

Lose ends:

  • SMW


  • Cargo


  • Categories
  • SMW


  • Cargo


  • Categories

108 links from other pages to service_tmp entry

Log

Legacy related