Open rincont opened 8 years ago
It should be in all the tables - but often it is the second column, not the first. The first is often a meaningless number used for data integrity checks. Have you found any tables where patientUnitStayID is not present?
On Sun, Jan 31, 2016 at 1:45 PM, rincont notifications@github.com wrote:
Should the patientUnitStayID be in all of the tables? In some tables we refer to the patientHealthSystemStayID and in others we have apachePrePatientID and/or apachePrePatientResultID... Doesn't the patientUnitStayID link them all together?
— Reply to this email directly or view it on GitHub https://github.com/mit-eicu/eicu-website/issues/11.
Yes I found tables where only the hospital ID known as patientHealthSystemStayID or the apache ID known as apachePrePatientResultID is present. No patientUnitStayID is present.
Which tables? I just looked at the database: all the APACHE* tables have a column for patientUnitStayID. Might be a documentation error.
Keith says we should just drop the "apachePre" tables as they aren't in the final database. This might address your concern.
all tables except autoacuityoverridehistory
include patientUnitStayID
. autoacuityoverridehistory
includes patienthealthsystemstayid
.
Should the patientUnitStayID be in all of the tables? In some tables we refer to the patientHealthSystemStayID and in others we have apachePrePatientID and/or apachePrePatientResultID... Doesn't the patientUnitStayID link them all together?