1 / 33

Patient Status Information Board

Patient Status Information Board. Team members: Daniel Sedam, Theodore Murdock, Seth Buntrock , Chris Nelson Advisor: G. Manimaran Client: Iowa Health Systems, Des Moines. Problem Statement. Difficult to track patients Knowing location of patients Patient data A need for

jonco
Télécharger la présentation

Patient Status Information Board

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. Patient Status Information Board Team members: Daniel Sedam, Theodore Murdock, Seth Buntrock, Chris Nelson Advisor: G. Manimaran Client: Iowa Health Systems, Des Moines

  2. Problem Statement • Difficult to track patients • Knowing location of patients • Patient data • A need for • Real-time patient information • Electronic system • Enhance communication between staff

  3. Solution • Design and Implement a Digital System that allows the CCU staff to quickly and efficiently keep track of patients status as well as the CCU status as a whole. • Components in the System • Patient Status Display Board • Web Client • Mobile Client • Sever and Database

  4. Concept Diagram

  5. Functional Requirements • Event Entry and Display • Laptop workstations • Mobile devices • Track Performance • Manage Users • Interactions • Database

  6. Non-Functional Requirements • Quick interaction • 10 seconds or 7 keystrokes • Easy to learn • 1 or 2 uses to familiarize • Privacy/Security • Improve overall patient flow • Extensible and dynamic

  7. Assumptions/ Limitation Users will be hospital personal within the CCU unit and associated doctors The network will be reliable Display board will be viewable by personal within the CCU only

  8. Market Survey • Current Display within the CCU unit at Methodist West • Lacking electronic way to display and record information about current patients • Other departments within Hospital are receiving electronic systems while the CCU is not • Old “System” • Marker and Dry erase board • Hand-written notes

  9. Risks and Mitigations • Availability of client, or lack thereof. • Increased flexibility with meeting times • Privacy/Security issues • Coordinating with HIPPA privacy officer • Scope – Requirements creep • Sticking to the project schedule • Shelved software (Not used by intended users) • Usability testing

  10. Hardware and Software Technology • Mobile Device • iOS 4.3 • Cocoa touch • 320 x 480 resolution screen • Wireless networking capabilities • Workstation • Windows IE 7.0.5730.13 • 17in monitor with 1280 x 1024 resolution • jQuery • JavaScript/Ajax • Html/CSS • Server • MySQL • Play Framework • Hibernate • GSON • Java 5.0

  11. Schedule

  12. Work Breakdown Daniel Sedam: Mobile Client Chris Nelson: Web Client Seth Buntrock: Server back-end and Database Theodore Murdock: Web Client

  13. Costs

  14. ImplementationDisplay Board & Web Client • Tools • Eclipse • Learning Experience • Web-based programming • AJAX and jQuery • Database communication

  15. ImplementationDisplay Board & Web Client • Log-in Page • Controlled Access • Main Page and Display • CCU Map • Patient Table • Status • Room number • Doctors • Notes • In Restraints • On Ventilator

  16. Add/Edit Patient • Add Patient • Select Empty room from map • Click add new patient button • Edit Patient • Click edit button at end of patient row • Select desired room from map • Having limited number of fields for patients • allows for quick and easy system maintenance

  17. CCU Map Visually shows current status of entire CCU • Color Coated statuses • White: Empty room • Red: Critical (not going anywhere) • Yellow: Stable • Green: Ready to transfer Access to viewing / adding/ editing patient information by clicking a room from the map

  18. Web Client Testing • Unit Testing • Firefox/Chrome/IE • Integration Testing • Usability Testing • Client feedback / survey • Field Testing • Unsuccessful due to client

  19. Web Client Evaluation • Initial Limitations / Issues • Familiarizing self with technology • Lining up communication • Limited feedback from visit • Client Evaluation • Easy to use • Quick interactions • Easy to see status of CCU

  20. Implementation Mobile Client • Tools • Xcode IDE • iOS simulator • Learning Experience • Database Communication • Mobile Interface Design • Objective C

  21. Implementation Mobile Client Offers an alternate way of viewing and updating system • Offers same functionality as Web Client • Mange Users • Logs • Manage Patients

  22. Mobile Client Menu • Nurse Menu • View Patients Information • CCU Map • Administrator Menu • View Patients Information • CCU Map • Manage Users • Logs Nurse Menu Admin Menu

  23. Mobile Client • Patient List • Quick reference list of patients sorted into Pods • Shows limited information • Patient Details • Room number • Initials • Status • Doctors • Notes • In Restraints • On Ventilator

  24. Mobile Client Testing Tested using Apple’s iPhone Simulator Manual Testing on both simulator and iPod touch device

  25. Mobile Client Evaluation • Issues • Client feedback from visit • Limitations • User’s willing to learn and use the application • Willingness of client to buy devices

  26. ImplementationSever / Database • MySQL • Play Framework • Relational database support through JDBC • Hibernate • JSON • Various other technologies and libraries

  27. Functional Decomposition

  28. Server / Database Testing JUnit Tests Restful Call Tests Integration Tests with Clients

  29. Testing Frameworks • JUnit • Java Unit Testing • Selenium framework • Automated JUnit Tests

  30. Testing Techniques Automated Unit Testing Edge case Testing UI testing Usability Testing

  31. Testing Results By implementing system in iterations we were able to find and fix bugs quicker Able to fix bugs without creating new ones Stronger, more robust system since system built in iterations allowing code to be tested multiple times with new functionality

  32. Conclusion / Future Work • Over all the project was a success • System follows all requirements • Client excited to use system • Integrate System with their legacy system • Load patient information from their system into ours

  33. Questions Custom Patient Information Status Board for Iowa Health Systems Client: Valerie with Iowa Health Systems of Des Moines Team: Daniel Sedam, Theodore Murdock, Seth Buntrock, Chris Nelson Advisor: G. Manimaran

More Related