Swap Locations: Difference between revisions
No edit summary |
|||
Line 11: | Line 11: | ||
Swing or swap locations are not real locations. While listed as in a swap location, the pt might still be in the old location or already be in a new location that gets entered after. Collectors seem to review the chart, make sense of what actually happened, and enter accordingly. If we engage in this manual sense-making, we can not use not use the [[Cognos EPR Report]] tools cleanly so would need to define how we deal with these patients. | Swing or swap locations are not real locations. While listed as in a swap location, the pt might still be in the old location or already be in a new location that gets entered after. Collectors seem to review the chart, make sense of what actually happened, and enter accordingly. If we engage in this manual sense-making, we can not use not use the [[Cognos EPR Report]] tools cleanly so would need to define how we deal with these patients. | ||
* Swing/swap bed location entries are an example of entries that can occur at STB site when a patient is temporarily located into a bed in epr for logistical purposes. Whenever a collector encounters this erroneous entry, the best consistent approach is to do an EPR/documentation review to reconcile potential discrepancies. The applicable cognos line(s) can then excluded. Perhaps the discussion below could be either deleted or made legacy? | * Swing/swap bed location entries are an example of entries that can occur at STB site when a patient is temporarily located into a bed in epr for logistical purposes. Whenever a collector encounters this erroneous entry, the best consistent approach is to do an EPR/documentation review to reconcile potential discrepancies. The applicable cognos line(s) can then be excluded. Perhaps the discussion below could be either deleted or made legacy? | ||
=== Proposed consistent approach === | === Proposed consistent approach === |
Revision as of 07:11, 21 January 2022
Some sites use swap locations as entries in EPR.
When patients need to switch locations due to medical reasons, patient swap locations can be performed in the ADT EPR. For example, patient A and patient B need to switch locations. Patient A is in a private room and patient B is in a semi-private room. Both patients could be transferred into the swap location or non-census location, freeing up both of the unit beds. Then both Patient A and Patient B can be transferred into the correct unit and room/bed.
Example: |
The problem
Swing or swap locations are not real locations. While listed as in a swap location, the pt might still be in the old location or already be in a new location that gets entered after. Collectors seem to review the chart, make sense of what actually happened, and enter accordingly. If we engage in this manual sense-making, we can not use not use the Cognos EPR Report tools cleanly so would need to define how we deal with these patients.
- Swing/swap bed location entries are an example of entries that can occur at STB site when a patient is temporarily located into a bed in epr for logistical purposes. Whenever a collector encounters this erroneous entry, the best consistent approach is to do an EPR/documentation review to reconcile potential discrepancies. The applicable cognos line(s) can then be excluded. Perhaps the discussion below could be either deleted or made legacy?
Proposed consistent approach
![]() |
|
Current state
<quote>...because cognos Is often using the swing bed as a legitimate date and time, we are getting incorrect information. I find that more often than not (not necessarily every single time), the swing bed entry is usually when the patient is still physically located in er, and has not yet, actually physically been moved up to the ward. The er needs to use that location to admit another patient. Therefore, they will put a “swing bed” entry in. because the swing bed entry is listed right after the er entry, cognos picks that up, and uses that as the admit to unit start date and time. This date and time, is, in actual fact wrong. The actual ward unit start time, is the next entry in the location history that does not have the swing bed tag as the location. (Debbie)</quote> Clarifications:
- The entry is not picked up by Cognos "because the swing bed entry is listed right after the er entry", it is picked up because it is a unit entry during the timeframe of a service admission.
- The swing bed is associated with whichever location it is a swing bed for. So, if the ER uses a ward swing bed, then maybe the real problem is that they should be using an ER swing bed? If they did, the pt would be correctly still listed as an ER
- Not necessarily, swing bed usage is not specific to ER only, and occasionally ambiguous specific locations (ie. a location unit that the patient does not physically go to) for swing bed entries are all picked up by cognos resulting in false positives (exclusion patients) to show up on cognos.
![]() |
|
![]() |
|
![]() |
|
![]() |
|
The use of swap or swing locations makes it hard to follow patients in Cognos Report Integrator, so we need to find out more about how these are used.
Swing beds in Cognos2 Unit Starter
CUS lists when someone arrives on a unit, not in a bed.
So GH-SWAP Locations are shown and SBGH Swing Beds are not.
possible solution: exclude by filter
![]() |
One problem with filtering these out would be that, I think, the unit record for a swap location might be the same as the unit record for a successive stay in that unit; ie. the bed entry chagnes, but the unit remains the same. So, the unit start dttm and unit end dttm don't care if part of the unit stay was in a swap location. Is that not true? If it is true, then how would we filter these out? if I eliminate every line that has a swap/swing bed (which I can do) then we will not get any line for those pts who never get into a real bed on that unit (which may be good), but we would still get the same line with unit start and end times including the swap/swing time for patients who eventually get into a bed on that unit. Ttenbergen 12:07, 2020 December 2 (CST) |
For these reasons all swing bed entries should be filtered out if possible.
possible solution: exclude by manual exclude
This will not exclude the record from Cognos2 Ender since that is based on service rather than unit.
Location specific info
"Swing beds" at STB
See SBGH Swing Beds
"Swap locations" at GRA
See GH-SWAP Location
HSC
According to Chastity there is no such thing at HSC.
Except, on 2021-02-12 we saw a unit "HSC-HOLD", and it wasn't clear what that was about.
Related articles
Related articles: |