Requirement Specification

Software Requirements Specification
For e-Health Solution for ETU at Colombo South
Teaching Hospital
Version 1.0
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
Revision History
Date
Version
Description
Author
05/11/2010
1.0
First version
Group 22
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
i
Table of Contents
Table of Contents i
1. INTRODUCTION 1
1.1 Purpose 1
1.2 Scope 1
1.3 Document Conventions 2
1.4 Definitions, Acronyms, and Abbreviations 2
1.5 References 2
1.6 Overview 2
2. OVERALL DESCRIPTION 3
2.1 Product Perspective 3
2.2 Product Features 5
2.3 User Classes and Characteristics 5
2.4 Operating Environment 6
2.5 Constraints 6
3. SYSTEM FEATURES 7
3.1 System Administration and Common User Functions 7
3.2 Patient Registration and Electronic Health Records (EHR) 11
3.3 Investigations and Results 18
3.4 Support Services Management 21
3.5 Supply Chain Management 26
3.6 Death Certification 30
4. SPECIFIC REQUIREMENTS 34
4.1 Usability 34
4.2 Reliability and Availability 34
4.3 Performance 34
4.4 Supportability 35
4.5 Design Constraints 35
4.6 On-line User Documentation and Help System Requirements 35
4.7 Interfaces 35
4.7.1 User Interfaces 35
4.7.2 Software Interfaces 37
4.7.3 Communications Interfaces 38
4.8 Applicable Standards 38
4.9 Software Quality Attributes 38
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
ii
Table of Figures
Figure 2.1 – The Ripple Effect expansion of the project ................................................................. 3
Figure 2.2 - Interaction of e-Arogya with other systems ................................................................ 4
Figure 2.3 – User Classes Hierarchy ................................................................................................ 6
Figure 4.1 - Page Navigation Details (Menu Level 1) .................................................................... 36
Figure 4.2 - Page Navigation Details-System Admin (Menu Level 2) ........................................... 36
Figure 4.3 - Page Navigation Details- Patient Registration & EHR (Menu Level 2) ...................... 36
Figure 4.4 - Page Navigation Details-Investigation & Results (Menu Level 2, 3 and 4) ................ 36
Figure 4.5 - Page Navigation Details- Supply Chain (Menu Level 2 and 3) ................................... 37
Figure 4.6 - Page Navigation Details - Support Service (Menu Level 2 and 3) ............................. 37
Figure 4.7 - Page Navigation Details -Death Certification version (Menu Level 2 and 3) ............ 37
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
1
1. INTRODUCTION
The famous saying, "Arogya Parama Laaba" means that the health is wealth. A healthy population increases the productivity of a country by a great proportion. Therefore any country provides an effective health care system to their citizens. Some countries like Sri Lanka, provides free health care services at government hospitals. At present, e-Health is a leading topic in the ICT industry. It aims to deliver efficient health care services to the community. This new technology is commenced by the ICT and health care institutions. Now e-Health solution for health care institutions is available in worldwide. Unfortunately this solution is not available in Sri Lanka yet due to many reasons such as financial problems and social problems. Therefore we mainly target to develop e-Health solution as our final year project. This solution should provide the effective health care system for ETU of the Colombo South Teaching Hospital. Later it should be expanded to the other departments of the hospital as well as for the other hospitals of Sri Lanka as a ripple effect. The System Requirements Specification (SRS) document provides an overview of the entire System Requirements Specifications of the project. In addition to the SRS, it also includes the purpose, scope, definitions, acronyms, abbreviations and references.
1.1 Purpose
The main purpose of this document is to collect, analyze and define the basic requirements of 'e-Arogya', the e-health solution for ETU at Colombo South Teaching Hospital. Here we focus on functional and non-functional requirements of the entire system. The capabilities needed by the stakeholders, targeted users the reason for the existence of such needs will further be discussed. The details of how this system fulfills these needs are also detailed in the latter parts of the document.
1.2 Scope
The objectives of this project is to develop a software system which can be used to provide an effective healthcare services to the Sri Lankan community by utilizing the available limited resources in an efficient and effective manner. This system will be developed based on the research carried out by Dr. Mudith Karunathilake and Dr. Shahani Weerawarne on ‘business process re-engineering for the Emergency Treatment Unit at the Colombo South Teaching hospital’. Also we mainly focus to achieve the following targets to the ETU
 To provide efficient patient care services.
 To develop an easy patient tracking system.
 To manage the medical records with efficient retrieving and single registration number.
 To eliminate unnecessary wastage of drugs, surgical items and meals.
 To facilitate human resource management more efficiency and productivity.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
