General Electric MUSE HL7 INTERFACE REFERENCE MANUAL_SM_2059568-021_B MUSETM v9 Cardiology Information System HL7 Interface Reference Manual Software Version 9 2059568-021 Revision B

GEHealthcare

MUSE™v9CardiologyInformationSystem
HL7Interface

ReferenceManual

SoftwareVersion9
2059568-021RevisionB

MUSECardiologyInformationSystemHL7
Interface
English
©2015GeneralElectricCompany.
AllRightsReserved.

PublicationInformation

TheinformationinthisdocumentappliesonlytoMUSE™v9CardiologyInformationSystem.Itdoesnotapplytoearlierproductversions.
Duetocontinuingproductinnovation,specicationsinthismanualaresubjecttochangewithoutnotice.

MUSEandMACaretrademarksownedbyGEMedicalSystemsInformationTechnologiesInc.,aGeneralElectricCompanygoingtomarketas
GEHealthcare.Allothertrademarkscontainedhereinarethepropertyoftheirrespectiveowners.

Thedocumentpartnumberandrevisionareoneachpageofthedocument.Therevisionidentiesthedocument’supdatelevel.Therevision
historyofthisdocumentissummarizedinthefollowingtable.

Revision

A

B

ToaccessotherGEHealthcareDiagnosticCardiologydocuments,gototheCommonDocumentationLibrary(CDL),locatedat

www.gehealthcare.com/documents,andclickCardiology.

ToaccessOriginalEquipmentManufacturer(OEM)documents,gotothedevicemanufacturer'swebsite.

ThisdocumentisintendedtobeatechnicalreferencemanualforGEHealthcareinternalandexternalcustomersimplementingtheHL7
interface.Itismeanttobeusedtohelptheperson,orpersons,responsibleforconguringtheHL7interfaceunderstandthefeatures
andlimitationsofaMUSEHL7interfacewiththeirHISsystem.

NOTE:

Allillustrationsinthisdocumentareprovidedasexamplesonly.Dependingonsystemconguration,screensinthedocumentmay
differfromthescreensonyoursystem.

Allpatientnamesanddataarectitious.Anysimilaritytoactualpersonsiscoincidental.

Date

27April2015Initialrelease.

17July2015Customerrelease.

Comments

ServiceManualLanguageInformation

WARNING
(EN)

ПРЕДУПРЕЖДЕНИЕ
(BG)

警告

(ZH-CN)

警告

(ZH-TW)

ThisservicemanualisavailableinEnglishonly.

•Ifacustomer'sserviceproviderrequiresalanguageotherthanEnglish,itisthecustomer's

responsibilitytoprovidetranslationservices.

•Donotattempttoservicetheequipmentunlessthisservicemanualhasbeenconsulted

andisunderstood.

•Failuretoheedthiswarningmayresultininjurytotheserviceprovider,operator,orpatient,

fromelectricshock,mechanicalorotherhazards.

Товаупътванезаработаеналичносамонаанглийскиезик.

•Акодоставчикътнауслугатанаклиентаизискадругезик,задължениенаклиентае

даосигурипревод.

•Неизползвайтеоборудването,предидастесеконсултиралииразбралиупътването

заработа.

•Неспазванетонатовапредупреждениеможедадоведедонараняваненадоставчика

науслугата,оператораилипациентврезултатнатоковударилимеханичнаили
другаопасност.

本维修手册仅提供英文版本。

•如果维修服务提供商需要非英文版本，客户需自行提供翻译服务。

•未详细阅读和完全理解本维修手册之前，不得进行维修。

•忽略本警告可能对维修人员，操作员或患者造成触电、机械伤害或其他形式的伤害。

本維修手冊只提供英文版。

•如果客戶的維修人員有英語以外的其他語言版本需求，則由該客戶負責提供翻

譯服務。

•除非您已詳閱本維修手冊並了解其內容，否則切勿嘗試對本設備進行維修。

•不重視本警告可能導致維修人員、操作人員或病患因電擊、機械因素或其他因素

而受到傷害。

2

MUSE™v9CardiologyInformation

System

2059568-021B

17July2015

