ExpertDoctorForum

CONTENTS
1. ABSTRACT
2. INTRODUCTION
3. DESIGN PRINCIPLES & EXPLANATION
3.1. MODULES
3.2. MODULE DESCRIPTIOIN
4. PROJECT DICTIONARY
4.1. UML DIAGRAMS
4.2. DATA DICTIONARY
5. FORMS & REPORTS
5.1. I/O SAMPLES
6. BIBILIOGRAPHY

1. ABSTRACT
Intended Target and Use : This System is mainly used by
Doctors, Dentists, Optometrists, and any medical professional. Medical
Professionals use photos on a daily basis in the practice of medicine.
Many times they run into a complicated patient and need to refer them
to another colleague or specialist.
A nice way to get a second opinion is through photos.

But then they

have to take photos print them out and mail them. Or you can email
them to an intended specialist but this can pose serious privacy issues
and can be time consuming.
This system is to solve this problem. i.e., to make it easy for
anyone to take photos, upload them to a web page that is secure and
then simply email the link to anyone.

The intended referral can then

view the pictures and enter comments at the end of the page, which are
then emailed to the user.
This can save valuable time and money and is much easier on patients
that have very limited resources.
Summary of Requirements : It is a membership based web site
that allows individuals to sign up and create an account. The basis of
the site is for members to create web pages from preformatted
templates with simple point and click. They can upload pictures and add
text to these templates.

Once they are finished they click create and

the web page is created in their folder under the root domain.

They

need to be able to password and username protect the individual web

pages they create so when someone comes to a particular page in their
folder they must enter the correct username and password in order to
view the page.
The web page that is produced should have small thumbnails of
the original images uploaded (so the page loads fast).

Then when

someone clicks on the thumbnail the actual larger picture opens in a

separate window.
After the user has created the page, they should be able to email
anyone they want to come see the page they have created. An email
should be sent to anyone the user desires.
The webpage created needs to have an open form at the bottom of the
page, where a viewer can respond to the creator within the web page.
In other words when a visitor comes to the site and views the pictures
and the text they can then enter a response in the form and then click
on a link that will email the form to the creator of the web page.

2, INTRODUCTIOIN
Present System: There are several discussion forums which provide
the facilities of mailing to the specialists, getting their suggestions and
requesting the specialists to attend the meetings. But all these facilities
were lacking the provision of mailing the page along with images of the
patients.
This will make this facility incomplete. As a specialist cannot give better
suggestions by just looking at the message of the words.
Reasons for why a new Discussion Forum is required

Text messages always give an incomplete idea about the pain or

trouble of a patient.

Mails with the pages created are not secured.

Mails get mixed up with the personal mails and are not easily
identified.

Messages which are not responded are not easily identified. There
is no alert message facility which will give intimation to the user
when a message expires.

Proposed System:

An image is equal to thousand words. It provides the facility of

photo-uploading. It also provides a best picture of the patients
problems.

This also keeps the pages created by the user secured.

Only the specialist who received the mail of the created page will
be viewing it through the password given by the user in the mail.

This also keeps the pages saved in the account of the user or the
doctor.

User is availed of other provisions like chatting with the doctor,

address book of the various specialists.

3. DESIGN PRINCIPLES & EXPLANATION

3.1. MODULES
The system is basically divided into the following modules.
1. Member Area
2. Control Panel
3.2. MODULE DESCRIPTIOIN
Members Area : When users first comes to the site they will
obviously hit the home page that will have an overall description of the
service and some marketing hype, etc. They will then click on a join
or sign up link, which will take then to the first stage in the
application.
At sign up, the user should provide all essential information. After
the user has entered all essential information it should be stored in a
database. An account will then be created for the user. This account will
create a folder under the root domain with their username.
Now that John has created his account there should be some sort
of control panel that he can log into to create pages, view user
feedback, delete pages, change usernames and passwords for different
pages, etc., The control panel should probably be located within his
folder to avoid confusion later on.
Page Creation : When user decides that he wants to create a
web page with some photos so he can get some feedback from a

colleague. He comes to the site and clicks on a LOG IN link, enters his
username and password and is then taken to his control panel.
Within his control panel there is a button that allows him to create a
new page. He clicks the button and then the wizard begins. He should
first be asked to name the page. This text will show up at the top of the
page created.
He will then be asked to choose a template. The templates should be
nothing more than simple web pages that have 2 pictures side by side
with an area for text below each one. There should be 8 templates. 2
pics, 4 pics, 6 pics, 8 pics, 10 pics, 12 pics, 14 pics, and 16 pics.
After choosing a template there should be an editor in a window
with the template inside. Within each picture spot there should be a link
that when clicked will allow john to choose a photo from his PC to be
uploaded to that spot.

User should be able to preview his page before finalizing. The preview
should have a picture in each spot and the accompanying text below
each picture.
This

application

will

be

dealing

with

sensitive

patient

information and needs a good level of security. User should be able

to choose a username and password for the web page or the folder that
will be created for it. So when a viewer comes to the page they should

be prompted for the username and password.

The application should

then check it against the set stored in the database and grant
permission to view or deny the user based on input.
When user clicks create, the application creates a unique folder within
his folder, uploads the photos to the folder, creates the HTML and saves
the photos and web page in it. (i.e., JSmith). The folder should be
named similar to the web page being created.
**Notes on the page generated. When the application creates the web
page should have a form at the bottom of EVERY page created that
allows a visitor to put his/her input in and then submit those comments
to the creator. This can be part of every template in the system.

