Notes
Outline
Just in Time E-Learning for Medical Application

Scenarios Formalized for Able and Unable Patient
Aimee Pail Brown
Subrata Acharya
Scenarios:
Unable & Able Patient
Full documentation of Scenarios:
Scenario_JIT_Medical
Example of Unable Patient
Includes Orchestration, Choreography, and Timing Details
Example
Scenario – Unable Patient
Sensor Equipment takes video/picture of Patient
Data sent to Condition and Record Agent for storage
Sensor detects alarm and alerts Hospital
Hospital receives alarm and alerts Physician and Nurse
Physician queries Patient’s Current Condition for Diagnosis
Physician Requests Nurse/Dispatch to perform action
After action is performed, Doctor again queries Patient’s condition for outcome of action
Sequence Diagram - UML
Orchestration – Execution Flow
Choreography – Agent Collaboration
Scenario – Able Patient
Patient takes reading (temperature) by sensor equipment
Data sent to Condition and Record Agent for storage
Sensor detects alarm and alerts Hospital
Hospital receives alarm and alerts Physician and Nurse
Physician queries Patient’s Current Condition for Diagnosis
Physician sends an Action to be performed by Patient
After action, Physician again queries for updated Condition of Patient
Sequence Diagram - UML
Orchestration – Execution Flow
Choreography – Agent Collaboration
Analysis with time constraints
Formalization using Pi-Calculus
State Transition of Data & Alert Propagation
Emphasizes Parallel and Sequential Execution
Formalization using Pi-Calculus
Sensor Data Propagation Notation:
(Patient(data!); Sensor(data?,data!); Condition(data?,data!); Records(data?))*
Alarm Propagation Notation:
Patient(data!); Sensor(data?,alarm!); (Condition(alarm?,alarm!); Records(alarm?))|(Hospital(alarm?, alarm!);(Expert(alarm?)|Nurse(alarm?)))
Notation Symbols:
; - sequential composition
? – input data
! – output data
* - iteration
| - parallel composition
  Next step, Index Card Development….
(url to IC Card)