2096198-014 CASE CardioSoft Reimbursement V7.0

GE Healthcare
CASE / CardioSoft V7.0

BDT/GDT Interface Specification
Medical Reimbursement Program
2096198-014 Revision C
CASE / CardioSoft V7.0

BDT/GDT Interface Specification
English
© 2018 General Electric Company.
All Rights Reserved.
Publication Information
This document describes version 7.0 of CASE/CardioSoft , also referred to as the “product”. It does not apply to earlier product versions. Due
to continuing product innovation, specifications in this document are subject to change without notice.
MUSE, MARS, CASE and CardioSoft are trademarks owned by GE Medical Systems Information Technologies, Inc., a General Electric
Company going to market as GE Healthcare. All other trademarks contained herein are the property of their respective owners.
NOTE:
Illustrations in this document are provided as examples only. Depending on system configuration, screens in the document may differ
from the screens on your system. Patient names and data are fictitious. Any similarity to actual persons is coincidental.
The document part number and revision are on each page of the document. The revision identifies the document’s update level. The
revision history of this document is summarized in the following table.
Revision Date Comment
A 20 March 2018 Initial Release
B 21 April 2018 Customer Release
C 18 October ATOM release
To access other GE Healthcare Diagnostic Cardiology documents, go to the Common Documentation Library (CDL), located at http://
apps.gehealthcare.com/servlet/ClientServlet?REQ=Enter+Documentation+Library , and click Cardiology.
To access Original Equipment Manufacturer (OEM) documents, go to the device manufacturer's website.
Support
GE Healthcare maintains a trained staff of application and technical experts to answer questions and to respond to issues and problems
that may arise during the installation, maintenance, and use of this product.
If you require additional assistance, contact your GE Healthcare representative or GE Healthcare support at one of the following numbers:
• North America: 1-800-558-7044
• Europe: +49 761 45 43 -0
• Asia: +86 21 3877 7888
Training
This document is intended as a supplement to, not a substitute for, thorough product training. If you have not received training on the use
of the product, you should request training assistance from GE Healthcare.
To see available training, go to the GE Healthcare training website (www.gehealthcare.com/training). Select Education > Product
Education-Technical > Diagnostic Cardiology. For more self-paced course offerings, tools, and reference guides you may find useful,
please visit the GE Healthcare Education Store at www.gehealthcare.com/educationstore.
2096198-014 Revision C CASE / CardioSoft V7.0 2

Service Manual Language Information
WARNING This service manual is available in English only.
(EN)
• If a customer's service provider requires a language other than English, it is the
customer's responsibility to provide translation services.
• Do not attempt to service the equipment unless this service manual has been
consulted and is understood.
• Failure to heed this warning may result in injury to the service provider, operator, or
patient, from electric shock, mechanical or other hazards.
ПРЕДУПРЕЖДЕНИЕ Това упътване за работа е налично само на английски език.

(BG)
• Ако доставчикът на услугата на клиента изиска друг език, задължение на клиента
е да осигури превод.
• Не използвайте оборудването, преди да сте се консултирали и разбрали
упътването за работа.
• Неспазването на това предупреждение може да доведе до нараняване на
доставчика на услугата, оператора или пациент в резултат на токов удар или
механична или друга опасност.
警告本维修手册仅提供英文版本。
ZH-CN
• 如果维修服务提供商需要非英文版本，客户需自行提供翻译服务。
• 未详细阅读和完全理解本维修手册之前，不得进行维修。
• 忽略本警告可能对维修人员，操作员或患者造成触电、机械伤害或其他形式的伤
害。
警告本維修手冊只提供英文版。
(ZH-TW)
• 如果客戶的維修人員有英語以外的其他語言版本需求，則由該客戶負責提供翻譯服
務。
• 除非您已詳閱本維修手冊並了解其內容，否則切勿嘗試對本設備進行維修。
• 不重視本警告可能導致維修人員、操作人員或病患因電擊、機械因素或其他因素而
受到傷害。
UPOZORENJE Ove upute za servisiranje dostupne su samo na engleskom jeziku.

(HR)
• Ukoliko korisnički servis zahtijeva neki drugi jezik, korisnikova je odgovornost osigurati
odgovarajući prijevod.
• Nemojte pokušavati servisirati opremu ukoliko niste konzultirali i razumjeli ove upute.
• Nepoštivanje ovog upozorenja može rezultirati ozljedama servisnog osoblja, korisnika
ili pacijenta prouzročenim električnim udarom te mehaničkim ili nekim drugim
opasnostima.
VAROVÁNÍ Tento provozní návod existuje pouze vanglickém jazyce.

(CS)
• Vpřípadě, že externí služba zákazníkům potřebuje návod vjiném jazyce, je zajištění
překladu doodpovídajícího jazyka úkolem zákazníka.
• Nesnažte se oúdržbu tohoto zařízení, aniž byste si přečetli tento provozní návod a
pochopili jeho obsah.
• Vpřípadě nedodržování této varování může dojít kporanění pracovníka prodejního
servisu, obslužného personálu nebo pacientů vlivem elektrického proudu, respektive
vlivem mechanických či jiných rizik.

ADVARSEL Denne servicemanual findes kun på engelsk.

(DA)
• Hvis en kundes tekniker har brug for et andet sprog end engelsk, er det kundens
ansvar at sørge for oversættelse.
• Forsøg ikke at servicere udstyret medmindre denne servicemanual har været
konsulteret og er forstået.
• Manglende overholdelse af denne advarsel kan medføre skade på grund af elektrisk,
mekanisk eller anden fare for teknikeren, operatøren eller patienten.
WAARSCHUWING Deze service manual is alleen in het Engels verkrijgbaar.

(NL)
• Indien het onderhoudspersoneel een andere taal nodig heeft, dan is de klant
verantwoordelijk voor de vertaling ervan.
• Probeer de apparatuur niet te onderhouden voordat deze service manual
geraadpleegd en begrepen is.
• Indien deze waarschuwing niet wordt opgevolgd, zou het onderhoudspersoneel, de
gebruiker of een patiënt gewond kunnen raken als gevolg van een elektrische schok,
mechanische of andere gevaren.
HOIATUS Käesolev teenindusjuhend on saadaval ainult inglise keeles.

(ET)
• Kui klienditeeninduse osutaja nõuab juhendit inglise keelest erinevas keeles, vastutab
klient tõlketeenuse osutamise eest.
• Ärge üritage seadmeid teenindada enne eelnevalt käesoleva teenindusjuhendiga
tutvumist ja sellest aru saamist.
• Käesoleva hoiatuse eiramine võib põhjustada teenuseosutaja, operaatori või patsiendi
vigastamist elektrilöögi, mehaanilise või muu ohu tagajärjel.
VAROITUS Tämä huolto-ohje on saatavilla vain englanniksi.

(FI)
• Jos asiakkaan huoltohenkilöstö vaatii muuta kuin englanninkielistä materiaalia,
tarvittavan käännöksen hankkiminen on asiakkaan vastuulla.
• Älä yritä korjata laitteistoa ennen kuin olet varmasti lukenut ja ymmärtänyt tämän
huolto-ohjeen.
• Mikäli tätä varoitusta ei noudateta, seurauksena voi olla huoltohenkilöstön, laitteiston
käyttäjän tai potilaan vahingoittuminen sähköiskun, mekaanisen vian tai muun
vaaratilanteen vuoksi.
ATTENTION Ce manuel technique n'est disponible qu'en anglais.

(FR)
• Si un service technique client souhaite obtenir ce manuel dans une autre langue que
l'anglais, il devra prendre en charge la traduction et la responsabilité du contenu.
• Ne pas tenter d'intervenir sur les équipements tant que le manuel technique n'a pas
été consulté et compris.
• Le non-respect de cet avertissement peut entraîner chez le technicien, l'opérateur ou
le patient des blessures dues à des dangers électriques, mécaniques ou autres.
4 CASE / CardioSoft V7.0 2096198-014 Revision C

WARNUNG Diese Serviceanleitung ist nur in englischer Sprache verfügbar.

(DE)
• Falls der Kundendienst eine andere Sprache benötigt, muss er für eine entsprechende
Übersetzung sorgen.
• Keine Wartung durchführen, ohne diese Serviceanleitung gelesen und verstanden zu
haben.
• Bei Zuwiderhandlung kann es zu Verletzungen des Kundendiensttechnikers, des
Anwenders oder des Patienten durch Stromschläge, mechanische oder sonstige
Gefahren kommen.
FIGYELMEZTETÉS Ez a szerviz kézikönyv kizárólag angol nyelven érhető el.

(HU)
• Ha a vevő szerviz ellátója angoltól eltérő nyelvre tart igényt, akkor a vevő felelőssége a
fordítás elkészíttetése.
• Ne próbálja elkezdeni használni a berendezést, amíg a szerviz kézikönyvben leírtakat
nem értelmezték és értették meg.
• Ezen figyelmeztetés figyelmen kívül hagyása a szerviz ellátó, a működtető vagy
a páciens áramütés, mechanikai vagy egyéb veszélyhelyzet miatti sérülését
eredményezheti.
AÐVÖRUN Þessi þjónustuhandbók er eingöngu fáanleg á ensku.

(IS)
• Ef að þjónustuveitandi viðskiptamanns þarfnast annars tungumáls en ensku, er það
skylda viðskiptamanns að skaffa tungumálaþjónustu.
• Reynið ekki að afgreiða tækið nema þessi þjónustuhandbók hefur verið skoðuð og
skilin.
• Brot á að sinna þessari aðvörun getur leitt til meiðsla á þjónustuveitanda, stjórnanda
eða sjúklingi frá raflosti, vélrænum eða öðrum áhættum.
PERINGATAN Manual servis ini hanya tersedia dalam bahasa Inggris.

(ID)
• Jika penyedia jasa servis pelanggan memerlukan bahasa lain selain dari Bahasa
Inggris, merupakan tanggung jawab dari penyedia jasa servis tersebut untuk
menyediakan terjemahannya.
• Jangan mencoba melakukan servis terhadap perlengkapan kecuali telah membaca
dan memahami manual servis ini.
• Mengabaikan peringatan ini bisa mengakibatkan cedera pada penyedia servis,
operator, atau pasien, karena terkena kejut listrik, bahaya mekanis atau bahaya
lainnya.
AVVERTENZA Il presente manuale di manutenzione è disponibile soltanto in Inglese.

