Contemporary Software Development

The objective of the proposed patient management system is to automate the management of patient information and have a simple, cost-effective, and user-friendly application. The application will be responsible for collecting patient information including personal details, diagnosis, treatment, and prescription. Additionally, the application will support other functions by integrating several modules including pharmacist module, doctor/nurse module, accountant module, and admin module to facilitate seamless interaction of hospital processes and facilitate better, more efficient healthcare.

CONTEMPORARY SOFTWARE DEVELOPMENT 1
Contemporary Software Development
Student Name
Institution
Course
Date

CONTEMPORARY SOFTWARE DEVELOPMENT 2
Abstract
The objective of the proposed patient management system is to automate the
management of patient information and have a simple, cost-effective, and user-friendly
application. The application will be responsible for collecting patient information including
personal details, diagnosis, treatment, and prescription. Additionally, the application will
support other functions by integrating several modules including pharmacist module,
doctor/nurse module, accountant module, and admin module to facilitate seamless interaction
of hospital processes and facilitate better, more efficient healthcare. Many medical
institutions have for a long time been using the traditional filing system to store all the
information related to patients making it difficult to retrieve and share information. The
application will improve efficiency within hospitals and facilitate more accurate diagnosis,
treatment, and prescriptions.

CONTEMPORARY SOFTWARE DEVELOPMENT 3
Table of Contents
Abstract.................................................................................................................................................1
1 Introduction...................................................................................................................................5
1.1 Background Information........................................................................................................5
1.2 System Description................................................................................................................7
1.3 System modules.....................................................................................................................8
1.4 Problem Specification............................................................................................................8
1.5 System Objectives.................................................................................................................9
1.6 Scope of the Project...............................................................................................................9
1.7 Limitations of the Project.......................................................................................................9
1.8 Significance of the Project...................................................................................................10
1.9 Project Plan..........................................................................................................................10
1.9.1 Project Schedule..........................................................................................................10
2 System Design............................................................................................................................12
2.1 Physical Design...................................................................................................................12
2.1.1 Use case diagram.........................................................................................................12
2.1.2 Class Diagram..............................................................................................................13
2.1.3 Sequence Diagram.......................................................................................................15
2.2 Database Design..................................................................................................................15
2.2.1 File Design...................................................................................................................17
2.2.2 Procedure Flowchart....................................................................................................18
2.2.3 System Flowchart.........................................................................................................18
2.2.4 Data Flow Diagram......................................................................................................20
2.3 Programming Language.......................................................................................................20
2.4 Interface Design...................................................................................................................20
2.4.1 Login Page...................................................................................................................20
2.4.2 Add Patient..................................................................................................................22
2.4.3 Add Doctor..................................................................................................................23
2.4.4 Make Appointment......................................................................................................24
2.5 Requirements Specification.................................................................................................25
2.5.1 Hardware Requirements...............................................................................................25
2.5.2 Software Requirements................................................................................................25
2.6 Development Tools..............................................................................................................25
2.6.1 Front End.....................................................................................................................25
2.6.2 Back End......................................................................................................................26
2.6.3 Application Server.......................................................................................................26
Conclusion...........................................................................................................................................26
List of References................................................................................................................................28

CONTEMPORARY SOFTWARE DEVELOPMENT 4
Table of Figures and Tables
Figure 1: Project Schedule.......................................................................................................10
Figure 2: Gantt Chart...............................................................................................................11
Figure 3: Use Case Diagram....................................................................................................13
Figure 4: Class Diagram...........................................................................................................14
Figure 5: Sequence diagram.....................................................................................................15
Figure 7: File Design................................................................................................................17
Figure 8: procedure Chart........................................................................................................18
Figure 9: System Flowchart.....................................................................................................19
Figure 10: Data Flow Diagram................................................................................................20
Figure 11: Login Screen...........................................................................................................21
Figure 12: Add Patient.............................................................................................................22
Figure 13: Add Doctor.............................................................................................................23
Figure 14: Add Appointment...................................................................................................24
Table 1: Doctor details.............................................................................................................16
Table 2: Patient Details............................................................................................................16
Table 3: Billing details.............................................................................................................17

