Professional Documents
Culture Documents
CSoft and CASE Database Repair Manual 2060290-088 Rev A
CSoft and CASE Database Repair Manual 2060290-088 Rev A
CASE / CardioSoft / CS
Version 6.7
2060290-088 Revision A
NOTE: The information in this manual only applies to the CASE / CardioSoft / CS Version 6.7. Due to conti-
nuing product innovation, specifications in this manual are subject to change without notice.
CASE, MAC, MARS, and MUSE are trademarks owned by GE Medical Systems Information Technologies
GmbH, a General Electric Company going to market as GE Healthcare.
1.3 General
The Database Repair Tool can be used for all CASE, CardioSoft and CS
versions up toV6.7 and for the examination files from all CardioSys versions.
There is no installation program. The program file CARD_REP.EXE must be
copied manually to the directory where CARDIO is installed (Program Install
Directory). There is a choice between English or German user interface
language.
The database can be repaired, because CARDIO stores the patient data in the
header of the examination files. So with each examination file that can be
successfully read from the disk, the appropriate patient and examination records
can be stored in the files PATIENT.BTR and EXAMINA.BTR.
REPAIR supports the following modalities.
Exercise Test, Resting ECG, Ambulatory Blood Pressure, Spirometry, Archived
Patient Records. The modalities from CardioSys up to V4.2 like Exercise Test,
Repair workflow
Each examination is stored in a different file. This file contains the complete data
testa and also the patient demographics. To have fast access to the patient examina-
tions, there are 2 index files. These files are the patient database (PATIENT.BTR)
and the examination database (EXAMINA.BTR). The repair works as follows:
RC000001.300
CU000001.444
CU000002.300
CU000003.777
PATIENT.BTR
P6765655 Lewis 2
P1111111 Brown 3
P2222222 Smith 4
EXAMINA.BTR
1.6 Settings
1. Control the Patient data with a dialog box that displays the data from the
database and the patient data coming from the examination file.
2. Always use the patient data from the examination file.
3. Always retain the patient data found in the database.
4. Use the data from the database and update empty fields with valid entries from
the examination file.
1. Ignore the examination: The examination file shall not be copied to the repair
directory.
2. Generate a new key and store the examination:
The seconds of the recording time shall be incremented and a new attempt is
made with the modified key.
This possibility should be used with great care, because when REPAIR is
executed several times with the same examination files, several entries will be
found in the database for the same test.
It is also possible to rebuild the whole Patient ID system by using random numbers
or by using some characters from the patient's Last Name, First Name and the Date
of birth.
Patient Filter
It is possible to set a filter for the patient‘s Last Name and Patient ID, so only
patients / examinations matching this filter shall be stored in the new database. The
filter specification can also include wildcards (* ?). Examples:
The specification for searching can also be extended by the property Match case.
You can continue working with the repaired database by choosing one of the follow-
ing options:
Copy the files USERS.BTR and the Configured Report Templates (directory:
NARRATIV) and the .ini files from the database master directory to the repair
directory: (button: Users/Conf. Reports…)
Delete the database master directory. Rename or copy the repair directory to the
database master directory.
1.8 Specialities
1.8.1 Merging data
With REPAIR, it is also possible to merge the patient data and examination data
stored in different directories into one database:
1. Decide which database to use as the base and copy the whole directory into a
repair directory (C:\Card_R0, ... C:\Card_R9 )
2. Select the directories of the files where the examinations are stored that should
be merged.
3. Start Repair and the selected examinations will be merged to the repair
directory.
However, the device where the examinations are stored must be writeable, because
during the repair procedure the header of each examination file will be changed and
the file will be renamed. The examination files will not be copied to the repair direc-
tory.
That is why REPAIR assumes that the full disclosure files are stored in the directory
named ..\ONLINE which exists in parallel with the examinations. So when REPAIR
does not find such a directory, no full disclosure file will be available for these
examinations.
Modalities for which full disclosure ECGs may exist are Exercise Test, STAT ECG,
Right-Heart Cath and Ergospirometry.
Example: If you want to repair Exercise Tests, where the examinations are stored in
the directory d:\exercise, make sure that the corresponding full disclosure files are
stored in d:\online
English
German
PatNameFormat1
PatNameFormat1=1
If the length of the patient name is 2 characters: A point shall be insert after
characters
If the length of the patient name is 3 characters and the second character is
a '.' '-' ',' :
A point shall be set at the second and fourth positions.
Example:
AN --> A.N.
U,G --> U.G.
NOTE
This was implemented at the request of a customer who wanted to obtain a
uniform patient ID.
PatIdFormat1
C-syntax like format string used to format numeric patient IDs
Example: PatIdFormat1="%06d"
Example: PatIdFormat1="%d"
PatIdFormat3
PatIdFormat3=1
Uses acquisition date and file extension to generate the Patient ID, if the items
Patient ID, Last Name, First Name coming from the examination file are empty and
the acquisition date is valid.
PatIdFormat3=2
Generates a random Patient ID, if the items Patient ID, Last Name, First Name com-
ing from the examination file are empty and the acquisition date is valid.
PatIdCarddas
PatIdCarddas=1
NOTE
This was implemented at the request of a customer who changed the Patient ID
format in the EMR system and so could no longer view the tests stored in
CardioSoft, via the GDT interface.
PatIdRefList
This function is helpful to transform Patient IDs to a new Patient ID system.
Old and new Patient IDs will be read from a reference file.
The reference file is a text file.
Old and new Patient IDs need to be separated by a special character (Default =
TAB)
Example:
www.gehealthcare.com