Change of remaining location names from "our" names to EPR/Cognos names: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
Line 6: Line 6:


However, there were emails and/or wiki discussions after this that raised concerns.  
However, there were emails and/or wiki discussions after this that raised concerns.  
{{Discuss |
*It's a blur to me now, but I seem to remember people still raising concerns about this change after the meeting. If you have ongoing concerns, please post them here. [[User:Ttenbergen|Ttenbergen]] 16:36, 2021 May 6 (CDT)
}}


== Preparation needed ==
== Preparation needed ==
Line 18: Line 14:
{{Discuss|
{{Discuss|
* sending excel file to Julie and Lisa to validate [[User:Ttenbergen|Ttenbergen]] 17:19, 2022 January 20 (CST)
* sending excel file to Julie and Lisa to validate [[User:Ttenbergen|Ttenbergen]] 17:19, 2022 January 20 (CST)
** Lisa and Julie have reviewed and annotated the excel file. Tina needs to review and update s_tmp table. [[User:Ttenbergen|Ttenbergen]] 14:23, 2022 January 25 (CST)
}}
}}
== Collector instructions ==
'''''Work in progress, don't go ahead with these yet! '''''
* we would make available the new unit entries as per wording in [[Cognos EPR Report]] as options for the [[Boarding Loc]] dropdown
** we will keep the old ones around for now - if we removed them there would likely be problems in CCMDB
*** we will leave both old and new active until all are changed 
* Nothing to change in [[Previous Location]], [[Pre-admit Inpatient Institution]], [[Dispo]]  
* Nothing to change in [[Previous Location]], [[Pre-admit Inpatient Institution]], [[Dispo]]  
** we already use generic *_Med in medicine, so it already doesn't allow automatic mapping
** we already use generic *_Med in medicine, so it already doesn't allow automatic mapping
Line 35: Line 26:
* [[CUS]]
* [[CUS]]
* [[Using Cognos2 to keep track of patients]]
* [[Using Cognos2 to keep track of patients]]
=== How will we code the HOBS status of a unit ===
Julie reports differently on HOBS units, e.g. the [[Transfer Ready DtTm]] is separate for them. So Julie needs to be able to determine whether a pt is in HOBS. Currently this is done by naming a unit HOBS, i.e. HOBS is not named with its actual location but by its special status. The actual location of the HOBS unit has changed over time and will probably change again.
Julie, Lisa and Tina discussed and agreed that all three of the following options are ''possible'' but we have not come to a conclusion which is better.
{{Discuss |
* Further discussion about this is planned. Tina to book meeting. [[User:Ttenbergen|Ttenbergen]] 14:23, 2022 January 25 (CST)
}}
We have several possible ways to deal with this going forward:
* continue designating the HOBS property in the name
** Pros:
*** easy for Julie because the info is implied
** Cons:
*** breaks the Cognos tracking
*** makes it hard to assign other meta data to units in the future (eg covid or palliative or other status of a unit)
* code boarding loc as Cognos/EPR name and put a check mark if the unit is currently a HOBS unit
** Pros:
*** easy for Julie because the info is right in the data she has connected already anway
*** works with Cognos tracking
** Cons:
*** collectors would continually have to enter this for a HOBS unit
*** then we would need a cross check to make sure this is consistently entered, yet if it's entered always for a unit, then why enter it?
*** makes it hard to assign other metadata to units in the future (eg covid or palliative or other status of a unit)
* store the metadata of a unit in a different table linked by actual location name, with start and end dates
** Pros:
*** works with Cognos tracking
*** is invisible / no action required to collectors in day-to-day data entry
*** is flexible and extensible to other metadata we may want to use in the future (but currently would be used for only one thing)
** Cons:
*** it is more difficult for Julie to set up (but this is a one-time task)
*** collectors would no longer actually declare that a pt is HOBS, so there is concern that we would not find out if a unit changes status in a timely manner
== Collector instructions ==
'''''Work in progress, don't go ahead with these yet! '''''
* we would make available the new unit entries as per wording in [[Cognos EPR Report]] as options for the [[Boarding Loc]] dropdown
** we will keep the old ones around for now - if we removed them there would likely be problems in CCMDB
*** we will leave both old and new active until all are changed 