CONTEMPORARY SOFTWARE DEVELOPMENT 5
1 Introduction
Several applications have been developed in recent years with the goal of improving and
enhancing the quality of life (Cresswell and Sheikh, 2012). The patient management system
will have a database that will store all the patient information. There are several patient
management systems within our reach today in the market but they have limited functions
(Dahanayake, 2011). Healthcare institutions have become a critical sector in the world as it
provides medical services to patients suffering from various illnesses. As such, it is essential
for hospitals to store patient medical records to offer better healthcare services when a patient
visits the hospital again (Choo, Johnston and Manias, 2013).
Many hospitals today are still using the traditional paper-based filing system to keep
patient medical records which are faced with many challenges including many errors,
inefficiency, ineffectiveness, and time-consuming. The traditional system also makes it
difficult to retrieve information. It can be said that the traditional system of filing is both
technically and economically unviable (De-Angelis, 2014). The main aim of the patient
management system is to provide an efficient, effective, paperless, and more accurate,
cheaper, and faster reliable system for storing and retrieving patient information. The
application will provide excellent data security at every user-system interaction and offer
reliable and robust back-up and storage capabilities.
1.1 Background Information
The objective of any software development is to create a system that meets customer
requirements, user-friendly, cost-effective, and improves business operations. However,
before one starts developing software, it is important to first analyze the different activities
and functions that the software is expected to perform and the relationship with both external
and internal entities (Abraham, 2010). When conducting the analysis process, it is important
to collect information on transactions and decisions points out that the current system handles
and what needs to be improved in the new system.
Patient information and records have become a principal repository that is essential in
providing quality healthcare. It influences all the stakeholders that are responsible for
receiving, providing and reimbursement of healthcare services (Mathai, Shiratudin and Sohel,
2017). Even with the numerous advances in technology, how patient records have been kept

CONTEMPORARY SOFTWARE DEVELOPMENT 6
is still almost similar to what it was decades ago, that is, many hospitals still prefer the
manual way of keeping patient records. This has created a big challenge to different
healthcare providers because of the need for efficiency and effectiveness due to increased
patient capacity (McCracken and Edwards, 2017). Having an information system will help in
addressing such issues.
An information system is made up of procedure, people, software, data, and hardware
that are have been designed to offer accurate, up-to-date, and reliable information to the
different users to effectively and efficiently perform their daily operations at the right time
and for the right reasons (Palojoki et al., 2016). The information system has become one of
the key components for healthcare institutions to have accurate patient information and
provide quality and better healthcare. Hospitals use information systems today to maintain,
update, and better understand the importance of having electronic data (Mouw, 2014).
Using patient management system in the healthcare industry to manage patient
information like medicine prescription, doctor’s appointments, scheduling, and patient
medical history not only improve quality of healthcare but also reduces the cost and saves
time (Rey, 2015). Moreover, it enhances data control within the hospital and offers better
integration with other existing systems such as scheduling module, financial module,
employee management among others. As such, a patient management system should have the
ability to interact with other systems and stakeholders including administrators, finance,
medical device users, nurses, and physicians (Stevenson and Nilsson, 2011).
The main goal of the patient management system is to provide accurate, up-to-date
patient medical history including treatment, illnesses, and prescriptions that the patient has
received over the years. It also offers easy accessibility and flexibility of patient information
to an authorized user (De-Angelis, 2014). The information system will provide a platform to
enable healthcare providers and patients to interact seamlessly. However, as mentioned
earlier, most healthcare institutions have not adopted this kind of technology because of the
insufficient knowledge and know-how of medical information systems to handle such
medical problems. In several developed countries, computer-aided healthcare has been partly
achieved in several institutions. However, in many countries, the patient-doctor ratio is still
high (Mathai, Shiratudin and Sohel, 2017). The ratio of patients to a doctor is still high and
this has created numerous issues including inadequate and improper medical care. This

