Multiple Encounter: Difference between revisions
Ttenbergen (talk | contribs) m still clean-up |
Ttenbergen (talk | contribs) m clean-up |
||
| 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. | ||
If a patient is never discharged in between L_Log entries it may be a '''[[Continuous Stay]]'''. | If a patient is never discharged in between L_Log entries it may be a '''[[Continuous Stay]]'''. | ||
| Line 13: | Line 13: | ||
[[Category: Statistical Analysis]] | [[Category: Statistical Analysis]] | ||
[[Category: Multiple Encounter]] | [[Category: Multiple Encounter | * ]] | ||
Revision as of 11:27, 22 January 2015
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.
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 Re-admission.
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.
See Category:Multiple encounter longitudinal consistency check