JALT Meeting - Rolling Agenda and Minutes 2023
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 |
| 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 |
| 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 |
_
_
JALT Meeting – January 11, 2023
last minutes from 2022 as starting point for this year, pls update/overwrite
- Present: ___
- Emails: LKaita@hsc.mb.ca; allan.garland@umanitoba.ca; JMojica@hsc.mb.ca; TTENBERGEN@hsc.mb.ca
- Minutes prepared by: AG
- Action items in BOLD
1. Followup about APACHE 2 Scoring
- Possible issue: When Allan summed the APS elements he got a slightly different mean value from the automatically calculated version. Julie to check on her automated calculation
- Tina and Julie will remove one of the (now identical) fields "ApTotal_Chronic" and "chronic_pts".
2. Visit_Admit_DtTm differences within same admission
- Tina reports that she has not received any such issues from Pagasa, and it's not clear if (a) there haven't been any vs. (b) there have been some but Pagasa has been dealing with them herself.
- Tina to ask Pagasa about this. If 'b' then we DO want them sent to Tina so she can send them to Charity to see if they can be fixed withing ADT/Cognos.
- Tina emailed Pagasa Ttenbergen 11:22, 2022 December 8 (CST)
3. BedHeldEnd DtTm - Per the last JALT meeting, the frequency of people leaving AMA (esp from ward) is not low. And, per Lisa, most of these are without notice. Thus it is not a trivial issue that there is a nontrivial difference between when the patient actually stops being under care vs. when the bed is released for reassignment.
- We agreed this mandates keeping track of both of these dates/times. Furthermore, a similar phenomenon occurs when a patient is sent to another hospital for a procedure, expecting to return (so the bed from the sending site is held) but then does not return.
- These 2 situations are easy for the DCs to identify and they always do so.
- So we will distinguish between:
- (a) Actual time under care, which is from Admit DtTm to the patient's Dispo DtTm -- we'll call this the patient's length of stay
- (b) What we'll call "Bed Assigned Time", i.e. from Admit DtTm to the time when the bed is released for reassignment, which we will call "BedHeldEndTime". This latter is generally available from Cognos (ADT), and Tina will create machinery to record BedHeldEndTime as a temp item. As above, this will ONLY be recorded in the situations when a patient leaves AMA but the bed is held for a bit hoping they come back (but they never do so) , or patient goes elsewhere for a procedure expecting them to return so bed is held but they never do come back.
- There will be 2 versions of BedHeldEndTime, i.e. BedHeldEndTime/AMA and BedHeldEndTime/Procedure.
4. Repeat item, regarding how to record time spent waiting for transfer (after Transfer Ready DtTm):
- We had previously decided to: (a) ignore such transfer delays <2 hrs, but (b) for all delays >=2 hrs to use the actual delay time.
- But this seems to conflict with the prior national Vital Signs Monitoring program (which is now defunct) which substracted 2 hrs from all actual delay intervals.
- Allan's rationale for not subtracting 2 hrs is as follows: While there are seemingly obligate delays in transferring a patient out (sending site getting the patient ready to travel and ensuring personnel are available, getting bed cleaned an ready in the accepting site and ensuring personnel are available) the concept of any given interval for these to occur is counter to the concept that we can and should always be striving to make out systems more efficient and reduce those delays.
- So, today Allan emailed Carmen, Rosanne and Bojan to get their input on this.
5. New question: How to deal with transfer delay in a recent case where patient in ICU was made ACP/C and then palliative ---> didn't die and indeed improved --> reversed the ACP/C and patient left ICU alive 7 days later.
- After discussion, we agreed that this is an extremely rare occurrence, and that rather than make a new rule for it, we will stick with the existing rule that transfer delays be calculated from when first transfer ready until the patient leaves. And also, this example is not fundamentally different from when a patient is ready to leave but gets sicker and the transfer is cancelled.
6. New question: Julie identified that there are cases (esp at St. B ICUs) where ER is the first boarding loc but within a few minutes (or sometimes simultaneous with) that boarding loc, a 2nd boarding loc of ICU is recorded.
- We think this most likely is a phenomenon of incomplete charts and so at our next JALT meeting Julie will let us know if this still occurs (and the # of them) in complete charts. Also, Lisa will ask the ICU DCs at St. B about this.
7. Next JALT meeting January 11, 2023 at 10 am -- this may be our last JALT meeting.