CONTEMPORARY SOFTWARE DEVELOPMENT 7
majorly affects the low-income class and doctors find themselves in a hurry in order to serve
all the patients. They tend to get overworked and tired.
With the ever-increasing population, it has become inevitable to have a patient
management system that will facilitate management and sharing of patient information
amongst the medical institutions to have better healthcare and allow doctors to make more
informed decisions (Mouw, 2014). The system also provides more accurate and up-to-date
information that the traditional filing system that has been used for a long time. Also, it is
expected that the medical industry will make use of more sophisticated technology to offer
medical care and the past patient information will be necessary for decision making. For
instance, a patient may be allergic to a particular treatment and if such records are not
available, then administering such medicine can cause more problems to the patient
(Stevenson and Nilsson, 2011).
1.2 System Description
The patient management system will be developed to enhance patient management
functions and automate some of the critical activities within a healthcare institution (Kazley
et al., 2012). The system will enable patient registration and the information collected will be
stored in a database. If the visiting patient has already been registered, the patient
identification number that is automatically generated during registration will be used to
search for the patient from the database. This will greatly improve access to patient
information and a lot of time and money is saved. A doctor will be assigned a number of
patients to attend to in a day; the doctor will conduct diagnosis and forwards a report
containing patent name and number with prescriptions to the pharmacist where the patient
will pick up his/her medicine. The doctor and the management will have the ability to view
the full patient report containing previous diagnosis and treatment procedures. The patient
record will be updated accordingly and stored in the database. The different users of the
system will be required to provide username and passwords in order to ensure the security of
patient information.
1.3 System modules
The application will be made up of five modules including patient module,
admin/management module, accountant module, pharmacist module, and doctor/nurse
module. The admin/management module will have superior privileges including adding and

CONTEMPORARY SOFTWARE DEVELOPMENT 8
managing all the system users, adding and monitoring appointments, monitoring patient
payments, blood bank reports, medical reports, diagnosis, and death reports. The patient
module will be comprised of requesting and viewing appointment status, viewing drug
prescriptions, list of doctors, medical history, and personal profile. The doctor/nurse module
will allow the doctor to make prescriptions to patients, manage patient appointments, conduct
diagnosis, update patient information, and manage own profile. The pharmacist module is
responsible for keeping a record of medicine and status, providing prescribed medicine to
patients, and monitor patient prescription. Finally, the accountant module will allow the
accountant to create invoices for payment, take cash, and monitor payment from patients.
1.4 Problem Specification
For a long time, patients have been spending a lot of money and time in hospitals
before getting proper medical attention. For instance, patients have had to queue for long
hours in right from registration process where they are supposed to buy hospital folder, or
spending time retrieving old file before finally consulting a medical consultant, then going to
the lab for testing, then to the pharmacy to buy prescribed medicine (Black, 2015). This is
such a time-consuming and tiring process. Patients may end up spending a whole day in the
hospital because of the manual processes involved in handling them.
Such situations are very discouraging and many patients have preferred going to other
healthcare providers who may not have the required qualifications and skills or resort for self-
medication (Emuoyibofarhe, Adewuyi and Amusan, 2018). This is very risky and may lead to
more dire problems or even death. Additionally, medical professionals have been tasked with
a huge number of tasks and as mentioned earlier, the ratio of doctor-patient is still high. As
such, doctors tend to spend less time examining a patient because of the need to serve many
other patients who are in waiting.
Additionally, prescription and diagnosis rely on the memory of the doctor and preferred
drugs. Doctors have a lot of information about various diseases, symptoms, complications,
and different prescription which can be similar in some cases. Therefore, accurate
prescription and diagnosis may not be achieved because depending on the human brain is
sometimes unreliable (Cresswell and Sheikh, 2012). Also, retrieval and storage of accurate
patient information is still a challenge in many medical institutions. This is because the
manual filing system has a number of challenges because it is difficult to obtain timely and
accurate patient information. Finally, storing patient information manually is costly, occupies

CONTEMPORARY SOFTWARE DEVELOPMENT 9
a lot of space and has data redundancy. All these challenges cause inefficiency,
ineffectiveness, and may lead to loss of lives.
1.5 System Objectives
The system will seek to achieve the following objectives:
 To make it easier and simple to store and retrieve patient information
 Minimize the number of patient records that are lost
 The system will enable a doctor to view patient medical history
 Add doctors to the systems and updating their profiles to reflect their field of
expertise.
 Generate patient reports
 Analyze the current activities and procedure that is employed in the healthcare
industry with regards to admission, diagnosis, and treatment of patients.
 Identify the problems with the current system
 Provide designs including UML diagrams and interfaces of the proposed web-based
