centralized medical information system project report

8/21/2019 Centralized Medical Information System Project Report

1/40

CENTRALIZED

MEDICAL INFORMATION SYSTEM

A MINI PROJECT REPROT

Submitted by

SADEED AMEEN P O

in partial fulfillment for the award of the degree

of

DIPLOMA

in

COMPUTER ENGINEERING

FACULTY OF COMPUTER ENGINEERING

SEETHI SAHIB MEMORIAL

POLYTECHNIC COLLEGE

TIRUR – KERALA


2/40

SEETHI SAHIB MEMORIAL POLYTECHNIC COLLEGE

TIRUR-KERALA

BONAFIDE CERTIFICATE

Certified that this project report titled “CENTRALIZED MEDICAL

INFORMATION” is the bonafide work of Mr. SADEED AMEEN P O (Reg. No:

12130513) who carried out the project under my supervision. Certified further

that to the best of my knowledge the work reported herein does not form part of

any other project reports or dissertation on the basis of which a degree or award

was conferred on an earlier occasion of this or any other candidate.

Mr. ABDUL NASAR KAIPANCHERRY Mr. RAFI P

HEAD OF THE DEPARTMENT SUPERVISORCOMPUTER ENGINEERING LECTURER

S.S.M POLYTECHNIC COLLEGE COMPUTER ENGINEERING

TIRUR, MALAPPURAM S.S.M POLYTECHNIC COLLEGE

KERALA TIRUR, MALAPPURAM

KERALA

INTERNAL EXAMINER: EXTERNAL EXAMINER:

PLACE: TIRURDATE:


3/40

ABSTRACT

Medical Directory provides world class Medical facilities on click of a button. One of the mostkey features is providing online consultancy with India's best doctors having proven track

record in their specialties. With support of online Doctor NRI patients can consult online best

doctors in India for any medical consultation and can also make available their medical records

(X-rays, Ultra Sound, CT SCAN) for Indian Doctor's view through various IT tools and applications

AAPKA DOCTOR enables patients in India or overseas to experience virtual in person

consultancy with any doctor specialist in his field in any part of world.


4/40

ACKNOWLEDGMENT

I hereby acknowledge all for helping me during my working. First, I thank God, and

dedicate this software for my dear father, mother, sisters, brothers, and all my dear friends.

Without whom it would never have been accomplished.

I would like to place on record my deep sense of gratitude to Mr. ABDUL NASAR

KAIPANCHERRY, HOD-Dept. of Computer Engineering, SSM Polytechnic College Tirur, India for

his generous guidance, help and useful suggestions.

I express my sincere gratitude to Mr. RAFI P, Dept. of Computer Engineering, SSM

Polytechnic College, Tirur, India, for his stimulating guidance, continuous encouragement and

supervision throughout the course of present work.

I also wish to extend my thanks to Mr. ALI CHELAT and MUHIYUDHEEN NASAR and

other colleagues for checking my work and for their insightful comments and constructive

suggestions to improve the quality of this miniproject work.

I am extremely thankful to Mr. ABDUL SALEEM, Lecture, SSM Polytechnic College, Tirur,

for providing me infrastructural facilities to work in, without which this work would not have

been possible.

I am also extremely grateful toward my teachers, staffs, and my colleagues of Dept. of

Computer Engineering, SSM Polytechnic College, Tirur, for providing me the facilities and also

giving support for doing this miniproject.

Finally, I thank the Dept. of Computer Engineering, SSM Polytechnic College, Tirur for

giving me this opportunity and providing an environment to do miniproject.

SADEED AMEEN PO


5/40

TABLE OF CONTENTS

TITLE PAGE No.

ABSTRACT iii

LIST OF TABLES viii

LIST OF FIGURES viii

LIST OF ABBREVIATIONS ix

1 CENTRALIZED MEDICAL INFORMATION SYSTEM 1

1.1 Introduction 1

1.1.1

Purpose 11.1.2 Overview 2

1.1.3 Environmental Characteristics 3

1.2 Goals of Implementation 3

1.3 Functional Requirements 3

1.4 Non – Functional Requirements 6

2 PROJECT IMPLEMENTATION 7

2.1 Familiarization with Java – Swing 7

2.1.1 Overview 7

2.1.2 Swing Features 7

2.1.3 Popular Java Editors 8

2.1.4 Swing Controls 8

2.1.4.1 Overview 8

2.1.4.2 Swing UI Elements 9

