Location metadata storage: Difference between revisions

m Text replacement - "[[Category: " to "[[Category:"
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DJ |
We track locations in many fields; they are drawn from either [[s_tmp table]] [[Boarding Loc]] entries or from [[s_dispo table]]. We are interested in some information about some of these locations, like their [[Level of care hierarchy]] / [[s_level_of_care table]] or how many beds they have.
* These are some notes to discuss at our meeting tomorrow.  [[User:Ttenbergen|Ttenbergen]] 15:55, 2022 February 8 (CST)
}}


We track locations in many fields; they are drawn from either [[s_tmp]] [[Boarding Loc]] entries or from [[s_dispo table]]. We are interested in some information about some of these locations, like their [[Level of care hierarchy]] or how many beds they have.
{{Todo
| who =Tina
| question =  _locationData
* _Dev_CFE linking of s_LocationData table
* _Dev_CCMDB - process to import data from wiki (similar to [[Converting ICD10 between wiki and ccmdb.accdb]])
* set up wiki template for locations
* consider data import for locations so no manual pre-populating of pages
* S_level_of_care needs to be integrated with whatever metadata we set up
* discussed at Task whether we should wait for Shared Health info, will make our own; Shared Health's data is no better than ours, so won't do that.
* [[STB-L2HA]] is another page we will need to include when we deal with this.
| todo_added = 2022-02-09 
| todo_action = 2022-02-09 
}}
 
{{Todo
| who = Tina
| todo_added = 2022-06-22
| todo_action = 2022-06-22
| question = _locationData 
* Discussed at JALT; we need to store this on a per page on wiki level, with multiple start and end dates being possible. Tina needs to create the structure for this and pre-populate. Probably discuss with Julie at the planning stage. [[User:Ttenbergen|Ttenbergen]] 12:04, 2022 June 22 (CDT)
** It needs to be possible to access this as data. [[User:Ttenbergen|Ttenbergen]] 09:58, 2022 June 28 (CDT)
}}


== Flexibility for values changing over time ==
== Flexibility for values changing over time ==
Line 9: Line 28:


== Flexibility for what needs to be collected ==
== Flexibility for what needs to be collected ==
There also might be information we have not even considered yet that we might need to track. So, we would want a flexible infrastructure. One way to do this would be something similar to the  [https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model Entity–attribute–value model] we use for the [[s_tmp table]] that has the following:
There also might be information we have not even considered yet that we might need to track. So, we would want a flexible infrastructure. One way to do this would be something similar to the  [https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model Entity–attribute–value model] we use for the [[s_tmp table]]. See [[s_LocationData table]] for more info.  
* location name (a physical location, so should not change) (the entity)
* Attribute (the place where we would ''name'' the thing we want to describe, e.g. "''bed number''")
* Value (the value for the named attribute, e.g. ''10'' in the case of beds)
* Start_DtTm (when did this entity-value combination become true)
* End_DtTm (when did the entity-value combination stop being true)
** End_DtTm is not needed for complete info, and in fact could become inconsistent, but it will make it easier for the [[Statistician]] to use. Since updates will be rarer than use, the difficulty is worth it
 
{{Todo
| who =Tina
| question =  _Dev_CCMDB 1
* do this high priority
| todo_added = date the question was added - defaults to blank 
| todo_action = date the issue should be brought forward, or is due 
}}


== How and where to keep the master data ==
== How and where to keep the master data ==
Line 33: Line 38:


== Types of data to consider ==
== Types of data to consider ==
* Bed numbers:  
* CC bed numbers are in
** and possibly other things: [[Collection location documentation]] / [[Site and Location table]]
** S:\WRHA\WRHA_CCMED\CCMDB_SAS_by_Julie\SASCFE\CC_data\CCBedMonth.xlsx 
** Bed numbers as in [[STB-L2HA]]
** S:\MED\MED_CCMED\CCMDB_ADMIN_DATABASE\Bed_CountAndDates\CCBedMonth.xlsx
** Julie's excel folder needs to be integrated
* Med numbers are not really tracked; there is an outdated list that was maintained by Trish in
** Also, we need a process to integrate it
** S:\MED\MED_CCMED\CCMDB_ADMIN_DATABASE\Bed_CountAndDates\BedBaseMonthly_Medicine.xlsx
*** complication: if stored in CCMBD, how does Pagasa or Julie get it into Master? Does this data need to live in CCMBD or can it live in ccmdb_data? Do collectors ever need this? Actually, since we want to store master data on wiki we will need to away to import this into the wiki
** S:\MED\MED_CCMED\CCMDB_ADMIN_DATABASE\!BedBase_count_CC_Med
** they get a download from https://whiteboard.manitoba-ehealth.ca/whiteboard/icu  
* possibly other things: [[Collection location documentation]] / [[Site and Location table]]
* [[STB-L2HA]] is an overflow location... do we want to designate those somehow?
* we need a process to import the data from the wiki into ccmdb.accdb
* we need a process to get a download from https://whiteboard.manitoba-ehealth.ca/whiteboard/icu onto wiki when it updates
* HOBS info - [[Change_of_remaining_location_names_from_"our"_names_to_EPR/Cognos_names#How_will_we_code_the_HOBS_status_of_a_unit]]
* HOBS info - [[Change_of_remaining_location_names_from_"our"_names_to_EPR/Cognos_names#How_will_we_code_the_HOBS_status_of_a_unit]]
* Bed numbers as in [[STB-L2HA]]
* [[Level of care hierarchy]] - currently lives in [[s_dispo table]] as "acuity_level" but we need to move it to here because it now needs to apply to [[Boarding Loc]]s
* [[Level of care hierarchy]]
* another possible use would be to store COVID status of a unit
* another possible use would be to store COVID status of a unit


== Related articles ==  
== Related articles ==  
{{Related Articles}}
{{Related Articles}}
[[Category:Location Information]]