LAU Collection Project: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
No edit summary
 
(32 intermediate revisions by 2 users not shown)
Line 1: Line 1:
More details to come
== Collection Instructions ==
== Collection Instructions ==
* Population: Lisa has organized charts and will provide collectors with a list
* Population: 200 charts per site, for those sites with [[Geri Rehab]] and [[LAU]], 50 charts for [[Geri Rehab]] and 150 for [[LAU]] with the following [[Service/Location]] entries:
* [[Boarding Loc]] - no [[Transfer Ready DtTm tmp entry]] for the LAU collection
** [[LAU]]
*** COH_LAU
*** SOH_LAU
*** VGH_LAU
** [[Geri Rehab]]
*** SOH_Geriatrics
*** VGH_Geriatrics
* Use the next [[Pat ID]] in your series, there is no need to manage them separately for this project
* [[Boarding Loc]] - use [[Transfer Ready DtTm]] to determine [[Transfer Ready DtTm tmp entry]]  
* [[Service tmp entry]] - no special instructions
* [[Service tmp entry]] - no special instructions
* special tmp entries for this:  
* special tmp entries for this:  
** [[LAU collection readmission data]]
** [[LAU collection readmission data]]
** [[Project Consults data]]
** [[Project Consults data]]
** [[ACP Status Collection for LAU]]
** [[ACP Status Collection]]
{{DL|
** [[LAU OT/PT consults]]
* check list for things we will need to include/finalize before collection start:
** [[LAU Public Trustee]]
** [[Dispo_field#Home_vs_Home_with_Support]] - "home with support" details
** [[LAU LTC consult]]
* we are including this right? [[User:Lkaita|Lisa Kaita]] 19:08, 4 March 2025 (CST)
 
** Once we get the details on [[Dispo_field#Home_vs_Home_with_Support]] resolved, that is the plan. [[User:Ttenbergen|Ttenbergen]] 18:51, 5 March 2025 (CST)
=== problems with [[Transfer Ready DtTm]] ==
}}
* Dan was right, this field is a mess trying to use our current definition with a population of patients that don't really fit an acute medicine profile.  If the patient went to Rehab the [[Transfer Ready DtTm]] will reflect the time they are accepted, if they became palliative the [[Transfer Ready DtTm]] will reflect when they became so, otherwise much of this was a judgment call, as many would be deemed transfer ready on admission by our definition.
* Decided to code time when the MD wrote medically stable for dc planning
 
=== Special Scenario - pt spends time in both [[LAU]] and [[Geri Rehab]] ===
* If the first [[Service tmp entry]] is an [[LAU]] service and [[Boarding Loc]], and the patient is later transferred to [[Geri Rehab]], create a second profile for the admission to the [[Service tmp entry]] [[Geri Rehab]] and [[Boarding Loc]]
 
=== Laptop setting changes during LAU collection ===
=== Laptop setting changes during LAU collection ===
* data collectors will their regular laptop for LAU collection and regular [[CCMDB.accdb]] for this project
* data collectors will use their regular laptop for LAU collection and regular [[CCMDB.accdb]] for this project
* collection for this is at a different site, so you need to change a setting to make the site-specific options available in the dropdowns
* collection for this is at a different site, so you need to change a setting to make the site-specific options available in the dropdowns
* See [[Settings (CCMBD.mdb)]] for how to access the settings
* See [[Settings (CCMBD.mdb)]] for how to access the settings
Line 24: Line 35:
* '''If you open a previously entered record for e.g. HSC while in e.g. VHG setting, some fields (eg. service location) will appear emtpy. The data is still there, but the dropdown doesn’t have it so the dropdown-driven box can’t show it. When you switch back to your usual setting the data will be visible, and it will remain visible in [[centralized_data.mdb]] either way. '''
* '''If you open a previously entered record for e.g. HSC while in e.g. VHG setting, some fields (eg. service location) will appear emtpy. The data is still there, but the dropdown doesn’t have it so the dropdown-driven box can’t show it. When you switch back to your usual setting the data will be visible, and it will remain visible in [[centralized_data.mdb]] either way. '''


==setup==
==Setup==
* [[CCMDB.accdb Change Log 2025#2025-03-06]]
** [[Project Consults data]]
*** added automatic "not entered" record to [[s_tmp table]]
*** added [[Query check Project Consults data]]
** [[ACP Status Collection]]
*** added options to [[s_tmp table]]
*** added [[query check ACP Status Collection]]
** [[LAU collection readmission data]]
*** added [[query check_LAU_collection_readmission_data]]
* [[CCMDB.accdb Change Log 2025#2025-03-04]] - Added [[LAU collection readmission data]] and [[Project Consults data]] to [[s_tmp table]]
* [[CCMDB.accdb Change Log 2025#2025-03-04]] - Added [[LAU collection readmission data]] and [[Project Consults data]] to [[s_tmp table]]
* [[CCMDB.accdb Change Log 2025#2025-03-03]] - Added data items to the tables.
* [[CCMDB.accdb Change Log 2025#2025-03-03]] - Added data items to the tables.
Line 79: Line 99:
}}
}}


== possible problems using program = "LAU" ==
== Collection dates ==
{{Discuss |
* Collection will happen between {{LAU Collection StartDt}} and {{LAU Collection EndDt}}
I was going to set the service_location entries in for the this project as program{{=}}"LAU". Then Lisa pointed out that this would not show the ADL tab, since it only shows for records where program is "Med". That made me realize that we have a lot of other code such as cross-checks that will also not work right if I set program{{=}}"LAU".
* The record set contains [[Dispo DtTm]] between
I am concerned that if I set program{{=}}"Med" we will similarly have these records show up mixed in with med data. For collection that will probably be fine since the cross checks etc should mostly be like for med records. But for anything Julie does with the data, this may be an issue.
** VGH Oct 6, 2024 and Dec 31, 2024
Once the collection project is complete we duplicate centralized_data.accdb and delete the LAU records from the master one, an only keep them in a project file. But: will this be a problem during the project? [[User:Ttenbergen|Ttenbergen]] 23:13, 5 March 2025 (CST)
** SOGH Dec 3,2024 and Dec 31, 2024
* Could we switch them to Facility_med, which Julie should be able to filter out, because they would be the 3 sites we don't normally collect? and in the tmp we will know if they are rehab vs LAU based on service, or there is probably alot more behind the scenes that I am missing???  [[User:Lkaita|Lisa Kaita]] 06:40, 6 March 2025 (CST)
** CGH Nov 22, 2024 and Dec 31, 2024
**As long as there is a data field which will identify the LAU's whether in tmp or in the service_location field (is this still active?) or serial number (have it started with high digit or with a letter followed by number) , I can filter them out if needed for analysis even if we keep them as Program {{=}}"Med".  The only concern is when we share the database to MCHP. Tina should remove those LAU's from Centralized data and PHI before I give them to MCHP.  --[[User:JMojica|JMojica]] 09:29, 6 March 2025 (CST)
* thanks Julie that makes sense, Tina should be ok then, or can you alter the serial numbers?  I think it is automated right? [[User:Lkaita|Lisa Kaita]] 10:08, 6 March 2025 (CST)


}}
== Identifying the project dataset ==
* [[Service/Location]] joined with [[s_dispo table]] will have [[S dispo.loc type]] = "LAU"
** will have program = "Med" because a bunch of functionality is tied in with Program, so if we made it "LAU" or "Family Med" we would need to make major changes to code and queries
** Julie is aware that this needs to be considered for the duration of the project collection
** after collection we can split [[Centralized_data.accdb]] so this sample becomes its own record set, and delete the records from the master db
*** this will need to be done before the next export to MCHP for sure


== Processing / Analysis ==
== Processing / Analysis ==
Line 94: Line 117:
\\ad.wrha.mb.ca\WRHA\HSC\shared\MED\MED_CCMED\CCMDB_Special_Projects\LAU collection
\\ad.wrha.mb.ca\WRHA\HSC\shared\MED\MED_CCMED\CCMDB_Special_Projects\LAU collection


[[Category: LAU Collection Project | *]]
[[Category:LAU Collection Project | *]]

Latest revision as of 16:37, 19 August 2025

Collection Instructions

= problems with Transfer Ready DtTm

  • Dan was right, this field is a mess trying to use our current definition with a population of patients that don't really fit an acute medicine profile. If the patient went to Rehab the Transfer Ready DtTm will reflect the time they are accepted, if they became palliative the Transfer Ready DtTm will reflect when they became so, otherwise much of this was a judgment call, as many would be deemed transfer ready on admission by our definition.
  • Decided to code time when the MD wrote medically stable for dc planning

Special Scenario - pt spends time in both LAU and Geri Rehab

Laptop setting changes during LAU collection

  • data collectors will use their regular laptop for LAU collection and regular CCMDB.accdb for this project
  • collection for this is at a different site, so you need to change a setting to make the site-specific options available in the dropdowns
  • See Settings (CCMBD.mdb) for how to access the settings
  • the one you need to change is for Hosp
  • take note of your current entry to restore it to that to go back to regular collection
    • settings are COH for Concordia, SOH for Seven Oaks, VGH for Victoria
  • If you open a previously entered record for e.g. HSC while in e.g. VHG setting, some fields (eg. service location) will appear emtpy. The data is still there, but the dropdown doesn’t have it so the dropdown-driven box can’t show it. When you switch back to your usual setting the data will be visible, and it will remain visible in centralized_data.mdb either way.

Setup

click to see specific additions   
  • table additions:
    • to S dispo table: VGH_LAU, SOH_LAU, COH_LAU
    • to s_tmp table for Service tmp entry:
      • COH MedicineLowAc/General
      • COH ALC Med LowAc/Panel Appr PCH
      • SOH Medicine LowAc/General
      • SOH ALCMedLowAc/Panel in Process
      • SOH Rehabilitation/Geriatrics
      • VGH medicine LowAc/General
      • VGH Rehabilitation/Geriatrics
      • VGH medicine LowAc/Community other
      • VGH medicine LowAc/Panel in Process
      • VGH medicine LowAc/Homecare
      • VGH medicine LowAc/Panel Appr other
      • VGH medicine LowAc/Panel Appr PCH
    • to s_tmp table for Boarding Loc:
      • COH-N1N
      • COH-N3E
      • COH-N3W
      • SOH-3BU1
      • SOH-3BU2
      • SOH-3BU3
      • SOH-3BU4
      • SOH-3BU5
      • SOH-3BU6
      • SOH-3BU7
      • SOH-3A10
      • SOH-3A11
      • SOH-3A12
      • SOH-5BU1
      • SOH-5BU2
      • SOH-5BU3
      • SOH-5BU4
      • SOH-5BU5
      • SOH-5BU6
      • SOH-5BU7
      • SOH-4BU4
      • SOH-4BU5
      • SOH-4BU6
      • SOH-4BU7
      • SOH-4AU8
      • SOH-4AU9
      • SOH-4AU11
      • SOH-4AU12
      • VGH-NU4N
      • VGH-NU4S
      • VGH-NU5N
      • VGH-NU5S
  • considered whether new entries were required for s_Cognos_Services table and s_Cognos_Units table; they are not

Collection dates

  • Collection will happen between 2025-03-15 and 2025-04-13
  • The record set contains Dispo DtTm between
    • VGH Oct 6, 2024 and Dec 31, 2024
    • SOGH Dec 3,2024 and Dec 31, 2024
    • CGH Nov 22, 2024 and Dec 31, 2024

Identifying the project dataset

  • Service/Location joined with s_dispo table will have S dispo.loc type = "LAU"
    • will have program = "Med" because a bunch of functionality is tied in with Program, so if we made it "LAU" or "Family Med" we would need to make major changes to code and queries
    • Julie is aware that this needs to be considered for the duration of the project collection
    • after collection we can split Centralized_data.accdb so this sample becomes its own record set, and delete the records from the master db
      • this will need to be done before the next export to MCHP for sure

Processing / Analysis

  • Project folder:

\\ad.wrha.mb.ca\WRHA\HSC\shared\MED\MED_CCMED\CCMDB_Special_Projects\LAU collection

Retrieved from "https://ccmdb.kuality.ca/index.php?title=LAU_Collection_Project&oldid=167406"