(IT)
• Se un addetto alla manutenzione richiede il manuale in una lingua diversa, il cliente è
tenuto a provvedere direttamente alla traduzione.
• Si proceda alla manutenzione dell'apparecchiatura solo dopo aver consultato il
presente manuale ed averne compreso il contenuto.
• Il non rispetto della presente avvertenza potrebbe far compiere operazioni da cui
derivino lesioni all'addetto, alla manutenzione, all'utilizzatore ed al paziente per
folgorazione elettrica, per urti meccanici od altri rischi.

警告このサービスマニュアルは英語版しかありません。
(JA)
• サービスを担当される業者が英語以外の言語を要求される場合、翻訳作業はその
業者の責任で行うものとさせていただきます。
• このサービスマニュアルを熟読し、十分に理解をした上で装置のサービスを行っ
てください。
• この警告に従わない場合、サービスを担当される方、操作員あるいは患者が、感
電や機械的又はその他の危険により負傷する可能性があります。
경고 본 서비스 지침서는 영어로만 이용하실 수 있습니다.

(KO)
• 고객의 서비스 제공자가 영어 이외의 언어를 요구할 경우, 번역 서비스를 제공하는
것은 고객의 책임입니다.
• 본 서비스 지침서를 참고했고 이해하지 않는 한은 해당 장비를 수리하려고 시도하지
마십시오.
• 이 경고에 유의하지 않으면 전기 쇼크, 기계상의 혹은 다른 위험으로부터 서비스 제
공자, 운영자 혹은 환자에게 위해를 가할 수 있습니다.
ЕСКЕРТУ Бұл қызмет көрсету бойынша нұсқаулығы тек ағылшын тілінде қолжетімді.
(KK)
• Тұтынушының қызмет провайдері ағылшын тілінен басқа тілдегі нұсқаны талап
етсе, аудару бойынша қызметтерімен қамтамасыз ету тұтынушы жауапкершілігінде
болуы тиіс.
• Бұл қызмет көрсету бойынша нұсқаулығын назарға алып, түсінбегенше, жабдыққа
қызмет көрсетуден бас тартыңыз.
• Бұл ескертуді елемеу қызмет провайдері, оператор немесе емделушінің электр
шогынан, механикалық немесе басқа қауіптер нəтижесінде жарақат алуына əкелуі
мүмкін.
BRĪDINĀJUMS Šī apkalpotāju rokasgrāmata ir pieejama tikai angļu valodā.

(LV)
• Ja apkalpošanas sniedzējam nepieciešama informācija citā, nevis angļu, valodā,
klienta pienākums ir nodrošināt tās tulkošanu.
• Neveiciet aprīkojuma apkopi, neizlasot un nesaprotot apkalpotāju rokasgrāmatu.
• Šī brīdinājuma neievērošana var radīt elektriskās strāvas trieciena, mehānisku vai citu
risku izraisītu traumu apkopes sniedzējam, operatoram vai pacientam.
ĮSPĖJIMAS Šis eksploatavimo vadovas yra prieinamas tik anglų kalba.

(LT)
• Jei kliento paslaugų tiekėjas reikalauja vadovo kita kalba - ne anglų, numatyti vertimo
paslaugas yra kliento atsakomybė.
• Nemėginkite atlikti įrangos techninės priežiūros, nebent atsižvelgėte į šį eksploatavimo
vadovą ir jį supratote.
• Jei neatkreipsite dėmesio į šį perspėjimą, galimi sužalojimai dėl elektros šoko,
mechaninių ar kitų paslaugų tiekėjui, operatoriui ar pacientui.

ADVARSEL Denne servicehåndboken finnes bare på engelsk.

(NO)
• Hvis kundens serviceleverandør trenger et annet språk, er det kundens ansvar å sørge
for oversettelse.
• Ikke forsøk å reparere utstyret uten at denne servicehåndboken er lest og forstått.
• Manglende hensyn til denne advarselen kan føre til at serviceleverandøren,
operatøren eller pasienten skades på grunn av elektrisk støt, mekaniske eller andre
farer.
OSTRZEŻENIE Niniejszy podręcznik serwisowy dostępny jest jedynie w języku angielskim.

(PL)
• Jeśli dostawca usług klienta wymaga języka innego niż angielski, zapewnienie usługi
tłumaczenia jest obowiązkiem klienta.
• Nie należy serwisować wyposażenia bez zapoznania się i zrozumienia niniejszego
podręcznika serwisowego.
• Niezastosowanie się do tego ostrzeżenia może spowodować urazy dostawcy usług,
operatora lub pacjenta w wyniku porażenia elektrycznego, zagrożenia mechanicznego
bądź innego.
AVISO Este manual de assistência técnica só se encontra disponível em inglês.

(PT-BR)
• Se o serviço de assistência técnica do cliente não for GE, e precisar de outro idioma,
será da responsabilidade do cliente fornecer os serviços de tradução.
• Não tente reparar o equipamento sem ter consultado e compreendido este manual de
assistência técnica.
• O não cumprimento deste aviso pode por em perigo a segurança do técnico, operador
ou paciente devido a choques elétricos, mecânicos ou outros.
AVISO Este manual técnico só se encontra disponível em inglês.

(PT-PT)
• Se a assistência técnica do cliente solicitar estes manuais noutro idioma, é da
responsabilidade do cliente fornecer os serviços de tradução.
• Não tente reparar o equipamento sem ter consultado e compreendido este manual
técnico.
• O não cumprimento deste aviso pode provocar lesões ao técnico, ao utilizador ou ao
paciente devido a choques eléctricos, mecânicos ou outros.
AVERTISMENT Acest manual de service este disponibil numai în limba engleză.

(RO)
• Dacă un furnizor de servicii pentru clienţi necesită o altă limbă decât cea engleză, este
de datoria clientului să furnizeze o traducere.
• Nu încercaţi să reparaţi echipamentul decât ulterior consultării şi înţelegerii acestui
manual de service.
• Ignorarea acestui avertisment ar putea duce la rănirea depanatorului, operatorului
sau pacientului în urma pericolelor de electrocutare, mecanice sau de altă natură.

ПРЕДУПРЕЖДЕНИЕ Настоящее руководство по обслуживанию предлагается только на английском языке.

(RU)
• Если сервисному персоналу клиента необходимо руководство не на английском, а
на каком-то другом языке, клиенту следует обеспечить перевод самостоятельно.
• Прежде чем приступать к обслуживанию оборудования, обязательно обратитесь к
настоящему руководству и внимательно изучите изложенные в нем сведения.
• Несоблюдение требований данного предупреждения может привести к тому,
что специалисты по обслуживанию, операторы или пациенты получат удар
электрическим током, механическую травму или другое повреждение.
UPOZORENJE Ovo servisno uputstvo je dostupno samo na engleskom jeziku.

(SR)
• Ako klijentov serviser zahteva neki drugi jezik, klijent je dužan da obezbedi
prevodilačke usluge.
• Ne pokušavajte da opravite uređaj ako niste pročitali i razumeli ovo servisno uputstvo.
• Zanemarivanje ovog upozorenja može dovesti do povređivanja servisera, rukovaoca ili
pacijenta usled strujnog udara, ili mehaničkih i drugih opasnosti.
VAROVANIE Tento návod na obsluhu je k dispozícii len v angličtine.

(SK)
• Ak zákazníkov poskytovateľ služieb vyžaduje iný jazyk ako angličtinu, poskytnutie
prekladateľských služieb je zodpovednosťou zákazníka.
• Nepokúšajte sa o obsluhu zariadenia skôr, ako si neprečítate návod na obsluhu a
neporozumiete mu.
• Zanedbanie tohto varovania môže vyústiť do zranenia poskytovateľa služieb,
obsluhujúcej osoby alebo pacienta elektrickým prúdom, mechanickým alebo iným
nebezpečenstvom.
OPOZORILO Ta servisni priročnik je na voljo samo v angleškem jeziku.

(SL)
• Če ponudnik storitve stranke potrebuje priročnik v drugem jeziku, mora stranka
zagotoviti prevod.
• Ne poskušajte servisirati opreme, če tega priročnika niste v celoti prebrali in razumeli.
• Če tega opozorila ne upoštevate, se lahko zaradi električnega udara, mehanskih ali
drugih nevarnosti poškoduje ponudnik storitev, operater ali bolnik.
ADVERTENCIA Este manual de servicio sólo existe en inglés.

(ES)
• Si el encargado de mantenimiento de un cliente necesita un idioma que no sea el
inglés, el cliente deberá encargarse de la traducción del manual.
• No se deberá dar servicio técnico al equipo, sin haber consultado y comprendido este
manual de servicio.
• La no observancia del presente aviso puede dar lugar a que el proveedor de servicios,
el operador o el paciente sufran lesiones provocadas por causas eléctricas, mecánicas
o de otra naturaleza.

VARNING Den här servicehandboken finns bara tillgänglig på engelska.

(SV)
• Om en kunds servicetekniker har behov av ett annat språk än engelska ansvarar
kunden för att tillhandahålla översättningstjänster.
• Försök inte utföra service på utrustningen om du inte har läst och förstår den här
servicehandboken.
• Om du inte tar hänsyn till den här varningen kan det resultera i skador på
serviceteknikern, operatören eller patienten till följd av elektriska stötar, mekaniska
faror eller andra faror.
UYARI Bu servis klavuzunun sadece İngilizcesi mevcuttur.

(TR)
• Eğer müşteri teknisyeni bu klavuzu İngilizce dşnda bir başka lisandan talep ederse,
bunu tercüme ettirmek müşteriye düşer.
• Servis klavuzunu okuyup anlamadan ekipmanlara müdahale etmeyiniz.
• Bu uyarya uyulmamas, elektrik, mekanik veya diğer tehlikelerden dolay teknisyen,
operatör veya hastann yaralanmasna yol açabilir.
ЗАСТЕРЕЖЕННЯ Дане керівництво з сервісного обслуговування постачається виключно англійською

