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

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 20: Line 20:
* 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


== Legacy related ==
== Related ==
* [[Project Legacy Co-managed]]
* [[Project Legacy Co-managed]]
* [[Proposed future changes to Location and Transfer Ready and related fields]]


[[Category:Change explainer page]]
[[Category:Change explainer page]]

Revision as of 18:12, 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

Related