Case / Cardiosoft V7.0: Emr Interface Reference Manual

GE Healthcare
CASE / CardioSoft V7.0

EMR INTERFACE REFERENCE MANUAL
2096198-015 Revision C
CASE / CardioSoft V7.0

EMR INTERFACE REFERENCE MANUAL
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 28 March 2018 Initial Release
B 24 April 2018 Customer Release
C 18 October 2018 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-015 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-015 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 Introduction...................................................................................................... 11
Purpose.....................................................................................................................................................................11
Legal Notice........................................................................................................................................................... 11
Reference Documents.......................................................................................................................................12
Conventions............................................................................................................................................................12
2 Interface Overview..........................................................................................13
Functions................................................................................................................................................................. 13
Workflow..................................................................................................................................................................13
3 Data Transfer................................................................................................... 21
Data Transfer: EMR to CASE/CardioSoft...................................................................................................21
Data Transfer: CASE/CardioSoft to EMR...................................................................................................21
HL7 Dataflow: CASE/CardioSoft – EMR.....................................................................................................23
4 Interface Specification....................................................................................24
EMR Interface Configuration..........................................................................................................................24
Functions Initiated by EMR.............................................................................................................................27
Functions Initiated by CASE/CardioSoft................................................................................................... 50
5 HL7 Messages.................................................................................................. 54
General..................................................................................................................................................................... 54
Legend...................................................................................................................................................................... 54
ORU – Observation Reporting.......................................................................................................................55
MDM – Document Management................................................................................................................. 69
MDM Message Segments................................................................................................................................71
ADT – Admission, Discharge and Transfer..............................................................................................79
ADT Message Segments.................................................................................................................................. 80
6 Appendix A........................................................................................................85
Character Set........................................................................................................................................................ 85
ST (String), TX (Text) and FT (Formatted Text).........................................................................................85
DT (Date) and TS (Timestamp).......................................................................................................................86
PN or PN - Person Name................................................................................................................................ 86
CN or XCN - Composite ID Number and Name................................................................................... 86
CASE / CardioSoft V7.0 10

1
Introduction
Purpose
This document is intended to be used as a technical description of the CASE and
CardioSoft EMR interface for external Electronic Medical Record (EMR) systems.
It provides a quick and easy mechanism for starting the CASE or CardioSoft
application via an EMR system. CASE/CardioSoft receives patient demographics
and clinical data from the EMR and sends test data for Resting ECG, Stress ECG,
Spirometry and Ambulatory Blood Pressure (ABP) to the EMR.
CASE/CardioSoft is launched by the EMR to run, edit or view a test in any of the four
modalities.
The EMR interface is available from CASE/CardioSoft V6.0 and higher. This document
is consistent with CASE/CardioSoft V7.0.
Legal Notice
This product contains several fields which can be filled in before performing an ECG.
Some fields must be filled in before performing an exam. Some fields are optional and
the user can assess whether they are needed to perform the exam. RACE is one of
the optional fields. It has been acknowledged by the medical profession as useful to
analyze some pathologies. In some jurisdictions, the processing of data revealing a
patient's racial origin is subject to legal requirements, such as obtaining the patient’s
prior consent. If you elect to collect this type of data, it is your responsibility to ensure
that you comply with all applicable legal requirements.

Introduction
Reference Documents
• CASE Service Manual
• CardioSoft Service Manual

• CardioSoft Software Installation Manual
Conventions
The following list is a collection of helpful hints and general guidelines.
• Items shown in Bold text are keys on the keyboard, text to be entered, or hardware
items such as buttons or switches on the equipment.
• Italicized items are software terms which identify menu items, buttons, or options
in various windows.

2
Interface Overview
Functions
The functions of the EMR interface are:
• Receiving patient demographics and clinical data.
• Startup in acquisition mode of a selected modality.
• Sending results and a reference to the test after the test is completed.
• Selection of patient and modality is provided by the EMR system. Changing patient
demographics is only possible via EMR system.
• Editing or viewing an existing test. The reference to the test is sent to the EMR and
is used by the EMR to edit or view the test.
• Data migration to update the EMR database with existing CASE/CardioSoft patient
demographics and references to existing tests.
• Data upload of received tests from ECG writers (patient demographics and
reference to the test) can be performed automatically.
The user interface is adapted in EMR mode (automatic detection). No additional
installation for the EMR interface is needed (Option Code XEMR). The data format is
HL7 V2.3.
Workflow
Both CASE/CardioSoft and the EMR client need to be installed on one workstation if
interaction is needed for conduct, edit (review), or viewing of tests.
Workflow Scenario 1: Conduct / Edit (Review) / View Tests

Interface Overview
Workflow Scenario 1
Client Workstation and Action / Description

Application
1.EMR Client on PC1 Enter patient demographics.
2. EMR Client on PC2 Enter the order for a new test.
3. EMR Client on PC3 Join entered order and open CASE/CardioSoft for the new test.
• Patient demographics, clinical data and test type details are

transferred to CASE/CardioSoft (EMR order ID is part of the
filename).

Interface Overview
Workflow Scenario 1
Client Workstation and Action / Description

Application
4. CASE/CardioSoft on PC3 Conduct test or finish test
• On end of test (when going to Post Test Review screen), the

defined observation values (results) are transferred back (EMR
order ID is part of the filename).
• Go back to EMR (button). The defined observation values

(results) are transferred back again, if changes were made in
Post Test Review screen.
5. EMR Client on PC3 Retrieve results (manually or automatically)
• EMR reads and stores observation values and a reference to

this test.
6. EMR Client on PC2 Join the open order and open CASE/CardioSoft to review the test.
• The reference to the test is used by EMR.
7. CardioSoft Client on PC2 Edit (review) test
• Go Back to EMR (button)
• Defined observation values (results) are transferred back (with

the originally EMR order ID in filename).
8. EMR Client on PC2 Retrieve results (manually orautomatically) and sign document
• EMR reads and stores observation values and a reference to

this test.
• Sign the document to make it part of the patients chart. After

signing, you can only view this test.
9. EMR Client on PC4 Open CASE/CardioSoft for viewing the test
• The reference to the test is used by the EMR.
10. CardioSoft Client on PC4 View the test
Workflow Scenario 2: Data Upload to EMR for Data Migration

Interface Overview
Workflow Scenario 2
Client Workstation and Application Action / Description
1.CASE/CardioSoft on PC1 Start CASE/CardioSoft.
2. CASE/CardioSoft on PC1 Start the upload in System Configuration >>

EMR tab.
• Patient demographics of all existing patients

and references to all existing tests (that are
stored in the CASE/CardioSoft database) are
sent to the EMR (HL7 via TCP/IP or shared
file).
• The EMR needs to read the HL7 messages,

create the patients chart and assign tests.
3. EMR Client on PC2 Open CASE/CardioSoft to view the test
4. CASE/CardioSoft on PC2 View the test.

Interface Overview
Workflow Scenario 3: Manual Reception of Resting ECGs via ECG Writer
Workflow Scenario 3
1.CASE/CardioSoft on PC1 Start CASE/CardioSoft.
2. CASE/CardioSoft on PC1 Enable the receive mode (System Configuration

>> Receive data from ECG device)

Interface Overview
Workflow Scenario 3
3. ECG Writer Send the test via serial interface.
At end of the transmission:
• CASE/CardioSoft on PC1
• Automatic or manual assignment

(selectable in dialog) of the test: A
new patient record is created and
test assigned or test is assigned to an
existing patient. If patient demographics
do not match, the test is stored in a list to
assign it manually.
• Corresponding patient demographics

and a reference to the test are sent to
EMR (HL7 via TCP/IP or shared file) if the
test was assigned successfully.
• EMR
• Read HL7 messages, create the patient’s

chart and assign the test.
4. EMR Client on PC2 Open CASE/CardioSoft to view the test.
Workflow Scenario 4: Automatic Reception of Resting ECGs via ECG Writer

Interface Overview
1.CardioSoft on PC1 Start CardioSoft in the Communication Server

Mode (see CardioSoft Service Manual ). The
dialog for automatic reception of Resting ECGs
via modem comes up (receive mode).

Interface Overview
2. ECG Writer Send the test via modem.
At the end of the transmission:
• CASE/CardioSoft on PC1
• Automatic assignment of test: New

patient record is created and test
assigned or test is assigned to an
existing patient. If patient demographics
do not match, test is stored in a list to
assign it manually.
• Corresponding patient demographics

and a reference to the test are sent to
EMR (HL7 via TCP/IP or shared file) if the
test was assigned successfully.
• EMR
• Read HL7 messages, create the patient’s

chart and assign the test.
3. EMR Client on PC2 Open CASE/CardioSoft tor view the test.
• The reference to the test is used by the EMR.

3
Data Transfer
Data Transfer: EMR to CASE/CardioSoft
• Patient demographics
• Patient ID, Name, DOB, Gender, Race
• Test order (Start / View / Edit)
• Test name (Stress, Resting, Spirometry, ABP)
• Clinical data
• Height / Weight of patient
• Pacemaker
• Attending physician
• Referring physician
• Ordering physician
• Reason for Test
• Medical History
• Medication
Data Transfer: CASE/CardioSoft to EMR

• Reference to the conducted test to edit or view it later.
• Test results (most observation values depend on the type of test)
For all tests:
• Interpretation
• Comment (any comment)
• Extra Questions (two short notes containing a question and response)
For Resting ECG

NOTE:
Also see "Table 1: Resting ECG" on page 31.
• Heart rate

Data Transfer
• BP systolic / diastolic
• PR / QT / QTc interval
• QRS duration
• P / T / QRS axis
• P duration
• Average PP / RR Interval
For Stress Test

NOTE:
Also see "Table 2: Stress Test" on page 35 .
• Max. heart rate
• Max. predicted heart rate
• Max. BP systolic / diastolic
• Max. load (Treadmill, Ergometer)
• Max. ST Level
• Max. TWA (T-Wave Alternans)
• Test protocol (e.g. BRUCE …)
• Total test time
• Stress test type (e.g. Treadmill, Ergometer, Persantine …)
• Baseline heart rate
• Reason for termination
• Time in exercise
For Spirometry
NOTE:
Also see "Table 3: Spirometry" on page 40
• Spirometry test type (Spirometry, Before Bronchodilation, After Bronchodilation)
• Reference values equation (for example, Knudson …)
• FVC (Forced vital capacity)
• FEV1 (Forced expiratory volume in the first second)
• FEV1 / FVC (FEV1 as percentage of FVC)
• Interpretation mode ("CHS" on basis of American Thoracic Society, "Europe" on
basis of ECCS)
• Measurement mode ("ATS" mode, "Envelope" mode)

