Diatelic An Intelligent Tele Surveillance System for Peritoneal

  • Slides: 24
Download presentation
Diatelic - An Intelligent Tele. Surveillance System for Peritoneal Dialysis Laurent Romary Minit Gupta

Diatelic - An Intelligent Tele. Surveillance System for Peritoneal Dialysis Laurent Romary Minit Gupta Loria Labs, Nancy

Context A Tele Medicine System Need for flexibility Use of XML Perspectives

Context A Tele Medicine System Need for flexibility Use of XML Perspectives

Quelle télémédecine? Différentes perspectives Télé-opération Transmission d ’informations : médecin-médecin Télémédecine « publique »

Quelle télémédecine? Différentes perspectives Télé-opération Transmission d ’informations : médecin-médecin Télémédecine « publique » : _ Rapprochement patient-médecin _ Matériel peu coûteux _ Utilisation simplifiée

Difficultés rencontrées en DP suivi épisodique du malade (mensuelle etc. ) fiche journalière de

Difficultés rencontrées en DP suivi épisodique du malade (mensuelle etc. ) fiche journalière de suivi pas d’exploitation de ces fiches en continu isolement du malade risques pathologiques importants => hospitalisations fréquentes

Objectifs de Diatélic moyens suivi médical en temps réel prévention des accidents finalité réduction

Objectifs de Diatélic moyens suivi médical en temps réel prévention des accidents finalité réduction de la morbidité amélioration du confort économies de santé

Follow Up Organisation patient Doctors RTC • fiches journalières • envoi et • réception

Follow Up Organisation patient Doctors RTC • fiches journalières • envoi et • réception de messages RTC/Internet base de données Expert System • alertes • suivi des malades • envoi et • réception de messages

Expérimentation en cours Validation technologique de Juillet 1998 à Mai 1999 après autorisation de

Expérimentation en cours Validation technologique de Juillet 1998 à Mai 1999 après autorisation de la CNIL Évaluation clinique depuis juin 1999 expérimentation randomisée auprès de 30 patients: _ _ 15 patients équipés de Diatélic 15 patients formant le groupe témoin

Diatelic: Extension to other pathologies like diabetes, heart diseases, … Interfacing with Data Acquisition

Diatelic: Extension to other pathologies like diabetes, heart diseases, … Interfacing with Data Acquisition Machines. Customization for each Patient. Dynamic Generation of the Interface.

Why UIML? XML based - homogenous view Easy updation Dynamic generation - daily monitoring

Why UIML? XML based - homogenous view Easy updation Dynamic generation - daily monitoring Swing renderer Ability to invoke methods at runtime - Potential Devices/Flexibility

New Follow up Organization Diabetes Doctors Peritoneal Dialysis RTC/Internet Application Heart Disease • Daily

New Follow up Organization Diabetes Doctors Peritoneal Dialysis RTC/Internet Application Heart Disease • Daily datas • Messages RTC Data base & Med. Comp Expert System • Alerts • Patient’s follow up • Messages

The XML Based Architecture

The XML Based Architecture

Medical Component Represents a single monitoring parameter, an entity, and defines its meta data.

Medical Component Represents a single monitoring parameter, an entity, and defines its meta data. It contains both medical and environmental information about the patient. The « peers » describes the method for the retrieval of the medical data. Blood Pressure is an example entity

<med. Comp id="00215062000112"> <name>Blood Pressure</name> <state>sitting</state>. . . <value id="00215062000112 sys" datatype="integer"> <descrip type="medical"

<med. Comp id="00215062000112"> <name>Blood Pressure</name> <state>sitting</state>. . . <value id="00215062000112 sys" datatype="integer"> <descrip type="medical" class="clinical">systolic</descrip> <bound type="max">23</bound> </value>. . . </med. Comp> <peers>. . . <retrieve idref="00215062000112 sys" type="bsn. Query"> <method> <name>bsn. Query</name> <param datatype="char" name="BP"/> <param datatype="char" name="Systolic"/> <return datatype="integer"/> </method> </retrieve>. . . </peers>

Dynamic Generation of the Interface It is a three phase process Phase I: parsing

Dynamic Generation of the Interface It is a three phase process Phase I: parsing the med. Comps file and initialising the local data structures Phase II: parsing the pre-written templates and filling in missing information Phase III: the templates are combined to form a valid UIML file and the Swing renderer invoked on it

<template name=”Help. Template”> <structure> <part class="JFrame" name="BPHelp. Frame"> <style>. . . </style> <part class="JPanel"

<template name=”Help. Template”> <structure> <part class="JFrame" name="BPHelp. Frame"> <style>. . . </style> <part class="JPanel" name="BPHelp. Main. Panel"> <style>. . . </style> <part class="JText. Area“ name="BPHelp. Text. Area"> <style>. . . <property name="text">this is the new BP Help. Entry type is mixed. Make of Machine is GAMBO. The scale for measuring used is mm of Hg. . Type: system. Param. Type: medical Class: clinical For value with id= 00215062000112 dias the lower bound is 5. Type: medical Class: clinical</property> </style> </part>. . . </structure> <behavior> <rule> <condition> <event class="action. Performed" part-name="BPHelp. Close. Button" /> </condition> <action> <property name="visible" part-name="BPHelp. Frame"> false</property> </action> </rule> </behavior> </template>

Conclusion Diatelic interface enhanced flexible, customizable separation of user interface and logic Non standard

Conclusion Diatelic interface enhanced flexible, customizable separation of user interface and logic Non standard templates - definition and parsing One to one mapping of the elements Marking the missing information The communication with the Data Acquisition Machine

Remarks Parsing the data entered Type definition and type checking Simple mathematical relations like

Remarks Parsing the data entered Type definition and type checking Simple mathematical relations like <, >, <> Programming language control structures ifthen-else, do-while Editing parts of the interface at run time Representation of graphics oriented interfaces and time based parameters.