Patient Medical Data Software

1
Patient Medical Data Software
The Requirements Document
January 26, 2005
2
Operation - Battleship

• Allen Felix
• Eric Sanchez
• Michael Moore
• Anthony Myslinski
• Andy Guinn

• Natalia Filonenko
• Dragon Blagojevic
• Dragos Visan
• Adam Nowicki

3
Introduction

• Current State
• Medical facilities in the state of Illinois have
  their own individual patient logging system.
• Description of the problem
• There is no central database with patient
  information that follows the patient wherever
  they might seek medical attention.

4
Objective

• The Company P.M.D.S. (Patient Medical Data
  Software) has been hired by the Rush Hospital
  Group to design a web-based interface that will
  allow patients, physicians, and administrative
  staff access to pertinent data from the
  hospitals medical records through a standard
  Internet connection.

5
System Functions

• After registering with the new Rush system, a
  patient is able to retrieve contact information
  for his/her own physician and various hospital
  staff, manage his her own contact and insurance
  information, review his/her own medical and
  appointment history, search an extensive medical
  knowledgebase, and post questions to a forum with
  input from other patients, nurses, and
  physicians.
• Physicians and hospital staff will be afforded
  similar functionalities. Physicians and staff
  are able to review specific patient accounts,
  manage appointments, post notes regarding the
  patients medical conditions, and answer patient
  questions in the online forum.

6
Planning

• Used MS Project 2003 to develop - a Gantt chart
  with dependencies - a calendar of the entire
  project with tasks associated with member
  names - an individual member's list of
  responsibilities (including dates and deadlines)
• Benefits to using MS Project 2003 - Easy to
  add/delete tasks without ruining dependencies
  - Everything (calendar, Gantt chart) is
  automatically updated when a field is updated in
  the task list

7
Testing - Overview

• Our testing procedures are very specific. They
  directly coincide with the requirements document.
  We have two testers, going through the system
  performing different tasks.
• Two types of tests
• Level 1 Quick easy, not more than 6 steps
• Level 2 Very intricate, testing more advanced
  features such as reporting, database access and
  manipulations of data

8
Example of Testing Matrix
Current Requirements Testing Procedures Comments (Tester 1) Comments (Tester 2)
Functional - Patient      
1.2.1.1 - Patient will launch Internet Explorer 4.0 or above and enter the URL for the P.M.D.S. page for Rush Hospital Group Launch browser, go to website    
1.2.1.2 - Patient will click on a link indicating patient login page. click on patient login link    
1.2.1.3 - Patient login page will have a text field in the center of the page labeled Patient Login ID, and another text field below labeled Password. There will be a submit button located beneath these textboxes. -    
1.2.1.3.1 - If the patient has never registered before they will be taken to another page with registration information. Patient will enter information and will wait 1-2 business days for personal information to be verified by a member of the Hospital Administration Board and / or staff. Use invalid login and register for new account    
9
Requirements - Overview

• We have broken the Requirements down into two
  main categories. Both of these categories have
  many sub-categories.
• Functional Requirements
• Non-Functional Requirements

10
Functional Requirements OverviewThe Functional
Requirements are primarily having to do with the
actual P.M.D.S. system interface.
- All interfaces, web pages, reports, forum
discussions, emails and other correspondences
with patients, nurses or physicians must be in
formal English and in at least 12 point font.
Only Times New Roman, Arial, and Courier are
acceptable fonts.

• There will be 3 main account types
• Patient
• Physician
• System Administrator

• For each account type there are separate
• Login screens
• Main account pages
• System Access Features

11
Detailed Example

• Patient login page will have a text field in the
  center of the page labeled Patient Login ID,
  and another text field below labeled Password.
  There will be a submit button located beneath
  these textboxes
• If the Patient has never registered before they
  will be taken to another page with registration
  information. Patient will enter information and
  will wait 1-2 business days for personal
  information to be verified by a member of the
  Hospital Administration Board and / or staff.
• If the patient enters incorrect login
  information, he/she will be taken back to the
  initial login page. The login page will have an
  error message in red which states, There is an
  error with your login. Please try again. The
  patient will get three login attempts before the
  account is disabled and will have to contact the
  system Administrator to reactivate the account.
• If the patient successfully logs in, they will be
  taken to their main account page.

12
Non-Functional Requirements Overview
The Non-Functional Requirement are primarily
having to do with all things related to the
hardware of the actual system and its components.

• Web server
• Backup Web Server
• Desktop or Laptop Computers
• Software

• Coding
• Database
• Database Security
• Backup
• Code Maintenance

13
Detailed Example

• Software Requirements
• Microsoft Internet Explorer 4.0 or higher
  versions will be used to view the HTML version of
  the application
• ASP.NET and HTML editor such as Macromedia
  Dreamweaver or Visual Studio P.M.D.S. is
  responsible for installation, virus protection
  and licensing purchases ONLY on P.M.D.S. in
  house pcs.
• Microsoft Visio, Word, Project or PowerPoint will
  be used to design, document and present the
  project P.M.D.S. is responsible for
  installation, virus protection and licensing
  purchases ONLY on P.M.D.S. in house pcs.

14
Example of Wolf / Thief Statements vs.
Requirements
Requirements
15
Wolf Thief
16
Patient Login - Continued Wolf
Thief
17
Wolf Thief
18
Wolf Thief
19
Physician Login - Continued Wolf
Thief
20
Wolf Thief
21
Wolf Thief
22
Phys. Access Level Cont. Wolf Thief