(UK) мовою.
• Якщо сервісний інженер потребує керівництво іншою мовою, користувач
зобов'язаний забезпечити послуги перекладача.
• Не намагайтеся здійснювати технічне обслуговування даного обладнання, якщо
ви не читали, або не зрозуміли інформацію, надану в керівництві з сервісного
обслуговування.
• Недотримання цього застереження може призвести до травмування сервісного
інженера, користувача даного обладнання або пацієнта внаслідок електричного
шоку, механічного ушкодження або з інших причин невірного обслуговування
обладнання.
CẢNH BÁO Tài Liệu Hướng Dẫn Sửa Chữa chỉ có bản tiếng Anh.
(VI)
• Nếu các đơn vị cung cấp dịch vụ cho khách hàng yêu cầu một ngôn ngữ nào khác tiếng
Anh, thì khách hàng sẽ có trách nhiệm cung cấp các dịch vụ dịch thuật.
• Không được sửa chữa thiết bị trừ khi đã tham khảo và hiểu Tài liệu Hướng dẫn Sửa chữa.
• Không tuân thủ những cảnh báo này có thể dẫn đến các tổn thương cho người thực hiện
sửa chữa, người vận hành hay bệnh nhân, do sốc điện, các rủi ro về cơ khí hay các rủi ro
khác

Contents
Publication Information....................................................................... 2
Service Manual Language Information................................................................ 3
1 General Description........................................................................................ 11
2 BDT Format Interface..................................................................................... 13

General Requirements...................................................................................................................................... 13
Our BDT extensions............................................................................................................................................13
Utilized Sections of the BDT Format.......................................................................................................... 14
Data transmitted from Medical Reimbursement Program to CASE/CardioSoft.................... 17
Calling the CASE/CardioSoft Application..................................................................................................18
Data transmitted from CASE/CardioSoft to Medical Reimbursement Program.................... 20
Special features of CASE/CardioSoft..........................................................................................................22
BDT Examples........................................................................................................................................................24
Character Set........................................................................................................................................................ 26
3 GDT Format Interface.....................................................................................27

General Requirements...................................................................................................................................... 27
Sections of the GDT Format...........................................................................................................................27
Data transmitted from Medical Reimbursement Program to CASE/CardioSoft.................... 34
Calling the CASE/CardioSoft Application..................................................................................................35
Data transmitted from CASE/CardioSoft to Medical Reimbursement Program.................... 37
Special features of CASE/CardioSoft..........................................................................................................38
User definable field identifier........................................................................................................................ 40
GDT Examples....................................................................................................................................................... 41
GDT Version............................................................................................................................................................44
Character Set........................................................................................................................................................ 44
File Reference Field IDs.................................................................................................................................... 44
4 List of Procedure IDs.......................................................................................46

ID List for Resting Spirogram........................................................................................................................ 46
ID List for Resting ECG......................................................................................................................................47
ID List for Stress Test ECG.............................................................................................................................. 48
ID List for Ambulatory Blood Pressure, Holter ECG.............................................................................49
ID List for Ergospirometry............................................................................................................................... 49

1
General Description
This document describes the communication of CASE/CardioSoft with Medical
Reimbursement Programs (MRP) via the BDT/GDT Interface.
The patient is always selected in the Medical Reimbursement Program. The CASE/
CardioSoft application is called automatically when the patient's electronic file
card in the medical reimbursement program is selected. It is not possible to select
another patient in the application. However, the system allows the user to call
other procedures stored for the selected patient (ECG, spirometry, etc.). Patient
data management is done in the medical reimbursement program, whereas the
medical signals (ECG, spirometric data, etc.) are handled in the application. New
procedures are created and existing procedures can be edited via the application.
When the user quits the application, the medical reimbursement program adopts the
most important data (not the signal traces!) of all new and edited procedures (ECG,
spirometry data, etc.) and billing of the medical services rendered can be initiated.
Normal dialog between medical reimbursement program and the CASE/CardioSoft
application to create new procedures:
• Start medical reimbursement program.
• Select patient.
• Display of a menu to select the desired procedure: select one of the medical
procedures: rest ECG, stress test, spirometry; this will activate the application and
display the signal acquisition screen of the selected procedure category.
• Record procedures (ECG, spirogram...) and modifying existing procedures.
• Quit the application.
• Medical reimbursement program automatically adopts the new/modified
procedures.
Normal dialog between medical reimbursement program and the CASE/CardioSoft
application to display existing procedures:
• Start medical reimbursement program.
• Select patient in medical reimbursement program.
• Display of the patient's electronic file card, indicating the existing procedures.
• Activate the application with the data of the selected patient, the procedure
category and the date/time of the procedure by selecting the stored procedure.
• Existing procedures (ECG, spirogram...) are displayed and may be edited.
• Quit the application.

General Description
• Medical reimbursement program automatically adopts the new/modified

procedures
Reference Document Title
[BDT] BDT data record description - interface description for system-independent

data transfer of medical data, Authors: Friedrich Lichtner and Juergen
Sembritzki, V 7/92 dated 22 July 1992
[GDT] GDT data record description - interface description for Connection of

medical devices, Author: Quality group of medical software, Version 2.0 5/98
(June, 1998) ,Version 2.1 5/01 (June, 2001)

2
BDT Format Interface
General Requirements
This document is based on the BDT data record description, version 7/92 [BDT],
worked out by Friedrich Lichtner and Jürgen Sembritzki of the German Central
Institute for Medical Care By Panel Doctors.
Brief summary of the most important features of the BDT format:
The data record comprises the following fields (with field ID):
• Data record ID (8000) e.g. 0020 for data medium header
• Data record length in bytes (8100) of the field Data record ID (incl.) up to the last
field before the next data record ID
• other fields ...
A field comprises the following field sections (with lengths):
• Length (3 byte): computed from the length of the contents + 9
• ID (4 byte): unequivocal field ID (e.g. 8000 data record category)
• Contents: data contents with variable length in IBM DOS character set (not
WINDOWS character set)
• End (2 byte): ASCII value 13 (CR) + ASCII value 10 (LF)
In order to display a field content over several lines, the field is repeated for each line
with the same ID.
Our BDT extensions

Our extensions to the BDT Medical Data Record (6200):
• Add the unit "cm" to the field "patient's height" (3622) in the patient´s demographic
data record (6100).
• Add the unit "kg" to the field "patient's weight" (3622) in the patient´s demographic
data record (6100).
• Add a new field "hospital findings status" with the suggested field ID 8404 and the
following contents (one letter) to the medical data record (6200):

ID Description
N new procedure
B new bronchodilation spirogram
G existing procedure was modified
L existing procedure was deleted
A existing procedure is requested from archive
• The reason for adding the new field "hospital findings status": The hospital findings
status is important for the communication between Medical Reimbursement
Programs and the recording unit. The ID for a new procedure (N) or for a new
bronchodilation spirogram (B) is important for activation of the reimbursement.
The ID for a modified procedure (G) is required for the documentation of the
different procedure categories. The ID for a deleted procedure (L) is required for
the deletion to take effect in the documentation of the medical reimbursement
program. The ID for an archived procedure (A) is used to retrieve an existing
procedure.
Utilized Sections of the BDT Format

The patient´s demographic data record (record ID: 6100) of the BDT format is used for
the patient data.
The medical data record (record ID: 6200) of the BDT format is used for the transfer of
procedures (resting ECG, resting spirogram).
General Points
The record length is checked. The record length is calculated from the field lengths,
beginning with the record ID field and ending with the last field of the record.
None of the unknown fields is evaluated.
To achieve a logical link between the patient data record and medical data record,
the same patient ID (field ID 3600) must be specified. The "patient status" field is not
evaluated and not generated by CASE/CardioSoft.
The field "storage date..." (field ID 6200) always specifies the date the BDT data record
was created, not the date the procedure was recorded.

Utilization of patient demographic data record

(6100)
field ID designation of example of explanation
field content field contents
8000 data record ID 6100 patient´s demographic data
8100 record length 04598
3301 patient's last MAIER

name
3302 patient's first HANS

name
3303 patient's date of 290363 format: DDMMYY If the year has only 2 digits,
birth than 1900 is added to the year. Preferred format:
DDMMYYYY. Additional to this field is the field 3103 with
the format DDMMYYYY from the new BDT accepted
3600 patient ID P875386432
3621 patient's sex 1 1=male 2=female
3622 patient's height 178 unit: cm
3623 patient's weight 78 unit: kg
Utilization of the Medical Data Record (6200)

field ID designation of field example of field explanation
content content
8000 data record ID 6200 medical data record
8100 record length 04598
3600 patient ID P875386432
6200 date medical data record 140292 format: DDMMYY

was stored
8402 device / procedure ID 10 10 = resting spirogram 11 =

resting ECG 12 = exercise ECG 13
= late potentials 16 = ambulatory
blood pressure 21 = right heart
catheterization 23 = Holter ECG

field ID designation of field example of field explanation

content content
8404 hospital findings status N N = new procedure B =

bronchodilation test G = existing
procedure was modified L = existing
procedure was deleted A = procedure
was recalled from archive
8432 procedure date 140292 format: DDMMYY (preferred format:

DDMMYYYY)
8433 procedure time 0930 format: HHMM (preferred format:

HHMMSS)
Example of Resting ECG Data (with field 8402=11)

field designation example of explanation
of field field content
content
8410 test ID RR_D refer to ID list Resting ECG
8411 test RR interval

designator
8420 result 700
8421 unit ms refer to ID list Resting ECG
8410 test ID QRS_D 2nd parameter
8411 test QRS interval

designator
8420 result 120
8421 unit ms
(repeat fields 8410 to 8421 for every parameter of the resting ECG procedure)
8410 test ID INTER refer to ID list Resting ECG
8411 test short-form

designator interpretation
8480 result ST depression
8480 result left axis

deviation
(repeat field 8480 for every line of the short-form interpretation)

Example of Resting Spirogram (with field 8402=10)

field designation example of explanation
of field field content
content
8410 test ID EVC refer to ID list Resting Spirogram
8411 test EVC