Data Transfer
For ABP
NOTE:
Also see "Table 4: ABP" on page 46 .
• Systolic / diastolic blood pressure, 24 hour average
• Systolic / diastolic blood pressure, day-time average
• Systolic / diastolic blood pressure, night-time average
• Total recording time
HL7 Dataflow: CASE/CardioSoft – EMR

4
Interface Specification
This interface uses HL7 Version 2.3.
For importing HL7 messages, CASE/CardioSoft also accepts versions 2.2, 2.1, 2.0 or
2.0d.
EMR Interface Configuration

Initial Steps
To run CASE/CardioSoft with an EMR system (EMR mode), perform the following steps:
1. On the EMR
a) Create the emr.ini file in the system folder (c:\winnt\ or c:\windows) with
the following content:
[Installation]
LogicianInstallPathTo=<Your EMR Install Path>
b) Create the following folder: <EMR Install Path>/CardioSoft before starting
the application.
2. On CASE/CardioSoft
a) Enter a valid Option Code XEMR in the System Configuration screen >
Option Code tab.
Interface Configuration to Control CASE/CardioSoft via EMR
After completing the steps in "Initial Steps" on page 24 the EMR tab in System
Configuration is available.

• CASE/CardioSoft needs two communication folders to import and export the HL7
files for Observation Reporting. (These folders can be identical.)
• CASE/CardioSoft imports the <xxx>.emr files from the “Read from”-folder. The EMR
system needs to write these files. CASE/CardioSoft is responsible for deleting them.
• CASE/CardioSoft exports <xxx>.car files to the “Write To”-folder. The EMR system
reads these files and is responsible for deleting them.
These communication folders are written and read from the file:
< EMR Install Path>/CardioSoft/CardioSoft.ini
It is intended, that the EMR system creates this file and writes the entries for the
communication folders to be used by CASE/CardioSoft. However, this file is also
created by CASE/CardioSoft, if it does not exist (Important: Folder <EMR Install
Path>/CardioSoft must exist). In this case, the default values for the communication
folders are used (TMP path of the system, with folders /csoft_emr and /emr_csoft
appended).
See the entries below that are used within the file CardioSoft.ini:
READDIR=<dir path> CASE/CardioSoft output directory (“Write to” in

system configuration dialog)
WRITEDIR=<dir path> CASE/CardioSoft input directory (“Read from” in

system configuration dialog)

Interface Configuration for Data Upload

Data upload (patient demographics and links to the tests) is conducted:
• Manually for data migration (initially existing patient records and tests within
CASE/CardioSoft)
• Automatically when tests from ECG Writers are received and assigned within
CASE/CardioSoft
The settings for the upload are available within the EMR tab.
Depending on how you want to transfer the data, select the corresponding settings.
For HL7 specifications, see "Functions Initiated by CASE/CardioSoft" on page 50.
Interface Configuration for Test Mode
CASE/CardioSoft can be launched in test mode. This means the test is conducted
without an acquisition module (with simulated patient data). To achieve this, the
following settings in the MSH and PID segments of the emr-file need to be edited:
1. Set MSH-11 (Processing ID) to “D”.
2. Set PID-5 Patient Name: “TEST DEMO”
3. Set PID-4 Patient ID: “TEST DEMO 000000”
4. Set PID-7 DOB: “19680428” (not required, internal data is taken)
5. Set PID-8 SEX: “M” (not required, internal data is taken)
6. Set PID-10 RACE: “U” (not required, internal data is taken)

The result file (.car) reflects this data.
Interface Configuration in Terms of User Administration
CASE/CardioSoft in EMR mode bypasses the Login screen, because the EMR client on
this workstation already provides user authentication.
If CASE/CardioSoft has enabled the Password function (System Configuration >>
User List), a mechanism is implemented to use the EMR User ID/Name for confirming
the reports in Post Test Review screen and event logging (System Configuration >>
User List >> Log Setup).
To achieve this, the EMR needs to create the file:
<EMR install path>\cfw,ini.
Each time a user logs in, the EMR writes the current User ID and Name as follows:
CURRENTUSER=George A. Johnson
CURRENTUSERID=gjohnson
<EMR Install Path> is defined in the emr.ini file (See "Initial Steps" on page 24.).

NOTE:
If the EMR does not provide the User ID/Name, confirmation of reports within
CASE/CardioSoft and event logging is possible. But without the User ID/Name, it is
not useful.
HL7 Settings
All HL7 settings are stored in the HL7.ini file in the section [GENERAL]. This file is stored
on the CASE/CardioSoft server (network folder) and is valid for all CASE/CardioSoft
clients.
Most settings are accessed by using the EMR tab. However, the following settings can
be changed manually by modifying HL7.ini.
HL7 Setting Description
GEN_ReqAckFromResponder=1 HL7 in Original Mode: Application Acknowledge

mode (only with TCP/IP; default value is 0)
GEN_AckTimeout=1000 Timeout after an expected Acknowledge

Message from the Responder in ms (value
is valid from 500 to 5000ms; default value is
2000ms)
GEN_MaxSentMess=1 Total number of messages sent before a final

error is assumed (original message and 1
repetition after first occurrence of error; value is
valid from 1 to 5; default value is 2)
GEN_EndOfSegmWithCRLF=0 End of segments with CR/LF (that means all

segments end with CR and LF; 0 means only CR;
default is 1)
Functions Initiated by EMR

The functions New, Edit and View are supported through the EMR interface for the
Resting ECG, Stress Test, Spirometry and ABP modalities.
NOTE:
Holter and external programs are not supported.
New Test Launched by EMR
Launching CASE/CardioSoft
CASE/CardioSoft is launched by EMR with the parameters EMR_N and the file name.
This filename format must be: <Modality>_<ID>.emr.
File Name Value Definitions
<Modality> R_ECG (Resting ECG)

File Name Value Definitions
S_ECG (Stress ECG)
SPIRO (Spirometry)
BPMONC (ABP: Configure ABP Device)
BPMOND (ABP: Read Data from ABP Device)
<ID> Should be used by the EMR as a unique ID, e.g.

