Multiple Encounter: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) m Text replacement - "Re-admission" to "Readmission" |
||
| (28 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Patients may show up in our database repeatedly | 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]]. | ||
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 | 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 Check List}} | |||
== Related Articles == | |||
{{Related Articles}} | |||
[[Category: Statistical Analysis]] | |||
[[Category:Statistical Analysis]] | [[Category: Multiple Encounter | * ]] | ||
Latest revision as of 21:10, 2021 April 29
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)
| App | Status | |
|---|---|---|
| Check VAP acquired only first encounter | Centralized data front end.accdb | declined |