Requirements Engineering for Health Informatics

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.