ACME MEDICAL MANAGEMENT SYSTEM (AMMS)

Transcription

1 Section ACME MEDICAL MANAGEMENT SYSTEM (AMMS) 1.1 Purpose The main purpose of the AMMS is to facilitate reception desk functions at the Acme Medical Clinic (keeping track of patient and doctor information, scheduling appointments, etc) while allowing clinic staff to quickly search and locate patient information in real time. 1.2 Document Conventions All system features and requirements are listed in the order of decreasing precedence. 1.3 Intended Audience and Reading Suggestions This document is directed towards the designers, test team, project managers, and the ACME staff members who will be utilizing the patient-doctor database on a regular basis. It is highly recommended that the glossary as seen in Appendix A be reviewed prior to reading any section of this SDS. The suggested reading sequence for the ACME staff members is listed below: START 1. Appendix A 2. All subsections of section 1 3. All subsections of section All subsections of section 3.7 END All other sections are optional for the ACME staff reader. 1

2 Section Document Outline 1. Introduction... Error! Bookmark not defined. 2. Document Outline... Error! Bookmark not defined. 3. Document Description... Error! Bookmark not defined. 3.1 Introduction System Overview Design Considerations Assumptions Operating Environment General Constraints Development Methods Architectural Strategies Reuse of existing software components Future plans for extending or enhancing the software User Interface Paradigms Hardware paradigms Software Interfaces Error detection and recovery Communication mechanisms System Architecture UML class Diagram Policies and Tactics Development Testing Maintenance Interfaces Hierarchical Organization Compilation Detailed System Design Login Daily Room Schedule Doctors New Doctor Search Doctor Search Results for Doctors View Doctor Profile Patients New Patient New Patient Emergency Information Medical Insurance Information Search for Patient Search Results for Patients View Patient Profile (General Info Tab) View Patient Profile (Insurance Tab) View Patient Profile (Record Visits Tab) View Patient Profile (Medical History Tab) Scheduling Visitation Information Payment Examination Rooms Appointment Reminder Glossary Bibliography

3 Section 3.1 Introduction AMMS is intended to be used by the reception desk staff and doctors at Acme Medical Clinic to replace the current manual process to manage patient and doctor information. Currently, ACME is plagued by an inefficient and ineffective management system, which often leads to several problems which includes but not limited to the following: 1. Patients missing appointments 2. Scheduling conflicts 3. Examination room conflicts 4. Unforeseen waiting period between schedule appointment time, and the time the patient is seen by the doctor 5. Loss of patient files. 6. Difficulty in finding patient records. The AMMS will improve efficiency by assisting the reception desk staff in performing desk related functions. Similarly, this system will assist the doctors by providing them with a real-time view of their day-to-day appointments. There are other benefits that the AMMS will provide and these are: 1. Avoidance of schedule conflicts 2. Automated schedule reminders 3. Improvement of appointment scheduling, while allowing scheduling of the maximum appointments possible per day 4. Quick search interface for locating patient information such as insurance information, vitals, and scheduled appointments 5. Quick search interface for locating doctor information such as doctor name, doctor specialty, and scheduled appointments 6. Electronic data storage of patient and doctor record. 7. Easy to use graphical user interface 8. Addition, deletion and change functionality for maintaining doctor and patient records 9. Enforcement of a no wait policy 3

4 3.2 System Overview The AMMS serves as a replacement of the manual process employed by the reception desk staff in performing their day-to-day activities. The major functions provided by AMMS are: Data entry and modifications o Patient information o Doctor information o Visit information Doctor information retrieval Automated appointment reminders Appointment rescheduling Appointment scheduling Provision and maintenance of payment information o Methods of Payment Credit Card information Co-pay information Preferred Payment option Cash Retrieval of patient history o Initial visit o Scheduling History o Doctors Seen o Purpose of Visits o Descriptive Diagnosis and prescription o Vitals o Payments o Provision of electronic forms for patience and doctors 4

