Service/Location field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
TOstryzniuk (talk | contribs)
CCMDB_legit, approved, Bureaucrats, Administrators
27,522 edits
m Service Location - just call field Location - reduce confusion
mNo edit summary
 
(70 intermediate revisions by 9 users not shown)
Line 1: Line 1:
''This field is currently being implemented, please check the instructions and put a discussion for anything that isn't clear. ''
{{Data_element
| field_name = Service_Location
| CCMDB_label = Service Location
| CCMDB_tab = Dispo
| element_description = Legacy field replaced by [[Boarding Loc]] and [[Service tmp entry]]
| in_table = L_Log table
| data_type = number
| datafield_length = long integer
| program_collecting = Med and CC
| created_raw = Raw
| data_element_start_date = 2016-07-01
| data_element_sort_index = 40
}}


Collection location a patient is admitted to, very similar to current "Location" field. This will be a dropdown that allows an appropriate subset of the contents of s_dispo.
The field was changed as part of  [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]].
{{Discussion}}
{{DL| LKTT
*why is the field call SERVICE LOCATION rather than LOCATION.  adds to the confusion. Is there a point to include addition word Service to location.  There really is not such thing as a Service Location.
* Now that we have decided to leave this as separate wiki pages, should we remove the above line? [[User:Lkaita|Lisa Kaita]] 06:45, 2024 April 11 (CDT)
**Suggestion, just call the field LOCATION as it was called before. Less confusion.
** How about this. But we still have a problem: what do we put into the element_description for this in the template call? That's kind of important since it drives the auto data dictionary. [[User:Ttenbergen|Ttenbergen]] 17:22, 2024 April 11 (CDT)
** need to chat about this T [[User:Lkaita|Lisa Kaita]] 14:38, 2024 October 2 (CDT)
*** Do you want to book a time for that conversation? I usually work HSC Wed and Thu. Also, to easily add things to "our" list, I added an LKTT which would allow filtering [[Questions]] for these. [[User:Ttenbergen|Ttenbergen]] 12:48, 2024 October 3 (CDT)}}


Patients boarding on other wards or units are coded as the home unit. Collectors can use "record" field for tracking actual location.
*'''This does not apply to [[STB_MICU]], [[STB_CICU]], [[STB_ACCU]] or [[HSC MICU]], [[HSC SICU]], [[HSC_IICU]]'''. Service Location field will not change.  


