1 / 13

Aimee Pail Brown Subrata Acharya

Just in Time E-Learning for Medical Application Milestone 2: Scenarios Formalized for Able and Unable Patient. Aimee Pail Brown Subrata Acharya. Introduction. Milestone 1 Create two scenarios for JiT Medical Application Unable Patient Scenario Able Patient Scenario

derekk
Télécharger la présentation

Aimee Pail Brown Subrata Acharya

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. Just in Time E-Learning for Medical ApplicationMilestone 2:Scenarios Formalized for Able and Unable Patient Aimee Pail Brown Subrata Acharya

  2. Introduction • Milestone 1 • Create two scenarios for JiT Medical Application • Unable Patient Scenario • Able Patient Scenario • Create UML sequence diagram for scenarios • Milestone 2 • Formalize the scenarios • Timing constraints • Orchestration and Choreography • Software Tool MagicDraw (12.5 EAP beta 1) • Provides tools to draw UML, orchestration, choreography diagrams • Representation of scenarios via pi-Calculus

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

  4. Sequence Diagram - UML

  5. Orchestration – Execution Flow

  6. Choreography – Agent Collaboration

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

  8. Sequence Diagram - UML

  9. Orchestration – Execution Flow

  10. Choreography – Agent Collaboration

  11. Formalization using Pi-Calculus • State Transition of Data & Alert Propagation

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

  13. IC Card team takes on from here…. Thank You!!!

More Related