High-fi Infirmary

INTRODUCTION & OBJECTIVE

    This document shows the requirement and functional document for High-fi Infirmary. It symbolizes all the needs and the requirements for the client [Global Life Clinic] to achieve a quality that is desired for the application and it contains information for the development team to design the application.

 PURPOSE OF THE PROJECT

     Its purpose is to maintain information about hospital and patients, doctors etc., It provides Interface for visitors of patients to gain information about them without visiting hospital directly.

EXISTING SYSTEM & DISADVANTAGES

    In present situation lot of hospitals maintains their personal data either by using manual records or by using computers. But they are not providing any online interface to all patients to view their personal details like test reports, deceases etc. To avoid this situation and to provide online communication between busy people to hospital management we are introducing a new portal called “High-fi Infirmary”.

 PROPOSED SYSTEM & ITS DISADVANTAGES

      This document shows the requirement and functional document for High-fi Infirmary. It symbolizes all the needs and the requirements for the client [Global Life Clinic] to achieve a quality that is desired for the application and it contains information for the development team to design the application.

 STUDY OF THE SYSTEM

To provide flexibility to the users, the interfaces have been developed that are accessible through a browser. The GUI’S at the top level have been categorized as

1. Administrative user interface
2. The operational or generic user interface

The ‘administrative user interface’ concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. These interfaces help the administrators with all the transactional states like Data insertion, Data deletion and Date updation along with the extensive data

Data search capabilities.The ‘operational or generic user interface’ helps the end users of the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information in a customized manner as per the included flexibilities

INPUT & OUTPOUT REPRESENTETION

Input design is a part of overall system design.  The main objective during the input design is as given below:

·         To produce a cost-effective method of input.

·         To achieve the highest possible level of accuracy.

·         To ensure that the input is acceptable and understood by the user.

INPUT STAGES:

The main input stages can be listed as below:

·       Data recording

·       Data transcription

·       Data conversion

·       Data verification

·       Data control

·       Data transmission

·       Data validation

·       Data correction

INPUT TYPES:

It is necessary to determine the various types of inputs.  Inputs can be categorized as follows:

·       External inputs, which are prime inputs for the system.

·       Internal inputs, which are user communications with the system.

·       Operational, which are computer department’s communications to the system?

·       Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:

At this stage choice has to be made about the input media.  To conclude about the input media consideration has to be given to;    

·       Type of input

·       Flexibility of format

·       Speed

·       Accuracy

·       Verification methods

·       Rejection rates

·       Ease of correction

·       Storage and handling requirements

·       Security

·       Easy to use

·       Portability

Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and interactive.  As

Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most suitable input device.

OUTPUT DESIGN:

In general are:

• External Outputs whose destination is outside the organization.
• Internal Outputs whose destination is with in organization and they are the User’s main interface with the computer. Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of the results for later consultation. The various types of outputs
• Operational outputs whose use is purely with in the computer department.
• Interface outputs, which involve the user in communicating directly with the system.

OUTPUT DEFINITION

The outputs should be defined in terms of the following points:

§  Type of the output

§  Content of the output

§  Format of the output

§  Location of the output

§  Frequency of the output

§  Volume of the output

§  Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable.

For Example

·         Will decimal points need to be inserted

·         Should leading zeros be suppressed.

OUTPUT MEDIA:

In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:

• The suitability for the device to the particular application.
• The need for a hard copy.
• The response time required.
• The location of the users
• The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are:   

The outputs were needed to be generated as a hard copy and as well as queries to be viewed on the screen.  Keeping in view these outputs, the format for the output is taken from the outputs, which are currently being obtained after manual processing.  The standard printer is to be used as output media for hard copies.

FUNCTIONAL REQUIREMENTS SPECIFICATION

The System has been divided into following modules:

1. Admin Module

2.Patient Module

3.Intra-network Module

4.Report Module

1.       Admin Module:

This module is designed for hospital administration department, by using this module hospital management can store any patient details who visits that hospital and also they can place all decease report details of each and every patient in this portal so that any patient can

view their details by logging in to this portal by using their username and password. This module is having following sub modules.

¨      Master

¨      Maintenance

¨      Master:

By using this module administrator can store medical practitioners (doctor) details who are working in that hospital and patient fee details who are visiting to that hospital.

