Software Requirement OPD Management

SRS Document OPD Management System

Nitin Prasher (PG/10/027), Anindam Basu (PG/10/005) Page 1

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)



Index

S.No. Topic Name Page Number

1. Introduction 3

1.1 Purpose 3

1.2 Scope of the work 4

1.3 Abbreviations Used 5

1.4 Overview 5

1.5 Manual Workflow 6

2. General Perspectives 7

2.1 Product Perspective 7

2.2 Stakeholders 7

2.3 Product Functions 8

2.4 General Constraints 9

2.5 Assumptions and Dependencies 9

3 Specific Requirements 10

3.1 Functional Requirements 10

3.2 Non Functional Requirements 13

4 Traceability Matrix 15

5 Appendix 16

5.1 Interview Question to the OPD Administrator

17

5.2 Focus Group Discussion with Other Users 18

5.3 Overview of the System 19

5.4 Overall OPD Management System & its Users

20

5.5 Use Cases 21

5.5.1 Patient Registration 22

5.5.2 Doctor’s Schedule 23

5.5.3 Patient Appointment 26

5.5.4 Patient Online Registration and Appointment

28

5.5.5 Generate Bill 30

5.5.6 Manage Patient Queue 32

6 Change Request Form 34



1. Introduction

ABC hospital is a state of art 300 bedded multispecialty hospital which is situated in Delhi

which was open to public on 1st January 2011. The hospital has specialties which comprises of

Cardiology, Neurology, Orthopedics, General Medicine, Nephrology, Pediatrics, Gynecology

and many more (Source: www.abchospital.com). The hospital is having an Outpatient

Department with an average of 500 patients per day to visit to the consultants present in the

hospital. The hospital is having totally manual based system which comprises of registering the

patient, Bill payment, providing appointment to the patient etc. The hospital is facing a

problem of longer queues in the OPD, more of the manual records, increased waiting time of

the patient and sometime cancellation of the appointment after the patient arrives to the

hospital. This has lead to less patient satisfaction and increase in paperwork (leading to

misplacing of the records from the records room). Also the hospital management seems a very

daunting task to find out the exact numbers to get out with some inferences so that it leads to

increase in efficiency and effectiveness of the hospital.

Another major problem that the hospital is facing that due to manual records, it has lead to less

accountability of the different staff present in the OPD. Whether it is front desk personnel or

billing personnel, the more of manual work and handling more papers is not a easy task and

therefore, it leads to staff doesn’t take any responsibility for the work which is carried out extra

due to the manual process (paperwork). It has lead only to increase in consumption of

stationery and space in the hospital (for storage).

1.1 Purpose

The purpose of this document is to convey information about the application’s requirements,

both functional and nonfunctional of the Outpatient Management System for ABC

multispecialty hospital. It describes the functions, goals and task the system can perform.

Software Development Team (SDT) would use this document to describe the scope of the

project and to plan for the system’s design and eventual implementation. SDT should consult

this document and its revisions as the only source of requirements for the project. They should

not consider any requirement statements, written or verbal until they appear in this document

or its revision. It would also serve as a legal document to protect the interests of the solution

providers once the requirements have been established.

This document is not only for the SDT’s but is intended to several groups which are as follows:

http://www.abchospital.com/



The hospital management and its team members should use this document and its

revisions as primary means to communicate confirmed requirements to the SDT. The

SRS will serve to establish a basis for agreement between the client and development

team about the functionality to be provided by the application.

The project manager will use this document during project planning and monitoring.

Application managers will review the document to clarity their understanding of what

the application does.

Test planners will use the document to clarity their understanding of what the

application does.

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 doctor’s

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.




The project client has determined that the application will provide the following benefits:

1) Provide patient satisfaction by reducing the waiting time and also providing the

appointment to the patient online.

2) Help the hospital staff to manage the queue of the patient in the OPD.

3) Reducing the paperwork (registration and billing).

4) Provide with the facility to easily search and take reports about the day to day

operations and leading to more efficient and effective providing of services to the

patient coming to the OPD for the consultation.

1.3 abbreviations used

OPD: Outpatient Department

SDT: Software Development Team

UID: Unique Identification Number

SMS: Short Message Service

GUI: Graphical User Interface

SRS: System/Software Requirement Specifications

HTML: Hypertext Markup Language

1.4 Overview

The SRS document tells about how the system will work and tells about the OPD management

system requirements as a whole. Section 2 of the document provides an overview of the

business domain that the proposed OPD management system will support. These include a

general description of the product, user characteristics, general constraints, and any

assumptions for this system.

Section 3 represents the entire functional and non functional requirement that the client has

provided for the system to actually do for the hospital. Section 4 tells about the traceability

matrix for the functional requirement of the system. Section 5 comprises of annexure where it

comprises of the Requirement Tools used for gathering requirement, Overall system diagram,

