1 / 24

Diatelic - An Intelligent TeleSurveillance System for Peritoneal Dialysis

Diatelic - An Intelligent TeleSurveillance System for Peritoneal Dialysis. Laurent Romary Minit Gupta. Loria Labs, Nancy. Context. A Tele Medicine System Need for flexibility Use of XML Perspectives. Quelle télémédecine?. Différentes perspectives Télé-opération

cheng
Download Presentation

Diatelic - An Intelligent TeleSurveillance System for Peritoneal Dialysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. 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

  4. 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

  5. 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é

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

  7. 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

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

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

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

  11. The XML Based Architecture

  12. 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

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

  14. Dynamic Generation of the Interface It is a three phase process Phase I: parsing the medComps 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

  15. <template name=”HelpTemplate”>  <structure> <part class="JFrame" name="BPHelpFrame"> <style>...</style> <part class="JPanel" name="BPHelpMainPanel"> <style>...</style> <part class="JTextArea“ name="BPHelpTextArea"> <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: systemParam. Type: medical Class: clinical For value with id= 00215062000112dias the lower bound is 5. Type: medical Class: clinical</property> </style> </part> ... </structure>   <behavior> <rule> <condition> <event class="actionPerformed" part-name="BPHelpCloseButton" /> </condition> <action> <property name="visible" part-name="BPHelpFrame"> false</property> </action> </rule> </behavior> </template>

  16. 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

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

More Related