Medical Practitioners:

This module includes information about doctors. It includes name of the doctor, his specialization of medicine, nothing but in which area he is specialized, also his address and finally his identification number is compulsory, this number will be generated automatically.

Category:

Category system is having full details of the fees structure based on the type of patients.

¨      Maintenance:

This module helps to maintain the details of the following

Patient registration

Registration of patient is very important, which helps to identify the patient with an identification number & easy retrieval of the patient records.

Consultation

Consultation holds the details of the patient’s history & family history. Details of the physical exam, the investigation, diagnostic etc. This gives the records in detail of patient medical history visit wise. This helps to go through easily the patients medical history.    

Diagnostic details

This will hold the details of the patient problem & the related doctors who have taken care of particular patient. He has to follow the schedules given by head of the department. He has to visits wards regularly according to schedule.

Certificates

It provides different varieties of certificates generally issued by the diagnostics like fitness, birth, death certificates etc., by showing these certificates doctor finalize that what problem they have & what to do next.

Visitor Details

This is use to maintain the details of the visitors. Visiting hours have to be validated to meet the patients. Here visitors are required to visit the patients only on visiting time that is allocated. In other timings, visitors are not allowed into the premises. If compulsory, then only they are allowed into the premises.

Delete Patient

By using this functionality administrator will delete patient details.

Delete Patient

By using this functionality administrator will delete Doctor Details.

2.      Patient Module:

By using this module patients can view all their report details regarding their deceases.  Mainly this module is designed for busy people, some times they can’t wait until getting all decease reports then hospital management will place their report details in the portal so that they can view their details at any time by using login id and password which are provided to them. This module consists following functionalities.

¨      Patient Details: By using this functionality any patient can view their basic details which are provided in a hospital.

¨Consultation Details: By using this functionality patient can view consultation details.

¨Diagnostics Details: By using this functionality patient can view diagnostics details.

¨Certificates: By using this functionality patient can view medical certificate details.

¨Visiting Hours: By using this functionality patient can view possible visiting hours of a hospital.

¨Doctor schedule: By using this functionality patient can view possible visiting hours of a particular consultant doctor.

¨Receipts: By using this functionality patient can view their billing details.

3. Intra-network Module:

By using this module over all hospital management staff can view the details of doctor schedule, different type of bills of hospital etc.

Doctor Schedule:

This is used to maintain the schedules of the doctor to words patient, and appointments, this will be maintained by hospital administrator only which helps to avoid confusion from doctor schedules.

Receipts:

Depending upon the category the patient is registered the consultation fee is collected & the same amount has to be entered through this receivables screen. The entire incoming amount has to be maintained by submitting through this screen.

Payments:

Hospital accounts & necessary financial statements can be generated here. It gives the details of the amounts to be paid by the hospital towards electricity bill, telephone bill, building rent, stationary, salaries and miscellaneous expenditure.

4. Reports Module:

By using this module hospital management can maintain reports on various categories. They will maintain different reports on following categories.

Registrations:

By using this functionality administrator can maintain details of all patients who are visited are admitted in that hospital.

Receipts:

Depending upon the category the patient is registered the consultation fee is collected & the same amount has to be entered through this receivables screen. The entire incoming amount has to be maintained by submitting through this functionality.

Payables:

This will take care of your personal accounting & the details of the amounts to be paid by the hospital towards electricity bill, telephone bill, building rent, stationary, salaries & miscellaneous expenditure.

 PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application. Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely with the users of the existing system to give the requirement specifications because they are the people who finally use the system.  This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements.  It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below:       

·         The system should be able to interface with the existing system

·         The system should be accurate

·         The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.

HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIREMENTS                              

PROCESSOR       :     Intel 2.0 GHz or above

HARD DISK        :     80 GB

RAM                     : 512 MB RAM.

   SOFTWARE REQUIREMENTS

OPERATING SYSTEM            : WINDOWS XP with SP2. 

LANGUAGE (FRONT END)   : JAVA (JDK1.5/1.6)

SERVER                                     : APACHE TOMCAT 5.5/6.0

WEB TECHNOLOGY              : HTML, JAVASCRIPT, CSS.

DATABASE (BACK END)        : MYSQL.

ARCHITECTURE                      : 3-TIER ARCHITECTUR