Adult Cardiac Database

The EACTS Adult Cardiac Database is a collaborative registry of cardiac surgical data from units across Europe. Since 2015, each participating unit has submitted a pre-defined dataset which has now been uploaded into this single central tool.

The aim of this project is to help produce evidence based guidelines to improve pre and post-operative care and allow a benchmarking platform for this specialty across Europe.

To request access to the EACTS demo version of the database, please click here.

Why join the Adult Cardiac Database?

EACTS encourages members to get involved with the QUIP – ACD, as your support will lead to more quality improvement projects and will increase the difference we can make to our patients.

Benchmarking Outcomes

The QUIP benchmarking tool makes use of anonymised data of surgical interventions, representing baseline data and outcomes of interventions from a given year. The benchmarking tool is accessible for a surgeon to recognise the data and outcomes from their hospital, enabling them to draw comparable data analysis with other hospitals anonymously.

Clinical Decision Guide

Because of the extremely broad spectrum of surgical interventions it will be possible to compare data of a specific patient in a participating hospital with similar cases in the database and their outcomes.

Standard and Bespoke Reports

Standard reports are reports produced at certain time intervals (eg annual reports). Any participant can approach the committee with questions concerning specific data analysis which require the anonymous use of data in the ACD.

Participation

Participation is easy. Please follow these 3 steps:

Step 1. To sign up please read the EACTS QUIP Charter carefully, and sign the Registration Form and return to Quip@Eacts.co.uk.

Step 2. The QUIP team at University Hospital Birmingham will contact you or your designated data manager to request your data fields (not the data itself) to map with the QUIP database. You or your data manager will then receive login details to access the QUIP database.

Step 3. You or your data manager will then upload the data via the QUIP tool. This upload is usually completed within minutes.

Adult Cardiac Database Video

adult-cardiac-database

Technical FAQs on the Adult Cardiac Database

How often should the data be uploaded?

We encourage centres to keep up to date with data uploads. Depending on the resources avaible at the centre, the data should be uploaded quaterly, every 6 months or yearly.

What is our hospital code?

The QUIP team will assign this to your hospital.

Should I submit data or any other patient level information to QUIP via email?

No. This would breach our data governance contract – patient level data via email is not secure. Please use the secure FTP link provided by our technical team to transfer any patient level data.

I want to view mortality and reoperations by volume, not rate – how do I do this on the tool?

Hover over any bars or points on any graph to view additional data, including mortality and reoperations by volume.

I submitted a yes/no field for EuroSCORE operation urgency, why is this field red on the data completeness page?

Yes/no fields are not always compatible with the QUIP data specification (downloadable on the tool) – in this case, we require operation urgency to detail whether it was elective, an emergency, urgent or salvage. This is to provide analysis with as high a level of accuracy as possible, and for the future purpose of providing analysis by EuroSCORE II and STS score.

Will units be able to see other units data?

A unit will only be able to see pseudonymised aggregate level data from other units.

At what levels will unit's be able to export/view data? When will this be available?

At the highest level. Units will only be able to download high level graphics for other units.
Feedback reports will be sent to all units with their own data in.

Who will be responsible for ensuring local legislation around publication of data followed, e.g. small number policies

The unit will be responsible for this.

Who decides who has access? Will this apply to aggregate data as well? How will this process be standardised?

The unit will be responsible for this.