designator
8420 result 5.03
8421 unit 1 refer to ID list Resting Spirogram
8460 normal-value 5.64 nominal value for EVC

text
8410 test ID FEVC 2nd value
8411 test FEVC

designator
8420 result 5.03
8421 unit 1
8460 normal-value 5.38

text
(repeat fields 8410 to 8421 for every value of the resting spirogram)
8410 test ID INTER refer to ID list
8411 test short-form

designator interpretation
8480 result ventilation

undisturbed
(repeat field 8480 for every line of the short-form interpretation)
Data transmitted from Medical Reimbursement Program to

CASE/CardioSoft
The medical reimbursement program transfers the following data of the selected
patient to the CASE/CardioSoft application in the form of a control file:
NOTE:
The patient must be clearly identified by the patient ID.
The following data is required:
• patient's last name

• patient's first name
• patient ID
• date of birth
• procedure category (rest ECG, spirogram,...)(ought to be included, but is not
required)
• procedure status (new recording, recording from archive)
• if procedure status = recording from archive: procedure date (format: DDMMYY)
and time (format: HHMM)
• height (in cm), sex (1:male, 2: female). Height and sex ought to be included, but
may also be entered in CardioSoft.
Calling the CASE/CardioSoft Application

Program call command syntax under WINDOWS:
CARDIO AAP <name of control file with directory>
Comments on command syntax:
The identifier AAP (1st parameter) tells the application that it was called from the
medical reimbursement program. The name of the control file (2nd parameter)
containing the patient data must include the directory of the control file. The
application uses this file as the return file. The only purpose of this directory (3rd
parameter) is to serve as a data buffer between medical reimbursement program and
the application. If this directory is accessed by several workstations in the network,
the name of the control file must be unique for every station in the network.
If the directory name includes at least one blank, double quotes must be used for
correct usage (e.g. C:\CARDIO\CARDIO.EXE AAP “C:\NEW DATA\ P00789.BDT”).
Special feature for the medical reimbursement program: When starting the medical
reimbursement program, this directory must be searched for procedures which
have as yet not been accepted, and the procedures carried out must be accepted
by the medical reimbursement program. This situation may occur if the computer is
switched off after a recording in CASE/CardioSoft.
Example:
C:\CARDIO\CARDIO.EXE AAP C:\NEWDATA\P00789.BDT
Options for calling the CASE/CardioSoft application from Medical Reimbursement
Programs:
The control file contains the specified data:
1. Program call including patient data, procedure category and status, procedure
date/time: The procedure (e.g., the ECG trace) corresponding to the selected time
appears immediately. Note: The procedure status must be set for "procedure

from archive". The following option is the most convenient solution: the
procedure (e.g., resting ECG of 2 Jan 1992, 15:30h) can be selected directly from
the electronic patient file card, and the appropriate ECG trace is displayed at the
push of a button.
2. Program call including patient data, procedure category and status (new
procedure): The signal acquisition screen of the procedure category selected in
the application is promptly displayed.
Options for calling CASE/CardioSoft application without Procedure Category:
If desired, the procedure category does not need to be transferred to the application.
If the status equals archive recording (date and time of procedure not required), the
application will display a list of all existing recordings on the selected patient. If the
status equals new recording, the survey of all procedures which can be created, a
new will be displayed.
Tips for DOS programs running in a DOS box under WINDOWS:
The application needs to be called only once under WINDOWS. Even when started,
the application can still continue to read in the BDT control files. The DOS medical
reimbursement program will be started in a DOS box under WINDOWS. The BDT
control file for the application is generated in the electronic patient file card, with
e.g. the following user notice appearing: "Please change to CASE/CardioSoft with
the ALT-Tab key and press the 'Patient' button (or start CASE/CardioSoft), return
with the ALT-Tab key after completing the procedure and acknowledge with a key".
The user changes to the Program Manager and starts the application (create an
icon with "c:\cardio\cardio.exe AAP <name of control file with directory>"). The
application will then execute the control file. After completion of the procedure, the
user changes back to the medical reimbursement program using the ALT-Tab key
and acknowledges with a key. The medical reimbursement program reads the control
file from the application. If any other procedures are to be carried out, it is sufficient
to change to the application and to press the "Patient" button (top left) to cause the
application to read in the control file.
Options for calling WINDOWS Medical Reimbursement Programs with DDE:
With the aplication´s DDE interface, a medical reimbursement program needs to
be started only once (for example, after starting the application, the attempt must
be made in one second intervals to establish a DDE link). It then transmits a DDE
command to the application specifying the name of the BDT/GDT control file. After
completing the procedure, the user clicks "Quit" button and acknowledges the query
"Return to medical reimbursement program?" with Yes. This will transmit the DDE
command "AppDataReady" from the application to the medical reimbursement
program. Now the medical reimbursement program can read the BDT/GDT results.
In general: A DDE command is executed with the 3 parameters <Program name>
<Topic> <Command>.
MRP command to call the application and establish the DDE connection:
C:\CARDIO\CARDIO.EXE DDE <MRP program name> <MRP-DDE-Topic>

NOTE:
The application transmits the message to read in the DDE data to the MRP
program specified together with the specified MRP DDE topic.
DDE command from the medical reimbursement program:
Program name: CARDIO
Topic: System
Command: BDT <name of control file with directory> or GDT

<name of control file with directory>
DDE command sent to the medical reimbursement program:
Program name: <MRP program name>
Topic: <MRP DDE topic>
Command: AppDataReady
NOTE:
The MRP program name and the MRP DDE topic are transferred when the
application is launched.
Example for the DDE implementation in the MRP program:
Check if the application is already active.
If no: Launch the application to establish the DDE connection: c:\Cardio\CARDIO.Exe
DDE <your MRP name> System.Wait until Cardio.Exe has established the DDE-
connection. Send the DDE command to CardioSoft: DDE command ("CARDIO",
"System", "BDT”, “c:\cardio\BDT-File") or with GDT DDE command ("CARDIO", "System",
"GDT”, “c:\cardio\GDT-File").
The application reads the BDT/GDT File and performs the according action (new test,
view existing test) After the action is finished, click on the button “Quit Program” in the
Initial Screen and answer the question “Return to medical reimbursement program”
with YES. Now the application sends the DDE command DDE command (“<your MRP
name>”, “System”, "AppDataReady") to the MRP and the measurement results are
available in the BDT/GDT file. In this state the application waits for the next DDE
command.
NOTE:
If there is no need for the MRP to be informed when the measurement results are
available from the applcation, a new DDE command can be sent from MRP while
the application stays in the “Post Test Review” mode.
Data transmitted from CASE/CardioSoft to Medical

Reimbursement Program

A medical data record is written to the received BDT file for each completed
procedure. When adopted by the medical reimbursement program, the BDT file must
be deleted. The BDT output file of the CASE/CardioSoft application is created only one
time for a new procedure (feature for GDT server).
For each deleted procedure, a data record with the appropriate ID for the medical
reimbursement program is added. It is possible to delete this procedure from the
medical reimbursement program.
If a procedure is edited in the application, a data record marked "edited procedure"
is added to the medical reimbursement program. The various changes can be
documented in the medical reimbursement program. The application only stores
the most recent version. Thus, the application can be called from the medical
reimbursement program only with the most recent version of the procedure.
Points to note (compared with BDT):
• The patient's year of birth (field ID 3303) transmitted to the application should have
four digits (format: DDMMYYYY).
• The year of the procedure (field ID 8432) transmitted to the application should
have four digits (format: DDMMYYYY).
For all procedure categories, the file should begin as follows:
• procedure category (rest ECG, spirogram,...)
• procedure date
• procedure time
• procedure status (new, edited)
For a designator indicating the procedure category, please refer to the ID list.
The application provides the result values (8240 result value, 8421 unit, 8460 normal
value text) by way of a BDT result text (8480). To do so, insert the following line in the
WIN.INI file in section "[CARDIO]": PAT_BdtValText=1
To set the application in the mode to append BDT records to the BDT file , insert the
following line in the WIN.INI file in section "[CARDIO]": PAT_AppendBdtRecord=1
The output of a measurement can be disabled with an entry in the file AAPOUT.INI
(Create this text file in the CASE/CardioSoft database directory). For example, enter
the section [AAPOUT]. Then in a new line enter the procedure ID and set it to zero. The
file AAPOUT.INI must have the following content to disable the heart rate (procedure
ID "HF") of a Rest ECG: [AAPOUT] HF=0
The following entries cause to disable the corresponding data objects (V6.72 and
later):
• ERG_INTER_SYS=0 Exercise Test: System Evaluation
• ERG_INTER_PHY=0 Exercise Test: Physician's Interpretation
• LBD_INTER_SYS=0 Amb.Blood Pressure: System Evaluation
• LBD_INTER_PHY=0 Amb.Blood Pressure: Physician's Interpretation

• RES_INTER_SYS=0 Resting ECG: System Evaluation

• RES_INTER_PHY=0 Resting ECG: Physician's Interpretation
• SPI_INTER_SYS=0 Spirometry: System Evaluation
• SPI_INTER_PHY=0 Spirometry: Physician's Interpretation
Special features of CASE/CardioSoft

The following special features should be taken into account when the CASE/
Cardiosoft application is called from the medical reimbursement program (marked
by the command parameter "AAP"). The entry of a password is not requested (access
control by medical reimbursement program is sufficient).
The functions "Patient/Modify...", "Patient/Select from list" and "Patient/New" are
disabled.
Using the patient ID in the task file, either an existing patient is called up from the
database or a new patient file is created automatically.
If the patient ID already exists in the application but the patient demographic data
of the medical reimbursement program are different (one of first name, last name
or date of birth), the default reaction of the application is to bring up a side-by-side
dialog to show both sides of data.
The user can then select the correct data or quit the dialog to stop the test. This is
mainly provided due to possible patient ID mismatches, for example, when patient IDs
are created locally on the application and then later by the medical reimbursement
program.The application provides this check from V6.51 and later.
However, if it is desired, this check can manually be configured:
Enter the following entry in LOC_WIN.INI (V6.6 and later), section [CARDIO]:
PAT_CheckDemogr=<value> // Range of values 0...2 Default:1

