1 / 13

MILE STONE 1

MILE STONE 1. Hospital Finder Component for SIS System. Anatoli Shein (aus4@pitt.edu). Motivation. Immediate help required. Motivation. At different locations. Motivation. Nearest hospitals. Motivation. Current traffic. SIS System Model. GUI. Health Sensor. Input Processor.

sasbury
Télécharger la présentation

MILE STONE 1

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. MILE STONE 1 Hospital Finder Component for SIS System Anatoli Shein (aus4@pitt.edu)

  2. Motivation Anatoli Shein Immediate help required

  3. Motivation Anatoli Shein At different locations

  4. Motivation Anatoli Shein • Nearest hospitals

  5. Motivation Anatoli Shein Current traffic

  6. SIS System Model GUI Health Sensor Input Processor SIS Server Hospital Finder VAMCIP Internet Google Maps API Daniel Petrov

  7. Passed Messages Hospital Finder Component Anatoli Shein Input messages:

  8. Passed Messages Hospital Finder Component Anatoli Shein Output messages:

  9. Output MsgID: 47 Coordinates Request <Msg> <Head> <MsgID>47</MsgID> <Description>Coordinates Request</Description> </Head> <Body> <Item> <Key>Name</Key> <Value>Hospital Finder</Value> </Item> <Item> <Key>DateTime</Key> <Value>2010-03-16 15:05:10.00000843</Value> </Item> </Body> </Msg> Anatoli Shein

  10. Input MsgID: 48 Coordinates Response <Msg> <Head> <MsgID>48</MsgID> <Description>Coordinates Response</Description> </Head> <Body> <Item> <Key>Longitue</Key> <Value>-79.956450</Value> </Item> <Item> <Key>Latitude</Key> <Value>40.441702</Value> </Item> <Item> <Key>DateTime</Key> <Value>2010-03-16 15:05:10.00000843</Value> </Item> </Body> </Msg> Anatoli Shein

  11. Output: Nearest Hospitals <Msg> <Head> <MsgID>48</MsgID> <Description>Nearest Hospitals</Description> </Head> <Body> <Item> <Key>HospitalLongitude</Key> <Value>82.145577</Value> </Item> <Item> <Key>HospitalLatitude</Key> <Value>-34.11120</Value> </Item> <Item> <Key>Distance</Key> <Value>15</Value> </Item> <Item> <Key>Time</Key> <Value>10</Value> </Item> <Item> <Key>Poliline</Key> <Value>a~l~Fjk~uOwHJy@P</Value> </Item> <Item> <Key>DateTime</Key> <Value>2014-10-16 16:10:18.000</Value> </Item> </Body> </Msg> Anatoli Shein

  12. Scenario: Hospital Finder component has to be pre-activated with message20: Create Component Patient is out for a walk He starts not feeling well, so one of the sensors generates an Alert Message (32, 34, 36, 38, or 42) The alert message triggers Hospital Finder component, which generates message 47: Coordinates Request Wait for message 48: Coordinates Response coming from GPS sensor Access Google Maps API through Hospital Finder component to get closest hospitals and directions in current traffic Generate and send to the GUI message 49: Nearest Hospitals GUI displays the results on the map, then the administrator chooses the most suitable hospital to contact for help Now Hospital Finder component can be killed with message22: Kill Component

  13. Anatoli Shein Thank you. Questions?

More Related