2020-03 STB COVID unit transition: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
This page is about the transition of collection units at STB to accommodate the new COVID unit.  
This page is about the transition of collection units at STB to accommodate the new COVID unit.  
{{Discuss |
* please review and shoot holes into before we implement.
* Do we need to separate W and S? or simply as one STB_A7.--[[User:JMojica|JMojica]] 16:51, 2020 March 26 (CDT)  }}


== Background ==
== Background ==
Line 17: Line 13:
* 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 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.  
* 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.  
* we were going to have "STB_A7S" and "STB_A7W" but this was changed to [[STB_A7_B]] since it's the same ward
  }}
  }}


== Transition plan ==
== Transition plan ==
* In [[s_dispo table]]:
* In [[s_dispo table]]:
** We will create new entries for :
** We create new entries for :
*** [[STB_E6_C]]
*** [[STB_E6_C]]
*** [[STB_A7S]]
*** [[STB_A7_B]]
*** [[STB_A7W]]
** We change [[STB_E6]] to [[STB_E6_B]]
** We will change [[STB_E6]] to [[STB_E6_P]]
*** STB_E6a --> STB_E6aB
*** STB_E6b --> STB_E6bB
*** STB_E6d --> STB_E6dB
* In [[s_tmp table]]:  
* In [[s_tmp table]]:  
** we will add a "STB_E6_P" entry that will stay active only during this transition.  
** we add [[Boarding Loc]] entry "STB_E6_P" that will stay active only during this transition.  
{{DT | Need to deactivate STB_E6_P once transition is over. }}


=== collector instructions ===
=== collector instructions ===
Line 43: Line 43:


=== data processor instructions ===
=== data processor instructions ===
{{Discuss |
No fix should be required for [[Previous Location]] / [[Dispo]] since the entry was re-named.  
* How will Pagasa fix [[Previous Location]] / [[Dispo]] for related records? Same question for the other two hospitals... }}
 
{{DT |  
{{DT |  
* set something up to help Pagasa with these specific orphans. }}
* set something up to help Pagasa with these specific [[Orphans in Centralized data.mdb]]. If I don't connect with her before she wants to do this, essentially this would be a query that filters to STB_E6 and STB_E6_B, and wherever there are two, delete the E6 entry. }}


== Reporting ==
== Reporting ==

Revision as of 21:39, 2020 March 29

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

Background

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.

Date of change

2020-Mar-26

  • last client moved out of E6 to A7 units on: 2020-Mar-25
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.
  • we were going to have "STB_A7S" and "STB_A7W" but this was changed to STB_A7_B since it's the same ward

Transition plan

Need to deactivate STB_E6_P once transition is over.

  • SMW


  • Cargo


  • Categories

collector instructions

E6 / A7 Collector

  • STB_E6 patients already on the laptop will automatically have their Service/Location changed to STB_E6_P
    • patients who are discharged while still on that ward don't require further changes
    • patients who are moved to one of the A7 locations should
      • have their Service/Location changed to STB_A7S resp STB_A7W
      • a Boarding Loc entry added for the first part of their stay on STB_E6_P
      • a move to "STB - Home medicine ward" should be added with the time they were moved

All other collectors

  • patients with STB_E6 in their Previous Location or Dispo fields will automatically have those changed to STB_E6_P
  • 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

No fix should be required for Previous Location / Dispo since the entry was re-named.


  • set something up to help Pagasa with these specific Orphans in Centralized data.mdb. If I don't connect with her before she wants to do this, essentially this would be a query that filters to STB_E6 and STB_E6_B, and wherever there are two, delete the E6 entry.
  • 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?
  • SMW


  • Cargo


  • Categories

Related articles

Related articles: