FAQ
Welcome to the Frequently Asked Questions (FAQ page). Below, we have tried to answer the most common questions visitors to this our Web site may have. If you find that your question is not answered on this page, please email us at nathanpate @ cardiobase.com
Can we print barcodes in Cardiobase?
Yes, it requires a suitable Code 3 of 9 font installed and a modification to the report pipelines. Please request a user guide from us.
We have a large SQL Server log file. Can it be reduced in size?
It is possible to run some simple steps in Query Analyzer to shrink the SQL Server log file. Please contact us at the above e-mail address and we will send you a user guide for this process.
What database options do we have?
Cardiobase is designed for either Firebird or Microsoft SQL Server. Firebird is an open source project so no additional licensing is required. With SQL server, relevant licensing is required. Most clients who select SQL server would have a site license in place.
Database options:
Firebird 1.5
SQL Server 2000
SQL Server 2005
File Storage Specifications
Cardiobase is a true 32bit Windows based relational database system and stores information in the industrial strength Firebird™ Client-Server SQL format or MS SQL Server. This allows, where authorized, third party reporting tools to query Cardiobase as well as allowing exchange of information with other institutions, database systems or medical equipment. We support HL7 as the optimal method for interfacing.
Images and Image Capture
Image capture is available from any other Windows based system that can also run Cardiobase concurrently. Image quality can be as high a quality as the monitor itself can display. Images are stored as jpeg format.
Cardiobase can be set up to automatically load images from systems such as the GE Muse and other mass storage systems. This is an efficient and practical way to load images such as ECGs, Exercise ECGs etc without having to go to a second program. See our interfaces section.
Security
Password access is provided by network software at PC level and stratified access levels within Cardiobase itself. The Firebird back-end database has extremely tight security.
Hardware and Network Requirements
Cardiobase operates on year 2000 compliant IBM compatible personal computers and Local Area Networks (LANs).
File server (Pentium 4 with 2 Gigabytes RAM recommended or better) with a suitable hard disk (e.g. 27gigabtye) to cater for expected volumes and other requirements. As a guide, Cardiobase data files require approximately one megabyte per 1000 records, excluding any images stored.
100 megabit network cards.
Recommended cabling is CAT 5 UTP.
Current Y2K compliant Windows XP for workstations, Windows Server 2003 with IIS
Back Up and Restoration Processes
Firebird has a built-in backup and restore facility to generate nightly Cardiobase back-ups. A suitable back up procedure is strongly recommended to store these Cardiobase-backup files. This is necessary with any system storing important information. Procedures for safe recovery should be tested before needed. Magnus Medical Software will be happy to advise, should you need assistance.
How do I remove unwanted words from the spell checker?
Removing unwanted words from the spell check dictionary
Speed issue with mix of Windows XP and early Netware server (Netware 5.1 or earlier).
Slow Cardiobase load up times where reported in July 2006 when workstations were upgraded to Windows XP from Windows 98. A Netware 5.1 application server was in use. It was found that the cause was an issue with ‘Opportunistic Locking’. This was resolved by moving to a later version Netware.
|
