Skip to main content
SpringerLink
Log in

Data Base Management in Interventional Electrophysiology—the Relational Advantage

  • Published:
Journal of Interventional Cardiac Electrophysiology Aims and scope Submit manuscript

Abstract

A relational database was designed to facilitate patient management and storage of complex electrophysiologic data of patients undergoing radiofrequency catheter ablation. The database has to deal with multiple data entries per patient record like radiofrequency current applications and catheters. Background. Due to the complexity of catheter mapping and ablation therapy, the investigators have to handle various data types. Contradictory to a flat-file database, a relational structured database is not limited to a “single record structure”. Implementation. The designed database is built on the relational database programming environment 4th Dimension (ACI). It is implemented on an Apple Macintosh computer system. The relational structure consists of 13 data files and enables an unlimited data entry of multiple items per data field: In 1288 patients 10308 radiofrequency current applications were applied for ablation therapy and 4798 diagnostic or therapeutic catheters were used.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  1. Scheinman MM. Catheter ablation for patients with cardiac arrhythmias. PACE 1986;9:551-564.

    Google Scholar 

  2. Adams DE. Setting up the laboratory for ablation. In: Zipes DP, ed. Catheter Ablation of Arrhythmias. Armonk, NY: Futura Publishing, 1994:81-104.

    Google Scholar 

  3. Harroff AL, France MA, Hayes JR. Guidelines for creating a simple database. M.D. Computing 1993;10(6):478-483.

    Google Scholar 

  4. Codd EF. A relational model of data for large shared data banks. Comm ACM 1970;13(6):377-387.

    Google Scholar 

  5. Date CJ. Many happy returns! (the 25th anniversary of the relational database model). Database Programming & Design 1994;7(9):19-23.

    Google Scholar 

  6. Date CJ, McGoveran D. Updating joins and other views. Database Programming & Design 1994;7(8):43-49.

    Google Scholar 

  7. McGoveran D. Nothing from nothing part III: Can't lose what you never had. Database Programming & Design 1994;7(2):42-48.

    Google Scholar 

  8. McGoveran D. Nothing from nothing part IV: It's in the way that you use it. Database Programming & Design 1994; 7(6):54-63.

    Google Scholar 

  9. McGoveran D. Nothing from nothing (or, What's logic got to do with it?). Database Programming & Design 1993;6(12): 32-41.

    Google Scholar 

  10. Zloof MM. Query-by-example: A data base language. IBM Systems J 1977;16(4):324-343.

    Google Scholar 

  11. Date CJ. How SQL missed the boat: An assessment of SQL from a relational perspective. Database Programming & Design 1993;6(9):19-23.

    Google Scholar 

  12. Soffer LJ, Wolfenson LB, Sivakoff MC. Clinician use of a pediatric cardiology database on a microcomputer. Computers in Biomed Res 1985;18(6):576-586.

    Google Scholar 

  13. Pinciroli F, Combi C, Pozzi G, Rossi R. MS2/Cardio: Towards a multi-service medical software for cardiology. Methods of Information in Medicine 1992;31(1):18-27.

    Google Scholar 

  14. Jasinski PJ. Data systems in cardiological departments: An overview of the literature. Medical Informatics 1985;10(3): 267-275.

    Google Scholar 

  15. Frye RL. The national ACC database (news). J Am Coll Cardiol 1991;17(6):1448-1449.

    Google Scholar 

  16. Kuck KH, Schlueter M. Radiofrequency catheter ablation of accessory pathways. PACE Pacing & Clin Electrophysiol 1992;15(9):1380-1386.

    Google Scholar 

  17. Perlman G. nside 4th Dimension. SYBEX, 1993;4-10.

  18. Lorie RA. Supporting complex objects in a relational system for engineering databases. In: Kim W, ed. Query Processing in Database Systems. Springer, 1985;145-155.

  19. Scheck HJ, Scholl MH. The relational model with relation-value attributes. Information Systems 1986;11(2):137-147.

    Google Scholar 

  20. Date CJ. Oh oh relational: Toward an OO/relational rapprochement (object-oriented and relational programming technologies). Database Programming & Design 1994;7(10): 23-27.

    Google Scholar 

  21. Gallaire H. Logic and databases: A deductive approach. ACM Computing Surveys 1984;16(2):153-185.

    Google Scholar 

  22. Swartout WR. Explaining and justifying expert consulting programs. In: Reggia JA, Thurim S, eds. Computer-Assisted Medical Decision Making. Springer, 1985;254-271.

  23. Schildt H. Expert systems. ed. In: Artificial Intelligence using C. New York: Osborne/McGraw-Hill, Berkley, CA 1987;71-116.

    Google Scholar 

  24. Greer T. In: Understanding Intranets. Microsoft Press, 1997;1-61.

Download references

Author information

Authors and Affiliations

  1. German Heart Center and I. Medical Department, TU, Munich

    Michael A. E. Schneider & Claus Schmitt

  2. St. Georg Hospital, Hamburg, Germany

    Jürgen Siebels

Authors
  1. Michael A. E. Schneider
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Jürgen Siebels
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Claus Schmitt
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

About this article

Cite this article

Schneider, M.A.E., Siebels, J. & Schmitt, C. Data Base Management in Interventional Electrophysiology—the Relational Advantage. J Interv Card Electrophysiol 2, 333–341 (1998). https://doi.org/10.1023/A:1009796101399

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1009796101399

Search

Navigation