|
- Trish, Julie and Tina discussed 2020-10-08, we will roll this out shortly but wait until Trish gives go-ahead before you change practices. Please comment inline if you see problems, or clarify things if I could have written them up better. Ttenbergen 22:05, 2020 October 8 (CDT)
|
Collection instructions
Identifying EMIPs for laptops using location based identification of pts
- same person/laptop as before will collect these
- find them as you have in the past
Entering an EMIP
- Service/Location: based on which Service covers the patient, use that service's main unit as the Service/Location
- Boarding Loc: for any pt from ER enter your site's ER as the first Boarding Loc entry; in case of an EMIP it will be the only entry; for other pts it will simply be the first entry before other Boarding Loc entries
- use the time of acceptance to service as Boarding Loc date and time (yes, that makes it the same as the Accept DtTm - we may address that duplication later once we are comfortable that this change has settled in
- this means that if the patient is later moved to a unit we collect (ie turns out to not be an EMIP after all), you can just enter that next location as an additional Boarding Loc entry, with that one having the same Boarding Loc Dt Tm as our Arrive DtTm
|
|
For those that do move to a unit where we collect can we not just take out all the tmp boarding entries and just treat it as a regular admission? i.e. have an accept and arrive time to the home unit location, is there a reason why we need all the tmp boarding entries in these cases? Lisa Kaita 07:40, 2020 October 9 (CDT)
|
Background
We encode EMIPs as a Service/Location for legacy reasons - it is not really a location as much as a special case. Under our current infrastructure we would more likely encode these as a special case of Boarding Loc. Now that we are moving to a PatientFollow model where patient load is split by chart number, we are running into patients in ER where we are not yet sure if they will end up EMIPs or ward patients. Leaving Service/Location blank is not allowed, so we either need to delay entering or come up with a new solution. We decided this was a good trigger to finally make encoding them like other Boarding Locs.
Cleanup and integration still required
|
Will need to reconcile the following:
|
Related articles