Multiple Encounter: Difference between revisions

(12 intermediate revisions by the same user not shown)

Line 1:

Patients may show up in our database repeatedly. ~~Because our~~ records are patient-ward-stay based~~, we do not have an inherent link to reflect this~~.

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 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 ''which article''?~~

~~If a patient is never discharged in between encounters, patient may be a ''~~[[~~Continuous Stay~~]]~~''. See~~ that ~~article~~ for ~~definitions~~.

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

~~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]]''. See that article for definitions.~~

~~Need to address:~~

== Related Articles ==

* check for inconsistencies like brain dead and ARF

[[Category: Statistical Analysis]]

[[Category:Statistical Analysis]]

[[Category: ~~Multi-encounter check~~ | *]]

[[Category:Multiple Encounter | * ]]

@@ Line 1: / Line 1: @@
-Patients may show up in our database repeatedly. Because our records are patient-ward-stay based, we do not have an inherent link to reflect this.
+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 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 ''which article''?
-If a patient is never discharged in between encounters, patient may be a ''[[Continuous Stay]]''. See that article for definitions.
+The [[data processor]] runs a set of checks during vetting that attempts to find and make consistent the records for patients encountered previously.
-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]]''. See that article for definitions.
+{{Data Integrity Check List}}
-Need to address:
+== Related Articles ==
-* check for inconsistencies like brain dead and ARF
+{{Related Articles}}
-[[Category: Statistical Analysis]]
+[[Category:Statistical Analysis]]
-[[Category: Multi-encounter check | *]]
+[[Category:Multiple Encounter | * ]]