2
1.3 Document Conventions
The following font styles are used in this document:
 Major Headings – 18 pt, Arial, Bold
 Sub Headings – 12 pt, Arial, Bold
 Other Headings – 10 pt, Arial, Bold
 All other text – 12 pt, Calibri(body)
1.4 Definitions, Acronyms, and Abbreviations
 ICT - Information & Communication Technology
 ETU - Emergency Treatment Unit
 SRS - Software Requirement Specification
 RUP- Rational Unified Process
 API – Application Programming Interface
 LAN – Local Area Network
 BHT - Bed Head Ticket
 EHR - Electronic Health Records
 JMO - Judicial Medical Officer
 SMS – Short Message Service
 ICU – Intensive Care Unit
1.5 References
 RUP template
 Final thesis on "business process re-engineering for the emergency treatment unit of Colombo south teaching hospital" by Karunathilaka M.N. on 2009
1.6 Overview
Rest of the document is organized in the following manner providing the overall description and the requirements of the 'e-Arogya' project. The 2nd chapter of this document gives an overall description of the entire project. It describes the product perspective, product features, user classes and characteristics, operating environment, constraints, assumptions and dependencies of the system. Chapter 3 of this document discusses the system features in a more detailed manner. Chapter 4 consists of the specific requirements of the project and it details the requirements such as usability, reliability and availability, performance, supportability, design constraints, online user documentation and help system, interfaces and software quality attributes.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
3
2. OVERALL DESCRIPTION
2.1 Product Perspective
The e-Arogya system is a software system that deals with managing all the clinical processes of the ETU of the Colombo south teaching hospital. At the moment the product will manage only the clinical processes of the ETU. Since ETU doesn’t work independently it requires interacting with the other sections of the hospital as well as with the other government organizations. This interaction is described in Figure 2.2. In Future this will be expanded to other departments of the hospital and later to other hospitals in Sri Lanka like a ripple effect. This concept is illustrated in Figure 2.1. When the system is used to manage all the hospitals in Sri Lanka, it will allow all the hospitals to work as a single unit. Therefore the efficiency of the health service will be increased.
Figure 2.1 – The Ripple Effect expansion of the project
Other Hospitals
Other departments
ETU
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
4
Figure 2.2 - Interaction of e-Arogya with other systems
e-Arogya
SMS Gateway
Other Departments of the Hospital
Administrations
Wards
Admission Room
Admitting Officer
Laboratory
Radiology Department
Pharmacy
Police Post
Judicial Medical Officer’s Office
ICU
Transport Unit
Telephone Exchange
Other Government Organizations
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
5
2.2 Product Features
Product Features of this system can be described under following six main categories.
1. Patient Registration and Electronic Health records(EHR)-
From the point of any individual admission, to the point of discharge or death document management is done through this process. This process should also include health record management. At the first admission every patient gets a registration number which is unique to him and in repeated admissions can use it, to retrieve health records efficiently in order to deliver quality care.
2. Investigations and results
From the point of ordering an investigation to receive confirmation of samples and the result availability managed through this process. The results were ultimately incorporated to the electronic health records automatically, for storage and easy dynamic retrieving.
3. Supply Chain Management
Ordering drugs, surgical items and any other stores item is manage through this process. Ultimate objective of the process is dynamic supply of items without ETU involvement.
4. Support Service management
From the request of a service to the completion of the task is managed through this core process. With the trend of outsourcing non-core services supervision too, is enabled through this process effectively.
5. Death Certification
From the point of death certification, to the issue of the death certificate is managed through this core process. The medico legal process too can be incorporated to this process in future when extended to other wards and units.
6. User privileges management
There are few user classes identified in ETU. Each user class should have separate privileges depending on the services provided by them. Therefore the system should provide an easy way of managing these user classes and their privileges.
2.3 User Classes and Characteristics
The users of this system are basically the employees of the ETU. According to the type of employment, access privileges to the system functions should vary. The owners of the overall system are Director and the Deputy Director IT. Five major user classes can be identified as Administration, Laboratory, Supply, Support Services and Death Certification. Each user class has a deputy Director as the administrator and various sub user classes can be identified under each user class. Sub user classes identified in the system are illustrated in Figure 2.3 according to the different user classes.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
6
2.4 Operating Environment
The system should be able to operate in an environment with very limited facilities. It should be able to run in a normal pc with limited memory and processing power. The system should be platform independent. Any person with basic computer knowledge should be able to use the system with small amount of training. These users should be able to install the system without any help from a technical person. When this system is expanded to all the hospitals in Sri Lanka all the hospitals should be managed as a single unit. Therefore there should be a central database which will facilitate to access medical records of any patient at any hospital once he/she has registered in the system.
2.5 Constraints
Since this system has lots of features that can be implemented, time is the major constraints. The end users may not have a very good knowledge on computers. Therefore the system should be very simple with a very user friendly interface. Since this system is developed for government hospitals it should be deployed and maintained with low cost. The proposed system requires an SMS gateway to send alerts to different parties. An SMS gateway which is freely available or available for low cost has to be found according to the budget.
Figure 2.3 – User Classes Hierarchy
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
7
3. SYSTEM FEATURES
Product Features of this system can be described under following main categories.
 System Administration and Common User Functions
 Patient Registration and Electronic Health records(EHR)
 Investigations and results
 Supply Chain Management
 Support Service management
 Death Certification
