JALT Meeting - Rolling Agenda and Minutes 2025
List of items to bring to JALT meeting
Add to this by adding the following to the article where the problem is documented:
{{DiscussTask | JALT
* <question details>}}(this will bring it to Task if not addressed at JALT)
or
{{Discuss | JALT
* <question details>}}(this will not bring it to Task) Toggle columns: Last modified
| wiki page | question | Last modified |
|---|---|---|
| wiki page | question | Last modified |
| Check pre acute consistent | JALT
| 2025-12-17 6:30:28 PM |
| Chronic Health Facility |
| 2025-11-28 1:43:16 PM |
| Chronic Health Facility |
| 2025-11-28 1:43:16 PM |
| Chronic Health Facility | We have discussed lately that we might want to become more nuanced about some chronic care locations (Deer Lodge (DLC) and Riverview). I have removed the details from the above linked fields and consolidated here. Once this page is cleaned up this discussion entry can be removed.
| 2025-11-28 1:43:16 PM |
| Data Processor Portal | JALT
| 2026-01-06 6:31:16 PM |
| Definition of a Medicine Program Admission | JALT
| 2025-12-09 12:55:39 AM |
| Discharged to community | JALT
Just a placeholder for now because the idea of how we define dispo to community (or for that matter, re-admit Previous Location) in data came up re. things like Readmission to MedWard and others. We have the obvious "Home" but if someone is discharged to something like Dialysis, would that also count? How do we define? Ideally by a column in s_dispo table such as s_dispo.loc_type, but that one uses "non-patient" which it also uses for Deceased patients (should we just split that out?). There is probably even more to this. Likely Julie has more than one approach in reporting. This came up because we were looking to define this for LAU collection readmission data.
| 2026-01-22 3:40:32 AM |
| Dispo field | JALT
I thought we had decided at JALT to collect this as presented by EPR... do I remember this wrong? I had already added it in CCMDB.accdb Change Log 2025#2025-03-11-1. Ttenbergen 22:52, 11 March 2025 (CDT)
| 2026-01-27 5:10:08 PM |
| Intended1stSrvc | JALT
| 2026-01-29 4:54:48 PM |
| Intended1stSrvc | JALT
| 2026-01-29 4:54:48 PM |
| Patients residing in Manitoba with ambiguous MH Health coverage | JALT
| 2025-08-14 5:06:29 PM |
| Project NonTradLoc | JALT
| 2026-01-13 8:28:31 PM |
| Project Overstay2 |
| 2025-12-17 5:44:01 PM |
| Query check tmp AHC | JALT
| 2026-01-13 8:58:25 PM |
| Selkirk Mental Health Centre | JALT - Mental Health Facilities in Addition to Selkirk
| 2025-12-17 6:03:11 PM |
| Selkirk Mental Health Centre | JALT - Mental Health Facility Coding vs PCH
| 2025-12-17 6:03:11 PM |
| Sending Patients | JALT
| 2025-12-17 5:50:08 PM |
| Service tmp post-send consistency checks |
| 2025-11-27 10:44:27 PM |
| Service/Location field |
| 2025-12-24 8:46:05 AM |
| Standard data cleaning process |
| 2025-03-12 2:51:43 AM |
| STB Medicine Collection Guide | There was a discussion about the beds that had been "handed to" them... what was the outcome, should it go here?
| 2026-01-06 4:43:51 PM |
_
_
- New Item Collector Coding- Patient and laptop profiles- ADL and Charlson discrepancy, See Tina's email forwarded to JALT members May 29, 2025
- ICD10 categories, see Tina's email Nov 6, 2024, forwarded to JALT members
JALT 2025-07-25
- Present: Tina, Julie, Jen, Lisa, Allan
- Minutes by: Allan
1. Continued discussion related to 2025-05 Revision of concept around ICUotherService
- See June 25, 2025 minutes
- Allan raised the idea of having all ICU-to-ICU transfers remain part of the original ICU database record, both for ICU-to-ICU transfers within a site (e.g. MICU to SICU) and between sites (e.g. GH ICU to MICU).
- By use of the 3 variables: Boarding Loc, Service tmp entry and modified ICUotherService --- we would be able to slice and dice ICU days any way desired for reporting.
- This would include NOT re-calculating the APAPCHE scoring -- which makes sense not to do as the APACHE system is entirely based on scoring at the very first admission to any ICU.
- But 1 thing we might have to re-visit is identifying the reason for ICU transfer, i.e. the "new admit diagnosis". This is quite complicated, as some ICU-to-ICU transfers are NOT because of a new problem mandating different care, while others are for new problems. Of course, given that we track acquired diagnoses with their dates of onset, along with CCI-coded procedures (e.g. surgical procedures), it's likely we could do a good job of inferring the reason for both physical location changes and service changes. Before going further on this issue, Allan will discuss with Bojan -- email sent; Allan will also bring up Tina's idea of whether it would be useful for the ICU Directors Meeting to include someone from the database.
2. Regarding identifying the "subsets" of location types within Riverview and Deer Lodge.
- It always has been, and remains virtually impossible to accurately know which segment of those locations sent a patient to hospital. While Allan previously queried Bojan, who indicated that the ICU program has no deep need to know that, Tina has identified that other efforts she and Dan are involved with DO have such a need. This is made even more complicated because, as in other sites, a given ward/floor at Riverview or Deer Lodge can change its "type" over time. However, to date she has not been able to identify/locate anyone who can help us with this. Tina will continue to seek this information
3. Regarding Dispo field -- there are disparate options for Previous Location and Dispo.
- We went through those, and made some (minor) alterations.
- Lisa will find, and send around, the full lists of "admit from" and "disposition" locations currently in use in the ADT system. We will look at these to decide on additional possible changes
JALT 2025-06-25
- Present: Tina, Julie, Jen, Lisa, Allan
- Minutes by: Allan
1. 2025-05 Revision of concept around ICUotherService - We spent most of this meeting continuing discussion about tracking services and locations.
- BACKGROUND:
- There are 3 basic variables to track: Service the patient should be on; Service the patient is on; Actual physical location of the patient. From the POV of any given ICU (e.g. MICU) there are then 5 relevant patient categories:
| Group | Service should be on | Actual service | Actual location | Meaning |
|---|---|---|---|---|
| A | mine | mine | my ICU | my natural patients |
| B | mine | mine | different ICU | my boarders elsewhere |
| C | different | different | my ICU | somebody else's boarders in my ICU |
| D | mine | different | different | my "double boarders" elsewhere |
| E | different | different | my ICU | somebody else's "double boarders" in my ICU |
- B+D means insufficient beds in my ICU; C+E means insufficient beds in other unit(s)
- The current quarterly reporting "by unit" is currently (per Julie) actually by service (i.e. A+B+E), but in discussion with Bojan, he told Allan that he has always wanted and assumed he was getting by physical unit (i.e. A+C+E).
- We currently have 4 variables that have been, or are, used to identify services and locations:
- Boarding Loc -- tracks the patient's actual physical location; can change
- Service tmp entry -- tracks the service taking care of the patient; can change
- Service Location -- is the INITIAL service that cared for the patient at hospital admission; does not change. Of note, this field is used to create the unique record identifier and for other purposes unrelated to the service caring for the patient. Thus, not only would it be problematic to delete it, but even renaming it would cause problems.
- ICUotherService -- this is a temp entry that can change over time, and is currently only used at St. B. It contains 2 bits of information, e.g. "ACCU under MICU" means that the patient should be in ACCU on ACCU service but is in MICU on MICU service.
- We recognize that this data infrastructure is confusing and contains some duplication. Here is a suggestion of being able to accurately track all of A, B, C, D and E in the simplest way and with the smallest amount of modifications to existing data infrastructure:
- Keep the current meaning of Service/Location but make very clear in the Wiki that it is a legacy-type field we still use but not to consider it part of the clarification of actual service or location
- Keep Boarding Loc and Service tmp entry with their current meanings
- Alter the meaning of ICUotherService to be the service the patient SHOULD be on. With this simplifying change to the coding of this field, we can unambiguously use these 3 variables to partition care into A, B, C, D and E. We then must re-decide on the criterion that leads us to create a new ICU record. Currently it is when the actual service changes.
|
just came across Proposed future changes to Location and Transfer Ready and related fields about a previous consideration to changing related fields. Ttenbergen 13:28, 27 June 2025 (CDT) |
JALT 2025-05-29
- 2025-05 Revision of concept around ICUotherService - This entire 2.5 hour meeting was about the very complicated issues that relate to patient's: physical location (Boarding Loc), actual care service (Service tmp entry), and where the patient "should be" (which is currently coded in "Other ICU", and Service Location).
- This is made even more complicated in that Service Location also serves functions related to "grouping" for reporting.
- Other issues that relate include: what alterations in locations and/or service should result in starting a new record; how to code Dispo field and Previous Location in the case of ICU-to-ICU transfers with creation of a new record.
- After discussion we agreed that the next step will be to clarify precisely what kinds of reports are desired by our users. In this regard, Allan has worked out a schema for classifying patients based on 3 binary characteristics, and will discuss it with Bojan
- Physical location of patient
- Current care service of patient
- Which service the patient "should be on"
JALT 2025-03-11
- Visit Admit dttm discrepancies, see Visit_Admit_DtTm_differences_within_same_admission
- TT to build Link_suspect_visitAdmitDtTm_mult_to-from-home query
- we have no record of Julie's Standard data cleaning process and should document that
- New disposition options- barriers to discharge and how best to capture this, Dispo_field
- Chronic_Health_Facility⚓
- Alternative_Integrated_Accommodation_(AIA)
- Service/Location field Revisit MICU overflow in SICU
- in context also of ICUotherService, Service tmp entry and Boarding Loc and STB CC
- Allan spoke on March 14 with Bojan about the wishes/needs of Critical Care regarding this:
- The "basic" information provided by Boarding Loc and Service tmp entry enable tracking patient-days boarding (defined as a patient cared for by Service A but in location B) -- but they do NOT need to know which location B (e.g. an MICU patient boarding in SICU vs. JK)
- They do want to be able to track the number of patient-days in which a patient who would normally go to ICU A, instead is in ICU B where they are cared for by Service B. This is something that is now tracked by the complicated Service Location field. A simpler alternative to track this could be to have for each ICU record an optional field that identifies it (perhaps called "ICU other service") which has options such as "ICU other service-MICU", "ICU other service-SICU", etc, indicating the ICU service the patient "should have been on"
- Example: A patient that would normally be cared for in ICCS, but ICCS is full. So the patient goes to ICMS on the ICMS service. Here loc=ICMS, Service=ICMS and this database record has a flag for "ICU other service-ICCS".
|
|
Previous
For earlier minutes see JALT Meeting - Rolling Agenda and Minutes 2024