If the application is launched by an external system via BDT or GDT, this entry defines
the reaction, if the incoming patient ID is identical with the local database, but the
patient demographic data (one of first name, last name or date of birth) are different.
0: No user interaction; If the incoming data field is not blank, the data is taken from
the external system, else from the local database (as up to V6.5).
1: A side-by-side dialog displays to select which patient demographic data should be
used for the local database.
2: An error message displays which must be confirmed. A new test cannot be
performed.
When patient demographic data are received via the BDT / GDT interface, the
Complete Patient Information dialog allows the user to complete missing patient
demographic data, depending on the procedure type and the chosen configuration.
The following items can individually be enabled or disabled per procedure type:
• Last name
• First name
• Date of birth
• Weight
• Gender
• Ethnic
• Pacemaker
For detailed information please see the CASE / CardioSoft Service Manual. This
feature is provided from V6.6 and higher.
From the main menu, you can exit the application directly without any additional
query.
If the application is called without the command parameter "GDT", all the usual
program functions are available.
query.
If the application is called without the command parameter "AAP", all the usual
Four digits should always be entered for the year of birth and of the procedure. The
BDT format has no provisions for entering the seconds of the procedure time (field
ID 8433). Thus, if several procedures are performed in the same minute (which is
unlikely), only the first procedure of that minute can be recalled.
From V6.51 and higher, the application also provides unit conversion for data input
(BDT always is in “cm, kg”) if the user has selected “in, lbs” for Height/ Weight Unit
in System Configuration and the following setting is done in AAPOUT.INI, section
[SETUP]: GDTUseConfigUnits=1
BDT Examples
(end each line with CR + LF)
Medical reimbursement example: new resting ECG , recorded on 20 December, 1991
at 9:30 hrs, patient name: HANS MAIER:
Data ...Comments
01380006100 ...record ID of med. data record: 6100
014810000117 ...record length: 117 Byte
0143301MAIER ...patient´s name: MAIER
0133302HANS ...patient´s first name: HANS
017330329031963 ...patient´s date of birth: 29 March 1963
0133600P128 ...patient ID: P128
01036211 ...patient´s sex: MALE
0123622178 ...patient´s height: 178 cm
011362378 ...patient´s weight: 78 kg
01380006200 ...rec. ID of medical data record: 6200
014810000077 ...record length: 77 bytes
0133600P128 ...patient ID: P128
0156200200192 ...storage date: 20.01.92
011840211 ...procedure-related ID field: rest ECG
0108404N ...hospital findings status: new proc.
Medical reimbursement example: new resting ECG; the following entries are added by
the CASE/CardioSoft application:
Data ...Comments
01380006200 ...record ID of medical data record:6200
014810000808 ...record length: 808 byte

Data ...Comments
0133600P128 ...patient ID: P128
0156200200192 ...storage date: 20.01.92
011840211 ..procedure-related ID field: rest ECG
0118404N ...hospital findings status: new proc.
0158432201291 ...ECG recording date: 20.12.91
0138433093020 ...ECG recording time: 9:30:20
0118410HR ...heart rate ID: HR
0118411HF ...parameter label: HF
011842083 ...parameter reading: 83
01484211/min ...unit of measure: 1/min
....followed by readings for: RR,QRS,QT,QTC,QTC calculation ,PQ,P,<QRS,<T !!!
Data ...Comments
0138410P_DG ...\
0128411< P ... \ < P : -25 degrees
0128420-25 ... /
0138421Grad .../
0148410INTER ...\
0348411Interpretation ... \ short interpretation

(short-form)
0348480Left axis deviation ... / line 1
0348480T-wave change ... / line 2
0398480unusual R/S .../ line 3

inversion area
Medical reimbursement example: request for resting ECG recorded on 20 December,

1991 at 9:30 hrs, patient´s name: HANS MAIER:
Data ...Comments
01380006100 ...record ID pat. demographic data: 6100
0143301MAIER ...patient name: MAIER
0133302HANS ...patient's first name: HANS

Data ...Comments
017330329031963 ...patient's date of birth: 29.3.1963
0133600P128 ...patient ID: P128
01036211 ...patient's sex: male
011362378 ...patient´s weight: 78 kg
01380006200 ...record ID of medical data record:6200
0148100000149 ...record length: 149 bytes
0133600P128 ...patient ID: P128
0156200200192 ...storage date: 20.01.92
011840211 ...procedure-related ID field: rest ECG
0118404A ...hospital findings status: archive proc.
0158432201291 ...ECG recording date: 20.12.91
0138433093020 ...ECG recording time: 9:30:20
Character Set
The character set for BDT is configurable in the file AAPOUT.INI in section [SETUP]
GDTOemCharSet=0: the character set is Windows ANSI. GDTOemCharSet=1: or
without this entry, IBM / DOS / OEM is used.
NOTE:
AAPOUT.INI must be located in the CASE/CardioSoft database folder. The
Medical Reimbursement Program may also transfer the character set in the field
9206. With V6.6 and higher, this entry is used if the following setting is done in
AAPOUT.INI in section [SETUP] PreferOemCharSetFromAAP=1.

3
GDT Format Interface
General Requirements
This document is based on the GDT data record description [GDT], worked out by
Quality Group of medical Software of the German Central Institute for Medical Care
By Panel Doctors. GDT is more modern form of the BDT interface. The basic syntax is
the same as in the BDT interface.
Brief summary of the most important features of the GDT format:
The data record comprises the following fields (with field ID):
• Data record ID (8000) for data medium header. Only the following medium headers
are supported: 6302, 6310, and 6311
• Data record length in bytes (8100) of the field Data record ID (incl.) up to the last
field before the next data record ID
• other fields
A field comprises the following field sections (with lengths):
• Length (3 byte): computed from the length of the contents + 9
• ID (4 byte): unequivocal field ID (e.g. 8000 data record category)
• Contents: data contents with variable length in IBM DOS character set (not
WINDOWS character set)
• End (2 byte): ASCII value 13 (CR) + ASCII value 10 (LF)
In order to display field content over several lines, the field is repeated for each line
with the same ID.
The record length is checked. The record length is calculated from the field lengths,
beginning with the record ID field and ending with the last field of the record. None of
the unknown fields are evaluated.
Sections of the GDT Format

The medical reimbursement program writes in the control file the data record to
request a new procedure (record ID: 6302) or requests to display a procedure from the
archive (record ID: 6311). The CASE/CardioSoft application writes in the control file the
data of a procedure (record ID: 6310).
NOTE:
*2.1 indicates that the appropriate field ID is supported by GDT 2.1.
Description of the record ID 6302 request of a new procedure:
Field ID Designation of field Examples of field Explanation

content contents
8000 data record ID 6302 request new procedure

(this field must always
exist)
8100 record length 04598 (this field must always

exist)
9206 *2.1 character set 1, 2, 3 Character set used

by CASE/CardioSoft
to *2.1 convert the
text data. 1: 7Bit 2:
IBM (Standard) CP 437
3: ISO8859-1 (ANSI)
CP 1252 1 and 3 are
ignored by CASE?
CardioSoft Details see
chapter: GDT Version /
Character Set
9218 *2.1 GDT version 02.10 maximum 5 characters

*2.1 Details see
Character Set
0102 *2.1 software vendor GE Healthcare This item is not

stored in the *2.1
CASE/CadioSoft
database. It’s written
for information to the
logbook
0103 *2.1 software Carddas This item is not

stored in the *2.1
CASE/CadioSoft
logbook
0132 *2.1 software release 3.5 This item is not

stored in the *2.1
CASE/CadioSoft
logbook
3000 patient ID P875386432 CASE/CardioSoft uses

up to 30 characters
exist)


content contents
3101 patient's last name SMITH CASE/CardioSoft uses

up to 30 characters
exist)
3102 patient's first name TOM CASE/CardioSoft uses

up to 30 characters
exist)
3103 pateint's date of birth 29031963 format: DDMMYYYY

date of birth (this field
must always exist)
3110 patient's sex 1 1 = male; 2 = female

(optional field)
3622 patient's height 178.5 unit: cm; CASE/

CardioSoft ignores the
digits after the point.
(optional field)
8402 procedure category EKG01 List of supported

Procedures BDM01
Ambulatory Blood
Pressure EKG01
Resting ECG EKG04
Holter ECG ERGO01
Stress Test ERGO05
Ergospirometry
LUFU02 Resting
Spirogram Revision
C BDT/GDT Interface
Specification Page 20
of 38 2040396-099 If
this field does not exist
or the procedure is not
provided, a menu with
all available procedure
categories is displayed.
Description of record ID 6311 request to display a procedure from the archive:

content contents
8000 data record ID 6311 request display

procedure form the
archive. (this field must
always exist)

exist)


content contents
9206 *2.1 character set 1, 2, 3 Character set used

by CASE/CardioSoft
to *2.1 convert the
text data. 1: 7Bit 2:
IBM (Standard) CP 437
3: ISO8859-1 (ANSI)
CP 1252 1 and 3 are
ignored by CASE/
CardioSoft Details see
Character Set
9218 *2.1 GDT version 02.10 maximum 5 characters

*2.1 Details see
Character Set
0102 *2.1 software vendor GE Healthcare This item is not

stored in the *2.1
CASE/CadioSoft
logbook
0103 *2.1 software Carddas This item is not

stored in the *2.1
CASE/CadioSoft
logbook
0132 *2.1 software release 3.5 This item is not

stored in the *2.1
CASE/CadioSoft
logbook
3000 patient ID P875386432 CASE/CardioSoft uses

up to 30 characters
exist)
3101 patient's last name SMITH CASE/CardioSoft uses

up to 30 characters
(optional field)
3102 patient's first name TOM CASE/CardioSoft uses

up to 30 characters
(optional field)
3103 patient's date of birth 29031963 format: DDMMYYYY

(optional field)


content contents
8402 procedure type EKG01 List of supported

Procedure Categories
see Description of the
record ID 6302 If this
field does not exist a
menu with all available
procedure data of this
patient is displayed.
8432 date of procedure 20051999 format: DDMMYYYY
8439 time of procedure 113058 format: HHMMSS
Utilization of the procedure data from CardioSoft data record (6310):
Field ID Designation of field Example of field Explanation