mobile application for managing patients.
1.6 Scope of the Project
This project is restricted to the development of patient management system that will
offer services such as admission, diagnosis, and treatment history of the patient and payment
of bills. The application will be developed using Java.
1.7 Limitations of the Project
The system will only cover the major aspect of patient information but will exclude
laboratory units because of financial and time constraints.
1.8 Significance of the Project
The patient management system will offer numerous advantages to healthcare industries
including (Chang-tae, 2014):
 Cost reduction
 Better and quality healthcare
 Promotes evidence-based treatment
 Better mobility and record keeping.

CONTEMPORARY SOFTWARE DEVELOPMENT 10
1.9 Project Plan
1.9.1 Project Schedule
The project will approximately take 58 days. However, the timeline may be altered
because of several factors that may affect project progress including unavailability of
resources required or delay in delivery.
Figure 1: Project Schedule
(Source: Author, 2019)

CONTEMPORARY SOFTWARE DEVELOPMENT 11
Figure 2: Gantt Chart
(Source: Author, 2019)

CONTEMPORARY SOFTWARE DEVELOPMENT 12
2 System Design
The objective of the system design stage is to plan on how to come up with a solution that
will address the requirements specified in the problem statement. It determines the various
elements that the application should have and how it will interact with both external and
internal entities (Anci and Wiradinata, 2018). System design describes the data, interfaces,
modules, components, and the architecture of the system that are required to meet the
requirements. System design is normally in two phases: database design and physical design.
2.1 Physical Design
The physical design illustrates a graphical representation of the application and how the
different entities interact with each other (Charland and LeRoux, 2011).
2.1.1 Use case diagram
This diagram illustrates the different system functions in terms of actors, their goals,
and any type of dependencies that may exist between the actors (Turan, 2015). The diagram
below represents the use case of the proposed patient management system.

CONTEMPORARY SOFTWARE DEVELOPMENT 13
doctor
Registration
Reception
Goto doctor
Take recept
pharmacist
laboratorist
Discharge summary
patient
Figure 3: Use Case Diagram
(Source: Di Martino and Esposito, 2015)
2.1.2 Class Diagram
It illustrates the different groups or categories of components that have common
behavior and attributes. A class diagram is divided into three sections: the upper section
illustrates the name of the component, the middle section illustrates the attributes that the
component has, and the lower section describes the operations (Turan, 2015). The figure
below represents the class diagram for the proposed application.

CONTEMPORARY SOFTWARE DEVELOPMENT 14
Figure 4: Class Diagram
(Source: Di Martino and Esposito, 2015)

CONTEMPORARY SOFTWARE DEVELOPMENT 15
2.1.3 Sequence Diagram
The sequence diagram represents how messages are orders among the different
modules (Turan, 2015). The figure below illustrates a sequence diagram for the proposed
system
Doctor Registration Reception Patient Laboratory Pharmacy ischarge summary
1 : login()
2 : view appointment()
3 : registration()
4 : send request()
5 : done any surgeries()
6 : go to laboratory()
7 : take medicins()
8 : paitent ok()
9 : send discharge summmary()
10 : discharge paitent()
Figure 5: Sequence diagram
(Source: Di Martino and Esposito, 2015)
2.2 Database Design
The output of the application will be designed to allow the generation of reports from
the database that can be printed. The output will contain information concerning a patient
from the database. The system will allow a person to view the report on the screen or printed
as hardcopy if needed. The output will include patient personal details, diagnosis and
treatment record, and billing record.

CONTEMPORARY SOFTWARE DEVELOPMENT 16
The input of the proposed system will be an admission form to allow entering of patient
information from the keyboard. The tables below represent samples of data representation in
the database
Table 1: Doctor details
Table 2: Patient Details

CONTEMPORARY SOFTWARE DEVELOPMENT 17
Table 3: Billing details
2.2.1 File Design
The database will be designed in such a way to remove redundancy. The database will
be designed using MySQL. The figure below represents the design of the file in the database.
Figure 6: File Design
(Source: Fernandes and Song, 2014)

CONTEMPORARY SOFTWARE DEVELOPMENT 18
2.2.2 Procedure Flowchart
The figure below represents the procedure chart
Figure 7: procedure Chart
(Source: Fernandes and Song, 2014)
2.2.3 System Flowchart
The figure below illustrates a system flowchart.