=== Transition plan ===
=== Transition plan ===
* The [[Boarding Loc]] entries for all records currently on the laptops will be manually changed by the respective collectors collectors starting on <code>[[#Change Date]]</code> and before <code>[[#Change Date]]</code> + 7 days.
We are planning to do this on admissions start Jan 1, 2022 (2022Q1), so some retrospective entries will be needed.
{{Discuss |
* How would that work, practically, when some patients discharged since Jan 1 may have been sent already? Or have they not been? Or do we need to tell collectors to hold off on them? [[User:Ttenbergen|Ttenbergen]] 14:23, 2022 January 25 (CST)
}}


== Tina's instructions ==
== Tina's instructions ==
Line 55: Line 92:


== Change Date ==
== Change Date ==
We are planning to do this on admissions start Jan 1, 2022 (2022Q1), so some retrospective entries will be needed.
Working on implementation date. [[User:Ttenbergen|Ttenbergen]] 12:56, 2022 January 25 (CST)
Working on implementation date. [[User:Ttenbergen|Ttenbergen]] 12:56, 2022 January 25 (CST)


== Status ==
== Status ==
*2021-04-29 - Julie email confirmed that she doesn't need the specific info listed on these pages since we now get the details in [[Boarding Loc]]. [[User:Ttenbergen|Ttenbergen]] 15:43, 2021 April 29 (CDT)
*2021-04-29 - Julie email confirmed that she doesn't need the specific info listed on these pages since we now get the details in [[Boarding Loc]]. [[User:Ttenbergen|Ttenbergen]] 15:43, 2021 April 29 (CDT)
* ?? [[Change of GRA location names from "our" names to EPR/Cognos names|completed at GRA]]
{{DJ |
* As per email from 2021-05-04, "The question is whether to use the generic HIGH OBS and IMCU instead of physical locations H7S or L2ME if we would like to  enter the physical locations COGNOS is showing.  If the decision is physical Locations – how would I know which are the high obs  wards? we would have to put it in the comments, so are we any further ahead?" How does that feature into our plan to move all to Cognos values? On the same note, it appears that GRA is using two designations for PACU dependign on post-OR vs Covid use...
** I say we use the actual location. Whether or not that location is currently HOBS or otherwise might change. Boarding Loc is a location, not a location type. This would make working [[Level of care hierarchy]] harder; we would likely need to add a new table that includes when units were what level, ie location, level startdttm. Are there other things it would make harder?
}}
* 2021-04-15 [[Task_Team_Meeting_-_Rolling_Agenda_and_Minutes_2021#ICU_Database_Task_Group_Meeting_–_April_15,_2021 | Task Meeting]] decided we should change these to the designations in Cognos.
* 2021-04-15 [[Task_Team_Meeting_-_Rolling_Agenda_and_Minutes_2021#ICU_Database_Task_Group_Meeting_–_April_15,_2021 | Task Meeting]] decided we should change these to the designations in Cognos.



Revision as of 15:23, 2022 January 25

We use different names for locations in s_dispo table (Previous Location, Pre-admit Inpatient Institution, Dispo) than in Cognos EPR Report, and sometimes different again in Boarding Loc. We have done a Change of GRA location names from "our" names to EPR/Cognos names, this page is about doing the same change at our other sites.

Decision to go ahead

We decided to go ahead with this change at Task_Team_Meeting_-_Rolling_Agenda_and_Minutes_2021#ICU Database Task Group Meeting – April 15, 2021 (#3), confirmed at the next Task meeting and again the one after.

However, there were emails and/or wiki discussions after this that raised concerns.

Preparation needed

The related data dropdowns live in three tables: s_Cognos_Units table, S dispo table, s_tmp table.

  • sending excel file to Julie and Lisa to validate Ttenbergen 17:19, 2022 January 20 (CST)
    • Lisa and Julie have reviewed and annotated the excel file. Tina needs to review and update s_tmp table. Ttenbergen 14:23, 2022 January 25 (CST)
  • SMW


  • Cargo


  • Categories
  • do we want to or have to make ICU locations consistent between s_dispo and boarding loc as we roll this out? Do Julie or Pagasa use these for linking? Ttenbergen 14:02, 2022 January 25 (CST)
  • SMW


  • Cargo


  • Categories

Other pages that will need to be confirmed to not need updating:

How will we code the HOBS status of a unit

Julie reports differently on HOBS units, e.g. the Transfer Ready DtTm is separate for them. So Julie needs to be able to determine whether a pt is in HOBS. Currently this is done by naming a unit HOBS, i.e. HOBS is not named with its actual location but by its special status. The actual location of the HOBS unit has changed over time and will probably change again.

Julie, Lisa and Tina discussed and agreed that all three of the following options are possible but we have not come to a conclusion which is better.

  • Further discussion about this is planned. Tina to book meeting. Ttenbergen 14:23, 2022 January 25 (CST)
  • SMW


  • Cargo


  • Categories

We have several possible ways to deal with this going forward:

  • continue designating the HOBS property in the name
    • Pros:
      • easy for Julie because the info is implied
    • Cons:
      • breaks the Cognos tracking
      • makes it hard to assign other meta data to units in the future (eg covid or palliative or other status of a unit)
  • code boarding loc as Cognos/EPR name and put a check mark if the unit is currently a HOBS unit
    • Pros:
      • easy for Julie because the info is right in the data she has connected already anway
      • works with Cognos tracking
    • Cons:
      • collectors would continually have to enter this for a HOBS unit
      • then we would need a cross check to make sure this is consistently entered, yet if it's entered always for a unit, then why enter it?
      • makes it hard to assign other metadata to units in the future (eg covid or palliative or other status of a unit)
  • store the metadata of a unit in a different table linked by actual location name, with start and end dates
    • Pros:
      • works with Cognos tracking
      • is invisible / no action required to collectors in day-to-day data entry
      • is flexible and extensible to other metadata we may want to use in the future (but currently would be used for only one thing)
    • Cons:
      • it is more difficult for Julie to set up (but this is a one-time task)
      • collectors would no longer actually declare that a pt is HOBS, so there is concern that we would not find out if a unit changes status in a timely manner


Collector instructions

Work in progress, don't go ahead with these yet!

  • we would make available the new unit entries as per wording in Cognos EPR Report as options for the Boarding Loc dropdown
    • we will keep the old ones around for now - if we removed them there would likely be problems in CCMDB
      • we will leave both old and new active until all are changed

Transition plan

We are planning to do this on admissions start Jan 1, 2022 (2022Q1), so some retrospective entries will be needed.

  • How would that work, practically, when some patients discharged since Jan 1 may have been sent already? Or have they not been? Or do we need to tell collectors to hold off on them? Ttenbergen 14:23, 2022 January 25 (CST)
  • SMW


  • Cargo


  • Categories

Tina's instructions

  • inactivate the old options
    • target date #Change Date
    • confirm no remaining old entries in pre-inpt, previous, service/loc, dispo.
SQL - but this is the wrong one...   

SELECT L_Log.D_ID, s_dispo.location_name, L_Log.RecordStatus, s_dispo.program FROM L_Log INNER JOIN s_dispo ON L_Log.Service_Location = s_dispo.dispo_ID WHERE (((s_dispo.location_name)<>"GRA_Med" And (s_dispo.location_name)<>"GRA_CC") AND ((L_Log.RecordStatus)<>"vetted") AND ((s_dispo.Site)="GRA"));

Data Processor's instructions

  • For Vetted cases, Pagasa has to change the affected ITEM values; this should be done by query, ask Tina for help with the queries if needed

Change Date

Working on implementation date. Ttenbergen 12:56, 2022 January 25 (CST)

Status

  • 2021-04-29 - Julie email confirmed that she doesn't need the specific info listed on these pages since we now get the details in Boarding Loc. Ttenbergen 15:43, 2021 April 29 (CDT)
  • 2021-04-15 Task Meeting decided we should change these to the designations in Cognos.

Related articles

Related articles: