The icustays table
Table source: Hospital database.
Table purpose: Defines each ICU stay in the database using STAY_ID.
Number of rows: 76,540
- patients on
- admissions on
stay_idis a generated identifier that is not based on any raw data identifier. The hospital and ICU databases are not intrinsically linked and so do not have any concept of an ICU encounter identifier.
icustaystable is derived from the
transferstable. Specifically, it excludes rows in
transferswhere the ward is not an ICU.
- Multiple consecutive icu stay entries from
transfersare merged into a single entry in
- Heart rate measurements are used to determine if an icu stay is valid. If the heart rate measurement for an icu stay in
transfersis not available, the icu stay will not be included in
|Name||Postgres data type|
Identifiers which specify the patient:
subject_id is unique to a patient,
hadm_id is unique to a patient hospital stay and
stay_id is unique to a patient ward stay.
LAST_CAREUNIT contain, respectively, the first and last ICU type in which the patient was cared for. As an
stay_id groups all ICU admissions within 24 hours of each other, it is possible for a patient to be transferred from one type of ICU to another and have the same
Care units are derived from the TRANSFERS table, and definition for the abbreviations can be found in the documentation for TRANSFERS.
INTIME provides the date and time the patient was transferred into the ICU.
OUTTIME provides the date and time the patient was transferred out of the ICU.
LOS is the length of stay for the patient for the given ICU stay, which may include one or more ICU units. The length of stay is measured in fractional days.
Was this page helpful?
Glad to hear it! Please raise an issue here to tell us how we can improve.
Sorry to hear that. Please raise an issue here to tell us how we can improve.