Patient-ID plus a document number (order ID).
It is stored in CASE/CardioSoft for each test and
used for the filename of the observation results.
The emr-file must be written by the EMR to the CASE/CardioSoft “Read from” folder,
that is displayed in System Configuration >> EMR tab.
Example for launching CASE/CardioSoft to conduct a Resting ECG:
c:\cardio\cardio.exe EMR_N R_ECG_80-TEST011_42.emr
Path name:
See Win.ini (Folder C:\Winnt or C:\Windows):
CardioInstallPath=C:\Cardio
Matching of Patient ID
The functions New Patient Record, Edit Patient Data, Delete Patient Record and Delete
Examination are completely disabled in CASE/CardioSoft in EMR Mode.
So all patient IDs come from the EMR, except two special cases, Data migration ( See
"Data Upload of Existing CASE/CardioSoft Tests to EMR" on page 50.) and reception
of external tests; e.g., from an ECG Writer (See "Data Upload of External Tests from
ECG Writers" on page 52.).
It is assumed that the EMR system has unique patient IDs.
Patient Management of CASE/CardioSoft searches for the patient referenced in the
message by PID-4. If PID-4 is empty, PID-3 is used.
Use always PID-3 for the EMRs patient ID.
Additionally use PID-4 for existing CASE/CardioSoft patient IDs in case of data
migration (if data was initially uploaded to the EMR database) or in case of receiving
tests from ECG Writers.
If there is a record in the database for this patient, this patient is selected and patient
demographics are updated in the CASE/CardioSoft database. If there is no record
found for this patient, a new record is created and this patient is selected.
Observation Results
Observation results depend on the selected modality. The results are written when
Back to EMR or Post Test Review is clicked.

The observation result filename is:

<Modality>_<ID>.car
whereas <ID> is identical with the incoming <ID> of the .emr-file.
This file is written by CASE/CardioSoft to the “Write to” folder, that is displayed in
System Configuration >> EMR tab.
The units of the result values are static and do not depend on the CASE/CardioSoft
System Configuration settings.
File Handling
CASE/CardioSoft deletes the .emr-file after processing. The EMR is responsible for
deleting the .car file.
Resting ECG
Example for launching CASE/CardioSoft to conduct a Resting ECG test:
R_ECG_80-TEST011_42.emr
MSH|^~\&|CPO_EMR||CARDIOSOFT||20040327110218||ORU|20040327110218001|P|2.3|||NE
PID|1||EMR_PID||MARKHAM^STEVE^||19650101|M||W
PV1|1||SOUTH||||^Winston^Harry^S.|^Ref-L^Ref-F
OBR|1|||R_ECG||20040327110218||||||||||OrderingÔrdering-LÔrdering-F
OBX|1|ST|History||CORONARY ARTERY DISEASE (ICD-414.00)
OBX|1|ST|Reason||Therapy outcome control
OBX|1|ST|Reason||Checkup
OBX|1|ST|Reason||Chest discomfort
OBX|1|ST|Reason||Confirm/Rule out CAD
OBX|1|ST|Reason||Angina Pectoris
OBX|1|ST|Height||72|IN
OBX|1|ST|Weight||160|LB
OBX|1|ST|Pacemaker||Y
OBX|1|ST|Medication||LISINOPRIL|180mg tablets
OBX|1|ST|Medication||HEXORAL|1500ml
OBX|1|ST|Medication||ASPIRIN|1100mg
OBX|1|ST|Medication||ISOSORB|175mg
Items of Interest
MSH-3=Sending App CPO_EMR
MSH-4=Receiving App CARDIOSOFT

Items of Interest
MSH-10=Message Control ID Unique ID
MSH-11=Operating mode P (Production)

D (Debug)
PID-3=Patient ID EMR Internal Patient ID
PID-4=Alternate ID CardioSoft ID (if one exists)
PID-5=Patient Name used: last^first^middle
PID-7=Date of Birth yyyymmdd
PID-8=Sex M, F, U
PID-10=Race See Spec for correct values
PV1-7=Attending Phys. used: ^last^first^middle^^^degree
PV1-8=Referring Phys used: ^last^first^middle^^^degree
OBR-4=Test Name R_ECG (Resting_ECG)
OBR-16=Ordering Phys ^last^first^middle^^^degree
OBX-3=Observation Name obs name (e.g. History, Reason, Height, Weight…)
OBX-5=Observation Value numeric or text value for observation
OBX-6=Units If applicable, the unit assoc. with the value
NOTE:
The “Medication” Observation name is reused for each medication sent. Each
medication is delivered with the medication name in OBX-3 and the dose in
OBX-5.
Resting ECG is started and the following clinical data is stored in CASE/CardioSoft:
• Attending Physician
• Referring Physician
• Ordering Physician
• Reason for Test (up to 4, rest is discarded)
• Medical-History
• Medication (up to 5, rest is discarded)
The EMR should use the CASE/CardioSoft default list in the Reason for Test combo
box. Medical-History and Medication are “Read Only” in CardioSoft.
After clicking Post Test Review or Back to EMR, the following data is provided by the
Resting ECG module:

Table 1: Resting ECG
CASE/CardioSoft ID Unit Description or Note
OTHER_REF Text Internal reference to test (to be

used by the EMR for editing or
viewing)
HR bpm Heart rate on

electrocardiogram
BP Systolic mmHg Blood pressure, systolic
BP Diastolic mmHg Blood pressure, diastolic
PR ms PR interval, electrocardiogram
QT ms QT interval, electrocardiogram
QTc ms Qt interval/qt interval,

electrocardiogram, corrected
for heart rate
QRSD ms QRS duration,

electrocardiogram
P Axis ° (deg P wave axis, electrocardiogram
T Axis ° (deg) T wave axis, electrocardiogram
EKG QRS axis ° (deg) Electrocardiogram QRS axis
P ms P-duration (from P-onset to P-

offset)
PP ms Average PP interval
RR ms Average RR interval
Interpretation Text Electrocardiogram

interpretation (clinical
interpretation of diagnosis)
Comment Text Any comment: workflow,

personal, non-clinical data. (60
char max)
Question 1 Text Short note containing a

question and response (52 char
max)

max)
Example for Resting ECG Observation Results:

R_ECG_80-TEST011_42.car:
MSH|^~\&|CARDIOSOFT||CPO_EMR||20040812174632||ORU|20040812174632001|P|2.3|||NE
PID|1||EMR_PID||MARKHAM^STEVE^^^^||19650101|M||W
OBR|1|||R_ECG|||20040812174627|||||||20040812174627||||EK||||20040812174627|||F
OBX|1|TX|OTHER_REF||000005_R_ECG_20040812174627.csoft
OBX|1|ST|HR||60|bpm|||||F
OBX|1|ST|BP Systolic|||mmHg|||||F
OBX|1|ST|BP Diastolic|||mmHg|||||F
OBX|1|ST|PR||164|ms|||||F
OBX|1|ST|QT||364|ms|||||F
OBX|1|ST|QTc||364|ms|||||F
OBX|1|ST|QRSD||86|ms|||||F
OBX|1|ST|P Axis||34|°|||||F
OBX|1|ST|T Axis||48|°|||||F
OBX|1|ST|EKG QRS axis||44|°|||||F
OBX|1|ST|P||88|ms|||||F
OBX|1|ST|PP||1000|ms|||||F
OBX|1|ST|RR||1000|ms|||||F
OBX|1|ST|Interpretation||Normal sinus rhythm\.br\Normal ECG\.br\||||||F
OBX|1|ST|Comment||This is the comment||||||F
OBX|1|ST|Question 1||Smoker Yes||||||F
OBX|1|ST|Question 2||Athlete No||||||F
Items of Interest
MSH-3, MSH-4 Names reversed to indicate opposite send

direction
OBR-4=Test Name R_ECG (Resting_ECG)
OBR-18=Document Type EK (EKG Report)
OBR-25=Result status F indicates normal status
OBX-3=Observation Name Obs name (e.g. History, Reason, Height, Weight…)
OBX-5=Observation Value Numeric or text value for observation
Question 1 & Question 2 The value field contains both the question and
answer (Prompt: value)
OTHER_REF Value for this OBX is the reference to the test.

CASE/CardioSoft creates and stores an HL7-file (internally) to reference the conducted

test. This filename is located in the OBX segment with OBX-3 OTHER_REF and must be
used by the EMR to edit or view this test.
When no test is started and button Back to EMR is pressed, an Abort message is sent.
The Abort message has the following format:
OBR|1|||R_ECG|||20040812174812|||||||20040812174812||||EK||||20040812174812|||X
OBX|1|ST|Comment||No test performed!||||||F
Items of Interest
OBR-4=Test Name Resting_ECG
OBR-25=Result status X indicates aborted test
OBX record Is used to return comment providing the reason

for aborting the test. The comment is generated
by the application. It is not entered by the user.
Stress ECG
Example for launching CASE/CardioSoft to conduct a Stress ECG test:

S_ECG_80-TEST011_43.emr
PID|1||EMR_PID||MARKHAM^STEVE||19650101|M||W
OBR|1|||S_ECG||20040327110218||||||||||OrderingÔrdering-LÔrdering-F
OBX|1|ST|History||ANGINA, FUNCTIONAL CLASS III (ICD-786.5)
OBX|1|ST|Reason||Abnormal ECG
OBX|1|ST|Reason||Chest Discomfort
OBX|1|ST|Reason||Vascular Disease
OBX|1|ST|Reason||Pre-Op Evaluation
OBX|1|ST|Reason||Evaluation
OBX|1|ST|Medication||LISINOPRIL 80mg tablets
Items of Interest
MSH-11=Operating mode P (Production), D (Debug)
PID-8=Sex M, F, U

Items of Interest
OBR-4=Test Name S_ECG (Stress ECG)
OBR-16=Ordering Phys used: ^last^first^middle^^^degree
NOTE:
OBX-5.
Stress test is started and clinical data is stored in CASE/CardioSoft:
• Medical-History
The EMR should use the CASE/CardioSoft default list in the Reason for Test list.
Medical-History and Medication are “read only” in CardioSoft.
After clicking Post Test Review or Back to EMR is pressed, the following data is
provided by the Stress ECG module:
Table 2: Stress Test
CASE/Cardio Soft ID Unit Description
OTHER_REF Text Internal Reference to test

(to use by EMR for editing or
viewing)
Max HR bpm Maximum heart rate achieved
Max predicted HR bpm Maximum predicted heart rate
Max BP Systolic mmHg Blood pressure, systolic,

maximum exercise

CASE/Cardio Soft ID Unit Description
Max BP Diastolic mmHg Blood pressure, diastolic,

maximum exercise
Max Load METS Maximum load, treadmill
Max Load Watt Maximum load, ergometer
Max ST Level mv Maximum ST level (maximum

ST depression)
Max TWA uV Maximum TWA (T-Wave

alternans)
Protocol Text Protocol, as in load sequence

of a stress test such as Bruce,
Naughton, Cornell, etc.
Total Test Time Text Exercise tolerance test, total

test time
nterpretation Text Stress electrocardiogram,

interpretation

char max)

max)

max)
Stress Test Type Text Stress test type (Treadmill,

Egometer, Persantine…)
Baseline HR bpm Resting HR
Reas. For Term. Text Reason for Termination

(Fatigue)
Total Ex Time Text Time in Exercise
Example for Stress ECG Observation Results

S_ECG_80-TEST011_43.car
OBR|1|||S_ECG|||20040812175027|||||||20040812175027||||EK||||20040812175027|||F
OBX|1|TX|OTHER_REF||000002_S_ECG_20040812175027.csoft
OBX|1|ST|Max HR||60|bpm|||||F
OBX|1|ST|Max predicted HR||158|bpm|||||F
OBX|1|ST|Max BP Systolic||155|mmHg|||||F
OBX|1|ST|Max BP Diastolic||99|mmHg|||||F
OBX|1|ST|Stress Test Type||Treadmill Stress Test||||||F
OBX|1|ST|Baseline HR||60|bpm|||||F
OBX|1|ST|Reas. for Term.||Leg discomfort||||||F
OBX|1|ST|Max Load||2.90|METS|||||F
OBX|1|ST|Protocol||BRUCE||||||F
OBX|1|ST|Total Ex Time||01:05||||||F
OBX|1|ST|Total Test Time||01:42||||||F
OBX|1|ST|Interpretation||Reasons for Termination: Leg discomfort\.br\Summary: Resting ECG: normal.
Functional Capacity: above average (>20%). \.br\Conclusion: This is the conclusion||||||F
OBX|1|ST|Comment||This is a comment||||||F
OBX|1|ST|Question 2||Athlete yes||||||F
Items of Interest

direction
answer


used by the EMR to edit/view this test.
When no test is started and you click Back to EMR, an Abort message is sent. The
Abort message has the following format:
OBR|1|||S_ECG|||20040812174812|||||||20040812174812||||EK||||20040812174812|||X
Items of Interest

After clicking Back to EMR, if the test is modified during Post Test Review, the .car file
is written again.
Spirometry
Example for launching CASE/CardioSoft to conduct a Spirometry test:

SPIRO_80-TEST011_44.emr
OBR|1|||SPIRO||20040327110218||||||||||OrderingÔrdering-LÔrdering-F
OBX|1|ST|History||DEPRESSION (ICD-311.)
OBX|1|ST|Reason||Respiratory problems
OBX|1|ST|Reason||Shortness of breath
OBX|1|ST|Reason||Pain
OBX|1|ST|Reason||Follow-up
Items of Interest
PID-8=Sex M, F, U
PV1-7=Attending Phys used: ^last^first^middle^^^degree
OBR-4=Test Name SPIRO (Spirometry)

Items of Interest
NOTE:
OBX-5.
Spirometry test is started and clinical data is stored in CASE/CardioSoft.
• Medical-History
The EMR should use the CASE/CardioSoft default list in the Reason for Testlist.
After clicking Post Test Review or Back to EMR the following data is provided by the
Spirometry module:
Table 3: Spirometry
CASE/ Cardio Soft ID Units Description

viewing)
SpiroTestType Text Spirometry test type
RefValEquation Text Spirometry reference values

