towards interoperability for telemedicine systems

8/3/2019 Towards Interoperability for Telemedicine Systems

1/20

Towardsinteroperability

for

ElectricalandComputerEngineeringDepartment,UniversityofPatras

WirelessMobileCommunicationand

MobiHealth 2010


2/20

IntegratedeHealthenvironment

differentMedical

Information

Systems(MIS)andapplicationsact

Telemedicineapplicationsarenot

autonomous,cooperationwith

RIS,LIS,

HIS,

PACS,

etc

should

be

supported


3/20

con .

Interoperability:the

ability

of

different

unctiona entitiesto:

Exchangeinformation(functional)

Gap:alotofdifferentstandardsexistwithvarious

Exchagecomprehensibleinformation(semantic)


4/20

Conditionsof

environment Design

considerations

e eme c nesys emsare o a y

distributed

unc ona yo propose sys em s

sharedbetweenthesitesthatparticipate

incommunication

Different

types of

networks

are

utilized Messages of

special

structure

are

used

thatareadoptabletotheappliednetwork

protocol

Transferthedatathe fastestpossible Addedinformationtothemessagesis

properlyaccessedandmodified

communicatewithotherMISs withina

healthcareenterprise

theproposedsystemusingdedicated

interfaces


5/20

Modellin intero erabilit serviceFunctional

aspect

Users:applicationsanddatastores

'

profiles

Arc itecture

consists

o

an

intermediatetransfersystem(TS)and

dedicatedinterfacingentities

managementdomain


6/20


aspect

(cont.)

Theendtoendcommunicationis

or anizedb

interoperability

service

(intservice)

exchangedusingaspecialstructure

a scommon ora users


7/20


aspect

(cont.)


8/20

Modellinginteroperabilityserviceint

service

design

It

is

considered

that:1) Duringanysession,theintserviceutilizesthe

functionalentitiesofintermediatesysteminorder

toestablish

the

appropriate

communication

path

betweenusers(originatorandrecipient)


9/20


service

design

It

is

considered

that:2) Theoperationoftheintserviceisaccomplished

throughsubmission,transfer anddelivery

interactions.An

interaction

is

considered

as

the

meansbywhichtheHTmessagesaretransferred

etweenusers omainsan TS


10/20


service

design

It

is

considered

that:3) Thecreationofthecommunicationpathsandthe

performanceofallinteractionsareachieved

throughthe

use

of

acomplete

set

of

service

elements


11/20


service

design

Originator Interfacingentities

TS Interfacingentities

Recipient

Submission Transfer Delivery


12/20

Modellin intero erabilit serviceint

service

design

MessageTransferringserviceelements(10):

message

transferringof

the

messages,

addressing,identificationandconversion

MessageStoringserviceelements(4):

transmissionand

receipt

conditions

of

messagesfrom/tomessagestoringentities

ResourceVerificationserviceelements(2):

verificationand

maintenance

of

the

connectionbetweenuserinterfacing

entitiesandTS


13/20

ImplementingthesystemArchitecture


14/20

Im lementin thes stemSpecial

mechanisms

modules

Translation

sers

profiles

Messagecoding

standardsrules


15/20


mechanisms

modules

Errorhandlingincludes:

a) Supervisionof

the

sessions

performance(envelopepart)

b Check s stem resources

c) Administrationof

queues

in

message

d) Useoffiltersfor:routing,feedback

an

emporarys orage

o

messages


16/20


mechanisms

modules

Auditing:

a) Continuousfunction

b) Logfileswith:

.

ii. Sendingdetails

(start

and

end

of

messages

transfer thesuccessorfailurenotifications

theresendingproceduresdetails,filtering

results

and

the

identification

data

of

message/session)

iii. Receivingdetails(startandterminationtime

po n s, er ngresu s, ypeso no ca ons

andidentification

data

of

message/session)


17/20

Functionality

is

provided

by

autnomous

execu a emo u es

UsersCatalogue,MetadataStore:relational

databases ,

HL7messaging:NeoToolLibrary

Databases:Oracle10gRDBMS,ADO,SQLDML

DICOMservices:CTNo ensourcesoftware

(WashingtonUniversity

of

Saint

Louis).


18/20

The

system

was

tested

using

LIS

and

PACS Auditingmechanismwasused

estimated:

Funactiona ity

Reliability 99,2

99,7

%

Efficiency

Howdifficultistoad ust

Portabilitythesystemundernewoperational

requirements?


19/20

Proposed

architecture

for

syntactic

interopera i itycontri utestot e

standardizationapproach

Noconstraint

to

the

applied

messaging

More

viable

solutions Betteradministration,maintenance,extension


20/20

towards interoperability for telemedicine systems

Documents