Use case Scenario etc. Section 6 comprises of the change request form if the client wants to

change something in the requirement which will be added up in the next version of the SRS.



1.5 manual workflow

Patient arrives at the hospital for

OPD consultation

Patient goes to the front desk

for the registration/

appointment

Patient goes to the Billing

counter for the

preconsultation billing

Patient goes to the doctor for OPD

consultation

If patient is an

old patient

If doctor has ordered

some procedures/

medication

Yes

No

Yes

Goes to billing counter for

Billing of the procedures

Goes for procedure to the

department or pharmacy

If ordered

revisitYes

No

Patient goes out of the

hospital

No



2 general perspectives

2.1 Product perspective

The OPD Management system is a self contained system that manages activities of the

Outpatient Department of the hospital which includes the patient registration, providing

appointment, billing for the patient and also managing queue of the patients during the OPD

hours. The system also provides the reports and analysis for the administrator which helps

them in decision making. The System would have the following stakeholders using the system

directly and indirectly.

2.2 stakeholders

The stakeholders and their characteristics are as follows:

1) Patient: He/ She is a person coming to the hospital for any consultation from the doctor

present during the OPD hours. The patient will not be a direct user of the system but

the system is majorly been used for individual patient records in the database. The

system will get the input from the patient and some of the outputs is provided to the

patient.

2) Front Desk Personnel: They all have general reception duties. Every staff has basic

computer training. They are responsible for taking the patient information from the

patient and entering the information in the system. They also are providing the

appointments to the patient if the patient requires any further visit to the doctor if

ordered. They are directly interacting with the system.

3) Billing Personnel: They all have the duties of general cashier to collect money from the

patient for the various services in the OPD which includes payment of preconsultation

billing and billing for the other services like Radiology, Lab Investigation and other

medication charges. They are also using the system directly for billing purposes.

4) Doctor: All doctors have a medical degree. Some have further specialized training and are

computer literate. Doctors will use the OPD Management System to upload their schedule in

excel format so that the appointment can be given to the patient.

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



medical assistant will use the system directly to call the next patient by pressing the

counter button.

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.



6) Report Generation: The system generates the reports as per of the Administrator option

selection. Like they can see the daily/ weekly/ monthly/yearly census, department wise

census etc.

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.




3 Specific Requirements

3.1 Functional Requirements

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.

Consultant’s 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.



OPF009 Reminder**

The system shall allow the administrator to send reminders to the consultants about the

scheduler updating by the doctor monthly/weekly as needed.

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.



OPF019 Bill Change

The user should be allowed change the final bill if necessary. There should be a free

text provided so that can be used by the billing department whenever necessary.

OPF020 OPD Card Print

The system should be able to provide print out of the OPD card for the patient which

consisting of Patient Name, UID, Token Number, Mobile Number, Age, Address in the

OPD card.

OPF021 Price changes***

The system should allow the billing personnel to update the prices details of the

different services if they are changed by the management.

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**



The administrator shall be able to update any information in the database.

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.



OPNF010 Back Up***

System shall provide the capability to back up data.

OPNF011 Down Time***

The system should not have a down time more than 10 minutes.

OPNF012 Error***

The system shall keep a log of all the error which might have been done by the users

during the usage.

OPNF013 Demo**

The system shall provide a demo of the different options and how does the system work.

OPNF014 Reliability***

The system shall be available working 24 hrs and especially from 8 am to 8 pm (OPD

timings).

OPNF015 Graphical User Interface**

The system should have a Graphic User Interface so that it becomes very easy for any

user to learn it and also decreases the time to finish any operation.

OPNF016 Interoperability***

The system should have the capability to be integrated with the system for future.



4. Traceability matrix

Requirement ID Name of Requirement

Module Name/ Requirement Description

Priority

OPF001 Patient Details Registration High OPF002 Register New Patient Registration High OPF003 Generate UID Registration High OPF004 Patient Search Registration High OPF005 Revisit of Old Patients Registration Medium OPF006 Assign Consultant

Room Registration High

OPF007 Upload Scheduler Appointment High OPF008 Change/Update

Scheduler Appointment High

OPF009 Reminder Appointment Medium OPF010 Appointment to the

patient Appointment High

OPF011 Appointment Details Appointment High OPF012 Generate Token

Number Appointment High

OPF013 Telephonic Appointment

Appointment Low

OPF014 SMS to the patient Appointment Low OPF015 Appointment Update Appointment High OPF016 Token Assign Appointment Medium OPF017 Patient Bill Billing High OPF018 Bill Print Billing High OPF019 Bill Change Billing Medium OPF020 OPD Card Print Billing Low OPF021 Price Changes Billing High OPF022 Display Token

Number Queue Management High

OPF023 Redirect Token Number

Queue Management High

OPF024 Call the patient Queue Management High OPF025 Staff Information Database High OPF026 Reset Information Database High OPF027 Employee Search Database Medium OPF028 Update Employee