equation (name of formula
used for calculation of
reference values such s ECCS,
Austrian, ECCS/ZAP, Forche,
NHANESIIII, Knudson, Finland,
Brazil)
Interpretation Text Spirometry interpretation

char max)


max)

max)
FVC l (liters) Forced vital capacity
FEV1 l (liters) Forced expiratory volume in 1st

second
FEV1FVC % (percent) FEV1/FVC (FEV1 as a

percentage of FVC)
SPI Interpr. Mode Text Interpretation Mode; 2 modes

are available: "CHS" on the
basis of ATS (American Thoracic
Society), "Europe" on the basis
of ECCS
SPI Meas. Mode Text Measurement Mode; "ATS"

mode (mostly used in US) or
"Envelope" mode
Example for Spirometry Observation Results
SPIRO_80-TEST011_44.car
OBR|1|||SPIRO|||20040812175548|||||||20040812175548||||DR||||20040812175548|||F
OBX|1|TX|OTHER_REF||000003_SPIRO_20040812175548.csoft
OBX|1|ST|Comment||This is the comment||||||F
OBX|1|ST|Question 1|| Smoker Yes||||||F
OBX|1|ST|Question 2||Athlete No||||||F
OBX|1|ST|Interpretation||Normal spirometry||||||F
OBX|1|ST|RefValEquation||Knudson||||||F
OBX|1|ST|SpiroTestType||Spirometry||||||F
OBX|1|ST|FVC||3.28|l|||||F
OBX|1|ST|FEV1||2.88|l|||||F
OBX|1|ST|FEV1FVC|| 87|%|||||F
OBX|1|ST|SPI Interpr. Mode||CHS||||||F
OBX|1|ST|SPI Meas. Mode||Envelope||||||F

Items of Interest

direction
OBR-4=Test Name SPIRO (Spirometry)
OBR-18=Document Type DR (Diagnostic Report Other)
answer
OTHER_REF Value for this OBX is the reference to the test

When no test is started and you click Back to EMR, an Abort message is sent. The
OBR|1|||SPIRO|||20040812174812|||||||20040812174812||||DR||||20040812174812|||X
Items of Interest
OBR-4=Test Name Stress ECG

by the application. It is not entered by the user
After clicking Back to EMR , if the test is modified during Post Test Review, the .car file
is written again.
ABP: Configuration of ABP Device
Example for launching CASE/CardioSoft to configure an ABP device:

BPMONC_80-TEST011_45.emr
OBR|1|||BPMONC||20040327110218||||||||||OrderingÔrdering-LÔrdering-F
OBX|1|ST|History||Text of the history goes here.
OBX|1|ST|Reason||Therapy outcome control
OBX|1|ST|Reason||Suspected sleep-apnea syndrome
OBX|1|ST|Reason||Kidney transplant
OBX|1|ST|Reason||Reason for Test-4
Items of Interest
PID-8=Sex M, F, U
OBR-4=Test Name BPMONC (ABP: Configuration)

Items of Interest
NOTE:
OBX-5.
ABP modality is started and clinical data is stored in CASE/CardioSoft.
• Medical-History
The EMR should use the CASE/CardioSoft default list in the Reason for Test list.
In the ABP modality the user can clear data in the device and program the device. The
Download Data button is disabled.
On clicking Back to EMR , ABP module provides the Configuration Status.
Example for ABP Observation Results (Configuration Status)
BPMONC_80-TEST011_45.car
OBR|1|||BPMONC|||20040812174812|||||||20040812174812||||DR||||20040812174812|||X
OBX|1|ST|Comment||Setup of BP device successfully completed!||||||F
Items of Interest
OBR-4=Test Name BPMONC (ABP: Configuration)
OBX record Is used to return comment providing the

configuration status. The comment is generated
by the application. It is not entered by the user

This configuration status is only informational. CASE / CardioSoft does not store
configuration status. An abort message is sent when CASE/CardioSoft cannot
establish a connection to the ABP device. The OBX record (OBX-5) returns the reason
for aborting the test .
ABP: Read Data from ABP Device
Example for launching CASE/CardioSoft to read data from an ABP device:
BPMOND_80-TEST011_46.emr
OBR|1|||BPMOND||20040327110218||||||||||OrderingÔrdering-LÔrdering-F
OBX|1|ST|History||Text of the history goes here.
Items of Interest
PID-8=Sex M, F, U

Items of Interest
OBR-4=Test Name BPMOND (ABP: Read Data from ABP Device)
NOTE:
Note that the “Medication” Observation name is reused for each medication sent.
Each medication is delivered with the medication name in OBX-3 and the dose in
OBX-5.
ABP test is started and following clinical data is stored in CASE/CardioSoft:
• Medical-History
The EMR should use the CASE/CardioSoft default list in the Reason for Testlist.
After connection to the ABP device is established, the user can download data from
the BP monitor. The program and clear data options in the ABP device are disabled.
After you click Download Data , the following results are provided by the ABP module:
Table 4: ABP

viewing)
24h aver BPsys mmHg Systolic blood pressure, 24-hr

average
24h aver BPdia mmHg Diastolic blood pressure, 24-hr

average

Interpretation Text Blood pressure interpretation,

ambulatory

char max)

max)

max)
Day aver BPsyst mmHg Day Time Average Systolic
Day aver BPdia mmHg Day Time Average Diastolic
Night aver BPsyst mmHg Night Time Average Systolic
Night aver BPDia mmHg Night Time Average Diastolic
ABP Tot Rec Time Text Total Recording Time
Example for Observation Results (Data from ABP Device):
BPMOND_80-TEST011_46.car
PID|1|| EMR_PID||MARKHAM^STEVE^^^^||19650101|M||W
OBR|1|||BPMOND|||20040812175548|||||||20040812175548||||DR||||20040812175548|||F
OBX|1|TX|OTHER_REF||000003_BPMOND_20040812175548.csoft
OBX|1|ST|Comment||This is a comment||||||F
OBX|1|ST|Question 2||Athlete Yes||||||F
OBX|1|ST|Interpretation||||||||F
OBX|1|ST|24h aver BPsys||133.3 |mmHg|||||F
OBX|1|ST|24h aver BPdia|| 86.6 |mmHg|||||F
OBX|1|ST|Day aver BPsyst||133.3 |mmHg|||||F
OBX|1|ST|Day aver BPdia|| 86.6 |mmHg|||||F
OBX|1|ST|Night aver BPsyst|||mmHg|||||F
OBX|1|ST|Night aver BPdia|||mmHg|||||F
OBX|1|ST|ABP Tot Rec Time||0:10 h||||||F

Items of Interest

direction
answer
OTHER_REF Value for this OBX is the reference to the test
CASE/CardioSoft creates and stores an HL7 file (internally) to reference the conducted
If data download in the APB device is not possible, an abort message is sent. The
OBR|1|||BPMOND|||20040812174812|||||||20040812174812||||DR||||20040812174812|||X
OBX|1|ST|Comment||Ambulatory Blood Pressure test/ setup not done!||||||F
Items of Interest

After clicking Back to EMR , if the test is modified duringPost Test Review, the .car file
is written again .
Edit Test
Case/CardioSoft is launched in Edit-Mode by the EMR with the parameters:
EMR_E <internal patient id>_<modality>_<time of teststamp>.csoft.

The EMR needs to take the filename with the extension .csoft (this is the document
reference) out of the .car-file, that was written to the “Write To” folder by CASE/
CardioSoft, after a new test was finished.
It is located in OBX-5 of that OBX segment, whose OBX-3 value is OTHER_REF.
Examples for launching CASE/CardioSoft in Edit-Mode:
Edit a Resting ECG test:
C:\Cardio\Cardio.exe EMR_E 000002_R_ECG_20050802135947.csoft
Edit a Stress ECG test:
C:\Cardio\Cardio.exe EMR_E 000003_S_ECG_20050902145947.csoft
Edit a Spirometry test:
C:\Cardio\Cardio.exe EMR_E 000004_SPIRO_20051002155947.csoft
Edit an ABP test::
C:\Cardio\Cardio.exe EMR_E 000005_BPMOND_20051102165947.csoft
Path name:
See Win.ini (Folder C:\Winnt or C:\Windows) in section [CARDIO]:
CardioInstallPath=C:\Cardio
After you click Back to EMR, data is passed back as .car file, even if no changes
are made. The format is identical as described in “"Resting ECG" on page 29” for
Resting ECG, “"Stress ECG" on page 33” for Stress ECG, “"Spirometry" on page 38”
for Spirometry and “"ABP: Read Data from ABP Device" on page 45” for ABP Read
Data.
The ID in the .car filename is identical to that was received within the .emr filename,
when this test was initially conducted.
The EMR is responsible to delete the file.
View Test
CASE/CardioSoft is launched in View Only-Mode by the EMR with the parameters
EMR_O <internal patient id>_<modality>_<time of teststamp>.csoft.
The EMR needs to take the filename with the extension .csoft (this is the document
reference) out of the .car-file, that was written to the “Write To” folder by CASE/
CardioSoft, after a new test was finished.
It is located in OBX-5 of that one OBX segment, that has the string OTHER_REF as
OBX-3.
With the CASE/CardioSoft Install program:
• The system variable “Path” is expanded with the location of the csoft-file.
• The file extension .csoft is mapped to <CASE/CardioSoft Local Install Folder>/
Cardio.exe EMR_O <xxx>.csoft.

To view tests, CASE/CardioSoft can be started:

• either by using Cardio.exe and reading the Path name out of Win.ini (as stated in
"“Edit Test” on page 38")
• or directly by launching the .csoft-file
Examples for launching CASE/CardioSoft in View Only-Mode:
View a Resting ECG test:
C:\Cardio\Cardio.exe EMR_O 000002_R_ECG_20050802135947.csoft
or directly launch
000002_R_ECG_20050802135947.csoft
View a Stress ECG test:
C:\Cardio\Cardio.exe EMR_O 000003_S_ECG_20050902145947.csoft
or directly launch
000003_S_ECG_20050902145947.csoft
View a Spirometry test:
C:\Cardio\Cardio.exe EMR_O 000004_SPIRO_20051002155947.csoft
or directly launch
000004_SPIRO_20051002155947.csoft
View an ABP test:
C:\Cardio\Cardio.exe EMR_O 000005_BPMOND_20051102165947.csoft
or directly launch
00005_BPMOND_20051102165947.csoft
After you click Back to EMR, no data is passed back.
Functions Initiated by CASE/CardioSoft