5 3.3 Design Considerations The design convention or programming standard to be used is the Microsoft Design Guidelines for Class Library Developers Assumptions 1. It is assumed that ACME has user-password management system which will be incorporated into AMMS. 2. It is assumed that ACME has SQL Server installed and running on a server. 3. It is assumed that any user (reception desk staff or doctor) possess some basic computer skills with the ability to type and use a Windows XP or 2000 PC. 4. It is assumed that ACME has an enforced NO WAIT policy 5. It is assumed that an ACME has an existing system which supports SMTP through a Microsoft exchange server Operating Environment AMMS will operate in a windows environment particularly on either a Windows XP or 2000 operating system. The Microsoft.NET framework 2.0 is a required component that must co-exist with the system General Constraints The following constraints were identified for the AMMS. a) The AMMS must work in a windows environment. b) The AMMS must interface with SQL server. c) The AMMS must be implemented in Microsoft.NET framework 2.0. d) The user (reception desk staff or doctor) must be notified when a search request is inappropriate or illegal. e) When a search is performed, the search results should be displayed and organized in tabs with the default tab being the general information tab. f) Each doctor is able to have more than one patient. g) Each doctor must have a unique ID number. h) Each patient must have a unique ID number. i) Each patient must have only one record. j) Any computer on which the AMMS will be running must have the following properties: I. 233 MHz minimum processor clock speed required (single or dual processor system); II. Intel Pentium/Celeron family, or AMD K6/Athlon/Duron family, or compatible processor available III. 128 MB of RAM or higher recommended IV. 10 megabytes of free disk space. 5

6 3.3.4 Development Methods Considerations for this project were first to divide the tasks grouped by the different users; the doctor, the receptionist, the patient, and credit card company. Once the tasks were grouped, data flow was analyzed between groups to see where information was generated to utilized. This lead from event-oriented decomposition to modular decomposition, to data-oriented decomposition, to settle on an objectoriented design. 3.4 Architectural Strategies Reuse of existing software components Patient and Doctor interfaces allows for entering new individuals, updating information, and deleting records those features and file maintenance are part of our Systems Toolbox and utilized as needed. Code that will be shared in AMMS can be seen when a doctor and a receptionist login into the system to search for patient information. They will both see the same screens and obtain the same results Future plans for extending or enhancing the software In the future, sales tax could be added to the application. An or text messaging system could also be interfaced in the future as an option to phone calls User Interface Paradigms The following rules will help design a user friendly, easy to navigate, and productive application. The rules followed by the design team are Shneiderman's 'Eight Golden Rules'. The Eight Golden Rules are: Strive for Consistency Enable frequent users to use shortcuts Offer Informative Feedback Design Dialogues to yield closure Offer simple error handling Permit easy reversal of actions Support internal locus of control Reduce short term memory load An example of these rules can be seen in the use of conventional drop down boxes throughout the application, the background color of all screens, a description (title) used in every screen, buttons to search, tabs to group relevant information in one screen, link back to main menu (present in every screen). 6

7 3.4.4 Hardware paradigms Any computer on which the AMMS will be running must have the following properties: MHz minimum processor clock speed required (single or dual processor system); 2. Intel Pentium/Celeron family, or AMD K6/Athlon/Duron family, or compatible processor available MB of RAM or higher recommended megabytes of free disk space. 5. A 7200 rpm hard drive Software Interfaces 1. The computer must have Windows XP/2000 installed. 2. Will use the.net framework 3. Will use SQL server 4. Will use existing password management system, for single logon to the system Error detection and recovery There should be a timeout for a session after a specified time (set by super-user). Error detection is described in detail in section for Functional Requirements, 5.3 for Security Requirements, 5.4 for Software Quality Requirements, 5.5 for Business Rules Communication mechanisms 1. functionality will be supported by the existing system used by ACME. 2. sent from the AMMS is customizable with patient name, and schedule appointment information. 3. Communication will be handled by contacting patients through automated telephone calls. 3.5 System Architecture The architectural style chosen was an object oriented design. This particular decomposition was chosen because it seemed to fit together with making patient and doctor abstract data types (ADT s). The patient abstract data type will contain all the necessary history, contact, and insurance information. The patient ADT will also interact with the payment ADT that contains all the patient account histories, outstanding patient balances, and outstanding insurance company balances. The doctor ADT will contain all contact information, specialty or field of medicine, and all patient history information from interaction with the patient ADT. 7

8 3.5.1 UML Class Diagram for AMMS Doctor search name doctor ID specialty contact info doctor_search() search_results() view_profile() Patient search name address patient ID contact info patient_search() search_results() view_profile() Payments cash credit card check amount bill_insurance() bill_patient() show_past_due() Doctor name address doctor ID specialty contact info new_doctor() update_doctor_table() Patient name address patient ID insurance info payment info contact info emergency info medical history schedule new_patient() list_of_doctors() update_patient_table() schedule_appointment() Credit Card System Scheduling doctor schedule exam room schedule daily room schedule show_monthly() show_available() open_time() show_daily() update_schedule() make_appointment() Reminders patient doctor type Check_appointment_date_time() generate_reminders() Automated reminder system 8