ServiceManualLanguageInformation(cont'd.)

UPOZORENJE
(HR)

VAROVÁNÍ
(CS)

ADVARSEL
(DA)

WAARSCHUWING
(NL)

HOIATUS
(ET)

VAROITUS
(FI)

Oveuputezaservisiranjedostupnesusamonaengleskomjeziku.

•Ukolikokorisničkiserviszahtijevanekidrugijezik,korisnikovajeodgovornostosigurati

odgovarajućiprijevod.

•Nemojtepokušavatiservisiratiopremuukolikonistekonzultiraliirazumjelioveupute.

•Nepoštivanjeovogupozorenjamožerezultiratiozljedamaservisnogosoblja,korisnikaili

pacijentaprouzročenimelektričnimudaromtemehaničkimilinekimdrugimopasnostima.

Tentoprovoznínávodexistujepouzevanglickémjazyce.

•Vpřípadě,žeexterníslužbazákazníkůmpotřebujenávodvjinémjazyce,jezajištění

překladudoodpovídajícíhojazykaúkolemzákazníka.

•Nesnažteseoúdržbutohotozařízení,anižbystesipřečetlitentoprovoznínávoda

pochopilijehoobsah.

•Vpřípaděnedodržovánítétovarovánímůžedojítkporaněnípracovníkaprodejního

servisu,obslužnéhopersonálunebopacientůvlivemelektrickéhoproudu,respektive
vlivemmechanickýchčijinýchrizik.

Denneservicemanualndeskunpåengelsk.

•Hvisenkundesteknikerharbrugforetandetsprogendengelsk,erdetkundensansvar

atsørgeforoversættelse.

•Forsøgikkeatservicereudstyretmedmindredenneservicemanualharværetkonsulteret

ogerforstået.

•Manglendeoverholdelseafdenneadvarselkanmedføreskadepågrundafelektrisk,

mekaniskellerandenfareforteknikeren,operatørenellerpatienten.

DezeservicemanualisalleeninhetEngelsverkrijgbaar.

•Indienhetonderhoudspersoneeleenanderetaalnodigheeft,danisdeklant

verantwoordelijkvoordevertalingervan.

•Probeerdeapparatuurnietteonderhoudenvoordatdezeservicemanualgeraadpleegd

enbegrepenis.

•Indiendezewaarschuwingnietwordtopgevolgd,zouhetonderhoudspersoneel,de

gebruikerofeenpatiëntgewondkunnenrakenalsgevolgvaneenelektrischeschok,
mechanischeofanderegevaren.

Käesolevteenindusjuhendonsaadavalainultinglisekeeles.

•Kuiklienditeeninduseosutajanõuabjuhenditinglisekeelesterinevaskeeles,vastutab

klienttõlketeenuseosutamiseeest.

•Ärgeüritageseadmeidteenindadaenneeelnevaltkäesolevateenindusjuhendiga

tutvumistjasellestarusaamist.

•Käesolevahoiatuseeiraminevõibpõhjustadateenuseosutaja,operaatorivõipatsiendi

vigastamistelektrilöögi,mehaanilisevõimuuohutagajärjel.

Tämähuolto-ohjeonsaatavillavainenglanniksi.

•Josasiakkaanhuoltohenkilöstövaatiimuutakuinenglanninkielistämateriaalia,tarvittavan

käännöksenhankkiminenonasiakkaanvastuulla.

•Äläyritäkorjatalaitteistoaennenkuinoletvarmastilukenutjaymmärtänyttämän

huolto-ohjeen.

•Mikälitätävaroitustaeinoudateta,seurauksenavoiollahuoltohenkilöstön,laitteiston

käyttäjäntaipotilaanvahingoittuminensähköiskun,mekaanisenviantaimuun
vaaratilanteenvuoksi.

2059568-021B

MUSE™v9CardiologyInformation

3

System

ServiceManualLanguageInformation(cont'd.)

ATTENTION
(FR)

WARNUNG
(DE)

ΠΡΟΕΙΔΟΠΟΙΗΣΗ
(EL)

FIGYELMEZTETÉS
(HU)

AÐVÖRUN
(IS)

PERINGATAN
(ID)

Cemanueltechniquen'estdisponiblequ'enanglais.

•Siunservicetechniqueclientsouhaiteobtenircemanueldansuneautrelangueque

l'anglais,ildevraprendreenchargelatraductionetlaresponsabilitéducontenu.

•Nepastenterd'intervenirsurleséquipementstantquelemanueltechniquen'apasété

consultéetcompris.

•Lenon-respectdecetavertissementpeutentraînerchezletechnicien,l'opérateuroule

patientdesblessuresduesàdesdangersélectriques,mécaniquesouautres.

DieseServiceanleitungistnurinenglischerSpracheverfügbar .

•FallsderKundendiensteineandereSprachebenötigt,musserfüreineentsprechende

Übersetzungsorgen.

•KeineWartungdurchführen,ohnedieseServiceanleitunggelesenundverstandenzu

haben.

•BeiZuwiderhandlungkanneszuVerletzungendesKundendiensttechnikers,des

AnwendersoderdesPatientendurchStromschläge,mechanischeodersonstigeGefahren
kommen.

Τοπαρόνεγχειρίδιοσέρβιςδιατίθεταιστααγγλικάμόνο.

•Εάντοάτομοπαροχήςσέρβιςενόςπελάτηαπαιτείτοπαρόνεγχειρίδιοσεγλώσσαεκτός

τωναγγλικών,αποτελείευθύνητουπελάτηναπαρέχειυπηρεσίεςμετάφρασης.

•Μηνεπιχειρήσετετηνεκτέλεσηεργασιώνσέρβιςστονεξοπλισμόεκτόςεάνέχετε

συμβουλευτείκαιέχετεκατανοήσειτοπαρόνεγχειρίδιοσέρβις.

•Εάνδενλάβετευπόψητηνπροειδοποίησηαυτή,ενδέχεταιναπροκληθείτραυματισμός

στοάτομοπαροχήςσέρβις,στοχειριστήήστονασθενήαπόηλεκτροπληξία,μηχανικούς
ήάλλουςκινδύνους.

Ezaszervizkézikönyvkizárólagangolnyelvenérhetőel.

•Haavevőszervizellátójaangoltóleltérőnyelvretartigényt,akkoravevőfelelőssége

afordításelkészíttetése.

•Nepróbáljaelkezdenihasználniaberendezést,amígaszervizkézikönyvbenleírtakat

nemértelmeztékésértettékmeg.

•Ezengyelmeztetésgyelmenkívülhagyásaaszervizellátó,aműködtetővagyapáciens

áramütés,mechanikaivagyegyébveszélyhelyzetmiattisérüléséteredményezheti.

Þessiþjónustuhandbókereingöngufáanlegáensku.

•Efaðþjónustuveitandiviðskiptamannsþarfnastannarstungumálsenensku,erþaðskylda

viðskiptamannsaðskaffatungumálaþjónustu.

•Reyniðekkiaðafgreiðatækiðnemaþessiþjónustuhandbókhefurveriðskoðuðogskilin.

•Brotáaðsinnaþessariaðvörungeturleitttilmeiðslaáþjónustuveitanda,stjórnandaeða

sjúklingifráraosti,vélrænumeðaöðrumáhættum.

ManualservisinihanyatersediadalambahasaInggris.

•JikapenyediajasaservispelangganmemerlukanbahasalainselaindariBahasaInggris,

merupakantanggungjawabdaripenyediajasaservistersebutuntukmenyediakan
terjemahannya.

•Janganmencobamelakukanservisterhadapperlengkapankecualitelahmembacadan

memahamimanualservisini.

•Mengabaikanperingataninibisamengakibatkancederapadapenyediaservis,operator ,

ataupasien,karenaterkenakejutlistrik,bahayamekanisataubahayalainnya.

4

MUSE™v9CardiologyInformation

System

2059568-021B

17July2015

ServiceManualLanguageInformation(cont'd.)

AVVERTENZA
(IT)

警告

(JA)

경고

(KO)

ЕСКЕРТУ
(KK)

BRĪDINĀJUMS
(LV)

ĮSPĖJIMAS
(LT)

IlpresentemanualedimanutenzioneèdisponibilesoltantoinInglese.

•Seunaddettoallamanutenzionerichiedeilmanualeinunalinguadiversa,ilclienteè

tenutoaprovvederedirettamenteallatraduzione.

•Siprocedaallamanutenzionedell'apparecchiaturasolodopoaverconsultatoilpresente

manualeedavernecompresoilcontenuto.

•Ilnonrispettodellapresenteavvertenzapotrebbefarcompiereoperazionidacuiderivino

lesioniall'addetto,allamanutenzione,all'utilizzatoreedalpazienteperfolgorazione
elettrica,perurtimeccaniciodaltririschi.

このサービスマニュアルは英語版しかありません。

•サービスを担当される業者が英語以外の言語を要求される場合、翻訳作業はその業

者の責任で行うものとさせていただきます。

•このサービスマニュアルを熟読し、十分に理解をした上で装置のサービスを

行ってください。

•この警告に従わない場合、サービスを担当される方、操作員あるいは患者が、感電

や機械的又はその他の危険により負傷する可能性があります。

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

•고객의서비스제공자가영어이외의언어를요구할경우,번역서비스를제공하는것

은고객의책임입니다.

•본서비스지침서를참고했고이해하지않는한은해당장비를수리하려고시도하

지마십시오.

•이경고에유의하지않으면전기쇼크,기계상의혹은다른위험으로부터서비스제

공자,운영자혹은환자에게위해를가할수있습니다.

Бұлқызметкөрсетубойыншанұсқаулығытекағылшынтіліндеқолжетімді.

•Тұтынушыныңқызметпровайдеріағылшынтіліненбасқатілдегінұсқаныталапетсе,

аударубойыншақызметтеріменқамтамасызетутұтынушыжауапкершілігіндеболуы
тиіс.

•Бұлқызметкөрсетубойыншанұсқаулығынназарғаалып,түсінбегенше,жабдыққа

қызметкөрсетуденбастартыңыз.

•Бұлескертудіелемеуқызметпровайдері,операторнемесеемделушініңэлектр

шогынан,механикалықнемесебасқақауіптернәтижесіндежарақаталуынаәкелуі
мүмкін.

Šīapkalpotājurokasgrāmatairpieejamatikaiangļuvalodā.

•Jaapkalpošanassniedzējamnepieciešamainformācijacitā,nevisangļu,valodā,klienta

pienākumsirnodrošināttāstulkošanu.

•Neveicietaprīkojumaapkopi,neizlasotunnesaprototapkalpotājurokasgrāmatu.

•Šībrīdinājumaneievērošanavarradītelektriskāsstrāvastrieciena,mehāniskuvaiciturisku

izraisītutraumuapkopessniedzējam,operatoramvaipacientam.

Šiseksploatavimovadovasyraprieinamastikanglųkalba.

•Jeiklientopaslaugųtiekėjasreikalaujavadovokitakalba-neanglų,numatytivertimo

paslaugasyraklientoatsakomybė.

•Nemėginkiteatliktiįrangostechninėspriežiūros,nebentatsižvelgėteįšįeksploatavimo

vadovąirjįsupratote.

•Jeineatkreipsitedėmesioįšįperspėjimą,galimisužalojimaidėlelektrosšoko,mechaninių

arkitųpaslaugųtiekėjui,operatoriuiarpacientui.

2059568-021B

MUSE™v9CardiologyInformation

5

System

ServiceManualLanguageInformation(cont'd.)

ADVARSEL
(NO)

Denneservicehåndbokennnesbarepåengelsk.

•Hviskundensserviceleverandørtrengeretannetspråk,erdetkundensansvaråsørge

foroversettelse.

•Ikkeforsøkåreparereutstyretutenatdenneservicehåndbokenerlestogforstått.

•Manglendehensyntildenneadvarselenkanføretilatserviceleverandøren,operatøren

ellerpasientenskadespågrunnavelektriskstøt,mekaniskeellerandrefarer.

OSTRZEŻENIE
(PL)

Niniejszypodręcznikserwisowydostępnyjestjedyniewjęzykuangielskim.

•Jeślidostawcausługklientawymagajęzykainnegoniżangielski,zapewnienieusługi

tłumaczeniajestobowiązkiemklienta.

•Nienależyserwisowaćwyposażeniabezzapoznaniasięizrozumienianiniejszego

podręcznikaserwisowego.

•Niezastosowaniesiędotegoostrzeżeniamożespowodowaćurazydostawcyusług,

operatoralubpacjentawwynikuporażeniaelektrycznego,zagrożeniamechanicznego
bądźinnego.

AVISO
(PT-BR)

Estemanualdeassistênciatécnicasóseencontradisponíveleminglês.

•SeoserviçodeassistênciatécnicadoclientenãoforGE,eprecisardeoutroidioma,será

daresponsabilidadedoclientefornecerosserviçosdetradução.

•Nãotenterepararoequipamentosemterconsultadoecompreendidoestemanualde

assistênciatécnica.

•Onãocumprimentodesteavisopodeporemperigoasegurançadotécnico,operadorou

pacientedevidoachoqueselétricos,mecânicosououtros.

AVISO
(PT-PT)

Estemanualtécnicosóseencontradisponíveleminglês.

•Seaassistênciatécnicadoclientesolicitarestesmanuaisnoutroidioma,éda

responsabilidadedoclientefornecerosserviçosdetradução.

•Nãotenterepararoequipamentosemterconsultadoecompreendidoestemanual

técnico.

•Onãocumprimentodesteavisopodeprovocarlesõesaotécnico,aoutilizadorouao

pacientedevidoachoqueseléctricos,mecânicosououtros.

AVERTISMENT
(RO)

Acestmanualdeserviceestedisponibilnumaiînlimbaengleză.

•Dacăunfurnizordeserviciipentruclienţinecesităoaltălimbădecâtceaengleză,estede

datoriaclientuluisăfurnizezeotraducere.

•Nuîncercaţisăreparaţiechipamentuldecâtulteriorconsultăriişiînţelegeriiacestui

manualdeservice.

•Ignorareaacestuiavertismentarputeaducelarănireadepanatorului,operatoruluisau

pacientuluiînurmapericolelordeelectrocutare,mecanicesaudealtănatură.

ПРЕДУПРЕЖДЕНИЕ
(RU)

Настоящееруководствопообслуживаниюпредлагаетсятольконаанглийскомязыке.

•Еслисервисномуперсоналуклиентанеобходиморуководствоненаанглийском,ана

каком-тодругомязыке,клиентуследуетобеспечитьпереводсамостоятельно.

•Преждечемприступатькобслуживаниюоборудования,обязательнообратитеськ

настоящемуруководствуивнимательноизучитеизложенныевнемсведения.

•Несоблюдениетребованийданногопредупрежденияможетпривестиктому,что

специалистыпообслуживанию,операторыилипациентыполучатударэлектрическим
током,механическуютравмуилидругоеповреждение.

6

MUSE™v9CardiologyInformation

System

2059568-021B

17July2015

ServiceManualLanguageInformation(cont'd.)

UPOZORENJE
(SR)

VAROVANIE
(SK)

OPOZORILO
(SL)

ADVERTENCIA
(ES)

VARNING
(SV)

UYARI
(TR)

Ovoservisnouputstvojedostupnosamonaengleskomjeziku.

•Akoklijentovserviserzahtevanekidrugijezik,klijentjedužandaobezbediprevodilačke

usluge.

•Nepokušavajtedaopraviteuređajakonistepročitaliirazumeliovoservisnouputstvo.

•Zanemarivanjeovogupozorenjamožedovestidopovređivanjaservisera,rukovaocaili

pacijentausledstrujnogudara,ilimehaničkihidrugihopasnosti.

Tentonávodnaobsluhujekdispozíciilenvangličtine.

•Akzákazníkovposkytovateľslužiebvyžadujeinýjazykakoangličtinu,poskytnutie

prekladateľskýchslužiebjezodpovednosťouzákazníka.

•Nepokúšajtesaoobsluhuzariadeniaskôr,akosineprečítatenávodnaobsluhua

neporozumietemu.

•Zanedbanietohtovarovaniamôževyústiťdozraneniaposkytovateľaslužieb,obsluhujúcej

osobyalebopacientaelektrickýmprúdom,mechanickýmaleboinýmnebezpečenstvom.

Taservisnipriročnikjenavoljosamovangleškemjeziku.

•Čeponudnikstoritvestrankepotrebujepriročnikvdrugemjeziku,morastrankazagotoviti

prevod.

•Neposkušajteservisiratiopreme,četegapriročnikanistevcelotiprebraliinrazumeli.

•Četegaopozorilaneupoštevate,selahkozaradielektričnegaudara,mehanskihalidrugih

nevarnostipoškodujeponudnikstoritev,operateralibolnik.

Estemanualdeserviciosóloexisteeninglés.

•Sielencargadodemantenimientodeunclientenecesitaunidiomaquenoseaelinglés,el

clientedeberáencargarsedelatraduccióndelmanual.

•Nosedeberádarserviciotécnicoalequipo,sinhaberconsultadoycomprendidoeste

manualdeservicio.

•Lanoobservanciadelpresenteavisopuededarlugaraqueelproveedordeservicios,el

operadoroelpacientesufranlesionesprovocadasporcausaseléctricas,mecánicaso
deotranaturaleza.

Denhärservicehandbokennnsbaratillgängligpåengelska.

•Omenkundsserviceteknikerharbehovavettannatspråkänengelskaansvararkunden

föratttillhandahållaöversättningstjänster.

•Försökinteutföraservicepåutrustningenomduinteharlästochförstårdenhär

servicehandboken.

•Omduintetarhänsyntilldenhärvarningenkandetresulteraiskadorpåserviceteknikern,

operatörenellerpatiententillföljdavelektriskastötar,mekaniskafarorellerandrafaror.

Buserviskılavuzununsadeceİngilizcesimevcuttur.

•Eğermüşteriteknisyenibukılavuzuİngilizcedışındabirbaşkalisandantalepederse,bunu

tercümeettirmekmüşteriyedüşer.

•Serviskılavuzunuokuyupanlamadanekipmanlaramüdahaleetmeyiniz.

•Buuyarıyauyulmaması,elektrik,mekanikveyadiğertehlikelerdendolayıteknisyen,

operatörveyahastanınyaralanmasınayolaçabilir .

2059568-021B

MUSE™v9CardiologyInformation

7

System

ServiceManualLanguageInformation(cont'd.)

ЗАСТЕРЕЖЕННЯ
(UK)

CẢNHBÁO
(VI)

Данекерівництвозсервісногообслуговуванняпостачаєтьсявиключноанглійськоюмовою.

•Якщосервіснийінженерпотребуєкерівництвоіншоюмовою,користувачзобов'язаний

забезпечитипослугиперекладача.

•Ненамагайтесяздійснюватитехнічнеобслуговуванняданогообладнання,якщо

винечитали,абонезрозумілиінформацію,наданувкерівництвізсервісного
обслуговування.

•Недотриманняцьогозастереженняможепризвестидотравмуваннясервісного

інженера,користувачаданогообладнанняабопацієнтавнаслідокелектричногошоку,
механічногоушкодженняабозіншихпричинневірногообслуговуванняобладнання.

TàiLiệuHướngDẫnSửaChữachỉcóbảntiếngAnh.

•Nếucácđơnvịcungcấpdịchvụchokháchhàngyêucầumộtngônngữnàokháctiếng

Anh,thìkháchhàngsẽcótráchnhiệmcungcấpcácdịchvụdịchthuật.

•KhôngđượcsửachữathiếtbịtrừkhiđãthamkhảovàhiểuTàiliệuHướngdẫnSửachữa.

•Khôngtuânthủnhữngcảnhbáonàycóthểdẫnđếncáctổnthươngchongườithực

hiệnsửachữa,ngườivậnhànhhaybệnhnhân,dosốcđiện,cácrủirovềcơkhíhay
cácrủirokhác.

8

MUSE™v9CardiologyInformation

System

2059568-021B

17July2015

Contents

1MUSEHL7Interface

AdditionalAssistance................................................................................15

HL7StandardBackground........................................................................15

TheoryofOperation..................................................................................17

PredenedCCGSites.................................................................................17

DefaultSiteLayout...................................................................................18

InteractionwiththeMUSESystem............................................................18

ADTInterface..........................................................................................18

ADTQueryInterface.................................................................................18

OrderInterface........................................................................................19

ResultInterface.......................................................................................19

ResultBatchInterface...............................................................................20

FinancialInterface...................................................................................20

FinancialBatchInterface...........................................................................20

ADT,Order,andResultDataStorage..............................................................20

GraphicalResultReportingMessages............................................................20

2HL7InboundImplementation

DepthofMerge.........................................................................................21

GeneralDescription..................................................................................23

Introduction...........................................................................................23

Low-levelCommunications.........................................................................23

InterfaceDataContent..............................................................................23

TransactionstotheMUSEHL7Interface...................................................24

MUSESystemIncomingHL7MessageCongurationOptions...............................24

ADTMessages.........................................................................................25

ADTMessageComposition.........................................................................26

OrderMessage........................................................................................27

OrderMessageComposition.......................................................................27

DepthofMergeImplementation...............................................................28

SiteConguration:UpdateMasterMUSEPatientList.........................................29

SiteConguration:UpdateUnconrmedTests.................................................29

SiteConguration:UpdateConrmedTestsforMergeTransactionsOnly................30

SiteConguration:UpdateFullPatientDemographicsfromMergeTransactions

...........................................................................................................30

ApplicationHigh-LevelAcknowledgmentMessages.................................30

AcknowledgmentMessageComposition..................................................31

3HL7OutboundImplementation

2059568-021B

MUSE™v9CardiologyInformation

System

9

GeneralDescription..................................................................................33

Low-LevelCommunications........................................................................33

InterfaceDataContent..............................................................................33

TransactionsFromtheMUSEHL7Interface..............................................34

MUSESystemOutgoingHL7MessageCongurationOptions...............................35

BatchDataTransfer.................................................................................39

4HL7QueryImplementation

Introduction..............................................................................................43

Low-levelCommunications.......................................................................43

InterfaceDataContent.............................................................................43

QueryTransactionsoftheMUSEHL7Interface........................................44

QueryTransactionHL7Messages.................................................................44

5SystemDataFieldDenitions

ADTFields..................................................................................................47

OrderFields...............................................................................................49

6HL7DataSegmentDenitions

Inbound(toMUSE)Segments....................................................................51

Outbound(fromMUSE)Segments.............................................................65

7HISDataManagement

Setup.........................................................................................................81

SchedulingHISDataMaintenance............................................................83

MaintainingtheLogandQueue................................................................83

8HL7ImplementationFAQs

FrequentlyAskedQuestions.....................................................................85

ADTFieldsandFunctions...........................................................................85

OrdersFieldsandFunctions........................................................................86

ResultandFinancialMessagesFieldsandFunctions..........................................87

CommunicationProtocolOptions.................................................................88

9HL7InterfaceTesting

Introduction..............................................................................................91

TestGoals..................................................................................................91

CustomerPrerequisitesforInterfaceTesting...........................................92

10

MUSE™v9CardiologyInformation

System

2059568-021B

TestProcedures.........................................................................................93

TestSequence...........................................................................................93

TestTemplates..........................................................................................94

TestingADTInterfaceTransactions..........................................................94

TestingTransactionsthatAddPatientDate.....................................................95

TestingTransactionsthatChangePatientData................................................96

TestingTransactionsthatMergePatientData..................................................97

TestingTransactionsthatDeletePatientData................................................101

HowtoViewPatientAdmittingandVisitInformationontheMUSEv9

System....................................................................................................102

TestingOrderTransactions.....................................................................104

HowtoViewPatientOrderInformationontheMUSESystem................106

TestingResultTransactions....................................................................108

TestProcedures.......................................................................................108

TestData.................................................................................................109

TestingResultsonMUSESystemswithInboundHL7ADTInterface

Only.........................................................................................................109

HowtoSendTestHL7ResultsfromtheMUSESystem(withInbound

HL7ADTInterface)..................................................................................111

TestingResultsonMUSESystemwithInboundHL7ADTandOrder

Interfaces................................................................................................115

HowtoSendTestHL7ResultsfromMUSESystem(InboundHL7ADT

andOrderInterfaces)..............................................................................117

TestingFinancialTransactions...............................................................121

TestingFinancialTransactionsonMUSESystems...........................................121

TestingInterfaceTransactions...................................................................122

MonitoringHL7TransactionsonMUSESystem......................................122

MUSEHISEventLog................................................................................122

MUSEHISChangeLog.............................................................................124

AAbbreviationsInManual

AbbreviationList.....................................................................................125

BOBXCodeTables

OBXObservationCodeTables.................................................................129

CWaveformProcessingRules

2059568-021B

MUSE™v9CardiologyInformation

System

11

EncodingandEncryption........................................................................137

Decryption..............................................................................................138

DADTTestPlanTemplates

Introduction............................................................................................139

ADTTransactionsforAddingPatientData............................................140

A01–AdmitPatient................................................................................140

A04–RegisterOutpatient.........................................................................142

A04–RegisterEmergencyPatient..............................................................144

A10–PatientArriving..............................................................................146

A13–CancelPatientDischarge.................................................................148

A05–Pre-AdmitInpatient........................................................................150

A05–Pre-AdmitOutpatient......................................................................152

ADTTransactionsforChangingPatientData.........................................155

A08–UpdatePatientInformation–ChangeDateofBirth.................................155

A08–UpdatePatientInformation–ChangeRace...........................................156

A08–UpdatePatientInformation–ChangeSex.............................................156

A08–UpdatePatientInformation–ChangeStreetAddress...............................157

A08–UpdatePatientInformation–ChangePatientName................................157

A08–UpdateAdmittingMDNameandHISID................................................158

A02–TransferPatientLocation.................................................................159

A06–TransferOutpatienttoInpatient.........................................................159

A07–TransferInpatienttoOutpatient.........................................................160

A12–CancelPatientTransfer....................................................................161

A17–SwapPatientLocations....................................................................161

A03–DischargePatient...........................................................................162

A09–PatientDeparting...........................................................................163

ADTTransactionsforDeletingPatientData..........................................163

TA11–CancelPatientAdmit.....................................................................164

A23–DeletePatient...............................................................................164

EOrderTestPlanTemplates

Introduction............................................................................................167

NewOrders............................................................................................168

NW–NewOrder-EKG............................................................................168

NW–NewOrder-SignalAveraged.............................................................170

NW–NewOrder-Holter..........................................................................171

NW–NewOrder-Stress..........................................................................173

ChangeOrders........................................................................................174

XO–ChangeOrder-EKG.........................................................................174

XO–ChangeOrder-SignalAveraged..........................................................175

XO–ChangeOrder–Holter......................................................................176

XO–ChangeOrder–Stress......................................................................176

OrderPriority..........................................................................................177

NW–EnterOrder–EKGSTATPriority...........................................................177

NW–EnterOrder–EKGRoutinePriority.......................................................178

NW–EnterOrder–EKGASAPPriority..........................................................178

NewEKGOrderswithaFutureDate.......................................................179

12

MUSE™v9CardiologyInformation

System

2059568-021B

MultipleOccurrenceEKGOrder..............................................................179

CancelEKGOrder....................................................................................180

DiscontinueEKGOrder............................................................................181

FResultsTestPlanTemplates

Introduction............................................................................................183

MUSEPreliminaryResultsonADTInterfaceOnly...................................184

PreliminaryResultsforEKG.......................................................................184

PreliminaryResultsforHiRes....................................................................186

PreliminaryResultsforHolter....................................................................188

MUSEPreliminaryResultsforStress............................................................189

MUSEDemographicCompleteResultsonADTInterfaceOnly................191

DemographicCompleteResultsforEKG......................................................191

MUSEDemographicCompleteResultsforHiRes............................................193

DemographicCompleteResultsforHolter....................................................194

DemographicCompleteResultsforStress.....................................................196

MUSEFinalResultsonADTInterfaceOnly..............................................198

FinalResultforEKG................................................................................198

FinalResultforHiRes..............................................................................199

FinalResultforHolter..............................................................................201

FinalResultforStress..............................................................................203

MUSECorrectedResultsonADTInterfaceOnly......................................204

CorrectedResultforEKG..........................................................................204

CorrectedResultforHiRes........................................................................206

CorrectedResultforHolter.......................................................................208

CorrectedResultforStress.......................................................................210

MUSEPreliminaryResultsonADTandOrdersInterface.........................212

PreliminaryResultsforEKG.......................................................................212

PreliminaryResultsforHiRes.....................................................................214

PreliminaryResultsforHolter....................................................................216

PreliminaryResultsforStress....................................................................218

MUSEDemographicCompleteResultsonADTandOrders

Interface..................................................................................................220

DemographicCompleteResultsforEKG.......................................................220

DemographicCompleteResultsforHiRes.....................................................222

DemographicCompleteResultsforHolter....................................................224

DemographicCompleteResultsforStress.....................................................226

MUSEFinalResultsonADTandOrdersInterface...................................228

FinalResultsforEKG...............................................................................228

FinalResultsforHiRes.............................................................................230

FinalResultsforHolter............................................................................232

FinalResultsforStress.............................................................................234

MUSECorrectedResultsonADTandOrdersInterfaces.........................236

CorrectedResultforEKG..........................................................................236

CorrectedResultforHiRes........................................................................238

CorrectedResultforHolter.......................................................................240

CorrectedResultforStress.......................................................................242

2059568-021B

MUSE™v9CardiologyInformation

System

13

GResultsandFinancialsTestPlanTemplates

Introduction............................................................................................245

MUSEPreliminaryResultsandBilling.....................................................246

PreliminaryResultsandBillingforEKG.........................................................246

PreliminaryResultsandBillingforHiRes......................................................248

PreliminaryResultsandBillingforHolter......................................................250

PreliminaryResultsandBillingforStress.......................................................252

MUSEDemographicCompleteResultsandBilling..................................254

DemographicCompleteResultsandBillingforEKG.........................................254

DemographicCompleteResultsandBillingforHiRes.......................................256

DemographicCompleteResultsandBillingforHolter.......................................258

DemographicCompleteResultsandBillingforStress.......................................260

MUSEFinalResultsandBilling...............................................................261

FinalResultsandBillingforEKG.................................................................261

FinalResultsandBillingforHiRes...............................................................263

FinalResultsandBillingforHolter...............................................................265

FinalResultsandBillingforStress...............................................................267

MUSECorrectedResultsandBilling.......................................................269

CorrectedResultsandBillingforEKG...........................................................269

CorrectedResultsandBillingforHiRes........................................................271

CorrectedResultsandBillingforHolter........................................................273

CorrectedResultsandBillingforStress........................................................275

14

MUSE™v9CardiologyInformation

System

2059568-021B

MUSEHL7Interface

TheGEHealthcaresystemcanbeconnectedtoahospitalinformationsystemby
theHealthLevelSevenStandardInterface(HL7).Thisdocumentisintendedtobea
technicalreferenceforGEHealthcarecustomersimplementingtheHL7interface.It
containsdataformatsforthetransmissionofdataanddescribestherequirements
forinterfacingtotheGEHealthcaresystemusingtheHL7standard.Thisdocument
doesnotdescribehowtransactionsareprocessedbytheGEHealthcaresystem,or
theclinicalimpactofusingsomeofthefeaturesdescribedhere.

Thisdocumentisnotintendedtoprovideinstructionsforimplementingandusing
theHL7Standard.DetailsoftheHL7standardcanbefoundinHealthLevelSeven
Version2.2orlater.

NOTE:

ThisdocumentdetailsalloptionswithintheGEHL7interface.Notallofthe
featuresandfunctionsdescribedinthismanualareincludedwithastandard
interface.ThepurchaseofadditionalmodulesinconjunctionwiththeGEHL7
StandardInterfacemayberequiredtoobtainthedesiredfunctionality.

1

AdditionalAssistance

GEHealthcaremaintainsatrainedstaffofapplicationandtechnicalexpertstoanswer
questionsandrespondtoissuesandproblemsthatmayariseduringtheinstallation,
maintenance,anduseofthissystem.

ContactyourlocalGEHealthcarerepresentativetorequestadditionalassistance.

HL7StandardBackground

TheHealthLevelSevenStandard(HL7)isusedtoexchangedatabetweencomputer
systems.Itdoesnotrequireaspeciccomputeroperatingsystem,programming
language,orcommunicationprotocolforitsimplementation.

ThegoaloftheHL7Standardistostandardizemessagecontentandusage,while
allowinguser-specicvariationswithinthestandard.Toaccomplishthis,theHL7
Standardspeciesencodingrulesusedtocreatethemessageformat.Basedonthese
rules,themessagesgenerallyconsistofdataeldsanddatasegments.

Amessageiscomprisedofmultiplesegments.Whilesomeofthesegmentsare
requiredtocreateamessage,othersareoptional.EachsegmentwithintheHL7
messageisseparatedbyspecialsegmentseparatorcharacters.

2059568-021B

MUSE™v9CardiologyInformation

15

System

MUSEHL7Interface

Eachsegmentcontainsanumberofdataelements.Thedataelementsmaybeof
varyinglengths.Likethesegments,elementsareseparatedfromeachotherbyspecial
characters.Anumberofdataelementsandtheirseparatorsarelogicallygrouped
togethertocreatedatasegmentssuchasthemessageheadersegmentorthepatient
identicationsegment.Withtheexceptionofthesegmentseparatorcharacters,the
datacontainedinHL7messagesconsistsofdisplayableASCIIcharacters.

Eachsegmentbeginswithathreecharactervalue,forexample“MSH”forthe
messageheadersegment.Thesethreecharactersuniquelyidentifythesegment
withinagivenmessage.Segmentsareidentiedaseitherrequiredoroptional,and
somemayberepeated.Similartodataelds,datasegmentsareseparatedfromeach
otherbysegmentseparatorcharacters.

BasedontheHL7encodingrules,eachmessagewithintheHL7protocolhasaknown
structure.Thesegmentsanddataeldsthatcompriseagivenmessagearealways
thesame,plusorminusthedenedoptionalsegmentsanddataelds.Asaresult,an
individualdataeldcanbefoundwithinamessagesimplybyknowingitscongured
positioninasegment.

HL7messagesarepassedbetweencomputersystemsaspartsofvalidtransactions.
Forexample,admittingapatientontheHospitalInformationSystem(HIS),orreceiving
acompletedstudyresultontheMUSEsystemwouldcauseanHL7messagetobe
generatedandsent.Afteramessageissent,thereceivingsystemprocessesthe
message.Whenprocessingiscomplete,thereceivingsystemcanprocessthenext
message,oritcanoptionallygenerateanapplication-levelacknowledgmentthatis
returnedtothesendingsystem.

SincetheHL7Standardprovidesexibilityinmessagecontentandformat,andin
communicationprotocoloptions,itsimplementationrequiresmutualagreement
betweenthesendingandreceivingcomputersystemsonthefollowingitems:

•Messageformats

•Acknowledgmentprotocol

•Communicationprotocol

•Datahandling

CommunicationbetweenHospitalInformationSystemspersonnelandMUSEInterface
personnelisessentialtodeterminethecustomer-specicuseoftheHL7Standard.

NOTE:

Thisdocumentisnotintendedtoprovideinstructionsforimplementingandusing
theHL7Standard.DetailsoftheHL7standardcanbefoundathttp://www.hl7.org/.

16

MUSE™v9CardiologyInformation

System

2059568-021B

MUSEHL7Interface

TheoryofOperation

Thefollowingdiagramdepictsatypicalproductiondeploymentenvironmentforthe
HL7StandardInterfaceandtheMUSEleserver.CCG(CentricityClinicalGateway)is
theHL7interfaceengine.

TheMUSEHL7InterfaceisdenedasthecombinationofHL7parsersontheMUSE
ServerandconguredMUSE-specicCCGSitesontheCCGServer,thatallowMUSEto
communicatewithanexternalsystemviaHL7.

CCGreceivestheinboundADTandOrder(ORM)messagesfromexternalsystems
(DIS/RIS/HIS)androutesthemtotheMUSEServer.ItalsoroutestheoutboundResults
(ORU)andBilling(DFT)messagesfromtheMUSEleservertoexternalsystems.CCG
alsoprocessesADTQuerymessageswhichMUSEmayusetorequestADTdatafrom
externalsystems.

ThedataexchangebetweenCCGandMUSEleserverisdoneusingTCP/IP
socket-basedcommunicationprotocol.Apre-denedHL7messageformatisusedto
routedatabetweenCCGandMUSEserver.

PredenedCCGSites

TheMUSEsystemshipswiththreepre-denedinterfaces:

•muse_prod

•batch_muse

•batch_his

NOTE:

his_prodcurrentlyshipswithCCG.

Thesesitesincludethenecessarythreadsandcongurationstoreceiveandroute
messagesbetweentheMUSEleserverandexternalsystems(DIS/RIS/HIS).

YourHL7engineerwillcongurethepre-denedinterfacetomeettheneedsofyour
hospitalsystems,soyourcongurationmaynotresemblethisdefaultlayoutexactly
aspresented.

2059568-021B

MUSE™v9CardiologyInformation

System

17

MUSEHL7Interface

DefaultSiteLayout

TheMUSEHL7InterfaceisdesignedtomeetthegoalsoftheHL7Standard.It
providestheexibilitytoeasilysupportuser-specicdifferencesintheHL7message
formats,andalsosupportsavarietyofcommunicationprotocolsfortheexchange
ofmessages.

TheMUSEHL7InterfacesupportsonlytheHL7Standardmessagetypesthathave
anequivalentfunctionontheMUSEsystem.Messagetypeswhichdonothavean
equivalentfunctionontheMUSEsystemarenotsupported.

TheMUSEsystemsupportsimmediateprocessingrulesforallmessagetypes.
Outboundbatchtransactions(deferredprocessing)aresupportedforresultand
nancialmessages.

InteractionwiththeMUSESystem

TheMUSEHL7Interfaceconsistsofsevenstandardcomponentinterfaces:

•ADT(Admit/Discharge/Transfer)

ADTInterface

•ADTQuery

•Order

•Result

•ResultBatch

•Financial

•FinancialBatch

Eachinterfacecomponentisapurchasableoption.Thecompleteinterfacemay
includeoneoranycombinationofthesecomponents.However,anADTinterfaceis
requiredwithanOrderinterface.WealsohighlyrecommendthatanOrderinterface
beincludedwitheveryFinancialinterface.

NOTE:

Theimplementationofoneormoreoftheinterfaceswillaffecttheoperationsof
therespectivedepartment(s)anditspersonnel.Changeswillaffecthowpatient
informationisenteredand/orhowbillingiscompleted.

TheMUSEHL7InterfaceacceptsunsolicitedmessagesforADTtransactionsfrom
thehostsystem.TheMUSEHL7Interfacecanrespondwithanapplication-level
acknowledgmentifrequiredbythehostsystem.Thisacknowledgmentindicatesthat
themessagewasreceived.Oncethemessagesareforwardedtoandprocessedon
theMUSEsystem,entriesaremadeintheMUSEADTdatabasesandMUSEsystem
userscanthenaccessthedata.

NOTE:

ADTQueryInterface

TheMUSEHL7InterfacehastheabilitytoquerythehostsystemforPatient
DemographicsbasedontheMUSEsystemuseractions,ortheMUSEsystemevents.

18

TheMUSEHL7interfacedoesnotsupportbatchprocessingofADTmessages.

MUSE™v9CardiologyInformation

System

2059568-021B

OrderInterface

MUSEHL7Interface

ThemessagesreturnedbythehostsystemareenteredintotheMUSEADTdatabase
andMUSEsystemuserscanthenaccessthedata.

TheADTQueryfeatureisforcustomerswhocannotsendUnsolicitedAdmitmessages
(ADTmessages)totheMUSEsystemtopopulatePatientInformationintheADT
Database.InsteadtheMUSEsystemsendsaQueryMessagetotheHIS,providing
theleastPatientInformation(PatientIDorPatientLastName)askingforPatient
DemographicsandwiththeQueryresponsereceivedfromHIS,MUSEadds/updates
PatientDetailsintheADTDatabase.

TherearethreetriggersintheMUSEsystemforADTQuery:

•Editor

•Normalization

•Device

ADTQuery,ifconguredforthesetasks,willsendaquerymessageouttothe
conguredportontheCCGsystem,receivestheresponsefromtheHISsystem,and
performsupdateoperationsontheMUSEsystem.

ResultInterface

TheMUSEHL7Interfacereceivesandprocessesreal-timeordertransactionmessages
fromthehostsystem.Theordermessagemustcontainanorderforonlyonestudy.
TheMUSEHL7Interfacecanrespondwithanapplication-levelacknowledgmentif
requiredbythehostsystem.Thisacknowledgmentindicatesthatthemessagewas
received.OncethemessagesareforwardedtoandprocessedontheMUSEsystem,
entriesaremadeintheMUSEADTdatabasesandtheMUSEsystemuserscanthen
accessthedata.

NOTE:

TheMUSEHL7interfacedoesnotsupportbatchprocessingofordermessages.
TheMUSEorderinterfacecannotbeconguredtoquerythehostsystemfor
orders,nordoesitcreateordernumbers.

TheMUSEHL7Interfacecandeliverresultmessagestothehostsystem.The
messagescanbeconguredtobesent:

•asthestudyisacquiredbytheMUSEsystem

•asthestudyisconrmed

•asallpatientdemographicsareconrmed

Ifnecessary,conrmedmessagescanberegeneratedandresenttothehostbya
user.However,unconrmedmessagesmayhavebeenupdated,andthusmaynot
beregeneratedexactlyastheywereinitiallyacquired.

TheHIScanusetheresultmessagesineitherofthefollowingways:

•Tomakestudyresultsavailableforaccessonthehospitalcomputersystem.

•Togeneratechargesforcompletedstudies.

TheMUSEHL7interfacedoesnotsendformattedtextanddoesnotsupportHL7
DSPsegments.

2059568-021B

MUSE™v9CardiologyInformation

System

19

MUSEHL7Interface

ResultBatchInterface

TheMUSEHL7Interfacecandeliverbatchesofresultmessages,allowingtheMUSE
systemusertocreateaschedulebasedondaily,weekly,and/ormonthlyintervalsat
whichtimethecollectedbatchofmessageswillbesent.

FinancialInterface

TheMUSEHL7Interfacecanbeconguredtosendseparatenancialmessagestothe
hostsystem.Themessagescanbeconguredtobesent:

•asthestudyisacquiredbytheMUSEsystem,

•asthestudyisconrmed

•asallpatientdemographicsareconrmed

Ifnecessary,messagescanberegeneratedandresenttothehostbyauser.However,
studydatamayhavebeenupdatedintheinterim,andthusthemessagesmaynotbe
regeneratedexactlyastheywereinitiallysent.

TheHIScanusethenancialmessagesineitherofthefollowingways:

•Togenerateprofessionalfeechargesforcompletedstudies.

•Togeneratetechnicalfeechargesforcompletedstudies.

FinancialBatchInterface

TheMUSEHL7Interfacecandeliverbatchesofnancialmessages,allowingtheMUSE
systemusertocreateaschedulebasedondaily,weekly,and/ormonthlyintervalsat
whichtimethecollectedbatchofmessageswillbesent.

ADT,Order,andResultDataStorage

TheADTandorderdataisstoredontheMUSEsysteminthreeinterfacetables:
patients,order,andvisit.Theseshort-terminterfacetablesaremaintainedonthe
MUSEsystemforaconguredlengthoftime.

ThestudyresultdataisstoredontheMUSEsystem,separatefromtheinterface
tables.ThestudyresultdataisrstacquiredintotheMUSEsystemasunconrmed
dataandstoredontheeditlistuntiltheyareconrmed.Theconrmedstudiesare
storedlong-terminthepatient’sstudydatabaseontheMUSEsystem.

AsastudyisacquiredintotheMUSEsystem,informationfromtheinterfacetablesis
incorporatedintotheunconrmedstudydata.Whilethestudyremainsunconrmed
ontheeditlist,theinterfaceinformationmaybeupdatedandthestudydatamaybe
edited.Oncethestudyisconrmedtothepatient’sstudydatabase,theinformationin
thestudy(includinginterfacedata)doesnotchangeunlessthesystemiscongured
fordepthofmergeforconrmedstudies.

GraphicalResultReportingMessages

TheMUSEHL7interfacesupportsreportingofbothdigitizedwaveformimagesand
waveformdatapointsinanHL7resultmessage.

MUSEhasdenedaZ-segmenttosupportgraphicalresultsinseveralimageformats.
ThesupportedformatsforgraphicalresultdataincludeAdobePortableDocument
Format(PDF),PostscriptLevel2,TIFFfaximage,PCL-5,andWindows16–bitmetale

20

MUSE™v9CardiologyInformation

2059568-021B

System

formats.AllimagetypesexceptPostscriptaresentintheHL7messageeither
UUencodedorBase64encoded.

ThewaveformdatapointoptionsfollowstheHL7standardforwaveforms.Onlythe
12-leadrestingECGdatatypeissupportedwhengeneratingHL7messagesthat
includethedetailedwaveformdatapoints.

DepthofMerge

TheMUSEsystemcanbeconguredtoallowpatientstudydemographicsand
visit/accountinformationstoredontheMUSEtobeautomaticallysynchronizedwith
theHISsystemwhenspecicHL7messagesarereceived.Thisdatasynchronization
maybeconguredtooperateonbothconrmedandunconrmedstudydataas
wellastheMUSEsitelevelpatientdemographicsdatastore.Thefollowingsitelevel
settingsareavailabletocontrolthebehaviorofdepthofmerge:

•UpdateMasterMUSEPatientList–AlldepthofmergeHL7messageswillupdate
theMUSEsiteleveldemographicsdata.Thissettingisnotrecommended.The
MasterPatientListisnotusedonsystemsthathaveanADTinterface.

•UpdateUnconrmedTests–AllHL7messageswillupdateunconrmedpatient
tests.

MUSEHL7Interface

•UpdateConrmedTestsforMergeTransactionsOnly–MergespecicHL7
messagewillupdateconrmedpatienttests.

•UpdateFullPatientDemographicsInformationFromMergeTransactions–
Updateallelds(ifnotcheckedonlyPatientID,LastName,FirstName,andDateof
Birthareupdated).

MergespecicHL7messagearethosethatchangePatientID,Visitand/orAccount
identierstothecorrectvalues.Thesearecurrentlytheonlytypeofmessagesthat
targetconrmedpatienttestdata.

2059568-021B

MUSE™v9CardiologyInformation

System

21

MUSEHL7Interface

22

MUSE™v9CardiologyInformation

System

2059568-021B

2

HL7InboundImplementation

GeneralDescription

Introduction

TheHL7StandardInterfaceisusedtoconnectahospital'sinformationsystem(HIS)to
theMUSEHL7Interfacetoexchangedata.TheMUSEHL7Interfacesupportsinbound
ADTandOrderdata.Theinbounddataisunsolicited,andisprocessedinreal-time.

TheMUSEHL7Interfacedoesnotsupportinboundbatchmessages.

Low-levelCommunications

Thespecicinstallationdetermineswhichlow-levelcommunicationprotocolis
used.TheHL7interfacestandardisdesignedtoaccommodateawidevarietyof
communicationmethodologies,frommessage-basedcommunicationstoletransfer
schemes.

Implementationofthelow-levelcommunicationprotocoldoesnotdirectly
affecttheHL7interfacemessagecontentandfunctionality.Notalllow-level
communicationprotocolssupporthigh-levelacknowledgments.Therefore,if
high-levelacknowledgmentsaredesired,alow-levelprotocolthatsupportsthem
mustbeselected.

TheHL7interfaceassumesthatthelow-levelcommunicationprotocolensuresthat
thedataarriveserror-free.Asaresult,nodataintegritycheckingisdoneatthe
applicationlevel.TheMUSEHL7interfaceallowsonlyTCP/IPsocketcommunication
forreceivinginboundHL7transactions.

InterfaceDataContent

ForHL7ADTandordermessages,dataeldsaremappedtotheMUSEsystemdata
eldsaccordingtotheconguredpositionintheHL7segmentstructures.TheMUSE
HL7InterfaceCongurationprogramsdenethemapping.

Thecongurationprogramsusedatatablesandsimplescriptingtodeterminehowto
processincomingHL7messages.ThecongurationprogramsmatchtheHL7elds
andfunctionsspeciedbyacustomertotheMUSEdataelds.

ThefollowingpagesprovidethegeneralformatofthevariousHL7datamessages
recognizedbytheMUSEsystemforinboundinterfaces.Thisdocumentdescribesonly

2059568-021B

MUSE™v9CardiologyInformation

23

System

HL7InboundImplementation

thedataeldsandsegmentsthatarerequiredorusedbytheMUSEsystem.Fields
andsegmentsnotlistedherewillbeignoredbytheMUSEsystem,unlessoptionally
conguredwithacustomizedsetup.SomecustomersmayincorporateaspecialZ
segmentintheHL7messageformat.TheMUSEsystemmaysupporttheinformation
containedintheZsegment,asdeterminedonacasebycasebasis.TheMUSEHL7
Interfaceiscapableofparsinginformationinaspecialsegmentaslongasthe
informationcorrespondstotheMUSEsystemdatabaseinformation.

NOTE:

TheMUSEsystemmessageprocessingfollowstheHL7immediateprocessing
rules.Itdoesnotsupportdeferredprocessing.

TransactionstotheMUSEHL7Interface

TheHISsendsADTand/orordermessagestotheMUSEHL7Interface.Oncethe
messagesentertheMUSEsystem,ataskparsesthemessagedataandcreates
oraltersentriesintheMUSEdatabase.MUSEsystemusersmaythenviewthe
information.AninboundinterfacemayconsistofADTonly,orADTandorders.

TheHL7ADTtransactionstransmitpatientdemographicandpatientvisitinformation
fromthehospital’sADTsystemtotheMUSEsystem.Neworupdatedpatient
informationisenteredintothehospital’sADTsystemandsenttotheMUSEsystemas
anunsolicitedtransaction.MUSEsystemuserscanthenviewthepatientinformation
receivedfromtheHIS.TheMUSEsystemwillnotacceptbatchADTmessages.

Theorderentrytransactionstransfertheorderinformationforarequestedstudyfrom
ahospital’sorderentrysystemtotheMUSEsystem.Allordersoriginateonthehost
systemandaresenttotheMUSEsystemasunsolicitedtransactions.

NOTE:

TheMUSEHL7Interfacedoesnotoriginateorders,createordernumbers,query
fororders,cancelorderstotheHIS,oracceptbatchordermessages.

InHL7terminology,theMUSEHL7Interfaceisconsidereda“ller”oforders.It
receivesordersfromthehospital’sorderentrysystem,allowsuserstoviewtheorder
information,andtracksorderstatusasstudiesarecompletedontheMUSEsystem.

MUSESystemIncomingHL7MessageCongurationOptions

TheMUSEHL7InterfacemapsincomingHL7ADTandordermessagesegmentdata
eldstocorrespondingHL7messagesrecognizedbyMUSE.Inturn,MUSEparsesthe
knownmessagesandupdatesitsdatabaseasneeded.Themappingisbasedon
knownmessagecongurations,andisdoneinCCGusingdatamappingtables.The
exibilityprovidedbythesetablesallowstheMUSEHL7Interfacetoaccommodate
differencesbetweensystemsinHL7ADTandordermessageimplementations.

NotallHL7dataeldsaresupportedbytheMUSEHL7Interface.TheHL7segments
anddataeldssupportedbytheMUSEHL7Interfacearetabulatedin“SystemData

FieldDenitions”onpage47and“HL7DataSegmentDenitions”onpage51.

ThefollowingsectionsdescribeMUSEdatamappingtablesandmessage
congurationsforinboundinterfaces

24

MUSE™v9CardiologyInformation

System

2059568-021B

HL7InboundImplementation

ADTMessages

ThefollowingHL7eventtypesaresupportedbytheMUSEHL7InterfaceforADT
messages:

ADTMessages

HL7event

A01

A02
A03

A04

A05

A06

A07

A08

A09

A10

A11

A12
A13
A17
A18

A19
A23

A34

A35Mergeaccount

MUSEfunction

AdmitpatientPatientisadmitted.Patientandopenvisit

TransferpatientPatientvisitlocationischanged
DischargepatientPatientvisitends.Visitstatusischanged

AdmitpatientPatientisadmitted.Patientandopenvisit

AdmitpatientPatientisadmitted.Patientandopenvisit

Transferoutpatientto
inpatient

Transferinpatientto
outpatient

UpdatepatientinformationPatientandvisitinformationareupdated

DischargepatientPatientvisitends.Visitstatusischanged

AdmitpatientPatientisadmitted.Patientandopenvisit

CanceladmitPatientvisitisdeletedifvisitdoesnothave

TransferpatientPatientvisitlocationischanged
CanceldischargeVisitstatusischangedtoOpen
Swappatients
MergepatientID

UpdatepatientinformationPatientquery(ADTquery)results
DeletepatientPatientvisitisdeletedifvisitdoesnothave

MergepatientID

MUSEAction

arecreatedinMUSEADTtables.

toclosed

arecreatedinMUSEADTtables.

arecreatedinMUSEADTtables.
Patientlocationandtypearechangedfor

visit
Patientlocationandtypearechangedfor

visit

toclosed

arecreatedinMUSEADTtables.

activeorders

TwopatientVisitlocationsareswapped
VisitsandordersassociatedwithonePID

aremovedtoadifferentPID

activeorders
VisitsandordersassociatedwithonePID

aremovedtoadifferentPID
Updatesaccountnumberwithnew

accountnumber

2059568-021B

MUSE™v9CardiologyInformation

System

25

HL7InboundImplementation

ADTMessages(cont'd.)

ADTMessageComposition

HL7event

A36

A42

A46

MUSEfunction

MergepatientIDand
account

Mergevisit

Mergevisit

MUSEAction

PatientIDandaccountnumberare
updatedwithnewPatientIDandaccount
number

Thevisitandallassociatedordersare
movedtonewvisitnumber

Thevisitandallassociatedordersare
movedtonewvisitnumber

NOTE:

A18functionalityisreservedforbackwardscompatibility.A34shouldbeused.

AllotherHL7messagesareunsupportedandwillnotbeprocessedbytheMUSE
HL7interfaceapplication.WhenanunsupportedHL7messageissenttotheMUSE
interface,anerrorislogged.

NOTE:

Inordertomaximizeperformance,unsupportedmessagesshouldbeltered
outbytheHISsystem.

ThegeneralformatforthevariousADTmessagesisgivenbelow.Segmentsenclosed
bysquarebrackets,[],areoptional.TheMUSEHL7InterfaceallowsonlyonePatient
IdenticationSegmentperHL7message,withtheexceptionoftheA17Swap
transaction.AtabulationofalltheHL7segmentsanddataeldsassupportedbythe
MUSEHL7Interfaceisincludedin“SystemDataFieldDenitions”onpage47and“HL7

DataSegmentDenitions”onpage51.

TheMUSEHL7interfacesupportsthefollowingHL7ADTmessagesegments.MUSE
HL7InterfacemessagecongurationallowstheuseofadditionalstandardHL7
segments,orspecialZ-segments,forspecicdatathatissupportedontheMUSE
system.HL7segmentsnotlistedbelow,orthatarenotconguredintheMUSEHL7
InterfaceareignoredbytheMUSEHL7InterfacewhenreceivedinanHL7ADT
message.TheMUSEHL7Interfacesupportseldsforpatientheight,patientweight,
andadmittingdiagnosiswhichdonotdirectlycorrelatewitheldsdenedbyHL7
ADTmessages.

ADTCommonTriggerEventsA01,A02,A03,A04,A05,A06,A07,A08,A09,A10,
A11,A12,A13,A23

•MSH-MessageHeadersegment

•EVN-EventTypesegment

•PID-PatientIdenticationsegment

•PV1-PatientVisitsegment

•[DG1]-Patientdiagnosissegment

•[NTE]-Notesegment

•{[OBX]}-Observationsegment

•[ZEX]-Extradataelds

26

MUSE™v9CardiologyInformation

System

2059568-021B

HL7InboundImplementation

ADTMergeA18,A34,A35,A36,A42,A46

•MSH-MessageHeadersegment

•EVN-EventTypesegment

•PID-PatientIdenticationsegment

•PV1-PatientVisitsegment

•MRG-MergeInformationsegment

ADTSwapA17

•MSH-MessageHeadersegment

•EVN-EventTypesegment

•PID-Patient1Identicationsegment(withsequencenumber1,required)

•PV1-Patient1Visitsegment(withsequencenumber1,required)

•PID-Patient2Identicationsegment(withsequencenumber2,required)

•PV1-Patient2Visitsegment(withsequencenumber2,required)

OrderMessage

OrderMessageComposition

ThefollowingHL7orderfunctionsaresupportedbytheMUSEHL7Interface:

OrderFunctions

Order

NWNewOrderAneworderiscreated.
CACancelOrderRequestAnexistingorderiscancelledifnotalreadyin

ODDeleteOrderAnexistingorderiscancelled.
XOChangeOrderRequestAnexistingorderischanged.Iforderdid

Description

processinMUSE.

notpreviouslyexistinMUSE,neworderis
created.

AllotherorderfunctionsareunsupportedandwillberejectedbytheMUSEHL7
interfaceapplication.

NOTE:

Inordertomaximizeperformance,unsupportedorderfunctionsshouldbe"ltered
out"sotheydonottransmittotheMUSEinterface.

Thegeneralformatofanordermessageisgivenbelow.Segmentsenclosedinsquare
brackets,[],areoptional.TheMUSEHL7Interfaceallowsonlyonecommonorder
segmentandoneObservationRequestsegmentpermessage(onlyoneorderis
allowedperHL7ordermessage).AtabulationofalltheHL7segmentsanddataelds
supportedbytheMUSEHL7Interfaceisincludedin“SystemDataFieldDenitions”on

page47and“HL7DataSegmentDenitions”onpage51.

Ingeneral,thesearetheonlyHL7ordermessagesegmentssupportedbytheMUSE
HL7Interface.MUSEHL7Interfacemessagecongurationmayallowtheuseof

2059568-021B

MUSE™v9CardiologyInformation

System

27

HL7InboundImplementation

additionalstandardHL7segments,orspecialZ-segments,forspecicdatathatis
supportedontheMUSEsystem.HL7segmentsnotlistedbelowornotsetupinthe
MUSEHL7InterfacecongurationprogramareignoredbytheMUSEHL7Interface
whenreceivedinaHL7ordermessage.

AlthoughthePV1segmentisshownasanoptionalsegmentintheHL7ordermessage,
theMUSEsystemsupportseldswhichmaystoreinformationintheMUSEdatabases
specicallyfromtheordermessagesPV1segment.TheMUSEHL7Interfacealso
supportseldsfororderingcommentswhichdonotdirectlycorrelatewithelds
denedbyHL7ORMmessages.

•MSH-MessageHeadersegment

•PID-PatientIdenticationsegment

•[PV1]-PatientVisitsegment

•ORC-CommonOrdersegment

•OBR-ObservationRequestsegment

•[NTE]-Notesegment

•[DG1]-Patientdiagnosissegment

•{[OBX]}-Observationsegment

•[ZEX]-Extradataelds

DepthofMergeImplementation

ThetypesofHL7messages,alongwiththeMUSEsitecongurationsettingthatwill
triggerautomaticupdatestopatientstudydatastoredontheMUSEsystemare
providedinthefollowingsections:

•“SiteConguration:UpdateMasterMUSEPatientList”onpage29

•“SiteConguration:UpdateUnconrmedTests”onpage29

•“SiteConguration:UpdateConrmedTestsforMergeTransactionsOnly”on

page30

•“SiteConguration:UpdateFullPatientDemographicsfromMergeTransactions

”onpage30

Itshouldbenotedthatifastudywhichisthetargetforanupdateormergeischecked
outforeditingatthetimethetransactionissenttotheMUSEsystemthestudywill
beleftun-merged.

28

MUSE™v9CardiologyInformation

System

2059568-021B

SiteConguration:UpdateMasterMUSEPatientList

ThefollowingmessageswillcausetheMUSEsitelevelpatientdemographicsdata
tobeupdatedforthespeciedpatient:

NOTE:

UpdateMasterMUSEPatientListshouldbeenabledonlywhentheworkow
requiresthatthecurrentsitelevelpatientdemographicsontheMUSEisalways
insynchronizationwiththeHISsystem.SinceallA08messageswilltriggeran
updatetothesiteleveldemographicswhenthepatientispresent,andsinceA08
messagesareverycommon,thismayplaceanunnecessaryloadonthesystem.
Thesiteleveldemographicswillbeupdatedasaconsequenceofunconrmed
recordsbeingupdated,itisgenerallyrecommendedthatthischeckboxbe
disabled.

MessageEvents

HL7InboundImplementation

MUSEFunction

AdmitPatient
UpdatePatient
TransferPatient
MergePID
MergeAccount
MergePID&Account
MergeVisit

HL7Event

ADT[A01,A04,A05,A10]
ADT[A08]
ADT[A12,A02]
ADT[A18,A34]
ADT[A35]
ADT[A36]
ADT[A42,A46]

SiteConguration:UpdateUnconrmedTests

Thefollowingmessageswillcauseunconrmedstudiestobeupdatedforthe
speciedpatient:

NOTE:

PID/NameandDateofBirthmismatcheswillprohibittheupdateofunconrmed
studies.

MessageEvents:

MUSEFunction

HL7Event

AdmitPatient
UpdatePatient
TransferPatient
UpdatePatientStatus
UpdateOrderORM[XO],iforderstatus=unconrmed
MergePID
MergeAccount

2059568-021B

MUSE™v9CardiologyInformation

System

ADT[A01,A04,A05,A10]
ADT[A08]
ADT[A12,A02]
ADT[A07,A06]

ADT[A18,A34]
ADT[A35]

29

HL7InboundImplementation

MessageEvents:(cont'd.)

MUSEFunction

MergePID&Account
MergeVisit

HL7Event

ADT[A36]
ADT[A42,A46]

SiteConguration:UpdateConrmedTestsforMerge
TransactionsOnly

Thefollowingmessageswillcauseconrmedstudiestobeupdatedforthespecied
patient:

MessageEvents:

MUSEFunction

MergePID
MergeAccount
MergePID&Account
MergeVisit

HL7Event

ADT[A18,A34]
ADT[A35]
ADT[A36]
ADT[A42,A46]

SiteConguration:UpdateFullPatientDemographicsfrom
MergeTransactions

ApplicationHigh-LevelAcknowledgment Messages

Thefollowingmessageswillcausealleldsoftheconrmedstudiestobeupdated
forthespeciedpatient:

NOTE:

IfnotcheckedonlyPatientID,LastName,FirstName,andDateofBirthare
updated.

MESSAGEEVENTS:

MUSEFunctionHL7Event

MergePIDADT[A18,A34]
MergeAccountADT[A35]
MergePID&AccountADT[A36]
MergeVisit[A42,A46]

TheMUSEHL7Interfacesupportsapplication-levelmessageacknowledgmentsin
responsetoinboundmessagesformattedasHL7originalmodeacknowledgments.
Thisfunctionallowsanapplicationtoacknowledgethatithasreceiveddataandhas
determinedthemessageisvalidHL7.Theacknowledgmentmessagereturnedtothe

30

MUSE™v9CardiologyInformation

System

2059568-021B

sendingapplicationisusedtodeterminewhethertoinitiateare-sendofthemessage,
toabortthetransactionortocontinueprocessingthenexttransaction.

Bydefault,theMUSEHL7InterfacewillalwayssendanHL7acknowledgment
messagetothehostsystemafterreceivinganADTorordermessage.

TheMUSEinterfacedoesnotsupportsinglecharacterorACK/NACKacknowledgment
responses.

AcknowledgmentMessageComposition

AcknowledgmentmessagescontainthefollowingHL7interfacesegments:

•MSH-MessageHeader

•MSA-MessageAcknowledgment

HL7acknowledgmentmessagesmaycontainoneofthreestatusesfromthereceiving
system:accept(AA),applicationerror(AE),orapplicationreject(AR).Accordingtothe
HL7specication,AEmessagescontainanerrorandarenottoberetransmitted.AR
messagesmayberetransmittedbasedonalocalagreementbetweenallparties
involvedintheinterfaceimplementation.

HL7InboundImplementation

TheMUSEHL7Interfaceisnotcapableofdetectingapplication-levelerrors.Becauseof
this,itiscapableonlyofrespondingwithanAAorAEacknowledgment.Itwillrespond
withanAEacknowledgmentwhentheHL7messageitselfiscorruptorincomplete.

TheMUSEHL7InterfacereturnstheADTorordermessageMSHsegmentControlID
eldassentbytheHISintheMSAsegmentoftheacknowledgmentresponse.

2059568-021B

MUSE™v9CardiologyInformation

System

31

HL7InboundImplementation

32

MUSE™v9CardiologyInformation

System

2059568-021B

3

HL7OutboundImplementation

GeneralDescription

TheHL7StandardInterfaceisusedtoconnectahospital’sinformationsystem(HIS)to
theMUSEHL7Interfacefortheexchangeofdata.UsingtheMUSEHL7interface,the
MUSEsystemcansendresultandnancialmessagestotheHIS.

TheMUSEHL7Interfacemaybeconguredtoprovideresultand/ornancial
messages.TheMUSEHL7Interfacecanbeconguredtoformattextualtestresults
and/ornanciallesandtransmitthemtotheHIS.Creditscannotbegeneratedwith
thenancialmessageinterface.Resultandnancialmessagescanbeconguredto
besentasindividualmessagesorinbatches.

Oneoranycombinationoftheresultornancialfunctionsmaybeimplemented.

NOTE:

AnancialinterfaceisonlyrecommendedwithanestablishedADTororder
interfacewhichensurespatientdatamatchesthehostcomputersystemdata.

Low-LevelCommunications

Thespecicinstallationdetermineswhichlow-levelcommunicationprotocolwill
beused.TheHL7interfacestandardisdesignedtoaccommodateawidevariety
ofcommunicationmethodologies,frommessage-basedcommunicationstole
transferschemes.Becauseofthisexibility,implementationofthelow-level
communicationprotocoldoesnotdirectlyaffecttheHL7interfacemessagecontent
andfunctionality.However,notalllow-levelcommunicationprotocolssupport
high-levelacknowledgments.Ifhigh-levelacknowledgmentsaredesired,selecta
low-levelprotocolthatsupportsthem.

TheHL7interfaceassumesthatthelow-levelcommunicationprotocolensuresthat
thedataarriveserror-free.Asaresult,nodataintegritycheckingisdoneatthe
applicationlevel.Examplesofpossiblecommunicationmethodsare:ftp,TCP/IP,
socketsandshareddrives.

InterfaceDataContent

ForHL7outboundmessages,thestudydatagatheredfromtheMUSEsystemis
mappedtothecongureddataeldpositionsintheHL7segmentstructurestocreate
resultand/ornancialmessages.DatamappingisaccomplishedthroughtheMUSE
HL7Interfacecongurationprograms(CCG).

2059568-021B

MUSE™v9CardiologyInformation

33

System

HL7OutboundImplementation

ThecongurationprogramsusedatatablesandscriptingtoformatoutgoingHL7
messages.ThecongurationprogramsprovidetheexibilitytomatchtheHL7elds
andfunctionsspeciedbyacustomertotheMUSEdataelds.

ThefollowingpagesprovidethegeneralformatofthevariousHL7datamessages
recognizedbytheMUSEsystemforoutboundinterfaces.Thisdocumentdescribes
onlythedataeldsandsegmentsthatareprovidedbytheMUSEsystem.Fieldsand
segmentsnotlistedherearenotsentbytheMUSEsystem.

NOTE:

Theimplementationofoneormoreoftheinterfaceswillaffecttheoperationsof
therespectivedepartment(s)anditspersonnel.Changeswillaffecthowpatient
informationisenteredand/orhowbillingiscompleted.

TransactionsFromtheMUSEHL7Interface

TheMUSEsystemmanagesandstorespatientstudiessuchasrestingECGs,Holters,
andexercisestressstudies.Initially,thestudiesareperformedonancillaryMUSE
devicesandthestudyresultsarethenacquiredintotheMUSEsystemforprocessing.
Atacquisition,thestudiesaregenerallyunconrmedwithastatusofpreliminary
whichmeansthattheresultshavenotbeeninterpretedorreadbyaphysician.When
astudyisinterpretedorreadbyaphysicianandconrmed,thestatusofthereport
updatestonal.Thestoredresultscanberetrievedand/oreditedasnecessary.Tests
thatarere-editedandsavedareincorrected/revisedstatus.

TheMUSEReportDistributionsetuputilityisusedtocongurethegenerationofresult
andnancialmessagestotheMUSEinterfaceengineandthentotheHIS.Aswithother
reportdistributioncongurations,eachMUSEstudytypehasitsownconguration.
Thereportdistributioncongurableparameterswithineachstudytypeare:

•Patient/studylocationparameter—ThesetupofthelocationparameterforHL7
messagingconformstothesamerulesasotherreportsordevices.Refertothe
MUSECardiologyInformationSystemOperator’sManualfordetailedconguration.

•Triggersforgenerationofmessage—Theavailabletriggersforgenerationofan
HL7messagearethesameasthoseforreportstodevices.SettingupanHL7
resultintheunconrmedsectionoftheReportDistributionutilitygeneratesan
HL7messageonacquisitionofthestudyfromtheancillarydevicetotheMUSE
server.EntriesintheDemographicsCompletesectionareexecutedwhenthe
studyismarkedas"DemographicsComplete.”Entriesintheconrmedsection
aregeneratedwhenthestudyisconrmedandwhenthestudyisrevisedand
re-conrmed.Iftheformatis“HISbilling,”theHL7messageisgeneratedonlyonce
foreachtrigger ,eveniftheactiontotriggeranothermessageisexecuted.Special
userprivilegesarerequiredtogenerateadditionalbillingmessages.

•Device—AcommunicationdeviceiscreatedandusedtotransmittheHL7
messageformattedbytheMUSEsystemtotheMUSEinterfaceengine.MultipleHL7
devicesmayhavebeencreatedfortransmittingdifferentmessagetypes.When
conguringreportdistributiontosendHL7resultandnancialmessagestothe
HIS,itisnecessarytochoosethecorrectdevice.TheHL7integrationengineerwho
conguredtheMUSEHL7interfacewillcommunicatethecorrectdevicetouse.

•Messageformats—MessageformatsareconguredbytheHL7integration
engineerandcanincludetextmessages,resultsmessageswithencoded
waveforms,andmessagesformattedforbilling.Themessageformatselectedin
reportdistributionthatissenttotheMUSEHL7interfaceenginemaybeassociated

34

MUSE™v9CardiologyInformation

System

2059568-021B

HL7OutboundImplementation

withtheHL7device,orbeastand-aloneformat.TheHL7integrationengineerwho
conguredthesystemwillcommunicatethecorrectformattoselect.

AdditionalnotesongenerationofFinancialmessages:
TheMUSEsystemisconguredtorecognizewhenauserperformsanactionthat

wouldgenerateasecondnancialmessageandwilleitheralloworsuppressthe
message.Whenaneventthatcouldgenerateaduplicatemessageoccurs(user
triggersaReportDistributionrouteforDemographicsCompleteorconrmsastudy
andtherouteisconguredforbilling),MUSEwillevaluatetheMUSEuser’sprivilegeto
determineiftheyhavesufcientprivilegestobillastudymorethanonce.Iftheuser
hasthisprivilegetheywillbepromptedtoconrmthattheywishtosendanother
nancialtransactionforthestudy.Iftheuserdoesnothavere-billprivileges,MUSE
willsuppressthegenerationoftheadditionalnancialmessage,eveniftheReport
Distributionsettingsareconguredtorouteonthisevent.

DuetothepotentialthatduplicatemessagesmaybesentfromMUSEthereceiving
HISsystemmusthandleduplicatenancialmessages.Ultimatelyitistheresponsibility
oftheHISbillingsystemtoensureproperchargesandcredits.

NOTE:

Useofnancialmessagesbasedonnewlyacquiredstudiesisnotrecommended.

MUSESystemOutgoingHL7MessageCongurationOptions

OutboundMessageStatuses

ThefollowingisadescriptionoftheHL7messagestatusesthatareusedbytheMUSE
HL7interfaceforOutbound(ORUandDFT)messages.

•PreliminaryResultStatusThisstatusindicatesastudyhasbeenperformedand
acquiredbytheMUSEsystem.ThemessagecontainsADTand/ororderinformation
asenteredatoravailableatthedevice.Itmayincludeacombinationofpreliminary
studymeasurementsand/orcomputergenerateddiagnosisstatements.The
preliminarystatusisindicatedbythe“P”inOBR-25andineld11ofeachOBX
segment.

NOTE:

Sendingnancialmessagesbasedonnewlyacquiredstudiesisnot
recommended.

•DemographicsCompleteStatusThisstatusindicatesthatthepatient
demographicsinformationintheMUSEsystemforaparticularstudyiscomplete.
ThisinterimstatuscanalsobetriggeredmanuallybyaMUSEuser.Themessage
containsADTand/ororderinformationasupdatedattheMUSEsystem.Itmay
includeacombinationofpreliminarystudymeasurementsand/orcomputer
generateddiagnosisstatements.Sendingaresultmessagewhenastudyreaches
DemographicsCompletestatusmaybeabetterchoicethensendingaPreliminary
ResultorBillingMessage,asitgivestheMUSEusersachancetocompleteany
missingpatientinformationfromthestudybeforesendingthemessage.The
demographicscompletestatusisindicatedbythe“I”inOBR-25andineld11
ofeachOBXsegment.

•FinalResultStatusThisstatusindicatesastudyhasbeeneditedattheMUSE
system,andthestudyresultshavebeenconrmedbyanoverreader.Themessage
containsADTand/ororderinformationasupdatedduringtheeditingsession.It
mayincludeacombinationofconrmedstudymeasurementsand/ordiagnosis

2059568-021B

MUSE™v9CardiologyInformation

System

35

HL7OutboundImplementation

statements.Thenalstatusisindicatedbythe“F”inOBR-25andineld11of
eachOBXstatement.

•CorrectedResultStatusAstatuswithcorrectedstatusindicatesthatapreviously
conrmedstudyhasbeenre-editedandre-conrmedaftertheinitialconrmation.
ThemessagecontainsADTand/ororderinformationasupdatedduringtheediting
session.Itmayincludeacombinationofconrmedstudymeasurementsand/or
diagnosisstatements.Thecorrectedstatusisindicatedbythe“C”inOBR-25andin
eld11ofeachOBXstatement.

ResultreportingfromaMUSEsystemthatdoesnotincludeanorderinterfaceis
possible.Thistypeofinterfacewillnotincludeallofthedatafoundinthefollowing
examples.Withoutanorderinterface,theordernumbermaynotbeavailableonthe
MUSEsystemtoincludeintheresultornancialmessages.Otherinformation,such
astheorderingphysician,mayalsonotbeavailable.Pleaserefertothetablesinthe
DataSegmentsectionattheendofthisdocumentfordetailsonthedatacontainedin
theMUSEsystemordertable.

StudyResultMessageComposition(ORU)

Allstudyresultmessageshavethesamebasicsegments:

•MSH-Messageheader

•PID-Patientidentication

•PV1-Patientvisit

•[OBR]-Observationrequest

•{OBX}-Observationresult

•[ZRI]-Reportimage(forwaveformsegmentonly)

OBXSegments

TheOBXsegmentscanrepeatandwillcontainmeasurements,asingle(non-coded
diagnosis)line,theMUSEEnterpriseIntegrationURL,oraspeciallyformatted
measurementanddiagnosisstatement.AnORUmessagecanbeconguredto
includespecicmeasurementsegmentsandvariouscombinationsoftheURLand
diagnosissegments.

BelowareexamplesofeachtypeofOBXsegmentandcommonlyusedcombinations
ofthesegments.

OBXDiscreteMeasurementdatasegments(1ton)

EachMUSEdatatypehasadifferentsetofreportablemeasurementsthatcan
besentinaresultsORUmessage.UsingtheOBXdiscretemeasurementoption,
theORUmessagecanbeconguredtocontainonlythespecicmeasurements
requestedbytheEMR/HIS.DiscreteOBXmeasurementsarefrequentlysentalongwith
theNon-coded,single-linediagnosisOBXsegment(describedbelow).Seetables
in“OBXCodeTables”onpage129foravailablemeasurementelementsandtheir
correspondingcodesforeachMUSEtesttype.

SampleOBXsegmentswithdiscretemeasurementsfroma12LeadECG:

OBX|1|ST|552^VentricularRate||140|BPM||||F
OBX|2|ST|553^AtrialRate||140|BPM||||F
OBX|3|ST|554^P-RInterval||120|ms||||F
OBX|4|ST|555^QRSDuration||92|ms||||F
OBX|5|ST|556^Q-TInterval||272|ms||||F

36

MUSE™v9CardiologyInformation

System

2059568-021B

HL7OutboundImplementation

OBX|6|ST|557^QTCCalculation(Bezet)||415|ms||||F
OBX|7|ST|558^PAxis||73|degrees||||F
OBX|8|ST|559^RAxis||66|degrees||||F
OBX|9|ST|560^TAxis||55|degrees||||F

OBXNon-codeddiagnosissegment(singlelinewithOBX-5eldrepetitions)
(1)

MUSEstudydiagnosisandinterpretationsareenteredonMUSEstudiesasindividual
statements,groupingsofstatements,orasfreetext.StatementsfromtheMUSE
statementlibraryareenteredsingularlyoringroupsonindividuallinesinthe
interpretationanddiagnosiswindowintheMUSEapplication.Theseindividuallines
canbesentfromtheMUSEapplicationinasingleOBXsegment,witheachline
separatedbythemessagerepetitionseparator.

Thesinglelinediagnosisstatementiscommonlyusedwithaselectionofmeasurement
OBXsegments.

Samplesingle-lineOBXinterpretationanddiagnosisstatement:

OBX|11|TX|208.0^Diagnosis||Sinustachycardia~Acute
pericarditis~NonspecificTwaveabnormality~Abnormal
ECG~ConfirmedbyWenzel,MarkA.(201)on6/29/2010
10:28:30AM|||||F

OBXMeasurementandDiagnosissegment(1)

AnotheroptionforMeasurementandDiagnosisreportingistousethepre-congured
singleOBXsegment.Thissegmentincludesapre-denedsetofmeasurementsand
theinterpretationdiagnosisstatementsinasingleminimallyformattedeld.This
optionalsousesrepeatingeldsinOBX-5usingthemessagerepetitionseparatorto
createlinebreaks.

SamplecombinedMeasurementanddiagnosissegment:

OBX|1|FT|ECGMEASANDDIAG^||TestReason:ChestPain~Blood
Pressure:120/085mmHG~Vent.Rate:140BPMAtrialRate
:140BPM~P-RInt:120msQRSDur:092ms~QTInt:
272msP-R-TAxes:073066055degrees~QTcInt:415
ms~~Sinustachycardia~Acutepericarditis~NonspecificTwave
abnormality~AbnormalECG~ConfirmedbyWenzel,MarkA.(201)
on6/29/201010:28:30AM~~ReferredBy:Holman,RobertG.
OverreadBy:Wenzel,MarkA.||||||F

2059568-021B

MUSE™v9CardiologyInformation

System

37

HL7OutboundImplementation

WhenanECGresultisdisplayedinanEMRintrue-typefont,theMeasurementand
DiagnosisdatawilldisplaysimilarlytothelayoutofthedataontheactualECGfrom
theGEHealthcareECGacquisitiondeviceasshownbelow:

OBXURLsegment(1)

AURLcompatiblewiththeMUSEEnterpriseIntegrationapplicationcanalsobesent
inanOBXsegment.ThisURLcanthenbestoredwiththestudydataintheEMRand
launchedfromcompatibleEMRstoshowthestudyimageinPDFformat.Purchaseof
oneoftheweb-basedMUSEEnterpriseIntegrationapplicationsisrequiredinorderto
viewtheimagelaunchedwiththeURL.CheckwithyourEMRvendorfortheabilityto
integratewithMUSEusingaURLweblaunch.

EmbeddedImageOption

SampleOBXsegmentwithURL:

OBX|10|RP|MUSEWebURL^||http://MUSETEST/musescripts/museweb.
dll%3FRetrieveTestByDateTime%3FPatientID=0002749255%26Date=
28-06-2010%26Time=15%3a32%3a03%3a255%26TestType=ECG%26Site=
1%26OutputType=PDF%26Ext=PDF||||||F

OBXcodeddiagnosissegmentsanddatapoints(1ton)

OBXsegmentsthatcontainDiagnosisstatementsalongwiththeMUSEstatement
librarycodesandwaveformdatapointscanalsobesentintheORUmessage.These
formatsareuncommonlyusedandthereforearenotdiscussedhere.AMUSEHL7
integrationengineercanexplaintheformatsanduseoftheseOBXsegmentsif
necessary.

IftheHL7embeddedwaveformoptionispurchased,theMUSEORUmessagewill
beconguredtocontainanencodedimageoftheECGreportorselectedpages
fromaStressorHolterstudy.TheimagedataisconvertedtoanASCIIformatthatis
compatiblewithHL7andcanbepassedthroughtheMUSEinterface.Theimagecan
bepassedintheHL7messageencodedineitherUUencodingorBase64encoding.

UUencodedEncoding

UUencodedimagesaresentintheORUmessageinaZsegment.Inaddition,all
datatypesexceptpostscriptareencrypted.Thereceivingsystemmustdecryptand
decodethewaveformimagecomponentofthemessagetoreturnthedatatoan
imagelethatcanbesavedintheEMR.

SampleZ-segment(PDFoption):

38

MUSE™v9CardiologyInformation

System

2059568-021B

StudyFinancialMessageComposition

HL7OutboundImplementation

ZPD|1|PDF|89448^73272^begin644WAV.DAT\X0D\\X0A\

M)5!$1BTQ+C`*)>+C…..

SeeAppendixC“WaveformProcessingRules”onpage137formoreinformationon
ZRIwaveformencryptionandencoding.

Base64Encoding

Base64encodedimagescanbesentintheORUmessageinaZsegmentorinanOBX
segment.Base64encodedimagesarenotencrypted.

SampleZ-segmentwithBase64imageinZPD-3.5:

ZPD|PDF||^^7288^^JVBERi0xLjAKJeLjz9PoCiAgNSAw...|||||F

SampleOBXwithBase64imageinOBX-5.5:

OBX|11|ED|CARDLRR||^^PDF^Base64^JVBERi0xLjAKJeLjz9PoCiAgNSA....|||||F

Ifanancialinterfaceispurchased,theMUSEHL7outboundinterfaceisconguredto
sendnancialtransactionsfromtheMUSEsystem.Financialtransactionsaresent
real-timeorasbatchesasconguredbythereportdistributionandbatchsettingsin
theMUSEsystem.

BatchDataTransfer

BatchDataTransferMessages

Financial(DFT)messagesmaycontainthefollowingmessagesegments.See“HL7

DataSegmentDenitions”onpage51forsegmentdenitions.

MSH–MessageHeader
PID–Patientidentication
PV1–Patientvisit
[OBR]–Observationrequest
FT1–FinancialTransaction

Aspreviouslymentioned,individualresultornanciallesaregeneratedasdescribed
in“TransactionsFromtheMUSEHL7Interface”onpage34.OutboundBatchles
canbesetupasanadditiontothestandardoutgoingHL7interface.Youcan
congurebatchestobesentonceperday,twiceperday,weekly,ormonthly.Atthe
preconguredtimes,abatchmessageiscreatedbygatheringindividualmessages
intoasinglelethatisthensenttotheHIS.

BatchDataTransferisanadditiontotheGEHL7OutboundInterfaces.BatchData
TransfercanbeusedforeitherresultorFinancialmessages.TheBatchDataTransfer
optionincludesamanagementtoolforthebatchlequeueandbatchlelogentries
intheMUSEapplication.

AtthetimesconguredintheMUSEBatchscheduler,thebatchleiscreatedby
gatheringtheindividualmessagesintobatchesandthenintoasinglemessagele.
TheformatoftheBatchmessageiscongurableintheMUSEapplication.EachResult
formattypeorBillingformattypewillbesentinitsownbatchle.TheGEHL7Interface
supportsmultipleBHS/BTSsegmentsetsinasinglebatchle.

2059568-021B

MUSE™v9CardiologyInformation

System

39

HL7OutboundImplementation

HighlevelacknowledgmentmessagescanbesupportedbytheGEHL7Interfacefor
batchmessages,butanacknowledgmentforeachindividualmessagecontained
withinthebatchmessageisnotsupported

ThebatchlesaremaintainedontheGEHealthcaresystemfrom1to365daysand
mayberesentifneededduringthattime.Thelengthoftimethelesaremaintainedis
congurable.

AbatchmessagehasabatchblockconsistingofFileHeader,FileTrailer,BatchHeader,
andBatchTrailersegments.WithinthebatchblockwehaveResultsORUmessages
forBatchResultsorBilling(DFT)messagesforBatchBillingmessage.

BatchResultsMessageStructure

FHS
BHS
ORUMessage1
ORUMessage2
.
.
.
BTS
FTS

BatchBillingMessageStructure

FHS
BHS
DFTMessage1
DFTMessage2
.
.
.
BTS
FTS

SegmentDenition

FHSFileHeaderSegment

SEQ

1
2

3
4

40

Optional/

Required

O

O

O
O

MUSE™v9CardiologyInformation

ELEMENTNAME

FileFieldSeparator
FileEncoding

Characters
FileSendingApplication
FileSendingFacility

System

MUSEField
Length

1
4

15
20MUSE

MUSE
Equivalent

|
^~\&

MUSEBatch

2059568-021B

FHSFileHeaderSegment(cont'd.)

HL7OutboundImplementation

SEQ

Optional/

5

6
7
8
9
10
11
12

FTS—FileTrailerSegment

SEQ

1O
2O

Optional/
Required

Required

ELEMENTNAME

MUSEField
Length

O

O
O
O
O
O
O
O

FileReceiving
Application

FileReceivingFacility
FileCreationDate/Time
FileSecurity
Filename/ID
FileHeaderComment
FileControlID
ReferenceFileControlID

ELEMENTNAME

15CCG

20CCG
26
40
20
80
20
20

MUSEField
Length

FileBatchCount
FileTrailerComment

10
80

MUSE
Equivalent

MUSE
Equivalent

BHS—BatchHeaderSegment

SEQ

1O
2O

3

4

5

6O
7

8O
9O
10O

Optional/
Required

ELEMENTNAME

BatchFieldSeparator
BatchEncoding

MUSEField
Length

1
4

MUSE
Equivalent

|
^~\&

Characters

O

BatchSending

15

MUSEBatch

Application

O

O

BatchSendingFacility

BatchReceiving

20

15CCG

Application
BatchReceivingFacility

O

BatchCreation

20
26

Date/Time
BatchSecurity
BatchNameID/Type
BatchComment

40
20
80

2059568-021B

MUSE™v9CardiologyInformation

System

41

HL7OutboundImplementation

BHS—BatchHeaderSegment(cont'd.)

SEQ

Optional/
Required

11O
12O

BTS—BatchTrailerSegment

SEQ

1O
2O
3

Optional/
Required

ELEMENTNAME

BatchControlID
ReferenceBatchControl

MUSEField
Length

20
20

MUSE
Equivalent

ID

ELEMENTNAME

MUSEField
Length

BatchMessageCount
BatchComment

O

BatchTotals

10
80
100

MUSE
Equivalent

42

MUSE™v9CardiologyInformation

System

2059568-021B

4

HL7QueryImplementation

Introduction

TheHL7StandardInterfaceisusedtoconnectahospital'sinformationsystem(HIS)
totheMUSEHL7Interfacetoexchangedata.TheMUSEHL7Interfacesupports
queryingforpatientdemographicsbypatientID.Theresponsemessage(inbound
data)isprocessedinreal-time.ThisgivesMUSEtheabilitytoensurethatithas
up-to-datepatientdemographicswheninteractingwithasystemthatdoesnot
provideunsolicitedHL7updates.

TheMUSEsystemcanbeconguredtotriggerademographicsquerybasedon
certainuserorsystemactions.

TheMUSEHL7InterfacecanbeconguredtoqueryaHISthroughtheStandardHL7
Interface,oritcanbeconguredtoquerydataprovidedbyawebservice(thisisa
commonapproachinMPIinteractions).

Low-levelCommunications

Thespecicinstallationdetermineswhichlow-levelcommunicationprotocolis
used.TheHL7interfacestandardisdesignedtoaccommodateawidevarietyof
communicationmethodologies,frommessage-basedcommunicationstoletransfer
schemes.

Implementationofthelow-levelcommunicationprotocoldoesnotdirectly
affecttheHL7interfacemessagecontentandfunctionality.Notalllow-level
communicationprotocolssupporthigh-levelacknowledgments.Therefore,if
high-levelacknowledgmentsaredesired,alow-levelprotocolthatsupportsthem
mustbeselected.

TheHL7interfaceassumesthatthelow-levelcommunicationprotocolensuresthat
thedataarriveserror-free.Asaresult,nodataintegritycheckingisdoneatthe
applicationlevel.TheMUSEHL7interfaceallowsonlyTCP/IPsocketcommunication
forHL7queries.

InterfaceDataContent

ThereareonlytwoHL7messagetypesinvolvedintheMUSE-supporteddemographics
query(Q01-thequerymessage,andA19-theresponsemessage).Youmayneed

2059568-021B

MUSE™v9CardiologyInformation

43

System

HL7QueryImplementation

tomapcertaindataeldswithintheHL7segmentsfortheoutgoingortheincoming
message.TheMUSEHL7Interfacecongurationprogram(CCG)denesthemapping.

Thecongurationprogramsusedatatablesandscriptingtodeterminehowtoprocess
outgoingqueryandincomingresponseHL7messages.Thecongurationprograms
matchtheHL7eldsandfunctionsspeciedbyacustomertotheMUSEdataelds

Thefollowingsection“QueryTransactionsoftheMUSEHL7Interface”providesthe
generalformatoftheQ01(query)andA19(response)HL7datamessagesusedbythe
MUSEsystemforthedemographicsquery.

QueryTransactionsoftheMUSEHL7Interface

TheMUSEsystemmanagesandstorespatientstudiesandrelatedpatient
demographicsassociatedwiththem.Insomesituations,patientdemographicsare
notsentbyaHIS,buttheHISsupportsbeingqueriedforthem.Inthesecases,the
MUSEHL7InterfacecanbeconguredtoquerytheHISforpatientdemographicsby
patientID.Patientdemographicqueriescanbeinitiatedmanuallybyauser,and/or
canbeconguredtotakeplaceautomatically.Queriesmaybeconguredtoexecute
automaticallyinthesecases:

•Astudyisnormalized(acquired)

•AstudyisopenedintheMUSEEditor

•Onanancillarydevice/systemdemographicsrequest

OncethemessagesentertheMUSEsystem,ataskparsesthemessagedataand
createsoraltersentriesintheMUSEdatabase.MUSEsystemusersmaythenview
theinformation.

QueryTransactionHL7Messages

Q01-ImmediateresponsequeryandA19-ADTResponsearetwoHL7messages
usedinthepatientdemographicsquery.

Q01-ImmediateResponseQuery

ThismessageisgeneratedbytheMUSEsystem.ItcontainsthepatientIDforwhich
demographicsarerequested.

Itconsistsofthefollowingdatasegments:

•MSH-Messageheader

•QRD-Querydenition

•QRF-Querylter

A19-ADTResponse

44

ExampleHL7QueryMessage(Q01)

ThismessageisgeneratedbytheHIS.Itcontainstherequesteddemographics.

MUSE™v9CardiologyInformation

System

2059568-021B

HL7QueryImplementation

Itconsistsofthefollowingdatasegments:

•MSH-Messageheader

•QRD-Querydenition

•EVN-Eventtype

•PID-Patientidentication

•PV1-Patientvisit

NOTE:

DependingonthecongurationoftheHIS,itmayrequireadifferentHL7query
message,andrespondwithadifferentHL7responsemessage.Inthiscase,the
requireddatasegmentscanbemappedusingtablesintheMUSEHL7Interface.

ExampleHL7ResponseMessage(A19)

2059568-021B

MUSE™v9CardiologyInformation

System

45

HL7QueryImplementation

46

MUSE™v9CardiologyInformation

System

2059568-021B

SystemDataFieldDenitions

TheMUSEsystemstoresthepatientdemographic,visit,andorderinformation.
FollowingarethedenitionsforthevariouseldsthataremaintainedontheMUSE
system.

ADTFields

MUSESystemADTFields—PatientDemographicInformation

5

Type

PatientID

Last,Firstname
AlternatePIDAlternatePatientIdentier,
DateofbirthPatientdateofbirth
Sex

Race

HeightPatientheight
WeightPatientweight
Kanjiname
PrioralternateIDPrioralternatepatient

Mailingaddressline1MailingAddress
Mailingaddressline2MailingAddress
CityCity
StateState32
Postalcode
CountryCountry32
Phonenumber1Patient’srstphonenumber

Description

PatientIdentier,unique
alphanumericvalue

Patientlastandrstname

Patientgender,mappedfrom
HISADTorORMmessage

Patientrace,mappedfrom
HISADTorORMmessage

Alternatepatientidentier

identier

postal/zipcode

Length

16

40,20
16
16
16

16

n/a
n/a
64
16

32
32
32

32

32

2059568-021B

MUSE™v9CardiologyInformation

System

47

SystemDataFieldDenitions

MUSESystemADTFields—PatientDemographicInformation(cont'd.)

Type

Description

Phonenumber2Patient’ssecondphone

number

Extradata1Additionaltextual

informationeld

Extradata2Additionaltextual

informationeld

Extradata3Additionaltextual

informationeld

Extradata4Additionaltextual

informationeld

MUSESystemADTFields—VISIT-PatientVisitInformation

Type

AccountnumberAccountnumber
PatientlocationPatientlocation
Room

BedPatientbedidentier

HISDisposition
AdmissiontypeAdmissiontype(ER,Accident,

AlternateLocationAlternatepatientlocation
AttendingMDnameNameofattendingphysician
AttendingMDHISIDHISIDofattendingphysician

Description

Patientroomidentier

(number)
HISpatientdisposition

L&D,Routine)

Length

32

32

32

32

32

Length

20
20
32
12

19
19

20
40,20
32

AdmittingMDnameNameofadmittingphysician
AdmittingMDHISIDHISIDofadmittingphysician
ReferringMDnameNameofreferringphysician
ReferringMDHISIDHISIDofreferringphysician
ConsultingMDnameNameofconsultingphysician
ConsultingMDHISIDHISIDofconsultingphysician
OtherHealthcareProvider

name
OtherHealthcareProvider

HISID
PrimaryDiagnosis

48

MUSE™v9CardiologyInformation

Nameofotherhealthcare
provider

HISIDofotherhealthcare
provider

Primarypatientdiagnosis

System

40,20
32
40,20
32
40,20
32
40,20

32

32

2059568-021B

MUSESystemADTFields—VISIT-PatientVisitInformation(cont'd.)

SystemDataFieldDenitions

Type

Description

SecondaryDiagnosisSecondarypatientdiagnosis
TertiaryDiagnosis

Tertiarypatientdiagnosis
AdmitDiagnosisPatientadmitdiagnosis
AdmissionDate/TimeAdmissionDate/Timen/a
HospitalServiceHospitalServiceexpectedfor

thisvisit
AdmissionsourceSourceofpatientadmission
AmbulatorystatusAmbulatorystatusofpatient
AlternateVisitNumberAlternatevisitnumber
Visitnumber

Visit/encounternumber
DischargedispositionDischargedisposition

(dischargedtohome,expired)
ServicefacilityFacilitywhereserviceis

beingperformed
DischargeDate/Time

Dateofpatientdischarge
Extradata1Additionaltextual

informationeld
Extradata2Additionaltextual

informationeld
Extradata3Additionaltextual

informationeld
Extradata4Additionaltextual

informationeld

Length

32
32
80

19

32
64
20
20
32

16

date/time
32

32

32

32

OrderFields

MUSESystemOrderFields—Informationforanorderforastudyoccurrence

Type

PlacersordernumberHIS-generatedordernumber
Startdate/time

Filler’sOrderNumberFiller’sOrderNumber
Priority

ParentordernumberParentOrderNumber

1.TheMUSEsystemacceptsordernumbersupto22characters.However,manyoftheolderGEHealthcareacquisitiondevicescanaccept
amaximumof9characters.Ifyouplantodownloadorderstoacquisitiondevices,consultwithyourHL7Integrationengineerson
strategiestomanageordernumberswithmorethan9characters.

2059568-021B

MUSE™v9CardiologyInformation

Description

Timetheorderisscheduled
forthestudytobeperformed

Scheduledpriorityfororder
(STAT,Routine,…)

System

Length

1

22

n/a

22
32

22

49

SystemDataFieldDenitions

MUSESystemOrderFields—Informationforanorderforastudyoccurrence(cont'd.)

Type

Orderplaceddate/time

Description

Dateandtimetheorderwas
placedontheHISsystem

PlacedbynameNameofpersonwhoplaced

order

PlacedbyHISIDHISSystemIDofpersonwho

placedtheorder

OrderingMDnameOrderingphysicianrstand

lastname

OrderingMDHISIDHISSystemIDofordering

physician,alphanumeric
value

HIStesttype

Universalserviceindicator
codeorbillingcode

HIStesttypetext
Testreason
Comments

Textualdescriptionofstudy
ReasonforTest(textual)
OrderingComments(textual)

Length

n/a

40,20

32

40,20

32

32

64
80
80

DangerCodeDangerCode
ExtraDataField1Additionaltextual

informationeld

ExtraDataField2Additionaltextual

informationeld

ExtraDataField3Additionaltextual

informationeld

ExtraDataField4Additionaltextual

informationeld

n/a
32

32

32

32

50

MUSE™v9CardiologyInformation

System

2059568-021B

HL7DataSegmentDenitions

ThefollowingtablesprovidedenitionsforthevariousHL7datasegmentssupported
bytheMUSEHL7interface.Eachsegmenteldisprovidedinaseparatetablethat
describestheeldssupportedbytheMUSEsystem,includingtheeldlengthand
optionality.ThetablesdisplaythedefaultlocationsforthedatainaMUSEmessage.
TheMUSEHL7engineerworkswiththecustomertodetermineiftheyneedtore-map
anydataeldforpropermessageprocessing.

NOTE:

TheeldlengthsarethemaximumlengthstheMUSEsystemsupports,notthe
maximumlengthbytheHL7denitions.

Inbound(toMUSE)Segments

ExplanationofTableHeadings—Inbound

6

Table
Heading

HL7Seq

Item#

MUSEField
Length

Supported
Y/N

Required
Y/C/N

HL7Element
Name

MUSE
Equivalent

TT
Notes

Description

Thisindicatesthesequencenumbersthatcanbeincludedaspartofthe
message.

TheHL7standarditemidentier.
ThisisthemaximumlengthoftheeldwithintheMUSEapplication.

ThislengthdoesnotincludeHL7delimiters.

YesifthedefaultMUSEinterfacecongurationsupportsthiseld.

Yiftheeldisrequired.
Ciftheeldisconditionallyrequired.
Niftheeldisoptional

ThisisthespecicHL7eldreferencedbythesegmentandsequence
number.

ThisindicatestheeldintheMUSEapplicationthatcorrespondstotheHL7
eld.
Notapplicableindicatesthattheelddoesnothaveacorrespondingeld
withintheMUSEapplication.

ThisisaY/Nindicatorspecifyingifthiseldrequiresatranslationtable.
Thisspaceisprovidedforaddingnotes.

2059568-021B

MUSE™v9CardiologyInformation

System

51

52

MessageHeaderSegment(MSH)Denitions

HL7DataSegmentDenitions

HL7

Item#MUSE

Seq

1000011
200002

SupportedRequired

Field

Length

YY

4YY

HL7

Element

Name

FieldSeparatorNotApplicable
Encoding

MUSE

Equivalent

NotApplicable

TT

Notes

N
N

Characters

3

0000315

4

0000420

5

MUSE™v9CardiologyInformation

0000515

60000620
7

0000726

System

90000915

100001020

YN

Sending

Application
YN
YN

SendingFacilityNotApplicable

Receiving

Application
YY
YN

ReceivingFacility

Date/Timeof

Message
YYMessageType
YY

Messagecontrol

ID

NotApplicable

NotApplicable

MUSESite
NotApplicable

NotApplicable
NotApplicable

N

TheSendingApplicationeldvalueis

dependentonthemessageoriginator.
N
N

TheReceivingApplicationFieldvalueis

dependentonthemessageoriginator.
Y
N

N
N

TheformatoftheMessageControl

IDisdeterminedbytheoriginating

application.Thereceivingsystem

mustbeabletoaccepttransactions

regardlessoftheformatofthiseld,

andmustreturntheControlIDinits

originalformat.Thiseldisnotrequired

whenhighlevelacknowledgmentsare

notused.

1100011
120001260

3YY

YY

ProcessingID
VersionID

NotApplicable
NotApplicable

N
N

2059568-021B

2059568-021B

MessageAcknowledgmentSegment(MSA)Denitions

HL7

Seq

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

1000022

YY

Acknowl-

NotApplicable

N

edgmentCode

20000326

YY

MessageControl
ID

NotApplicable

N

ThemessagecontrolIDforthe

acknowledgmentwillmatchthecontrol

IDofthemessagebeingacknowledged.

3

0000480

MUSE™v9CardiologyInformation

System

YNTextMessage

NotApplicable

N

53

54

EventTypeSegment(EVN)Denitions

HL7DataSegmentDenitions

HL7

Seq

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

100099

MUSE™v9CardiologyInformation

System

3Y

Y(seenote)

EventTypeCodeNotApplicable

N

RequiredforADTmessagesonly.

2059568-021B

2059568-021B

PatientIdenticationSegment(PID)Denitions

HL7

Seq.

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

100104
3

0010616

4YY

YY

SetID-PID

PatientIdentier

NotApplicable
PatientID

N
N

List

4

0010716

YN

Secondary

SecondaryID

N

PatientID-PID

5.10010840

YN

PatientLast

LastNameN

Name

MUSE™v9CardiologyInformation

5.20010820

YN

PatientFirst

FirstName

N

Name

7

0011026

System

80011116
90011264

100011316

11.10011432

YN

Date/Timeof

DateofBirth

Birth
YN
YN

SexSex

PatientAlias

KanjiName

YNRaceRaceY

YN

PatientAddress

MailingAddress

N

Timevaluewillbedisregardedbythe

MUSEsystem.
Y
N

N

Line

11.20011432

YN

PatientAddress

MailingAddress

N

Line

11.30011432

11.40011432

11.50011432

11.60011432
130011632

55

YN
YN
YN
YN
YN

CityCity
StateState
PostalCodePostalCode
CountryCode
PhoneNumber–

Home

Country

PhoneNumber
1

N
N
N
N
N

56

PatientIdenticationSegment(PID)Denitions(cont'd.)

HL7DataSegmentDenitions

HL7

Seq.

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

140011732

180012120

190012216

YN

YN

YN

PhoneNumber­Business

PatientAccount
Number

SSN-Patient

PhoneNumber
2

Account
Number

NotApplicable

N

N

N

SSNisstoredintheADTdatabasebutis
notdisplayedintheMUSEsystem.

MUSE™v9CardiologyInformation

System

2059568-021B

2059568-021B

PatientVisitSegment(PV1)Denitions

HL7

Seq.

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

100131
20013216

3.10013320

4YY

YN
YN

SetID-PV1

NotApplicable
PatientClassPatientClass
AssignedPatient

HISLocation
Location—Point

N
Y
Y

ThisvalueismappedtotheMUSE
LocationintheMUSEsystem.

ofCare

3.20013320

3.3

MUSE™v9CardiologyInformation

4

7.10013732

0013316
00134

4YN

YNRoomRoomN
YN

BedBed
AdmissionTypeAdmissionType

YN

AttendingDoctorAttendingMD

N
N
N

HISID

System

7.20013740

YN

AttendingDoctorAttendingMD

N

NameLast

7.3

0013720

YN

AttendingDoctorAttendingMD

N

NameFirst

8.10013832

YN

ReferringDoctorReferringMD

N

HISID

8.20013840

YN

ReferringDoctorReferringMD

N

NameLast

8.30013820

YN

ReferringDoctorReferringMD

N

NameFirst

9.10013932

9.20013940

9.30013920

100014019

57

YN

YN

YN

YN

Consulting
Doctor

Consulting
Doctor

Consulting
Doctor

HospitalServiceHospital

ConsultingMD

HISID

ConsultingMD

NameLast

ConsultingMD

NameFirst

Service

N

N

N

N

58

PatientVisitSegment(PV1)Denitions(cont'd.)

HL7DataSegmentDenitions

HL7

Seq.

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE

Equivalent

TT

Notes

Length

1400144
15001452

17.10014732

3YN

YN

YN

AdmitSourceAdmitSource
Ambulatory

Status

Ambulatory

Status
AdmittingDoctorAdmittingMD

N
N

N

HISID

17.20014740

MUSE™v9CardiologyInformation

17.30014720

YN

YN

AdmittingDoctorAdmittingMD

NameLast
AdmittingDoctorAdmittingMD

N

N

NameFirst

System

190014920

YY

VisitNumberVisitNumber

N

ForCustomerFacilitiesthatdon'thave
oruseVisitNumbers,theMUSEsystem
canusetheAccountnumber(from
PID-18)forthiseld.

3600166

39001692

3YN

YN

Discharge
Disposition

ServicingFacility

Discharge

Disposition

Servicing

N

N

Facility

44
45

0017426
0017526

YN
YN

AdmitDate/Time
Discharge

AdmitDate

DischargeDate

N
N

Date/Time

500018020

52.10127432

2059568-021B

52.20127440

52.30127420

YN

YN

YN

YN

AlternateVisit
Number

OtherHealthcare
Provider

OtherHealthcare
Provider

OtherHealthcare
Provider

NotApplicable

PrimaryCare

MDHISID

PrimaryCare

MDNameLast

PrimaryCare

MDNameFirst

N

ThisvalueisnotdisplayedintheMUSE
application.

N

N

N

2059568-021B

MergePatientInformationSegment(MRG)Denitions

HL7

Seq

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

10021116

3

0023120

Y

C

PriorPatient

PriorID

IdentierList

Y

C

PriorPatient

NotApplicable

N

RequiredforA18,A34,andA36message
types.

N

RequiredforA35messages.

AccountNumber

5

0127920

MUSE™v9CardiologyInformation

System

Y

C

PriorVisit

NotApplicable

Number

N

RequiredforA36,A42,A46message
types.

59

60

CommonOrderSegment(ORC)Denitions

HL7DataSegmentDenitions

HL7

Seq

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

1002152
20021622

3

7.4

MUSE™v9CardiologyInformation

7.60022122

0021722

0022126

YY
YY

YN

YN

YN

OrderControlNotApplicable
PlacerOrder

Number
FillerOrder

Number
Quantity/Timing

-StartDate/Time
Quantity/Timing

Placer'sOrder
Number

Filler'sOrder
Number

StartDate/
Time

Priority

Y
N

N

N

Y

-Priority

80022222

System

90022326

10.10022432

10.20022440

10.30022420

12.10022632

12.20022640

2059568-021B

12.30022620

YNParent

YN

YN

YN

YN

YN

YN

YN

Date/Timeof
Transaction

EnteredBy-ID
number

EnteredBy­FamilyName

EnteredBy
–GivenName

Ordering
Provider-ID
Number

Ordering
Provider–Family
Name

Ordering
Provider–Given
Name

ParentOrder
Number

OrderPlaced
Time

PlacedBy-HIS
ID

PlacedBy-last
name

PlacedBy–rst
name

Ordering
Provider—HIS
ID

Ordering
Provider–Last
Name

Ordering
Provider–First
Name

N

N

N

N

N

N

N

N

2059568-021B

ObservationRequestSegment(OBR)Denitions(Inbound)

HL7

Seq

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

100237

4.10023832

4YY

YY

SetID—OBR

UniversalService

NotApplicable
HISTestType

N
Y

ID—Identier

4.20023832

120024664

31.20026380

MUSE™v9CardiologyInformation

System

YN

YN
YN

UniversalService
ID–Text

DangerCodeNotApplicable
ReasonforStudy

HISTestType
Text

TestReasonN

N

N

61

62

NoteSegment(NTE)Denitions

HL7DataSegmentDenitions

HL7

Seq

Item#MUSE

SupportedRequiredHL7Element

Field

Name

MUSE
Equivalent

TT

Notes

Length

100096
3

0009880

4YY

YN

Set–IDNTE
Comment

NotApplicable
Order

N
N

Comments

MUSE™v9CardiologyInformation

System

2059568-021B

2059568-021B

ObservationResultSegment(OBX)Denitions

HL7

Seq

Item#MUSE

SupportedRequiredElementname

Field

MUSE
Equivalent

TT

Notes

Length

100569

4YY

SetID–OBX

NotApplicable

N

SegmentRepetition1containsthe
patientheight.

SegmentRepetition2containsthe
patientweight.

5.10057310

YN

Observation
Value

SegID=1,
HeightValue

N

inInches

MUSE™v9CardiologyInformation

SegID=2,
WeightValue
inlbs

5.20057310

System

YN

Observation
Value

SegID-1,
HeightValue
incm

N

SegID=2,
WeightValue
inkg

63

64

DiagnosisSegment(DG1)Denitions

HL7DataSegmentDenitions

HL7

Seq

Item#MUSE

SupportedRequiredElementname

eld

MUSE
Equivalent

TT

Notes

length

100375
3

0037732

4YY

YN

SetID–DG1

DiagnosisCode
–DG1

NotApplicable
Primary

Diagnosis
Secondary

Diagnosis
Tertiary

Diagnosis(see

MUSE™v9CardiologyInformation

4

0037880

YN

Diagnosis
Description

System

note)

Admitting
Diagnosis

N
N

AsDG1canbearepeatinggroup,
DG1-3.1canbeusedformultiple
diagnoses.TheMUSEsystemaccepts
upto3repeatsandplacesthevaluesin
DG1-3.1intothePrimary(rstrepeat),
Secondary(secondrepeat),andTertiary
(thirdrepeat)Diagnosiseldsinthe
MUSE.system.

N

FromtherstrepetitionoftheDG1
segment.

2059568-021B

Outbound(fromMUSE)Segments

ExplanationofTableHeadings—Outbound

HL7DataSegmentDenitions

Table
Heading

HL7Seq

Item#

MUSEField
Length

PresentA/C

HL7Element
Name

MUSE
Equivalent

Notes

Description

Thisindicatesthesequencenumbersthatcanbeincludedaspartofthe
message.

TheHL7standarditemidentier
ThisisthemaximumlengthoftheeldwithintheMUSEapplication.

ThislengthdoesnotincludeHL7delimiters.
A(Always)indicateseldsthatarepopulatedforanyMUSEOBmessage.C

(Conditional)indicatesaeldthatmaybepopulateddependingonthestudy
status,and/orstudyadministrativeorclinicalcompleteness.

ThisisthespecicHL7eldreferencedbythesegmentandsequence
number.

ThisindicatestheeldintheMUSEapplicationthatcorrespondstotheHL7
eld.
Notapplicableindicatesthattheelddoesnothaveacorrespondingeld
withintheMUSEapplication.

Thisspaceisprovidedforaddingnotes.

2059568-021B

MUSE™v9CardiologyInformation

System

65

66

MessageSegment(MSH)Denitions

HL7DataSegmentDenitions

HL7SeqItem#

MUSE™v9CardiologyInformation

1000011
200002
3
4
5

0000315
0000420

0000515
60000620
7

0000726
90000915

MUSEeld
length

4Y

Present

HL7ElementnameMUSEEquivalent

A/C

Y

FieldSeparator

EncodingCharacters
Y
Y
Y
Y
Y

SendingApplication

SendingFacility

ReceivingApplication

ReceivingFacility

Date/TimeOfMessage
YMessageType

Notes

|
^~|&

MEIMUSE
MEIMUSE
HISSystem
CCG

ORUmessageswill
sendORU^R01

DFTmessageswill

System

100001020

Y

MessageControlID

sendDFT^P03
date/timestamp

CCYYM
MDDHH

MMSS
1100011
120001260

3Y

ProcessingID

Y

VersionID

P

2.4

2059568-021B

2059568-021B

PatientID(PID)SegmentDenitions(ORUandDFT)

HL7SeqItem#

MUSEeld
length

100104
3
4

0010616
0010716C

4A

5.10010840C

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

SetID-PID

A

PatientIdentierList
SecondaryPatientID-

PID
PatientLastName

NotApplicable
PatientID
SecondaryIDPresentifenteredbyuserorsenttotheMUSE

systemintheADTregistrationmessage.

LastName

PresentifenteredbyuserorsenttotheMUSE
systemintheADTregistrationmessage.

5.20010820C

MUSE™v9CardiologyInformation

7

0011026C

PatientFirstNameFirstName

Date/TimeofBirth

PresentifenteredbyuserorsenttotheMUSE
systemintheADTregistrationmessage.

DateofBirthPresentifenteredbyuserorsenttotheMUSE

systemintheADTregistrationmessage.

80011116CSexSex

System

90011264C

100011316C

PatientAlias
RaceRace

KanjiName

PresentifenteredbyuserorsenttotheMUSE
systeminanADTregistrationmessage.

PresentifsentintheADTregistrationmessage.
PresentifenteredbyuserorsenttotheMUSE

systemintheADTregistrationmessage.

11.10011432C

11.20011432C

11.30011432C

11.40011432CStateState

11.50011432C

11.60011432C

PatientAddressLine1MailingAddressPresentifsentintheADTregistrationmessage.
PatientAddressLine2MailingAddressPresentifsentintheADTregistrationmessage.
CityCity

PresentifsentintheADTregistrationmessage.

PresentifsentintheADTregistrationmessage.
PostalCodePostalCodePresentifsentintheADTregistrationmessage.
CountryCode

Country

PresentifsentintheADTregistrationmessage.

67

130011632C

PhoneNumber-HomePhoneNumber1PresentifsentintheADTregistrationmessage.

68

PatientID(PID)SegmentDenitions(ORUandDFT)(cont'd.)

HL7DataSegmentDenitions

HL7SeqItem#

MUSEeld
length

140011732C

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

PhoneNumber-

PhoneNumber2PresentifsentintheADTregistrationmessage.

Business

180012120C

PatientAccount

AccountNumberPresentifsentintheADTregistrationmessage.

Number

190012216C

MUSE™v9CardiologyInformation

System

SSNNumber-PatientNotApplicablePresentifsentintheADTregistrationmessage.

2059568-021B

2059568-021B

PatientVisitSegment(PV1)Descriptions(ORUandDFT)

HL7SeqItem#

MUSEeld
length

100131

4A

20013216C

3.10013320

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

SetID-PV1

NotApplicable

PatientClassPatientClassPresentifsentintheADTregistrationmessage.

A

AssignedPatient
Location-pointof

MUSELocation
Name

care

3.20013320C

AssignedPatient
Location-Room

MUSE™v9CardiologyInformation

3.3

3.4

0013316C

001338

AssignedPatient
Location-Bed

A

AssignedPatient

Room

PresentifenteredbyuserorsenttotheMUSE
systemintheADTregistrationmessage.

BedPresentifenteredbyuserorsenttotheMUSE

systemintheADTregistrationmessage.

MUSESite

Location-Facility

System

3.7

0013316C

AssignedPatient

HISLocation

PresentifsentintheADTregistrationmessage.

Location-Building

3.800133

4A

AssignedPatient

MUSELocationID

Location-Floor

4

00134

7.10013732C

7.20013740C

4

C

AdmissionTypeAdmissionTypePresentifsentintheADTregistrationmessage.
AttendingDoctorAttendingMDHISIDPresentifsentintheADTregistrationmessage.
AttendingDoctorAttendingMDName

PresentifsentintheADTregistrationmessage.

Last

7.3

0013720C

AttendingDoctorAttendingMDName

PresentifsentintheADTregistrationmessage.

First

8.10013832C

ReferringDoctorReferringMDHISIDPresentifenteredbyuserorsenttotheMUSE

systemintheADTregistrationmessage.

8.20013840C

8.30013820C

ReferringDoctorReferringMDName

Last

ReferringDoctorReferringMDName

First

PresentifenteredbyuserorsenttotheMUSE
systemintheADTregistrationmessage.

PresentifenteredbyuserorsenttotheMUSE
systemintheADTregistrationmessage.

69

70

PatientVisitSegment(PV1)Descriptions(ORUandDFT)(cont'd.)

HL7DataSegmentDenitions

HL7SeqItem#

MUSEeld
length

9.10013932C

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

ConsultingDoctorConsultingMDHIS

PresentifsentintheADTregistrationmessage.

ID

9.20013940C

ConsultingDoctorConsultingMD

PresentifsentintheADTregistrationmessage.

NameLast

9.30013920C

ConsultingDoctorConsultingMD

PresentifsentintheADTregistrationmessage.

NameFirst

MUSE™v9CardiologyInformation

1400144

3

C

15001452C

100014019C

System

17.10014732C

17.20014740C

HospitalServiceHospitalServicePresentifsentintheADTregistrationmessage.
AdmitSourceAdmitSourcePresentifsentintheADTregistrationmessage.
AmbulatoryStatusAmbulatoryStatusPresentifsentintheADTregistrationmessage.
AdmittingDoctorAdmittingMDHISIDPresentifsentintheADTregistrationmessage.
AdmittingDoctorAdmittingMDName

PresentifsentintheADTregistrationmessage.

Last

17.30014720C

AdmittingDoctorAdmittingMDName

PresentifsentintheADTregistrationmessage.

First

190014920C

VisitNumberVisitNumberPresentifenteredbyuserorsenttotheMUSE

systemintheADTregistrationmessage.

3600166

3

C

DischargeDispositionDischarge

PresentifsentintheADTregistrationmessage.

Disposition
390016916C
44

2059568-021B

45

0017426C
0017526C

500018020C

ServicingFacilityServiceFacilityPresentifsentintheADTregistrationmessage.
AdmitDate/Time
DischargeDate/Time

AdmitDatePresentifsentintheADTregistrationmessage.

DischargeDatePresentifsentintheADTregistrationmessage.

AlternateVisitNumberNotApplicablePresentifsentintheADTregistrationmessage.

2059568-021B

PatientVisitSegment(PV1)Descriptions(ORUandDFT)(cont'd.)

HL7SeqItem#

MUSEeld
length

52.10127432C

52.20127440C

52.30127420C

MUSE™v9CardiologyInformation

System

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

OtherHealthcare
Provider

OtherHealthcare
Provider

OtherHealthcare
Provider

PrimaryCareMDHIS

ID

PrimaryCareMD

LastName

PrimaryCareMD

FirstName

PresentifsentintheADTregistrationmessage.

PresentifsentintheADTregistrationmessage.

PresentifsentintheADTregistrationmessage.

HL7DataSegmentDenitions

71

72

ObservationRequestSegment(OBR)Denitions

HL7DataSegmentDenitions

HL7SeqItem#

MUSEeld
length

100237

4A

20021622C

3

0021722C

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

SetID

PlacerOrderNumberPlacer'sOrder

NotApplicable

PresentifenteredbyuserorsenttotheMUSE

Number

systemintheORMOrdermessage.

FillerOrderNumber+Filler'sOrderNumberPresentifsenttotheMUSEsystemintheORM

Ordermessage.

MUSE™v9CardiologyInformation

4.10023832C

UniversalServiceID­Identier

4.20023832C

UniversalServiceID­Text

System

4.5

0023812

A

UniversalServiceID-

HISTestType

HISTestTypeText

MUSETestName

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

AlternateText

60024026

7.10024126

A

A

RequestedDate/TimeCurrentDate/Time

Observation

TestDate/TimeThedate/timethestudywasperformed.

Date/Time#

7.20024126

A

Observation

TestTime

StudyTimeisinWebformat.

Date/Time#

100024432C

13.10024712

2059568-021B

13.20024710C
140024826C

CollectorIdentierMedicareIDof

ReturnedifbuiltinMUSESetup.

AcquisitionTech

A

RelevantClinicalInfo-

UserDenedLabel

Text
RelevantClinicalInfoUserDenedTextIfenteredbyaMUSEuser
SpecimenReceived

EditDate/Time

Presentifstudywasedited.

Date/Time

2059568-021B

ObservationRequestSegment(OBR)Denitions(cont'd.)

HL7SeqItem#

16.10022632C

16.20022640C

16.30022620C

MUSE™v9CardiologyInformation

200025360
220025526

MUSEeld
length

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

OrderingProvider-ID
Number

OrderingProvider­FamilyName

OrderingProvider­GivenName

A
A

FillerField1+
ResultsRpt/Status

OrderingProvider­HISID

OrderingProvider­LastName

OrderingProvider­FirstName

MUSETestID

CurrentDate/Time

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

Chng-Date/Time

System

25002581
290026122C

310026380C

A

ResultStatus
Parent

ReasonforStudy

MUSETestStatus

ParentOrder
Number

TestReason

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

PresentifenteredbyuserorsenttotheMUSE
systemintheORMOrdermessage.

32.10026432C

32.20026440C

32.30026420C

32.1100264

5

C

PrincipalResult
Interpreter

PrincipalResult
Interpreter

PrincipalResult
Interpreter

PrincipalResult
Interpreter

OverreaderMedicare
ID

OverreaderLast
Name

OverreaderFirst
Name

OverreaderMUSE
UserID

Presentifthestudywasoverreadandthe
overreaderwasassignedaMedicareID.

Presentifthestudywasoverread.

Presentifthestudywasoverread.

Presentifthestudywasoverread.

HL7DataSegmentDenitions

73

74

ObservationRequestSegment(OBR)Denitions(cont'd.)

HL7DataSegmentDenitions

HL7SeqItem#

MUSEeld
length

33.10026532C

33.20026540C

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

AssistantResult
Interpreter

AssistantResult

FellowMedicareIDPresentifstudywasreadbyaFellowandthe

FellowwasassignedaMedicareID.

FellowLastNamePresentifthestudywasreadbyaFellow.

Interpreter

MUSE™v9CardiologyInformation

33.3

0026520C

AssistantResult

FellowFirstNamePresentifthestudywasreadbyaFellow.

Interpreter

System

33.1100265

5

C

AssistantResult

FellowMUSEUserIDPresentifthestudywasreadbyaFellow.

Interpreter

34.10026632C

TechnicianAcquisitionTech

MedicareID

34.20026640C

TechnicianAcquisitionTechLast

Name

34.3

0026620C

TechnicianAcquisitionTechFirst

Name

34.1100266

5

C

TechnicianAcquisitionTech

MUSEUserID

35.10026732C

Transcriptionist

EditorMedicareIDPresentifstudywaseditedandtheeditorwas

assignedaMedicareID.

35.20026740C

2059568-021B

35.3

0026720C

35.1100267
360026826C

5

C

Transcriptionist
Transcriptionist
Transcriptionist

ScheduledDate/Time

EditorLastNamePresentifthestudywasedited.
EditorFirstNamePresentifthestudywasedited.
EditorMUSEUserIDPresentifthestudywasedited.
OrderStart

Date/Time

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

2059568-021B

FinancialTransactionSegment(FT1)Denitions

SeqHL7Item

Number

100355
4

5

0035826
0035926

GEField
Length

4A

Present

ElementNameMUSEEquivalent

Notes

A/C

SetID

A
A

TransactionDate
TransactionPosting

TestDate/Time
CurrentDate/Time

Date

6.2003608

A

TransactionType

CG

TheMUSEinterfaceonlysupportscharge
transactiontypes.Creditsarenotsupported
throughtheinterface.

MUSE™v9CardiologyInformation

7.20036132C

80036232C

TransactionCode

Transaction
Description

System

1000364

4A

TransactionQuantity

HISTestTypeText

HISTestType

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

TheMUSEinterfacereportsnancialinformation
onastudy-by-studybasis,thereforethequantity
eldisalwaysone(1).

16.10013320

A

AssignedPatient
Location-Pointof

MUSELocation
Name

MUSELocationnameofwherethestudywas
performed.

Care

16.20013320C

16.30013316C

16.4001338

AssignedPatient
Location-Room

AssignedPatient
Location-Bed

A

AssignedPatient

Room

PresentifenteredbytheuserorsenttotheMUSE
systemintheADTregistrationmessage.

BedPresentifenteredbytheuserorsenttotheMUSE

systemintheADTregistrationmessage.

MUSESite

Location-Facility

16.70013316C

AssignedPatient

HISLocation

PresentifsentintheADTregistrationmessage.

Location-Building

75

76

FinancialTransactionSegment(FT1)Denitions(cont'd.)

HL7DataSegmentDenitions

SeqHL7Item

Number

16.800133

GEField
Length

4A

18001482C

20.10026432C

MUSE™v9CardiologyInformation

20.20026440C

System

20.30026420C

20.1100264

5

21.10022632C

21.20022640C

21.30022620C

Present

ElementNameMUSEEquivalent

Notes

A/C

AssignedPatient
Location-Floor

PatientType

PrincipalResult
Interpreter

PrincipalResult
Interpreter

PrincipalResult
Interpreter

C

PrincipalResult
Interpreter

OrderingProvider-ID
number

OrderingProvider­FamilyName

OrderingProvider­GivenName

MUSELocationID

MUSELocationIDofwherethestudywas
performed.

PresentifsentintheADTregistrationmessage.

OverreaderMedicareIDPresentifthestudywasoverreadandthe

overreaderwasassignedaMedicareID.

OverreaderLast

Presentifthestudywasoverread.

Name
OverreaderFirst

Presentifthestudywasoverread.

Name
OverreaderMUSE

Presentifthestudywasoverread.

UserID

OrderingProvider­HISID

OrderingProvider­LastName

OrderingProvider­FirstName

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

PresentifsenttotheMUSEsystemintheORM
Ordermessage.

2059568-021B

230026722C

PlacerOrderNumberPlacer'sOrder

Number

PresentifenteredbytheuserorsenttotheMUSE
systemintheORMOrdermessage.

2059568-021B

FinancialTransactionSegment(FT1)Denitions(cont'd.)

SeqHL7Item

Number

GEField
Length

24.10026732C

Present

ElementNameMUSEEquivalent

Notes

A/C

Transcriptionist

EditorMedicareIDPresentifstudywaseditedandtheeditorwas

assignedaMedicareID.

24.20026740C

24.30026720C

24.1100267

MUSE™v9CardiologyInformation

System

5

C

Transcriptionist
Transcriptionist
Transcriptionist

EditorLastNamePresentifthestudywasedited.
EditorFirstNamePresentifthestudywasedited.
EditorMUSEUserIDPresentifthestudywasedited.

HL7DataSegmentDenitions

77

78

ObservationResultSegment(OBX)Denitions

HL7DataSegmentDenitions

HL7SeqItem#

100569
2005702
3

0057180

MUSEeld
length

4A

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

SetID–OBX
A
A

ValueType

ObservationIdentierAppendixB“OBX

ST,RP.CE,TX,FT

Congurable

CodeTables”on
page129.

5

0057365536C

ObservationValue

Measurement,

RepeatingField
Diagnosis,or
EncodedImage

MUSE™v9CardiologyInformation

60057460C

11005791

System

A

Units
ObservResultsStatus

Value
IfApplicable
MUSETestStatus

2059568-021B

2059568-021B

WaveformSegment(ZRI)Denitions,UUencoded

HL7SeqItem#

3.1

MUSE™v9CardiologyInformation

3.2

MUSEeld
length

1
2

N/A
N/A

N/A

N/A

4A
3A

10

10

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

SetID

N/A

A

N/A

N/A
Waveform

Description
Numberof

See“GraphicalResultReportingMessages”onpage

20

Totalnumberofbytesinthedataeld.

EncryptedBytes

A

N/A

Numberof
UnencryptedBytes

TotalnumberofbytesofdataoncetheHL7escape

charactersareremovedfromthedataandpossibly

UUDecoded.

System

3.3

N/AN/A

A

N/A

Data

79

80

WaveformSegmentDenitions,Base64encoded

HL7DataSegmentDenitions

HL7SeqItem#

1

3.3

N/A

N/A

MUSEeld
length

3A

16

Present

HL7ElementnameMUSEEquivalent

Notes

A/C

N/A

WaveformImage
Type

A

N/A

EncodedWaveform

See“GraphicalResultReportingMessages”onpage

20

StringLength

MUSE™v9CardiologyInformation

3.5

11

System

N/AN/A

N/A

1

A

N/A

EncodedWaveform
String

A

N/A

TestStatus

2059568-021B

7

HISDataManagement

ThissectiondescribeshowtocongureMUSEtoperformclean-upofoldHIS
Patient/VisitAccountandOrderData.Theusercancongurenumberofdaysto
considerforcleanupandalsoschedulethetimewhenthisscheduledtaskcanrun
onMUSE.

Setup

MUSEmustbesetuptoperformclean-upofoldHISdata.

1.GotoSetup>Sites>HISSettings>General.

2.AttheNumberofdaystoretainvisitsafterdischargeisreceivedeld,type
anumberupto366days.Thisoptionallowsyoutosetthenumberofdaysto
retaindischargedaccounts.

Thisoptionisforremovingoldervisits/accountsforwhichadischarge
transactionhasbeenreceived(MUSEaccountstatusisClosed).

3.AttheNumberofdaystoretaincompletedOrderseld,typeanumberupto
255days.Thisoptionallowsyoutodenethenumberofdaysbeforecompleted
ordersarepurged.

Thisoptionistodeletecompletedordersthathavebeencompletedforlonger
thanthenumberofdayscongured.

2059568-021B

MUSE™v9CardiologyInformation

System

81

HISDataManagement

4.AttheDefaultnumberofdaystoretainopenOrdersafterOrderdateeld,
typeanumberupto255days.Thisoptionallowsyoutosethowlongyouwant
anopenorderleftintheopenorderlist.

Thisoptionistoretainordersthatarenotfullledforoveraspeciednumber
ofdays.

5.ClickApplyandthenclickOK.

82

MUSE™v9CardiologyInformation

System

2059568-021B

SchedulingHISDataMaintenance

TheHISDataManagementtaskwillcleanexpiredAccounts/Visits,Patientsandorders
fromthetemporaryHIStablesasconguredintheHISsettingscongurationinthe
abovesection.TheusercansetthetimeofdaythattheHISDataMaintenancewillrun.

1.GotoSetup>ScheduledTasks>HISDataMaintenance>.Thendoubleclick
toopentheGeneralscreen.

HISDataManagement

2.SelecttheScheduleTimetostartthemaintenanceprocess.

3.ClickApplyandthenclickOK.

MaintainingtheLogandQueue

ThisoptionallowstheusertosetthenumberofdaystheHISEventLogentriescanbe
heldintheMUSEsystembeforecleanup.

1.HighlightScheduledTasksinthemenutreeattheleftsideofthewindow.

2.HighlightLogandQueueMaintenance.Right-clickandselectProperties.The
ScheduledTaskProperty—LogsandQueueswindowopens.

3.HighlightHISEventLoginthemenutreeattheleftsideofthewindow.Set
theDaystoHold.

2059568-021B

MUSE™v9CardiologyInformation

System

83

HISDataManagement

4.SelecttheXMLdeviceifapplicable.

5.ClickApply,andthenOKwhennished.

84

MUSE™v9CardiologyInformation

System

2059568-021B

HL7ImplementationFAQs

FrequentlyAskedQuestions

ADTFieldsandFunctions

MyHISsystemusesADTfunctionA18asanAccountNumberMerge,isthis
compatiblewiththeMUSEsystem?

TheMUSEsystemnormallymapstheA18transactiontoaPatientIDmerge.
Otherwise,theMUSEsystemcanbeconguredtoignoretheA18transaction,orifthe
necessarydataispresentinthemessage,changethemessagetoamessagetype
thattheMUSEsystemsupportssuchasanA35.HealthLevelSevenVersion2.2and
laterdenenewmergetransactionsthatarealsosupportedbytheinterfacethatmay
applytothisfunctionality.AllmergetransactionsontheMUSEsystemrequirethe
PatientIDataminimum.

8

MyHISsystemusespatientnameslargerthantheMUSEsystemaccepts.The
originalHISnamemustbereturnedinresultandbillingmessages.Willthiswork?

TheMUSEsystemsupports40characterlastnamesand20characterrstnames.
Thesystemwilltruncatelongernames.

Attimes,weadmitpatientsunderanaliasthatwewanttosendtotheMUSE
system.Howdoesthiswork?

TheMUSEinterfaceandMUSEsystemsdonotsupportapatientalias.

TheADTtransactionsA20(patientbedstatusupdate),A21(patientgoesona
leaveofabsence),andA22(patientreturnsfromleaveofabsence)arenotlisted,
doestheMUSEinterfacesupportthem?

No.ThefunctionssupportedbytheMUSEsystemarelistedinthismanual.Ifsent,A20,
A21,andA22transactionswillerroroutintheHL7interfaceengine.Thesetransaction
typesshouldbelteredontheHISside.

ThePR1,GT1,IN1,ACC,andUB1segmentsarenotlisted.DoestheMUSEinterface
supportthem?

No.ThesegmentssupportedbytheMUSEsystemarelistedinthismanual.Depending
upontheparticulardatasentinthePR1,GT1,IN1,ACC,orUB1segments,theMUSE
systemmaybeoptionallyconguredtostorethedata.Thismustbedeterminedona
casebycasebasis.ThedatamaynotbeviewablebytheMUSEsystemusers.The
datamaynotbeavailabletoreturninresultornancialmessages.Also,seenextFAQ.

2059568-021B

MUSE™v9CardiologyInformation

System

85

HL7ImplementationFAQs

OursystemusesaspecialZsegment(Z02,ZPV,etc.).IsthisacceptedbytheMUSE
system?

Possibly.Ingeneral,theMUSEsystemignoressegmentsnotlistedinthismanual.
However,theMUSEsysteminterfacemaybeoptionallyconguredtomapdataelds
fromanysegmentintheHL7messagetocorrespondingeldsintheMUSEdatabases.
IfthespecialZsegmentcontainsdatathatcanbestoredontheMUSEsystem,itcan
beused.Forexample,HL7doesnotspecifypatientheightandweightinthestandard
segments,butitcanbesentinaspecialZsegment.IftheMUSEsystemiscongured
torecognizetheZsegmentaspatientheightandweight,thedatawillbeaccepted.
FieldsmappedlikethismaynotbeviewableontheMUSEsystemand/ormaynotbe
availabletobereturnedinresultornancialmessages.

Oursystemusessystemidandepisodeidentiersthatarerequiredinresults.
Canyoustorethisinformation?

No.TheMUSEinterfacedoesnotstorethesystemidandepisode.

DoestheMUSEsystemupdateorderinformationinthestudiesontheMUSEserver?

AnADTinterfacewillupdateADTinformationontheMUSEsystem;anorderinterface
willupdateorderinformationontheMUSEsystem.Orderinformationisupdatedona
studyonlyuntilthestudyissettoDemographicsCompletestatusorhigher.

OrdersFieldsandFunctions

OurordermessagesmaycontainmultipleOBRsegments.CantheMUSEsystem
acceptit?

No.TheMUSEsystemonlyprocessesoneprocedureperpatientpermessage,i.e.one
OBRsegmentperordermessagewithquantity1(one).

Weorderrecurringstudies,1everydayfor5daysatasettimeor1everyhour
for5hours.HowdoestheMUSEsystemhandlethis?

TheMUSEsystemonlyprocessesoneprocedureperpatientpermessage,i.e.oneOBR
segmentperordermessagewithquantity1(one).Forthisexample,theHISsystem
wouldgenerate5individualordermessagesforasinglestudywiththerequested
dateandtimeforeachstudy.

ThePV1segmentislistedasoptional.Whatdoesthatmean?

TheMUSEsystemusesinformationinthePV1segmenttoupdateADTandvisit
databaseinformation.WhentheHISsystemissendingordermessagesonly,more
informationcanbegatheredifthePV1segmentissentwiththeordermessage.For
HISsystemssendingbothADTandordermessages,thePV1segmentintheorder
messagemaybeusedtoupdateADTandvisitinformationifconguredtodoso.

Ourordersystemusesa25-digitplacerordernumber.CantheMUSEsystem
acceptthat?

No.TheMUSEsystemacceptamaximumof22charactersfortheplaceordernumber.

NOTE:

Someancillarydevicesacceptonly9characterordernumbers.

Ourordersystemusesordernumberandoccurrencenumbertoidentifypatient
studies.DoestheMUSEsystemstorethisinformation?

TheMUSEsystemrequiresaplaceordernumberwhichisakeytotheorderdatabase
(maximumof22characters).

86

MUSE™v9CardiologyInformation

System

2059568-021B

HL7ImplementationFAQs

CanyoucreateordernumbersforstudysontheMUSEsystem?

No.TheMUSEsystemisconsideredalleroforders,notaplacer.

DoestheMUSEorderinterfaceusecontrolcodesNA,SN,OC,SSforprocessing
orders?

No.TheonlyordercontrolcodesapplicabletotheMUSEsystemareNW(neworder),
CA(cancelorder),OD(DeleteOrder),andXO(updateorder).

CantheMUSEorderinterfaceassignordernumberstoorderrequestsorcreate
requestsfororders?

No.TheMUSEsystemisconsideredallerofordersnotaplacer.

DoestheMUSEsystemsendcancelordermessagestotheHIS?

No.TheMUSEsystemdependsontheHISordersystemtocreate,cancel,and
changeorders.TheMUSEsystemcanbeconguredtoallowuserstocancelorders
locallyontheMUSEsystem,butthisdoesnotaffecttheHISordersystemandisnot
communicatedtotheHISsystem.Ingeneral,ordersshouldbecanceledontheHIS
ordersystem,notontheMUSEsystem.

CantheMUSEsystemuserseditorders?

No.OrderinformationisonlychangedbytheupdatesfromtheHISordersystem.

ResultandFinancialMessagesFieldsandFunctions

DoesthePhysicianIDontheMUSEsystemmatchtheHISID?

GenerallytheMUSEIDandtheHISIDforphysiciansarenotthesame,howevertheHIS
IDcanbemapped,or"matched,"toaMUSEuserinMUSEUsersetup.Thephysicians
ontheMUSEsystemaregivenaUserIDanywhereintherangefrom1–65,535.Not
allphysiciansintheHISsystemhaveUserIDsontheMUSEsystem.

WerequiretheHospitalIDforphysicians(overreader,referring,ordering),
transcriptionists,etc.DoestheMUSEsystemusetheHospitalID?

TheMUSEsystemusestheMedicareIDeldintheuserlisttostoreHospitalIDor
mnemonicsthatareneededforresultandnancialmessages.Thiselddatais
enteredandmaintainedbythecustomer.TheHISsystemcanmaintainalookuptable
thatcorrelatestheMUSEInformationSystemUserIDandtheHospitalID.

OurADTandOrdermessagesincludethephysician’shospitalID.Wewantthis
informationreturnedintheresults/nancialmessages.

ThePhysicianIDinformationsentintheADTand/orordermessagesisstoredin
thedatabaseHISIDeldupto32characters.WhenADTandorderinformation
ismatchedtoastudy,physicianinformationisstoredwiththestudyandcanbe
returnedinaresultsornancialmessage.

Theonlyallowablestatusvaluesforourresultsarependinganddraft.

TheMUSEinterfacehasfourstandardreportstatuses,twounconrmedstatuses:
PreliminaryandDemographicsCompleteandtwoconrmedstatuses:Finaland
Corrected/RevisedFinal.TheinterfacecanmaptheMUSEreportstatussentinthe
HL7messagetocustomerspecications.

Canyousendthetransactiondollaramountinthenancialmessage?

TheMUSEinterfacedoesnotsupporttransactiondollaramounts.

2059568-021B

MUSE™v9CardiologyInformation

System

87

HL7ImplementationFAQs

HowdoestheMUSEsystemdocredits?

TheMUSEinterfacedoesnotsendcreditmessages

Whataretheoptionsforinterfacingwaveformimagedata?

WaveformimagedatacanbesentfromtheMUSEsystemtotheHISinanHL7
message.TheimagecanbesentasPDF,TIFF,PostScript,PCL,andWindowsMetale.
TheimageintheHL7messagewilleitherbeUUencodedorBase64encodedandthe
HISsystemwilldecodeanddisplaythegraphics.

DoIneedaFinancialInterfaceandaResultInterface?

TheMUSEHL7interfaceoptionforsendingHL7nancialtransactionscanbe
purchased.Thesearesentinrealtimeorinbatches.SomeHISsystemsmaybeable
togeneratechargesbasedontheresulttransactions,andwouldthereforenotrequire
theseparatenancialoption.

HowandwhenwillIreceiveduplicatenancialmessages?

Therearethreestudystatesthatcantriggerachargemessage,NewlyAcquired,
DemographicsComplete,andConrmed.Ifconguredtodoso,andastudyissetto
oneofthesestates,achargemessageistriggeredandabillingmessageisformatted
andsenttotheHIS.Whenthebillingmessageisproperlyformatted,abitagissetto
indicatethatanancialmessagehasbeensentforthatteststatus.Notethatthereis
aseparatebillingbitforeachofthebillingtriggers(NewlyAcquired,Demographics
Complete,andConrmed).

Ifaftertherstoccurrenceofabillingtriggerastudyisagainsettothesamestate,
thesystemwillblockasecondnancialmessagefrombeingsentforthatstate.
However,iftheuserhas"re-bill"privileges,theuserwillreceiveapromptandcanthen
electtoeithersuppressthechargemessageorallowasecondchargemessageto
begenerated.

NOTE:

YoucanaddcolumnstotheEditListandRetrievalPanetoidentifywhether
chargeshavebeengeneratedforaparticularstate.Youcanalsondthis
informationthroughadatabasesearch.

CommunicationProtocolOptions

Ourcommunication’sprotocoldoesnotfollowtheHL7standard;itusesasingle
characteracknowledgment.CantheMUSEsystembeconguredtoacceptthis?

TheMUSEsupportsstandardHL7originalmodeacknowledgmentmessages,nota
singlecharacterorACK/NACKacknowledgment.

WeusetheHL7standardacknowledgments.DoesMUSEsupportsequence
protocol?

No.

OursystemusesTCP/IP .Whenoursidegoesdown,wesendashutdownmessage
toourinterfacesandwantashutdownmessagesentwhentheMUSEsidegoes
down.

TheMUSEsystemdoesnotsendshutdownmessages,andtheywillbeignored.The
MUSEsystemfunctionsproperlywithoutshutdownmessages.TheMUSEinbound
interfaceforADTandordersstartsandopensalisteningportandwaitsfora
connectionfromtheHIS.WhentheconnectionfromtheHISisreleased,theMUSE

88

MUSE™v9CardiologyInformation

System

2059568-021B

HL7ImplementationFAQs

inboundsidereleasestheconnectionandreopensthelisteningportandwaitsfora
connectiontothehost.TheMUSEoutboundinterfaceonlymakesaconnectiontothe
HISwhenmessagesareavailabletosend.Iftheconnectionisnotaccepted,theMUSE
systemmaintainsthemessagesasitcontinuestotrytheconnection.

Whoistheclientandwhoistheserver?

TheMUSEsystemwillbetheserverforADTandordertransactions(includingthe
patientdemographicsquery).TheMUSEsystemwillbetheclientforresultand
nancialtransactions.Thisfollows“thesendingapplicationistheclient”rule.

2059568-021B

MUSE™v9CardiologyInformation

System

89

HL7ImplementationFAQs

90

MUSE™v9CardiologyInformation

System

2059568-021B

HL7InterfaceTesting

Introduction

TheinformationinthisdocumentisdesignedtobeaguideorstartingpointforGE
Healthcarecustomerstouseastheydeveloptheirtestplans.Thecustomerneeds
toreviewandrevisethetestinginformationcontainedinthereference-onlytest
plansandcustomizethemtomeettheirsite’sspecicworkowanddataexchange
requirements.

Thecustomerisultimatelyresponsibleforensuringtheinterfacesfromtheir
informationsystemstotheMUSEsystemandfromtheMUSEsystemtotheir
informationsystemsupdatethesendingandreceivingsystemasexpectedtosupport
thecardiologydepartmentandhospitalworkow.

Inmanycases,thecustomer’sinformationsystemdepartmentwillhaveestablished
testingplanmaterialsinplacetousefordatavalidationandintegratedtesting.Inthat
case,theycanchoosenottousethetestexampleincludedinthisdocument.

9

TheimplementationofeachpurchasedHL7interfacewillvaryfromcustomerto
customerdependingonthesite’scardiologyandotherdepartments’workow.

TestGoals

Tocompletelyexerciseyoursysteminthetestenvironment,youshouldtestall
oftheinterfaceoptionsandfeaturespurchasedforyourinstitution,suchasADT
(Admit/Discharge/Transfer),Orders,Results,andFinancials.

Inaddition,youshouldtestyoursystemundertwodifferentconditions:single
transaction(functionalorunit)testsandmultipletransaction(endtoendorintegrated)
tests.

TypeofTesting

UnitTests

IntegratedTestsIntegratedtestinginvolvesthesimulationof

2059568-021B

MUSE™v9CardiologyInformation

System

Description

Functionalorunittestinginvolvesinitiation
ofindividualtransactionsandfollowingthem
throughthetestenvironmenttoensurethat
alldataeldsontheMUSEapplicationare
updatedproperly.

theproductionworkow.

91

HL7InterfaceTesting

CustomerPrerequisitesforInterfaceTesting

Thecustomermustperformthefollowingstepstoconrmthatalltheprerequisitesfor
testingtheHL7interfacearecomplete.

1.ObtainacopyofthedocumentMUSEv9CardiologyInformationSystemHL7
ReferencefromyourGEHealthcareHL7engineerorGEHealthcareproject
manager.

Reviewthemanual.

2.Verifyyourtestenvironmentmirrorstheproductionenvironment.

NOTE:

ToensurethattheUnitandIntegratedTestingoutcomesmirrorthe
outcomesthatwilloccurintheProductionenvironment,theCustomer
needstoensurethattheTESTHIS(HospitalInformationSystem),EMR,and
interfaceengineenvironmentsaresetuptomirrortheproductionHIS,EMR,
andinterfaceengineenvironments.

3.ParticipateintheHL7specicationreviewwiththeGEHealthcareHL7engineer.
CustomersthatareupgradingfromapriorMUSEreleasetoaMUSEv9system

arenotrequiredtohaveanin-depthspecicationreview,unlessnewinterfaces
arebeingimplementedaspartofthev9upgrade.ExistinginterfacesonaMUSE
installationwillbeconguredtomatchthepriorinterfaceformatsasclosely
aspossible.TheMUSEv9systemmayrequiresomechangestotheinboundor
outboundHL7messagesthatwereusedinthepriorreleases.

CustomerswhoarenewtotheMUSEsystemorwhowillbeimplementingnew
HL7interfaceswillberequiredtohaveanin-depthspecicationreviewwith
theirGEHealthcareHL7engineer.

4.Verifytheconnectivityandmessagevalidation.
CustomersneedtoverifythatallHL7transactionsbetweentheMUSEsystem

andthesite’sHIS/EMRsystemsaresuccessfullytransmittedandprocessed.
Initialinterfaceconnectivityandhighlevelmessagevalidationwillbecompleted

priortoformalunittesting.Thesetasksaretobecompletedbythecustomer’s
HL7orclinicalanalystandtheGEHealthcareHL7engineer.

5.Identifyandscheduleresourcesforinterfacetesting.
Customerresourcesthataretypicallyinvolvedwiththetestingareincludedin

thelistbelow.Beawarethattheresourcesrequiredfortheunitandintegrated
testingwillvaryfromcustomertocustomerbasedoninterfacespurchased,
numberofsitesdenedintheMUSEsystem,numberofinboundHISand
outboundEMR,andbillingsystemssendingorreceivingdata.

•HL7engineer/interfaceanalyst

•ITclinicalanalyst

•ITnetworkengineer

•ITregistrationanalyst

•ITEMRanalyst

•IThospitalbillinganalyst

•ITtechnicalbillinganalyst

92

MUSE™v9CardiologyInformation

System

2059568-021B

•Biomedicaltechnician

•Patientregistrationstaff

•Healthinformationmanagementstaff

•Nursingandclinicalstaff

•EKGtechnicians

•MUSEsystemadministrator

TestProcedures

Thefollowingisareference-onlytestplan.ItisimportanttotestallaspectsofyourHL7
interfacesoftware.Besuretocreateexamplesforeachtransactionandeventtype,
andprovidedatathatwilltestalloftheoptionsandfeaturesyouhavepurchased.

TheinterfacetestsshouldbeperformedforeachsiteconguredontheMUSEsystem.

TestSequence

HL7InterfaceTesting

TheMUSEHL7Interfaceconsistsofsevenstandardcomponentinterfaces:

•ADT(Admit/Discharge/Transfer)

•ADTquery

•Order

•Result

•Resultbatch

•Financial

•Financialbatch

Eachcomponentisapurchasableoption.Thecompleteinterfacemayincludeoneor
anycombinationofthesecomponents.However,anADTinterfaceisrequiredwith
anOrderinterfaces.WealsohighlyrecommendthatanOrderinterfacebeincluded
witheachFinancialinterface.

Whilethisvariesfromcustomertocustomerdependingontheinterfacecomponent
optionspurchased,therecommendedsequencefortestproceduresisasfollows:

•TestallADTtransactionsthatwillbesupportedforeachsite.

•TestADTQueryforeachsite.

•TestallOrdertransactionsthatwillbesupportedforeachsite.

•TestallResulttransactionsthatwillbesupportedforeachsite.

•TestResultBatchprocessingforeachsite.

•TestallFinancialtransactionsthatwillbesupportedforeachsite.

•TestFinancialBatchtransactionsforeachsite.

•Testtheabilityofthesystemtosuccessfullyrecoverfromanyshutdownthatmay

occurduringtransactionprocessing.

2059568-021B

MUSE™v9CardiologyInformation

System

93

HL7InterfaceTesting

TestTemplates

Sampletemplatesareprovidedforthemajortransactiontypes:

•AppendixD“ADTTestPlanTemplates”onpage139

•AppendixE“OrderTestPlanTemplates”onpage167

•AppendixF“ResultsTestPlanTemplates”onpage183

•AppendixG“ResultsandFinancialsTestPlanTemplates”onpage245

TestingADTInterfaceTransactions

TheGEMUSEHL7ADTinterfaceacceptsunsolicitedmessagesforADTtransactions
fromtheHIS(HospitalInformationSystem).Thesemessagesmustincludedatafor
onlyonepatient.

NOTE:

TheMUSEv9HL7ADTinterfacedoesnotsupportbatchprocessingofADT
transactionmessages.

ForthoroughADTinterfacetesting,patientadmission,discharge,andtransferevents
enteredintheHIStriggeracorrespondingHL7ADTmessageandevent.Themessage
andeventtypesentintheHL7transactionindicateswhattypeofworkowevent
tookplaceforthepatient.

ToensurethattheMUSEv9databaseisupdatedasexpectedbytheADTmessages
sentfromyourHIS,eachHL7eventtypethatyouwillbesendingtoMUSEneeds
tobetested.

TovalidatethatanHL7eventtypeupdatestheMUSEdatabaseasexpected,perform
theactionthattriggerstheeventonyourHIS(forexample,totriggeranA01event,
AdmitanInpatienttoyourhospitaltestsystem;totriggeranA02event,Transferan
existingInpatienttoadifferentroom/bedonyourhospitalsystem;etc.),thencompare
theADTdataeldsenteredforthepatientonyourHISwiththedataeldspopulated
ontheAdmitandVisitinformationscreensintheMUSEsystem.

TosimplifytestingandvericationoftheADTtransactionprocessing,weseparate
thetestsintofourgroups:

•Transactionsthataddpatientdata

•Transactionsthatchangepatientdata

•Transactionsthatmergepatientdata

•Transactionsthatdeletepatientdata

94

MUSE™v9CardiologyInformation

System

2059568-021B

TestingTransactionsthatAddPatientDate

Thetransactionsthataddpatientdataaredescribedinthefollowingtable:

ADTTransactionsthatAddPatientData

HL7InterfaceTesting

HL7EventType

A01

A04

A05

A10

A13

TransactionDescriptionAction

AdmitpatientAnewrecordisaddedtothe

MUSEdatabase.

Registerapatient

Pre-admitapatientAnewrecordisaddedtothe

Patientarriving

CanceldischargeAdeletedrecordisreinstated

Anewrecordisaddedtothe
MUSEdatabase.

MUSEdatabase.
Anewrecordisaddedtothe

MUSEdatabase.

intheMUSEdatabase.

Thesetransactionsprimarilyaffectpatientidenticationdataandcanbeveriedon
theMUSEv9systembyviewingtheMUSEAdmittingInformationandVisitInformation
screens.

NOTE:

OnlyHL7eventtypesthatwillbesenttotheMUSEsystemfromtheHIS(Hospital
InformationSystem)needtobetested.

UsethefollowingstepstotesttheADTtransactionsthataddpatientdata:

1.OnyourtestHIS,beginbyadmittinganewpatient.
ThisactiontriggersanA01(AdmitPatient)transactiontobesenttotheMUSE

system.

2.LogontothetestMUSEsystemtoverifythatthenewlyadmittedpatientisin
theMUSEsystem.

Followthefollowinginstructionstoviewpatientadmittingandvisitinformation
in“HowtoViewPatientAdmittingandVisitInformationontheMUSEv9System”

onpage102.

3.VerifythattheinformationdisplayedontheMUSEAdmittingandVisit
InformationscreenmatchestheinformationenteredonyourHIS.

Itishighlyrecommendedtodoaeld-by-eldcomparisonbetweenthedata
valuedontheMUSEscreensandthedatavaluedonyourHIS.

4.RecordanyeldthatisnotvaluedontheMUSEsystem,butwasvaluedon
yourHIS.

Forexample.iftheReferringDoctoreldwasvaluedonyourHISbutnotonthe
MUSEsystem,youneedtoinvestigatetodeterminewhytheeldwasnotvalued.

2059568-021B

MUSE™v9CardiologyInformation

System

95

HL7InterfaceTesting

5.RecordanyeldthatcontainsavalueontheMUSEsystemthatdoesnotmatch
thevalueinyourHIS.

Forexample,ifthepatient’sRaceeldonyourHISsystemwasenteredas
“Hispanic,”buttheracelistedontheMUSEsystemis“Black,”youneedto
investigatetodeterminewhytheeldwasvaluedincorrectly.

NOTE:

VericationofthePatientIDeld,asitisvaluedintheMUSEsystem,is
critical.Mostcustomersvaluethepatient’smedicalrecordnumberin
thePatientIDeld.ThePatientIDeldontheMUSEsystemisusedto
uniquelyidentifythepatient.Thelengthandformatonthiseldmust
remainconsistenttoensureuniqueidenticationofthepatient.During
HL7specicationreview,youneedtodeterminethelengthandformatof
thePatientIDeld.

6.AfterverifyingthatallofthedataeldsfortheAdmittransactionhasupdated
theMUSEsystemcorrectly,sendanothertransactionthataddspatientdata
andrepeatstep2.

7.Continuetestinguntilallthetransactionsthataddpatientdataforeachsite
denedontheMUSEsystemhavebeentestedandveried.

TestingTransactionsthatChangePatientData

Thetransactionsthatchangepatientdataaredescribedinthefollowingtable:

ADTTransactionsthatChangePatientData

HL7EventType

A02

A06

A07

A08

A03

A09

TransactionDescriptionAction

TransferapatientThepatientrecordischanged

Transferoutpatientto
inpatient

Transferinpatientto
outpatient

UpdatepatientinformationThepatientrecordis

DischargeapatientPatientrecord(account)

PatientdepartingPatientrecord(account)

toreectthenewlocation
information.

Thepatientrecordischanged
toreectthenewpatient
classication.

Thepatientrecordischanged
toreectthenewpatient
classication.

changedtoreectthe
newinformation.

statuschangesfromopento
closed.

statuschangesfromopento
closed.

96

MUSE™v9CardiologyInformation

System

2059568-021B

ADTTransactionsthatChangePatientData(cont'd.)

HL7InterfaceTesting

HL7EventType

A12

A17

TransactionDescriptionAction

CanceltransferApatienttransferiscanceled.

Thepatientrecordischanged
toshowthelocationpriorto
thetransfer.

Swappatients

Usedwhentwopatientswill
exchangebeds.Bothpatient
recordsarechangedto
reectthelocationchanges.

NOTE:

OnlyHL7eventtypesthatwillbesenttotheMUSEsystemfromtheHISneed
tobetested.

Usethesestepstotesttransactionsthatchangepatientdata:

1.OnyourtestHIS,beginbyadmittinganewpatient.
ThisactiontriggersanA01(AdmitPatient)transactiontobesenttotheMUSE

system.

2.LogontothetestMUSEsystemtoverifythatthenewlyadmittedpatientisin
theMUSEsystem.

Followthefollowinginstructionstoviewpatientadmittingandvisitinformation
in“HowtoViewPatientAdmittingandVisitInformationontheMUSEv9System”

onpage102.

3.OnyourtestHIS,selectthepatientadmittedinstep1andtransferthepatient
toanotherNursingUnitRoom/Bed.

4.Verifythatthepatientlocationroom/beddisplayedontheMUSEVisit
Informationscreenmatchesthenewpatientlocationroomorbedinformation
enteredonyourHIS,

5.AfterverifyingthatthepatientlocationonMUSEwasupdatedbytheTransfer
transaction,sendanothertransactionthatchangespatientdataandverifythat
anydatachangedontheHISisupdatedorchangedontheMUSEAdmitting
andVisitInformationscreens.

6.Continuetestinguntilallofthetransactionsthatchangepatientdataforeach
sitedeneonMUSEhavebeentestedandveried.

TestingTransactionsthatMergePatientData

NOTE:

Itishighlyrecommendedthatthecustomer’sHealthInformationManagement,
IntegrationTeam,andCardiologyDepartmentstaffreviewthesiteconguration
optionsforthedepthofthemergeimplementationwiththeGEHealthcareHL7
engineer.

TheMUSEsystemhastheabilitytobeconguredtoallowpatientstudydemographics
andvisit/accountinformationstoredontheMUSEtobeautomaticallysynchronized
withtheHISsystemwhenspecicHL7messagesarereceived.Thisdata

2059568-021B

MUSE™v9CardiologyInformation

System

97

HL7InterfaceTesting

synchronizationmaybeconguredtooperateonbothconrmedandunconrmed
studydataaswellastheMUSEsitelevelpatientdemographicsdatastore.

Thefollowingsitelevelsettingsareavailabletocontrolthebehaviorofthedepth
ofthemerge:

SiteLevelMergeSettings

MergeLevelSettingDescriptionofDepthofMerge

UpdateMasterMUSEPatientListAlldepthofmergeHL7messageswillupdate

theMUSEsiteleveldemographicsdata.

NOTE:

Duetohightrafcofupdatemessages,
itisnotrecommendedtoenablethis
option.

UpdateUnconrmedTestsAlldepthofmergeHL7messageswillupdate

unconrmedpatienttests.

UpdateConrmedTestsforMerge
TransactionsOnly

UpdateFullPatientDemographics
InformationfromMergeTransactions

MergespecicHL7messagewillupdate
conrmedpatienttests.

Updateallelds.
Ifnotselected,onlyPatientID,LastName,

FirstName,andDateofBirtheldsare
updated.

Merge-specicHL7messagesarethosethatchangepatientID,visitand/oraccount
identierstothecorrectvalues.Currently,thesearetheonlytypeofmessagesthat
targetconrmedpatienttestdata.TheHL7mergeeventtype,alongwiththeMUSE
DepthofMergeSiteconguration,determineswhattablesareupdatedintheMUSE
systemwhenthemessageisreceived.

Thefollowingtabledescribesthetransactionsthatmergepatientdata:

ADTTransactionsthatMergePatientData

HL7EventType

A18

TransactionDescriptionAction

MergepatientID

Visitsandordersassociated
withonePID(Non-surviving
PID)aremovedtoadifferent
PID(SurvivingPID.).The
non-survivingPIDisdeleted.

NOTE:

A18functionalityis
reservedforbackwards
compatibility.UseA34
instead.

A34

MergepatientID

Visitsandordersassociated
withonePID(Non-surviving
PID)aremovedtoadifferent
PID(SurvivingPID).The
non-survivingPIDisdeleted.

(SameasA18.)

98

MUSE™v9CardiologyInformation

System

2059568-021B

ADTTransactionsthatMergePatientData(cont'd.)

HL7InterfaceTesting

HL7EventType

A35Mergeaccount

A36

A42

A46

TransactionDescriptionAction

Updatesaccountnumber
withnewaccountnumber.If
anon-survivingaccount
numberexistsfora
specicvisitnumber,the
non-survivingaccount
numberischangedtothe
survivingaccountnumber.

MergepatientIDandaccountMovesaspecicvisit

associatedwiththe
non-survivingPIDtothe
survivingPID.patientIDand
accountnumberareupdated
withthenewpatientIDand
accountnumber.

Mergevisit

Thevisitnumberandall
associatedordersaremoved
tothenewvisitnumber .
Allordersassociatedwith
thenon-survivingvisit
numberaremovedtothe
survivingvisitnumberand
thenon-survivingvisit
numberisdeleted.

Mergevisit

Thevisitnumberandall
associatedordersaremoved
tothenewvisitnumber .
Allordersassociatedwith
thenon-survivingvisit
numberaremovedtothe
survivingvisitnumberand
thenon-survivingvisit
numberisdeleted.

ThefollowingtabledescribesthebehavioroftheHL7Mergetransactionsandthe
MUSESiteDepthofMergeconguration.

2059568-021B

MUSE™v9CardiologyInformation

System

99

HL7InterfaceTesting

TransactionMUSEPatients

MergePatientID
(A18,A34)

MoveallVisits
associatedwiththe
non-survivingPIDto
thesurvivingPIDand
thendeletingthe
NonsurvivingPID

MergePatientIDand
Account(36)

Moveaspecicvisit
associatedwiththe
NonsurvivingPatient
IDtotheSurviving
PatientID

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallpatient
leveldemographics
elds.

NoChange:

Otherthanstandard
synchronization
ofchanging
demographicson
tests.

TestUnconrmedTestConrmed

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallelds.

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallelds.

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallpatient
leveldemographics.

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallpatient
leveldemographics.

MergeVisits(A42,
A46)

Moveallorders
associatedwith
Nonsurviving
VisitNumberto
theSurvivingVisit
Numberanddelete
theNonsurviving
VisitNumber

MergeAccounts
(A35)

ChangesAccount
Number

NoChange:

Otherthanstandard
synchronization
ofchanging
demographicson
tests.

NoChange:

Otherthanstandard
synchronization
ofchanging
demographicson
tests.

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallelds.

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallelds.

NOTE:

OnlyHL7eventtypesthatwillbesenttoMUSEfromtheHISneedtobetested.

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallpatient
leveldemographics.

Ifcongured:

Updatesrecordwith
non-survivingPID
tosurvivingPIDand
updatestheName
andDateofBirth
elds.

Ifconguredforfull
merge:

Updatesallpatient
leveldemographics.

UsethefollowingstepstotesttheADTtransactionsthatmergepatientdata:

1.OnyourtestHIS,beginbyadmittingtwo(2)newpatients.
Thepatientsshouldbethesamesexandhavethesamebirthdate.

100

MUSE™v9CardiologyInformation

System

2059568-021B