Multiple Encounter: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
JMojica (talk | contribs)
CCMDB_legit, admin, approved, Administrators
2,815 edits
m Text replacement - "[[Category: " to "[[Category:"
 
(19 intermediate revisions by the same user not shown)
Line 1: Line 1:
Patients may show up in our database repeatedly either during the same hospital stay or at a later time. If they show up at a later time, but soon after the last hospital stay, they may qualify as "readmission", which we report monthly, quarterly and annually.
Patients may show up in our database repeatedly. Our [[L_Log]] records are patient-ward-stay based. Once the [[data processor]] completes the [[centralized data Vetting Process]] (i.e. [[PHIN field|PHINs]] are checked and PseudoPHINs are generated) the PHIN field can be used for linking L_Log records for the same patient. This combining data is stored in [[L Person table]] by [[Encounter processing]].


== Multiple Encounters ==
If a patient is never discharged in between L_Log entries it may be a '''[[Continuous Stay]]'''.  
* Multiple encounters are considered of same patient if the combination of following fields match:
** PHIN
** Names (First and Last)
** DOB
** Gender
** Hospital Chart# if admitted in the same hospital
* Data quality check programs are being run after every appending of new data to the master database of both Critical Care and Medicine.  The programs find errors in  records not matching in any of the above combination of fields.
** The Data Processor runs the two  programs at her local computer C:\TMSX\CombLookupProof.exe followed by C:\TMSX\CombinedErrorsFinder.exe in that order.
** The Statistician runs the SAS program in the shared folder  X:\Julie\SAS\CriticalCare\chkchartdupCCnMED.sas .
** The Data Processor fixes any errors found ensuring the consistencies in the demographics of same patient on both databases.


== Continuous Hospital Stay - Medicine ==
If a patient is discharged and then admitted again at a later time, but soon after the last hospital stay, they may qualify as '''[[Readmission]]'''.  
The [[statistician]] uses data from [[Admit From & Discharged To]], [[Med Var 1 - Admit-from Ward]] and [[Med Var 2 - Discharge-to Ward]] to
* link profiles from one ward to another when both wards are within the database program
** {{discussion}} what do you mean "when both wards are within the database program" - would we have data if they were not?Ttenbergen 18:07, 2012 November 22 (EST)
* detect a likely continuous stay when a pt is discharged from one of our wards to a non-collected ward and then re-admitted to one of our wards from the same non-collected ward.  


== Readmissions ==
== Multiple encounter longitudinal consistency checks ==
For our purposes, readmissions are admissions of patients who were recorded by our database recently.  
For patients encountered repeatedly some data should be consistent between stays.  


=== ICU Definition ===
The [[data processor]] runs a set of checks during vetting that attempts to find and make consistent the records for patients encountered previously.
For ICU, a readmission is a patient where
* (admit date/time) - (most recent ICU discharge date/time to ward or home) <= 72 hours
* is '''not''' admitted for planned and scheduled surgery
* might be readmitted from Ward or outside hospital
** is there anywhere pt would not be allowed to be admitted from? Ttenbergen 18:07, 2012 November 22 (EST) {{discussion}}
 
=== Medicine Definition ===
For medicine, a readmission is a patient where
* (admit date/time) - (most recent discharge date/time to the hospital) <= 7 days after their most recent discharge time to the hospital
* is admitted from outside hospital
* ''(Legacy: planned surgery used to be excluded, but this stopped because of insufficient data when we stopped collecting some APACHE elements in the medicine program Dec 31, 2006)''


{{Data Integrity Check List}}


== Related Articles ==
{{Related Articles}}


[[Category:Statistical Analysis]]
[[Category:Statistical Analysis]]
[[Category:Questions Statistician]]
[[Category:Multiple Encounter | * ]]
[[Category: Multi-encounter check | *]]

Latest revision as of 10:56, 30 July 2025

Patients may show up in our database repeatedly. Our L_Log records are patient-ward-stay based. Once the data processor completes the centralized data Vetting Process (i.e. PHINs are checked and PseudoPHINs are generated) the PHIN field can be used for linking L_Log records for the same patient. This combining data is stored in L Person table by Encounter processing.

If a patient is never discharged in between L_Log entries it may be a Continuous Stay.

If a patient is discharged and then admitted again at a later time, but soon after the last hospital stay, they may qualify as Readmission.

Multiple encounter longitudinal consistency checks

For patients encountered repeatedly some data should be consistent between stays.

The data processor runs a set of checks during vetting that attempts to find and make consistent the records for patients encountered previously.

Data Integrity Checks (automatic list)

 AppStatus
Check VAP acquired only first encounterCentralized data front end.accdbdeclined

Related Articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Multiple_Encounter&oldid=166620"