Each of these categories have different features that are, when combined together provide the total functionalities provided by the ETU.
3.1 System Administration and Common User Functions
This category contains use cases on creating user classes, change user class privileges, create users, add users to user classes, view log history and other common use cases such as login and change password.
Use case name
UC 1 : Login
Overview
This use case enables the users to login to the system based on the privileges defined.
Actor
Director, Deputy Director ,Deputy Director IT, Deputy Director Administration, Deputy Director Supply, Deputy Director Laboratory, Deputy Director Support Service, Specialist, Doctor, Nurse, MRO, Admission counter officer, Admitting officer, Coroner, Head of Hospital Police Post, JMO, Clerk, Overseer, Store Manager, Store Keeper, Pharmacist, Pathologist, Microbiologist, Hematologist, MLT, In charge of Ambulance, In charge of Cleaning, In charge of Meals
Pre-Conditions
The user should have been added to the system by an administrator.
Flow of events
Basic Flow
 User should enter user name and password.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
8
 Verify username and password with the database.
 Enter details to system log.
Terminating Outcome
 If correct navigate user to home page.
 Else display error message.
Use case name
UC2 : Add or Change user classes
Overview
This use case enables the administrator to add new user classes.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Deputy Director Supply, Deputy Director Laboratory, Deputy Director Support Service
Pre-conditions
 User should have logged in as administrator
Flow of events
Basic Flow
 User should enter details and create a new user class.
 Define privileges to the user class.
 New user class details should be stored in the database.
 Enter details to system log.
Terminating Outcome
 New user class created.
 If there are any error in the details entered, display and error message and prompt the user to enter details again.
Use case name
UC3 : Add new user
Overview
This user class enables to add a new user to the system.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Deputy
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
9
Director Supply, Deputy Director Laboratory, Deputy Director Support Service
Pre-conditions
 User should have logged in login as administrator
Flow of events
Basic Flow
 Enter details of the new user.
 Define a user class to the user.
 Details of the new user should be stored in the database.
 Enter details to system log.
Terminating Outcome
 New user added to the system.
 If there are any error in the details entered, display and error message and prompt the user to enter details again.
Use case name
UC4 : Change User Class
Overview
This use case enables the administrators of a given user class to change an assigned user class of a user.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Deputy Director Supply, Deputy Director Laboratory, Deputy Director Support Service
Pre-conditions
 User should have logged in login as an administrator
 The given user class should have been created.
 The given user should have been added to the system.
Flow of events
Basic Flow
 Select the user class.
 Display users already assigned to the user class.
 Search for the required user.
 Add or Remove the user from the user
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
10
class.
 Enter details to system log.
Terminating Outcome
 Database successfully updated.
 If there are any error in the details entered, display and error message and prompt the user to enter details again.
Use case name
UC5 : View system log
Overview
This use class enables the user to view the system log for a given time frame.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Deputy Director Supply, Deputy Director Laboratory, Deputy Director Support Service
Pre-conditions
 User should have logged in as an administrator
Flow of events
Basic Flow
 The user should enter a time frame.
 Retrieve log details for the given time frame from the database.
Terminating Outcome
 Display retrieved data to the user.
 If the given time frame is invalid display an error message and prompt the user to enter again.
Use case name
UC6 : Change password
Overview
This use case enables the user to change their password.
Actor
All users
Pre-conditions
 The user should have logged in their own account.
Flow of events
Basic Flow
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
11
 User should enter their old password.
 The user should enter the new password twice.
 Confirm that the new password is entered correctly.
 Confirm the old password with the database.
 Change the password field in the database.
 Enter details to system log.
Terminating Outcome
 If the required information is not valid display an error message and prompt the user to enter details again.
 If password change is successful display a message to the user.
