The noteevents table
Table source: Hospital database.
Table purpose: Contains all notes for patients.
Number of rows: 2,083,180
- PATIENTS on
- ADMISSIONS on
- CAREGIVERS on
TEXTis often large and contains many newline characters: it may be easier to read if viewed in a distinct program rather than the one performing the queries.
- Echo reports, ECG reports, and radiology reports are available for both inpatient and outpatient stays. If a patient is an outpatient, there will not be an
HADM_IDassociated with the note. If the patient is an inpatient, but was not admitted to the ICU for that particular hospital admission, then there will not be an
HADM_IDassociated with the note.
- Echos are generated using templates and in some cases there may be discrepancies in severity. For example one report may contain: “Mild PA systolic hypertension. Severe PA systolic hypertension.” indicating that the caregiver may not have removed the appropriate item from the template.
|Name||Postgres data type|
Identifiers which specify the patient:
SUBJECT_ID is unique to a patient and
HADM_ID is unique to a patient hospital stay.
CHARTDATE records the date at which the note was charted.
DESCRIPTION define the type of note recorded. For example, a
CATEGORY of ‘Discharge’ indicates that the note is a discharge note, and a
DESCRIPTION of ‘Summary’ in conjunction with this indicates that the note is a discharge summary.
CGID is the identifier for the caregiver who input the note.
A ‘1’ in the
ISERROR column indicates that a physician has identified this note as an error.
TEXT contains the note text.