Event-Driven Rule-Based Reasoning using EYE Ben De Meester Dörthe Arndt, Pieter Bonte, Jabran Bhatti, Wim Dereuddre, Ruben Verborgh, Femke Ongenae, Filip De Turck, Erik Mannens, and Rik Van de Walle University Ghent – iMinds – Multimedia Lab [email protected]| @Ben__DM http://ceur-ws.org/Vol-1488/paper-08.pdf OrdRing2015@ISWC | October 11 th 2015 | Bethlehem, PA
24
Embed
OrdRing2015 - Event-Driven Rule-based Reasoning using EYE
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Event-Driven Rule-Based Reasoning using EYE
Ben De MeesterDörthe Arndt, Pieter Bonte, Jabran Bhatti,
Wim Dereuddre, Ruben Verborgh, Femke Ongenae, Filip De Turck, Erik Mannens, and Rik Van de Walle
OrdRing2015@ISWC | October 11th 2015 | Bethlehem, PA
We present
A nurse call system via reasoning.
Why via (rule) reasoning?
How is it done?
Where are we now?
eHealth Scenario1. Call launched – select nurse + update call2. Call Redirect – select different nurse3. Call Temp. Accept – Update Call Status4. Corridor – Location update5. Patient location – update location, turn on lights and update nurse6. Presence on – update call, turn on lights & update nurse status7. Presence off – update call, turn off lights & update nurse status7. Presence off – update call, turn off lights & update nurse status8. Corridor – update location, turn off lights & update nurse status
A Nurse call system
Hospital, finding the most suitable nurse.
Most suitable?Trust relationshipCompetencesLocationStatus
ACCIOHealthcare ontology (DL)
How complex?
Assigning the ‘correct’ nurse can be complex
This complex
Filters in sequenceCorrect competences
Decisions in sequenceBeing closer and with a patient is more important than being far away and free
ConfigurabilityEvery hospital is different
So, you want to assign a nurse?
Needs
Event-basedNurses move, calls get made, …
StatefulKeep current states of the nurses
Scalable1 – 50 wards
ExpressiveDL-ontology + complex decision trees
Reasoning techniques
OWL DL-reasoning + SPARQLCon: Bad performance (e.g., location calculation for SPARQL)
Stream reasoningCon: not enough expressitivity
OWL-RL + rule reasoningCon: Not DL (but not necessary for this use case)Pro: easy mapping from decision treesPro: all rules are executed at oncePro: one system for everything
N3
{ this } => { that }
Turtle superset
Very expressivethat can be rulesbuilt-ins (e.g. time predicates)Datalog is not expressive enoughForward and backward reasoning
EYE Reasoner
Performant
PrologEYE supports all built-in Prolog predicates
Rule reasoning
File-based
Use case analysis
Small portion dynamic dataSplit up static from dynamic
State changes can introduce conflictProgrammatic update