The Cardiac Analytics and Innovation (CardiacAI) project was established to link de-identified healthcare data in a secure environment so that researchers can study the care of people with cardiovascular disease whilst also protecting the privacy of the individuals contained within the data.
The data collection as described below contains 33 tables with 600+ fields in total. These may be numeric keys that can be used to identify events that occurred as part of a single hospital admission/visit or instance of a clinical event (e.g. a surgery). Alternatively, they may be numeric or categorical data fields describing the clinical event (e.g. type of anaesthesia used in a surgery). The data collection also contains numeric keys that can be linked to de-identified free text fields (clinical notes). These free text fields are stored in a de-identified and encrypted form separate from the main data collection and require researchers meet strong project applicability standards for access.
Click on a table name below for more information about the contents of that table including the table specific fields.
Some tables (Vital Signs, Pathology and Documents) have measurements (e.g. pulse rate, Hb) or document types (discharge form) that are represented by a code. The description of these codes can be found in the Concepts tables.
|
Table name
|
Table description
|
|---|---|
|
The PATIENT table contains demographic information for each patient.
|
|
|
The ENCOUNTER table contains information regarding an inpatient visit.
|
|
|
The TRIAGE table contains a information extracted from the triage report completed on presentation to the emergency department.
|
|
|
The WARD_MOVEMENT table contains information relating to ward admission, transfer and discharge during a patient’s encounter.
|
|
|
The DIAGNOSIS table contains a list of the diagnoses associated with a patient’s encounter.
|
|
|
The PROBLEM table contains diagnoses and other conditions that are associated with the patient.
|
|
| FAMILY_HISTORY |
The FAMILY HISTORY table contains information recorded in EMR about the patient’s family medical history
|
| The SOCIAL_HISTORY table contains information recorded in EMR about the patient’s social determinants of health | |
|
The ALLERGY table contains all allergies that are associated with the patient.
|
|
| The PROCEDURE table contains procedure codes that were recorded in the CERNER procedure table for an encounter. | |
|
The SURGERY table contains information relating to a surgical case completed by the theatre nurses.
|
|
|
The OPERATION_REPORT table contains information from the operation reports written by the surgeon.
|
|
|
The OPERATION_REPORT_CODE table contains Medical Benefit Scheme (MBS) procedure codes that were recorded by the proceduralist in the operation report.
|
|
|
The OPERATION_REPORT_TEXT table contains the de-identified free-text information recorded by the proceduralist in the operation report. This table requires special permission from the CardiacAI Data Governance Committee to access.
|
|
|
The IMPLANT table contains information relating to the devices implanted during the operation.
|
|
|
The MEDICATION_ORDER table contains information relating to inpatient or admission/discharge (outpatient) medication orders.
|
|
|
The MEDICATION_ADMINISTRATION table contains information relating to the administration of medications.
|
|
|
The MEDICATION_ORDER_RECONCILIATION table contains information relating to medication reconcilliation events.
|
|
|
The BLOOD_TRANSFUSION table contains information relating to the administration of a blood product.
|
|
|
The BLOOD_PRODUCT table contains information relating to a blood product that was administered.
|
|
|
The PATHOLOGY table contains information relating to pathology order and results. Details of the type of pathology test can be found in the measurement concepts table.
|
|
|
The MICROBIOLOGY table contains information relating to urine, blood or sputum culture test results.
|
|
|
The IMAGING table contains information about medical imaging orders and the time of subsequent reports. It does not contain medical images or report text.
|
|
|
The VITAL_SIGN table contains information related to vital sign measurement. Details of the type of vital sign measurement can be found in the measurement concepts table.
|
|
|
The DOCUMENT table contains information relating to clinical documents. Details of the clinical document type can be found in the Document Concepts table.
|
|
| DOCUMENT_TEXT | The DOCUMENT_TEXT table contains the de-identified free-text from the clinical documents. This table requires special permission from the CardiacAI Data Governance Committee to access. |
| CHEREL_PATIENT_LINK | The CHEREL_PATIENT_LINK table contains cleaned links between the hospital EMR Patient_ID and the PPN of the NSW Admitted Patient Data Collection (APDC), NSW Emergency Department Data Collection (EDDC), NSW Registry of Births Deaths and Marriages (RBDM) death registrations and the Cause of Death Unit Record File (COD-URF) datasets. This table can be used to find the linked data from these datasets for each individual in the hospital EMR data. More information about these datasets can be found here. |
| CHEREL_ENCOUNTER_LINK | The CHEREL_ENCOUNTER_LINK table contains cleaned links between the hospital EMR Encounter_ID and the APDC_Project_Recnum of each episode the APDC dataset. This table can be used to find each EMR encounter’s associated APDC record. More information about this dataset can be found here. |
| APDC | The APDC table contains the cleaned, linked data from the NSW Admitted Patient Data Collection (APDC). More information about this dataset can be found here. |
| APDC_CARDIAC_FLAG | The APDC_CARDIAC_FLAG table contains flags that indicate if the APDC episode has a cardiac diagnosis or procedure code |
| EDDC | The EDDC table contains the cleaned, linked data from the NSW Emergency Department Data Collection (EDDC). More information about this dataset can be found here. |
| DEATHS | The DEATHS table contains the cleaned, linked death records for individuals in the CardiacAI dataset. Dates of death are derived by cross-checking dates across the EMR, APDC, EDDC and RBDM datasets. More information about these datasets can be found here. |
| COD | The COD table contains linked cause-of-death records for individuals in the CardiacAI dataset from the NSW Cause Of Death – Unit Record File (COD-URF) dataset. More information about this dataset can be found here. |