CASE/CardioSoft is started directly via an icon on the desktop.
Data Upload of Existing CASE/CardioSoft Tests to EMR
In cases where an EMR is newly installed into an existing CASE/CardioSoft
environment, CASE/CardioSoft provides one-time upload of data from CASE/
CardioSoft to the EMR.
This ensures that a chart exists in the EMR for every patient on CASE/CardioSoft. In
addition, CASE/CardioSoft provides document references, that allows access to test
reports.

For each patient in the CASE/CardioSoft database a demographics file is created,

then for each test a document reference file is created. All files are copied to a folder
or data is sent via TCP/IP communication. See System Configuration >> EMR Tab.
Acknowledging is configurable manually in HL7.ini: See "HL7 Settings" on page 27.
Patient Demographics File (HL7-message: ADT,

A04)
Filename <pid>_<modality>.hd
PID CASE/CardioSoft Internal Patient ID
Modality R_ECG, S_ECG, SPIRO, BPMOND
Example for a Demographics File:

Name: 000002_S_ECG.hd
Format:
MSH|^~\&|CARDIOSOFT||LINLOGIC|LOGICIAN|20040327110218||ADTÂ04|20040327110218001|P|2.3|||
NE
EVN|A04|20040327110218||
PID|1||Cardiosoft_PID||MARKHAM^STEVE^^^^||19650101|M||W
Document Reference File (HL7-message: MDM,

T02)
Filename <pid>_<modality>_<time of testtimestamp>.ht
PID CASE/CardioSoft Internal Patient ID
Timestamp time of test yyyymmddhhmmss (time of test)
Modality R_ECG, S_ECG, SPIRO, BPMOND
Example for Document Reference File:

Name: 000002_R_ECG_20040504140211.ht
Format:

MSH|^~\&|CARDIOSOFT||LINKLOGIC|LOGICIAN|20040327110218||MDM^T02|20040327110218001|P|
2.3|||NE
EVN|T02|20040504140211||
PID|1||Cardiosoft_PID||MARKHAM^STEVE||19650101|M||W
TXA||EK|TX|20040504140211||20040504140211||||||000002_R_ECG_20040504140211||||||
OBX|1|ST|||CASE/CardioSoft: Resting ECG||||||F
OBX|1|ST|||\.br\\.br\\.br\To review the test, click on the paperclip icon to the right.||||||F
OBX|1|TX|OTHER_REF||000002_R_ECG_20040504140211.csoft
Items of interest:
TXA-2 Document Type: DR for Diagnostic Report other

or EK for EKG Report
TXA-4 Time of Test
TXA-6 Time of Test
TXA-12 Unique Document number: (<internal patient

id>_<modality>_<time of test>) Modality: R_ECG,
S_ECG, SPIRO, BPMOND. To support legacy
tests from CASE/CardioSoft releases prior V5.0,
R_ECG42, S_ECG42 are used. These are old
versions of stress and Resting ECG.
First OBX-5 Text: CASE/CardioSoft <Modality> report
NOTE:
If the EMR wants to launch a new test with one of the uploaded patient IDs, EMR
must use PID-4 of the uploaded A04 messages for PID-4 of the emr file and use
the EMR patient ID for PID-3 of the emr file.
Data Upload of External Tests from ECG Writers
When a test is received from an ECG Writer (System Configuration >> Receive Data
from ECG Device), CASE/CardioSoft does the Patient ID matching as follows:
• If External Patient ID is found:
• If Patient’s Last Name and First Name and Gender and Date Of Birth are
identical, assign test in CASE/CardioSoft to the patient’s chart
• If different, assign the test manually (Side by Side-Dialog comes up)
• If External Patient ID is not found:
• Use received Patient ID and patient demographic data to create a new patient
record in the database
• Assign this test
For each test that is received from an ECG Writer and assigned to the CASE/
CardioSoft database, a patient demographics file and document reference file are
created and written to a folder or sent via TCP/IP to the EMR.
Acknowledging is configurable manually in HL7.ini: See "HL7 Settings" on page 27.
The same settings are used as for data migration of existing CASE/CardioSoft tests in
"Data Upload of Existing CASE/CardioSoft Tests to EMR" on page 50. (See System
Configuration >> EMR Tab).
The format of Patient demographics file and document reference file are identical to
"Data Upload of Existing CASE/CardioSoft Tests to EMR" on page 50.

5
HL7 Messages
General
The abstract message definition syntax used to describe the supported HL7
messages is consistent with the syntax used in the HL7 specification, version 2.3.
Although not required, it is preferred that Ignored or Not Used message segments not
be included in a supported HL7 message. When present, Ignored message segments
are ignored and CASE/CardioSoft performs no data validation. When present, Not
Used message segments are parsed and CASE/CardioSoft validates the data. If there
is invalid data, CASE/CardioSoft generates an error and does not import the file or the
segment with the invalid data.
HL7-Errors are logged in HL7_ERR.LOG with timestamp, reason of error plus reference
to the HL7-Message. The HL7 message itself is completely stored by using MSH-10 as
filename (<MSH-10>.log). The erroneous field is marked to identify the issue. If MSH-10
is not available, the type of error is only logged in HL7_ERR.LOG.
Legend
The following legend is used throughout the document.
Value Description
R Required. This field is required to have valid data. Missing or invalid data causes CASE/
CardioSoft to generate an error and to not import the file or the segment with the
missing or invalid data.
O Optional. This field is not required to have data. On import, if data is provided, it is
validated. If the data is invalid, CASE/CardioSoft generates an error and does not
import the file or the segment with the invalid data. On export, if CASE/CardioSoft has
data, it exports it.
C Conditional. Data may be either required or optional, depending on the condition. For
further clarification, read the associated footnote.
I Ignored. Data is not required and it is not used in CASE/CardioSoft. If there is data,
CASE/CardioSoft does not validate it.
N Not Used. Data is not required and it is not used in CASE/CardioSoft. However, if data
is present, CASE/CardioSoft parses and validates the data. If the data is invalid, CASE/
CardioSoft generates an error and does not import the file or the segment with the
invalid data.
U Used. CASE/CardioSoft exports data in this field.

HL7 Messages
ORU – Observation Reporting

The ORU message supports the import (patient demographics, observation request
and clinical data) and export of observation data (including link to the report). It uses a
subset of the complete HL7 message set for Observation Reporting and only includes
support for the ORU message.
Each ORU message contains one OBR message segment in which observations
were documented. Nested under the OBR message segment are one or more OBX
message segments, one for each documented observation.
Legend: R = Required, O = Optional, C = Conditional, I = Ignored
Message Segments Import Export
ORU
MSH R R
PID R [0] R [0]
[{NTE}] I I
[PV1] O I
[ORC] I I
OBR R [1] R [1]
{[NTE]} I I
{[OBX]} O O
{[NTE]} I I
[DSC] I [2] I [2]
MSH C [3] C [3]

HL7 Messages
Message Segments Import Export
ORU
MSA C [3] C [3]
[ERR] I I
Note Description
[0] Although this message segment is considered optional in the HL7

specification, CASE/CardioSoft requires it. One PID segment per
message is allowed.
[1] One OBR segment per message is allowed.
[2] The application-specific HL7 message continuation protocol is not

supported.
[3] Acknowledging is only supported in Upload mode.
ORU Message Segments
ORU-MSH – Message Header
Legend: R = Required, O = Optional, C = Conditional, N = Not Used, U = Used
MSH Segment
CASE/CardioSoft Applicability
Seq Length Data HL7 Element Name Import Export

Type table
1 1 ST Field Separator R U
2 4 ST Encoding Characters R U
3 40 HD Sending Application O U
4 20 HD Sending Facility O U
5 40 HD Receiving Application N C [1]
6 30 HD Receiving Facility N C [2]
7 26 TS Date/Time Of O U
Message
8 40 ST Security N N
9 7 CM 76 Message Type R [3] U [3]
10 20 ST Message Control ID R [4] U [4]
11 3 PT 103 Processing ID R [5] U

HL7 Messages
MSH Segment

Type table
12 8 ID 104 Version ID R [6] U
13 15 NM Sequence Number N N
14 180 ST Continuation Pointer N N
15 2 ID 155 Accept Ack Type O [7] N
16 2 ID 155 Application Ack Type N [8] U [8]
17 2 ID Country Code N N
18 6 ID 211 Character Set N N
19 60 CE Principal Language N N
Of Message
Note Description
[1] MSH-5 contains MSH-3 of the initiating system, if we are the responder
[3] The supported values for Message Type include:

• ORU = Unsolicited transmission of an observation
• ACK = General acknowledgment message
NOTE:
The second component, trigger event, is ignored on import and not used on
export.
[4] On Import, MSH-10 is used as a unique ID to log potential errors of this HL7 message.
In this case the HL7 message is stored with MSH-10 as filename (<MSH-10>.log).
Reason of error plus reference to this filename is stored in file HL7_ERR.Log. For
the error file location, see setting in EMR-tab in system configuration screen of
CASE/CardioSoft. On Export, the creation time of the message is used for MSH-10
(time stamp yyyymmddhhmmssxxx, where <xxx> is a sequence number in case of
identical time stamp).
[5] The supported values for Processing ID include:

• D = Debugging
• P = Production
NOTE:
D is used, if interface is in test mode with simulated patient data: See "Interface
Configuration for Test Mode" on page 26.

HL7 Messages
Note Description
[6] The supported values for Version ID include:

• 2.0 = Release 2.0, Sept. 1988
• 2.0D = Release 2.0D, Oct. 1988
• 2.1 = Release 2.1, March 1990
• 2.2 = Release 2.2, December 1994
• 2.3 = Release 2.3, April 1997
[7] In this mode only NE (Never) is supported.
[8] Application acknowledgment is currently unsupported on import and export. On

export, the value NE is used. The Ack types are still validated for import.
ORU-PID – Patient Identification
PID Segment
Seq Length Data HL7Table Element Import Export

Type Name
1 4 SI Set ID - N N
Patient ID
2 20 CX Patient ID N N
(External ID)
3 20 CX Patient ID R [1] U [1]

(Internal ID)
4 30 CX Alternate O [2] O [2]