content contents
8000 data record ID 6310 procedure data form

CASE/CardioSoft (this
field must always exist)

exist)
9206 *2.1 character set 2, 3 Character set, used

by CASE/CardioSoft to
*2.1 handle the text
data. 2: IBM (Standard)
CP 437 3: ISO8859-1
(ANSI) CP 1252 Details
see chapter: GDT
Version / Character Set
9218 *2.1 GDT version 02.00 02.10 maximum 5 characters

Details see chapter:
GDT Version /
Character Set
0102 *2.1 software vendor GE Healthcare company name
0103 *2.1 software CardioSoft name of the product
0132 *2.1 software release v6.6 software version
3000 patient ID P875386432 CASE/CardioSoft writes

up to 30 characters
exist)
3101 patient's last name SMITH CASE/CardioSoft writes

up to 30 characters
3102 patient's first name TOM CASE/CardioSoft writes

up to 30 characters


content contents
3103 patient's date of birth 29031963 format: DDMMYYYY
8402 procedure type EKG01 List of Procedure

Categories see
Description of the
record ID 6302
8432 data of Procedure 20051999 format: DDMMYYYY
8439 time of procedure 113058 format: HHMMSS
8410 test ident PROC the content depends

on the setting in
AAPOUT.INI (V6.6)
[Setup] PROC=1 =>
content is PROC
PROC=2 => content
is empty PROC=3 =>
Modality: Spiro, Resting
The default is PROC=1
6302 *2.1 file identifier 1 continuous number of

the exported *2.1 file
from CASE/CardioSoft
6303 *2.1 file format PDF, XML extension of the

exported file
6304 *2.1 file content Report Data content of the

exported file extension
XML: Data, others:
Report
6305 *2.1 file reference c:\Exp\xyz.pdf reference to the

exported file
Note: the fields 6302 .. 6305 are repeated for every exported file from the test
6330 *2.1 name of free category DICOM STUDY Instance

UID part 1
6331 *2.1 content of free first 60 bytes of the

category DICOM *2.1 Study
Instance UID
6332 *2.1 name of free category DICOM STUDY Instance

UID part 2
6333 *2.1 content of free remaining bytes of

category the DICOM *2.1 Study
Instance UID
8990 *2.1 signature Dr.XY, 10.06.09 confirmation string

from confirmed tests
*2.1 confirmed by:
physician, date


content contents
6228 formatted result HR: 84 /min For more lines of

Text the field 6228
is repeated. CASE/
CardioSoft V4.14 and
later sends field 6228
instead of field 8410,
8411, 8420, 8421,
8460, 8480. With CASE/
CardioSoft V5.0 this
output with 8411,
8420, 8421, 8460,
8480 can be activated.
Display the content of
this field with a none
proportional font.
8410 data ID FEVC (up to 6 characters)(this

field is only supported
V4.13 and CASE/
CardioSoft V5.0 with
configuration)
8411 data label FEVC data label in the

language selected
in CardioSoft (this
field is only supported
V4.13 and CASE/
configuration)
8420 data value 5.03 data value (this field

is only supported
from Revision C
BDT/GDT Interface
Specification Page 23
of 38 2040396-099
CASE/CardioSoft
V4.13 and CASE/
configuration)
8421 1 unit of the data value

(this field is only
supported from CASE/
CASE/CardioSoft V5.0
with configuration)


content contents
8460 data normal value 5.38 normal value (optional)

(this field is only
supported from CASE/
CASE/CardioSoft V5.0
with configuration)
8480 data text ventilation... data text field is

available instead of
data value (8420),data
unit (8421) and data
normal value (8460).
For more lines of
Text the field 8480 is
repeated. (this field
is only supported
V4.13 and CASE/
configuration)
Data transmitted from Medical Reimbursement Program to

CASE/CardioSoft
The medical reimbursement program transfers the following data of the selected
patient to the CASE/CardioSoft application in the form of a control file:
NOTE:
The patient must be clearly identified by the patient ID.
The following data is required:
• patient's last name
• patient's first name
• patient ID
• date of birth (optional)
• procedure category (rest ECG, spirogram,...) (should be included, but is not required)
• procedure status : new procedure or procedure from archive
• if procedure status = procedure from archive: date of procedure date and time of
procedure can be send.
• height (in cm), sex (1:male, 2: female). Height and sex should be included, but may
also be entered in the application.

Calling the CASE/CardioSoft Application

Program call command syntax under WINDOWS:
C:\CARDIO\CARDIO.EXE GDT <name of control file with directory>
Comments on command syntax:
The identifier GDT (1st parameter) tells the application that it was called from the
medical reimbursement program. The name of the control file (2nd parameter)
containing the patient data must include the directory of the control file.
The control file name must start with "HELL" and follow a ID of the calling program.
For example, "HELLAAP.GDT". The extension must be always ".GDT". If the syntax of the
file name is wrong, the error message number 1135 is displayed. For the output file
the ID of the calling program is first in the file name and than follows "HELL" (for the
example the output file name is "AAPHELL.GDT").
The directory path to the GDT file cannot include the string "HELL".
The only purpose of this directory is to serve as a data buffer between medical
reimbursement program and the application.
NOTE:
If this file is accessed by several workstations in the network, the name of the
control file must be unique for the workstation in the network or stored in a local
directory.
If the directory name includes at least one blank, double quotes must be used for
correct usage (e.g. C:\CARDIO\CARDIO.EXE GDT “C:\NEW DATA\ HELLAAP.GDT”).
Special feature for the medical reimbursement program: When starting the medical
reimbursement program, this directory must be searched for procedures which
have as yet not been accepted, and the procedures carried out must be accepted
by the medical reimbursement program. This situation may occur if the computer is
switched off after a recording in the application.
Example:
C:\CARDIO\CARDIO.EXE GDT C:\NEWDATA\HELLAAP.GDT
Options for calling CASE/CardioSoft without Procedure Category:
If desired, the procedure category does not need to be transferred to the application.
If the status equals archive recording (date and time of procedure not required), the
application will display a list of all existing recordings on the selected patient. If the
status equals new recording, the survey of all procedures which can be created anew
will be displayed.
Tips for DOS programs running in a DOS box under WINDOWS:
The application needs to be called only once under Windows. Even when started,
the application can still continue to read in the GDT control files. The DOS medical
reimbursement program will be started in a DOS box under Windows. The GDT
control file for the application is generated in the electronic patient file card, and

