LAU Collection Project: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 9: Line 9:
** [[Project Consults data]]
** [[Project Consults data]]
** [[ACP Status Collection for LAU]]
** [[ACP Status Collection for LAU]]
{{DL|
** [[Dispo_field#Home_vs_Home_with_Support]]
* check list for things we will need to include/finalize before collection start:
 
** [[Dispo_field#Home_vs_Home_with_Support]] - "home with support" details
* 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)
}}
=== 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 their regular laptop for LAU collection and regular [[CCMDB.accdb]] for this project

Revision as of 14:20, 6 March 2025

More details to come

Collection Instructions

Laptop setting changes during LAU collection

  • data collectors will 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

possible problems using program = "LAU"

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". 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. 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? Ttenbergen 23:13, 5 March 2025 (CST)

  • 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??? Lisa Kaita 06:40, 6 March 2025 (CST)
    • 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. --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? Lisa Kaita 10:08, 6 March 2025 (CST)


  • SMW


  • Cargo


  • Categories

Processing / Analysis

  • Project folder:

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