Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Mini project Requirements Management HIT- 403 Software requirement specification document For Opd management system, Submitted to: Dr. Anandhi Ramachandran Prepared By: Dr. Nitin prasher (pg/10/027) Anindam BAsu (pg/10/005)
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 1
Page 2
1.2 Scope of the work The proposed software product is the OPD management system. The system will be used in the Outpatient Department of the hospital. The system will be used to register a new patient for the OPD consultation and provide appointment to the new and old patients for the doctors consultation. The system will also help the patients to be registered online and get prior appointment for a doctor while sitting at their homes. The OPD management system consists of 6 users: 1) Administrators (Super Users) 2) Front Desk Personnel 3) Billing Personnel 4) Medical Assistant 5) Doctors 6) Website (www.abchospital.com) The administrator will use this system for generating reports and analysis so that it can be further use for the better functioning of the hospital. The system will also help the hospital with one of the major problems they are facing and i.e. managing the long queues of waiting patients. Also the manual billing for the consultation and other services for the OPD will also become electronic.
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 4
No
If ordered revisit
Yes
Yes
Yes
No
No
Page 6
5) Medical Assistant: Medical assistant are the assistant to the doctors which are taking all the details of the patients and also calls the patients who are waiting outside. The
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 7
2.3 Product functions The system functions can be described as follows: 1) Registration of the Patients: Whenever a new patient is coming for the OPD consultation, the front desk personnel register the patient to the system. The system generates a UID for the patient which is now been used by the other users who are the part of this system. If the patient is old then the front desk personnel search for the patient in the system by using its UID or any other data element such as Name, Address, mobile number etc. The front desk personnel assigns the consultation room to the patient. 2) Appointment: The patient can get the appointment through this system. The registered patient is been provided with the appointment with the consultant. The front desk personnel gives appointment while checking the scheduler of the consultant which is been provided by the doctors in the system. The system generates a token number after the appointment has been saved. SMS facility is also been provided. 3) Web Based Registration and Appointment: The system will be integrated with the hospital website. The system allows the patient to register and get appointment online. The main feature of this integration is that the patient will not get the UID after the patient is getting registered. The system will generate the token number for the patient and the details are also send as SMS. 4) Billing: In this, the billing personnel logs into the system and provide with the bill for the patient. The bill includes the preconsultation billing and billing for the services which is ordered after the doctor consultation. The billing system also allows the user with the free text so that they can update the bill for the patients if required. 5) Queue Management: The token number given to the patients after the appointment is displayed in the Display which is kept in front of the OPD consultation room. The system automatically redirects the next token assigned to that consultation room.
Page 8
2.4 General constraints The hospital is having website www.abchospital.com which works in MySQL database. The server is working on linux platform and the minimum browser is Internet Explorer 6, Google Chrome, Mozilla 3.1 and higher and other browsers. The language used is HTML The hospital management wants the system should be integrated to the other departments. The system should have a Graphical user interface so that the user feels it easy to use. The system should be having very less down time not more than 1 minute. 2.5 Assumptions and Dependencies It is assumed that the hospital will have at least 10 computers with the Windows XP as the Operating System for the system. The hospital should have Display Systems installed at the entrance of each consultation room.
It is assumed that the Hospital will have enough trained staff to take care of the system.
Page 9
Note: * represents Low Priority; ** Medium Priority; *** High Priority Registration
OPF001 Patient Details*** The system shall have the following mandatory information for patient: First Name, Last Name, Phone Number, Address (Present & Permanent) Postal Code, City, Country etc. (Please See Annexure). OPF002 Register New Patient*** The system should be able to register new patients coming for the OPD (both online and offline). OPF003 Generate UID*** The system should generate a patient ID after the registration has been done except for the online registration. It should also be providing a registration print out. OPF004 Patient Search*** The older patients should be able to search in the system easily using the UID, patient name, mobile number, DOB, Residence number, email ID etc. OPF005 Revisit of old patient** The system should not provide another UID for the older patients who are coming for the revisit in the OPD. OPF006 Assign Consultation Room*** The front desk staff shall use the system to assign the consultation room for the patient after registration.
Consultants Scheduler
OPF007 Upload Scheduler*** The system should allow administrator to upload a scheduler in a specific format monthly so that the prior appointments could be provided to the patient. OPF008 Change/Update the Scheduler*** The system should allow administrator to do any changes/ updating the scheduler is necessary.
Page 10
Appointment
OPF010 Appointment to the patient*** The system should provide appointment to both old and new patients (online and offline) after the complete registration. OPF011 Appointment Details The appointment shall contain the following: Date and Time of the appointment, Consultant Name (if provided by the patient), Reason for appointment (Optional). OPF012 Generate Token Number The system should generate a number (not same as UID) which may term as token number for the appointment of the patient. OPF013 Telephonic Appointment For telephonic appointment only patient name and contact number is required for providing the appointment. OPF 014 SMS to the patient The appointment detail is to be sent to the patient via SMS or email (if provided). OPF 015 Appointment Update The system shall allow the users to update/ change the appointment details and the updated details to be sent to the patient via SMS/email. OPF016 Token Assign The system shall allow the administrator to update/edit the token number if the patient has not arrived for that day. (The token number can be assigned to any other patient).
Billing
OPF017 Patient Bill The system shall provide with the billing for all the services in the OPD like procedures, pharmacy etc. OPF018 Bill Print The system shall print out the detail bill to the patient before going for consultation (only preconsultation billing). Other services billing is to be provided as per order.
Page 11
Queue Management
OPF022 Display Token No.*** The system should be able to display the token number of the patient in the display screen at the entrance of the consultation room. OPF023 Redirect Token Number*** The system should automatically redirect the token number for the assigned consultation room. OPF024 Call the patient*** The system should allow the medical assistant to the consultant to call next patient after the consultation of the previous patient is over. The next assigned number should be displayed.
Database
OPF025 Staff Information*** Each Staff who are directly or indirectly involved in the system shall have mandatory information: Employee ID, First Name, Last Name, Phone Number, Address, Postal Code, City, Country, Employee Type. OPF026 Reset Information*** Before saving in the database, there should be reset option if entered incorrectly. OPF027 Employee Search** The system shall allow the administrator to search (using last name, first name or Employee ID). OPF028 Update Employee Information**
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 12
Reports
OPF029 Periodic Reports*** The system should generate reports for the number of registration periodically (daily/ weekly/ monthly/ yearly). OPF030 Analysis*** The system should help the administration to analyze the data with any option present in the database. 3.2 Non functional requirements OPNF001 Login ID*** All the users using the system should have login ID and password respectively. OPNF002 Modification** Any modification in the database (insert, change or update) shall be synchronized and done by the administrator. OPNF003 Signature*** The bill/ registration slip generated should have a provision of electronic signature. OPNF004 Users*** Users shall be able to view all the information in the system regarding their specific module but shall not be able to modify any information in it. OPNF005 Authentication*** Administrator should be provided with an additional password for authentication (including username and password). OPNF006 Capacity*** The system must support at least 50 people at any given specific time (offline). OPNF007 Web Based Capacity*** The system must support 1000 people during online registration and appointment. OPNF008 User Interface*** User interface should open within 5 seconds. OPNF009 Response Time*** The system shall give response within 2 seconds after submitting the details.
Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 13
Page 14
Requirement ID
OPF001 OPF002 OPF003 OPF004 OPF005 OPF006 OPF007 OPF008 OPF009 OPF010 OPF011 OPF012 OPF013 OPF014 OPF015 OPF016 OPF017 OPF018 OPF019 OPF020 OPF021 OPF022 OPF023 OPF024 OPF025 OPF026 OPF027 OPF028 OPF029 OPF030
Name of Requirement
Patient Details Register New Patient Generate UID Patient Search Revisit of Old Patients Assign Consultant Room Upload Scheduler Change/Update Scheduler Reminder Appointment to the patient Appointment Details Generate Token Number Telephonic Appointment SMS to the patient Appointment Update Token Assign Patient Bill Bill Print Bill Change OPD Card Print Price Changes Display Token Number Redirect Token Number Call the patient Staff Information Reset Information Employee Search Update Employee Information Periodic Reports Analysis
Priority
High High High High Medium High High High Medium High High High Low Low High Medium High High Medium Low High High High High High High Medium Medium High High
Page 15
Appendix
Page 16
Page 17
Page 18
Registration System
Appointment System
Billing System
Online System
Offline System
Online System
Offline System
Page 19
Page 20
Patient Registration
Doctor, Administrator
Upload Scheduler
Patient Appointment
Website, Patient
Generate Bill
Manage Queue
Page 21
Page 22
Actors: Front Desk Personnel & Patients Description: Here the patient is going to be registered and is provided with a Unique Identification Number for the patient to get the consultation in OPD. Preconditions: 1. 2. Postconditions: 1. 2. Normal Flow: 1. 2. 3. 4. 5. 6. Alternative Flows: 1. Front Desk is logged into the system. The patient has arrived to the front desk The patient gets a Print Out with Registration Details. Patient gets a UID number. Patient arrives at the front desk counter. Demographic details are taken System generates a UID for the patient. The details are saved for the patient. Print out is given out to the patient. Consultation room is assigned. If patient has already been registered then the front desk personnel would search the patient and assign the consultation room. Exceptions: 1. If the details are wrong then the Reset button is clicked then the details have to be filled again. Includes: None Priority: *** Frequency of Use: 10 users. Used from 8 am to 8 pm Special Requirements: 1. The system should generate a UID which is unique throughout the hospital Assumptions: There are around 500 patients coming for the OPD Consultation Notes and Issues: The system should not have a downtime of more than 1 minute. The registration cant be done for the patient on previous date.
Page 23
Page 24
Actors: Doctor, Administrator Description: The system would allow the doctor to upload his/her scheduler for the month. The changes can be made by the administrator only. Preconditions: 1. Doctor should be logged into the system. 2. The upload should be in Excel format. Postconditions: 1. The doctor scheduler is uploaded. Normal Flow: 1. The doctor uploads the scheduler in the system. 2. The scheduler is been used for the appointments Alternative Flows: 1. The scheduler can be updated or changed by the administrator Exceptions: None Includes: The SMS is to be send to the doctor for uploading the scheduler Priority: *** Frequency of Use: Can be used weekly/monthly as per requirement. Special Requirements: The administrator should be able to update and do changes as per requirement and send the same for appointment. Assumptions: The scheduler format is been provided by the administrator Notes and Issues: None
Page 25
Page 26
Actors: Front desk Personnel, Administrator, Patient Description: In this the patient would be provided with the appointment ordered by the Doctor or by his own wish Preconditions: 1. The patient should be a registered patient. Postconditions: 1. The patient gets a token number and appointment to the doctor Normal Flow: 1. The front desk personnel would search for the patient. 2. The user checks the scheduler and provides appointment. 3. The user may be able to change the appointment if required. 4. The system provides token number to the patient. Alternative Flows: None Exceptions: If the details are wrong then the user would press reset and the details are put again. Includes: It includes SMS to the patient mobile with the appointment details. If the appointment has been changed then also the intimation has to send to the patient. Priority: *** Frequency of Use: Same front desk officials. From 8 am to 8 pm Special Requirements: The system should generate a token no and save it in the same patient database. Assumptions: The OPD on an average has 500 patients daily. Notes and Issues: The appointment cant be provided for the previous day. No downtime for the system more than 10 minutes.
Page 27
Page 28
Actors: Website, Patient Description: Patient will get the appointment online for the doctor Preconditions: 1. The patient should be first registered to the hospital online. Postconditions: 1. The patient gets an appointment with the token number. Normal Flow: 1. Patient visits the website and register by entering the details into the registration field provided. 2. Website checks the scheduler and provides the appointment to the patient. 3. System generates the token number for the patient. 4. The patient can take the print if he/she wants to have a hard copy of the appointment with details Alternative Flows: If the patient is an old patient then he/she wont have to register again. The website would have two options one for new patient and other for old patient. Directly the system would generate the token number and appointment details. Exceptions: Reset of the information is provided if the patient details fed are wrong. The patient might only register but not take appointment, and then the token number is not to be generated. Includes: Send the appointment details to the mobile number if provided. Priority: *** Frequency of Use: 24 Hrs Users cant say. At a time 1000 might be there. Special Requirements: The website is to be integrated with the system. Website URL: www.abchospitals.com Assumptions: None Notes and Issues: Do not generate UID for the patient if the patient is registering for the first time.
Page 29
Page 30
Actors: Administrator, Billing Personnel, Patient Description: The system generates a bill for the patient so that the patient can pay for the consultation charges before the consultation. This is also used for providing bill for other services like radiology, lab, pharmacy etc. Preconditions: 1. The billing personnel should be logged into the system. 2. The patient should have done his/her registration. Postconditions: 1. Bill is been provided to the patient and cash is been collected. 2. OPD card is generated if going for consultation Normal Flow: 1. Search patient from the UID provided to the patient. 2. Save the bill accordingly as per the services is to be provided. 3. Print and authorize the bill Alternative Flows: If the patient is coming for the billing of other services then only the bill for the services is been saved for that UID and print is given to the patient. Exceptions: If the details are for other patient (wrong UID) then the reset option is there. The user can update/cancel the bill if required. Includes: Printing of OPD card if going for consultation Priority: *** Frequency of Use: 24 hrs. Peak time is between 8 am to 8 pm by max 10 users Special Requirements: The user should be able to add some text if required and there should be option of bill update/change in the system. Assumptions: When the bill details are saved it is assumed that the money has been taken from the patient. Notes and Issues: The administrator has the only right to change the saved bill in the back end if required.
Page 31
Page 32
Actors: Medical Assistant, Administrator, Patient Description: The system is use to manage the long queues by displaying the token numbers outside the consultant room. Preconditions: 1. The patient has taken an appointment and has a token number with him/her. Postconditions: 1. The patient is called and doctor gives consultation. Normal Flow: 1. The token number is displayed and the patient with that token number comes into the room. 2. Medical assistant press the counter button leading to display of next token number. 3. Next token number is displayed and the patient comes inside the consultant room. Alternative Flows: Null Exceptions: If the patient with the token number has not turned up for the day then the administrator shall be able to assign the token number to any other patient. Includes: Report generated at the end of the day. Priority: *** Frequency of Use: OPD hours. 10 users Special Requirements: System should automatically redirect the token number assigned to that consultation room. Eg: If 2435 and 2523 is assigned to room no 102 then after 2435 the display should show 2523 not 2436. Assumptions: The hospital has displays installed at the entrance of the consultants room. Notes and Issues: The average OPD consultation time is 10 minutes (Observation).
Page 33
Request Description
Justification
Alternative Solutions
1.
2.
3.
Page 34
Option 1
Option 2
Option 3
Schedule
Effort
Cost
Recommendation
Authorization
Action: Authorized By: Date:
Page 35