2.1.5 Event 11

2.1.5.1 Types of Events 11

2.1.5.2 Event Handling 12

2.1.5.3 Steps in Event Handling 13

2.1.5.4 Event Object Class 13

2.1.6 Swing Event Classes 14

2.1.7 Swing Adapters 16

2.1.8 Swing Menu Controls 17

2.1.9 Swing Containers 18


6/40

2.2 MySQL – Database 19

2.2.1 Basic Commands 20

3 SYSTEM DESIGN AND CODES 22

3.1 Starting Page 223.2 Searching Page 23

3.2.1 Source Code 23

3.2.1.1 Search Button Action Event 23

3.2.2 MySQL Tables 25

3.3 Select from suggestions Page 26


3.3.1.1 English TextField Key Pressed 27

3.4 Results Page 29



3.5 Save Results Page 35


3.6 Modify words Page 36


3.6.1.1 Add Meaning Button Action Event 36

3.6.1.2 Delete from Dictionary Button Action Event 37

3.6.1.3 Add to Dictionary Button Action Event 37

3.7 Change PIN Page 39


3.7.1.1 OK Button Action Event 39


4 DATA FLOW DIAGRAM (DFD) 41

4.1 DFD for get suggestions 41

4.2 DFD for retrieving Malayalam meaning from database 42

5 CONCLUSION 43

5.1 Conclusion and Future Scope 43

REFERENCES 44


7/40

LIST OF FIGURES

Figure 2.1 UI Elements 8

Figure 2.2 Swing menu Controls 17

Figure 3.1 Starting Page 22Figure 3.2 Searching Page 23

Figure 3.3 Select from the suggestions 26

Figure 3.4 Results Page 29

Figure 3.5 Save results Page 35

Figure 3.6 Modify Words Page 36

Figure 3.7 Change PIN Page 39

Figure 4.1 DFD for get suggestions 41

Figure 4.2 DFD for retrieving Malayalam meaning from database 42

LIST OF TABLES

Table 3.1 dict 24

Table 3.2 ml_dict 27

Table 3.3 dict_conn 32

Table 3.4 locktbl 36


8/40

LIST OF ABBREVIATIONS

OS Operating System

SSM Seethi Sahib Memmorial

HOD Head of Department

DEPT Department

SRS Software Requirement Analysis

IEEE Institute of Electrical and Electronics Engineers

HDD Hard Disk Drive

GB Giga Byte

RAM Random Access Memory

IDE Integrated Development Environment

SQL Structured Query Language

PC Personnel Computer

XP Extreme Programming

GUI Graphical User Interface

API Application Programming Interface

AWT Abstract Window Toolkit

UI User Interface

GWT Google Web Toolkit

RDBMS Relational Database Management System

GNU GNU’S Not Unix

FIG Figure

DFD Data Flow Diagram

DB Database


9/40

INTRODUCTION

Medical Directory provides world class Medical facilities on click of a button.

One of the most key features is providing online consultancy with India's best

doctors having proven track record in their specialties. With support of online

Doctor NRI patients can consult online best doctors in India for any medical

consultation and can also make available their medical records (X-rays, Ultra

Sound, CT SCAN) for Indian Doctor's view through various IT tools and

applications AAPKA DOCTOR enables patients in India or overseas to experience

virtual in person consultancy with any doctor specialist in his field in any part of

world.

Main modules are

ADMIN MODULE

This module has two parts one is hospital registration and doctor registration .the

details of the doctors and the respective hospital will be shown respectively .from

the details given the patients can look through and proceed and choose their needs.

DOCTER MODULE

In this module, the doctors view their booking and notes questions send by the

patients .the doctor reply to the questions and send the prescriptions. So that the

patients could gets the ideas of these diseases and remedies for the same.


10/40

PATIENT MODULE

In this module, the patients register after which they search for the doctor and book for the consultation. They can send questions, view notes and see the

prescriptions.

1. PROPOSED SYSTEM

In our framework, there are multiple SDs, multiple owners, multiple AAs, and

multiple users. . The attribute hierarchy of files – leaf nodes is atomic file

categories while internal nodes are compound categories. Dark boxes are the

categories that a PSD’s data readers have access to. Two ABE systems are

involved: for each PSD the YWRL’s revocable KP-ABE scheme [9] is adopted;

for each PUD, our proposed revocable MA-ABE is used. We term the users having

read and write access as data readers and contributors, respectively. . The system

