2025-05 Revision of concept around ICUotherService
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:
|
|
108 links from other pages to service_tmp entry
Log
- JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-11-27
- confirmed we will need to keep Service tmp entry, but will not use the data for Critical Care records and will not do Service tmp post-send consistency checks for them; Julie and Tina will review need of checks for Medicine records
- we 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