STB is opening a number of beds on STB_A7S and STB_A7W. Patients from our usual STB_E6 unit will move there, and the physical E6 location will become the COVID ward.
notes on plans that changed
there was a plan to only change names for some of the records, but because the names are really only linked values in the s_dispo table you can't change them for some, you have to make a new entry.
there were thoughts about continuing to collect these patients as STB_E6 even once on A7*; this might have been practical for that collector but would have been confusing for other collectors since their previous location and dispo fields should match, so we decided to name the Service/Location as it actually is.
if the patient was transferred there before the move date, you can leave that. If they were transferred there after the move date but before we put the new entries in place, you may need to change the dispo to STB_A7S resp STB_A7W. Don't worry too much about this, we can fix it at the back end, but if you notice it please fix.
data processor instructions
How will Pagasa fix Previous Location / Dispo for related records? Same question for the other two hospitals...
SMW
Cargo
Categories
set something up to help Pagasa with these specific orphans.
SMW
Cargo
Categories
Reporting
Cleanup
We needed to use P for Pre_COVID and C for COVID since full names would have broken D_ID in sending. Once the last pt of a location is sent, we can change those names in the s_dispo table.
SMW
Cargo
Categories
deactivate STB_E6_P in s_Tmp table once last pt has moved.
SMW
Cargo
Categories
Cross checks
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?
