Patient Records Management System
Submitted By
Student Name Student ID
MD ABDUR 242-15-062
RAHIM
Student-2 Name Student-2 ID
Student-3 Name Student-3 ID
Student-4 Name Student-4 ID
Student-5 Name Student-5 ID
MINI LAB PROJECT REPORT
This Report Presented in Partial Fulfillment of the course CSE114:
Programming and Problem Solving in the Computer Science and
Engineering Department
DAFFODIL INTERNATIONAL UNIVERSITY
Dhaka, Bangladesh
December 3, 2024
DECLARATION
We hereby declare that this lab project has been done by us under the supervision of Mr. Saiful
Islam, Assistant Professor, 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:
Saiful Islam
Assistant Professor
Department of Computer Science and Engineering Daffodil
International University
Submitted by
MD ABDUR RAHIM
ID:242-15-062
Dept. of CSE, DIU
Student Name Student Student Name Student
ID: ID:
Dept. of CSE, DIU Dept. of CSE, DIU
Student Name Student Student Name Student
ID: ID:
Dept. of CSE, DIU Dept. of CSE, DIU
COURSE & PROGRAM OUTCOME
The following course have course outcomes as following:.
Table 1: Course Outcome Statements
CO’s Statements
CO1 Define and Relate classes, objects, members of the class, and relationships among
them needed for solving specific problems
CO2 Formulate knowledge of object-oriented programming and Java in problem solving
CO3 Analyze Unified Modeling Language (UML) models to Present a specific problem
CO4 Develop solutions for real-world complex problems applying OOP concepts while
evaluating their effectiveness based on industry standards.
Table 2: Mapping of CO, PO, Blooms, KP and CEP
CO PO Blooms KP CEP
CO1 PO1 C1, C2 KP3 EP1, EP3
CO2 PO2 C2 KP3 EP1, EP3
CO3 PO3 C4, A1 KP3 EP1, EP2
CO4 PO3 C3, C6, A3, KP4 EP1, EP3
P3
The mapping justification of this table is provided in section 4.3.1, 4.3.2 and 4.3.3.
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........................................................................................................................ 2
2 Proposed Methodology/Architecture 3
2.1 Requirement Analysis & Design Specification......................................................................... 3
2.1.1 Overview.......................................................................................................................3
2.1.2 Proposed Methodology/ System Design....................................................................... 3
2.1.3 UI Design...................................................................................................................... 4
2.2 Overall Project Plan................................................................................................................... 4-6
3 Implementation and Results 7
3.1 Implementation.......................................................................................................................... 7
3.2 Performance Analysis................................................................................................................ 7
3.3 Results and Discussion.............................................................................................................. 8
4 Engineering Standards and Mapping 9
4.1 Impact on Society, Environment and Sustainability.................................................................. 9
4.1.1 Impact on Life...............................................................................................................9
4.1.2 Impact on Society & Environment............................................................................... 9
4.1.3 Ethical Aspects..............................................................................................................9
4.1.4 Sustainability Plan........................................................................................................ 9
4.2 Project Management and Team Work........................................................................................9
4.3 Complex Engineering Problem..................................................................................................9
4.3.1 Mapping of Program Outcome..................................................................................... 9
Table of Contents Table of Contents
5 Conclusion 10
5.1 Summary....................................................................................................................................10
5.2 Limitation...................................................................................................................................10
5.3 Future Work............................................................................................................................... 10
References 11
Chapter 1
Introduction
This chapter outlines the problem statement, motivation, objectives, and a feasibility study for the
project.
1.1 Introduction
Efficient management of patient records is a critical challenge in healthcare systems, especially in
smaller facilities where manual processes dominate. This project aims to develop a digital solution
to address these challenges by providing a reliable, user-friendly, and cost-effective system.
1.2 Motivation
Manual patient record-keeping is prone to errors, delays, and inefficiencies. A digital management
system simplifies the process, ensuring faster and more accurate data handling. Solving this
problem will enhance workflow efficiency and provide a learning opportunity in system design and
programming.
1.3 Objectives
1 . To design a structured and user-friendly system for managing patient records.
2 . To provide functionalities like adding, updating, searching, and storing records.
3 . To implement data persistence using file handling.
4 . To ensure security and scalability for future enhancements.
1.4 Feasibility Study
A study of existing software revealed that they are often expensive or overly complex for
small-scale facilities. This project, leveraging basic C programming and file handling, is both
technically and economically feasible.
1.5 Gap Analysis
Existing systems either lack affordability or usability for smaller healthcare providers. This project
fills this gap by offering a lightweight and efficient solution tailored to their needs.
1.6 Project Outcome
The Patient Records Management System provides an effective solution for managing patient information
through the following outcomes:
1. Data Management:
○ Facilitates adding, updating, and retrieving patient records in an organized manner.
2. Data Persistence:
○ Ensures data is saved to and loaded from files, preserving records across sessions.
3. User-Friendly Interface:
○ A simple, text-based menu system allows users to easily navigate and perform tasks.
4. Error Handling:
○ Provides validation and error-checking to prevent invalid data entry, enhancing system
reliability.
These outcomes ensure the system is practical for small-scale patient record management while highlighting
areas for scalability and improvement in future iterations.
Chapter 2
Proposed Methodology/Architecture
This chapter describes the proposed system’s architecture and the methodology used for
development.
2.1 Requirement Analysis & Design Specification
● Data Requirements: Patient name, age, gender, contact number, and medical history.
● Functional Requirements: Add, update, search, display, and store patient records.
● Non-functional Requirements: Scalability, reliability, and user-friendliness.
2.1.1 Overview
The system is implemented in C, leveraging a struct to manage patient data, and file operations
for persistent storage.
2.1.2 Proposed Methodology/ System Design
Figure 2.1: System Design
2.1.3 UI Design
2.2 Overall Project Plan
Chapter 3
Implementation and Results
3.1 Implementation
Modules: Add, Update, Search, Display, and Save Records.
File Handling: Persistent storage through binary files.
3.2 Performance Analysis
Performance Analysis examines how efficiently the system handles operations and resources. For the Patient
Records Management System, key performance aspects include:
1. Efficiency of Operations:
○ Add Record: Executes quickly for small arrays, but performance may degrade as the array
grows.
○ Search Record: Uses linear search, with performance depending on the number of records.
○ Update Record: Relies on search efficiency and is similar in complexity.
2. File Handling:
○ Saving and loading records involve sequential processing, which depends on file size.
Optimizing file formats (e.g., binary over text) can improve speed.
3. Scalability:
○ The system is suitable for small to medium datasets but may need dynamic data structures for
larger volumes.
4. Resource Usage:
○ Memory and CPU usage are moderate,with potential spikes during searches or fill operations.
To improve, consider indexing or optimizing the search algorithm for faster processing. This analysis ensures
the system remains reliable and user-friendly.
3.3 Results and Discussion
The Patient Records Management System successfully achieves its primary objectives.
Results
1. Users can add, search, update, and display patient records effectively.
2. File handling ensures data is saved and loaded successfully, maintaining persistence.
3. A user-friendly text-based menu simplifies navigation.
Discussion
1. The system works efficiently for small datasets but may slow down as data grows due to the linear
search method.
2. Fixed array size limits scalability; dynamic structures or databases could improve this.
3. Future enhancements could include better search algorithms and a more interactive interface for
scalability and usability.
Chapter 4
Engineering Standards and Mapping
This chapter discusses the project’s societal, environmental, and ethical impacts, along with its alignment with
engineering standards.
4.1 Impact on Society, Environment and Sustainability
4.1.1 Impact on Life
Improves patient care by providing quick and accurate access to records.
4.1.2 Impact on Society & Environment
Reduces paper usage, contributing to environmental sustainability.
4.1.3 Ethical Aspects
Ensures patient data confidentiality through secure file handling practices.
4.1.4 Sustainability Plan
The system is scalable and adaptable for integration with larger healthcare management systems.
4.2 Project Management and Team Work
Cost Analysis: Estimated development costs include resources for programming and testing.
Alternate Budget: Manual record-keeping systems vs. digital implementation costs and benefits.
4.3 Complex Engineering Problem
4.3.1 Mapping of Program Outcome.
Table 4.1: Justification of Program Outcomes
PO’s Justification
PO1 Knowledge of programming applied to solve real issues.
PO2 System design aligns with user and societal needs.
PO3 Ethical considerations in data handling.
Chapter 5
Conclusion
5.1 Summary
The Patient Records Management System simplifies healthcare record-keeping and ensures efficiency and
reliability.
5.2 Limitation
Limited to a command-line interface.
Supports up to 100 records in its current state.
5.3 Future Work
Add a graphical user interface (GUI).
Implement data encryption for security.
Enable cloud storage for better accessibility.
References:
1. Kernighan, B.W., & Ritchie, D.M. The C Programming Language.
2. Epic IT Tutorials on File Handling in C.
3. Healthcare Record Management Standards Documentation.
