LAU Collection Project

Collection Instructions

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:
- VGH_LAU
- VGH Geriatrics
- COH_LAU
- SOH_LAU
- SOH_ 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
special tmp entries for this:

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

	This means the entries will need to be available as Previous Location and Dispo, and we can't restrict those by site, so they will be available everywhere. Lisa's email mentioned that Nick would want them available to be collected that way anyway. We will need to inform collectors of the change and update Previous Location and Dispo.

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.

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

	will need to update this when it's done: Collection will happen between 2025-03-01 and enter_date_when_completed The record set contains Dispo DtTm between enter_when_we_know_earliest and 2025-01-01

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.mdb 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

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