Patient ID-
PID
5 48 XPN Patient R U
Name
6 48 XPN Mother’s N N
Maiden
Name
7 26 TS Date/Time O O
of Birth
8 1 IS 0001 Sex O [3] U
9 48 XPN Patient N N
Alias

HL7 Messages
PID Segment

Type Name
10 1 IS 0005 Race O [4] O
11 106 XAD Patient N N

Address
12 4 IS County N N
Code
13 250 XTN Phone N N

Number -
Home
14 250 XTN Phone N N

Number -
Work
15 60 CE 0296 Primary N N
Language
16 1 IS 0002 Marital N N
Status
17 3 IS 0006 Religion N N
18 20 CX Patient N N
Account
Number
19 11 ST SSN N N
Number -
Patient
20 25 DLN Driver’s N N
License
Number-
Patient
21 20 CX Mother’s N N
Identifier
22 3 IS 0189 Ethnic N N
Group
23 60 ST Birth Place N N
24 2 ID 0136 Multiple N N
Birth
Indicator
25 2 NM Birth Order N N
26 4 IS 0171 Citizenship N N

HL7 Messages
PID Segment

Type Name
27 60 CE 0172 Veterans N N
Military
Status
28 80 CE Nationality N N
29 26 TS Patient N N
Death Date
and Time
30 1 ID 0136 Patient N N
Death
Indicator
Note Description
[1] PID-3, Patient ID (Internal ID), is assumed to contain the patient identifier of the
EMR system used to match the import data with a CASE/CardioSoft patient ID, if
PID-4 is not available (See "General" on page 54.).
[2] PID-4, Alternate Patient ID, is assumed to be the CASE/CardioSoft’s Patient’s ID,
that was previously uploaded to the EMR database (data migration of existing
patients and tests). If available, PID-4 is used primarily to access to existing CASE/
CardioSoft’s Patient IDs. Although HL7 states a length of 20, with CASE/CardioSoft
a maximum length of 30 is possible (due to data migration of existing patients and
tests).
[3] The supported values for Sex include: F = FemaleM = Male O = Other (treated as
Unknown) U = Unknown
[4] The supported values for Race include:
Value = Definition >> CASE/CardioSoft
On Import (if not B Black Black

supported, CASE/
C Chinese Asian
CardioSoft uses
<Unknown>) H Hispanic Hispanic
J Japanese Asian
N Native Am. Native American
0 Orient./Asian Asian
P Pacific Isl.r Pacific Islander
W White Caucasian
T Other Unknown
U Undeterm. Unknown (Default)

HL7 Messages
Note Description
On Export (if Asian Black O Oriental/Asian

not supported, Caucasian BlackWhite
B
<Unknown> is used) HispanicNative Hispanic Native
American Oriental W American
Pacific Islander Oriental/Asian
Unknown H Pacific Islander
N Undetermined
(default)
O
P
U
ORU-PV1 – Patient Visit
PV1 Segment

Type Name
1 4 SI Set ID- N N
PV1
2 1 IS 0004 Patient N N
Class
3 80 PL Assigned N N
Patient
Location
4 2 IS 0007 Admission N N
Type
5 20 CX Preadmit N N
Number
6 80 PL Prior N N
Patient
Location
7 60 XCN 0010 Attending O [1] N

Doctor
8 60 XCN 0010 Referring O [1] N

Doctor
9 60 XCN 0010 Consulting N N

Doctor

HL7 Messages
PV1 Segment

Type Name
10 3 IS 0069 Hospital N N
Service
11 80 PL Temporary N N
Location
12 2 IS 0087 Pre- N N
admit
Test
Indicator
13 2 IS 0092 Readmission
N N
Indicator
14 3 IS 0023 Admit N N
Source
15 2 IS 0009 AmbulatoryN N
Status
16 2 IS 0099 VIP N N
Indicator
17 60 XCN 0010 Admitting N N

Doctor
18 2 IS 0018 Patient N N
Type
19 20 CX Visit N N
Number
20 50 FC 0064 Financial N N
Class
21 2 IS 0032 Charge N N
Price
Indicator
22 2 IS 0045 Courtesy N N
Code
23 2 IS 0046 Credit N N
Rating
24 2 IS 0044 Contract N N
Code
25 8 DT Contract N N
Effective
Date

HL7 Messages
PV1 Segment

Type Name
26 12 NM Contract N N
Amount
27 3 NM Contract N N
Period
28 2 IS 0073 Interest N N
Code
29 1 IS 0110 Transfer N N
to Bad
Dept
Code
30 8 DT Transfer N N
to Bad
Dept
Date
31 10 IS 0021 Bad Debt N N

Agency
Code
32 12 NM Bad Debt N N
Transfer
Amount
33 12 NM Bad Debt N N
Recovery
Amount
34 1 IS 0111 Delete N N
Account
Indicator
35 8 DT Delete N N
Account
Date
36 3 IS 0112 Discharge N N
Disposition
37 25 CM 0113 Discharged N N
to
Location
38 2 IS 0114 Diet Type N N
39 2 IS 0115 Servicing N N
Facility

HL7 Messages
PV1 Segment

Type Name
40 1 IS 0116 Bed N N
Status
41 2 IS 0117 Account N N
Status
42 80 PL Pending N N
Location
43 80 PL Prior N N
Temporary
Location
44 26 TS Admit N N
Date/
Time
45 26 TS Discharge N N
Date/
Time
46 12 NM Current N N
Patient
Balance
47 12 NM Total N N
Charges
48 12 NM Total N N
Adjustments
49 12 NM Total N N
Payments
50 20 CX 0192 Alternate N N
Visit ID
51 1 IS 0326 Visit N N
Indicator
52 60 XCN 0010 Other N N

Healthcare
Provider
Note Description
[1] Attending and Referring Doctor: Part of CASE/CardioSoft test information
ORU-OBR – Observation Request

HL7 Messages
OBR Segment
Seq Length Data HL7Table Element Name Import Export

Type
1 4 SI Set ID - OBR N N
2 75 EI Placer Order N N
Number
3 75 EI Filler Order N N
Number
4 200 CE Universal Service R [0] U [0]

ID
5 2 ID Priority N N
6 26 TS Requested Date/ N N
Time
7 26 TS Observation Date/ N U [1]

Time
8 26 TS Observation End N N
Date/Time
9 20 CQ Collection Volume N N
10 60 XCN Collector Identifier N N
11 1 ID 0065 Specimen Action N N

Code
12 60 CE Danger Code N N
13 300 ST Relevant Clinical N N

Information
14 26 TS Specimen Received N U [1]

Date/Time
15 300 CM 0070 Specimen Source N N
16 80 XCN Ordering Provider O [2] N
17 40 XTN Order Callback N N

Phone Number
18 60 ST Placer Field 1 N O [3]
19 60 ST Placer Field 2 N N
20 500 ST Filler Field 1 N N

HL7 Messages
OBR Segment

Type
21 60 ST Filler Field 2 N N
22 26 TS Results Rpt/Status N U [1]

Chng - Date/Time
23 40 CM Charge to Practice N N
24 10 ID 0074 Diagnostic Service N N

Sect ID
25 1 ID 0123 Result Status N U [4]
26 400 CM Parent Result N N
27 200 TQ Quantity/Timing N N
28 150 XCN Result Copies To N N
29 150 CM Parent N N
30 20 ID 0124 Transportation N N
Mode
31 300 CE Reason for Study N N
32 200 CM Principal Result N N

Interpreter
33 200 CM Assistant Result N N

Interpreter
34 200 CM Technician N N
35 200 CM Transcriptionist N N
36 26 TS Scheduled Date/ N N
Time
37 4 NM Number of Sample N N
Containers
38 60 CE Transport Logistics N N
of Collected
Sample
39 200 CE Collector’s N N
Comment
40 60 CE Transport N N
Arrangement
Responsibility

HL7 Messages
OBR Segment

Type
41 30 ID 0224 Transport N N
Arranged
42 1 ID 0225 Escort Required N N
43 200 CE Planned Patient N N

Transport
Comment
Note Description
[0] OBR-4, Universal Service IDs is populated as follows:

First component, Identifier:
• R_ECG for Resting ECG test
• S_ECG for Stress ECG test
• SPIRO for Spirometry test
• BPMONC for ABP: Configure ABP Device
• BPMOND for ABP: Read Data from ABP Device
[1] Date/Time of conducted CASE/CardioSoft test.
[2] Ordering Provider: Part of CASE/CardioSoft test information.
[3] OBR-18, Placer Field 1, is populated with the document type ID (Additional to HL7 table
270).
Used IDs:
• EK (EKG Report for Resting ECG and Stress Test)
• DR (Diagnostic Report Other for Spirometry and ABP test)
[4] OBR-25, Result Status:

• F (Final) for completed tests
• X (Deleted) for aborted tests
ORU-OBX – Observation/Result

HL7 Messages
OBX Segment

Type Table
1 10 SI Set ID - N N
Observation
Simple
2 2 ID 0125 Value Type O [0] U [0]
3 590 CE Observation R [1] [3] U [1] [3]

Identifier
4 20 ST Observation Sub- N N
ID
5 2000 ST Observation O [3] U [3]

Value
6 60 CE Units O [2] [3] C [2] [3]
7 60 ST Reference Range N N
8 10 ID 0078 Abnormal Flags N N
9 5 NM Probability N N
10 5 ID 0080 Nature of N N
Abnormal Test
11 2 ID 0085 Observation N U [4]

Result Status
12 26 TS Date Last Obs N N

Normal Values
13 20 ST User Defined N N
Access Checks
14 26 TS Date/Time of the N N
Observation
15 200 CE Producer’s ID N N
16 80 XCN Responsible N N
Observer
17 60 CE Observation N N
method
Note Description
[0] OBX-2, Value Type: On Import, Value types must be one of ST, FT or TX. On Export, only
value type ST and TX (only for Identifier OTHER_REF) is used.

HL7 Messages
Note Description
[1] OBX-3, Observation Identifier, is populated as follows:

• The first component, Identifier, contains the unique CASE/CardioSoft Observation
Identifier
• Other imported Identifiers as listed below are disregarded (no error)
[2] OBX-6, Units, is populated as follows:

