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 |
| Collection of data on homelessness | JALT
* who should we clarify with, I would think if they have a MB PHIN or are self pay then you would choose MB, if they don't then I would choose Not known Lisa Kaita 21:25, 6 September 2025 (CDT)
| 2026-03-10 1:20:00 AM |
| 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-03-11 7:10:29 AM |
| John or Jane Doe patient | JALT
| 2026-03-10 1:35:07 AM |
| 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 |
| Transfer for bed management | JALT
| 2026-03-10 1:22:38 AM |
_
_
JALT Meeting – January 11, 2023
- Present: J,A,L,T
- 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. We now believe it is correct.
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. Regarding the new infrastructure to separately record both Dispo DtTm field (for when the patient is no longer under our care) and BedHeldEnd DtTm (for when the assigned bed is released).
- This only applies to situations when patient vacates the bed but it is "held" for expected or possible return of the patient.
- The main such situations are the patient does NOT return after: (a) going elsewhere for a procedure, or (b) leaving AMA and the bed is held for a day or 2 hoping she/he will return. Which of these occurred is recorded in TEMP.
- Today we recognized another such situation: Patient living at St.Amont had a PEG, went back to St. Amont hoping he'd do well, but the hospital bed was held for a day just in case. As this situation isn't covered by recording AMA or Procedure in TEMP, we agreed to add another possible TEMP entry for such occurrence, to be named something like "Other" or "Weird Reason". Tina/Julie will implement this.
- Julie also inquired about how to now report about bed-days and occupancy. After discussion, we agreed that she will alter reporting as follows:
- Primarily report on days patients were in beds being cared for in those beds (i.e. from Admit DtTm until Dispo DtTm.
- But also report the ADDITIONAL cumulative days when beds were held with the expectation patients would return to them, but did not, as directly above.
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. 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 12, 2023.