2020-10 EMIP changes: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
| Line 6: | Line 6: | ||
* same person/laptop as before will collect these | * same person/laptop as before will collect these | ||
* find them as you have in the past | * find them as you have in the past | ||
{{Todo |who = Tina || todo_action = 2021-01-15 | | {{Todo |who = Tina || todo_action = 2021-01-15 | question = | ||
This will eventually need to come out, probably in January or so when even the last of these has been entered. }} | This will eventually need to come out, probably in January or so when even the last of these has been entered. }} | ||
Revision as of 15:09, 2020 November 26
Collection instructions
Identifying EMIPs for laptops using PatientFollow model
They don't need to be separately identified, they are simply a patient who started on one of our services and is therefore listed on Cognos2 Service Starter.
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
|
This will eventually need to come out, probably in January or so when even the last of these has been entered. |
|
Entering an EMIP
- Service/Location: enter based on Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry
- 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
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
| Related articles: |