A Project Report ON Pathology LAB Management System PDF

Preview

Summary

Download A Project Report ON Pathology LAB Management System PDF

Description

Pathology Lab Management System

A PROJECT REPORT ON Pathology Lab Management System FOR THE SESSION 2015-2016

M.J.P.ROHILKHAND UNIVERSITY, BAREILLY

BACHELOR OF COMPUTER APPLICATION SHRI KRISHNA INSTITUTE OF MANAGEMENT AND SCIENCE NH-93, BEHJOI ROAD, CHANDAUSI, DISTT SAMBHAL

SUBMITTED TO: -

SUBMITTED BY:-

MR. AMAN VARSHNEY

Srijan Manani Rollno.14640043

1

Pathology Lab Management System

DECLARATION I hereby declare that the project entitled

”Pathology Lab Management

System” submitted for the BCA Degree is my original work and the project has not formed the basis for the award of any degree, associate ship, fellowship or any other similar titles.

Place : Chandausi

Signature of the Students

Date :

Srijan Manani Rollno.14640043

2

Pathology Lab Management System

CERTIFICATE This is to certify that:Srijan Manani(14640043) Has delivered his project and submitted report On

Pathology Lab Management System Of year 2015-2016 towards the fulfillment of B.C.A. (Bachelor of Computer Application) as per M.J.P.ROHILKHAND UNIVERSITY, BAREILLY.

Mr. Aman Varshney Mr. Rajneesh Gupta (Lecturer) (H.O.D.) Date: Place: Chandausi

3

Pathology Lab Management System

Index TITLE Acknowledgement Introduction Abstract Of Project Objective System Analysis Problem Statement Feasibility Study SRS Document Project Planning Project Scheduling Gantt Chart Pert Network System Design System Coding Data Flow Diagram ER- Diagram Modules Database Design Output Screen Implementation Software Methodology Testing Maintenance Conclusion Future Scope & Further Enhancement Bibliography

4

PAGE NO 5 6 7 8 9 12 13 15 23 24 26 27 28 38 24 26 38 50 52 58 75 77 80 82 83 84

Pathology Lab Management System

ACKNOWLEDGEMENT Nothing concrete can be achieved without an optimal combination of inspiration and perspiration. No work can be accomplished without taking the guidance of the experts. It is only the views and advice from ingenious intellectual that help in the transformation of a product into a quality product. I gratefully thanks to Mr. Aman Varshney (Faculty) who has given us the opportunity our parents. They have also us throughout the development project.

5

Pathology Lab Management System

INTRODUCTION Documenting the assembly, maintenance use and troubleshooting of a system as complex as a voting system is a difficult task .A single system might combine proprietary hardware, custom operating systems and software, commodity personal computers, and pen and paper. Describing these highly varied components is one function of voting system documentation .But it is not only voting system technology that is heterogeneous; so are voting systems users, and the environments in which the systems are used. Election officials, poll workers, and voters often need guidance from documents in order to administer or use a voting system. In addition, voting system certification—the process by which a system is approved for use in state— demands evidence that a voting system complies with one or more sets of standards or guidelines. Documentation provides the details that certification bodies need to evaluate the System. Taken as a whole, voting system documentation must explain the system in several ways to meet the needs of these multiple audiences. As the modern organizations are automated and computers are working as per the instructions, it becomes essential for the coordination of human beings, commodity and computers in a modern organization. Many big cities where the life is busy needs the transaction of the goods within few minutes of time. So, this online information recorded by the distributor helps him to complete this task within the time. The administrators and all the others can communicate with the system through this project, thus facilitating effective implementation and monitoring of various activities of the voting Software.

6

Pathology Lab Management System

ABSTRACT

The Pathology Lab Management System (PLMS) is designed for Any Pathology Lab to replace their existing manual, paper based system. The new system is to control the following information; patient information, room availability, staff and operating and patient invoices. These services are to be provided in an efficient, cost effective manner, with the goal of reducing the time and resources currently required for such tasks. A significant part of the operation of any Pathology Lab involves the acquisition,

management

and

timely

retrieval

of

great

volumes

of

information. This information typically involves; patient personal information and medical history, staff information, , staff scheduling and various facilities waiting lists. All of this information must be managed in an efficient and cost wise

fashion

so

that

an institution's

resources

may

be

effectively

utilized PLMS will automate the management of the Pathology Lab making it more efficient and error free. It aims at standardizing data, consolidating data ensuring data integrity and reducing inconsistencies.

7

Pathology Lab Management System

OBJECTIVE Pathology Lab currently uses a manual system for the management and maintenance of critical information. The current system requires numerous paper forms, with data stores spread throughout the Pathology Lab management infrastructure. Often information (on forms) is incomplete, or does not follow management standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to ensure that no vital information is lost. Multiple copies of the same information exist in the Pathology Lab and may lead to inconsistencies in data in various data stores. A significant part of the operation of any Pathology Lab involves the acquisition,