Information Database Medium

OPF029 Periodic Reports Reports High OPF030 Analysis Reports High



Appendix



5.1 Interview questions to the opd administrator

Q1. What is the current workflow been followed in the hospital’s outpatient

department?

Q2. What all are the problems you are facing in the manual system/ process you

are following?

Q3. What are the basic requirements that you are expecting from the

computerized system?

Q4. How many users are going to use this system in the Outpatient Department?

Q5. Do you want to have any super user for this system who would be the person

we have to report after the completion of this project?

Q6. Any system other than manual process you are using for your hospital

especially?

Q7. Any future plans you are having for your hospital in which this system

would be integrated?

Q8. What are your expectations from this system?



5.2 Focus group discussion questions to the other users

Q1. In the hospital the patient is first registered. What is the process you are

following? Do you have any kind of Registration form for the same?

Q2. How do you come to know that the patient coming is a new patient or a

follow up patient? Do you provide any unique number to different patients?

Q3. How do you make sure that the patient doesn’t go to the doctor without

paying the pre consultation payment in the billing counter?

Q4. In an average, how many patients do you cater during your OPD hours

daily? What are the OPD timings?

Q5. What are the methods in which the patients get appointment for the doctor

in an OPD? Is this same for both New and Old patients.

Q6. What are the major problems according to you does the staff is facing during

OPD hours?

Q7. How do you cater the large queues in the department? Is there any process

been followed?

Q8. On an average how many minutes does a doctor take for a consultation?

Q9. How do you charge a patient if doctor orders for a procedures/ medication?

Q10. If there is change in the appointment schedule, then how do you intimate

the patient?

Q11. What are the expectations from the system that is going to be implemented

in the OPD department?



5.3 Overview of the system

OPD MANAGEMENT SYSTEM

Registration

System

Appointment

System

Billing System Queue

Management

System

Online

System

Offline

System

Online

System

Offline

System



5.4. The overall opd management system & its users



5.5 Use cases

Actors Use Cases

Front Desk Personnel, Patient Patient Registration

Doctor, Administrator Upload Scheduler

Front Desk Personnel, Administrator, Patient Patient Appointment

Website, Patient Patient Online Appointment and Registration

Billing Personnel, Administrator, Patient Generate Bill

Medical Assistant, Administrator, Patient Manage Queue



5.5.1 UC01 Patient registration



Use Case ID: UC01

Use Case Name: Patient Registration

Created By: Anindam, Nitin Last Updated By: Anindam, Nitin

Date Created: 5th September 2011 Date Last

Updated:

6th September 2011

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. Front Desk is logged into the system. 2. The patient has arrived to the front desk

Postconditions: 1. The patient gets a Print Out with Registration Details. 2. Patient gets a UID number.

Normal Flow: 1. Patient arrives at the front desk counter. 2. Demographic details are taken 3. System generates a UID for the patient. 4. The details are saved for the patient. 5. Print out is given out to the patient. 6. Consultation room is assigned.

Alternative Flows: 1. 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 can’t be done for the patient on previous

date.



5.5.2 uc02 doctor’s scheduler



Use Case ID: UC02

Use Case Name: Doctor’s Scheduler



Updated:

6th September 2011

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



5.5.3 Uc03 patient appointment



Use Case ID: UC03

Use Case Name: Patient Appointment



Updated:

6th September 2011

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 can’t be provided for the previous day.

No downtime for the system more than 10 minutes.



5.5.4 Uc04 patient online registration and appointment



Use Case ID: UC04

Use Case Name: Patient Online Registration & Appointment


Date Created: 5th September 2011 Date Last Updated: 6th September 2011

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 won’t 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 can’t 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.

http://www.abchospitals.com/



5.5.5 uc05 Generate bill



Use Case ID: UC05

Use Case Name: Generate Bill

Created By: Nitin, Anindam Last Updated By: Nitin, Anindam


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.



5.5.6 uc06 Manage patient queue



Use Case ID: UC06

Use Case Name: Manage Patient Queue

Created By: Nitin, Anindam Last Updated By: Nitin, Anindam


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

consultant’s room.

Notes and Issues: The average OPD consultation time is 10 minutes

(Observation).



6. Change Request Form Abc hospital

Request No: Request

Date:

Request Title: Status:

Originator's Name: Phone/Email

/Mailstop:

Sponsor's Name: Priority:

Assigned To: Response

Date:

Request Description

Justification

Alternative Solutions

1.

2.

3.



Impact Assessment

Impacts Option 1 Option 2 Option 3

Functional

Scope

Schedule

Effort

Cost

Recommendation

Authorization

Action: Authorized By: Date:

Software Requirement OPD Management

Documents

front desk

nitin date

anindam date

opd management

front desk

alternative

normal flow

outpatient