Patient Record Management System

Submitted By

Student Name Student ID

Md.Abdullah 242-15-955
Md.Sariful Islam 242-15-954
Tanzim Ahmed 242-15-953
Nur A Monjil Arvi 242-15-948
Farhana Meherin 242-15-958
Rimu
Samia Bushra Prapti 242-15-959

MINI LAB PROJECT REPORT

This Report Presented in Partial Fulfillment of the course CSE114:
Programming and Problem Solving Lab Computer Science and
Engineering Department

DAFFODIL INTERNATIONAL UNIVERSITY

Dhaka, Bangladesh
December 9, 2024
 DECLARATION
We hereby declare that this lab project has been done by us under the supervision of Abdullah Al
Shafi, Lecturer, Department of Computer Science and Engineering, Daffodil International University.
We also declare that neither this project nor any part of this project has been submitted elsewhere as lab
projects.

Submitted To:

Abdullah Al Shafi

Course Teacher’s Name

Designation Lecturer
Department of Computer Science and Engineering Daffodil
International University

Submitted by

Md.Abdullah
Student Name Student
ID:242-15-955
Dept. of CSE, DIU

Md.Sariful Isalm Tanzim Ahmed

Student Name Student Student Name Student
ID:242-15-954 ID:242-15-953
Dept. of CSE, DIU Dept. of CSE, DIU

Samia Bushra Prapti Farhana Meherin Rimu

Student Name Student Student Name Student
ID:242-15-959 ID:242-15-958
Dept. of CSE, DIU Dept. of CSE, DIU

Nur A Monjil Arvi

Student Name Student
ID:242-15-948
Dept. of CSE, DIU

©Daffodil International University i

 COURSE & PROGRAM OUTCOME

The following course have course outcomes as following:.

Table 1: Course Outcome Statements

CO’s Statements
CO1 Able to solve computing problems, Expression Evaluation using programming concepts
and learn the basic concept of ACM Problem solving techniques.
CO2 Able to apply fundamental programming elements including: variable, use of data types
and data structures, decision structures, loop structures, pointer, string, console, file IO,
and functions
CO3 Able to specify the problem requirements, analyze the problem, design the algorithm to
solve the problem and implement with the help of programming language.
CO4 Able to apply the knowledge of programming and problem solving in real life problems.

PO’s Statements
PO1 Identify, formulate, and analyze complex computing and engineering problems using
principles of mathematics, science, and engineering.
PO2 Design efficient, scalable, and sustainable software, systems, or processes to meet specific
needs, considering societal, safety, and environmental constraints.
PO3 Apply modern engineering and IT tools, techniques, and skills to solve engineering problems,
with an understanding of their limitations.
PO4 Apply ethical principles and commit to professional responsibilities in computing practice
while understanding the impact of engineering solutions on society and the environment.

Bloom’s Statements
Statements

C1 Remembering

C2 Understanding

C3 Applying

A1 Affective
domain

A2 Psychomotor
domain

KP

KP1 This knowledge profile involves the understanding of

mathematical principles and computing fundamentals
required to analyze and solve problems in computer
science and engineering

KP2 This profile covers the foundational knowledge of

©Daffodil International University ii
 engineering concepts, applied to computing systems,
software, and hardware.

KP3 This knowledge profile pertains to advanced concepts in

software engineering, systems programming, and
computational theories.

KP4 his profile focuses on understanding professional ethics,

legal responsibilities, and the societal impact of computing
technologies.
CO PO Blooms KP CEP
CO1 PO1 C1 KP1 EP1
CO2 PO2 C2 KP2 EP2
CO3 PO3 C3 KP3 EP3
CO4 PO3 A1,A2 KP4 EP4,EP5

Table 2: Mapping of CO, PO, Blooms, KP and CEP

The mapping justification of this table is provided in section 4.3.1, 4.3.2 and 4.3.3.

©Daffodil International University iii

 Table of Contents

Declaration i

Course & Program Outcome ii

1 Introduction 1
1.1 Introduction................................................................................................................................1
1.2 Motivation..................................................................................................................................1
1.3 Objectives...................................................................................................................................1
1.4 Feasibility Study.........................................................................................................................1
1.5 Gap Analysis..............................................................................................................................1
1.6 Project Outcome.........................................................................................................................1

