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 |
| 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)
| 2025-12-19 4:07:48 AM |
| Dispo field | JALT Task
| 2025-12-19 4:07:48 AM |
| Dispo field | JALT Task
| 2025-12-19 4:07:48 AM |
| Dispo field | JALT Task
| 2025-12-19 4:07:48 AM |
| Intended1stSrvc | JALT
| 2026-01-15 9:28:46 PM |
| Intended1stSrvc | JALT
| 2026-01-15 9:28:46 PM |
| Intended1stSrvc | JALT
| 2026-01-15 9:28:46 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 |
_
_
JALT Meeting – October 31, 2024
- 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. Discussion about ED-delays
- There are situations where a patient in an ICU or ward is transferred temporarily to ED to clear a bed, while remaining on the same service that was caring for them in the ICU or ward.
- After discussion we agreed that for the purpose of calculating delays in ED while on ICU or Medicine service but physically in ED, we will count the first (and only the first) such period in ED. Thus if a patient were to start in ED and spend interval T1 in ED on the ICU service --> go to ICU --> go back to ED to clear an ICU bed but remain on the ICU service for a time T2: the ED delay will be T1 only.
- BUT also, Allan sent Heather and Bojan a query about this today..
2. Discussion about ALC
- It turns out that the administration attempts to keep track itself of a variety of categories ("buckets") of admitted patients waiting to go elsewhere -- e.g. paneling, etc.
- While we agreed that we should not be concerned about seeking to ensure that our numbers are the same as their numbers --- Tina raised the question of whether we should have the same buckets/categories as they have.
- We agreed that we need a separate meeting to discuss this, to which Dan will be invited. In advance of that we will create lists of the 2 sets of buckets.
JALT Meeting – June 28, 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. With regards to the replatforming plan to PwC/Salesforce, we discussed how to store comorbid diagnoses in a separate patient-level object.
- Issues involved include: (a) while most comorbids are permanent, some can come and go, even more than once, and (b) there ARE errors made in recording comorbid diagnoses and these tend to be propogated forwards indefinitely ("chart lore").
- We agreed on a plan for a Salesforce Comorid "object" which for every comorbid ICD-10 code, there would be 1 or more entries/rows.
- Each row will have a Diagnosis field, and 2 date fields. The first date is the admission date when that comorbid is first recorded. The second date would remain empty as long as that comorbid continues to be recorded, but if there comes an admission date at which it is no longer present this second date would contain that admission date. Neither of these dates should be considered to reliably identify the onset or ending of the presence of that comorbidity.
- Complex example: Patient has CKD Stage 5 (N18.5) with 1st recording of it as a comorbid is at first ever ward admission on 2/3/2005.
- On that date this comorbidity object would gain an entry as follows:
- Code-----DateA-----DateB
- N18.5----2/3/2005
- At the ward admission on 4/5/2007 there is no recording of CKD as a comorbid. The collector searches and finds out that the patient had a kidney transplant in Ontario in 2006, and that's why it's gone, i.e. it really went away. Now the object should be:
- Code-----DateA-----DateB
- N18.5----2/3/2005--4/5/2007
- Z94.0----4/5/2007 <---- this is: Past history, transplanted kidney
- But, sadly, the transplant fails and at the next admission (to ICU now) on 6/7/2010 the CKD is back so now it'll read:
- Code-----DateA-----DateB
- N18.5----2/3/2005--4/5/2007
- Z94.0----4/5/2007
- N18.5----6/7/2010
- On that date this comorbidity object would gain an entry as follows:
2. We need to go over/remember why we previously decided that in identifying comorbid diagnoses we would use Admit Diagnosis and Acquired Diagnosis.
- Emailed Allan: You wrote up the decision to use all buckets for Charlson in a series of edits on 2019-02-13 in Charlson_Comorbidities_in_ICD10_codes. I don't see an entry corresponding to that date in a Task meeting and we didn’t have JALT meetings then. Do you have a record of what might have been discussed then that caused you to update it? Ttenbergen 12:34, 2023 July 5 (CDT)
3. We began a discussion about records with no labs at all.
- This could be real (e.g. very short admissions, with labs done in ED before coming to ward or ICU).
- But a problematic reason is when the person has 2 PHINs -- as occurs with a person initially a John/Jane Doe who is then identified.
- In this case, we have concrete examples of 1 PHIN/MRN having no labs with the actual labs from this encounter being in the 2nd PHIN/MRN.
- After discussion we decided to handle such "lab empty" situations as follows: Pagasa to identify them -->
- if LOS<6 hours ignore the problem as it's probably real
- if LOS>6 hours Pagasa to check in the EHR to see if this person/encounter actually has 2 PHINs/MRNs. If so she will collapse the 2 records into one, and ensure that the info for the actual labs be sent to Alun Carter with the next request.
JALT Meeting – April 19, 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. After further work and careful consideration our long-standing concept of limiting some ICD10 codes to specific bins (i.e. admit, acquired, comorbid), we recognized that doing so would have some positives, but that it also has some negatives. Most importantly though, was the recognition that even though some codes would not make sense in a given bin as a standalone item, it could make sense as a linked item. THUS, we agreed to cancel this planned work.
2. We need to update out Privacy Impact Assessment. Allan & Tina are working on this and have a Zoom meeting planned with Rosanne and Dan to discuss some items on 2023-04-26.
4. Update on Charlson comorbidity coding. Allan sent the final version to Tina, who will work with Julie to implement it.
5. New item: There are locations (e.g. HSC-GA7S) whose level of care changes over time. For example it has variously been a ward level and an IICU level. Thus we recognized that we need level of care to be a variable that can change over time. Tina to work on creating machinery to support that.
6. We discussed the request of Nelson Prudencio for ICU data.
- Nelson is a data person in the Shared Health Business Performance Group. He is apparently interested in comparing the indicators on our quarterly reports to the electronic data sources available to Shared Health.
- We agreed that Nelson should be invited to the next Steering Committee meeting. Allan emailed Rosanne today about this.
JALT Meeting – March 22, 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. Final decision about how to deal with delays (either in admission from ED, or for other transfers) -- given that the administrators (Bojan, Roseanne, Ebi) all agree that short delays are inconsequential, we agreed that from this point onwards, for all types of delays, our reporting will simply provide actual delays. No allowances will be made such that delays less than some value will be ignored.
2. Further work on whether/how to decide on limiting some ICD10 codes to specific bins (i.e. admit, acquired, comorbid). We agreed on a multiple stage process:
- First Allan will peruse the Excel file Julie/Tina made that indicates for each ICD10 code the # (%) in each of the 3 bins. This will be used to prescreen for items that might be prolematic -- DONE.
- Second, Lisa will assign 1 or more data collectors to go through and make preliminary "DISALLOW" decisions on them.
- Third, those disallowed in stage#2 will be reviewed for a final decision.
3. We need to update out Privacy Impact Assessment. Tina/Allan to meet April 5 at 9am for this purpose. Follow-up meeting with Roseanne and Dan booked for 2023-04-26.
4. Update on Charlson comorbidity coding. Tina resent this email to Allan and he responded on March 26, 2023.
5. Issues were raised about coding of possible repeat episodes of AKI. Allan has modified the AKI template regarding this.
JALT Meeting – Feb 2, 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. Update regarding those records where ER is the first boarding loc but the patient is there for only a few minutes, or even for Zero minutes.
- Per last time, we recognized that these are real when the patient is actually in an ER bed.
- What we don't yet know is about the cases (of which Julie found 147) where patient is admitted from ED triage without being put in an ED cot.
- The crux of this issue is exactly how our users utilize this information. If, as we suspect, it is to identify opportunities for substantially reducing such ER delays, then short delays (e.g. <10 mins for sure, and prob even <20 mins) are irrelevant as they're not likely remediable. If this is the case, then for collection and reporting purposes we should only report on those with ER delays >some threshold (e.g. 30 mins).
- Allan emailed Bojan, Carmen and Roseanne about this today ---> and they replied that indeed they only care about delays that are substantial.
2. We need to update out yearly PIA report. Tina will email the last one to Allan.
3. Discussion about the intention throughout the province to start collecting (voluntarily) on indiginous status and LGBTQ status. We recognized that this would be very interesting data to have in our databases.
- Allan related that "they" are working on a governance plan, so Tina will put a reminder on this item to revisit it December 2023.
4. Information suggests that the Dept of Medicine is (again) contemplating ceasing to fund the Medicine database.
- Allan spoke today with Bojan about this, particularly about the importance of ensuring that IF they do so, that the ICU Database will be protected. The plan is that Allan and Bojan will meet with Dr. Renner and Hana to discuss these issues.
5. Question about whether to include medicine patients on a soon-to-open ward at HSC, that might be a mixed (medicine and non-medicine patients) ward.
- Answer: Yes, but only include those on Medicine service.
6. We were informed that Hi Obs at HSC has recently had some patients on non-Medicine services (Respirology, Neurology). We agreed that we will only include the Medicine patients in our database.
7. Update on Charlson comorbidity coding. Allan to respond to the email sent by Tina on Jan 26, 2023.
JALT Meeting – January 11/12, 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. RESOLVED ITEM: 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 Chastity to see if they can be fixed withing ADT/Cognos.
- Tina emailed Pagasa about this December 8, 2022 but hasn't heard back, and again 2023-01-25.
3. RESOLVED ITEM: 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.Amant had a PEG, went back to St. Amant 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 has added this option to CCMDB as part of CCMDB.accdb Change Log 2023#2023-01-25.
- 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. RESOLVED ITEM: 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.
- Allan asked Bojan if this plan is OK, and he said yes.
5. RESOLVED ITEM: 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. RESOLVED ITEM: 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.
- Though we first thought this is a phenomenon of incomplete charts, Julie checked and it is NOT. After discussion we determined that this is a real phenomenon that occurs when ICU/ward team only agrees to accept the patient once a bed is available, and that once that happens the patient IS quickly transferred from ED to ICU or ward.
7. In looking into #6, Julie noticed that there are 2 sorts of admissions about which she is concerned:
- (1) Direct admit without passing through ED at all. These are real, and almost certainly are direct admissions from clinics to wards. So not a problem.
- (2) Admit from ED triage without being put in an ED cot. Again, these may well be real, and if so likely are admissions to wards (rather than ICUs). Julie will send a few of these to Lisa, who will check on them.
Previous
For earlier minutes see JALT Meeting - Rolling Agenda and Minutes 2022