9 3.6 Polices and Tactics Development All the development is to be done with the.net development library and should use a mysql database to store the pertinent information. The project will be compiled using Microsoft Visual Studio.NET. All code will meet standard coding requirements. These will often link to the same page and will be merged into one cohesive application in the final stage of development Testing The individual pieces shall be tested separately and then once they are joined. Exhaustive testing is unnecessary, but full testing of everyday use should occur. In the event of a bug, a patch will be release within a reasonable time frame Maintenance The server should be backed up on a regular basis. The SQL database will need to remain as compact as the data set allows and old users should be removed. The client computers should be reasonably used and free of viruses and other problems Interfaces All manipulation of data should be done through the provided client web pages. The client and the server should be linked on a standard Ethernet network. All residents may only access the system by the use of a compatible web browser Hierarchical Organization The web pages should be laid out in an organized manner Compilation The system will be compiled using visual studio.net s built in compiler and will be loaded when the end user loads the default web browser. 9

10 3.7 Detailed System Design Login Display Components Username text box this text box is where the user enters their username. Password text box this text box is where the user enters their password. Sign In button - by selecting the user is logged in to the system s main screen. Display Precondition User must enter URL for application Display Post Condition Home screen for application is displayed Error Handling Username/Password will be verified. An error will be displayed and prompt the user to input proper values if username/password are incorrect. 10

11 3.7.2 Daily Room Schedule Display Components Daily tab Displays current tab Scheduling tab Allows users to enter submenu to schedule future appointment. Patient tab Allows users to enter submenu to register, update/search a patient. Doctors tab - Allows users to enter submenu to register, update/search a doctor. Reminders tab Allows users to enter submenu to view list of confirmed appointments. Payments tab Allows users to enter submenu to input information required for patient s payment. Daily schedule table Allows user to view current days scheduled by room and time. Logout link by clicking this link, the user is logged out of the system and is returned to login screen. Display Precondition User must be logged in Display Post Condition Displays sub menu 11

12 Displays login screen if logout button clicked Error Handling Screen will interface actively with scheduling, doctor, and patient database. If error occurs connecting to database, error message will be displayed Doctors Utilizes System Toolbox see Display Components Daily tab Allows users to view current days scheduled by room and time. Scheduling tab Allows users to enter submenu to schedule future appointment. Patient tab Allows users to enter submenu to register, update/search a patient. Doctors tab Displays current tab. Reminders tab Allows users to enter submenu to view list of confirmed appointments. Payments tab Allows users to enter submenu to input information required for patient s payment. New Doctor button - by selecting this button the new doctor screen is displayed Update/Search Doctor button - by selecting this button the update/search doctor screen is displayed. 12

13 Logout link by clicking this link, the user is logged out of the system and is returned to login screen. Display Precondition User must be logged in Doctor tab must have been clicked Display Post Condition Displays sub menu Displays login screen if logout button clicked Error Handling None New Doctor Display Components First Name Text box this box is where the user enters in the Doctor s first name Last Name Text box this box is where the user enters in the Doctor s last name Middle Initial Text box this box is where the user enters in the Doctor s middle initial Cell Phone# text box this text box is where the user enters the Doctor s cell phone number. 13

14 Work Phone# text box this text box is where the user enters the Doctor s work phone number. Pager Phone# text box this text box is where the user enters the Doctor s pager number. Specialty/Field text box this text box is where the user enters the Doctor s specialty Doctor ID# text box this text box is where the user enters the Doctor s ID number. Enter Button by selecting this button a new doctor profile is added to the system Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click the New Doctor button Display Post Condition Displays New Doctor screen blank. Error Handling If user enters a value that is not consistent with the variable type. An error will display and prompt the user to input the proper value. If user leaves all fields blank, error message will prompt the user to enter required fields If doctor already exists, an error message will be displayed and the user will be taken back to new doctor screen 14

15 Search Doctor Display Components Last Name Text box this box is where the user enters in the Doctor s last name First Name Text box this box is where the user enters in the Doctor s first name Middle Initial Text box this box is where the user enters in the Doctor s middle initial Work Phone# text box this text box is where the user enters the Doctor s work phone number. Cell Phone# text box this text box is where the user enters the Doctor s cell phone number. Pager Phone# text box this text box is where the user enters the Doctor s pager number. Specialty/Field text box this text box is where the user enters the Doctor s specialty Doctor ID# text box this text box is where the user enters the Doctor s ID number. Search Button by selecting this button the system looks for matching profiles Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). 15