2 Proposed Methodology/Architecture 2
2.1 Requirement Analysis & Design Specification..........................................................................2
2.1.1 Overview.......................................................................................................................2
2.1.2 Proposed Methodology/ System Design.......................................................................2
2.1.3 UI Design......................................................................................................................3
2.2 Overall Project Plan...................................................................................................................4

3 Implementation and Results 5

3.1 Implementation...........................................................................................................................5
3.2 Performance Analysis.................................................................................................................5
3.3 Results and Discussion...............................................................................................................6

4 Engineering Standards and Mapping 7

4.1 Impact on Society, Environment and Sustainability..................................................................7
4.1.1 Impact on Life...............................................................................................................7
4.1.2 Impact on Society & Environment................................................................................7
4.1.3 Ethical Aspects..............................................................................................................7
4.1.4 Sustainability Plan.........................................................................................................7
4.2 Project Management and Team Work.......................................................................................7
4.3 Complex Engineering Problem..................................................................................................7
4.3.1 Mapping of Program Outcome......................................................................................8
4.3.2 Complex Problem Solving............................................................................................9
4.3.3 Engineering Activities...................................................................................................9

©Daffodil International University iv

Table of Contents Table of Contents

5 Conclusion 10
5.1 Summary....................................................................................................................................10
5.2 Limitation...................................................................................................................................10
5.3 Future Work...............................................................................................................................10

References 11

©Daffodil International University v

 Chapter 1

Introduction

This chapter outlines the project’s background, motivation, objectives, feasibility, gap analysis, and expected
outcomes. It highlights the need for a streamlined approach to managing patient records.

1.1 Introduction
Managing patient records manually is inefficient, error-prone, and insecure. This project addresses these
issues by developing a digital Patient Records Management System (PRMS) using C programming, ensuring
secure, reliable, and accessible record management.

1.2 Motivation
Manual methods of managing patient records delay access to critical information. A digital solution simplifies
and secures the process. This project also enhances technical skills and prepares the team for real-world
challenges.

1.3 Objectives
The project aims to:

• Develop a system for adding, viewing, updating, and storing patient records.

• Ensure data accuracy, security, and persistence through file storage.

• Create an intuitive and error-resistant user interface.

1.4 Feasibility Study

Existing solutions are complex and costly for small-scale facilities. This project focuses on a lightweight,
standalone tool built in C, making it a feasible option for smaller healthcare providers needing an efficient
system.

1.5 Gap Analysis

The lack of simple, offline tools for patient record management is a significant gap. This project bridges the
gap by creating an affordable and accessible system for small clinics and independent practitioners.

1.6 Project Outcome

The project will deliver a functional PRMS with essential features, enabling streamlined patient record
management. It will also enhance the team’s programming and project development expertise.

©Daffodil International University 1

 Chapter 2

Proposed Methodology/Architecture

This chapter outlines the methodology and system design for the Patient Records Management System
(PRMS). It explains how the system will be developed, how the user interface will be designed, and the
overall plan for completing the project.

2.1 Requirement Analysis & Design Specification

2.1.1 Overview
The goal of the Patient Records Management System (PRMS) is to make it easier for
healthcare workers to manage patient information. The system will allow users to
add, update, search, and store patient details. This section explains what the system
needs to do and how we will design it to meet those needs.
2.1.2 Proposed Methodology/ System Design

START

MAIN MENU
1. USER PANEL
2. ADMIN PANEL
3. EXIT

PROGRAM
EXIT

USER PANEL

VIEW PATIENT

(DISPLAY PATIENTS)

©Daffodil International University

BACK TO 2
MAIN MENU
 ADMIN PANEL

BACK TO MAIN MENU

UPDATE PATIENT

SCARCH
PATIENT

DISPLAY
PATIENT

ADD PATIENT

Figure 2.1: This is a sample diagram

2.1.3 UI Design

The user interface (UI) will be simple and text-based. This means users will interact with the system
through text menus, and they’ll select options to perform tasks like adding or viewing patient
records. The UI will be designed to be easy to understand, with clear instructions and error messages
to help the user if something goes wrong.