3.2 Patient Registration and Electronic Health Records (EHR)
All the patient details and their medical history fall under this category. System features under this category can be described from following use cases.
Use case name
UC7 : Register New Patient
Overview
This use case allows users to enter a new patient to the system
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Admission Counter Officer
Pre-conditions
 Admission counter officer should have logged in to the system
Flow of events
Basic Flow
 Search if the patient already exists in the system.
 Enter details and create a new account
 Enter details to the database
 Enter details to system log.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
12
Terminating Outcome
 Patient successfully entered to the system.
Post-Conditions
Use case name
UC8 : Initial Diagnosis
Overview
This use case allows users to find medical history of a patient if available and make the initial diagnosis
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Admitting Officer
Pre-conditions
 The user should have logged in to the system
Flow of events
Basic Flow
 Search for the patient.
 If patient is already in the system view medical history.
 Enter the initial diagnosis.
 Enter details to system log.
Terminating Outcome
 Initial diagnosis successfully entered to the system.
 If patient does not exist in the system follow UC7
Post-Conditions
 Transfer patient to ETU/ICU/ward
Use case name
UC9 : Search a Patient
Overview
This use case allows users to search for a patient using the patient’s name, health record id, national id or birthday.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, All users under Deputy Director Administration
Pre-conditions
 The user should log in to the system.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
13
Flow of events
Basic Flow
 Enter the name, heath record id, national id or birthday.
 Select the category from the drop down list.
 Search using search button
 Query the database using given details
Terminating Outcome
 Display search results
Use case name
UC10 : View Patient Details
Overview
This use case allows users to view details of the particular patient.
Actor
Director, Deputy Director ,Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse, MRO, Admission counter officer, Admitting officer
Pre-conditions
 The given patient should exist in the system
 The user should log in to the system.
Flow of events
Basic Flow
 Follow UC9.
 Select the person from the search results list.
 Query the database to get the required details.
Terminating Outcome
 Display the details of the required patient.
Post-Conditions
Use case name
UC11 : View Medical Records
Overview
This use case allows users to view medical records of a particular patient.
Actor
Director, Deputy Director ,Deputy Director IT,
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
14
Deputy Director Administration, Specialist, Doctor, Nurse, MRO, Admitting officer
Pre-conditions
 The given patient should exist in the system
 The user should log in to the system.
Flow of events
Basic Flow
 Follow UC9.
 Select the person from the search results list.
 Query the database to get the required details.
 Enter details to system log.
Terminating Outcome
 Display the medical history of the selected patient.
Post-Conditions
 If required add new medical notes.