16 Display Precondition User must be logged in User must click the Search for button Display Post Condition Displays Search Results for doctor Error Handling If all fields are blank, system will display error message prompting user to enter at least one field to return search results Search Results for Doctor Display Components Search Result links by clicking a link within the search results (if any), the user will be taken to the screen that displays the doctor s information. Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). 16

17 Display Precondition User must be logged in User must click the Search button in the Search Doctor screen Display Post Condition Displays Update/View screen for Doctor Error Handling If no search results are returned the user will be shown a message saying nothing was found View Doctor Profile Save Display Components Last Name Label this label is where the Doctor s last name is displayed First Name Label this label is where Doctor s first name is displayed Middle Initial Label this label is where Doctor s middle initial is displayed 17

18 Work Phone# Label this label is where the Doctor s work phone number is displayed Cell Phone# Label this label is where the Doctor s cell phone number is displayed. Pager Phone# Label this label is where the user enters the Doctor s pager number is displayed. Specialty/Field Label this label is where the Doctor s specialty is displayed. Doctor ID# Label this label is where the Doctor s ID number is displayed. Save button by clicking this button any information changed will be updated Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click the Search link from the search results screen Display Post Condition If back to main menu link is clicked, user will be taken back to main menu. Error Handling N/A 18

19 3.7.4 Patient Utilizes System Toolbox see Display Components Daily tab Allows users to view current days scheduled by room and time. Scheduling tab Allows users to enter submenu to schedule future appointment. Patient tab Displays current tab Doctors tab Allows users to enter submenu to register, update/search a doctor. Reminders tab Allows users to enter submenu to view list of confirmed appointments. Payments tab Allows users to enter submenu to input information required for patient s payment. New Patient button - by selecting this button the new doctor screen is displayed Search for Patient button - by selecting this button the search for patient screen is displayed. Logout link by clicking this link, the user is logged out of the system and is returned to login screen. Display Precondition User must be logged in 19

20 Patient tab must have been clicked Display Post Condition Displays sub menu Displays login screen if logout button clicked Error Handling None 20

21 New Patient Display Components Today s Date label this label will display the current date Social Security Number text box this box will allow users to enter their social security number Last Name Text box this box is where the user enters in the Patient s last name First Name Text box this box is where the user enters in the Patient s first name 21

22 Middle Initial Text box this box is where the user enters in the Patient s middle initial Address Text box this box is where the user enters the Patient s street address City Text box this box is where the user enters in the Patient s City State Text box this box is where the user enters in the Patient s State Zip Code Text box this box is where the user enters in the Patient s Zip Code Date of Birth Text box this box is where the user enters in the Patient s date of birth Home Phone Text box this box is where the user enters in the Patient s home phone number Cell Phone Text box this box is where the user enters in the Patient s cell phone number Work Phone Text box this box is where the user enters in the Patient s work phone number Address text box this box is where the user enters in the Patient s Address Sex text box this box is where the user enters in the Patient Sex Employer text box this is where the user enters in the Patient s Employer Occupation text box this is where the user enters in the Patient s Occupation Patient Id text box this is where the user enters in the Patient s ID Reason for Visit text box this is where the user enters in the Patient s reason for visit Preferred Contact Method text box this is where the user enters in the Patient s preferred contact method Next Button by selecting this button the user will be taken to the next screen for Patient information Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click the New Patient Button 22

23 Display Post Condition Displays New Patient second screen Error Handling If user enters a value that is not consistent with the variable type. An error will display and prompt the user to input the proper value. If user leaves all fields blank, error message will prompt the user to enter required fields If patient already exists, an error message will be displayed and the user will be taken back to new patient screen New Patient Emergency Information Display Components First Name Text box this box will allow users to enter the Patient s emergency contact s first name Last Name Text box this box will allow users to enter Patient s emergency contact s last name Middle Initial Text box - this box will allow users to enter Patient s emergency contact s middle initial Relationship text box - this box allow users to enter the contact s relationship to Patient 23

24 Telephone # text box this box will display the Contact s phone number. Back Button by selecting this button the user will be taken back to the main Patient Information Screen. Next Button by selecting this button the user will be taken to the next screen for Medical Insurance Information. Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click the Next Button from main Patient Information Screen User must click the Back Button from the Medical Insurance Information Screen Display Post Condition Displays Medical Insurance Information screen. Displays main Patient Information screen Error Handling If user enters a value that is not consistent with the variable type. An error will display and prompt the user to input the proper value. If user leaves all fields blank, error message will prompt the user to enter required fields 24