©Daffodil International University 3

 2.2 Overall Project Plan
The project will be completed in several steps:

• Phase 1: Planning and Gathering Requirements (1 week)

• Understand the needs of the users and plan the project.
• Phase 2: Designing the System (2 weeks)
• Create the system’s structure and design the user interface.
• Phase 3: Writing the Code (4 weeks)
• Write the code for adding, searching, updating, and displaying patient records.
• Phase 4: Testing the System (2 weeks)
• Check everything to make sure it works and fix any problems.
• Phase 5: Deploying and Documenting (1 week)
• Make the system ready for use and prepare the final report.
• Phase 6: Maintenance (Ongoing)
• Provide support and fix any issues after the system is in use.

©Daffodil International University 4

 Chapter 3

Implementation and Results

This chapter explains the development and implementation process of the Patient Records Management
System, covering the design of core features and the technical details involved. It also evaluates the
performance, presents the results of the system’s functionality, and discusses potential improvements.

3.1 Implementation
• Design:
• The struct Patient in the code is used to store details like name, age,
gender, contact, and medicalHistory.
• The array patients[MAX_PATIENTS] handles multiple patient records.
• Features:
• Functions in the code (addPatient, displayPatients, searchPatient,
updatePatient) perform core tasks like adding, viewing, searching, and
updating patient records.
• File handling was mentioned as a potential addition, but if needed, it
can be implemented in a similar way (e.g., saving/loading from a file).
• Interface:
• The menu in the main function provides options to navigate through the
functionalities, matching the described interface.

3.2 Performance Analysis

• Speed:

• The code uses an array, so adding/updating is quick since it directly uses

array indexing. Searching uses a linear loop (for loop in searchPatient), which
gets slower as more records are added.

• Memory:

• The array has a fixed size (MAX_PATIENTS = 100), which limits the
number of records. File handling can be added to address memory concerns.

• Limitations:

• The fixed-size array is a limitation, and the searching process could be

optimized for larger datasets.

©Daffodil International University 5

 3.3 Results and Discussion
• Results:
• The code successfully performs all key functionalities: adding, displaying, searching, and
updating records.
• Discussion:
• The code demonstrates a basic but functional system for patient record management. It provides a
good foundation, and additional features like file handling, dynamic memory, or database integration can
enhance it.

©Daffodil International University 6

 Chapter 4

Engineering Standards and Mapping

This chapter discusses how the project aligns with engineering standards and its broader impact. It examines
the societal, environmental, and ethical implications of the system, explores sustainability, evaluates project
management practices, and maps the project outcomes to complex engineering problem criteria.

4.1 Impact on Society, Environment and Sustainability

4.1.1 Impact on Life
Explains how the project improves patient record management, enhancing healthcare
efficiency and patient outcomes.
4.1.2 Impact on Society & Environment
Discusses how the system minimizes errors in medical data handling, potentially reducing
environmental waste caused by paper records.
4.1.3 Ethical Aspects
Covers patient data privacy, security, and adherence to ethical guidelines in record management.
4.1.4 Sustainability Plan
Outlines how the system supports long-term goals by using digital records to reduce
reliance on physical storage and paperwork

4.2 Project Management and Team Work

This project was a collaborative effort involving six team members, each responsible for specific components
of the Patient Records Management System. We divided the tasks in a way that allowed each member to
focus on distinct aspects of the project while ensuring seamless integration of all components. The team
worked together to meet the project requirements and deliver a functional and efficient system.
Team Responsibilities:
 Md.Abdulla: Responsible for defining the Patient structure and the global declarations such as
MAX_PATIENTS and function prototypes.
 Md.Sariful Islam: Implemented the main function, including the main menu and navigation logic
between the user and admin panels.
 Tanzim Ahmed: Developed the User Panel, enabling users to view patient records and return to the
main menu.
 Nur A Monjil Arvi: Designed the Admin Panel, including functionalities for adding, displaying,
searching, and updating patient records.
 Farhana Mehrin Rimu: Handled the patient addition and update functionalities, ensuring proper
