Swap Locations: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
(49 intermediate revisions by 7 users not shown) | |||
Line 1: | Line 1: | ||
Some sites use swap locations as entries in [[EPR]] | Some sites use swap locations as entries in [[EPR]]. | ||
{{ | When patients need to switch locations, patient swap locations can be performed in the ADT EPR. | ||
* | {{Ex| | ||
* Ex 1: 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. | |||
* Ex 2: A patient was in a swing bed from 0243 until 0405 that is the actual arrival time to the unit. | |||
The patient remained in ER until 0405 but MR staff had to electronically enter/place the patient somewhere. | |||
}} | }} | ||
== The problem == | |||
* | * We need to ensure this is dealt with consistently in the context of [[Using Cognos2 to keep track of patients]] and [[Cognos2 Unit Starter]]. [[CUS]] lists when someone arrives on a '''''unit''''', not in a bed. So, for [[GH-SWAP Location]]s it is immediately visible that pt is there, but for [[SBGH Swing Beds]] it is not. | ||
* Since EPR/Cognos lists these patients as being physically on the unit already (just in a swing bed) and we list them (correctly) as still being in the ER, this could result in discrepancy between our reports and other hospital reports. This can't be fixed, but is good to know if we are ever asked about reasons for discrepancies. | |||
== The solution == | |||
We considered whether there are ways to deal with these in the data/filters/programs, but since the scenarios when and how these would be used aren't entirely predictable it was decided to keep these a manual process. See [[SBGH Swing Beds]] and [[GH-SWAP Location]] for details. | |||
== 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 == | ||
Line 14: | Line 32: | ||
[[Category:Hospital EPR]] | [[Category:Hospital EPR]] | ||
[[Category:Cognos Report Integrator]] | [[Category:Cognos Report Integrator]] | ||
[[Category:Cognos Issue]] |
Latest revision as of 12:17, 2022 January 27
Some sites use swap locations as entries in EPR.
When patients need to switch locations, patient swap locations can be performed in the ADT EPR.
Example: |
The patient remained in ER until 0405 but MR staff had to electronically enter/place the patient somewhere. |
The problem
- We need to ensure this is dealt with consistently in the context of Using Cognos2 to keep track of patients and Cognos2 Unit Starter. CUS lists when someone arrives on a unit, not in a bed. So, for GH-SWAP Locations it is immediately visible that pt is there, but for SBGH Swing Beds it is not.
- Since EPR/Cognos lists these patients as being physically on the unit already (just in a swing bed) and we list them (correctly) as still being in the ER, this could result in discrepancy between our reports and other hospital reports. This can't be fixed, but is good to know if we are ever asked about reasons for discrepancies.
The solution
We considered whether there are ways to deal with these in the data/filters/programs, but since the scenarios when and how these would be used aren't entirely predictable it was decided to keep these a manual process. See SBGH Swing Beds and GH-SWAP Location for details.
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: |