Processes around changing a PatientFollow assignment: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m →Process for the collector who will now be collecting the chart number ending: Cleaned out discussions that were either confirmation or special case errors. |
||
| Line 12: | Line 12: | ||
== Process for the collector who will now be collecting the chart number ending == | == Process for the collector who will now be collecting the chart number ending == | ||
* patients with a chart ending now needs to be collected on a different laptop will show up on the [[Cognos2 Service Starter]] of that laptop the next time there is a new service start DtTm after the transition date, ''even if their record was started on a different laptop'' | * patients with a chart ending now needs to be collected on a different laptop will show up on the [[Cognos2 Service Starter]] of that laptop the next time there is a new service start DtTm after the transition date, ''even if their record was started on a different laptop'' | ||
* enter these patients through [[Cognos2 Service Starter]], which will add the [[Visit Admit DtTm field]] of the original entry on the other laptop | * enter these patients through [[Cognos2 Service Starter]], which will add the [[Visit Admit DtTm field]] of the original entry on the other laptop | ||
* only enter the additional unit or service changes that happen after/at admission to your unit, since the ones before will be on the other laptop already | * only enter the additional unit or service changes that happen after/at admission to your unit, since the ones before will be on the other laptop already | ||
* for [[Previous Location]], [[Previous Service]], [[Pre-admit Inpatient Institution]] use what someone from another site/program would use if they received this patient | * for [[Previous Location]], [[Previous Service]], [[Pre-admit Inpatient Institution]] use what someone from another site/program would use if they received this patient | ||
* enter [[Acquired Diagnoses]] and [[Acquired Procedure]]s that happen after the transition dttm | * enter [[Acquired Diagnoses]] and [[Acquired Procedure]]s that happen after the transition dttm | ||
== Cross-threshold records that persist for a long time == | == Cross-threshold records that persist for a long time == | ||
Revision as of 20:47, 2021 January 14
Patients are assigned to collectors using the PatientFollow Project. This page explains what needs to happen when an assignment is changed. The collector/laptop that used to collect a number needs to phase out that number, the collector/laptop who gains that number needs to start them, and we need to be sure that Julie will report on them continuously. We need a process where the time frame for the transition is limited.
Since PatientFollow Project assignments are based on the Service Start DtTm (collected as Service tmp entry), the transition is based on of the Service Start/Change dttms.
Process for the collector who will no longer be collecting the chart number ending
- for patients with a service start DtTm after the transition date, a line will not show up in Cognos2 Service Starter on the laptops that are no longer collecting them (they will show up on the new laptop, see next section)
- If the next service change would lead to a discharge from the affected laptop's, do a regular discharge.
- If the next service change would not lead to a discharge from the affected laptop's (ie would just lead to another Service tmp entry), then discharge the patient to the Dispo location appropriate for their next unit (ie use the Dispo that someone from another site would use if they sent a pt there). This might mean that you are setting Dispo to the same value as Service/Location.
- enter Comorbid Diagnoses, Admit Diagnoses,Acquired Diagnoses and Admit Procedures,Acquired Procedures that happen before the transition dttm
Process for the collector who will now be collecting the chart number ending
- patients with a chart ending now needs to be collected on a different laptop will show up on the Cognos2 Service Starter of that laptop the next time there is a new service start DtTm after the transition date, even if their record was started on a different laptop
- enter these patients through Cognos2 Service Starter, which will add the Visit Admit DtTm field of the original entry on the other laptop
- only enter the additional unit or service changes that happen after/at admission to your unit, since the ones before will be on the other laptop already
- for Previous Location, Previous Service, Pre-admit Inpatient Institution use what someone from another site/program would use if they received this patient
- enter Acquired Diagnoses and Acquired Procedures that happen after the transition dttm
Cross-threshold records that persist for a long time
A change in service will trigger a re-assignment, but a patient could remain on the same service for a long time after a PatientFollow change. If the change was just done for workload re-distribution reasons this may not matter and collection can continue on the original laptop. If the re-assingment was done to wind down a laptop entirely the the remaining records should be discussed with main office on a regular basis to decide if collection should continue on that laptop, or if the record should be moved to the new laptop (ie. manually re-entered there, and deleted from old laptop). This will be a case-by-case decision.
What needs to be changed in CCMDB.mdb every time there are assignment changes
The S PatientFollow distribution table needs to be updated to set an ending time for the earlier laptop. A new line needs to be added for the later laptop, with the same start DtTm as the end DtTm for the earlier one.
Process Julie uses to re-connect the data
If we use the Visit Admit DtTm field to define Hospital stays, and the Boarding Locs and Service tmp entry instead of old Service/Location etc, then e.g. LOS and Bed occupancy would be the same, whether they come from one laptop or several.
|
|
To Do
|
Fix the cross checks so this can work; one way would be to exempt records with a visit admit dttm before follow-ending and a dispo (or now) after a follow-ending; messy query for messy times. |
|
