Medical Application

1. Giant Squid Michal Cohen Robet Esho Chris Hogan Kate Kuleva Nisha Makwana Alex Rodrigues Rafal Urbanczyk Medical Application

2. Topics Covered Requirements Design Planning Medical Application

3. Requirements General With the building of our internet application, we have come to a decision to create an application that will benefit those who need to make appointments for a doctor’s visit. This application will make, change, and cancel any appointments necessary. This application is aimed for use with the general public, who want to make a visit to the doctor’s office without going through any annoying staff members to create it. Medical Application

4. Medical Application Overview • The goal of this project is for anyone with an internet connection to be able and given the opportunity to assign appointment for themselves or others to a local doctor’s office. The site will be targeted for patients looking to have tests done. The site will be in the English language only. • All of these requirements are set by default and can be changed by the company to better accompany their business. These defaults help set up an understanding of what can be done with this application.

5. Medical Application Functional Requirements • These requirements will be able to identify what the system will be able to do. Without these requirements, the system will fail and all other requirements will initially become void.

6. Medical Application Functional Requirements • The site will be available to all users via a PC. (PC with internet access and a browser) • The user will be asked to log on with a username and password to gain access to the system.(unique username for each user) (Required to log in) • Able to view all personal information. (Qualified personal only will be able to)

7. Medical Application Functional Requirements • The user will not be able to register online. The user must come in for a checkup where the account will be created. • Able to edit personal records. (Only privileged staff can edit) • Cancel appointments. ( and notify the other party of such) • Able to view medical records. (by paitient) and (by paitient by day) • View all appointments by patient. • View all appointments by day. • View all tests by patient. (test results) • View appointments by doctor. (by day ?? or by something… or that is a lot)

8. Medical Application Functional Requirements • View all by day and by test. (appointments by appointment type) • View by day and by ID. (appointments) • View test results by ID. • View test results by ID and by tests. • Delete Tests (results) • Delete tests by type and client. • Delete tests by Client, type and date. • Delete test by data. • Add test • Change password.

9. Medical Application • Email notifications of appointments. (Don’t think we are doing this…) • Email notifications of cancellations. • Email notifications of reminders. (automatically 48 hours before appointment) • Make doctors. • Delete doctors. • Make Staff. • Delete Staff. • Make test types. • Delete test types.

10. Medical Application • Records can be deleted after seven years.(will be automatically deleted by system. We can’t grantee they won’t be deleted before then…) • Views can be seen by day • Views can be seen by patient • Views can be seen by doctor. • Overrides can be made. • Web server must be accessed by anyone on the internet. • Server must have admin with root functionality. • Log in must be implemented to keep information secure. • Calendar must be built into database to hold appointments.

11. Medical Application Functional Requirements • -Mention appointment can’t be conflicting. • -Appointments are scheduled by time. • -Different appointments take different times • -Have to hold information for how long the an appointment takes. • -Has to only offer times when the office is open. • -Time units defined as 10 minutes each. • -Privacy must be maintained. (ie restricted access).

12. Medical Application Functional Requirements • -Implementation of an Access Chart that allows admin to set privileges. • -So all the “views” and “makes” should be “privilege user can xxxxx” so that way it’s covered that the admin get’s to decide WHO gets to do what. • -Also, there are 3 things that can be done. ADD or MAKE (I think add is better), EDIT, and DELETE. You can’t edit an appointment… but you can edit a user, of any type, and the privileges, and the test results… but not the medical documents (since they are files).

13. Medical Application Non-Functional Requirements • These requirements are based on a specific criterion that can be used to judge the operation of a system, rather than specific behaviors.

14. Medical Application • The patient picks from a list of tests before seeing that is available to schedule an appointment. (list of appointment types, not tests anymore) • Every appointment must have a certain appointment type.(chosen by user) • Cannot have multiple instances of same test scheduled.(for the same patient) • Office info in portrayed. (this should be a functional) • Server must have a database. (secure and connected xxxx type)

15. Medical Application • All accounts must be able to access information on the office hours and locations. • The site will be running on Windows Server 2003 since we will be implementing ASP.NET code. • The application will run on a majority of internet browsers. Internet Explorer, Netscape, Mozilla, and Safari. • The database will be designed with Microsoft Access 2003, which will have SQL statements. • Performance of the site will vary from computer to computer. We will try and implement as much information to process through our server, leaving the client with minimal processing. • The system will be backed up on different ectweb servers. If all else fails, the system will be in place. Godaddy.com.

16. Medical Application Data • Data is a very important criterion. Stored data is what keeps the application running. The information that is stored will and must be secure to the fullest extent. This data is very personal and should not be shared with anyone else. The information will be kept in a secure database with minimal access to edit information. • The type of data that will be stored in the database would be medical records of each patient. This gives the user access to their information and available whenever the need arises. Test results will also be stored, to be viewed by the patient. The results can be reviewed days after the initial test was taken.

17. Medical Application Users • There are different categories of users on this application. The top level of users would be the administrator. The admin would be responsible for the entire system at all times. The admin would add and delete users as needed. He would fix any problems that would occur and give permission to any other user. Besides interacting with the system, he would test and maintain the entire system. • Another category would be doctors. The doctors would be able to grant patients to make more than one appointment. They will also be able to view entire schedules, appointments and medical records.

18. Users • The staff would also be able to view entire schedules and appointments but are not able to view medical records. The staff is able to troubleshoot minor problems. Lastly, the patients have the least amount of access. They are able to schedule appointments, cancel appointments and modify them

19. Design Info Info Info Medical Application

20. Planning Info Info Name of Project

21. Questions? Name of Project