Multiple Encounter: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Encounter vs admission vs record: moved content to Encounter number since that is really what that was about
m Text replacement - "[[Category: " to "[[Category:"
 
(7 intermediate revisions by the same user not shown)
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]].


For patients encountered repeatedly some data should be consistent between stays.
If a patient is never discharged in between L_Log entries it may be a '''[[Continuous Stay]]'''.
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.
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]]'''.  


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.
== Multiple encounter longitudinal consistency checks ==
 
For patients encountered repeatedly some data should be consistent between stays.
== Terminology and definitions==
''temporary parking during clean-up''


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


===== Encounter vs admission vs record =====
{{Data Integrity Check List}}
*Continuous Admission: patients that move between ICU's and wards within their own center or to other centers in the city during the same hospital admission. (Trish)
*New encounter: when a patient is discharged from the hospital system in the city back to the community and he then returns to the hospital from the community (generally through the ER), this is a new encounter to the hospital system in the city. (Trish)
** So, does "same encounter" mean the same as "same hospital admission"? We really can't use that since we don't collect on all wards. I was asking Julie about this before, but we didn't finish the discussion. [[User:Ttenbergen|Ttenbergen]] 14:53, 29 October 2008 (CDT)
***Isn't this going off onto a tangent?  Depend on how you are looking at the data. Same encounter to one hospital or same encounter to hospital system in the city or new encounter to a hospital or new encounter to the hospital system in the city.
**** We are using the terms, and I need to be sure we are all using them in the same way. I don't think that's a tangent, is it? We are using "encounter" to mean different things at different times.[[User:Ttenbergen|Ttenbergen]] 14:24, 30 October 2008 (CDT)


==Need to address==  
== Related Articles ==
* check for inconsistencies like brain dead and ARF
{{Related Articles}}


[[Category: Statistical Analysis]]
[[Category:Statistical Analysis]]
[[Category: Multiple Encounter]]
[[Category:Multiple Encounter | * ]]

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: