CS6201 - Requirements Engineering for Health Informatics: Epilepsy EPR

This report outlines the requirements engineering process for developing an electronic patient record (EPR) system for epilepsy services, driven by the HSE National Clinical Care Programme. The goal is to create a centralized web application accessible to various disciplines across different epilepsy centers, enhancing patient care and research capabilities. The report includes a glossary of terms, data requirements with a data dictionary detailing patient information, epilepsy history, encounters, telephone interactions, and medication details. It also specifies quality requirements related to system accessibility, data capture, and medication management. The system aims to improve efficiency, diagnostic speed, research collaboration, and patient record management, building upon existing EPR frameworks while adhering to security guidelines. Desklib offers solved assignments and past papers for students.

Requirements Engineering for Health Informatics
Background
Epilepsy service has been identified by HSE National clinical service as a provision for project
transformation. There are about 40,000 patients that are using Epilepsy services currently. In
order for this services to provide the best care possible services, an Electronic system is required
to accomplish this. This system will be responsible for offering services that will fulfill all the
needs of its users. The system will be designed as a central system that will require partnership
from the vendor and different number form existing healthcare systems. There are existing
systems that were developed in different Healthcare services and they have been used in different
places. In those systems, there are a number of users who are using them. The HSE set out a
demand for a proposition to dedicate the above task. They look for a specialist organization who
will help accomplish the undertaking objectives by building up the framework to meet the
quality, security and productivity prerequisites.
Purpose
So as to satisfy these goals and to guarantee congruity of care, the HSE requires a Web app
online electronic wellbeing record system, which can be utilized by a huge number of various
orders. This system can be utilized by a different number of users from any given location
associated with the different number of Epilepsy. The system will be suitable for offering all the
services that are required in the health services. The data center will be centralized in order for it
to offer equal services to all stations that are involved in providing health services. The
framework needs the capacity to build up any improvements or usefulness required to meet the
clinical necessities and administration needs of epilepsy patients in an advancing human services
condition. The performance of the system should be continuous and should be available at any
time. The framework must be equipped for having a bi-directional interface with a wide range of
doctor's facility frameworks and distinctive occurrences of frameworks over an extensive variety
of healing centers. The framework must have a full suite of detailing usefulness and the capacity
to grow impromptu reports as required. Preparing and client rules must be given and ceaselessly

refreshed. The framework must have full, entire review trails and should furnish strong security
controls in accordance with the HSE security rules.
Some of the goals of the system include the following. The goals of the system should be
efficient and safe for the users.
 The system will reduce the time of clinic appointments.
 Increase the speed of diagnosing diseases.
 Increase the research process up to an international level.
 Making prescriptions and medications simpler.
 Promote self-treatment.
 Promote health care analysis.
 Provide centered –management of patients records.
 Allow collaboration in international research.
The framework goals are to construct further on the current EPR framework. The Demand for
Proposals record plots the prerequisites as the accompanying:
 Support and maintenance of the system is one of the highest priority that the system is
being constructed for.
 The system will be constructed to allow room for improvement for future purposes.


Glossary of terms
This is the list of glossary terms that may be used.
Framework- this are various components that help the system achieve its objectives.
System- a set of entities that a accomplish certain objectives.
EPR: - Recordkeeping system.
Efficiency: This is the ration of useful work performed by the machines.
Usefulness: This is the capability of the software to meet the stated requirements.
Objectives: This is the main aim of any particular system.
Goal: This is an objective or ambition of the system.
Maintenance: This is the state of preserving something of a situation. Like maintaining the
state of the system.
Accessibility: this the ability and quality of being reached at any time from any location.
Failure: this is the deviation of the system from its main requirements to be accomplished.
Functionality requirements: this are the requirements that a system must accomplish.
Project: is a temporary endeavor with particular objectives.
Unwavering quality: The capacity of the product item to play out its capacities under
expressed conditions for a predefined timeframe, or for a predetermined number of activities.
Prerequisite: These are like the requirements of the system. A condition or ability required by a
client to take care of an issue or accomplish a goal. A condition or ability that must be met or
controlled by a framework or framework part to fulfill an agreement, standard, detail, or other
formally forced archives. An archived portrayal of a condition or ability.
Security: This is the freedom away from any harm.
User: These are the people who use the EPR system.

GUI- This the interface of the system the user interacts with it.
HSE: This is the health service executive.
Patient: these are the clients who uses the services form the health care clinics.
Network admin: This is the manager of the system who has a lot of privileges in the system.
MRN: This is the medical number that uniquely identifies patients in the records.
DOR: Date of registration:
Module: This is the smallest part of a project that is used to accomplish a certain task.

Data requirements
The system shall store data information basing on the following data model.

Data dictionary
Class: patient
Patient identifier:
Won't wind up operational until the national one of a kind patient identifier is executed, turned
gray out until broadly actualized however on the patient statistic screen.
Addition of patient criteria
All the details of the patients should either be in text format or Numerical this include the
Gender, Date of Birth and the UID number .The attributes include, first and last name, DOR
,UID number, Address and gender.
Class:Epilepsy history
The attributes in this class include: Classification, Date of episode, Free-comment, Diagnosis and
Duration.
Class: First patient Encounter
The attributes in this class include: Signs of the diseases, Injuries that are caused, Neurogically,
Cranial nerves ,pupils limbs and gait.
Class: Telephone
This contains all the details of telephones that are a made in the hospitals .The attributes in this
section include the type of call made, the time that the call was made, date of the call and the
reason of the call.
Class: Medication
This contains all the details of the medicines that are required by patients, this are the attributes
of this class .They include the following the name of the drug, dose that is prescribed to the
patient, routes, date of deletion and the name of the who deleted it from any particular record and
the frequency of which the medicine should be applied.

The following describes the words that were used in the above classes.
MRN-This is a unique number that identifies a patient in the EPR system. It must be of type
integer.
DOR- This is the date that the patient was registered in the system.
DOB: This is the date of birth of the customer of the patient.
First_name: This is the patient's forename. It must be the enlisted original name on all
recognizable proof, for example, Passport, Driving License. It will acknowledge just alpha
characters and should be a greatest of 20 characters long.
Lastname, this is the patient's last name. It must be the enlisted original name on all
recognizable proof, for example, Passport, national id. It will acknowledge just alpha characters
and should be a greatest of 20 characters long.
Address: This is the patient's location. It is limited to three lines of content. It will be utilized for
sending all correspondence to the patient. Every patient will just have one current location.
Dose: This is the prescription that is given to the patient
Gender: This is the sex of the patient can either be male or female.
Nick_name: This is the name that is given to the patient by the hospital.
Medical_name: This is the medicine that is given to any patient.
Message_id: This is the id of the message that is sent by anybody using the system.
Date_of expiry: This is the date which the medicine or the drug is to to expire.
Manufacturer_name: This is the name of the company that manufactured the drugs.

Quality requirements
Requirement #: 1 Requirement Type: Event/Use Case
#:
Description:
The system shall support all the requirements
That is required by the users
Rationale: Health centers in Ireland are in the process of introducing the EPR
system that will
Manage all the patient Records.
Source: Health department is the
Fit Criterion: The system shall meet all the requirements that are required in the
hospitals
Customer Satisfaction: 7 Customer Dissatisfaction: 6
Dependencies: Conflicts: N/A
N/A
Supporting Materials: n/A
History:
Requirement #: 2 Requirement Type: Event/Use Case

#:
Description: The system shall capture all the details of the patients.
Rationale: The system shall capture each date that the patient’s records are taken.
Source: This must be in the format DD/MM/YYYY
Fit Criterion: Clinical staff/end user
Customer Satisfaction:8 Customer Dissatisfaction: 7
Dependencies: N/A Conflicts:N/A
Supporting Materials: None
History: Created on January 2015
Requirement #: 3 Requirement Type: Event/Use Case
#:
Description: The system will be able to be accessed from any location

Rationale: The system will be able to be accessed using the vpn network
Source: Through the online web application.
Fit Criterion: Clinical staff/end user/Members of the staff.
Customer Satisfaction:8 Customer Dissatisfaction: 7
Dependencies: N/A Conflicts:N/A
Supporting Materials: None
History: Created on
Requirement #: 4 Requirement Type: Event/Use Case
#:
Description: The system shall capture all the history of epilepsy episode.
Rationale: In the clinical requirements the history must be captured.
Source: Through the online web application.
Fit Criterion: Clinical staff/end user/Members of the staff.

Customer Satisfaction:8 Customer Dissatisfaction: 7
Dependencies: N/A Conflicts:N/A
Supporting Materials: None
History: Created on
Requirement #: 6 Requirement Type: Event/Use Case
#:
Description: The system shall provide a user with a list of organisations they work in on log on
Rationale: Clinical staff often work in more than one health organisation
Source: Clients must select an hospital from the list of the hospitals
Fit Criterion: Through a combo box
Customer Satisfaction:8 Customer Dissatisfaction: 7
Dependencies: N/A Conflicts: N/A
Supporting Materials: None
History: Created on

Requirement #: 7 Requirement Type: Event/Use Case
#:
Description: The system shall have a medications module with a frequency for individual
medications
Rationale: The clinical staff require recording of medications order sentences built into the
system
Source: The frequency must meet clinical guidelines
Fit Criterion: The frequency must meet clinical guidelines
Customer Satisfaction:8 Customer Dissatisfaction: 7
Dependencies: N/A Conflicts:N/A
Supporting Materials: None
History: Created on