2020-03 HSC COVID unit transition

This page is about the transition of collection units at HSC to accommodate the new COVID unit.

Background

• Thursday March 19.20 – patients in HSC_D5_Pre_COVID will be moving to HSC_WRS3 (Level 3 of 735 Notre Dame Ave. old womens Hosp)
• Friday March 20.20 – patients in HSC_D4_pre_COVID will be moving to HSC D5
• Friday March 20.20 - D4 will be the new COVID-19 ward (HSC_D4_COVID ?)

HSC_D4_COVID

See HSC_D4_COVID for how we will collect the new ward.

Temporary naming

• changed names of the following in s_dispo table because the longer version was breaking sending:
  • HSC_D4_pre_COVID to HSC_D4_P
  • HSC_D5_Pre_COVID to HSC_D5_P
  • HSC_D4_COVID to HSC_D4_C

Once the last of these is sent we can name them back to their longer, more expressive versions.

• SMW

• Cargo

• Categories

deactivate HSC_D4_P / HSC_D5_P in s_tmp table once last pt has moved.

• SMW

• Cargo

• Categories

How will we identify these patients in EPR

EPR reports should work for the new locations as usual.

Transition plan

Due to the original transition plan duplicate records were created:

• one with the the original, pre-covid location (only renamed), and negative Pat_ID
• one with the future location, and negative Pat_ID

The plan was chagned as follows.

collector instructions

1. delete the duplicate record with the positive Pat_ID, and keep the one with the negative Pat_ID
2. change the Service/Location of the record to the new location (ie to HSC_WRS3 resp HSC_D5 )
3. enter the actual location as part of Boarding Loc:
   • for patients who had no location borrowing during transition:
     • change the "no borrow" line to "HSC_D5_P", resp "HSC_D4_P"
     • add a line for "HSC - Home medicine ward" with the time that the patient was actually moved
   • if there were patients who actually were in a borrow location during the transition, let's talk about how we would enter those

data processor instructions

The change of Service/Location will cause Orphans in Centralized data.mdb. Query COV_Pat_ID_matcher should help with cleanup. You may need to change the parameters H4/H5 to make it work for the respective laptop.

Expandoriginal plan, keep until fully backed out, but THIS IS NOT HOW WE WILL DO IT

Tina will pull data from the D4 and D5 laptops and collectors will need to do a CCMDB data.mdb restore from Regional Server before collection. Old D5 laptop (Laptop identifier H5) will need to do this first thing on the morning of Thursday, March 19 Old D4 laptop (Laptop identifier H4) will need to do this first thing on the morning of Friday, March 20 Tina will duplicate all records for units D4 and D5 that don't have a Dispo_DtTm. The Service/Location and Serial number sequences will be as follows. H5 (old D5) for patients who currently have Service/Location HSC_D5: original remains with renamed location HSC_D5_Pre_COVID, 'negative of Serial number as before, Dispo will be HSC_WRS3 other copy will be HSC_WRS3, same Serial number as before, Previous Location will be HSC_D5_Pre_COVID This may resulted in Orphans in Centralized data.mdb for these patients, since the the D5 entry was renamed and therefore the dispo_ID remains the same, but the serial was turned negative. Tina cleaned these up and emailed Pagasa with further info. H4 (old D4) for patients who previously had Service/Location "HSC_D4": original will remain with renamed location HSC_D4_pre_COVID, 'negative of Serial number as before, Dispo will be HSC_D5 other copy will be HSC_D5, same Serial number as before, Previous Location will be HSC_D4_pre_COVID, Accept_DtTm blank and Arrive_DtTm blank This may result in Orphans in Centralized data.mdb for these patients, since the the D5 entry was renamed and therefore the dispo_ID remains the same, but the serial was turned negative. Tina will discuss with Pagasa SMW Cargo Categories Collector will set the Dispo_DtTm and Arrive_DtTm to official transition time, doesn't so much matter what they use but should be consistent in the two records. Collectors will continue the same serial pool they used for the old Service/Location at the new one. That way they can just up the count from where they were. We will not need to add _a, _b, _d to the new locations because including the laptop identifier in D_ID takes care of that. Why not do this with one entry rather than 2? We could have had one entry, started at old location and then ended at new location. The transition might have been quite prolonged since a pt may have been on ward for long time, and might stay there for long time, especially with D5 population. We would have been in a transition status for months. Possibly longer than this new arrangement will stay. With the current dynamic state, best to have a transition we can complete in a predictable time frame.

Reporting

Med reporting is by ward and combined. service location D5 before March 19 and WRS3N can be together.

Cross checks

We have no CCMDB.accdb Data Integrity Checks yet for Boarding Loc , so that won’t limit our options. Is this the time to add cross-checks?

• SMW

• Cargo

• Categories

Have not yet checked how this will impact CFE Data Integrity Checks. Pagasa, of the top of your head which would be impacted and how?

• SMW

• Cargo

• Categories