management

and

timely

retrieval

of

great

volumes

of

information. This information typically involves; patient personal information and medical history, staff information, room and ward scheduling, staff scheduling, operating theater scheduling and various facilities waiting lists. All of this information must be managed in an efficient and cost wise fashion so that an institution's resources may be effectively utilized PLMS will automate the management of the pathology lab making it more efficient and error free. It aims at standardizing data, consolidating data ensuring data integrity and reducing inconsistencies.

8

Pathology Lab Management System

System Analysis 1. Existing System Pathology Labs currently use a manual system for the management and maintenance of critical information. The current system requires numerous paper forms, with data stores spread throughout the pathology lab management infrastructure. Often information (on forms) is incomplete, or does not follow management standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to ensure that no vital information is lost. Multiple copies of the same information exist in the Pathology Lab and may lead to inconsistencies in data in various data stores. 2. Proposed System The Pathology Lab Management System (PHMS) is designed for Any Pathology Lab to replace their existing manual, paper based system. The new system is to control the following information; patient information, staff and patient invoices. These services are to be provided in an efficient, cost effective manner, with the goal of reducing the time and resources currently required for such tasks.

9

Pathology Lab Management System

System Specifications

Minimum Hardware Requirements:

Pentium-IV(Processor).



256 MB Ram



512 KB Cache Memory



Hard disk 140 GB



Microsoft Compatible 101 or more Key Board

Software Requirements: 

Operating System :

Windows XP, 7



Programming language:

.NET



Web-Technology:



Front-End:

C#.NET



Back-End:

Sql Server 2008 R2



Web Server:

IIS

ASP.NET 4.0

If system, which is going to be developed, is complex in nature the goals of the entire system could not be easily comprehended. Hence the need for a more rigorous system analysis phase arose.

10

Pathology Lab Management System

User Developer

Generate Request

Managers

Problem Statement

User Interviews Domain Knowledge

Build Models

Experience Object Model Functional Model

11

Pathology Lab Management System

PROBLEM STATEMENT As per the norms of system development lifecycle is concerned. The very first step in designing a system is defining the problem. A system is a collection of entities, which work together in synergy to achieve a predefined goal and objectives. The definition phase of the system answers the question, what does the need and wants from the new system? The definition phase can be called the requirement analysis or logical design phase. We can never skip the definition phase. New system are always be evaluated, first and foremost, on whether or not it fulfilled the business requirement regardless of how impressive the technological solution be. The initial activity of definition phase is to outline the business requirements. The foundation of this activity was established in the study phase when the system improvement objectives were identified. This activity translates those objectives into inputs, outputs, and process that will be specified in greater deal during subsequent activities. The problem produced a need to change the existing system. Some of these shortcomings are being discussed below. 

Manual work is tedious and slow.



Manual work is more prone to errors.



It is difficult to keep details of heavy records.



Any task may require lot of manual intervention, which results in big loss of time.



Paper records also require huge space to store them safety.



Main problem related to security i.e. records are not secured.



The problem of personnel is big i.e. extra Staff always was a set back to the organization.

12

Pathology Lab Management System

FEASIBILITY STUDY Feasibility study is conducted once the problem is clearly understood. Feasibility study is a high level capsule version of the entire system analysis and design process.

The objective is to determine quickly at a minimum

expense how to solve a problem. The purpose of feasibility is not to solve the problem but to determine if the problem is worth solving. The system has been tested for feasibility in the following points. 1. Technical Feasibility 2. Economical Feasibility 3. Operational Feasibility.

1. Technical Feasibility The project entitles "Courier Service System” is technically feasibility because of the below mentioned feature.

The project was

developed in Java which Graphical User Interface. It provides the high level of reliability, availability and compatibility. All these make Java an appropriate language for this project. Thus the existing software Java is a powerful language. 2. Economical Feasibility The computerized system will help in automate the selection leading the profits and details of the organization. With this software, the machine and manpower utilization are expected to go up by 80-90% approximately. The costs incurred of not creating the system are set to be great, because precious time can be wanted by manually.

13

Pathology Lab Management System

3. Operational Feasibility In this project, the management will know the details of each project where he may be presented and the data will be maintained as decentralized and if any inquires for that particular contract can be known as per their requirements and necessaries.

14

Pathology Lab Management System

SOFTWARE REQUIREMENT SPECIFICATIONS The Software Requirements Specification is produced at the culmination of the analysis task. SRS is a document that completely describes what the proposed software should do without describing how the software will do it. The basic limitation for this is that the user need keeps changing as environment in which the system was to function changes with time. This leads to a request for requirement changes even after the requirement phase is done and the SRS is produced. The function and performance allocated to software as part of System Engineering are refined by: Establishing a complete information description of the System. A detailed functional description. A representation of System behavior . An indication of performance requirements and design constraints. Appropriate validation criteria, & Other information pertinent to requirements.