25 Medical Insurance Information Display Components First Name Text box this box will allow users to enter the Patient s first name Last Name Text box this box will allow users to enter Patient s last name Middle Initial Text box - this box will allow users to enter Patient s middle initial Relationship to Patient text box - this box allow users to enter the relationship to Patient Insurance Company text box this box allow users to enter the Insurance Company Name Insured s Employer text box this box allow users to enter Insured s Employer s Name Insured s SS# or ID# text box this box allow users to enter Insured s Social Security Number of Identification Number Group # text box this box allow users to enter Insured s Group Number Back Button by selecting this button the user will be taken back to the main Patient Information Screen. 25

26 Enter Button by selecting this button a new Patient profile is added to the system Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click the Next Button from main Emergency Contact screen Display Post Condition Displays New Patient Information Screen blank Displays main menu (daily menu) Error Handling If user enters a value that is not consistent with the variable type. An error will display and prompt the user to input the proper value. If user leaves all fields blank, error message will prompt the user to enter required fields 26

27 Search for Patient Display Components Last Name Text box this box is where the user enters in the patient s last name First Name Text box this box is where the user enters in the patient s first name Middle Initial Text box this box is where the user enters in the patient s middle initial Work Phone# text box this text box is where the user enters the patient s work phone number. Cell Phone# text box this text box is where the user enters the patient s cell phone number. Home Phone# text box this text box is where the user enters the patient s pager number. Patient ID# text box this text box is where the user enters the patient s ID number. Search Button by selecting this button the system looks for matching profiles 27

28 Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click the Search for button Display Post Condition Displays Search Results for patient Error Handling If all fields are blank, system will display error message prompting user to enter at least one field to return search results Search Results for Patient Patient Display Components Search Result links by clicking a link within the search results (if any), the user will be taken to the screen that displays the patient s information. Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). 28

29 Display Precondition User must be logged in User must click the Search button in the Search Patient screen Display Post Condition Displays General Information Tab for Patient. Error Handling If no search results are returned the user will be shown a message saying nothing was found View Patient Profile (General Info Tab) Display Components Date of last visit label this label will display the date of the last visit Social Security Number label this label will display the patient s social security number Sex text box this label will display the patient s Sex Last Name Text box this label will display the patient s last name 29

30 First Name Text box this label will display the patient s first name Middle Initial Text box this label will display the patient s middle initial Address Text box this label will display the patient s street address City Text box this label will display the patient s City State Text box this label will display the patient s State Zip Code Text box this label will display the patient s Zip Code Date of Birth Text box this label will display the patient s date of birth Home Phone Text box this label will display the patient s home phone number Cell Phone Text box this label will display the patient s cell phone number Work Phone Text box this label will display the patient s work phone number Address text box this label will display the patient s Address Employer text box this label will display the patient s Employer Occupation text box this label will display the patient s Occupation Preferred Contact Method text box this label will display the patient s preferred contact method General Info Tab - displays the current tab Insurance Tab - displays the insurance information Record Visits Tab - displays the record of previous visits Medical History Tab - displays the medical history Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click a link from the patient search results Display Post Condition Displays chosen tab Taken to main menu if main menu link clicked 30

31 Error Handling N/A View Patient Profile (Insurance Tab) Display Components Name of Account Holder label - this label displays the name of the insurance account holder Company Name label this label displays the Insurance Company Name Phone Number label this label displays the Insurance Phone Number Insurance Number label this label displays the Insurance ID Number Last Co-pay/Payment Amount label this label displays the amount of the last payment General Info Tab - displays the patient s general information Insurance Tab - displays the current tab Record Visits Tab - displays the record of previous visits Medical History Tab - displays the medical history Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition 31

32 User must be logged in User must click the Insurance Tab Display Post Condition Displays different tab Displays main menu (daily menu), if main menu link clicked Error Handling N/A View Patient Profile (Record Visits Tab) Display Components Date of Previous Visit label - this label displays the date of previous patient s visits Filter Search by date text box this box will allow the user to display only a particular month/day date of visits General Info Tab - displays the patient s general information Insurance Tab - displays the insurance tab 32

