1 / 31

Patient Information Status Board

Patient Information Status 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

hollye
Télécharger la présentation

Patient Information Status 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 Information Status 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. Concept Diagram

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

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

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

  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. Project Goal To take last groups design and customize it for the CCU. Create a dynamic system that is user friendly, extensible, and reusable for other parts of the hospital. Create a web and mobile application for viewing and updating patient’s status on the fly

  9. Schedule

  10. Schedule

  11. Costs

  12. Functional Decomposition

  13. 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 • Apache Tomcat • Hibernate • GSON • Java 5.0

  14. Display Board The patient display board will be a view/read-only version of the workstation web-client. This display will be located in a doctor’s lounge not viewable by the public.

  15. Display Board

  16. Web Client Modules

  17. Mobile Application

  18. Mobile Client Modules

  19. Web and Mobile Use Case Design

  20. Web and Mobile Use Case Design

  21. Web and Mobile Use Case Design

  22. Web and Mobile Use Case Design

  23. Server and Database • Hibernate Objects • Room • Doctor • Log • User

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

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

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

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

  28. Task Breakdown • Daniel • Mobile client • Seth • Server and database • Chris • Web-client • Theodore • Security • Help with Web-client

  29. Current Status • Researching and familiarizing selves with technologies • Project Plan • Have a solid design document for implementing the desired system • Have a working skeleton of all components talking with each other • Server • Database • iPhone app • Web client

  30. Plan for next Semester Deploy first iteration of design in September, fall 2011 Test and incorporate feedback from staff for iteration Develop more functionality for next iteration Deploy final instillation sometime in November

  31. Questions? Patient Information Status Board Client: Iowa Health Systems Advisor: G. Manimaran Team: Daniel Sedam, Theodore Murdock, Seth Buntrock, Chris Nelson

More Related