first defines a common universe of data attributes shared by every PSD, such as

“basic profile”, “medical history”, “allergies”, and “prescriptions”. An emergency

attribute is also defined for break-glass access. Each PHR owner’s client

application generates its corresponding public/master keys. The public keys can be

published via user’s profile in an online healthcare social-network (HSN) (which

could be part of the PHR service. There are two ways for distributing secret keys.

First, when first using the PHR service, a PHR owner can specify the access

privilege of a data reader in her PSD, and let her application generate and distribute

corresponding key to the latter,. Based on that, the policy engine of the application


11/40

automatically derives an access structure, and runs keygen of KP-ABE to generate

the user secret key that embeds her access structure. In addition, the data attributes

can be organized in a hierarchical manner for efficient policy generation. When the

user is granted all the file types under a category, her access privilege will be

represented by that category instead.

Advantages of the proposed system:

Accessibility

Much faster than existing one

User friendly.

Provides high accuracy & efficiency.

Security through encryption and authentication.

Less time consumption.

Data confidentiality.

On-demand revocation.

Flexible


12/40

2. Methodology

Waterfall Model

This is the most common and classic of life cycle models, also referred to as a

linear-sequential life cycle model. It is very simple to understand and use. In a

waterfall model, each phase must be completed in its entirety before the next phase

can begin. At the end of each phase, a review takes place to determine if the


13/40

project is on the right path and whether or not to continue or discard the

project. The phases do not overlap in a waterfall model.

Advantages

Simple and easy to use.

Easy to manage due to the rigidity of the model – each phase has specific

deliverables and a review process.

Phases are processed and completed one at a time.

Works well for smaller projects where requirements are very well

understood.

3. Platform

Software Requirements

Operating System : Windows XP/7

Front End : PHP

Back End : MySQL

Hardware Requirements


14/40

Processor : Pentium IV class processor, 450 megahertz

(MHz)

RAM : 512MB

Hard Disk : 80GB

Keyboard : 108-character keyboard

Mouse : Logitech mouse

Monitor : VGA/SVGA

4. FEASIBILITY STUDY

System Analysis and Design

Analysis involves the requirement determination and specification. First we

have to analyze the obtained resources. In the Enterprise business service engine

includes three modules Admin, Customer, Employees.

Feasibility Analysis

A feasibility study is a preliminary study undertaken to

determine and document a project's viability .Results of this study are used to make

a decision whether to proceed with the project, or not. If it indeed leads to a project

being approved, it will-before the real work of problem and the recommendation

on the best alternative.


15/40

Enterprise business service engine is an online site for the

registering complaints. This site also helps customers for getting information like

solution for their complaints. The feasibility study was carried out to find whether

the proposed system can be developed and implemented without any problem

within the time limit. The following feasibility was considered for the project in

order to ensure that the project is viable and it does not have any major

obstructions. In this regard, the following feasibility analysis was conducted.

Technical Feasibility.

Behavioral Feasibility

Economic Feasibility

TECHNICAL FEASIBILITY

In this project technical feasibility was done to find out whether thenecessary technology exist and if the equipment have the capacity to hold data

required by the use of new system.

BEHAVIORAL FEASIBILITY

When doing project in an external firm there can be in cooperation and

other unpredictable egoism from the colleagues especially when a new idea is being

introduced. These are behavioral and depend upon individual behavior of person


16/40

involved. Behavioral feasibility were done in order to analyze the attitude of the

people who are directly involved with my project.

ECONOMICAL FEASIBILITY

In this project economical feasibility were carried out to find whether

the existing resources are sufficient for doing the project. Economic feasibility also

counts any extra h/w which is required, should be affordable in terms of cost. It

also stress whether the system can be built within the specified time interval.

Establish cost and schedule constraints. Economic feasibility produced positive

result as no equipments was needed to purchase additionally.

5.

HIGH LEVEL DESIGN

The high level design of this project includes the various modules thesystem is comprised of .This is a web based application for solving customer

complaints online.

The application has three modules:

Administrator Doctor

Patient


17/40

Administrator

Hospital Registration

View Doctor List

View Patient List

View Feedback

Doctor

Patient Registration File Uploading

OP Scheduling

View Requests and Send Solution

Receipt Entry

Chat

Patient

Request for token

Request Help

Chat

6. Database design


18/40

A database is a collection of interrelated data stored with minimum

redundancy to serve many users quickly and efficiently. The general objective is to

make information access easy, quick, and inexpensive and flexible for the user. In

a database environment, common data are available in which several users can use.

The concept behind a database is an integrated collection of data and provides a

centralized access to the data from the program. It makes possible to treat data as a

separate resource.

While designing database, several objectives must be considered:

Controlled Redundancy

Data Independence

Accuracy and Integrity

Privacy and Security

Performance

7.

Tables

Login


19/40

Doctor

Patient


20/40

Hospital

Doctor Consulting Time

Patient View Consulting Time


21/40

Booking

Patient Question


22/40

Doctor Answer

Doctor Service Department


23/40

8. DATA FLOW DIAGRAMS

Level 0

Level 1

Login

Centralized Medical

Information SystemData Base

User

Login

Admin

Hospital

registration

Doctor

Registration

View Patients

Doctor

Consulting Time


24/40

Login

Login

Doctor

View Booking

Details

View Patient

Question

Chat

Change

Password


25/40

Login

Login

Patient

View Doctors

Booking

View reply

Send Question

Chat


26/40

Use case Diagram

Admin

Hospital

Registration

Doctor

Registration

Add Doctor

Consulting Time

View Patient


27/40

Doctor

View Patient

Booking

View Question

Change Password

Chat


28/40

Patient

View Doctors

Booking

Send Question

View Reply


29/40

ER Diagram

Booking

Pid

did

Patient

Email_id

pidPname

Answer

qid

pid

Dctr_id

Add

Consulting Time

TimeDoct_id

Consl id

Hosp_id

Doctor

Dname

EmailHosp_id

ADMIN Register Hospital

hname email

hregno

Register

Booking

View

Add

View

add

view

Question

pid

qid

d_id

Question


30/40

9. VALIDATION AND TESTING

Software validation is achieved through a series of tests that

demonstrate conformity with requirements. Validation succeeds when software

functions in a manner that can be reasonably expected by the end user. Testing is

necessary for the success of the system. During testing of a program to be tested is

executed with a set of test data and the output of the program for test data is

evaluated to determine if the programs are performing as expected.

First the application goes through a phase often referred as alpha

testing in which the errors and failures based on simulated user requirements are

verified and studied. The modified software is then subjected to phase two called

beta testing in the actual user’s site or live environment. After a scheduled time,

failures and errors are documented for final correction and enhancements are made

before the package is released.

In my project validation and checks have been done in order to ensure

that the developed system is performing up to its expectation. Validations have

been done in the area of registration section. In registration forms, certain rules

have been set like no field left blank. The user name should have a minimum of six

letters, password should contain a minimum of seven letters and so on. In this way

each field in the registration form are checked, checking for user name availability

and reporting status. Most of this checking is done at server side. In the login pages

appropriate messages are displayed when a user provides an invalid response.


31/40

System Testing

Testing is the process of executing the program with the intent of findingerrors. Testing cannot show the absence of defects, it can only show that software

errors are present.

Test Type

Functionality Testing.

Usability Testing.

Interface Testing.

Compatibility Testing.

1) Functionality Testing