CONTEMPORARY SOFTWARE DEVELOPMENT 19
Figure 8: System Flowchart
(Source: Fernandes and Song, 2014)

CONTEMPORARY SOFTWARE DEVELOPMENT 20
2.2.4 Data Flow Diagram
Figure 9: Data Flow Diagram
(Source: Fernandes and Song, 2014)
2.3 Programming Language
The proposed patient management system will be developed using PHP because it is a
stable and easy software development platform (Choo and Lee, 2013). It is also flexible and
has the ability to offer the development team with hints and better graphical user interface
(Vuorimaa et al., 2015).
2.4 Interface Design
2.4.1 Login Page
The application will have a standard login page for all the users. User will be
prompted to select the category to login to. The users will be able to enjoy the application
functions after successfully logging in by providing correct username and password.

CONTEMPORARY SOFTWARE DEVELOPMENT 21
Figure 10: Login Screen
(Source: Mathai, Shiratudin and Sohel, 2017)
The login page will have three user groups including a doctor, patient, and
management. The features will be based on the user category. The management will have the
rights to create and delete doctor and patient profiles and are responsible for monitoring any
pending diagnosis and test reports and approving appointments. The management category
will act as the system administrator. The patients will have the ability to update their profiles
and make appointments with the available doctors. Also, they will have the ability to check
their medical history. Their functions are more limited than those of management. The doctor
will have the ability to check all the appointments and accept or reject them depending on
their availability. They will also be able to make a prescription to their patients on the
prescription page which will have a number of automated features. All the features that
enable the doctor to make prescriptions will be provided for in the prescription page. This
will greatly improve doctors’ productivity by enhancing their efficiency and effectiveness.

CONTEMPORARY SOFTWARE DEVELOPMENT 22
2.4.2 Add Patient
Figure 11: Add Patient
(Source: Mathai, Shiratudin and Sohel, 2017)
This feature will be available for admin to register a new patient. This registration
form will facilitate registering full details of the patient by providing patient name, address,
phone number, gender, age, username, and password. These details can be updated by the
patient upon successful login. All the details should be entered correctly to ensure the
accuracy of the information.

CONTEMPORARY SOFTWARE DEVELOPMENT 23
2.4.3 Add Doctor
Figure 12: Add Doctor
(Source: Mathai, Shiratudin and Sohel, 2017)
This is a feature that is only available to the management/admin category. Doctor’s
details that are needed to successfully add a doctor to the database include a phone number,
physical address, national ID, Zip Code, gender, age, and full names. The doctor will have
the privilege to modify these details upon successful login and when needed. The
management will have the rights to assign a patient to a doctor or contact the doctor to accept
or reject an appointment based on his/her schedule. Some of the other crucial information
such as doctor’s profession and specialty will be added and patients will be able to view
doctors’ specialty. This information is very essential as it will enable the patients to choose
the right doctor to address their cases.

CONTEMPORARY SOFTWARE DEVELOPMENT 24
2.4.4 Make Appointment
Figure 13: Add Appointment
(Source: Mathai, Shiratudin and Sohel, 2017)
The management will have the ability to add appointments for the patients who are
admitted to the hospital. The above screen shows the add appointment function where the
admin will select a doctor depending on the case and choose the patient name and date. This
is important as it ensures that the doctors are always on schedule to attend to patients without
being overwhelmed. Also, it enables the patients to know the time and the date to see the
doctor and avoid having to queue and spending a lot of time. The patients will only request
for an appointment but the doctor or the management will be responsible for approving the
appointment dates or adjusting them depending on the doctor’s availability. This reduces the
chances of double booking and allows the doctor to have ample time with their patients. In
case of emergencies and a doctor is needed, the management will be required to reschedule
all the upcoming appointments and notify both the patient and the doctor.

CONTEMPORARY SOFTWARE DEVELOPMENT 25
2.5 Requirements Specification
For any application or software to run smoothly and efficiently, there should be a
minimum set of requirements that should be met (Inoue et al., 2010). These requirements
serve as guidelines in system implementation. This section will describe the minimum
hardware and software requirements for the proposed web-based patient management system
2.5.1 Hardware Requirements
The following are the minimum hardware requirements for the proposed system (Maniar
and Ahmed, 2017).
 Storage space (Hard disk capacity)- 80 GB
 RAM-2 GB
 Processor- Intel core i5.