It

needs to email the responses to the email address on file for the user
and also alert the user at their control panel that a response has been
posted to whatever web page they created. They should then be able to
view these responses from within the control panel and delete them
when they are done.
User can then select to email an alert to who ever he chooses. So if he
wants his colleague in Germany to view the pictures he can enter the
email address and send an email that will have a link to the web page in
it. The email should also send the username and password for the
particular page.

After user has created his page there should be an area in his control
panel that allows him to view, delete and edit his work. This part should
allow him to email alerts, change usernames and passwords, delete
pages (and also the associated folder and files in that folder) and
change text within the template, change pictures within the template.
Generated Pages : The people using this system will be medical
professionals. After they have created their pages and emails sent then
other medical personnel will view the pictures and provide feedback.
When a viewer comes to a generated page the first thing that should
happen is a prompt for username and password. Once they have
provided the correct pair then they can view the page.
The pictures should be smaller thumbnails of the originals. When the
viewer clicks on the picture a new window opens with the original sized
picture.
After they have reviewed the pictures and text they should then scroll to
the bottom of the page and enter their comments into a form.

This

form should ask for the viewers name and comment. The viewer, then
clicks submit and the comments will be emailed to the creator and also
saved in the database. When the creator comes to his control panel,
there should be an alert that a comment has been posted.

He/she

should then be able to click on a link and view the comment. After
reviewing the comment they should be able to delete or respond to the

comment. Once they have deleted the comment then it will be removed
from the database and the control panel.
Quick Summary
Application
-

Signup and create account

Creates unique folder on server

From control panel launch template wizard

Choose from templates

Upload pics and create text in easy editor

Username and password protect file/folder

Creates web page and stores all files for that session in unique
folder

Can send email alert to anyone, will email link and username and
password

Viewer comes to page and submits comments

Comments are emailed to user and stored for viewing at control

panel

Control Panel
-

Central member area after login

User can create, delete or edit pages

View and respond to or delete comments

Signals user when file has resided for more than 2 weeks again at
30 days

Address book with users contacts for easy emailing

4. PROJECT DICTIONARY
4.1. UML DIAGRAMS

Usecase diagram for Mailing the page

Usecase diagram for view-messages

Class diagram for Doctors discussion forum :

Class relationship diagram for doctors online discussion forum

Class relationship diagram for page creation

Class relationship diagram for mailing the page

Class relationship diagram for View-Messages

Class relationship diagram for facilities utilization

6.5.1 Sequence diagram for Page-Creation

Collaboration diagram for Page-Creation

Sequence diagram for Mailing the Pages

Collaboration diagram for Mailing the Pages

Sequence diagram for View-Messages

Collaboration diagram for View-Messages

4.2. DATA DICTIONARY

Data dictionaries are an integral component of structured analysis, since

data flow diagrams by themselves not fully describe the subject of the
investigation. The data dictionary provides additional information about
the system.
A data dictionary is a catalog - a repository - of the elements in a
system.

In a data dictionary we will find a list of all the elements

composing the data flowing through a system. The major elements are
data flows, data stores and process. The data dictionary stores details
and descriptions of these elements.
Why is a Data Dictionary important?
Analysts use data dictionaries for five important reasons:
1. To manage the detail in large systems.
2. To communicate a common meaning for all system elements.
3. To document the features of the system.
4. To facilitate analysis of the details in order to evaluate
characteristics and determine where system changes should be
made.
5. To locate errors and omissions in the system

Table Name:

Sno
1
2
3
4
5
6
7
7
8
9
10
11
12

UserDetails

Attribute
UserID
Password
First Name
LastName
Address
City
Phone
Specialization
HintQuestion
HintAnswer
Email
Hospital Name
Hospital ID

Data Type
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alphabetic
Alpha-Numeric
Alphabetic
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alphabetic
Numeric

Key constraint
Required
Required
Required
Not Required
Not Required
Not Required
Not Required
Required
Required
Required
Required
Required
Required

6.1.2 Table Name:

Sno
1
2
3
4
5
6
7
8

Messages

Attribute
MessageID
FromUserID
ToUserID
DateModified
Message
Status
Subject
Filename

Table Name:

Table Name:
Sno
1
2
3

Key constraint
Required
Required
Required
Required
Required
Required
Required
Required

Data Type
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alphabetic
Alpha-Numeric
Alpha-Numeric

Key constraint
Required
Required
Required
Not Required
Not Required
Not Required
Not Required
Required

Data Type
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alphabetic

Key constraint
Required
Required
Required
Not Required
Not Required
Not Required

Data Type
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric

Key constraint
Required
Required
Required

PhoneBook

Sno
Attribute
1
PhID
2
UserID
3
Name
4
Address
5
OfficePhone
6
MobilePhone
7
ResiPhone
8
Email
Table Name:
Pages
Sno
1
2
3
4
5
6

Data Type
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alpha-Numeric
Alphabetic
Alpha-Numeric
Alpha-Numeric

Attribute
PageID
PageName
CreatedBy
UserName
CreatedOn
NoofPics
Pictures
Attribute
PicID
PageID
Filename

Comments

5. FORMS & REPORTS

5.1. I/O SAMPLES