1. INTRODUCTION 1.1 PURPOSE The Software is for the automation of Pathology Lab Management. It maintains two levels of users: Administrator Level  User Level(patient, doctors, receptionist) The Software includes: Maintaining Patient details.  Providing Prescription, Precautions and Diet advice.  Providing and maintaining all kinds of tests for a patient.  Billing and Report generation.

1.2 Document Conventions

15

Pathology Lab Management System International Standards when adopted by a system for a universal level of Quality. The standards are designed to ensure the most effective, safe, efficient methods & process. The system’s compliances with international standards to measure how well key systems support to improve performance and manage risk effectively which give greater customer confidence.

1.3 Intended Audience and Reading Suggestions This Software Requirements document is intended for: Developers who can review project’s capabilities and more easily understand where their efforts should be targeted to improve or add more features to it (design and code the application – it sets the guidelines for future development). Project testers can use this document as a base for their testing strategy as some bugs are easier to find using a requirements document. This way testing becomes more methodically organized. End users of this application who wish to read about what this project can do.

1.4 Project Scope This Project can be used in any Pathology labs for maintaining patient details and their test results .They have provide online chatting between patient and doctor and provide the facility to online appointment.

1.5 References The official website of the project contains a brief description of the project, screenshots, links, FAQ’s and a blog with all the news of the project: http://www.pdfsam.org/ + − Project’s development and distribution website at Source forge. It provides the project’s source code, a bug reporting and tracking system, and all the available file downloads of the project: http://sourceforge.net/projects/pdfsam/ − PDF sam wiki: http://www.pdfsam.org/mediawiki/

2. Overall Description 2.1 Product Perspective  Planned approach towards working: - The working in the organization will be well planned and organized. The data will be stored properly in data stores.which will help in retrieval of information as well as its storage.

16

Pathology Lab Management System  Accuracy: - The level of accuracy in the proposed system will be higher. All operation would be done correctly and it ensures that whatever information is coming from the center is accurate.  Reliability: - The reliability of the proposed system will be high due to the above stated reasons. The reason for the increased reliability of the system is that now there would be proper storage of information.  No Redundancy: - In the proposed system utmost care would be that no information is repeated anywhere, in storage or otherwise. This would assure economic use of storage space and consistency in the data stored.  Immediate retrieval of information: - The main objective of proposed system is to provide for a quick and efficient retrieval of information. Any type of information would be available whenever the user requires.  Immediate storage of information: - In manual system there are many problems to store the largest amount of information.  Easy to Operate: - The system should be easy to operate and should be such that it can be developed within a short period of time and fit in the limited budget of the user.

2.2 Product Features This software contains the ER Diagram (Entity Relationship Diagram) and a DFD (Data Flow Diagram) with 0 and 1 level DFD. It also contains snapshots of the web pages and data tables. • Automate the existing manual system. •

Online registration of Patient.

•

Quick and fast process.

•

Provide the facility to Online Appoinment

•

Chating and mailing between doctor and patient.

•

Patient gives this feedback according to provide services by Pathology Lab.

2.3 User Classes and Characteristics This software is used five types of end user. First is Adminstrator who has right to control this software. Administrator view complaints and mark the complaint to the person complaint, can also forward the complaint to the concerned person. User classes of system are as follows:

17

Pathology Lab Management System

Administrator:Administrator is responsible for following activities:1. Add/edit doctor details. 2. Add/edit Employees details. 3. Provide shift allotement of doctors and employees. 4. Approved/Disapproved leave request of doctors and employees. 5. Approved/Disapproved Pharmacy and Accessories request. 6. Add/edit login account. Employee:1. Add/edit medicine detail. 2. Check/maintaine medicine stock 3. View own leave request and shift time. 4. Add/edit login account. Doctor:Doctor is responsible for following activities:1. Add /edit leave request. 2. View own leave request and shift duration. 3. View appointment whose approved by reception. 4. View medical history of Patients. 5. Add/edit login account. Patient:1. View own profiles. 2. View appointment status. 3. View own reports. 4. Add/edit login account. Reception:1. Add/edit accessories record.

18

Pathology Lab Management System 2. Provide the medical report of patient. 3. Check/approved the appointment status. 4. Generate the discharge report and billing. 5. Add/edit login account.

User Characteristics Every user should be:  Comfortable of working with computer.  He must have knowledge in medical field.  He must also have basic knowledge of English too.

2.5 Design and Implementation Constraints  GUI is only in English.  Login and password is used for identification of user and there is no facility for guest.  This software has one major limitation i.e. It cannot be viewed and access by unauthorized user. It can be used for limited number of users.

2.6 User Documentation The user manual...