PatientFollow Project: Difference between revisions
TOstryzniuk (talk | contribs) |
Ttenbergen (talk | contribs) |
||
| (26 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
This page describes how collection of incoming patients is split across data collectors | |||
== Identifying admissions / Starting collection == | |||
Patients are assigned to laptops by the last two digits of their [[Chart number]]. [[Cognos2 Service Starter]] automatically filter them, just follow [[Using Cognos2 to keep track of patients]]. Special considerations apply to [[John or Jane Doe patient#PatientFollow Project considerations|John or Jane Doe patient]]s. | |||
== | == Entering into the laptop == | ||
The initial ward would need to be entered as usual. For stays on subsequent wards, [[Cognos2 Service Starter]] and [[Patient Viewer Tab Cognos ADT2]] can be used to create another line in the [[Boarding Loc]] and [[Service tmp entry]]. | |||
Data would go into one profile unless a patient leaves the service. For example, if a pt starts in medicine, then goes to ICU, and then comes back to medicine, then coming back to medicine would mean starting a new profile. | |||
=== | == Fallback process when Cognos data is unavailable == | ||
See [[Cognos downtime procedure]] | |||
== Medical Records requests == | |||
Shelf split based on [[Laptop identifier]], see [[HSC Medical Records requests]] for details. | Shelf split based on [[Laptop identifier]], see [[HSC Medical Records requests]] for details. | ||
== Actual chart number split per site and per laptop == | == Actual chart number split per site and per laptop == | ||
The split is automatically reflected in [[ | The split is automatically reflected in [[Cognos2 Service Starter]], no additional filtering needed. The corresponding data is stored in [[S PatientFollow distribution table]]. | ||
=== Viewing the numbers assigned to a given laptop === | === Viewing the numbers assigned to a given laptop === | ||
The assignment is a matter of laptop, chart number ending and the date at which point a specific distribution started. We don't want to store it here on the wiki because it is kind of messy and hard to keep updated. Use [["Show PatientFollow allocation" button]] to see which numbers are assigned to the laptop you are working on during which timeframe. | The assignment is a matter of laptop, chart number ending and the date at which point a specific distribution started. We don't want to store it here on the wiki because it is kind of messy and hard to keep updated. Use [["Show PatientFollow allocation" button]] to see which numbers are assigned to the laptop you are working on during which timeframe. | ||
== | === Assignment changes === | ||
See [[Processes around changing a PatientFollow assignment]] | |||
== | === Exception: HSC_IICU === | ||
See [[HSC_IICU_Collection_Guide#Workload_Sharing_for_HSC_IICU]] | |||
== Follow between medicine/critical care or just within one program == | == Follow between medicine/critical care or just within one program == | ||
Initially we were just following patients within the same program, but later we moved on to [[Change to having each collector collect both programs on the same laptop]]. | |||
== old process and questions that were addressed == | |||
{{Collapsable | {{Collapsable | ||
| always= old process and questions that were addressed | | always= old process and questions that were addressed | ||
| full= | | full= | ||
=== Old Process === | |||
Our database used to collect patient ward stays, which meant the data of a patient could be processed by several collectors during the admission. This lead to extra, wasted work of different collectors familiarizing themselves with the same patient. {{PAGENAME}} was set up to change to a system where one collector keeps following a patient. | |||
Currently patients are assigned to collectors/laptops based on where they are admitted. To change to the new system, we would need to identify patients who enter a given site and then assign them to the collector pool equitably. We are planning on a process based on the last two digits of the chart number. | |||
=== If we split by chart number, how do we ensure no pts are missed or duplicated? === | |||
* '''duplication''' - there could only be duplication if you enter a chart number that is someone else's; your [[Cognos2 Service Starter]] will only show your patients, so you would not duplicate someone else's, and any risk of duplicating your own is no higher than it was with the old process. | |||
* '''missing a patient''' - we have been testing the [[Cognos EPR Report]] to make sure patients are not missed from it; for PatientFollow we will simply filter that list, so if all patients were on it, they should still all be on the split list | |||
** main office can run a check between Cognos Data and our data for the first few weeks to make sure all Cognos data is also in our data | |||
=== Would the LOS have any impact on this sharing plan? === | === Would the LOS have any impact on this sharing plan? === | ||
{{Collapsable | {{Collapsable | ||
| Line 54: | Line 58: | ||
| always= The last two digits of chart numbers are evenly distributed and can be used for this. | | always= The last two digits of chart numbers are evenly distributed and can be used for this. | ||
| full= * Tina has taken a basic look at the distribution of these numbers and emailed Julie and Trish for feedback. Ttenbergen 17:31, 2019 August 1 (CDT) | | full= * Tina has taken a basic look at the distribution of these numbers and emailed Julie and Trish for feedback. Ttenbergen 17:31, 2019 August 1 (CDT) | ||
** Julie did additional analysis by looking at the distribution of the '''last two digits''' numbers from last 5 years 2014 to 2018 as follows: 1) all sites together, 2) each site separately 3) each year from all sites separately and 4) each site and year - the distributions showed similarity with few peaks in some numbers. She grouped the last two digits numbers into a) 10 subgroups (e.g. 0-9,10-19,20-29, …, 90-99 ) and b) 20 subgroups (e.g. 0-4, 5-9, 10-14, 15-19, …, 95-99) and their distributions showed uniformly across subgroups. Each of the 10 subgroups showed counts close to 10% while each of the 20 subgroups showed counts close to 5%. The histograms are in '' | ** Julie did additional analysis by looking at the distribution of the '''last two digits''' numbers from last 5 years 2014 to 2018 as follows: 1) all sites together, 2) each site separately 3) each year from all sites separately and 4) each site and year - the distributions showed similarity with few peaks in some numbers. She grouped the last two digits numbers into a) 10 subgroups (e.g. 0-9,10-19,20-29, …, 90-99 ) and b) 20 subgroups (e.g. 0-4, 5-9, 10-14, 15-19, …, 95-99) and their distributions showed uniformly across subgroups. Each of the 10 subgroups showed counts close to 10% while each of the 20 subgroups showed counts close to 5%. The histograms are in ''{{S:\MED\MED_CCMED}}CCMDB_Special_Projects\Project_PatientFollow_ChartNumberDistribution''. The results support the viability of using the last two digits of the chart number in allocating patients among the data collectors. Additional analysis info is in S:\MED\MED_CCMED\ChartLastDigitAnalysis\NormalizedCounts_Comparison\2_Paired T-Test and Data.xlsx | ||
*** Additional analyses were done separately for Medicine and Critical Program for each site and 1) each year, 2) each quarter and 3 )each month to determine any seasonal variation across time. The distributions are generally uniform across subgroups with relatively few peaks. However, there seems to be some seasonal variation which is observed more in Critical Care than Medicine Program. The histograms are also in in '' | *** Additional analyses were done separately for Medicine and Critical Program for each site and 1) each year, 2) each quarter and 3 )each month to determine any seasonal variation across time. The distributions are generally uniform across subgroups with relatively few peaks. However, there seems to be some seasonal variation which is observed more in Critical Care than Medicine Program. The histograms are also in in ''{{S:\MED\MED_CCMED}}CCMDB_Special_Projects\Project_PatientFollow_ChartNumberDistribution''. | ||
** Julie also did the distribution of the '''first two digits''' numbers and found out that the distribution was skewed to the right. Therefore, this cannot be used as a tool for allocating patients. The distribution is in '' | ** Julie also did the distribution of the '''first two digits''' numbers and found out that the distribution was skewed to the right. Therefore, this cannot be used as a tool for allocating patients. The distribution is in ''{{S:\MED\MED_CCMED}}CCMDB_Special_Projects\Project_PatientFollow_ChartNumberDistribution'' . | ||
* I think this is a good starting strategy to allocate patients among the data collectors proportionately in each site.}} | * I think this is a good starting strategy to allocate patients among the data collectors proportionately in each site.}} | ||
| Line 79: | Line 83: | ||
*It should be questioned then whether amalgamating all data collection units within a site for example there are 4 medicine collection units at STB + EMIPs how to possibly track and reconcile all these lists with any semblance of accuracy. This would be a very labor/time intensive and complicated process, as well as a significant logistical challenge. Use of EPR lists to create further lists/spreadsheets in Excel seems redundant and a risky proposition in terms of inclusion and accuracy. There are also potential PHIA considerations whereas patient information on laptops is currently stored/accessed through a separate program, what are the implications for "personal" and/or redundant storage of patient information on data collector accounts? [[User:Ppiche|Pamela Piche]] 10:19, 2019 September 5 (CDT) | *It should be questioned then whether amalgamating all data collection units within a site for example there are 4 medicine collection units at STB + EMIPs how to possibly track and reconcile all these lists with any semblance of accuracy. This would be a very labor/time intensive and complicated process, as well as a significant logistical challenge. Use of EPR lists to create further lists/spreadsheets in Excel seems redundant and a risky proposition in terms of inclusion and accuracy. There are also potential PHIA considerations whereas patient information on laptops is currently stored/accessed through a separate program, what are the implications for "personal" and/or redundant storage of patient information on data collector accounts? [[User:Ppiche|Pamela Piche]] 10:19, 2019 September 5 (CDT) | ||
** There would be no extra lists, the allocation would happen automatically within Cognos, so the processes you guys have now would just go away, you would simply enter the | ** There would be no extra lists, the allocation would happen automatically within Cognos, so the processes you guys have now would just go away, you would simply enter the patient that show up on your [[CSS]], and you wouldn't even see the ones that are not yours. RE concerns about patients that may be missing from Cognos, that is a separate issue: if pts are missing from Cognos, and still don't show up on the 2nd day after their admission, you need to tell me so we can troubleshoot that. If those are addressed then this should no longer be relevant to patientFollow. If this answers the concerns, please remove this discussion. If not, please elaborate. Ttenbergen 21:41, 2020 October 15 (CDT) | ||
}} | |||
== Background == | == Background == | ||
| Line 86: | Line 91: | ||
=== Transition dates === | === Transition dates === | ||
Since this demarcation comes up repeatedly, use [[query created_PatientFollow]] so this is done consistently. | |||
{{Collapsable | |||
| always= Transition dates | |||
| full= | |||
Patient Follow one record one episode model | Patient Follow one record one episode model | ||
====GRA==== | ====GRA==== | ||
GRA Med & GRA_CC | GRA Med & GRA_CC | ||
*patient allocation by Chart last two digits starting 2020-Oct-01; All patients who have an | *patient allocation by Chart last two digits starting 2020-Oct-01; All patients who have an ''Accept DtTm'' or [[Dispo DtTm field | Dispo DtTm]] ON or AFTER 2020-Oct_1, the collector will apply the patient follow model | ||
====HSC==== | ====HSC==== | ||
HSC Med | HSC Med & HSC CC (MICU) (SICU) | ||
*(Excludes HSC IICU) | *(Excludes HSC IICU) | ||
**All patients who have an | **All patients who have an ''Accept DtTm'' or [[Dispo DtTm field | Dispo DtTm]] ON or AFTER '''2020-Oct-15''' the collector will apply the patient follow model | ||
** In the Task meeting '''Nov 30,2021''', it was decided that HSC CC has to go back to the old system, continuous admissions at HSC MICU and HSC SICU had been changed and made into 2 separate records onwards. From '''2020-Oct-15''', there were only 11 vetted records having such case and they were un-winded. | |||
====STB==== | ====STB==== | ||
STB Med | STB Med | ||
*All patients who have a | *All patients who have a ''Accept DtTm'' or [[Dispo DtTm field | Dispo DtTm]] ON or AFTER '''2020-Oct-15''', the collector will apply the patient follow model | ||
STB ICU's | STB ICU's | ||
* S7-STB MICU & S9-STB ACCU >= '''2020-10-15''' | * S7-STB MICU & S9-STB ACCU >= '''2020-10-15''' | ||
* S8-STB_CICU - Stephanie Cortilet: since Steph pre-enters, start with Patients with | * S8-STB_CICU - Stephanie Cortilet: since Steph pre-enters, start with Patients with ''Accept DtTm'' >= 2020-10-16 | ||
** [[STB_CC#Decision to not combine collection of STB CC on one laptop]] but the [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] still apply | ** [[STB_CC#Decision to not combine collection of STB CC on one laptop]] but some of the [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] still apply. | ||
}} | |||
== Related articles == | == Related articles == | ||
| Line 108: | Line 121: | ||
[[Category:PatientFollow Project| *]] | [[Category:PatientFollow Project| *]] | ||
[[Category:Change explainer page]] | |||