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

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:


== Log ==
== Log ==
* 2025-09-25 started documentation for [[Intended1stSrvc]]
* [[JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-11-27]] confirmed we will need to ''keep'' [[Service tmp entry]], but will stop collecting [[ICUotherService]] and start [[Intended1stSrvc]]
* [[JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-10-08]] decided to ''stop'' collection of [[Service tmp entry]]
* 2025-09-25 - started documentation for [[Intended1stSrvc]]
* Text-search [[JALT Meeting - Rolling Agenda and Minutes 2025]] for the minutes of the discussions about this
* Text-search [[JALT Meeting - Rolling Agenda and Minutes 2025]] for the minutes of the discussions about this



Revision as of 17:35, 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.

Log

Legacy related