displays following user notice: "Please change to CASE/CardioSoft with the ALT-Tab
key and press the 'Patient' button (or start CardioSoft), return with the ALT-Tab key
after completing the procedure and acknowledge with a key". The user changes
to the Program Manager and starts the application (create an icon with "c:\cardio
\cardio.exe GDT <name of control file with directory>"). The application will then
execute the control file. After completion of the procedure, the user changes back
to the medical reimbursement program using the ALT-Tab key and acknowledges
with a key. The medical reimbursement program reads the control file from the
application. If any other procedures are to be carried out, it is sufficient to change to
the application and to press the "Patient" button (top left) to cause the application to
read in the control file.
Options for calling Windows Medical Reimbursement Programs with DDE:
With the application´s DDE interface, a medical reimbursement program needs to
start only once (e.g. after starting the CASE/CardioSoft application, attempt must
be made in one second intervals to establish a DDE link). It then transmits a DDE
command to the application specifying the name of the GDT control file. The program
changeover is very rapid. After completing the procedure, the user clicks "Quit" button
and acknowledges the query "Return to medical reimbursement program?" with
Yes. This will transmit the DDE command "AppDataReady" from the application to
the medical reimbursement program. The medical reimbursement program is then
capable of reading the GDT data.
Calling command syntax from CASE/CardioSoft application using DDE:
C:\CARDIO\CARDIO.EXE DDE <MRP program name> <MRP-DDE-Topic>
NOTE:
The application transmits the message to read in the DDE data to the MRP
program specified together with the specified MRP DDE topic.
DDE command from the medical reimbursement program:
Program name: CARDIO
Topic: System
Command: GDT <name of control file with directory>
DDE command sent to the medical reimbursement program:
Program name: <MRP program name>
Topic: <MRP DDE topic>
Command: AppDataReady
NOTE:
The MRP program name and the MRP DDE topic are transferred during program
start up.

Data transmitted from CASE/CardioSoft to Medical

Reimbursement Program
The BDT output file of the application is created only one time for a new procedure
(feature for GDT server).
The option of CASE/CardioSoft to disable the output of a measurement :
The output of a measurement value can be disabled with an entry in the file
AAPOUT.INI. In V6 or above, AAPOUT.INI must be located in the CASE/CardioSoft
database folder.
Enter first the section [AAPOUT]. Then in a new line enter the procedure ID and set it
to Zero.
The file AAPOUT.INI must have the following content to disable the heart rate of a
Rest ECG: [AAPOUT] HF=0
The following entries disable the corresponding data objects (version V6.72 and
later): ERG_INTER_SYS=0 Exercise Test: System Evaluation ERG_INTER_PHY=0
Exercise Test: Physician's Interpretation LBD_INTER_SYS=0 Amb.Blood Pressure:
System Evaluation LBD_INTER_PHY=0 Amb.Blood Pressure: Physician's Interpretation
RES_INTER_SYS=0 Resting ECG: System Evaluation RES_INTER_PHY=0 Resting
ECG: Physician's Interpretation SPI_INTER_SYS=0 Spirometry: System Evaluation
SPI_INTER_PHY=0 Spirometry: Physician's Interpretation
The option of CASE/CardioSoft to enable the output of a measurements with Test-ID:
The output of the measurements with Test-ID can be enabled with an entry in the
file AAPOUT.INI. Please enter first the section [SETUP] and than in a new line with the
content GDTDataFields=1.
Every Measurement generates the test ID (8410), test designator (8411), result (8420),
unit (8421), normal value text (8460) or as Text result (8480).
The file AAPOUT.INI must have the following content to enable the output of
measurements with Test-ID: [SETUP] GDTDataFields=1
The option of CASE/CardioSoft to enable automatic output of GDT file and Bitmap
Picture:
The automatic output of GDT file can be enabled with an entry in the file AAPOUT.INI.
First enter the section [SETUP] and then in a new line “GDTOutDir=1”. This function can
only be used, if the application is called without GDT/BDT Parameter. For every new or
changed procedure a GDT file is generated with the file name PROC<number>.GDT in
the subdirectory GDTOUT of the Application Data Folder. <number> has a range from
0 to 9999.
The file AAPOUT.INI must have the following content to enable the automatic output
of GDT file: [SETUP] GDTOutDir=1
If automatic output of GDT is enabled, the following field IDs (Patient demographic
data) 3101 (Last Name), 3102 (First Name), 3103 (Date of birth), 3110 (Gender) are
inserted in the GDT-out file (6310). This is especially needed for examinations from
outside of the system, for example, an ECG recorder.
In addition to the automatic output of the results, the output of a picture can be
enabled with an entry in the file AAPOUT.INI in the section [SETUP]: “GDTOutFile=1.”
This function can also only be used, if the application is called without GDT/BDT
Parameter. For every new or changed procedure, a Bitmap Picture is generated with
the file name “PIC<number>.BMP” in the subdirectory GDTOUT of the Application Data
Folder. In the GDT file “PROC<number>.BMP”, the entry 9154 includes the path and file
name of the picture. The file AAPOUT.INI must have the following content to enable
the automatic output of a GDT-file and a BMP-file: [SETUP] GDTOutDir=1 GDTOutFile=1
The file location for automatic GDT output (and also for the BMP-files) is configurable
(from V5.1). The default location is as described above (GDTOUT). Use the entry
“GDTOutLoc” in AAPOUT.INI to select another directory. The directory is automatically
created, but only the last component of the directory name can name a new
directory. For example, if the entry “GDTOutLoc=c:\cardio\dir1\dir2” is used in
AAPOUT.INI and c:\cardio exists, c:\cardio\dir1\dir2 is not created. The UNC notation
is provided, for example, “GDTOutLoc=\\pc\gdt”.
[SETUP]
GDTOutDir=1
GDTOutFile=1
GDTOutLoc=c:\dir1
The function of CASE/CardioSoft Web to display a procedure (In CASE/CardioSoft Web

V5.0 and newer):
With the GetExamDirect function a selected procedure can be displayed with CASE/
CarioSoft Web. If only the Patient ID is defined in the URL, then the List of Procedures
of this patient is displayed.
The following parameters must follow the GetExamDirect URL: PatID : Patient ID
ExamType : Procedure Type with LUFU02 for Spiremetry, EKG01 for Resting ECG,
ERGO01 for Stress Test, BDM01 for Ambulatory Blood Pressure, EKG04 for Holter.
ExamDate: Recording date of procedure with the Format DDMMYYYY (D: day; M:
month; Y: year)
ExamTime : Recording time of procedure with the Format HHMMSS (H: hour; M:
minute; S: second).
Example with the server name “localhost” to display a Resting ECG with
recording date 7.Feb.2003 and recording time 15:40:49: http://localhost/
scripts/CardioSoftWeb/iscard.dll?GetExamDirect?PatID=P007&ExamT
ype=EKG01&ExamDate=07022003&ExamTime=154049
Special features of CASE/CardioSoft

The following special features should be taken into account when the CASE/
CardioSoft application is called from the medical reimbursement program (marked
by the command parameter "GDT"). The entry of a password is not requested (access
control by medical reimbursement program is sufficient).
The functions "Patient/Modify...", "Patient/Select from list" and "Patient/New" are
disabled.
Using the patient ID in the task file, either an existing patient is called from the
database or a new patient file is created automatically.
If the patient ID already exists in the application but the patient demographic data
of the medical reimbursement program are different (one of first name, last name
or date of birth), the default reaction of the application is to bring up a side-by-side
dialog to show both sides of data.
The user can then select the correct data or quit the dialog to stop the test. This
is mainly provided due to possible patient ID mismatches, for example, when
patient ID’s were created locally on the application and then later by the medical
reimbursement program. The application provides this check from V6.51 and later.
However, if it is desired, this check can manually be configured:
Enter the following entry in LOC_WIN.INI (V6.6 and later), section [CARDIO]:
PAT_CheckDemogr=<value> // Range of values 0...2 Default:1
If the application is launched by an external system via BDT or GDT, this entry defines
the reaction, if the incoming Patient ID is identical with the local database, but the
patient demographic data (one of first name, last name or date of birth) are different.
0: No user interaction; If the incoming data field is not blank, the data is taken from
the external system, else from the local database (as up to V6.5).
1: A side-by-side dialog displays to select which patient demographic data should be
used for the local database.
2: An error message displays which must be confirmed. A new test cannot be
performed.
When patient demographic data are received via the BDT / GDT interface, the
Complete Patient Information dialog allows the user to complete missing patient
demographic data, depending on the procedure type and the chosen configuration.
The following items can individually be enabled or disabled per procedure type:
• Last name
• First name
• Date of birth
• Weight
• Gender
• Ethnic
• Pacemaker
For detailed information, see the CASE / CardioSoft Service Manual. This feature is
provided from V6.6 and higher.
query.
If the application is called without the command parameter "GDT", all the usual
The application also provides unit conversion for data input (GDT always is in “cm, kg”)
if the user has selected “in, lbs” for Height/ Weight Unit in System Configuration and
the following setting is done in AAPOUT.INI, section [SETUP]: GDTUseConfigUnits=1
User definable field identifier

The CASE/CardioSoft application supports the possibility to define free field identifiers.
The EMR system can use these fields to launch the application to acquire or view
a test, and the application writes these fields back to the GDT file when the test is
finished.
This feature helps for the EMR system to store additional information about the test in
the GDT output file.
Example:
• Unique order or request number
• Additional patient identifier
NOTE:
• These items are not stored in the CASE/CardioSoft database.
• Make sure to use only unused GDT numbers.
The entries (max.10) can be defined as follows:
AAPOUT.INI (Database folder )
[SETUP]
GDT_FreeFieldId1=6351
GDT_FreeFieldId2=6352
This feature is provided from V6.6 and higher.
GDT Examples
(end each line with CR + LF)
Medical reimbursement example: new resting ECG with patient Tom Smith:
Data ...Comments
01380006302 ...record ID of med. data record: 6302
014810000206 ...record length: 206 Byte
014921802.10 ...GDT version 2.10
01092062 ...OEM character set
0220102GE Healthcare ...software vendor
0160103Carddas ...software name
01201323.5 ...software release
0133000P007 ...patient ID: P007
0143101Smith ...patient´s last name: Smith
0123102Tom ...patient´s first name: Tom
013362378.0 ...patient´s weight: 78.0 kg
0148402EKG01 ...procedure type: Resting ECG
Resting ECG Data from CASE/CardioSoft:

Data ...Comments
01380006310 ...record ID: 6310
014921802.10 ...GDT version 2.10
0190103CardioSoft ...software name
0133000P007 ...patient ID: P007
011362378 ...patient´s weight: 78.0 kg
0138410PROC ...test ident
017843220051999 ...date of procedure: 20 May 1999
0158439114701 ...time of procedure: 11:47:01
0378990Dr. No, 19.06.2009, 9:15:30 …confirmation text
0336330DICOM Study Instance (1) …DICOM study instance UID Part(1)
05563311.2.840.113619.2.235.4486 … study instance

137440696201411238252
01063021 …file identifier, continuous number=1
0126303PDF …file format, extension=PDF
0156304Report …file content=REPORT
0536305D:\Export … file reference

\P007#Smith#2009_06_19#09_15_18.PDF
01063022 …file identifier, continuous number=2
0126303RTF …file format, extension=RTF
0156304Report …file content=REPORT
0536305D:\Export …file identifier, continuous number=3

\P007#Smith#2009_06_19#09_15_18.RTF 01063023
0126303XML …file format, extension=XML
0136304Data …file content=DATA

Data ...Comments
0536305D:\Export … file reference

\P007#Smith#2009_06_19#09_15_18.XML
00186228HR 85 bpm ...heart rate value
....followed by readings for: RR,QRS,QT,QTC,QTC calculation ,PQ,P,<QRS,<T !!!
0306228Measurements Summary: ...Interpretation label:
Measurements...
0356228 negative T-wave (lateral) ...Interpretation: 1.line
0406228 because T <=-0.1 mV in [V6] ...Interpretation: 2.line
Medical reimbursement example: request for resting ECG recorded on 20 May 1999
at 11:47:01 hrs, patient´s name Tom Smith:
Data ...Comments
01380006311 ...record ID: 6311
014921802.10 ...GDT version 2.10
0160103Carddas ...software name
0133000P007 ...patient ID: P007
0143101Smith ...patient last name: Smith
0123102Tom ...patient first name: Tom
013362378.0 ...patient´s weight: 78.0 kg
017843220051999 ...date of procedure: 20 May 1999
0158439114701 ...time of procedure: 11:47:01

GDT Version
From V6.6 or above, CASE/CardioSoft supports features from GDT 2.1. The GDT
version to be used can be defined by the CASE/CardioSoft application (AAPOUT.INI) or
the Medical Reimbursement Program (field ID 9218)
The following entry in AAPOUT.INI (CASE/CardioSoft database folder) defines that
the settings are used as defined by the Medical Reimbursement Program. [SETUP]
PreferGdtVersionFromAAP=1
For CASE/CardioSoft, the GDT version is configurable in the file AAPOUT.INI in section
[SETUP] GDT_Version=2.0
If there is no entry, CASE/CardioSoft uses GDT 2.1.
Character Set
The character set for GDT is configurable in the file AAPOUT.INI (CASE/CardioSoft
database folder) in section.
[SETUP]
GDTOemCharSet=0: the character set is Windows ANSI.
GDTOemCharSet=1: or without this entry, IBM / DOS / OEM is used
The Medical Reimbursement Program may also transfer the character set in the
field 9206. With V6.6 and higher, this entry is used if the following setting is done in
AAPOUT.INI in section [SETUP] PreferOemCharSetFromAAP=1.
File Reference Field IDs

CASE/CardioSoft uses the field IDs to describe the attributes of the exported files as
follows:
6302 file identifier continuous number of the

exported
6303 file format extension of the exported file
6304 file content content of the exported file
6305 file reference reference to the exported file
To be able to adapt better to the conditions of the different EMR suppliers, there is the
possibility to map these field IDs to others.
This is configurable in the file AAPOUT.INI (CASE/CardioSoft database folder) in section
[SETUP].
RefNumberID=xxxx // file identifier default: 6302 range: 0 .. 9999
RefFormatID=xxxx // file format default: 6303 range: 0 .. 9999
RefContentID=xxxx // file content default: 6304 range: 0 .. 9999
RefFileNameID=xxxx // file reference default: 6305 range: 0 .. 9999
NOTE:
The value “0” ensures that the appropriate field is not written to the GDT output.

4
List of Procedure IDs
ID List for Resting Spirogram
Designation ID Unit Remark
- Expiratory vital EVC l (liters) only LF501

capacity (EVC)
- Forced exp. vital FVC 1

capacity (FVC)
- Forced exp. vital FEV05 1 only SpiroSoft

capacity in 0.5 seconds
(FEV05)
- Forced exp. vital FEV1 1

capacity in 1 second
(FEV1)
- FEV1 referred to FEV1/IVC % only LF501

inspiratory vital cap.
(FEV1/IVC)
- FEV1 referred to FVC FEV1/FVC %

(FEV1/FVC)

capacity in 3 seconds
(FEV3)

capacity in 6 seconds
(FEV6)
- FEV1 referred to FEV6 FEV1/FEV6 % only SpiroSoft

(FEV1/FEV6)
- Peak expiratory flow PEF l/s (liters/second)

(PEF)
- Max. exp. flow when MEF75 l/s

75% of FVC is yet to be
exhaled (MEF75%)

exhaled (MEF50%)

Designation ID Unit Remark

exhaled (MEF25%)
- Max. mid expiratory MMF l/s

flow(MMEF)
- Inspiratory vital IVC l (liters) only LF501

capacity (IVC)
- Forced insp. vital FIVC 1

capacity (FIVC)
- Forced insp. vital FIV1 1

capacity in 1 second
(FIV1)
- FIV1 referred to IVC FIV1/IVC % only LF501

(FIV1/IVC)
- FIV1 referred to FVC FIV1/FVC %

(FIV1/FVC)
- Peak inspiratory flow PIF l/s (liters/second)

(PIF)
- Max. insp. flow when l/s

75% of FIVC is inhaled
(MIF75%) MIF75

(MIF50%) MIF50

(MIF25%) MIF25
- Max. voluntary MVV l/min (liters/minute)

ventilation (indirect)
- Interpretation (if INTER

configured, system
evaluation is included)
ID List for Resting ECG

All parameter values refer to the dominant beat. Blood pressure value is supported
from CASE/CardioSoft V5 and higher.
Designation ID Unit
Heart Rate (HR) HF bpm

Designation ID Unit
blood pressure BP mmHg
RR interval (RR) RR_D ms
QRS duration (QRS) QRS_D ms
QT duration (QT) QT_D ms
QTC duration (QTC) QTC_D ms
QTC calculation QTC_BE (no unit)
(content: 1 = acc. to Bazett, 2 = acc. to Hegglin-Holzmann)
QTcBD dur. QTcBD ms
(QT interval according to Bazett)
PQ duration (PQ) PQ_D ms
P duration (P) P_D ms
QRS angle (< QRS) QRS_WI degreees
T angle (< T) T_WI degrees
P angle (< P) P_WI degrees
Interpretation INTER (no unit)
(content: Interpretation of the ECG signal acquisition, possibly edited by the physician)
Comment BEMERK comments on ECG procedure
QT-Dispersion QT_DISP ms
PP PP_D ms
ID List for Stress Test ECG

Designation ID Unit
DurationPhase 1 BP1_D min
NamePhase 1 BP1_N
NamePhase 2 BP2_N
NamePhase 3 BP3_N

Designation ID Unit
Total Test Time GES_D min

Comment BEMERK
Interpretation INTER
ID List for Ambulatory Blood Pressure, Holter ECG

Designation ID Unit
Interpretation (statistic INTER

summary and interpretation)
ID List for Ergospirometry

Designation ID Unit
Duration Phase 1 BP1_D min
Name Phase 1 BP1_N
Name Phase 2 BP2_N
Name Phase 3 BP3_N
Total Test Time GES_D min
Comment BEMERK
Interpretation INTER
IVC (Inspiratory vital capacity) VCin liter
FVCex (Forced expiratory vital FVCex liter

capacity)
FEV1 (Forced expiratory volume FEV1 liter

after one second)
PEF (Max. expiratory peak flow) PEF liter/sec
Time (Measurement time) Zeit h:mm:ss
Load Last Watt
VO2 (Oxygen uptake) VO2 liter/min

Designation ID Unit
VO2/kg (Oxygen absorption per VO2/kg ml/(min*kg)

kilogram body weight)
VCO2 (Exhaled carbon dioxide VCO2 liter/min

volume)
HR HF 1/min
O2 pulse (Oxygen absorption O2-Puls ml/beat

per heart beat)
BPsys BDsys mmHg
BPdia BDdia mmHg
VE (Expiratory breathing VE liter/min

volume)
VT (Tidal volume) VT liter
f-ergo (Breathing frequency AF 1/min

ergospirometry)

GE Medical Systems GE Medical Systems
Information Technologies, Inc. Information Technologies GmbH
8200 West Tower Avenue Munzinger Straße 5
Milwaukee, WI 53223 USA 79111 Freiburg Germany
Tel: +1 414 355 5000 Tel: +49 761 45 43 -0
Tel: +1 800 558 5120 (US Only)
GE Medical Systems Information Technologies, Inc., a General Electric Company, going to market as GE Healthcare.
www.gehealthcare.com

2096198-014 CASE CardioSoft Reimbursement V7.0

Uploaded by

Copyright:

Available Formats

You might also like

2096198-014 CASE CardioSoft Reimbursement V7.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2096198-014 CASE CardioSoft Reimbursement V7.0

Uploaded by

Copyright:

Available Formats

GE Healthcare

CASE / CardioSoft V7.0

CASE / CardioSoft V7.0

Revision Date Comment

A 20 March 2018 Initial Release

B 21 April 2018 Customer Release

C 18 October ATOM release

2096198-014 Revision C CASE / CardioSoft V7.0 2

ПРЕДУПРЕЖДЕНИЕ Това упътване за работа е налично само на английски език.

UPOZORENJE Ove upute za servisiranje dostupne su samo na engleskom jeziku.

VAROVÁNÍ Tento provozní návod existuje pouze vanglickém jazyce.

2096198-014 Revision C CASE / CardioSoft V7.0 3

ADVARSEL Denne servicemanual findes kun på engelsk.

WAARSCHUWING Deze service manual is alleen in het Engels verkrijgbaar.

HOIATUS Käesolev teenindusjuhend on saadaval ainult inglise keeles.

VAROITUS Tämä huolto-ohje on saatavilla vain englanniksi.

ATTENTION Ce manuel technique n'est disponible qu'en anglais.

4 CASE / CardioSoft V7.0 2096198-014 Revision C

WARNUNG Diese Serviceanleitung ist nur in englischer Sprache verfügbar.

FIGYELMEZTETÉS Ez a szerviz kézikönyv kizárólag angol nyelven érhető el.

AÐVÖRUN Þessi þjónustuhandbók er eingöngu fáanleg á ensku.

PERINGATAN Manual servis ini hanya tersedia dalam bahasa Inggris.

AVVERTENZA Il presente manuale di manutenzione è disponibile soltanto in Inglese.

2096198-014 Revision C CASE / CardioSoft V7.0 5

경고 본 서비스 지침서는 영어로만 이용하실 수 있습니다.

BRĪDINĀJUMS Šī apkalpotāju rokasgrāmata ir pieejama tikai angļu valodā.

ĮSPĖJIMAS Šis eksploatavimo vadovas yra prieinamas tik anglų kalba.

6 CASE / CardioSoft V7.0 2096198-014 Revision C

ADVARSEL Denne servicehåndboken finnes bare på engelsk.

OSTRZEŻENIE Niniejszy podręcznik serwisowy dostępny jest jedynie w języku angielskim.

AVISO Este manual de assistência técnica só se encontra disponível em inglês.

AVISO Este manual técnico só se encontra disponível em inglês.

AVERTISMENT Acest manual de service este disponibil numai în limba engleză.

2096198-014 Revision C CASE / CardioSoft V7.0 7

ПРЕДУПРЕЖДЕНИЕ Настоящее руководство по обслуживанию предлагается только на английском языке.

UPOZORENJE Ovo servisno uputstvo je dostupno samo na engleskom jeziku.

VAROVANIE Tento návod na obsluhu je k dispozícii len v angličtine.

OPOZORILO Ta servisni priročnik je na voljo samo v angleškem jeziku.

ADVERTENCIA Este manual de servicio sólo existe en inglés.

8 CASE / CardioSoft V7.0 2096198-014 Revision C

VARNING Den här servicehandboken finns bara tillgänglig på engelska.

UYARI Bu servis klavuzunun sadece İngilizcesi mevcuttur.

ЗАСТЕРЕЖЕННЯ Дане керівництво з сервісного обслуговування постачається виключно англійською

9 CASE / CardioSoft V7.0 2096198-014 Revision C

2 BDT Format Interface..................................................................................... 13

3 GDT Format Interface.....................................................................................27

4 List of Procedure IDs.......................................................................................46

2096198-014 Revision C CASE / CardioSoft V7.0 10

2096198-014 Revision C CASE / CardioSoft V7.0 11

• Medical reimbursement program automatically adopts the new/modified

Reference Document Title

[BDT] BDT data record description - interface description for system-independent

[GDT] GDT data record description - interface description for Connection of

12 CASE / CardioSoft V7.0 2096198-014 Revision C

Our BDT extensions

2096198-014 Revision C CASE / CardioSoft V7.0 13

B new bronchodilation spirogram

G existing procedure was modified

L existing procedure was deleted