BCIS PCI Access data collection tool (database)

Current PCI Database

A database designed to capture details about percutaneous coronary intervention procedures.

This PCI Database is designed to capture details about percutaneous coronary interventional procedures. Procedure reports and GP letters can be created, the data can be analysed within the database, or exported for analysis. This database is designed to collect the dataset agreed by the British Cardiovascular Intervention Society (BCIS) / National Institute for Cardiovascular Outcomes Research (NICOR). It can create the comma separated values (csv) file required for upload data to the Lotus Notes application on your local computer prior encryption and export to the CCAD servers. I have written the database in Access 2002.  Version 18.1 fixes some bugs in Version 18.0 (all other files are unchanged)

 

May 2019 Menu Options update

To incorporate the new library options introduced in May 2019, 4 tables in the database need to be replaced with new versions.  Instructions to do this are in this file.

The file containing those tables can be downloaded at this link (it will need to be unzipped once downloaded) BCIS database updated tables

 

April 2018 update

Version 18.3

The latest version of the database below is version 18.3.  I suggest that anyone who wants to start from scratch using this database starts with version 18.3.  The three files required are available for download here:

  1. PCI Database 18.3 for distribution COMPLETE
  2. Mousehook dll
  3. Release Notes for version 18.x

 

The latest PCI database that can be updated from previous versions is:
Version 17.1 (2016)
Compatible with BCIS-NICOR Dataset Version 5.6.x

 

This database is not locked so the code can be explored and modified if necessary (see Release Notes ‘getting inside the database’). You can ask your IT department to set up a link between this database and your local hospital Patient Administration System, so that patient demographics, NHS numbers etc. do not have to be entered manually. A link to the lab results server is also very helpful.

 

The database is designed so that most of the data is entered during and at the end of a PCI procedure, and a procedure report can be printed for the patient notes at that stage. A final set of data is entered after patient discharge.

 

The data can be analysed using the queries I have written, and in addition the full dataset (excluding sub-tables) can be exported to Microsoft Excel to be analysed elsewhere. In addition once the data are uploaded to the Lotus Notes application, all the Lotus analysis tools are also available.

 

The database is designed to run in versions of Access up to 2007. It will also run on newer versions of Access (e.g. 2010 and in Windows 7), but if you may get error messages you will need to apply the fix in this link – running database in Access 2010 and Windows 7.

 

To use the database you need to down load 3 files:
1. PCI database 17.1 for distribution COMPLETEb.mdb
2. C9Z_MouseHook.dll
3. Release notes for version 17.0

 

More information on current and previous datasets, and the detailed version histories are available on the BCIS-CCAD Datasets and History Page.

 

To Update from Version 16 to Version 17:

If you are already using version 16 of my database, then you can update it to version 17.0, retaining all your original data, by using the following two files:

1. Instructions to upgrade PCI Database from version 16 to 17
2. PCI database 17.0 for distribution CARRIERb.mdb

 

02-01-2014: Patch for Version 17.0
The versions above are fixed, but if you have downloaded database versions whose names are not appended with a ‘b’, then you need to apply this fix for the export routine.
1. Explanation
2. Export repair

 

20-01-2016: Patch for version 17.0b
The full version 17.1 above is fixed. If however you are using version 17.0 or 17.0b, then you need to apply this patch to correct an error with the circulatory support export process.
1. Explanation and instructions
2. Update file (circsupportupdate)

 

By Peter F Ludman, BCIS Audit Lead

Mechanisms for Collection of PCI Data

How local units can collect the national audit data.

Mechanisms for Collection

BCIS-CCAD datasets and history

BCIS-CCAD datasets and history