1 / 11

Web Interface for Health Care Database

Web Interface for Health Care Database. Priyanka Walke. System Description. Web interface that connects to the Health Care Database & displays the health information of the patients.

ronan-munoz
Télécharger la présentation

Web Interface for Health Care Database

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. Web Interface for Health Care Database Priyanka Walke

  2. System Description • Web interface that connects to the Health Care Database & displays the health information of the patients. • It would allow the users to fetch / update the patients health data from the Health Care Database by providing a search feature based on the Database attributes like Blood Pressure, Blood Sugar, EKG or SPO2. • The Health Care Database will also be accessible from the Online Health Care Monitor which can receive messages from & send messages to the Local Health Care System.

  3. Web Interface Health Care Database Online Health Care Monitor messages Local Health Care System Input Processor Uploader Blood Pressure Blood Sugar EKG General Health SPO2 GUI Web Server Sensors

  4. Messages • The Online Health Care Monitor accepts the User Profile & sends Msg 45 (User profile such as Name, Age, Sex, Height, Weight & Medical Conditions) to the Uploader & the Monitors. • The Sensors send Msg 30 (Sensor Data) to the Input Processor which passes the data & extracts the vital signals. It produces Msg 31 (Blood Pressure reading for Blood Pressure Monitor), Msg 33 (SPO2 reading for the SPO2 Monitor) & Msg 35 (EKG reading for the EKG Monitor).

  5. Messages (Continued…) • The Blood Pressure Monitor receives Msg 31 from the Input Processor & checks for abnormality. It performs an initial check if the High Blood Pressure reading is above 130 or not. If so, it generates an alert by sending Msg 32 (Blood Pressure alert) for the GUI which displays the vital signals. • The Blood Pressure Monitor accepts Msg 45 & 31 & produces Msg 32. • The Blood Pressure Monitor sends Msg 32 (Blood Pressure alert) to the Uploader which uploads the data to the Health Care Database. • The GUI accepts Msg 32, 34, 36, 38 & produces Msg 20 & 21.

  6. XML for specific message instances

  7. XML for Msg 31 <Msg> <Head> <MsgID>31</MsgID> <Description>Blood Pressure Reading</Description> </Head> <Body> <Item> <Key>Systolic</Key> <Value>114</Value> </Item> <Item> <Key>Diastolic</Key> <Value>61</Value> </Item> <Item> <Key>Pulse</Key> <Value>75</Value> </Item> <Item> <Key>DateTime</Key> <Value>2010-03-16 15:05:10.00000843</Value> </Item> </Body> </Msg>

  8. XML for Msg 32 <Item> <Key>Systolic</Key> <Value>114</Value> </Item> <Item> <Key>Diastolic</Key> <Value>61</Value> </Item> <Item> <Key>Pulse</Key> <Value>75</Value> </Item> <Item> <Key>Alert Type</Key> <Value>Blood Pressure Alert</Value> </Item> <Msg> <Head> <MsgID>32</MsgID> <Description>Blood Pressure Alert</Description> </Head> <Body> <Item> <Key>Diagnosis</Key> <Value>Severe</Value> </Item> <Item> <Key>Suggestions</Key> <Value>See doctor immediately</Value> </Item>

  9. XML for Msg 32 (Continued…) <Item> <Key>Name</Key> <Value>g3 Blood Pressure Monitor</Value> </Item> <Item> <Key>DateTime</Key> <Value>Sat Feb 27 18:10:20 EST 2010</Value> </Item> </Body> </Msg> <Item> <Key>Name</Key> <Value>g3 Blood Pressure Monitor</Value> </Item> <Item> <Key>DateTime</Key> <Value>Sat Feb 27 18:10:20 EST 2010</Value> </Item> </Body> </Msg>

  10. Scenarios • Redesigning the Users database in order to accommodate various attributes as shown below. • User table schema: • Id, first_name, last_name, email, date, SPO2DataStream, Systolic, Diastolic, Pulse, BloodPressureDataStream, DateTimeBP, DateTimeSPO2, EKGDataStream, DateTimeEKG, TemperatureDataStream, DateTimeTemperature.

  11. Scenarios (Continued…) • The Web Interface will allow the users to view the patient data & also search for the data based upon different search criteria’s such as Blood Pressure, Blood Sugar, EKG, SPO2 etc. • It will also allow update operation on the data. • Huge DataStreams in case of EKG or temperature would be stored in a file and a link to that file would be incorporated as an entry in the respective database field. • This Web Interface would be accessible under the chronobot subdirectory of the ipage.

More Related