Multiple Encounter: Difference between revisions

(4 intermediate revisions by the same user not shown)

Line 1:

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.

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 '''[[~~Re-admission~~]]'''.

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 ==

Line 10:

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]]~~

[[Category: Statistical Analysis]]

== Related Articles ==

[[Category: Multiple Encounter | * ]]

[[Category:Statistical Analysis]]

[[Category:Multiple Encounter | * ]]

@@ Line 1: / Line 1: @@
-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.
+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 '''[[Re-admission]]'''.
+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 ==
@@ Line 10: / Line 10: @@
 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]]
+{{Data Integrity Check List}}
-[[Category: Statistical Analysis]]
+== Related Articles ==
-[[Category: Multiple Encounter | * ]]
+{{Related Articles}}
+[[Category:Statistical Analysis]]
+[[Category:Multiple Encounter | * ]]