1 / 14

Communicating the Logic of a Treatment Plan Formulated in Asbru to Domain Experts

Communicating the Logic of a Treatment Plan Formulated in Asbru to Domain Experts. WOLFGANG AiGNER, SILVIA MiKSCH {aigner, silvia}@asgaard.tuwien.ac.at. Overview. motivation challenges visual representation interaction, focus + context user centered design limitations conclusions.

cameo
Download Presentation

Communicating the Logic of a Treatment Plan Formulated in Asbru to Domain Experts

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. Communicating the Logic of a Treatment Plan Formulated in Asbru to Domain Experts • WOLFGANG AiGNER, SILVIA MiKSCH • {aigner, silvia}@asgaard.tuwien.ac.at

  2. Overview • motivation • challenges • visual representation • interaction, focus + context • user centered design • limitations • conclusions

  3. Road to Computerized Guidelines and Protocols Data Abstraction Guideline Execution Formal Methods Guideline Authoring Formal Guideline Representation

  4. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plan-library SYSTEM "asbru_7_3.dtd"> <plan-library> <domain-defs> <domain name="controlled_ventilation_domain"> ... </domain> </domain-defs> <plans> <plan-group> <plan name="ventilation_plan"> <intentions> ... </intentions> <conditions> <complete-condition> <constraint-combination type="and"> <parameter-proposition parameter-name="FiO2"> <value-description type="less-or-equal"> <numerical-constant value="40"/> </value-description> ... </constraint-combination> </complete-condition> <abort-condition> <constraint-combination type="or"> <parameter-proposition parameter-name="FiO2"> <value-description type="greater-than"> <numerical-constant value="90"/> </value-description> ... </constraint-combination> </abort-condition> </conditions> <plan-body> <subplans type="sequentially"> ... <plan-activation> <plan-schema name="initial_plan"/> </plan-activation> <plan-activation> <plan-schema name="controlled_ventilation_plan"/> </plan-activation> </subplans> </plan-body> </plan> ... <plan name="controlled_ventilation_plan"> <plan-body> <subplans type="parallel"> ... <plan-activation> <plan-schema name="handle_PCO2_plan"/> </plan-activation> <plan-activation> <plan-schema name="handle_tcSaO2_low_plan"/> </plan-activation> <plan-activation> <plan-schema name="handle_tcSaO2_high_plan"/> </plan-activation> </subplans> </plan-body> </plan> ... </plan-group> </plans> </plan-library>

  5. Users’ Challenges • time saving • minimal learning effort • intuitive, simple, and clearly structured • Flow-Chart Algorithms / Clinical Algorithm Maps • Standards Proposal: Society for Medical Decision Making, 1992

  6. Asbru’s Challenges • logical sequences • hierarchical decomposition • flexible execution order • sequential, parallel, any-order, unordered • state characteristics of conditions

  7. Visual Representation

  8. Plan Examples

  9. Focus + Context

  10. Prototype

  11. User Centered Design • 3-step evaluation process • qualitative • scenario-based

  12. Limitations • no temporal aspects • execution support limited • introduction of new concepts • representation cumbersome for certain constellations

  13. Conclusions • visual communication of the logic of a treatment plan to domain experts • + quick verification of formal representation • based on a well-known representation • incorporation of Asbru concepts • interactive exploration, focus + context • user centered development approach

More Related