Patient Information
Status Board
::Design::
Group Members: Daniel Sedam, Theodore Murdock, Seth Buntrock, Chris Nelson
Client: Iowa Health Systems of Des Moines
Advisor: Manimaran Govindarasu
Project Overview
To design and implement a Patient Status Board for doctors
and nurses with a supporting client web and mobile
application
Current System: white board and hand written notes
New System: Web and mobile application that allows quick
and easy patient entries and maintenance
High-level Design
High-level Design
Technology choices
Web and mobile based technology
Java Servlets
Javascript/jQuery and Ajax
MySQL
iOS and Coacoa
JSON
Hibernate
Block Diagram
Detailed Design
Database
MySQL
Hibernate
Server
Apache Tomcat
Gson api
JSON
Object
Jquery
JS
Framework/AJAX
JavaScript/AJAX
Web Client
IE
JSON-Framework
IOS Client
NSMutableDictionar
y
Detailed Design
Hibernate Data Objects
User
Long userID
String username
String(32) hash
String(1) group
String salt
Room
Long roomID
Int roomNumber
Int podNumber
Int priority
String(3) initials
Boolean inRestraints
Boolean onVentilator
String notes
List<Doctor>
doctorList
Doctor
Long doctorID
String doctorUsername
Boolean LeaveApproved
Detailed Design
Server/Client Communication
REST Type
URL
Upload Data
Result
GET
…/Room/1
None
Returns Room 1
JSON object to
client
GET
…/Room
None
Returns all Rooms
to the client
POST
…/Room/1
JSON object
Creates new
object into the
database
PUT
…/Room/1
JSON object
Updates Room 1’s
information
DELETE
…/Room/1
None
Removes Room 1
from the database
Detailed Design
Client Requests Room 3’s Data
1. HTTP POST: …/Room/3
Tomcat
Server
4. Returned as JSON Obj
3. Returns data as
Java object
2. Query: from room
where roomID=3
Database
Server
Web Client Design
Web Client Design
Web Client Design
Web Client Design
iPod touch App Design
iPod touch App Design
iPod touch App Design
Database
logout
Login
Patients
Menu
Server
Stats
Patients View
Edit
Map
Add/Remove
Web interface
Update database
Verification
Update
Automated Unit Testing
Ensure each web service updates or retrieves data correctly
boundary value testing
equivalence class testing
Ensure that only users with the proper credentials have
access to each service
Cactus testing framework
UI Testing
Perform each use case and alternate flow, verifying the
defined results.
May be supplemented by automated UI testing, based on the
outcome of our research into web testing methodologies.
Deployment and Beta/Usability
Testing
Beta version scheduled for late September
Allows for two month-long cycles of:
Gathering usability issues, bug reports, missing requirements (1
week)
Implementing new requirements and fixing bugs (2 weeks)
Redeploying the application (1 week)
Questions?