• The first component, Identifier, contains the appropriate unit
• Other imported units for the listed Identifiers are treated as error
[3] Table of supported OBX Identifiers / Units (see [3] table below)
[4] OBX-11, Observation Result Status, is always set to F (Final)
[3] Imported Identifiers / Units / Values
CASE/Cardio Soft Units (OBX-6) Value (OBX-5) Description/Notes

ID (OBX-3)
History - Text Medical History of patient.If

multiple OBX segments with
this ID are used, the text is
appended.
Reason - Text Reason for test.Recommended:

use separate OBX segments for
each reason for test.
Medication Text (e.g. 5 MG) Text Medications and dose.

Recommended: use separate
OBX segments for each
medication.OBX-6 is used as
Dose (separate field in CASE/
CardioSoft test information)
Height CM or IN Numeric Value (e.g. 178, Height of Patient. Use this ID

178.6) only once.
Weight KG or LB Numeric Value (e.g. 75, Weight of patient. Use this ID

75.6) only once.
Pacemaker - Y or N Pacemaker patient. Use this ID

only once.
NOTE:
Exported Identifiers are listed separately for each modality in this
document (see corresponding tables).
MDM – Document Management

HL7 Messages
The MDM message is used to export document references of already conducted

CASE/CardioSoft tests (Data upload of already existing tests or new tests, that are
conducted on an ECG Writer and received by CardioSoft. See "Data Upload of Existing
CASE/CardioSoft Tests to EMR" on page 50, and "Data Upload of External Tests from
ECG Writers" on page 52).
The document reference is transferred within an OBX segment with the Identifier
OTHER_REF.
MDM
T02
Message Import Export

Segments
MSH R
EVN R
PID R
PV1 I [1]
TXA R [2]
{OBX} R [3]
MSH C
MSA C
[ERR] I
Note Description
[0] MDM-Import is only internally supported, because all document references

that are exported by CASE/CardioSoft are also stored internally as a MDM-
T02 message. The EMR only uses the exported document reference to view
or edit the test.
[1] Although the HL7 specification considers this message segment to be

required, CASE/CardioSoft does not use it on export.
[2] The TXA message segment is always exported as part of an MDM

message.
[3] The first exported OBX segment states the type of test, that is referenced
by this message. The 2nd OBX segment can be ignored. The 3rd OBX
segment (Identifier OTHER_REF) shall be used by the EMR as document
reference.

HL7 Messages
MDM Message Segments

MDM-MSH – Message Header
MSH Segment
CASE/CardioSoft
Applicability
Seq Length Data Type HL7 Table Element Table Export
1 1 ST Field Separator U
2 4 ST Encoding Characters U
3 40 HD Sending Application U
4 20 HD Sending Facility U
5 40 HD Receiving Application C [1]
6 30 HD Receiving Facility C [2]
7 26 TS Date/Time Of Message U
8 40 ST Security N
9 7 CM 0076 Message Type U [3]
10 20 ST Message Control ID U [4]
11 3 PT 0103 Processing ID U [5]
12 8 ID 0104 Version ID U [6]
13 15 NM Sequence Number N
14 180 ST Continuation Pointer N
15 2 ID 0155 Accept Ack Type N
16 2 ID 0155 Application Ack Type U [7]
17 2 ID Country Code N
18 6 ID 0211 Character Set N
19 60 CE Principal Language Of N
Message
Note Description

HL7 Messages
Note Description

The second component, trigger event, is ignored on import and not used on export
[4] On Export, the creation time of the message is used for MSH-10 (time stamp
yyyymmddhhmmssxxx, where <xxx> is a sequence number in case of identical time
stamp).

D = Debugging
P = Production
[6] On export, 2.3 is used for Version ID
[7] The supported values for Accept Ack Type include:

AL = Always
NE = Never (default)
If application acknowledgment should be used, an entry in HL7.INI needs to be done
manually (See "HL7 Settings" on page 27.)
MDM-EVN – Event Type
EVN Segment
CASE/CardioSoft
Applicability
Seq Length Data Type HL7 Table Element Name Export
1 3 ID 0003 Event Type Code U [1]
2 26 TS Recorded Date/Time U [2]
3 26 TS Date/Time of N
Planned Event
4 3 IS 0062 Event Reason Code N
5 60 XCN 0188 Operator ID N
6 26 TS Event Occurred N

HL7 Messages
Note Description
[1] The supported values for Event Type Code include:

• T02 Original document notification and content
• Trigger event T02 is always used
[2] EVN-2, Date/Time of Event, is populated with the creation date/time of the test
(referenced document)
MDM-PID – Patient Identification
PID Segment
CASE/
CardioSoft
Applicability
Seq Length Data Type HL7 Element Name Export

Table
1 4 SI Set ID - Patient ID N
2 20 CX Patient ID (External ID) N
3 20 CX Patient ID (Internal ID) U [1]
4 30 CX Alternate Patient ID-PID O [2]
5 48 XPN Patient Name U
6 48 XPN Mother’s Maiden Name N
7 26 TS Date/Time of Birth O
8 1 IS 0001 Sex U [3]
9 48 XPN Patient Alias N
10 1 IS 0005 Race O [4]
11 106 XAD Patient Address N
12 4 IS County Code N
13 250 XTN Phone Number - Home N
14 250 XTN Phone Number - Work N
15 60 CE 0296 Primary Language N
16 1 IS 0002 Marital Status N
17 3 IS 0006 Religion N

HL7 Messages
PID Segment
CASE/
CardioSoft
Applicability
Seq Length Data Type HL7 Element Name Export

Table
18 20 CX Patient Account Number N
19 11 ST SSN Number - Patient N
20 25 DLN Driver’s License Number- N

Patient
21 20 CX Mother’s Identifier N
22 3 IS 0189 Ethnic Group N
23 60 ST Birth Place N
24 2 ID 0136 Multiple Birth Indicator N
25 2 NM Birth Order N
26 4 IS 0171 Citizenship N
27 60 CE 0172 Veterans Military Status N
28 80 CE Nationality N
29 26 TS Patient Death Date and N

Time
30 1 ID 0136 Patient Death Indicator N
Note Description
[1] PID-3, Patient ID (Internal ID), is assumed to contain the patient identifier of CASE/
CardioSoft.
[2] PID-4, Alternate Patient ID, is assumed to be the CASE/CardioSoft’s Patient’s ID, that was
previously uploaded to the EMR database (data migration of existing patients and tests).
If available, PID-4 is used primarily to access to existing CASE/CardioSoft’s Patient IDs.
Although HL7 states a length of 20, with CASE/ CardioSoft a maximum length of 30 is
possible (due to data migration of existing patients and tests).
[3] The supported values for Sex include:

F = Female
M = Male
O = Other (treated as Unknown)
U = Unknown

HL7 Messages
Value = Definition CASE/CardioSoft

>>
On Export (if not Asian O Oriental/Asian

supported,<Unknown>
Black B Black
is used)
Caucasian W White
Hispanic H Hispanic
Native American N Native American
Oriental O Oriental/Asian
Pacific Islander P Pacific Islander
Unknown U Undetermined (default)
MDM-TXA – Transcription Document Header
TXA Segment
CASE/CardioSoft
Applicability
Seq Length Data Type HL7 Table Element Export

Name
1 4 SI Set ID - O
Document
2 30 IS 0270 Document U [1]

Type
3 2 ID 0191 Document U [2]

Content
Presentation
4 26 TS Activity Date/ U [3]

Time
5 60 XCN Primary N
Activity
Provider Code/
Name
6 26 TS Origination U [3]
Date/Time
7 26 TS Transcription N
Date/Time
8 26 TS Edit Date/Time N
9 60 XCN Originator N
Code/Name

HL7 Messages
TXA Segment
CASE/CardioSoft
Applicability

Name
10 60 XCN Assigned N
Document
Authenticator
11 48 XCN Transcriptionist N
Code/Name
12 30 EI Unique U [4]
Document
Number
13 16 ST Parent C [5]
Document
Number
14 22 EI Placer Order N
Number
15 8 EI Filler Order N
Number
16 30 ST Unique N
Document File
Name
17 2 ID 0271 Document U [6]

Completion
Status
18 2 ID 0272 Document N
Confidentiality
Status
Availability
Status
Storage Status
21 30 ST Document N
Change
Reason
22 60 PPN Authentication N
Person, Time
Stamp

HL7 Messages
TXA Segment
CASE/CardioSoft
Applicability

Name
23 60 XCN Distributed N
Copies (Code
and Name of
Recipients)
Note Description
[1] CASE/CardioSoft uses the following document types:

• EK (for Resting ECG, and Stress ECG)
• DR (for Ambulatory Blood Pressure and Spirometry)
[2] On Export, the supported values for Document Content Presentation are
shown below:
TX = Machine readable text document
[3] TXA-4/6 is populated with the creation date/time of the exported document.
[4] TXA-12, Unique Document Number of referenced CASE/CardioSoft

document:<internal patient ID>_<modality identifier>_<creation date/time of
document>
[5] TXA-13, Parent Document Number: For internal use (used in MDM-T02
message of the .csoft files for storing the EMR document ID (order ID), that is
part of the .emr-filename)
[6] TXA-17 On Export, always IP is used
MDM-OBX – Observation/Result
OBX Segment
CASE/
CardioSoft
Applicability
1 10 SI Set ID - Observation Simple N
2 2 ID 0125 Value Type U [1]
3 590 CE Observation Identifier C [2]
4 20 ST Observation Sub-ID N

HL7 Messages
OBX Segment
CASE/
CardioSoft
Applicability
5 65536 ST Observation Value U [3]
6 60 CE Units N
7 60 ST Reference Range N
8 10 ID 0078 Abnormal Flags N
9 5 NM Probability N
10 5 ID 0080 Nature of Abnormal Test N
11 2 ID 0085 Observation Result Status N
12 26 TS Date Last Obs Normal Values N
13 20 ST User Defined Access Checks N
14 26 TS Date/Time of the Observation N
15 200 CE Producer’s ID N
16 80 XCN Responsible Observer N
17 60 CE Observation method N
Note Description
[1] OBX-2 is always populated with ST or TX
[2] OBX-3 is populated with OTHER_REF, if the document reference (test reference) is
used in OBX-5
[3] OBX-5, Observation value: Type of test, that is referenced by this message (1st OBX
segment). The 2nd OBX segment can be ignored. The 3rd OBX segment (Identifier
OTHER_REF) shall be used by the EMR as document reference (test reference)
MDM-MSA – Message Acknowledgment

HL7 Messages
MSA Segment
CASE/
CardioSoft
Applicability
Seq Length Data Type HL7 Table Element Name Import
1 2 ID 0008 Acknowledgement COde R [1]
2 20 ST Message Control ID R
3 80 ST Text Message O
4 15 NM Expected Sequence Number N
5 1 ID 0102 Delayed Ack Type N
6 100 CE Error Condition N
The supported values for Acknowledgment Code include:

• AA = Original mode: Application Acknowledgment: Accept
• AR = Original mode: Application Acknowledgment: Reject
• AE = Original mode: Application acknowledgment: Error
NOTE:
Receipt of either AR or AE initiates message re-send events.
ADT – Admission, Discharge and Transfer

The ADT message is used to export patient demographics data of CASE/CardioSoft
patient records.
ADT messages are uploaded once to the EMR for data migration (all already existing
patient records in the database).
ADT messages are uploaded at any time, when CASE/CardioSoft receives Resting
ECG tests, that were conducted on an ECG Writer. (See "Data Upload of Existing CASE/
CardioSoft Tests to EMR" on page 50 and "Data Upload of External Tests from ECG
Writers" on page 52.)
ADT
A04
Message Segments Import [0] Export
MSH R
EVN R

HL7 Messages
ADT
A04
Message Segments Import [0] Export
PID R
MSH C
MSA C
[ERR] I
Note Description
[0] ADT-Import currently is not supported.
ADT Message Segments

ADT-MSH – Message Header
MSH Segment
CASE/CardioSoft
Applicability
1 1 ST Field Separator U
2 4 ST Encoding Characters U
3 40 HD Sending Application U
4 20 HD Sending Facility U
5 40 HD Receiving Application C [1]
6 30 HD Receiving Facility C [2]
7 26 TS Date/Time Of Message U
8 40 ST Security N
9 7 CM 0076 Message Type U [3]
10 20 ST Message Control ID U [4]
11 3 PT 0103 Processing ID U [5]

HL7 Messages
MSH Segment
CASE/CardioSoft
Applicability
12 8 ID 0104 Version ID U [6]
13 15 NM Sequence Number N
14 180 ST Continuation Pointer N
15 2 ID 0155 Accept Ack Type N
16 2 ID 0155 Application Ack Type U [7]
17 2 ID Country Code N
18 6 ID 0211 Character Set N
19 60 CE Principal Language Of N
Message
Note Description
[1] MSH-5 contains LINKLOGIC
[2] MSH-6 contains LOGICIAN

• ADT = Admission, discharge, and transfer message
On Export, the second component trigger event is always populated with A04 and is
identical to EVN-1 (Event Type Code)
[4] On Export, the creation time of the message is used for MSH-10 (time stamp
yyyymmddhhmmssxxx, where <xxx> is a sequence number in case of identical time
stamp).

• D = Debugging
• P = Production
[6] On export, 2.3 is used for Version ID
[7] The supported values for Accept Ack Type include:

• AL Always
• NE Never (default)
If application acknowledgment should be used, an entry in HL7.INI needs to be done
manually (See "HL7 Settings" on page 27.)
ADT-EVN – Event Type

HL7 Messages
EVN Segment
CASE/
CardioSoft
Applicability
Seq Length Data Type HL7 Table Element Name CASE/

CardioSoft
Applicability
1 3 ID 0003 Event Type Code U [1]
2 26 TS Recorded Date/Time U [2]
3 26 TS Date/Time of Planned Event N
4 3 IS 0062 Event Reason Code N
5 60 XCN 0188 Operator ID N
6 26 TS Event Occurred N
Note Description
[1] The supported values for Event Type Code include:
• A04 = Register a patient
[2] EVN-2, Date/Time of Event, is populated with the creation date/time of the message
ADT-PID – Patient Identification

PID Segment
CASE/CardioSoft
Applicability
1 4 SI Set ID - Patient ID N
2 20 CX Patient ID (External ID) N
3 20 CX Patient ID (Internal ID) U [1]
4 30 CX Alternate Patient ID-PID O [2]
5 48 XPN Patient Name U
6 48 XPN Mother’s Maiden Name N

HL7 Messages
PID Segment
CASE/CardioSoft
Applicability
7 26 TS Date/Time of Birth O
8 1 IS 0001 Sex U [3]
9 48 XPN Patient Alias N
10 1 IS 0005 Race O [4]
11 106 XAD Patient Address N
12 4 IS County Code N
13 250 XTN Phone Number - Home N
14 250 XTN Phone Number - Work N
15 60 CE 0296 Primary Language N
16 1 IS 0002 Marital Status N
17 3 IS 0006 Religion N
18 20 CX Patient Account Number N
19 11 ST SSN Number - Patient N
20 25 DLN Driver’s License N

Number-Patient
21 20 CX Mother’s Identifier N
22 3 IS 0189 Ethnic Group N
23 60 ST Birth Place N
24 2 ID 0136 Multiple Birth Indicator N
25 2 NM Birth Order N
26 4 IS 0171 Citizenship N
27 60 CE 0172 Veterans Military Status N
28 80 CE Nationality N
29 26 TS Patient Death Date and N

Time
30 1 ID 0136 Patient Death Indicator N

HL7 Messages
Note Description
[1] PID-3, Patient ID (Internal ID), is assumed to contain the patient identifier of CASE/
CardioSoft.
[2] PID-4, Alternate Patient ID, is assumed to be the CASE/CardioSoft’s Patient’s ID, that was
previously uploaded to the EMR database (data migration of existing patients and tests).
If available, PID-4 is used primarily to access to existing CASE/CardioSoft’s Patient IDs.
Although HL7 states a length of 20, with CASE/ CardioSoft a maximum length of 30 is
possible (due to data migration of existing patients and tests).
[3] The supported values for Sex include:

F = Female
M = Male
O = Other (treated as Unknown)

U = Unknown
On Export (if not Asian O Oriental/Asian

supported,<Unknown> is
Black B Black
used)
Caucasian W White
Hispanic H Hispanic
Native American N Native American
Oriental O Oriental/Asian
Pacific Islander P Pacific Islander

Unknown U Undetermined
(default)
ADT-MSA – Message Acknowledgment

See MDM-MSA segment (See "MDM-MSA – Message Acknowledgment" on page 78.)

6
Appendix A
Character Set
• In v7.0 the used character set is not delivered/interpreted within the MSH
segment. CASE/CardioSoft uses for all languages (except the list below) the ANSI
(ISO-8859-1) character set (Windows-1252).
• For Chinese language the Chinese Simplified (GB2312) character set is used
(Windows-936).
• For Japanese language the Shift-JIS character set is used (Windows-932).
• For Polish/ Hungarian/ Czech languages the Central Europe (ISO-8859-2)
character set is used (Windows-1250).
• For Russian language the Cyrillic (ISO-8859-5) character set is used
(Windows-1251).
Please also See "MDM-MSA – Message Acknowledgment" on page 78.
• CASE/CardioSoft does not interpret or otherwise support check digit schemes
employed within compound data types.
• On import, the NULL string (“”) can be used to replace an existing string field with a
NULL value.
ST (String), TX (Text) and FT (Formatted Text)

These data types are treated identically.
The following escape sequences are defined, where \ represents the escape delimiter
defined in MSH:
Delimiter Description
\F\ Field separator
\S\ Component separator
\T\ Subcomponent separator
\R\ Repetition separator
\E\ Escape character
\.br\ Line break

Appendix A
All other escape sequences are removed from the data.
DT (Date) and TS (Timestamp)

Unless otherwise specified, the format for date and timestamp fields must be
YYYYMMDDHHMMSS. Although the month and day are considered optional in the HL7
specification of the date format, CASE/CardioSoft requires them.
PN or PN - Person Name
Components:
<family name (ST)> ^ <given name (ST)> ^ <middle initial

or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix
(e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)>
CASE/CardioSoft only uses family name, given name, middle initial or name (example:
PID-5). All other components are ignored.
HL7 CASE/CardioSoft patient name

(patient demographics)
Jones^Robin^D.ÎI^Dr.^MD Last Name: Jones

First Name: Robin D.
CN or XCN - Composite ID Number and Name

Components:
<ID number (ST)> ^ <family name (ST)> ^ <given name (ST)>

^ <middle initial or name (ST)> ^ <suffix (e.g., JR or
III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g.,
MD) (ST)> ^ <source table (IS)> ^ <assigning authority
(HD)>
CASE/CardioSoft only uses family name, given name, middle initial or name and
degree (Example: PV1-7, PV1-8, OBR-16). All other components are ignored.
HL7 CASE/CardioSoft doctors name

(for test information)
rjones^Jones^Robin^D.ÎI^Dr.^MD One String: Jones MD, Robin D.

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 7044 (US Only)
GE Medical Systems Information Technologies, Inc., a General Electric Company, going to market as GE Healthcare.
www.gehealthcare.com

Case / Cardiosoft V7.0: Emr Interface Reference Manual

Uploaded by

Document Information

Original Title

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

Case / Cardiosoft V7.0: Emr Interface Reference Manual

Uploaded by

Copyright:

Available Formats

GE Healthcare

CASE / CardioSoft V7.0

CASE / CardioSoft V7.0

Revision Date Comment

A 28 March 2018 Initial Release

B 24 April 2018 Customer Release

C 18 October 2018 ATOM release

2096198-015 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-015 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-015 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-015 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-015 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-015 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-015 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-015 Revision C

CASE / CardioSoft V7.0 10

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

• CardioSoft Service Manual

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

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

Client Workstation and Action / Description

1.EMR Client on PC1 Enter patient demographics.

2. EMR Client on PC2 Enter the order for a new test.

• Patient demographics, clinical data and test type details are

14 CASE / CardioSoft V7.0 2096198-015 Revision C

Client Workstation and Action / Description

4. CASE/CardioSoft on PC3 Conduct test or finish test

• On end of test (when going to Post Test Review screen), the

• Go back to EMR (button). The defined observation values

5. EMR Client on PC3 Retrieve results (manually or automatically)

• EMR reads and stores observation values and a reference to

• The reference to the test is used by EMR.

7. CardioSoft Client on PC2 Edit (review) test

• Go Back to EMR (button)