2.5.2 Software Requirements
The following are the minimum software requirements for the proposed system (Merugu
and Chinnam, 2019).
 Operating system Windows, MacOS, iOS, Android
 Back end/ Database- MySQL
 Frontend- PHP
2.6 Development Tools
2.6.1 Front End
Since the application will be web-based, the preferred development language to
design the front-end will be PHP. It is an HTML-embedded, cross-platform, and server-side
scripting language that is widely used in the development of web-based systems and
applications (Anto, 2011). The reason why PHP is the preferred front-end development
language is that its syntax has been borrowed from a number of other programming
languages including Pearl, Java, and C and has a number of distinct PHP-specific properties.
PHP will allow application developers to create dynamic pages quickly. Also, the need to
have several CGI programs is eliminated by allowing the developer to introduce simple
scripts in the HTML files directly. PHP also makes it simple to troubleshoot and manage
web-based applications by putting all the web page components in one HTML file. PHP also
supports all the major operating systems, both mobile OS and desktop OS (Anto, 2011).

CONTEMPORARY SOFTWARE DEVELOPMENT 26
2.6.2 Back End
MySQL will be used to the back-end which is basically the database. It is reliable,
faster, and easy to use and have over time become one of the popular database development
tools because it has offered better administration, maintenance, and limited downtime
(Tapdiya and Xue, 2014). MySQL is one of the open-source relational DBMS and is flexible
and reliable. It is a multi-user, multi-threaded, and high-performance database management
platform. MySQL can run on MacOS, Windows, and UNIX Operating systems. MySQL also
has the ability to handle large volumes of data faster as compared to the existing solutions.
MySQL support the proposed web-based mobile application.
2.6.3 Application Server
XAMPP server is the preferred application server for the proposed application. It is
made up of MySQL database, Apache HTTP Server, and script interpreters are written in
Pearl and PHP programming languages (Singh, 2019).
Conclusion
In conclusion, patient information and records have become a principal repository that
is essential in providing quality healthcare. It influences all the stakeholders that are
responsible for receiving, providing and reimbursement of healthcare services. Even with the
numerous advances in technology, how patient records have been kept is still almost similar
to what it was decades ago, that is, many hospitals still prefer the manual way of keeping
patient records. This has created a big challenge to different healthcare providers because of
the need for efficiency and effectiveness due to increased patient capacity. Having an
information system will help in addressing such issues.
The proposed system will enable patient registration and the information collected
will be stored in a database. If the visiting patient has already been registered, the patient
identification number that is automatically generated during registration will be used to
search for the patient from the database. This will greatly improve access to patient
information and a lot of time and money is saved
For a long time, patients have been spending a lot of money and time in hospitals
before getting proper medical attention. For instance, patients have had to queue for long
hours in right from registration process where they are supposed to buy hospital folder, or
spending time retrieving old file before finally consulting a medical consultant, then going to

CONTEMPORARY SOFTWARE DEVELOPMENT 27
the lab for testing, then to the pharmacy to buy prescribed medicine. This is such a time-
consuming and tiring process. Patients may end up spending a whole day in the hospital
because of the manual processes involved in handling them. The patient management system
will offer numerous advantages to healthcare industries including cost reduction, better and
quality healthcare, promotes evidence-based treatment, and better mobility and record
keeping.