input and validation of patient data.
 Samia Bushra Prapti: Implemented the display and search patient functionalities, ensuring users
and admins can view and search patient records efficiently.
Challenges and Solutions:
 Challenge: Dividing the tasks effectively to ensure each member was working on a well-defined
portion of the project. Solution: We carefully planned the project structure, allocated tasks based on
individual strengths, and held regular meetings to monitor progress.
 Challenge: Integrating individual components into a fully functional system.
 Solution: The team worked together to resolve integration issues by reviewing each other’s code and
performing thorough testing to ensure compatibility across all sections.
In conclusion, the project was a successful result of teamwork, cooperation, and effective division of tasks.
©Daffodil International University 7
Each member played a crucial role in completing the Patient Records Management System, and we learned
valuable lessons in communication, collaboration, and problem-solving throughout the development process.

4.3 Complex Engineering Problem

4.3.1 Mapping of Program Outcome
Links project achievements to specific program outcomes, such as problem-solving,
sustainable design, teamwork, and adherence to professional engineering standards.

Table 4.3.2: Mapping with complex problem solving.

©Daffodil International University 8

 EP2 EP3 EP4 EP6
EP1 Depth of Familiarity EP5 Extent EP7
Range of Extent of
Dept of Conflicting Analysis of Issues Of Inter-
Knowledge Requiremen Applicable Stakeholder dependence
ts Codes Involvement
.
Dept of Range of Depth of Familiarity The system Stakeholde The
Knowledge,T Conflicting Analysis,Th of adheres to rs include solution
he project Requireme e problem Issues,The basic C healthcare involves
involves nts,The was problem is programmi professiona inter-
knowledge system analyzed well-known ng ls who dependenc
of software had to by in principles require a e between
engineering meet the breaking it healthcare, and system to software
principles, C needs of down into where general file manage (code) and
programmin healthcare smaller patient handling patient hardware
g, and file profession tasks such data techniques records (storage) to
handling. als for as input manageme . efficiently. maintain a
accuracy, handling, nt is crucial functional
security, record but system.
and ease updating, challenging
of use, and .
while searching
maintainin
g
simplicity

4.3.3 Engineering Activities

In this section, provide a mapping with engineering activities. For each mapping add subsections to put
rationale (Use Table 4.3).

Table 4.3: Mapping with complex engineering activities.

EA3 EA4
EA1 EA2 Innovation EA5
Consequences for
Range of Level of Interaction society and
resources Familiarity
environment
The project used The system The system he system helps The system was
software required introduced a improve developed using
development interaction with simple yet healthcare familiar software
resources such users (healthcare effective delivery by engineering
as C workers) to approach to ensuring that methods such as
programming, understand their managing patient patient records using arrays,
file handling needs and how data digitally, are more structures, and
techniques, and the system providing a accurate, file handling for
testing tools should function. solution to a long- accessible, and data storage.

©Daffodil International University 9

 Chapter 5

Conclusion
This chapter provides a brief summary of the project, explains its current limitations, and suggests ideas
for future improvements.

5.1 Summary

The project successfully created a system to manage patient records, including

features to add, update, search, and store records.

5.2 Limitation

1. Fixed Record Limit: The system uses a fixed-size array, which limits the
number of patient records it can handle.

2. Basic Interface: The text-based menu is functional but not user-friendly for
non-technical users.

3. No Advanced Search: Searching is limited to exact matches for name or

contact number.

4. Lack of Security: There is no encryption or secure access for sensitive

patient data.

5. No Multi-User Access: The system does not support multiple users or role-
based permissions.

6. No Real-Time Data Updates: The system cannot handle

5.3 Future Work

In the future, the system can be improved by adding a database for storing more records, improving the
interface, and adding security features to protect patient data.

©Daffodil International University 1

0
 References
1. Kernighan, B. W., & Ritchie, D. M. The C Programming Language. Prentice Hall, 1988.
2. GeeksforGeeks, “C Programming Basics and File Handling.” https://www.geeksforgeeks.org.
3. TutorialsPoint, “C Programming Tutorials.” https://www.tutorialspoint.com.
4. GCC Compiler for program execution.
5. Visual Studio Code for code editing.

©Daffodil International University 1

1