Checked all the links:

Tested all internal links and found they are working correctly. Tested links

jumping on the same pages. This is case when one tries to upload file or photo.

Tested links used to send the feedback to administrator Checked if there are any

orphan page that is dangling pages. I performed the above test on all hypertext

links and found that they are working correctly.

Tested forms in all pages:

Forms are the integral part and so the next focus was on forms. Firstly

checked all the validations on each field like user name and password should be of


32/40

fixed length, verifying a randomly generated number code, checking whether all

mandatory fields are filled and so on.

In search utility, there is a text box and it has no button. All users have to

enter the search string and press return key. So, it has to contain a default string

“search others” to let the user know that it’s a search box. So, checks for this

default string were also made.

Checked by providing wrong inputs to the fields in the forms and found they

are responding appropriately .Wrong input include like proving an invalid user

name or password or both, no email id in mail message, no message, no body,

deliberately mistyping password in “retype passwords” and so on.

In My Profile, we can update or create profiles, so checks have been made to

ensure they are working properly that we can do the promised operation.

Database testing:

Checks have been made to ensure whether the database functions are

working. Like when a new user registers with the site there is database query

regarding this. So, these queries are tested by looking into the actual database

whether all entries have been affected to the database. If this is not the case, query

is checked and rectified. Database checking was positive.


33/40

2) Usability Testing:

Test for navigation:

Navigation means how the user surfs the web pages, different controls like

buttons, boxes or how user using the links on the pages to surf different pages.

Usability testing:

Web site should be easy to use, in my site instructions are provided clearly by various buttons, hyper links, images, and icons. This has been provided to for

easy use of the system by the end users. Checks have been made successfully if the

provided instructions are correct and help the end user in easy navigation and use

of the system.

Content Checking

Content should be logical and easy to understand. In my project pleasant

colors have been added and it is eye catchy. Every image is of fixed size. I have

also checked for spelling errors, and the overall look and feel of the site.

3) Interface Testing:

The main interfaces are:

Web server and application server interface.

Application server and Database server interface.


34/40

In this project, SQL server is used. SQL server should hold all the VB files

which will be interacting with the application logic in the ASP .NET. All these

interactions between these servers has been checked and found to be working

properly. Errors are also handled properly.

4) Compatibility Testing

Compatibility of your web site is very important testing aspect. The following

compatibility test is done:

Browser Compatibility

Some applications are very dependent on browsers. Different browsers

have different configurations and settings that our web page should be compatible

with. In my project most of the validation happens at server. The web site uses

customized CSS templates. This ensures that those pages will be displayed with the

correct layout as defined, in all browsers. This web application has been tested on

browsers like Internet explorer .They are found to be working correctly.


35/40

10. IMPLEMENTATION AND DEPLOYMENT

System implementation is the construction of the new system and the

delivery of that system into production. Implementation is the stage of the project

when the theoretical design is turned into a working system. If the implementation

stage is not properly planned and controlled, it can cause chaos. Thus it can be

considered to be the most crucial stage in achieving a successful new system and in

giving the users confidence that the new system will work and be effective. It may

involve the complete implementation of a computer complex or the introduction of

one small subsystem.

There are three type of implementation:

Fresh Implementation

Replacement implementation

Modified implementation

In this it is fresh implementation, because it is the first time this software is

used. Here the manual work done is changed and fresh software is implemented.

Implementation is not the last stage. There comes another problem of maintenance,

it is the improvement and updation of the software in response to the changes in

the organization, the activities includes in this stage are:

Correcting design errors

Correcting coding errors


36/40

Updating documentation and test data

Adding, modifying or redeveloping the code

Regular acceptance and validation test

Installation Manual

Enterprise business service engine Installation

Enterprise business service engine will work using windows server. User can

use Enterprise business service engine using web browsers like Internet explorer

6.0, Fire fox etc.

Steps

1. Install Windows 2000 or above.

For a standard server:

Pentium 133 with ACPI system BIOS available after Jan. 1999.

256 MB RAM

2 GB HD (1.2 GB free) (Windows will not install if there is less than

850 MB).

? The standard Microsoft Windows 2000 CD is bootable. Therefore, start by

placing the Windows 2000 CD in your computer and reboot.


37/40

? As computer boots it may prompt you to press any key to boot from CD. Press

any key. If you do not get this prompt or are unable to boot from the CD, please

refer to document CH000217 for information on how to boot from a CD.

? When prompted, press the enter key to setup Windows.

? If you agree with the license agreement, press the F8 key.

3. SCREEN SHOTS

4. SOURCE CODE


38/40

12. CONCLUSION

In this paper, we have proposed a novel framework of secure sharing of personal

health records in cloud computing. Considering partially trustworthy cloud

servers, we argue that to fully realize the patient-centric concept, patients shall

have complete control of their own privacy through encrypting their PHR files to

allow fine-grained access. The framework addresses the unique challenges brought

by multiple PHR owners and users, in that we greatly reduce the complexity of keymanagement while enhance the privacy guarantees compared with previous works.

We utilize ABE to encrypt the PHR data, so that patients can allow access not only

by personal users, but also various users from public domains with different

professional roles, qualifications and affiliations. Furthermore, we enhance an

existing MA-ABE scheme to handle efficient and on-demand user revocation, and

prove its security. Through implementation and simulation, we show that our

solution is both scalable and efficient.


39/40

13. BIBLIOGRAPHY

Website References:

1. www.sql.com

2. www.aspfree.com

3. www.w3schools.com

4. www.dotnetspider.com.

Book References:

Book Name Author

1. Software Engineering and Application Rogger S. Pressman

2. Complete Reference SQL James R.Groff and Paul N.Wainley


40/40

centralized medical information system project report

Documents