== Collection Instruction ==
== Collection Instruction ==
essentially like [[Location]] is done now
''see [[Change_from_Service_Location_to_Service,_Boarding_Loc_and_Transfer_Ready_DtTm_tmp_entry#The_change]] for how to code during the transition to the new scheme


If you know the location exactly, you can type it. Otherwise press the "magic wand" button to take you to the [[S dispo chooser‎]] to help filter options if desired.
When entering from [[CSS]] or [["Add Patient with Serial Helper" button]], or in [[Patient Viewer Tab Dispo]], under {{PAGENAME}} select the generic site/program entry:
* [[GRA_Med]], [[HSC_Med]], [[STB_Med]] for medicine
* [[GRA_CC]], [[HSC_MICU]], [[HSC_SICU]], [[HSC_IICU]], [[HSC_IICU]], [[STB_MICU]], [[STB_ACCU]], [[STB_ICCS]] for critical care (see [[STB_CC#Decision to not combine collection of STB CC on one laptop]])
 
==Bed Borrow==
* When a service borrows a bed in another unit/ward but still follows them the [[Service Location]] should be the location where the patient would have been had there been enough beds/space for them.  example.  ACCU patient, followed by ACCU service but physically located in CICU, service location=ACCU. The [[Boarding Loc]] in the Tmp will identify that they are "borrowing" a bed in CICU.  If this patient is then transferred to their normal unit, ACCU, add this location as a [[Boarding Loc]] in the tmp, this would be a single profile.  If the patient was NOT followed by ACCU but by CICU, see [[ICUotherService]] for instructions on how to collect.
* second example- HSC MICU often overflows or borrows a bed in SICU, but MICU follows them, the [[Service/Location]] would be HSC MICU, the [[Boarding Loc]] would reflect the real physical location HSC SICU, and the [[Service tmp entry]] should be HSC Critical Care Medicine.  If the patient is later transferred to HSC MICU, this location would be added as a [[Boarding Loc]], this would remain a single profile.  However, iF the Service changes to an SICU service and they take over care, then a new profile would be started showing the new [[Service Location]] and the new [[Service tmp entry]] and [[Boarding Loc]]
 
The concepts that used to be stored in this are essentially now stored as:
* [[Service tmp entry]] for the service
* [[Boarding Loc]] for the physical location
 
{{Location dropdown cleanup}}
 
{{Guideline Minimal Data Set}}
 
== Adding a new service/location entry ==
* add to ''[[s_dispo table]]''
* consider all checks in [[:Category:Service/Location check]] to see if they need to be modified to work right for the new location.


== Data Use / Purpose ==
== Data Use / Purpose ==
To be filled in
See [[Site and Location table]] for possible entries.
 
Used to determine the location or services the patient went during a hospital stay.


== {{CCMDB Data Integrity Checks}} ==
Used to categorize/stratify the distribution of patients across hospitals and wards/units when reporting summary statistics.
To be filled in


== Reports ==
== Integrity checks ==
To be filled in
{{Data Integrity Check List}}


== Implementation ==
== Implementation ==
The field is populated with options from the [[s_dispo table]].
The field is populated with options from the [[s_dispo table]].
=== Retiring an available Service/Location field entry ===
<!-- linked to heading from [S locations allowed collection table#Removing entries] -->
Sometimes a ward may close or change names, or we may stop collecting somewhere. In that case, an entry for [[Service/Location]] needs to be made unavailable by editing the  [[s_locations_allowed_collection table]].
'''If a location is no longer available on a laptop records with that location can't be set to "complete".''' So, if we transition from one location to a new one, we need to get collectors to change the locations for all existing records to the new one, and change the number to using the new number series.
Another option might be to keep old location available, at risk of manual mistakes and continuing to use the old location, and of location-number Pool mix-ups. Either way, '''needs to be planned'''.


== Legacy ==
== Legacy ==
This field is part of the [[2016 Time and Place changes]] and corresponds to to the old [[Location]] field
This field is subject to [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]]. However, we still need it because of how we decided to collect patients at HSC and STB CC.
 
This field is part of the [[2016 Time and Place changes]] and corresponds to to the old Location field, resp L_Log.R_Location.
 
== Related articles ==
{{Related Articles}}


[[Category: 2016 Time and Place changes]]
[[Category: 2016 Time and Place changes]]
[[Category: Admit/Discharge]]
[[Category: Registry Data]]
[[Category: Data Collection Guide]]

Latest revision as of 11:48, 2024 October 3

Data Element (edit)
Field Name: Service_Location
CCMDB Label: Service Location
CCMDB tab: Dispo
Table: L_Log table
Data type: number
Length: long integer
Program: Med and CC
Created/Raw: Raw
Start Date: 2016-07-01
End Date: 2300-01-01
Sort Index: 40

Legacy field replaced by Boarding Loc and Service tmp entry

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


The field was changed as part of Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry.

LKTT

  • Now that we have decided to leave this as separate wiki pages, should we remove the above line? Lisa Kaita 06:45, 2024 April 11 (CDT)
    • How about this. But we still have a problem: what do we put into the element_description for this in the template call? That's kind of important since it drives the auto data dictionary. Ttenbergen 17:22, 2024 April 11 (CDT)
    • need to chat about this T Lisa Kaita 14:38, 2024 October 2 (CDT)
      • Do you want to book a time for that conversation? I usually work HSC Wed and Thu. Also, to easily add things to "our" list, I added an LKTT which would allow filtering Questions for these. Ttenbergen 12:48, 2024 October 3 (CDT)
  • SMW


  • Cargo


  • Categories

Collection Instruction

see Change_from_Service_Location_to_Service,_Boarding_Loc_and_Transfer_Ready_DtTm_tmp_entry#The_change for how to code during the transition to the new scheme

When entering from CSS or "Add Patient with Serial Helper" button, or in Patient Viewer Tab Dispo, under Service/Location field select the generic site/program entry:

Bed Borrow

  • When a service borrows a bed in another unit/ward but still follows them the Service Location should be the location where the patient would have been had there been enough beds/space for them. example. ACCU patient, followed by ACCU service but physically located in CICU, service location=ACCU. The Boarding Loc in the Tmp will identify that they are "borrowing" a bed in CICU. If this patient is then transferred to their normal unit, ACCU, add this location as a Boarding Loc in the tmp, this would be a single profile. If the patient was NOT followed by ACCU but by CICU, see ICUotherService for instructions on how to collect.
  • second example- HSC MICU often overflows or borrows a bed in SICU, but MICU follows them, the Service/Location would be HSC MICU, the Boarding Loc would reflect the real physical location HSC SICU, and the Service tmp entry should be HSC Critical Care Medicine. If the patient is later transferred to HSC MICU, this location would be added as a Boarding Loc, this would remain a single profile. However, iF the Service changes to an SICU service and they take over care, then a new profile would be started showing the new Service Location and the new Service tmp entry and Boarding Loc

The concepts that used to be stored in this are essentially now stored as:

"Can we remove the items that are no longer Service/Locations, Previous Locations, Pre-admit Inpatient Institutions or dispo locations from the dropdowns?"

We can and will remove them, but that can only happen once no more laptops use them. We will need to keep track of this and then remove them when ready. If I removed them now, then any box that currently has them enter would misbehave.

query of what is currently available

SQL    
SELECT s_dispo.location_name, s_dispo.Site, s_dispo.active, s_dispo.inpatient, s_dispo.previous_location, s_dispo.s_location, s_dispo.dispo
FROM s_dispo
WHERE (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.inpatient)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.previous_location)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.s_location)=True)) OR (((s_dispo.Site)>"") AND ((s_dispo.active)=True) AND ((s_dispo.dispo)=True));

Query of what is currently used

query z_s_dispo_inactivatable

Minimal Data Set

This entry is part of the Minimal Data Set. Special collection instructions apply, see that page for more info.

Adding a new service/location entry

Data Use / Purpose

See Site and Location table for possible entries.

Used to determine the location or services the patient went during a hospital stay.

Used to categorize/stratify the distribution of patients across hospitals and wards/units when reporting summary statistics.

Integrity checks

Data Integrity Checks (automatic list)

 AppStatus
Query check minimal data set incompleteCCMDB.accdbimplemented
Check function location NE dispoCCMDB.accdbimplemented
Check function previous NE LocationCCMDB.accdbimplemented
Check function preAdmit NE LocationCCMDB.accdbimplemented
Query s tmp ABO TEE checksCCMDB.accdbimplemented
Query send check centralized is ownerCCMDB.accdbimplemented
Query s tmp EuroSCORE II checksCCMDB.accdbimplemented
Query s tmp Boarding Loc no borrow but entryCCMDB.accdbretired
PL SameCHART Site Diff PHINCentralized data front end.accdbimplemented
Link suspect mismatch pre inpt ours incomplete queryCentralized data front end.accdbimplemented
Link suspect not same visitAdmitDtTm queryCentralized data front end.accdbimplemented
Reconnect check orphans queryCentralized data front end.accdbimplemented

Implementation

The field is populated with options from the s_dispo table.

Retiring an available Service/Location field entry

Sometimes a ward may close or change names, or we may stop collecting somewhere. In that case, an entry for Service/Location needs to be made unavailable by editing the s_locations_allowed_collection table.

If a location is no longer available on a laptop records with that location can't be set to "complete". So, if we transition from one location to a new one, we need to get collectors to change the locations for all existing records to the new one, and change the number to using the new number series. Another option might be to keep old location available, at risk of manual mistakes and continuing to use the old location, and of location-number Pool mix-ups. Either way, needs to be planned.

Legacy

This field is subject to Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry. However, we still need it because of how we decided to collect patients at HSC and STB CC.

This field is part of the 2016 Time and Place changes and corresponds to to the old Location field, resp L_Log.R_Location.

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Service/Location_field&oldid=161824"