CONTEMPORARY SOFTWARE DEVELOPMENT 28
List of References
Abraham, S. (2010). Technological Trends in Health Care. The Health Care Manager, 29(4),
pp.318-323.
Anci, A. and Wiradinata, T. (2018). Design and Development of RunForFun Mobile
Application. MATEC Web of Conferences, 164, p.01005.
Anto, J. (2011). PHP - Advanced Tutorial. SSRN Electronic Journal, (2), pp.105-128.
Black, S. (2015). Problems at Addenbrooke’s caused by failure to implement electronic
patient record system effectively. BMJ, p.h5721.
Chang-tae, K. (2014). The Effects of Electronic Medical Record (EMR) System on Hospital
Management Performance. International Business Education Review, 11(4), pp.157-178.
Charland, A. and LeRoux, B. (2011). Mobile Application Development: Web vs.
Native. Queue, 9(4), p.20.
Choo, C. and Lee, S. (2013). Towards Persistence Framework-Based Rapid Application
Development Toolkit for Web Application Development. Journal of Computer Science, 4(4),
pp.290-297.
Choo, J., Johnston, L. and Manias, E. (2013). Effectiveness of an electronic inpatient
medication record in reducing medication errors in Singapore. Nursing & Health Sciences,
16(2), pp.245-254.
Cresswell, K. and Sheikh, A. (2012). Electronic Health Record Technology. JAMA, 307(21).
Dahanayake, S. (2011). Electronic Patient Record System for psychiatry units. Sri Lanka
Journal of Bio-Medical Informatics, 1(0), p.32.
De-Angelis, C. (2014). The Electronic Health Record: Boon or Bust for Good Patient
Care?. Milbank Quarterly, 92(3), pp.442-445.
Di Martino, B. and Esposito, A. (2015). A rule-based procedure for automatic recognition of
design patterns in UML diagrams. Software: Practice and Experience, 46(7), pp.983-1007.

CONTEMPORARY SOFTWARE DEVELOPMENT 29
Emuoyibofarhe, J., Adewuyi, K. and Amusan, E. (2018). Development of an Improved
Electronic Patient Health Record Management System with Speech Recognition. Journal of
Advances in Mathematics and Computer Science, 29(6), pp.1-15.
Fernandes, F. and Song, M. (2014). UML-Checker: An Approach for Verifying UML
Behavioral Diagrams. Journal of Software, 9(5).
Inoue, T., Asakura, H., Uematsu, Y., Sato, H. And Takahashi, N. (2010). Web API Database
Systems for Rapid Web Application Development. IEICE Transactions on Information and
Systems, E93-D(12), pp.3181-3193.
Kazley, A., Diana, M., Ford, E. and Menachemi, N. (2012). Is electronic health record use
associated with patient satisfaction in hospitals?. Health Care Management Review, 37(1),
pp.23-30.
Maniar, F. and Ahmed, A. (2017). Ontology Driven Requirement Specification. Journal of
Independent Studies and Research - Computing, 15(2).
Mathai, N., Shiratudin, M. and Sohel, F. (2017). Electronic Health Record Management:
Expectations, Issues, and Challenges. Journal of Health & Medical Informatics, 08(03).
McCracken, S. and Edwards, J. (2017). Implementing a knowledge management system
within an NHS hospital: a case study exploring the roll-out of an electronic patient record
(EPR). Knowledge Management Research & Practice, 15(1), pp.1-11.
Merugu, R. and Chinnam, S. (2019). Automated cloud service based quality requirement
classification for software requirement specification. Evolutionary Intelligence, 14(5), pp.11-
17.
Mouw, E. (2014). Political Attitudes on the Dutch Electronic Patient Record. International
Journal of Privacy and Health Information Management, 2(1), pp.34-50.
Palojoki, S., Pajunen, T., Saranto, K. and Lehtonen, L. (2016). Electronic Health Record-
Related Safety Concerns: A Cross-Sectional Survey of Electronic Health Record
Users. JMIR Medical Informatics, 4(2), p.e13.
Rey, K. (2015). Electronic Health Record Adoption. SSRN Electronic Journal, 8(4), pp.57-
78.

CONTEMPORARY SOFTWARE DEVELOPMENT 30
Singh, A. (2019). Data Migration from Relational Database to MongoDB using XAMPP and
NoSQL. SSRN Electronic Journal. 5(4), pp.21-29.
Stevenson, J. and Nilsson, G. (2011). Nurses’ perceptions of an electronic patient record from
a patient safety perspective: a qualitative study. Journal of Advanced Nursing, 68(3), pp.667-
676.
Tapdiya, A. and Xue, Y. (2014). Performance Variations in Profiling Mysql Server on the
Xen Platform: Is It Xen or Mysql?. International Journal of Computer Science and
Information Technology, 6(2), pp.1-19.
Turan, M. (2015). Integrating Software Metrics with UML Diagrams. Lecture Notes on
Software Engineering, 3(3), pp.220-224.
Vuorimaa, P., Laine, M., Litvinova, E. and Shestakov, D. (2015). Leveraging declarative
languages in web application development. World Wide Web, 19(4), pp.519-543.