Use case name
UC12 : Edit Patient Details
Overview
This use case allows users to edit patient details.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Admission Counter Officer
Pre-conditions
● The user should log in to the system
● The patient should have already entered to the system.
Flow of events
Basic Flow
● Follow UC9
● Select the required patient from the search results list.
● Edit details.
● Update the database.
● Enter details to system log.
Terminating Outcome
● Patient’s details edited.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
15
Post-Conditions
Use case name
UC13 : Add Medical Records
Overview
This use case allows users to add medical records of a given patient.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Admitting Officer, MRO
Pre-conditions
● The user should log in to the system.
● The user should have the required privileges.
● The patient should have been already entered to the system.
Flow of events
Basic Flow
● Follow UC9
● Selected the required patient from the search results list.
● Enter medical records.
● Save medical records in the database with the patient’s health id, date and the identification of the user.
● Enter details to system log.
Terminating Outcome
● New medical record of the patient with the date the record entered.
Post-Conditions
Use case name
UC14 : Patient Transfer
Overview
This use case allows user to transfer patient to a ward or ICU.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, MRO, Doctor, Specialist
Pre-conditions
● The user should log in to the system.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
16
● The patient should have already entered to the system.
● The patient should have been already assigned to a ward, ICU or ETU.
Flow of events
Basic Flow
● If required follow CU9.
● Select the patient.
● Enter transfer details.
● Update the database regarding patient’s details.
● Add the patient to the new ward patient list in database.
● Remove the patient from the current ward patient list in database.
● Enter details to system log.
Terminating Outcome
● Patient removed from the list of patients in the current ward.
● Patient added to the list of patients in the new ward.
Post-Conditions
Use case name
UC15 : Discharge a patient
Overview
This use case allows a user to discharge a patient from the hospital.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, MRO, Doctor, Nurse
Pre-conditions
● The user should log in to the system.
● The patient should have already been added to the system.
● The patient should belong to a ward, ICU or ETU.
Flow of events
Basic Flow
● Follow UC9 if required.
● Select the patient from the list of patients
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
17
in the current ward.
● Enter final entry in the medical records if required.(UC 13)
● Mark patient as discharged.
● Remove patient from the list of patient in the current ward.
● Update the database.
● Enter details to system log.
Terminating Outcome
● Patient is marked as discharged and removed from the list of patients in the ward.
Post-Conditions
● Terminate the online accessibility to the patient’s health records from irrelevant sites.
Use case name
UC16 : Give Drugs to a patient
Overview
This use case allows users to record drugs given to patients in the hospital.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse
Pre-conditions
● The user should log in to the system.
● The patient should have been already entered to the system.
Flow of events
Basic Flow
● If required follow UC9.
● Enter drugs and the quantity given to the patient.
● Update database.
● Reduce the quantity from the local (ETU) store database.
● Enter details to system log.
Terminating Outcome
● View details of the drugs given to the patient.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
18
Post-Conditions
Use case name
UC17 : Give Clinical Items
Overview
This use case allows users to record clinical items used on a patient.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse
Pre-conditions
● The user should log in to the system.
● The patient should have been already entered to the system.
Flow of events
Basic Flow
● If required follow UC9.
● Enter clinical item and the quantity given to the patient.
● Update database.
● Reduce the quantity from the local (ETU) store database.
● Enter details to system log.
Terminating Outcome
● View details of the clinical items used on the patient.
Post-Conditions
3.3 Investigations and Results
In medicine different investigations are used to diagnose a patient. This feature category handles different parts of the investigation process. A doctor or any other authorized person can order an investigation for a given patient.
Use case name
UC18 : Request Investigation
Overview
This use case allows user to request an investigation on behalf a patient.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
19
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse
Pre-conditions
● The user should log in to the system.
● The patient should have been already entered to the system.
Flow of events
Basic Flow
● If required follow UC9.
● View list of current patients in the ward/ ICU/ ETU.
● Select the required patient.
● Enter investigation request with the investigation type and sample ID.
● Update the database.
● Enter details to system log.
Terminating Outcome
● Requesting an investigation for the given patient.
Post-Conditions
● Send the sample to the relevant laboratory.
Use case name
UC19 : View Requested Investigations
Overview
This use case allows user to view the list of requested investigation with the patient’s ID based on the laboratory.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse
Pre-conditions
● The user should log in to the system.
● There should be investigation requests without results received.
● Samples should have been sent to the relevant laboratory.
Flow of events
Basic Flow
● Query the details of the investigation
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
20
requests and the relevant laboratory from the database.
Terminating Outcome
● Display the investigation requests ordered according to the laboratory.
Post-Conditions
● The user should be able to enter investigation results in the relevant request.
Use case name
UC20 : Enter Investigations Results
Overview
This use case allows users to enter the results of the investigations requested.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse
Pre-conditions
● The user should log in to the system.
● The samples should have been delivered to the laboratory.
● The results should have been received from the laboratory.
Flow of events
Basic Flow
● Follow CU19.
● Enter investigation results.
● Update the database.
● Enter details to system log.
Terminating Outcome
● Update and display investigation results in the patient’s profile.
Post-Conditions
Inform the laboratory that the results have been received.
Use case name
UC 21 : Request Ambulance Service
Overview
This use case allows user to record any requests send for Ambulance Service.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
21
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Nurse, Clerk
Pre-conditions
● The user should log in to the system.
Flow of events
Basic Flow
● Send a request for an ambulance via email.
● Update database.
● Enter details to system log.
Terminating Outcome
● Request sent to the ambulance service department.
Post-Conditions
● Confirm ambulance request acceptance.
3.4 Support Services Management
Hospital needs many support services like ambulances, food for patients, cleaning and maintenance, etc. this section handles all these support services. From the request of a service to the completion of the task is managed through this core process.
Use case name
UC 22 : Order Meal
Overview
This use case allows users to order meals required for the patients in the ward/ICU/ETU
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Doctor, Nurse, Clerk
Pre-conditions
● The user should log in to the system.
● There should be patients who require meals in the ward/ETU/ICU.
Flow of events
Basic Flow
● View list of patients currently in the ward/ICU/ETU.
● Assign meal category from the drop down list.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
22
● Submit meals request to the kitchen.
● Update database on each patient’s profile.
● Enter details to system log.
Terminating Outcome
● Kitchen receives a meal request.
Post-Conditions
● Ward/ETU/ICU receives the meal order on-time and updates the system.
Use case name
UC23 : Meal Categories
Overview
This use case allows users to view and enter new meal categories to the system.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Support Service, Specialist, Doctor, Nurse
Pre-conditions
● The user should log in to the system.
Flow of events
Basic Flow
● Display current meal categories.
● Enter meal categories.
● Update database.
● Send request to get the approval from the kitchen.
● Enter details to system log.
Terminating Outcome
● New meal category added to the system.
Post-Conditions
● The kitchen should approve the new meal category.
Use case name
UC24 : Items sent for Laundry
Overview
This use case allows users to enter the details of items sent for laundry.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Nurses, Clerk
Pre-conditions
● User should have logged into the system
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
23
with necessary privileges relevant item should have been added to the system.
Flow of events
Basic Flow
● Select the item category from the list.
● Enter the quantity of sent items and other details.
● Enter data to the database.
● Enter details to system log.
Terminating Outcome
● If successful details added to the system.
● If there are any errors in the input prompt user to enter details again.
Post-Conditions
Send items to the laundry.
Use case name
UC25 : Items Received After Laundry
Overview
This use case allows users to enter details of the received items after laundry.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
● Sent laundry items details should have been added.
Flow of events
Basic Flow
● Select the relevant sent laundry item details.
● Add the quantity and required details of the received items.
● Update the database with received item details.
● Enter details to system log.
Terminating Outcome
● If successful received laundry items details are added to the system.
● If there are any errors in the input prompt the user to re-enter details.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
24
Post-Conditions
Confirm of the received items to the laundry.
Use case name
UC26 : Calculate Cost for Laundry
Overview
This use case allows calculating the cost for the laundry for a selected time period.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
● Laundry items should have been added to the system.
● All the sent and received items details for the selected time period should have been added.
Flow of events
Basic Flow
● Select the laundry time period.
● Get the quantity of sent and received items and the cost for each item category.
● Calculate the cost for each category and the total cost for the selected time period.
● Enter details to system log.
Terminating Outcome
● Display the summary of laundry items and the calculated cost for the selected time period.
Post-Conditions
Use case name
UC27 : Laundry item Types and Costs
Overview
This use case allows users to add new laundry items and the cost for the item.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Support Services, Nurse, Clerk
Pre-conditions
● User should have logged into the system
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
25
with required privileges.
Flow of events
Basic Flow
● User enters the laundry item type details.
● Laundry item type details are added to the database.
● Enter details to system log.
Terminating Outcome
● If successful laundry item type details are added to the system.
● If there are any errors in the input prompt the user to re-enter details.
Post-Conditions
Use case name
UC28 : Request Ward Cleaning
Overview
This use case allows users to enter the details of requests to clean the ETU.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow
● User enters the details of the request to clean the ETU.
● Enter the details to the database.
● Enter details to system log.
Terminating Outcome
● If successful ward cleaning request details are added to the system.
● If there are any errors in the input prompt the user to re-enter details.
Post-Conditions
Send the request to the cleaning section.
Use case name
UC 29 : Cleaning History
Overview
This user class allows users to view the
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
26
history of the cleaning of the ETU for a selected time period.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow
● User selects the time period for which the cleaning history is required.
● Query database to retrieve the required data.
Terminating Outcome
● If entered time period is valid display the details to the user.
● Else prompt the user to enter a valid time period.
Post-Conditions
3.5 Supply Chain Management
A hospital stores drugs, surgical items to deliver an efficient service to patients. Ordering of these items is handled by this category.
Use case name
UC 30: Check Available Clinical Items
Overview
This use case allows users to check the available quantity of clinical items in the ETU.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow
● Retrieve the data from the database.
Terminating Outcome
● Display the available clinical items details
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
27
to the user.
Post-Conditions
Use case name
UC 31 : Order Clinical Items
Overview
This use case allows users to order new clinical items from the stores.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
● The clinical item type should have added to the system.
● Enter details to system log.
Flow of events
Basic Flow
● System calculate the required quantity of items based on the past data and displays to the user.
● User can edit the quantity of required clinical items if necessary.
● Enter the order quantity to the database.
Terminating Outcome
● If successful clinical items order details are added to the system.
● If there are any errors in the input prompt the user to re-enter details.
Post-Conditions
Send the order to the relevant store.
Use case name
UC 32 : Add New Clinical Item types
Overview
This use case allows users to enter new clinical item types to the system.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Supply, Specialist, Doctor, Nurse, Clerk
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
28
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow
● User enters details of the new clinical item type.
● Enter the details to the database.
● Enter details to system log.
Terminating Outcome
● If successful new clinical item type details are added to the system.
● If there are any errors in the input prompt the user to re-enter details.
Post-Conditions
Use case name
UC 33: Check Available non-Clinical Items
Overview
This use case allows users to check the available quantity of non-clinical items in the ETU.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow
● Retrieve the data from the database.
Terminating Outcome
● Display the available non-clinical items details to the user.
Post-Conditions
Use case name
UC 34 : Order non-Clinical Items
Overview
This use case allows users to order non-clinical items from the stores.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
29
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Administration, Specialist, Doctor, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
● The non-clinical item type should have been added to the system.
Flow of events
Basic Flow
● System calculate the required quantity of items based on the past data and displays to the user.
● User can edit the quantity of required non-clinical items if necessary.
● Enter the order quantity to the database.
● Enter details to system log.
● Enter details to system log.
Terminating Outcome
● If successful non-clinical items order details are added to the system.
● If there are any errors in the input prompt the user to re-enter details.
Post-Conditions
Send the order to the relevant store.
Use case name
UC 35 : Add New non-Clinical Item types
Overview
This use case allows users to enter new non-clinical item types to the system.
Actor
Director, Deputy Director, Deputy Director IT, Deputy Director Supply, Specialist, Doctor, Nurse, Clerk
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow
● User enters details of the new non-clinical item type.
● Enter the details to the database.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
30
● Enter details to system log.
Terminating Outcome
● If successful new non-clinical item type details are added to the system.
● If there are any errors in the input prompt the user to re-enter details.
Post-Conditions
3.6 Death Certification
When a death of a patient occurs there is a legal procedure that should be followed before releasing the body to the relatives. This process is handles by the features provided in this category.
Use case name
UC 36 : Declaration of Death
Overview
This use case allows users to declare the death of a patient.
Actor
Director, Deputy Director, Deputy Director IT, Deputy director administration, Doctor, Nurse
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow:
● Confirmation of death.
● Fill the declaration of death form with the cause of the death.
● Update the data base.
● Enter details to system log.
Terminating Outcome
● If the death is confirmed, then inform the required other parties to release body.
● Terminate the online accessibility to the patient’s health records from irrelevant sites.
Post-Conditions
● If the cause of death unknown, inform the
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
31
deputy director administration for inquest and reports to the police posts arrangement.
Use case name
UC 37 : Inform Police Post
Overview
This use case allows users to inform the police post
Actor
Director, Deputy Director, Deputy Director IT, Deputy director administration, Hospital police post
Pre-conditions
● User should have logged into the system with required privileges.
● The cause of death should be unknown
Flow of events
Basic Flow:
● To take the police post arrangement forms via the data base.
● Send details to the police post.
● Update the data base.
● Enter details to system log.
Terminating Outcome
● Police post is informed about the death.
Post-Conditions
● If there is a problem, cancel the releasing of the body and inform the JMO.
Use case name
UC 38 : Inform JMO Office
Overview
This use case allows users to inform the JMO about a death.
Actor
Director, Deputy Director, Deputy Director IT, Deputy director administration, JMO, Clerical staff, Coroner
Pre-conditions
● User should have logged into the system with required privileges.
● The cause of death is unknown
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
32
Flow of events
Basic Flow:
● Send request to the JMO.
● Enter details to system log.
Terminating Outcome
● JMO is informed about the death.
Post-Conditions
Use case name
UC 39 : Inquest Request
Overview
This use case allows users to request an inquest about the death.
Actor
Director, Deputy Director, Deputy Director IT, Deputy director administration, JMO, Coroner
Pre-conditions
● User should have logged into the system with required privileges.
● Cause of the death unknown.
Flow of events
Basic Flow:
● Update police post information (if available)
● Update the data base.
● Enter details to system log.
Terminating Outcome
● Enter results of the inquest.
Post-Conditions
● If details are correct then inform the JMO for a post mortem.
Use case name
UC 40 : Post Mortem
Overview
This use case allows users to request the post mortem of the death.
Actor
Director, Deputy Director, Deputy Director IT, Deputy director administration, JMO
Pre-conditions
● User should have logged into the system with required privileges.
● The cause of death is unknown.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
33
Flow of events
Basic flow:
● Update police post information (if available)
● Update the data base.
● Give cause of death or release order.
● Update user profile in the database.
● Enter details to system log.
Terminating Outcome
● Confirm the correctness of the post mortem results .
Post-Conditions
Use case name
UC 41 : Issue Death Certificate
Overview
This use case allows users to issue the death certificate.
Actor
Director, Deputy Director, Deputy Director IT, Deputy director administration, Doctor, Birth and Death registrar
Pre-conditions
● User should have logged into the system with required privileges.
● Death of the patient should be confirmed.
Flow of events
Basic flow:
● Update the data base about the death.
● Certification of the death by the Birth and Death registrar.
● Enter details to system log.
Terminating Outcome
● Successfully issue the death certificate to the relations of the patient.
Post-Conditions
● Terminate the online accessibility to the patient’s health records from irrelevant sites.
Use case name
UC 42 : Release Body
Overview
This use case allows users to release the
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
34
body.
Actor
Director, Deputy Director, Deputy Director IT, Deputy director administration, Doctor
Pre-conditions
● User should have logged into the system with required privileges.
Flow of events
Basic Flow:
● Update the database.
● Issue the release letter.
● Enter details to system log.
Terminating Outcome
● Release body to the relations of the death man.
Post-Conditions
● Terminate the online accessibility to the patient’s health records from irrelevant sites.
4. SPECIFIC REQUIREMENTS
4.1 Usability
This system should be developed so that any user with basic computer knowledge can use the functions of a single user class after 2 hours of training. Since this is developed to be available in three languages Sinhala, English and Tamil there should be an easy way of changing the language.
4.2 Reliability and Availability
Reliability, the measure of delivering system services correctly as specified, should be higher, so that user can rely upon it in any time. The system failures can occur due to server failure, communication channel problem, storage etc. These failures should be recoverable with in a particular amount of time. Therefore both reliability and availability are very important for this system.
4.3 Performance
Performance is a highly required feature in this system because at ETU patients should be treated immediately. Therefore response time for a transaction should be less than 1 second.
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
35
4.4 Supportability
System should support any systems and procedures that are already in use at the hospital.
4.5 Design Constraints
Since this system is to be developed using an existing e-Health system new features added should adhere to the existing system architecture. Technology used should also be same as the technology used in the selected open source system.
4.6 On-line User Documentation and Help System Requirements
There should be a separate website for ‘e-Arogya’ which contains all the details of the system and help documents.
4.7 Interfaces
4.7.1 User Interfaces
Initially, a logging screen is displayed for the every user. When the user logs in, the user is directed to an interface depending on the user class the user belongs to. If the user is in the admission section, then a search box is provided to find if a given patient already exists in the system. If the patient does not exist, then a form is provided to enter the patient details. If the user is a doctor or a nurse then the interface displays a list of patients current being treated by the user and a search box to search a given patient based on the health id number or the name. When the user clicks on a patient’s name, all the details and medical history of the patient is displayed. The user can enter new details for a given patient. If the user belongs to the Investigations and results user class, then the user is directed to a page that contains a list of pending investigations requests. The page also contains a search box that allows the user to search past medical investigations. There will be a menu that provides access to other services provided by this user class. If the user belongs to the Supply chain management user class, then the user is directed to a page that contains a list of items that are ordered by different departments. The user can also view the amount of items available and the quantity of the items. If particular items are running low of the supplies, then it is indicated to the user. If the user belongs to the Support service management, the user is directed to a page that contains a list of pending requests for the services such as ambulances. The user can view past service requests.
If the user belongs to the Death certification user class, the user is directed to a page that
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
36
contains a list of deaths that occurred while the user is offline. Each item contains a link that allows the user to send requests to other involved parties. Basic flow of the user interfaces for each section is described in following figures.
Figure 4.1 - Page Navigation Details (Menu Level 1)
Figure 4.2 - Page Navigation Details-System Admin (Menu Level 2)
Figure 4.3 - Page Navigation Details- Patient Registration & EHR (Menu Level 2)
Figure 4.4 - Page Navigation Details-Investigation & Results (Menu Level 2, 3 and 4)
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
37
Figure 4.5 - Page Navigation Details- Supply Chain (Menu Level 2 and 3)
Figure 4.6 - Page Navigation Details - Support Service (Menu Level 2 and 3)
Figure 4.7 - Page Navigation Details -Death Certification version (Menu Level 2 and 3)
4.7.2 Software Interfaces
There should be an interface to communicate with the database. The system should provide an
e-Arogya Version: 1.0
Software Requirements Specification Date: 29/10/2010
SRS for e-Health Solution for ETU at Colombo South Teaching Hospital
38
API that allows other systems to be plugged in.
4.7.3 Communications Interfaces
When the system is expanded to other departments in the hospital, a LAN is required to communicate between the departments.
4.8 Applicable Standards
The system should adhere to Open Standards.
4.9 Software Quality Attributes
The quality of the software obviously depends on accuracy, speed, maintainability and user friendliness. Here since the main objective is to re-engineer the current process in the hospital, design should ensure that the system is well accepted by the users in the hospital. Users should be able to use the system with minimum knowledge of technique used and with minimum knowledge of laws and regulations. All the required legal restrictions must be handled within the system.