Aadhaar is a 12-digit unique identity number that can be obtained by residents of

India, based on their biometric and demographic data.

“Yes, patients will have the right to access their records and give consent for sharing.
But after the records have been anonymised, they will also be used for big data
analytics. The right to use the data has to be there with the government.”

demographic information includes information relating to the name, date of birth,

address and other relevant information of an individual, as may be specified by
regulations for the purpose of issuing an Aadhaar number, but shall not include race,
religion, caste, tribe, ethnicity, language, records of entitlement, income or medical
history.

A person at the meeting pointed out differences arising within the group over two major
questions in the process of finalising of the policy.

One is who will own and control the data.

“If the data is legally owned by the person to whom it belongs, one concern is that data
once ‘de-identified’ should also be available to the government and researchers,” said an
expert committee member who did not wish to be identified. “For example, for policy-
making on HIV treatment, I as a policy-maker need to know how many individuals are
HIV positive.”

De-identification is temporarily de-linking data from information that might be used to

identify a patient. Such de-identification is different from anonymisation of data.

“Since the owner of the data may not be in favour of sharing any personal information,
the legislation draft provides for anonymisation, which will destroy the identifiable
pieces of information permanently at source,” said the expert committee member.
 ADVERTISEMENT

Thus, de-identifying patient data can be reversed. This is useful for doctors to access
data when a patient returns to a hospital or visits another doctor or is incapacitated.

But the government wants to anonymise patient data, which will no longer allows the
data to be traced back to the individual, which is a more permanent de-linking.

PROJECT TITLE: PATIENT MANAGEMENT SYSTEM

Category : Web Application

PURPOSE

The health records will contain all the information related to the patient including
name, address, and the health records produced during his or her visit to the hospital
such as X-ray reports, blood test reports among others.The Software is for the
automation of Hospital Management.It maintains two levels of users:-

 Administartion level
 User level

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

SCOPE

The proposed software product is the Hospital Management System (HMS). The system
will be used to get the information from the patients and then storing that data for
future usage. The intentions of the system are to reduce over-time pay and increase the
number of patients that can be treated accurately. Requirements statements in this
document are both functional and non-functional.
DESCRIPTION

 Proposed System

This system is proposed with following modules:

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. Immediate storage of information: - In manual system there are many
problems to store the largest amount of information.
7. 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.

USER CHARACTERISTICS
The system will be used in the hospital. The administrators,front-desk staff will be the
main users. Given the condition that not all the users are computer-literate. Some users
may have to be trained on using the system. The system is also designed to be user-
friendly. It uses a Graphical User Interface (GUI).

Front-desk staff:
They all have general reception and secretarial duties. Every staff has some
basic computer training. They are responsible for patient’s check-in or notification of
appropriate people .

Administrators:
They all have post-secondary education relating to general business administration
practices. Every administrator has basic computer training. They are responsible for all
of the scheduling and updating day/night employee shifts.

ADVANTAGES OF HOSPITAL MANAGEMENT SYSTEM

1. Achieve good quality ratings: A hospital that is capable of sending and receiving
patient information and medical reports electronically always gets a higher
preference over others.
2. Better revenue management: Revenue management is a key element because
it requires a fortune to run a hospital and. It is impossible to track the same using
age-old manual systems. Automated hospital management system that is tailored
as per the business requirements can solve the purpose effectively. It offers fast
and accurate transactional and management reports that give an instant feel of
how the business is doing.
3. Avoid errors and track every single detail: Installing an automated
management system removes the chance of error completely, and you avoid
compliance issues and lawsuits, the two biggest hassles for medical centers and
hospitals.

4. Improved clinical decision-making : A good quality management system makes

sure that operational and clinical decision-making process is fast, accurate, and
efficient. With an easy, single view availability of data points, doctors, and medical
support staff gets facilitated.

5. Improve data security: A full-fledged hospital management system keeps every

bit of information secure from unauthorized access. However, it is equally
important that you implement a state-of-the-art system with centralized controls
and not a standalone home-grown system
 6. Establish your hospital as technically advanced: When a hospital is managed
by new-age hospital management system, it gets established as a techno-savvy
and modern medical center. It is highly important in the fiercely competitive
modern world that your hospital has a good reputation.

FUNCTIONAL REQUIRMENTS

1. Registration
 The HPIMS shall allow front-desk staff to add new patients to the system.
 The HPIMS shall allow front-desk staff to give each patient a ID and add
it to the patient’s record. This ID shall be used by the patient throughout
his/her stayinhospital.

2. Check out
 The administrative staff in the ward shall be allowed to delete the ID of
the patient from the system when the patient checks out.

3. Report generation
 The HPIMS shall generate reports on patients about the following
information: patient’s PHN, patient’s name, ward name, bed number and
the doctor’s name which was assigned.
 The HPIMS shall generate reports on bed availability about the following
information: ward name, bed number, occupied/unoccupied.

4. Database
 Each patient shall have the following mandatory information: first name,
last name, phone number, personal health number, address, postal code,
city, country, patient identification number.
 The HPIMS shall allow the user to update any of the patient’s information.

NON-FUNCTIONAL REQUIREMENTS

1. Security
  The system requires the patient to identify himself /herself using PHN
 Any modification (insert, delete, update) for the Database shall be
synchronized and done only by the administrator in the ward.
 Administrators shall be able to view and modify all information in
HPMS.

2. Performance Requirements
 The system shall give responses in 1 second after checking the patient’s
information.
 The user-interface screen shall respond within 5 seconds.
 The systems must conform to the Microsoft Accessibility guidelines

3. Maintainability
 The system shall provide the capability to back-up the Data
 The system shall keep a log of all the errors.
4. Reliability
 The system shall be available all the time

SOFTWARE TOOLS

 Database server: Microsoft SQL Server-2012

 Client: Internet Explorer or any web browser
 Development End: Netbeans 8.1 - IDE for Java developing.
 Programming language: java,c,c#.

DEPLOYMENT

 OS – Windows 7/8/8.1/10- Very user friendly and common OS

HARDWARE SPECIFICATION

 core i5 processor
 4GB RAM
 500GB HDD