{"file_name":"omr","description":"The Online Medical Record (OMR) table stores miscellaneous information documented in the electronic health record. It is a useful source of outpatient measurements such as blood pressure, weight, height, and body mass index.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"chartdate","description":"The date on which the observation was recorded."},{"column_name":"seq_num","description":"An monotonically increasing integer which uniquely distinguishes results of the same type recorded on the same day. For example, if two blood pressure measurements occur on the same day, seq_num orders them chronologically."},{"column_name":"result_name","description":"Each row provides detail regarding a single observation in the EHR. result_name provides a human interpretable description of the observation. As of MIMIC-IV v2.2, the following table lists the number of observations and the most common value."},{"column_name":"result_value","description":"result_value is the value associated with the given OMR observation. For example, for the result_name of ‘Blood Pressure’, the field_value column contains the recorded blood pressure (120/80, 130/70, and so on)."}],"class":"hosp"}
{"file_name":"provider","description":"A description table for providers in the database referenced by provider_id. As of MIMIC-IV v2.2, this table simply lists all unique provider_id in the database. Note that most tables contain a prefix before provider_id. All columns with a suffix link to provider_id.","columns":[{"column_name":"provider_id","description":"provider_id lists all possible identifiers for providers used throughout the database. Provider identifiers follow a consistent pattern: the letter “P”, followed by either three numbers, followed by two letters or two numbers. For example, “P003AB”, “P00102”, “P1248B”, etc. Provider identifiers are randomly generated and do not have any inherent meaning aside from uniquely identifying the same provider across the database."}],"class":"hosp"}
{"file_name":"admissions","description":"The admissions table gives information regarding a patient’s admission to the hospital. Since each unique hospital visit for a patient is assigned a unique hadm_id, the admissions table can be considered as a definition table for hadm_id. Information available includes timing information for admission and discharge, demographic information, the source of the admission, and so on.","columns":[{"column_name":"subject_id","description":"Each row of this table contains a unique hadm_id, which represents a single patient’s admission to the hospital. hadm_id ranges from 2000000 - 2999999. It is possible for this table to have duplicate subject_id, indicating that a single patient had multiple admissions to the hospital. The ADMISSIONS table can be linked to the PATIENTS table using subject_id."},{"column_name":"hadm_id","description":"Each row of this table contains a unique hadm_id, which represents a single patient’s admission to the hospital. hadm_id ranges from 2000000 - 2999999. It is possible for this table to have duplicate subject_id, indicating that a single patient had multiple admissions to the hospital. The ADMISSIONS table can be linked to the PATIENTS table using subject_id."},{"column_name":"admittime","description":"admittime provides the date and time the patient was admitted to the hospital, while dischtime provides the date and time the patient was discharged from the hospital. If applicable, deathtime provides the time of in-hospital death for the patient. Note that deathtime is only present if the patient died in-hospital, and is almost always the same as the patient’s dischtime. However, there can be some discrepancies due to typographical errors."},{"column_name":"dischtime","description":"admittime provides the date and time the patient was admitted to the hospital, while dischtime provides the date and time the patient was discharged from the hospital. If applicable, deathtime provides the time of in-hospital death for the patient. Note that deathtime is only present if the patient died in-hospital, and is almost always the same as the patient’s dischtime. However, there can be some discrepancies due to typographical errors"},{"column_name":"deathtime","description":"admittime provides the date and time the patient was admitted to the hospital, while dischtime provides the date and time the patient was discharged from the hospital. If applicable, deathtime provides the time of in-hospital death for the patient. Note that deathtime is only present if the patient died in-hospital, and is almost always the same as the patient’s dischtime. However, there can be some discrepancies due to typographical errors."},{"column_name":"admission_type","description":"admission_type is useful for classifying the urgency of the admission. There are 9 possibilities: ‘AMBULATORY OBSERVATION’, ‘DIRECT EMER.’, ‘DIRECT OBSERVATION’, ‘ELECTIVE’, ‘EU OBSERVATION’, ‘EW EMER.’, ‘OBSERVATION ADMIT’, ‘SURGICAL SAME DAY ADMISSION’, ‘URGENT’."},{"column_name":"admit_provider_id","description":"admit_provider_id provides an anonymous identifier for the provider who admitted the patient. Provider identifiers follow a consistent pattern: the letter “P”, followed by either three numbers, followed by two letters or two numbers. For example, “P003AB”, “P00102”, “P1248B”, etc. Provider identifiers are randomly generated and do not have any inherent meaning aside from uniquely identifying the same provider across the database."},{"column_name":"admission_location","description":"admission_location provides information about the location of the patient prior to arriving at the hospital. Note that as the emergency room is technically a clinic, patients who are admitted via the emergency room usually have it as their admission location."},{"column_name":"discharge_location","description":"Similarly, discharge_location is the disposition of the patient after they are discharged from the hospital."},{"column_name":"insurance","description":"The insurance, language, marital_status, and ethnicity columns provide information about patient demographics for the given hospitalization. Note that as this data is documented for each hospital admission, they may change from stay to stay."},{"column_name":"language","description":"The insurance, language, marital_status, and ethnicity columns provide information about patient demographics for the given hospitalization. Note that as this data is documented for each hospital admission, they may change from stay to stay."},{"column_name":"marital_status","description":"The insurance, language, marital_status, and ethnicity columns provide information about patient demographics for the given hospitalization. Note that as this data is documented for each hospital admission, they may change from stay to stay."},{"column_name":"ethicity","description":"The insurance, language, marital_status, and ethnicity columns provide information about patient demographics for the given hospitalization. Note that as this data is documented for each hospital admission, they may change from stay to stay."},{"column_name":"edregtime","description":"The date and time at which the patient was registered and discharged from the emergency department."},{"column_name":"edouttime","description":"The date and time at which the patient was registered and discharged from the emergency department."},{"column_name":"hospital_expire_flag","description":"This is a binary flag which indicates whether the patient died within the given hospitalization. 1 indicates death in the hospital, and 0 indicates survival to hospital discharge."}, {"column_name": "text", "description": "Admission summaries are long form narratives which describe the patient's introduction the reason for a patient’s admission to the hospital."}],"class":"hosp"}
{"file_name":"d_hcpcs","description":"The d_hcpcs table is used to acquire human readable definitions for the codes used in the hcpcsevents table. The concepts primarily correspond to hospital billing, and are mostly CPT codes. Unfortunately due to licensing restrictions not all code definitions are available.","columns":[{"column_name":"code","description":"A five character code which uniquely represents the event."},{"column_name":"category","description":"Broad classification of the code."},{"column_name":"long_description","description":"Textual descriptions of the code listed for the given row."},{"column_name":"short_description","description":"Textual descriptions of the code listed for the given row."}],"class":"hosp"}
{"file_name":"d_icd_diagnoses","description":"This table defines International Classification of Diseases (ICD) Version 9 and 10 codes for diagnoses. These codes are assigned at the end of the patient’s stay and are used by the hospital to bill for care provided.","columns":[{"column_name":"icd_code","description":"icd_code is the International Coding Definitions (ICD) code."},{"column_name":"icd_version","description":"There are two versions for this coding system: version 9 (ICD-9) and version 10 (ICD-10). These can be differentiated using the icd_version column. In general, ICD-10 codes are more detailed, though code mappings (or “cross-walks”) exist which convert ICD-9 codes to ICD-10 codes.Both ICD-9 and ICD-10 codes are often presented with a decimal. This decimal is not required for interpretation of an ICD code; i.e. the icd_code of ‘0010’ is equivalent to ‘001.0’.ICD-9 and ICD-10 codes have distinct formats: ICD-9 codes are 5 character long strings which are entirely numeric (with the exception of codes prefixed with “E” or “V” which are used for external causes of injury or supplemental classification). Importantly, ICD-9 codes are retained as strings in the database as the leading 0s in codes are meaningful.ICD-10 codes are 3-7 characters long and always prefixed by a letter followed by a set of numeric values."},{"column_name":"long_title","description":"The long_title provides the meaning of the ICD code. For example, the ICD-9 code 0010 has long_title “Cholera due to vibrio cholerae”."}],"class":"hosp"}
{"file_name":"d_icd_procedures","description":"This table defines International Classification of Diseases (ICD) codes for procedures. These codes are assigned at the end of the patient’s stay and are used by the hospital to bill for care provided. They can further be used to identify if certain procedures have been performed (e.g. surgery).","columns":[{"column_name":"icd_code","description":"icd_code is the International Coding Definitions (ICD) code."},{"column_name":"icd_version","description":"There are two versions for this coding system: version 9 (ICD-9) and version 10 (ICD-10). These can be differentiated using the icd_version column. In general, ICD-10 codes are more detailed, though code mappings (or “cross-walks”) exist which convert ICD-9 codes to ICD-10 codes.Both ICD-9 and ICD-10 codes are often presented with a decimal. This decimal is not required for interpretation of an ICD code; i.e. the icd_code of ‘0010’ is equivalent to ‘001.0’."},{"column_name":"long_title","description":"The title fields provide a brief definition for the given procedure code in ``."}],"class":"hosp"}
{"file_name":"d_labitems","description":"d_labitems contains definitions for all itemid associated with lab measurements in the MIMIC database. All data in labevents link to the d_labitems table. Each unique (fluid, category, label) tuple in the hospital database was assigned an itemid in this table, and the use of this itemid facilitates efficient storage and querying of the data.Laboratory data contains information collected and recorded in the hospital laboratory database. This includes measurements made in wards within the hospital and clinics outside the hospital. Most concepts in this table have been mapped to LOINC codes, an openly available ontology which facilitates interoperability.","columns":[{"column_name":"itemid","description":"A unique identifier for a laboratory concept. itemid is unique to each row, and can be used to identify data in labevents associated with a specific concept."},{"column_name":"label","description":"The label column describes the concept which is represented by the itemid."},{"column_name":"fluid","description":"fluid describes the substance on which the measurement was made. For example, chemistry measurements are frequently performed on blood, which is listed in this column as ‘BLOOD’. Many of these measurements are also acquirable on other fluids, such as urine, and this column differentiates these distinct concepts."},{"column_name":"category","description":"category provides higher level information as to the type of measurement. For example, a category of ‘ABG’ indicates that the measurement is an arterial blood gas."}],"class":"hosp"}
{"file_name":"diagnoses_icd","description":"During routine hospital care, patients are billed by the hospital for diagnoses associated with their hospital stay. This table contains a record of all diagnoses a patient was billed for during their hospital stay using the ICD-9 and ICD-10 ontologies. Diagnoses are billed on hospital discharge, and are determined by trained persons who read signed clinical notes.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"seq_num","description":"The priority assigned to the diagnoses. The priority can be interpreted as a ranking of which diagnoses are “important”, but many caveats to this broad statement exist. For example, patients who are diagnosed with sepsis must have sepsis as their 2nd billed condition. The 1st billed condition must be the infectious agent. There’s also less importance placed on ranking low priority diagnoses “correctly” (as there may be no correct ordering of the priority of the 5th - 10th diagnosis codes, for example)."},{"column_name":"icd_code","description":"icd_code is the International Coding Definitions (ICD) code."},{"column_name":"icd_version","description":"There are two versions for this coding system: version 9 (ICD-9) and version 10 (ICD-10). These can be differentiated using the icd_version column. In general, ICD-10 codes are more detailed, though code mappings (or “cross-walks”) exist which convert ICD-9 codes to ICD-10 codes.Both ICD-9 and ICD-10 codes are often presented with a decimal. This decimal is not required for interpretation of an ICD code; i.e. the icd_code of ‘0010’ is equivalent to ‘001.0’."}, {"column_name": "charttime", "description": "The time at which the diagnosis was charted."}],"class":"hosp"}
{"file_name":"drgcodes","description":"Diagnosis related groups (DRGs) are used by the hospital to obtain reimbursement for a patient’s hospital stay. The codes correspond to the primary reason for a patient’s stay at the hospital.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"drg_type","description":"The specific DRG ontology used for the code."},{"column_name":"drg_code","description":"The DRG code."},{"column_name":"description","description":"A description for the given DRG code."},{"column_name":"drg_severity","description":"Some DRG ontologies further qualify the patient severity of illness and likelihood of mortality, which are recorded here."},{"column_name":"drg_mortality","description":"Some DRG ontologies further qualify the patient severity of illness and likelihood of mortality, which are recorded here."}],"class":"hosp"}
{"file_name":"emar","description":"The EMAR table is used to record administrations of a given medicine to an individual patient. Records in this table are populated by bedside nursing staff scanning barcodes associated with the medicine and the patient.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"emar_id","description":"Identifiers for the eMAR table. emar_id is a unique identifier for each order made in eMAR. emar_seq is a consecutive integer which numbers eMAR orders chronologically. emar_id is composed of subject_id and emar_seq in the following pattern: ‘subject_id-emar_seq’."},{"column_name":"emar_seq","description":"Identifiers for the eMAR table. emar_id is a unique identifier for each order made in eMAR. emar_seq is a consecutive integer which numbers eMAR orders chronologically. emar_id is composed of subject_id and emar_seq in the following pattern: ‘subject_id-emar_seq’."},{"column_name":"poe_id","description":"An identifier which links administrations in emar to orders in poe and prescriptions."},{"column_name":"pharmacy_id","description":"An identifier which links administrations in emar to pharmacy information in the pharmacy table."},{"column_name":"enter_provider_id","description":"enter_provider_id provides an anonymous identifier for the provider who entered the information into the eMAR system. Provider identifiers follow a consistent pattern: the letter “P”, followed by either three numbers, followed by two letters or two numbers. For example, “P003AB”, “P00102”, “P1248B”, etc. Provider identifiers are randomly generated and do not have any inherent meaning aside from uniquely identifying the same provider across the database."},{"column_name":"charttime","description":"The time at which the medication was administered."},{"column_name":"medication","description":"The name of the medication which was administered."},{"column_name":"event_txt","description":"Information about the administration. Most frequently event_txt is ‘Administered’, but other possible values are ‘Applied’, ‘Confirmed’, ‘Delayed’, ‘Not Given’, and so on."},{"column_name":"scheduletime","description":"If present, the time at which the administration was scheduled."},{"column_name":"storetime","description":"The time at which the administration was documented in the eMAR table."}],"class":"hosp"}
{"file_name":"emar_detail","description":"The emar_detail table contains information for each medicine administration made in the EMAR table. Information includes the associated pharmacy order, the dose due, the dose given, and many other parameters associated with the medical administration.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"emar_id","description":"Identifiers for the eMAR table. emar_id is a unique identifier for each order made in eMAR. emar_seq is a consecutive integer which numbers eMAR orders chronologically. emar_id is composed of subject_id and emar_seq in the following pattern: ‘subject_id-emar_seq’."},{"column_name":"emar_seq","description":"Identifiers for the eMAR table. emar_id is a unique identifier for each order made in eMAR. emar_seq is a consecutive integer which numbers eMAR orders chronologically. emar_id is composed of subject_id and emar_seq in the following pattern: ‘subject_id-emar_seq’."},{"column_name":"parent_field_ordinal","description":"parent_field_ordinal delineates multiple administrations for the same eMar event, e.g. multiple formulary doses for the full dose. As eMAR requires the administrating provider to scan a barcode for each formulary provided to the patient, it is often the case that multiple rows in emar_detail correspond to a single row in emar (e.g. multiple pills are administered which add up to the desired dose). The structure for emar_detail rows is as follows:There is one row per eMAR order with a NULL parent_field_ordinal: this row usually contains the desired dose for the administration.Afterward, if there are N formulary doses, parent_field_ordinal will take values ‘1.1’, ‘1.2’, …, ‘1.N’.The most common case occurs when there is only one formulary dose per medication. In this case the emar_id will have two rows in the emar_detail table: one with a NULL value for parent_field_ordinal (usually providing the dose due), and one row with a value of ‘1.1’ for parent_field_ordinal (usually providing the actual dose administered)."},{"column_name":"administration_type","description":"The type of administration, including ‘IV Bolus’, ‘IV Infusion’, ‘Medication Infusion’, ‘Transdermal Patch’, and so on."},{"column_name":"pharmacy_id","description":"An identifier which allows linking the eMAR order to pharmacy information provided in the pharmacy table. Note: rarely the same emar_id may have multiple distinct pharmacy_id across rows in the emar_detail table."},{"column_name":"Remaining columns","description":"The remaining columns provide information about the delivery of the formulary dose of the administered medication."}],"class":"hosp"}
{"file_name":"hpcsevents","description":"Billed events occurring during the hospitalization. Includes CPT codes.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"chartdate","description":"The date associated with the coded event."},{"column_name":"hcpcs_cd","description":"A five character code which uniquely represents the event. Link this to code in d_hcpcs for a longer description of the code."},{"column_name":"seq_num","description":"An assigned order to HCPCS codes for an individual hospitalization. This order sometimes conveys meaning, e.g. sometimes higher priority, but this is not guaranteed across all codes."},{"column_name":"short_description","description":"A short textual descriptions of the hcpcs_cd listed for the given row."}],"class":"hosp"}
{"file_name":"labevents","description":"The labevents table stores the results of all laboratory measurements made for a single patient. These include hematology measurements, blood gases, chemistry panels, and less common tests such as genetic assays.","columns":[{"column_name":"labevent_id","description":"An integer which is unique for every row in the table."},{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"specimen_id","description":"Uniquely denoted the specimen from which the lab measurement was made. Most lab measurements are made on patient derived samples (specimens) such as blood, urine, and so on. Often multiple measurements are made on the same sample. The specimen_id will group measurements made on the same sample, e.g. blood gas measurements made on the same sample of blood."},{"column_name":"itemid","description":"An identifier which uniquely denotes laboratory concepts."},{"column_name":"order_provider_id","description":"order_provider_id provides an anonymous identifier for the provider who ordered the laboratory measurement. Provider identifiers follow a consistent pattern: the letter “P”, followed by either three numbers, followed by two letters or two numbers. For example, “P003AB”, “P00102”, “P1248B”, etc. Provider identifiers are randomly generated and do not have any inherent meaning aside from uniquely identifying the same provider across the database."},{"column_name":"charttime","description":"The time at which the laboratory measurement was charted. This is usually the time at which the specimen was acquired, and is usually significantly earlier than the time at which the measurement is available."},{"column_name":"storetime","description":"The time at which the measurement was made available in the laboratory system. This is when the information would have been available to care providers."},{"column_name":"value","description":"The result of the laboratory measurement and, if it is numeric, the value cast as a numeric data type."},{"column_name":"valuenum","description":"The result of the laboratory measurement and, if it is numeric, the value cast as a numeric data type."},{"column_name":"valueuom","description":"The unit of measurement for the laboratory concept."},{"column_name":"ref_range_lower","description":"Upper and lower reference ranges indicating the normal range for the laboratory measurements. Values outside the reference ranges are considered abnormal."},{"column_name":"ref_range_upper","description":"Upper and lower reference ranges indicating the normal range for the laboratory measurements. Values outside the reference ranges are considered abnormal."},{"column_name":"flag","description":"A brief string mainly used to indicate if the laboratory measurement is abnormal."},{"column_name":"priority","description":"The priority of the laboratory measurement: either routine or stat (urgent)."},{"column_name":"comment","description":"Deidentified free-text comments associated with the laboratory measurement. Usually these provide information about the sample, whether any notifications were made to care providers regarding the results, considerations for interpretation, or in some cases the comments contain the result of the laboratory itself. Comments which have been fully deidentified (i.e. no information content retained) are present as three underscores: ___. A NULL comment indicates no comment was made for the row."}],"class":"hosp"}
{"file_name":"microbiologyevents","description":"Microbiology tests are a common procedure to check for infectious growth and to assess which antibiotic treatments are most effective.The table is best explained with a demonstrative example. If a blood culture is requested for a patient, then a blood sample will be taken and sent to the microbiology lab. The time at which this blood sample is taken is the charttime. The spec_type_desc will indicate that this is a blood sample. Bacteria will be cultured on the blood sample, and the remaining columns depend on the outcome of this growth:If no growth is found, the remaining columns will be NULLIf bacteria is found, then each organism of bacteria will be present in org_name, resulting in multiple rows for the single specimen (i.e. multiple rows for the given spec_type_desc).If antibiotics are tested on a given bacterial organism, then each antibiotic tested will be present in the ab_name column (i.e. multiple rows for the given org_name associated with the given spec_type_desc). Antibiotic parameters and sensitivities are present in the remaining columns (dilution_text, dilution_comparison, dilution_value, interpretation).","columns":[{"column_name":"microevent","description":"A unique integer denoting the row."},{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"micro_specimen_id","description":"Uniquely denoted the specimen from which the microbiology measurement was made. Most microbiology measurements are made on patient derived samples (specimens) such as blood, urine, and so on. Often multiple measurements are made on the same sample. The micro_specimen_id will group measurements made on the same sample, e.g. organisms which grew from the same blood sample."},{"column_name":"order_provider_id","description":"order_provider_id provides an anonymous identifier for the provider who ordered the microbiology test. Provider identifiers follow a consistent pattern: the letter “P”, followed by either three numbers, followed by two letters or two numbers. For example, “P003AB”, “P00102”, “P1248B”, etc. Provider identifiers are randomly generated and do not have any inherent meaning aside from uniquely identifying the same provider across the database."},{"column_name":"charttime","description":"charttime records the time at which an observation was charted, and is usually the closest proxy to the time the data was actually measured. chartdate is the same as charttime, except there is no time available.chartdate was included as time information is not always available for microbiology measurements: in order to be clear about when this occurs, charttime is null, and chartdate contains the date of the measurement.In the cases where both charttime and chartdate exists, chartdate is equal to a truncated version of charttime (i.e. charttime without the timing information). Not all observations have a charttime, but all observations have a chartdate."},{"column_name":"chartdate","description":"charttime records the time at which an observation was charted, and is usually the closest proxy to the time the data was actually measured. chartdate is the same as charttime, except there is no time available.chartdate was included as time information is not always available for microbiology measurements: in order to be clear about when this occurs, charttime is null, and chartdate contains the date of the measurement.In the cases where both charttime and chartdate exists, chartdate is equal to a truncated version of charttime (i.e. charttime without the timing information). Not all observations have a charttime, but all observations have a chartdate."},{"column_name":"spec_itemid","description":"The specimen which is tested for bacterial growth. The specimen is a sample derived from a patient; e.g. blood, urine, sputum, etc."},{"column_name":"spec_type_desc","description":"The specimen which is tested for bacterial growth. The specimen is a sample derived from a patient; e.g. blood, urine, sputum, etc."},{"column_name":"test_seq","description":"If multiple samples are drawn, the test_seq will delineate them. For example, if an aerobic and anerobic culture bottle are used for the same specimen, they will have distinct test_seq values (likely 1 and 2)."},{"column_name":"storedate","description":"The date (storedate) or date and time (storetime) of when the microbiology result was available. While many interim results are made available during the process of assessing a microbiology culture, the times here are the time of the last known update."},{"column_name":"storetime","description":"The date (storedate) or date and time (storetime) of when the microbiology result was available. While many interim results are made available during the process of assessing a microbiology culture, the times here are the time of the last known update."},{"column_name":"test_itemid","description":"The test performed on the given specimen."},{"column_name":"test_name","description":"The test performed on the given specimen."},{"column_name":"org_itemid","description":"The organism, if any, which grew when tested. If NULL, no organism grew (i.e. a negative culture)."},{"column_name":"org_name","description":"The organism, if any, which grew when tested. If NULL, no organism grew (i.e. a negative culture)."},{"column_name":"isolate_num","description":"For testing antibiotics, the isolated colony (integer; starts at 1)."},{"column_name":"ab_itemid","description":"If an antibiotic was tested against the given organism for sensitivity, the antibiotic is listed here."},{"column_name":"ab_name","description":"If an antibiotic was tested against the given organism for sensitivity, the antibiotic is listed here."},{"column_name":"dilution_text","description":"Dilution values when testing antibiotic sensitivity."},{"column_name":"dilution_comparison","description":"Dilution values when testing antibiotic sensitivity."},{"column_name":"dilution_value","description":"Dilution values when testing antibiotic sensitivity."},{"column_name":"interpretation","description":"interpretation of the antibiotic sensitivity, and indicates the results of the test. “S” is sensitive, “R” is resistant, “I” is intermediate, and “P” is pending."},{"column_name":"comments","description":"Deidentified free-text comments associated with the microbiology measurement. Usually these provide information about the sample, whether any notifications were made to care providers regarding the results, considerations for interpretation, or in some cases the comments contain the result of the measurement itself. Comments which have been fully deidentified (i.e. no information content retained) are present as three underscores: ___. A NULL comment indicates no comment was made for the row."}],"class":"hosp"}
{"file_name":"patients","description":"Information that is consistent for the lifetime of a patient is stored in this table.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual. As subject_id is the primary key for the table, it is unique for each row."},{"column_name":"gender","description":"gender is the genotypical sex of the patient."},{"column_name":"anchor_age","description":"These columns provide information regarding the actual patient year for the patient admission, and the patient’s age at that time.These columns provide information regarding the actual patient year for the patient admission, and the patient’s age at that time. anchor_age is the patient’s age in the anchor_year. If a patient’s anchor_age is over 89 in the anchor_year then their anchor_age is set to 91, regardless of how old they actually were."},{"column_name":"anchor_year","description":"These columns provide information regarding the actual patient year for the patient admission, and the patient’s age at that time. anchor_year is a shifted year for the patient."},{"column_name":"anchor_year_group","description":"These columns provide information regarding the actual patient year for the patient admission, and the patient’s age at that time. anchor_year_group is a range of years - the patient’s anchor_year occurred during this range."},{"column_name":"dod","description":"The de-identified date of death for the patient. Date of death is extracted from two sources: the hospital information system and the Massachusetts State Registry of Vital Records and Statistics. Individual patient records from MIMIC were matched to the vital records using a custom algorithm based on identifiers including name, social security number, and date of birth.As a result of the linkage, out of hospital mortality is available for MIMIC-IV patients up to one year post-hospital discharge. All patient deaths occurring more than one year after hospital discharge are censored. Survival studies should incorporate this into their design."}],"class":"hosp"}
{"file_name":"pharmacy","description":"The pharmacy table provides detailed information regarding filled medications which were prescribed to the patient. Pharmacy information includes the dose of the drug, the number of formulary doses, the frequency of dosing, the medication route, and the duration of the prescription.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"pharmacy_id","description":"A unique identifier for the given pharmacy entry. Each row of the pharmacy table has a unique pharmacy_id. This identifier can be used to link the pharmacy information to the provider order (in poe or prescriptions) or to the administration of the medication (in emar)."},{"column_name":"poe_id","description":"A foreign key which links to the provider order entry order in the prescriptions table associated with this pharmacy record."},{"column_name":"starttime","description":"The start and stop times for the given prescribed medication."},{"column_name":"stoptime","description":"The start and stop times for the given prescribed medication."},{"column_name":"medication","description":"The name of the medication provided."},{"column_name":"proc_type","description":"The type of order: “IV Piggyback”, “Non-formulary”, “Unit Dose”, and so on."},{"column_name":"status","description":"Whether the prescription is active, inactive, or discontinued."},{"column_name":"entertime","description":"The date and time at which the prescription was entered into the pharmacy system."},{"column_name":"verifiedtime","description":"The date and time at which the prescription was verified by a physician."},{"column_name":"route","description":"The intended route of administration for the prescription."},{"column_name":"frequency","description":"The frequency at which the medication should be administered to the patient. Many commonly used short hands are used in the frequency column. Q# indicates every # hours; e.g. “Q6” or “Q6H” is every 6 hours."},{"column_name":"disp_sched","description":"The hours of the day at which the medication should be administered, e.g. “08, 20” would indicate the medication should be administered at 8:00 AM and 8:00 PM, respectively."},{"column_name":"infusion_type","description":"A coded letter describing the type of infusion: ‘B’, ‘C’, ‘N’, ‘N1’, ‘O’, or ‘R’."},{"column_name":"sliding_scale","description":"Indicates whether the medication should be given on a sliding scale: either ‘Y’ or ‘N’."},{"column_name":"lockout_interval","description":"The time the patient must wait until providing themselves with another dose; often used with patient controlled analgesia."},{"column_name":"basal_rate","description":"The rate at which the medication is given over 24 hours."},{"column_name":"one_hr_max","description":"The maximum dose that may be given in a single hour."},{"column_name":"doses_per_24_hrs","description":"The number of expected doses per 24 hours. Note that this column can be misleading for continuously infused medications as they are usually only “dosed” once per day, despite continuous administration."},{"column_name":"duration","description":"duration is the numeric duration of the given dose, while duration_interval can be considered as the unit of measurement for the given duration. For example, often duration is 1 and duration_interval is “Doses”. Alternatively, duration could be 8 and the duration_interval could be “Weeks”"},{"column_name":"duration_interval","description":"duration is the numeric duration of the given dose, while duration_interval can be considered as the unit of measurement for the given duration. For example, often duration is 1 and duration_interval is “Doses”. Alternatively, duration could be 8 and the duration_interval could be “Weeks”"},{"column_name":"expiration_value","description":"If the drug has a relevant expiry date, these columns detail when this occurs. expiration_value and expiration_unit provide a length of time until the drug expires, e.g. 30 days, 72 hours, and so on. expirationdate provides the deidentified date of expiry."},{"column_name":"expiration_unit","description":"If the drug has a relevant expiry date, these columns detail when this occurs. expiration_value and expiration_unit provide a length of time until the drug expires, e.g. 30 days, 72 hours, and so on. expirationdate provides the deidentified date of expiry."},{"column_name":"expirationdate","description":"If the drug has a relevant expiry date, these columns detail when this occurs. expiration_value and expiration_unit provide a length of time until the drug expires, e.g. 30 days, 72 hours, and so on. expirationdate provides the deidentified date of expiry."},{"column_name":"dispensation","description":"The source of dispensation for the medication."},{"column_name":"fill_quantity","description":"What proportion of the formulary to fill."}],"class":"hosp"}
{"file_name":"poe","description":"Provider order entry (POE) is the general interface through which care providers at the hospital enter orders. Most treatments and procedures must be ordered via POE.","columns":[{"column_name":"poe_id","description":"A unique identifier for the given order. poe_id is composed of subject_id and a monotonically increasing integer, poe_seq, in the following format: subject_id-poe_seq."},{"column_name":"poe_seq","description":"A monotonically increasing integer which chronologically sorts the POE orders. That is, POE orders can be ordered sequentially by poe_seq."},{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"ordertime","description":"The date and time at which the provider order was made."},{"column_name":"order_type","description":"The type of provider order. One of the following: ADT orders, Blood Bank, Cardiology, Consults, Critical Care, General Care, Hemodialysis, IV therapy, Lab, Medications, Neurology, Nutrition, OB, RadiologyRespiratory, TPN."},{"column_name":"order_subtype","description":"Further detail on the type of order made by the provider. The order_subtype is best interpreted alongside the order_type, e.g. order_type: 'Cardiology' with order_subtype: 'Holter Monitor'."},{"column_name":"transaction_type","description":"The action which the provider performed when performing this order. One of the following: Change, Co, D/C, H, New, T."},{"column_name":"discontinue_of_poe_id","description":"If this order discontinues a previous order, then discontinue_of_poe_id will link to the previous order which was discontinued. Conversely, if this order was later discontinued by a distinct order, then discontinued_by_poe_id will link to that future order."},{"column_name":"discontinued_by_poe_id","description":"If this order discontinues a previous order, then discontinue_of_poe_id will link to the previous order which was discontinued. Conversely, if this order was later discontinued by a distinct order, then discontinued_by_poe_id will link to that future order."},{"column_name":"order_provider_id","description":"order_provider_id provides an anonymous identifier for the provider who made the order. Provider identifiers follow a consistent pattern: the letter “P”, followed by either three numbers, followed by two letters or two numbers. For example, “P003AB”, “P00102”, “P1248B”, etc. Provider identifiers are randomly generated and do not have any inherent meaning aside from uniquely identifying the same provider across the database."},{"column_name":"order_status","description":"Whether the order is still active (‘Active’) or whether it has been inactivated (‘Inactive’)."}],"class":"hosp"}
{"file_name":"poe_detail","description":"The poe_detail table provides further information on POE orders. The table uses an Entity-Attribute-Value (EAV) model: the entity is poe_id, the attribute is field_name, and the value is field_value. EAV tables allow for flexible description of entities when the attributes are heterogenous.","columns":[{"column_name":"poe_id","description":"A unique identifier for the given order. poe_id is composed of subject_id and a monotonically increasing integer, poe_seq, in the following format: subject_id-poe_seq."},{"column_name":"poe_seq","description":"A monotonically increasing integer which chronologically sorts the POE orders. That is, POE orders can be ordered sequentially by poe_seq."},{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"field_name","description":"Each row provides detail regarding a particular aspect of a POE order. field_name is the name given to that aspect. As of MIMIC-IV v2.2, the following table lists the possible values and the most common entry for it in field_value."},{"column_name":"field_value","description":"field_value is the value associated with the given POE order and field_name. For example, for the field_name of ‘Admit to’, the field_value column contains the type of unit the patient was admitted to (Psychiatry, GYN, and so on)."}],"class":"hosp"}
{"file_name":"prescriptions","description":"The prescriptions table provides information about prescribed medications. Information includes the name of the drug, coded identifiers including the Generic Sequence Number (GSN) and National Drug Code (NDC), the product strength, the formulary dose, and the route of administration.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"pharmacy_id","description":"An identifier which links administrations in emar to pharmacy information in the pharmacy table."},{"column_name":"poe_id","description":"These columns allow linking prescriptions to associated orders in the poe table."},{"column_name":"poe_seq","description":"These columns allow linking prescriptions to associated orders in the poe table."},{"column_name":"order_provider_id","description":"order_provider_id provides an anonymous identifier for the provider who initiated the order. Provider identifiers follow a consistent pattern: the letter “P”, followed by either three numbers, followed by two letters or two numbers. For example, “P003AB”, “P00102”, “P1248B”, etc. Provider identifiers are randomly generated and do not have any inherent meaning aside from uniquely identifying the same provider across the database."},{"column_name":"starttime","description":"The prescribed start and stop time for the medication."},{"column_name":"stoptime","description":"The prescribed start and stop time for the medication."},{"column_name":"drug_type","description":"The component of the prescription which the drug occupies. Can be one of ‘MAIN’, ‘BASE’, or ‘ADDITIVE’."},{"column_name":"drug","description":"A free-text description of the medication administered."},{"column_name":"formulary_drug_cd","description":"A hospital specific ontology used to order drugs from the formulary."},{"column_name":"gsn","description":"The Generic Sequence Number (GSN), a coded identifier used for medications."},{"column_name":"ndc","description":"The National Drug Code (NDC), a coded identifier which uniquely identifiers medications."},{"column_name":"prod_strength","description":"A free-text description of the composition of the prescribed medication (e.g. ‘12 mg / 0.8 mL Oral Syringe’, ‘12.5mg Tablet’, etc)."},{"column_name":"form_rx","description":"The container in which the formulary dose is delivered (e.g. ‘TABLET’, ‘VIAL’, etc)."},{"column_name":"dose_val_rx","description":"The prescribed dose for the patient intended to be administered over the given time period."},{"column_name":"dose_unit_rx","description":"The unit of measurement for the dose."},{"column_name":"form_val_disp","description":"The amount of the medication which is contained in a single formulary dose."},{"column_name":"form_unit_disp","description":"The unit of measurement used for the formulary dosage."},{"column_name":"doses_per_24_hrs","description":"The number of doses per 24 hours for which the medication is to be given. A daily dose would result in doses_per_24_hrs: 1, bidaily (BID) would be 2, and so on."},{"column_name":"route","description":"The route of administration for the medication."}],"class":"hosp"}
{"file_name":"procedures_icd","description":"During routine hospital care, patients are billed by the hospital for procedures they undergo. This table contains a record of all procedures a patient was billed for during their hospital stay using the ICD-9 and ICD-10 ontologies.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"seq_num","description":"An assigned priority for procedures which occurred within the hospital stay."},{"column_name":"chartdate","description":"The date of the associated procedures. Date does not strictly correlate with seq_num."},{"column_name":"icd_code","description":"icd_code is the International Coding Definitions (ICD) code."},{"column_name":"icd_version","description":"There are two versions for this coding system: version 9 (ICD-9) and version 10 (ICD-10). These can be differentiated using the icd_version column. In general, ICD-10 codes are more detailed, though code mappings (or “cross-walks”) exist which convert ICD-9 codes to ICD-10 codes."}],"class":"hosp"}
{"file_name":"services","description":"The services table describes the service that a patient was admitted under. While a patient can be physicially located at a given ICU type (say MICU), they are not necessarily being cared for by the team which staffs the MICU. This can happen due to a number of reasons, including bed shortage. The services table should be used if interested in identifying the type of service a patient is receiving in the hospital. For example, if interested in identifying surgical patients, the recommended method is searching for patients admitted under a surgical service. Each service is listed in the table as an abbreviation - this is exactly how the data is stored in the hospital database. For user convenience, we have provided a description of each service type.","columns":[{"column_name":"subject_id","description":"subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."},{"column_name":"hadm_id","description":"hadm_id is an integer identifier which is unique for each patient hospitalization."},{"column_name":"transfertime","description":"transfertime is the time at which the patient moved from the prev_service (if present) to the curr_service."},{"column_name":"prev_service","description":"prev_service and curr_service are the previous and current service that the patient resides under."},{"column_name":"curr_service","description":"prev_service and curr_service are the previous and current service that the patient resides under."}],"appendices":[{"abbreviations":"CMED","description":"Cardiac Medical - for non-surgical cardiac related admissions"},{"abbreviations":"CSURG","description":"Cardiac Surgery - for surgical cardiac admissions"},{"abbreviations":"DENT","description":"Dental - for dental/jaw related admissions"},{"abbreviations":"ENT","description":"Ear, nose, and throat - conditions primarily affecting these areas"},{"abbreviations":"EYE","description":"Eye diseases - including subspecialty services in glaucoma, cataract surgery, cornea and external diseases, and neuro-ophthalmology."},{"abbreviations":"GU","description":"Genitourinary - reproductive organs/urinary system"},{"abbreviations":"GYN","description":"Gynecological - female reproductive systems and breasts"},{"abbreviations":"MED","description":"Medical - general service for internal medicine"},{"abbreviations":"NB","description":"Newborn - infants born at the hospital"},{"abbreviations":"NBB","description":"Newborn baby - infants born at the hospital"},{"abbreviations":"NMED","description":"Neurologic Medical - non-surgical, relating to the brain"},{"abbreviations":"NSURG","description":"Neurologic Surgical - surgical, relating to the brain"},{"abbreviations":"OBS","description":"Obstetrics - conerned with childbirth and the care of women giving birth"},{"abbreviations":"ORTHO","description":"Orthopaedic - surgical, relating to the musculoskeletal system"},{"abbreviations":"OMED","description":"Oncologic Medical - non-surgical, relating to cancer"},{"abbreviations":"PSURG","description":"Plastic - restortation/reconstruction of the human body (including cosmetic or aesthetic)"},{"abbreviations":"PSYCH","description":"Psychiatric - mental disorders relating to mood, behaviour, cognition, or perceptions"},{"abbreviations":"SURG","description":"Surgical - general surgical service not classified elsewhere"},{"abbreviations":"TRAUM","description":"Trauma - injury or damage caused by physical harm from an external source"},{"abbreviations":"TSURG","description":"Thoracic Surgical - surgery on the thorax, located between the neck and the abdomen"},{"abbreviations":"VSURG","description":"Vascular Surgical - surgery relating to the circulatory system"}],"class":"hosp"}
{"file_name":"transfers","description":"Physical locations for patients throughout their hospital stay.","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient."},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay."},{"column_name":"transfer_id","description":"transfer_id is unique to a patient physical location."},{"column_name":"eventtype","description":"eventtype describes what transfer event occurred: ‘ed’ for an emergency department stay, ‘admit’ for an admission to the hospital, ‘transfer’ for an intra-hospital transfer and ‘discharge’ for a discharge from the hospital."},{"column_name":"careunit","description":"The type of unit or ward in which the patient is physically located. Examples of care units include medical ICUs, surgical ICUs, medical wards, new baby nurseries, and so on."},{"column_name":"intime","description":"intime provides the date and time the patient was transferred into the current care unit (careunit) from the previous care unit. outtime provides the date and time the patient was transferred out of the current physical location."},{"column_name":"outtime","description":"intime provides the date and time the patient was transferred into the current care unit (careunit) from the previous care unit. outtime provides the date and time the patient was transferred out of the current physical location."}],"class":"hosp"}
{"file_name":"caregiver","description":"A description table for the ICU caregivers in the ICU module referenced by caregiver_id. As of MIMIC-IV v2.2, this table simply lists all unique caregiver_id in the database.Note that, in order to distinguish identifiers used in the hospital wide EHR from those used in the ICU information system, we have adopted the nomenclature of “caregivers” for the ICU (caregiver_id and caregivers). For the hospital data in the hosp module, we use the terminology of “providers” (provider_id and providers). However, conceptually, both these sets of identifiers and tables refer to practicing providers at the hospital.","columns":[{"column_name":"caregiver_id","description":"caregiver_id lists all possible identifiers for caregivers used in the ICU module. caregiver_id uniquely identifies a single caregiver who documented data in the ICU information system."}],"class":"icu"}
{"file_name":"d_items","description":"Dimension table describing itemid. Defines concepts recorded in the events table in the ICU module.","columns":[{"column_name":"itemid","description":"As an alternate primary key to the table, itemid is unique to each row."},{"column_name":"label","description":"The label column describes the concept which is represented by the itemid."},{"column_name":"abbreviation","description":"The abbreviation column, only available in Metavision, lists a common abbreviation for the label."},{"column_name":"linksto","description":"linksto provides the table name which the data links to. For example, a value of ‘chartevents’ indicates that the itemid of the given row is contained in CHARTEVENTS. A single itemid is only used in one event table, that is, if an itemid is contained in CHARTEVENTS it will not be contained in any other event table (e.g. IOEVENTS, CHARTEVENTS, etc)."},{"column_name":"category","description":"category provides some information of the type of data the itemid corresponds to. Examples include ‘ABG’, which indicates the measurement is sourced from an arterial blood gas, ‘IV Medication’, which indicates that the medication is administered through an intravenous line, and so on."},{"column_name":"unitname","description":"unitname specifies the unit of measurement used for the itemid. This column is not always available, and this may be because the unit of measurement varies, a unit of measurement does not make sense for the given data type, or the unit of measurement is simply missing. Note that there is sometimes additional information on the unit of measurement in the associated event table, e.g. the valueuom column in CHARTEVENTS."},{"column_name":"param_type","description":"param_type describes the type of data which is recorded: a date, a number or a text field."},{"column_name":"lownormalvalue","description":"These columns store reference ranges for the measurement. Note that a reference range encompasses the expected value of a measurement: values outside of this may still be physiologically plausible, but are considered unusual."},{"column_name":"highnormalvalue","description":"These columns store reference ranges for the measurement. Note that a reference range encompasses the expected value of a measurement: values outside of this may still be physiologically plausible, but are considered unusual."}],"class":"icu"}
{"file_name":"chartevents","description":"chartevents contains all the charted data available for a patient. During their ICU stay, the primary repository of a patient’s information is their electronic chart. The electronic chart displays patients' routine vital signs and any additional information relevant to their care: ventilator settings, laboratory values, code status, mental status, and so on. As a result, the bulk of information about a patient’s stay is contained in chartevents. Furthermore, even though laboratory values are captured elsewhere (labevents), they are frequently repeated within chartevents. This occurs because it is desirable to display the laboratory values on the patient’s electronic chart, and so the values are copied from the database storing laboratory values to the database storing the chartevents.","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient"},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay."},{"column_name":"stay_id","description":"stay_id is unique to a patient ward stay."},{"column_name":"caregiver_id","description":"caregiver_id uniquely identifies a single caregiver who documented data in the ICU information system."},{"column_name":"charttime","description":"charttime records the time at which an observation was made, and is usually the closest proxy to the time the data was actually measured."},{"column_name":"storetime","description":"storetime records the time at which an observation was manually input or manually validated by a member of the clinical staff."},{"column_name":"itemid","description":"Identifier for a single measurement type in the database. Each row associated with one itemid (e.g. 220045) corresponds to an instantiation of the same measurement (e.g. heart rate)."},{"column_name":"value","description":"value contains the value measured for the concept identified by the itemid. If this value is numeric, then valuenum contains the same data in a numeric format. If this data is not numeric, valuenum is null. In some cases (e.g. scores like Glasgow Coma Scale, Richmond Sedation Agitation Scale and Code Status), valuenum contains the score and value contains the score and text describing the meaning of the score."},{"column_name":"valuenum","description":"value contains the value measured for the concept identified by the itemid. If this value is numeric, then valuenum contains the same data in a numeric format. If this data is not numeric, valuenum is null. In some cases (e.g. scores like Glasgow Coma Scale, Richmond Sedation Agitation Scale and Code Status), valuenum contains the score and value contains the score and text describing the meaning of the score."},{"column_name":"valueuom","description":"valueuom is the unit of measurement for the value, if appropriate."},{"column_name":"warning","description":"warning specifies if a warning for this observation was manually documented by the care provider."}],"class":"icu"}
{"file_name":"datetimeevents","description":"datetimeevents contains all date measurements about a patient in the ICU. For example, the date of last dialysis would be in the datetimeevents table, but the systolic blood pressure would not be in this table. As all dates in MIMIC are anonymized to protect patient confidentiality, all dates in this table have been shifted. Note that the chronology for an individual patient has been unaffected however, and quantities such as the difference between two dates remain true to reality.","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient"},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay."},{"column_name":"stay_id","description":"stay_id is unique to a patient ward stay."},{"column_name":"caregiver_id","description":"caregiver_id uniquely identifies a single caregiver who documented data in the ICU information system."},{"column_name":"charttime","description":"charttime records the time at which an observation was made, and is usually the closest proxy to the time the data was actually measured."},{"column_name":"storetime","description":"storetime records the time at which an observation was manually input or manually validated by a member of the clinical staff."},{"column_name":"itemid","description":"Identifier for a single measurement type in the database. Each row associated with one itemid (e.g. 220045) corresponds to an instantiation of the same measurement (e.g. heart rate)."},{"column_name":"value","description":"value contains the value measured for the concept identified by the itemid. If this value is numeric, then valuenum contains the same data in a numeric format. If this data is not numeric, valuenum is null. In some cases (e.g. scores like Glasgow Coma Scale, Richmond Sedation Agitation Scale and Code Status), valuenum contains the score and value contains the score and text describing the meaning of the score."},{"column_name":"valuenum","description":"value contains the value measured for the concept identified by the itemid. If this value is numeric, then valuenum contains the same data in a numeric format. If this data is not numeric, valuenum is null. In some cases (e.g. scores like Glasgow Coma Scale, Richmond Sedation Agitation Scale and Code Status), valuenum contains the score and value contains the score and text describing the meaning of the score."},{"column_name":"valueuom","description":"valueuom is the unit of measurement for the value, if appropriate."},{"column_name":"warning","description":"warning specifies if a warning for this observation was manually documented by the care provider."}],"class":"icu"}
{"file_name":"icustays","description":"Tracking information for ICU stays including admission and discharge times.","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient."},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay."},{"column_name":"stay_id","description":"stay_id is unique to a patient ward stay."},{"column_name":"FIRST_CAREUNIT","description":"FIRST_CAREUNIT and 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 stay_id.Care units are derived from the TRANSFERS table, and definition for the abbreviations can be found in the documentation for TRANSFERS."},{"column_name":"LAST_CAREUNIT","description":"FIRST_CAREUNIT and 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 stay_id.Care units are derived from the TRANSFERS table, and definition for the abbreviations can be found in the documentation for TRANSFERS."},{"column_name":"INTIME","description":"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."},{"column_name":"OUTTIME","description":"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."},{"column_name":"LOS","description":"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."}],"class":"icu"}
{"file_name":"Ingredientevents","description":"Ingredients of continuous or intermittent administrations including nutritional and water content.","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient."},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay."},{"column_name":"stay_id","description":"stay_id is unique to a patient ICU stay."},{"column_name":"caregiver_id","description":"caregiver_id uniquely identifies a single caregiver who documented data in the ICU information system."},{"column_name":"starttime","description":"starttime and endtime record the start and end time of the event."},{"column_name":"endtime","description":"starttime and endtime record the start and end time of the event."},{"column_name":"storetime","description":"storetime records the time at which an observation was manually input or manually validated by a member of the clinical staff."},{"column_name":"itemid","description":"Identifier for a single measurement type in the database. Each row associated with one itemid which corresponds to an instantiation of the same measurement (e.g. norepinephrine)."},{"column_name":"amount","description":"amount and amountuom list the amount of a drug or substance administered to the patient either between the starttime and endtime."},{"column_name":"amountuom","description":"amount and amountuom list the amount of a drug or substance administered to the patient either between the starttime and endtime."},{"column_name":"rate","description":"rate and rateuom list the rate at which the drug or substance was administered to the patient either between the starttime and endtime."},{"column_name":"rateuom","description":"rate and rateuom list the rate at which the drug or substance was administered to the patient either between the starttime and endtime."},{"column_name":"orderid","description":"orderid links multiple items contained in the same solution together. For example, when a solution of noradrenaline and normal saline is administered both noradrenaline and normal saline occur on distinct rows but will have the same orderid."},{"column_name":"linkorderid","description":"linkorderid links the same order across multiple instantiations: for example, if the rate of delivery for the solution with noradrenaline and normal saline is changed, two new rows which share the same new orderid will be generated, but the linkorderid will be the same."},{"column_name":"statusdescription","description":"statusdescription states the ultimate status of the item, or more specifically, row. It is used to indicate why the delivery of the compound has ended. There are only six possible statuses: Changed - The current delivery has ended as some aspect of it has changed (most frequently, the rate has been changed). Paused - The current delivery has been paused. FinishedRunning - The delivery of the item has finished (most frequently, the bag containing the compound is empty). Stopped - The delivery of the item been terminated by the caregiver. Rewritten - Incorrect information was input, and so the information in this row was rewritten (these rows are primarily useful for auditing purposes - the rates/amounts described were not delivered and so should not be used if determining what compounds a patient has received). Flushed - A line was flushed."},{"column_name":"originalamount","description":"Drugs are usually mixed within a solution and delivered continuously from the same bag. This column represents the amount of the compound contained in the bag at starttime."},{"column_name":"originalrate","description":"This is the rate that was input by the care provider. Note that this may differ from rate because of various reasons: originalrate was the original planned rate, while the rate column will be the true rate delivered."}],"class":"icu"}
{"file_name":"inputevents","description":"Information documented regarding continuous infusions or intermittent administrations. The original source database recorded input data using two tables: RANGESIGNALS and ORDERENTRY. These tables do not appear in MIMIC as they have been merged to form the INPUTEVENTS table. RANGESIGNALS contains recorded data elements which last for a fixed period of time. Furthermore, the RANGESIGNALS table recorded information for each component of the drug separately. For example, for a norepinephrine administration there would be two components: a main order component (norepinephrine) and a solution component (NaCl). The starttime and endtime of RANGESIGNALS indicated when the drug started and finished. Any change in the drug rate would result in the current infusion ending, and a new starttime being created.","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient."},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay."},{"column_name":"stay_id","description":"stay_id is unique to a patient ICU stay."},{"column_name":"caregiver_id","description":"caregiver_id uniquely identifies a single caregiver who documented data in the ICU information system."},{"column_name":"starttime","description":"starttime and endtime record the start and end time of the event."},{"column_name":"endtime","description":"starttime and endtime record the start and end time of the event."},{"column_name":"storetime","description":"storetime records the time at which an observation was manually input or manually validated by a member of the clinical staff."},{"column_name":"itemid","description":"Identifier for a single measurement type in the database. Each row associated with one itemid which corresponds to an instantiation of the same measurement (e.g. norepinephrine)."},{"column_name":"amount","description":"amount and amountuom list the amount of a drug or substance administered to the patient either between the starttime and endtime."},{"column_name":"amountuom","description":"amount and amountuom list the amount of a drug or substance administered to the patient either between the starttime and endtime."},{"column_name":"rate","description":"rate and rateuom list the rate at which the drug or substance was administered to the patient either between the starttime and endtime."},{"column_name":"rateuom","description":"rate and rateuom list the rate at which the drug or substance was administered to the patient either between the starttime and endtime."},{"column_name":"orderid","description":"orderid links multiple items contained in the same solution together. For example, when a solution of noradrenaline and normal saline is administered both noradrenaline and normal saline occur on distinct rows but will have the same orderid."},{"column_name":"linkorderid","description":"linkorderid links the same order across multiple instantiations: for example, if the rate of delivery for the solution with noradrenaline and normal saline is changed, two new rows which share the same new orderid will be generated, but the linkorderid will be the same."},{"column_name":"statusdescription","description":"statusdescription states the ultimate status of the item, or more specifically, row. It is used to indicate why the delivery of the compound has ended. There are only six possible statuses: Changed - The current delivery has ended as some aspect of it has changed (most frequently, the rate has been changed). Paused - The current delivery has been paused. FinishedRunning - The delivery of the item has finished (most frequently, the bag containing the compound is empty). Stopped - The delivery of the item been terminated by the caregiver. Rewritten - Incorrect information was input, and so the information in this row was rewritten (these rows are primarily useful for auditing purposes - the rates/amounts described were not delivered and so should not be used if determining what compounds a patient has received). Flushed - A line was flushed."},{"column_name":"ordercategoryname","description":"These columns provide higher level information about the order the medication/solution is a part of. Categories represent the type of administration, while the ordercomponenttypedescription describes the role of the substance in the solution (i.e. main order parameter, additive, or mixed solution)"},{"column_name":"secondaryordercategoryname","description":"These columns provide higher level information about the order the medication/solution is a part of. Categories represent the type of administration, while the ordercomponenttypedescription describes the role of the substance in the solution (i.e. main order parameter, additive, or mixed solution)"},{"column_name":"ordercomponenttypedescription","description":"These columns provide higher level information about the order the medication/solution is a part of. Categories represent the type of administration, while the ordercomponenttypedescription describes the role of the substance in the solution (i.e. main order parameter, additive, or mixed solution)"},{"column_name":"ordercategorydescription","description":"These columns provide higher level information about the order the medication/solution is a part of. Categories represent the type of administration, while the ordercomponenttypedescription describes the role of the substance in the solution (i.e. main order parameter, additive, or mixed solution)"},{"column_name":"patientweight","description":"The patient weight in kilograms."},{"column_name":"totalamount","description":"Intravenous administrations are usually given by hanging a bag of fluid at the bedside for continuous infusion over a certain period of time. These columns list the total amount of the fluid in the bag containing the solution."},{"column_name":"totalamountuom","description":"Intravenous administrations are usually given by hanging a bag of fluid at the bedside for continuous infusion over a certain period of time. These columns list the total amount of the fluid in the bag containing the solution."},{"column_name":"isopenbag","description":"Whether the order was from an open bag."},{"column_name":"continueinnextdept","description":"If the order ended on patient transfer, this field indicates if it continued into the next department (e.g. a floor)."},{"column_name":"originalamount","description":"Drugs are usually mixed within a solution and delivered continuously from the same bag. This column represents the amount of the drug contained in the bag at starttime. For the first infusion of a new bag, originalamount: totalamount. Later on, if the rate is changed, then the amount of the drug in the bag will be lower (as some has been administered to the patient). As a result, originalamount < totalamount, and originalamount will be the amount of drug leftover in the bag at that starttime."},{"column_name":"originalrate","description":"This is the rate that was input by the care provider. Note that this may differ from rate because of various reasons: originalrate was the original planned rate, while the rate column will be the true rate delivered. For example, if a a bag is about to run out and the care giver decides to push the rest of the fluid, then rate > originalrate. However, these two columns are usually the same, but have minor non-clinically significant differences due to rounding error."}],"class":"icu"}
{"file_name":"outputevents","description":"Information regarding patient outputs including urine, drainage, and so on.","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient."},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay"},{"column_name":"stay_id","description":"stay_id is unique to a patient ICU stay."},{"column_name":"caregiver_id","description":"caregiver_id uniquely identifies a single caregiver who documented data in the ICU information system."},{"column_name":"charttime","description":"charttime is the time of an output event."},{"column_name":"storetime","description":"storetime records the time at which an observation was manually input or manually validated by a member of the clinical staff."},{"column_name":"itemid","description":"Identifier for a single measurement type in the database. Each row associated with one itemid (e.g. 212) corresponds to an instantiation of the same measurement (e.g. heart rate)."},{"column_name":"value","description":"value and valueuom list the amount of a substance at the charttime (when the exact start time is unknown, but usually up to an hour before)."},{"column_name":"valueuom","description":"value and valueuom list the amount of a substance at the charttime (when the exact start time is unknown, but usually up to an hour before)."}],"class":"icu"}
{"file_name":"procedureevents","description":"Procedures documented during the ICU stay (e.g. ventilation), though not necessarily conducted within the ICU (e.g. x-ray imaging).","columns":[{"column_name":"subject_id","description":"subject_id is unique to a patient."},{"column_name":"hadm_id","description":"hadm_id is unique to a patient hospital stay."},{"column_name":"stay_id","description":"stay_id is unique to a patient ICU stay."},{"column_name":"caregiver_id","description":"caregiver_id uniquely identifies a single caregiver who documented data in the ICU information system."},{"column_name":"starttime","description":"starttime and endtime record the start and end time of an event."},{"column_name":"endtime","description":"starttime and endtime record the start and end time of an event."},{"column_name":"storetime","description":"storetime specifies the time when the event was recorded in the system."},{"column_name":"itemid","description":"Identifier for a single measurement type in the database. Each row associated with one itemid (e.g. 212) corresponds to a type of measurement (e.g. heart rate). The d_items table may be joined on this field. For any itemid appearing in the procedureevents table, d_items linksto column will have the value ‘procedureevents’."},{"column_name":"value","description":"In the procedureevents table, this identifies the duration of the procedure (if applicable). For example, if querying for itemid 225794 (“Non-invasive Ventilation”), then the value column indicates the duration of ventilation therapy."},{"column_name":"valueuom","description":"The unit of measurement for the value. Most frequently “None” (no value recorded); otherwise one of “day”, “hour”, or “min”. A query for itemiid 225794 (“Non-invasive Ventilation”) returning a value of 461 and valueuom of ‘min’ would correspond to non-invasive ventilation provided for 461 minutes; this value is expected to match the difference between the starttime and endtime fields for the record. A procedure with valueuom equal to “None” corresponds to a procedure which is instantaneous (e.g. intubation, patient transfer) or whose duration is not relevant (e.g. imaging procedures). For these records, there will be a difference of one second between starttime and endtime values."},{"column_name":"location","description":"location and locationcategory provide information about where on the patient’s body the procedure is taking place. For example, the location might be ‘Left Upper Arm’ and the locationcategory might be ‘Invasive Venous’."},{"column_name":"locationcategory","description":"location and locationcategory provide information about where on the patient’s body the procedure is taking place. For example, the location might be ‘Left Upper Arm’ and the locationcategory might be ‘Invasive Venous’."},{"column_name":"orderid","description":"These columns link procedures to specific physician orders. Unlike in the mimic_icu.inputevents table, most procedures in procedureevents are ordered independently.There are a limited number of records for which the same procedure was performed again at a later date under the same original order. When a procedure was repeated under the same original order, the linkorderid field of the record for the later procedure will be set to the orderid field of the earlier record. In all other cases, orderid = linkorderid."},{"column_name":"linkorderid","description":"These columns link procedures to specific physician orders. Unlike in the mimic_icu.inputevents table, most procedures in procedureevents are ordered independently.There are a limited number of records for which the same procedure was performed again at a later date under the same original order. When a procedure was repeated under the same original order, the linkorderid field of the record for the later procedure will be set to the orderid field of the earlier record. In all other cases, orderid = linkorderid."},{"column_name":"ordercategoryname","description":"These columns provide higher level information about the medication/solution order. Categories represent the type of administration."},{"column_name":"ordercategorydescription","description":"These columns provide higher level information about the medication/solution order. Categories represent the type of administration."},{"column_name":"patientweight","description":"The patient weight in kilograms."},{"column_name":"isopenbag","description":"Whether the order was from an open bag."},{"column_name":"continueinnextdept","description":"If the order ended on patient transfer, this field indicates if it continued into the next department (e.g. a floor)."},{"column_name":"statusdescription","description":"statusdescription states the ultimate status of the procedure referred to in the row. The statuses appearing on the procedureevents table are: Paused - The current delivery has been paused. FinishedRunning - The delivery of the item has finished (most frequently, the bag containing the compound is empty). Stopped - The delivery of the item been terminated by the caregiver. Nearly all procedures recorded in procedureevents have a status of FinishedRunning."},{"column_name":"originalamount","description":"These fields are present in the table and never null, but have no clear meaning. In particular, “originalrate” is either 0 or 1 for all records."},{"column_name":"originalrate","description":"These fields are present in the table and never null, but have no clear meaning. In particular, “originalrate” is either 0 or 1 for all records."}],"class":"icu"}
{"file_name": "diagnosis", "description": "The diagnosis table provides billed diagnoses for patients. Diagnoses are determined after discharge from the emergency department.", "columns": [{"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "stay_id", "description": "An identifier which uniquely identifies a single emergency department stay for a single patient."}, {"column_name": "charttime", "description": "The time at which the diagnosis was charted."}, {"column_name": "seq_num", "description": "A pseudo-priority for the diagnosis. A seq_num of 1 usually indicates a \u201cprimary\u201d diagnosis, but accurately assessing the priority for patients with multiple diagnoses is challenging."}, {"column_name": "icd_code", "description": "A coded diagnosis using the International Classification of Diseases (ICD) ontology."}, {"column_name": "icd_version", "description": "The version of the ICD system used; either 9 indicating ICD-9 or 10 indicating ICD-10. The ontologies for these two systems differ, and therefore the meaning of the icd_code will depend on the icd_version."}, {"column_name": "icd_title", "description": "The textual description of the diagnosis."}],"class":"ed"}
{"file_name": "edstays", "description": "The edstays table is the primary tracking table for emergency department visits. It provides the time the patient entered the emergency department and the time they left the emergency department.", "columns": [{"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "hadm_id", "description": "If the patient was admitted to the hospital after their ED stay, hadm_id will contain the hospital identifier (ranges from 2000000 - 2999999). The hadm_id may be used to link the ED stay with the hospitalization in MIMIC-IV. If hadm_id is NULL, the patient was not admitted to the hospital after their ED stay."}, {"column_name": "stay_id", "description": "An identifier which uniquely identifies a single emergency department stay for a single patient."}, {"column_name": "intime", "description": "The admission datetime (intime) and discharge datetime (outtime) of the given emergency department stay."}, {"column_name": "outtime", "description": "The admission datetime (intime) and discharge datetime (outtime) of the given emergency department stay."}, {"column_name": "gender", "description": "The patient\u2019s administrative gender as documented in the hospital system."}, {"column_name": "race", "description": "The patient\u2019s self-reported race. Race is aggregated into higher level categories for very small groups. As of MIMIC-IV-ED v2.1, there were 33 unique categories for race."}, {"column_name": "arrival_transport", "description": "The method through which the individual arrived at the ED. Possible entries is provide below: WALK IN, AMBULANCE, UNKNOWN, OTHER, HELICOPTER."}, {"column_name": "disposition", "description": "The method through which the individual left the ED. Of the non-null methods, the possibilities include: HOME, ADMITTED, TRANSFER, LEFT WITHOUT BEIN SEEN, OTHER, LEFT AGAINST MEDICAL ADVICE, ELOPED, EXPIRED."}],"class":"ed"}
{"file_name": "medrecon", "description": "On admission to the emergency departments, staff will ask the patient what current medications they are taking. This process is called medicine reconciliation, and the medrecon table stores the findings of the care providers.", "columns": [{"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "stay_id", "description": "An identifier which uniquely identifies a single emergency department stay for a single patient."}, {"column_name": "charttime", "description": "The time at which the medicine reconciliation was charted."}, {"column_name": "name", "description": "The name of the medication."}, {"column_name": "gsn", "description": "The Generic Sequence Number (GSN), an ontology for the medication."}, {"column_name": "ndc", "description": "The National Drug Code (ndc) for the medication."}, {"column_name": "etc_rn", "description": "Medications are grouped using a hierarchical ontology known as the Enhanced Therapeutic Class (ETC). As more than one group may be associated with the medication, a sequential integer (etc_rn) was generated to differentiate the groups. There is no meaning to the order of etc_rn. etccode provides the code and etcdescription provides the description of the group."}, {"column_name": "etccode", "description": "Medications are grouped using a hierarchical ontology known as the Enhanced Therapeutic Class (ETC). As more than one group may be associated with the medication, a sequential integer (etc_rn) was generated to differentiate the groups. There is no meaning to the order of etc_rn. etccode provides the code and etcdescription provides the description of the group."}, {"column_name": "etcdescription", "description": "Medications are grouped using a hierarchical ontology known as the Enhanced Therapeutic Class (ETC). As more than one group may be associated with the medication, a sequential integer (etc_rn) was generated to differentiate the groups. There is no meaning to the order of etc_rn. etccode provides the code and etcdescription provides the description of the group."}],"class":"ed"}
{"file_name": "pyxis", "description": "The pyxis table provides information for medicine dispensations made via the Pyxis system.", "columns": [{"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "stay_id", "description": "An identifier which uniquely identifies a single emergency department stay for a single patient."}, {"column_name": "charttime", "description": "The time at which the medication was charted, which is the closest approximation to the time the medication was administered."}, {"column_name": "med_rn", "description": "A row number for the medicine used to group single dispensations."}, {"column_name": "name", "description": "The name of the medicine."}, {"column_name": "gsn", "description": "The Generic Sequence Number (GSN), an ontology which provides a code for each medicine."}, {"column_name": "gsn_rn", "description": "As a medicine may be a member of multiple groups in the GSN ontology, this row number differentiates them. The order of gsn_rn has no meaning."}],"class":"ed"}
{"file_name": "triage", "description": "The triage table contains information about the patient when they were first triaged in the emergency department. Patients are assessed at triage by a single care provider and asked a series of questions to assess their current health status. Their vital signs are measured and a level of acuity is assigned. Based on the level of acuity, the patient either waits in the waiting room for later attention, or is prioritized for immediate care.", "columns": [{"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "stay_id", "description": "An identifier which uniquely identifies a single emergency department stay for a single patient."}, {"column_name": "temperature", "description": "The patient\u2019s temperature in degrees Farenheit. Some temperatures may be incorrectly documented as Celsius."}, {"column_name": "heartrate", "description": "The patient\u2019s heart rate in beats per minute."}, {"column_name": "resprate", "description": "The patient\u2019s respiratory rate in breaths per minute."}, {"column_name": "o2sat", "description": "The patient\u2019s peripheral oxygen saturation as a percentage."}, {"column_name": "sbp", "description": "The patient\u2019s systolic and diastolic blood pressure, respectively, measured in millimitres of mercury (mmHg)."}, {"column_name": "dbp", "description": "The patient\u2019s systolic and diastolic blood pressure, respectively, measured in millimitres of mercury (mmHg)."}, {"column_name": "pain", "description": "The level of pain self-reported by the patient, on a scale of 0-10."}, {"column_name": "acuity", "description": "Emergency Severity Index (ESI) - Triage Levels"}, {"column_name": "acuity", "description": "Emergency Severity Index (ESI) - Triage Levels\nAn order of priority based upon acuity utilizing the Emergency Severity Index (ESI) Five Level triage system. This priority is assigned by a registered nurse. Level 1 is the highest priority, while level 5 is the lowest priority. The levels are:\n\nLevel 1 (Highest Priority)\nWhen a Level 1 condition or patient meets ED Trigger Criteria, the triage process stops, the patient is taken directly to a room and immediate physician intervention is requested.\nPatient conditions which trigger level 1 include: being unresponsive, intubated, apneic, pulseless, requiring a medication/intervention to alter ESI level (e.g., Narcan, Adenosine, Cardioversion), trauma, stroke, or STEMI.\nLevel 2\nWhen a Level 2 condition is identified, the triage nurse notifies the resource nurse and appropriate placement will be determined.\nPatient conditions which trigger level 2 include: high-risk situations, new onset confusion, suicidal/homicidal ideation, lethargy, seizures or disorientation, possible ectopic pregnancy, an immunocompromised patient with a fever, severe pain/distress, or vital sign instability.\nLevel 3\nIncludes patients requiring two or more resources (labs, EKG, x-rays, IV fluids, etc.) with stable vital signs.\nLevel 4\nPatients requiring one resource only (labs, EKG, etc.).\nLevel 5 (Lowest Priority)\nPatients not requiring any resources."}, {"column_name": "chiefcomplaint", "description": "A deidentified free-text description of the patient\u2019s chief complaint."}],"class":"ed"}
{"file_name": "vitalsign", "description": "Patients admitted to the emergency department have routine vital signs taken ever 1-4 hours. These vital signs are stored in the vitalsign table.", "columns": [{"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "stay_id", "description": "An identifier which uniquely identifies a single emergency department stay for a single patient."}, {"column_name": "charttime", "description": "The time at which the vital signs were charted."}, {"column_name": "temperature", "description": "The patient\u2019s temperature in degrees Farenheit. Some temperatures may be incorrectly documented as Celsius."}, {"column_name": "heartrate", "description": "The patient\u2019s heart rate in beats per minute."}, {"column_name": "resprate", "description": "The patient\u2019s respiratory rate in breaths per minute."}, {"column_name": "o2sat", "description": "The patient\u2019s oxygen saturation measured as a percentage."}, {"column_name": "sbp", "description": "The patient\u2019s systolic (sbp) and diastolic (dbp) blood pressure measured in millimetres of mercury (mmHg)."}, {"column_name": "dbp", "description": "The patient\u2019s systolic (sbp) and diastolic (dbp) blood pressure measured in millimetres of mercury (mmHg)."}, {"column_name": "rhythm", "description": "The patient\u2019s heart rhythm."}, {"column_name": "pain", "description": "The patient\u2019s self-reported level of pain on a scale from 0-10. The pain is documented as free-text and may contain non-numeric entries."}],"class":"ed"}
{"file_name": "discharge", "description": "The discharge table contains discharge summaries for hospitalizations. Discharge summaries are long form narratives which describe the reason for a patient\u2019s admission to the hospital, their hospital course, and any relevant discharge instructions.", "columns": [{"column_name": "note_id", "description": "A unique identifier for the given note. note_id is composed of subject_id, the note_type (always two characters long), and a monotonically increasing integer, note_seq, in the following format: subject_id-note_type-note_seq."}, {"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "hadm_id", "description": "hadm_id is an integer identifier which is unique for each patient hospitalization."}, {"column_name": "note_type", "description": "The type of note recorded in the row. There are two types of note: \u2018DS\u2019 - discharge summary\uff0c \u2018AD\u2019 - discharge summary addendum"}, {"column_name": "note_seq", "description": "A monotonically increasing integer which chronologically sorts the notes within note_type categories. That is, notes can be ordered sequentially by note_seq."}, {"column_name": "charttime", "description": "The time at which the note was charted - this is usually the most relevant time for interpreting the content of the note, but it is not necessarily when the note was fully written."}, {"column_name": "storetime", "description": "The time at which the note was stored in the database. This is usually when the note was completed and signed."}],"class":"note"}
{"file_name": "discharge_detail", "description": "Additional information associated with notes documented in the discharge table. Can be linked to the discharge table using note_id.", "columns": [{"column_name": "note_id", "description": "A unique identifier for the given note. note_id is composed of subject_id, the note_type (always two characters long), and a monotonically increasing integer, note_seq, in the following format: subject_id-note_type-note_seq."}, {"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "field_name", "description": "Each row provides detail regarding a particular aspect of a note. field_name is the name given to that aspect. As of MIMIC-IV, v1.0, possible values include: author."}, {"column_name": "field_value", "description": "field_value is the value associated with the given field_name, associated with a note. For example, for the field_name of \u2018author\u2019, the field_value column contains the author of the note."}],"class":"note"}
{"file_name": "radiology", "description": "The radiology table contains free-text radiology reports associated with radiography imaging. Radiology reports cover a variety of imaging modalities: x-ray, computed tomography, magnetic resonance imaging, ultrasound, and so on. Free-text radiology reports are semi-structured and usually follow a consistent template for a given imaging protocol.", "columns": [{"column_name": "note_id", "description": "A unique identifier for the given note. note_id is composed of subject_id, the note_type (always two characters long), and a monotonically increasing integer, note_seq, in the following format: subject_id-note_type-note_seq."}, {"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "hadm_id", "description": "hadm_id is an integer identifier which is unique for each patient hospitalization."}, {"column_name": "note_type", "description": "The type of note recorded in the row. There are two types of note: \u2018RR\u2019 - radiology report,  \u2018AR\u2019 - radiology report addendum"}, {"column_name": "note_seq", "description": "A monotonically increasing integer which chronologically sorts the notes within note_type categories. That is, notes can be ordered sequentially by note_seq."}, {"column_name": "charttime", "description": "The time at which the note was charted - this is usually the most relevant time for interpreting the content of the note, but it is not necessarily when the note was fully written."}, {"column_name": "storetime", "description": "The time at which the note was stored in the database. This is usually when the note was completed and signed."}],"class":"note"}
{"file_name": "radiology_detail", "description": "Additional information associated with notes documented in the radiology table. Can be linked to the radiology table using note_id.", "columns": [{"column_name": "note_id", "description": "A unique identifier for the given note. note_id is composed of subject_id, the note_type (always two characters long), and a monotonically increasing integer, note_seq, in the following format: subject_id-note_type-note_seq."}, {"column_name": "subject_id", "description": "subject_id is a unique identifier which specifies an individual patient. Any rows associated with a single subject_id pertain to the same individual."}, {"column_name": "field_name", "description": "Each row provides detail regarding a particular aspect of a note. field_name is the name given to that aspect. As of MIMIC-IV, v1.0, possible values include: addendum_note_id, parent_note_id, cpt_code, exam_code, exam_name."}, {"column_name": "field_value", "description": "field_value is the value associated with the given field_name, associated with a note. For example, for the field_name of \u2018author\u2019, the field_value column contains the author of the note."}],"class":"note"}