33 Record Visits Tab - displays the current tab Medical History Tab - displays the medical history Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in User must click the Insurance Tab Display Post Condition Displays different tab Displays main menu (daily menu), if main menu link clicked Error Handling N/A View Patient Profile (Medical History Tab) 33

34 Display Components Date of Visit label this label displays the date of Patient s visit. Reason for Visit label this label displays the Patient s reason for visit. Doctor s Notes label this label displays the Doctor s notes. Heart Rate label this label displays the Patient s heart rate. Systolic label this label displays the Patient s Systolic. Diastolic label this label displays the Patient s Diastolic Temperature label this label displays the Patient s temperature for the current visit Weight label this label displays the Patient s weight. Height label this label displays the Patient s height. General Info Tab - displays the patient s general information Insurance Tab - displays the patient s insurance information Record Visits Tab - displays the patient s record visits Medical History Tab - displays the current tab Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in Display Post Condition Displays payment screen Displays login screen if logout button clicked Error Handling Screen will interface actively with scheduling, doctor, and patient database. If error occurs connecting to database, error message will be displayed. 34

35 3.7.5 Scheduling Display Components Daily tab Allows users to view current days scheduled by room and time. Scheduling tab Displays current tab Patient tab Allows users to enter submenu to register, update/search a patient. Doctors tab - Allows users to enter submenu to register, update/search a doctor. Reminders tab Allows users to enter submenu to view list of confirmed appointments. Payments tab Allows users to enter submenu to input information required for patient s payment. Daily schedule table Allows user to view current days scheduled by room and time. Logout link by clicking this link, the user is logged out of the system and is returned to login screen. Display Precondition User must be logged in 35

36 User must click scheduling tab Display Post Condition Scheduling will be adjusted for month Displays login screen if logout button clicked Error Handling Screen will interface actively with scheduling, doctor, and patient database. If error occurs connecting to database, error message will be displayed Visitation Information 36

37 Display Components Date of Visit text box this box allows users to enter date of Patient s visit Reason for Visit text box this is where the user enters in the Patient s reason for visit Doctor s Notes text box this is where the user enters in the Doctor s notes Heart Rate text box this is where the user enters in the Patient s heart rate for the current visit Systolic text box this is where the user enters in the Patient s Systolic for the current visit Diastolic text box this is where the user enters in the Patient s Diastolic for the current visit Temperature text box this is where the user enters in the Patient s temperature for the current visit Weight text box this is where the user enters in the Patient s weight for the current visit Height text box this is where the user enters in the Patient s height for the current visit Next Button by selecting this button the user will be taken to the payment screen. Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in Display Post Condition Displays payment screen Displays login screen if logout button clicked Error Handling Screen will interface actively with scheduling, doctor, and patient database. If error occurs connecting to database, error message will be displayed. 37

38 Payment Display Components Payment Account Holder text box this is where the user enters in the Payment Account Holder s name, if payment is by credit card Cash/Check check box this is where the user checks if the payment is by Cash or Check. Address text box this is where the user enters in the Address of the Account Holder Credit Card Number text box this is where the user enters in the Credit Card Number, if paid with Credit Card. Amount text box this is where the user enters in the Amount paid by the patient. Back Button by selecting this button the user will be taken back to the visitation information screen Pay Button by selecting this button the user will process the credit card/cash payment and keep a record of the transaction Back to main menu link by clicking this link the user will be taken back to the main menu(daily tab). Display Precondition User must be logged in 38

39 Display Post Condition Displays sub menu Displays login screen if logout button clicked Error Handling Screen will interface actively with scheduling, doctor, and patient database. If error occurs connecting to database, error message will be displayed Examination Rooms Room are maintained through the Scheduling Appointment Reminder Handled by automated system 39

40 Appendix A Glossary Term Database Software Requirements Specification Stakeholder Reception Desk Staff Doctor AMMS SQL Server No wait policy MHz MB RAM SDS SMTP Definition Collection of all the information monitored by this system. A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document. Any person with an interest in the project who is not a developer. User of the system. This are principal system user This is the secondary system user Acme Medical Management System Data store for the system. System interfaces with this. This is a policy that ensures that appointment times as honored. Thus, if an appointment is scheduled for 8am, the patient must see the doctor at exactly 8am and no later. MegaHertz MegaByte Random access memory Software requirements specification Simple mail transfer protocol Bibliography References The Case o f The Killer Robot, Richard G. Epstein, West Chester University West Chester, PA, epstein@golden, wcupa, edu, Copyright 1989, 1994 Richard G. Epstein 40