Primary Healthcare Web Technology Application

Primary Healthcare Web Technology Application Primary health care ABSTRACT Primary Health Care is committed to helping patients take control of their health. This system is virtual, but our physicians and their dedication is real. Using secure, web-based technologies provided by Medical Web, our health-care providers offer advice and treatment for a variety of conditions. Patients can communicate securely and confidentially with our physicians throughout the treatment process using our messaging system. As a physician-owned company, we are committed to helping our patients receive the utmost care and medical attention. Primary Health Care delivers quality healthcare through innovative services. Using secure, web-based technologies provided by Medical Web, our physicians provide advice and treatment for a variety of healthcare conditions. Our services include: Treatment of Non-emergent Conditions Mental Health Naturopathic Advice Remedies Physician Advice Laboratory Interpretations All of our services are provided through the Internet in a secure and confidential manner. A secure communication portal is established between the patient and a Primary health care provider to allow one-on-one interaction. Physicians can discuss treatment options with patients and patients can respond. By building a trusting relationship, Primary health care can effectively provide a direct benefit to each and every patient. 1.1 INTRODUCTION TO PROJECT Primary health care delivers quality healthcare through innovative services. Using secure, web-based technologies provided by Medical Web, our physicians provide advice and treatment for a variety of healthcare conditions. Our services include: Treatment of Non-emergent Conditions Mental Health Naturopathic Advice Remedies Physician Advice Laboratory Interpretations All of our services are provided through the Internet in a secure and confidential manner. A secure communication portal is established between the patient and a Primary health care provider to allow one-on-one interaction. Physicians can discuss treatment options with patients and patients can respond. By building a trusting relationship, Primary health care can effectively provide a direct benefit to each and every patient. ORGANIZATION PROFILE Software Solutions is an IT solution provider for a dynamic environment where business and technology strategies converge. Their approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organizations current IT assets. Their work with large global corporations and new products or services and to implement prudent business and technology strategies in todays environment. Xxxxxxxs RANGE OF EXPERTISE INCLUDES: Software Development Services Engineering Services Systems Integration Customer Relationship Management Product Development Electronic Commerce Consulting IT Outsourcing We apply technology with innovation and responsibility to achieve two broad objectives: Effectively address the business issues our customers face today. Generate new opportunities that will help them stay ahead in the future. THIS APPROACH RESTS ON: A strategy where we architect, integrate and manage technology services and solutions we call it AIM for success. A robust offshore development methodology and reduced demand on customer resources. A focus on the use of reusable frameworks to provide cost and times benefits. They combine the best people, processes and technology to achieve excellent results consistency. We offer customers the advantages of: SPEED: They understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low risk path to achieve results. Our track record is testimony to complex projects delivered within and evens before schedule. EXPERTISE: Our teams combine cutting edge technology skills with rich domain expertise. Whats equally important they share a strong customer orientation that means they actually start by listening to the customer. Theyre focused on coming up with solutions that serve customer requirements today and anticipate future needs. A FULL SERVICE PORTFOLIO: They offer customers the advantage of being able to Architect, integrate and manage technology services. This means that they can rely on one, fully accountable source instead of trying to integrate disparate multi vendor solutions. SERVICES: Xxx is providing its services to companies which are in the field of production, quality control etc with their rich expertise and experience and information technology they are in best position to provide software solutions to distinct business requirements. 1.2 PURPOSE OF THE PROJECT The project is fully integrated with Customer Relationship Management (CRM) solution and developed in a manner that is easily manageable, time saving and relieving one form semi automated. Primary health care delivers quality healthcare through innovative services. Using secure, web-based technologies provided by Medical Web, our physicians provide advice and treatment for a variety of healthcare conditions. Our services include: Treatment of Non-emergent Conditions Mental Health Naturopathic Advice Remedies Physician Advice Laboratory Interpretations All of our services are provided through the Internet in a secure and confidential manner. A secure communication portal is established between the patient and a Primary health care provider to allow one-on-one interaction. Physicians can discuss treatment options with patients and patients can respond. By building a trusting relationship, Primary health care can effectively provide a direct benefit to each and every patient. 1.3 PROBLEM IN EXISTING SYSTEM The existing system is a manual system. Here the User of the system needs to save his information in the form of excel sheets or Disk Drives. There is no sharing is possible if the data is in the form of paper or Disk drives. There is no online appointment facility. The manual system gives us very less security for saving data; some data may be lost due to mismanagement. There is no rich user interface. Its a limited system and fewer users friendly. There is no email facility. Searching of particular information is very critical it takes lot of time. The users cannot able to restrict the information. There is no report generation. SOLUTION OF THESE PROBLEMS The development of the new system objective is to address the solutions for the drawbacks of existing problem domain. Using this new system the patient can register for making online appointment with doctor. For interaction between patient and doctor chatting has provided. By this facility patient would chat with doctor. The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach. User Friendliness is provided in the application with various controls provided by system Rich User Interface. This system provides online appointment facility. The system makes the overall project management much easier and flexible. It can be accessed over the Intranet. It provides email facility. The user information files can be stored in centralized database which can be maintained by the system. his can give the good security for user information because data is not in client machine. Authentication is provided for this application only registered users can access. It provides search facility. There is no risk of data management at any level while the project development is under process. Report generation features is provided to generate different kind of data reports. SYSTEM ANALYSIS 2.1 INTRODUCTION After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution. 2.2 ANALYSIS MODEL SDLC METHDOLOGIES This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process. SPIRAL MODEL was defined by Barry Boehm in his 1988 article, â€Å"A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models. As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project. The steps for Spiral Model can be generalized as follows: The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system. A preliminary design is created for the new system. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product. A second prototype is evolved by a fourfold procedure: Evaluating the first prototype in terms of its strengths, weakness, and risks. Defining the requirements of the second prototype. Planning an designing the second prototype. Constructing and testing the second prototype. At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customers judgment, result in a less-than-satisfactory final product. The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above. The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired. The final system is constructed, based on the refined prototype. The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time. The following diagram shows how a spiral model acts like: 2.3 STUDY OF THE SYSTEM In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browser interface. The GUIS at the top level have been categorized as Administrative user interface 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. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion and Data updating along with the extensive data search capabilities. The operational or generic user interface helps the users upon 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 helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities NUMBER OF MODULES The system after careful analysis has been identified to be presented with the following modules: Administrator Managers Doctors Patients General Public Web Registration Search Reports Authentication Administrator Administrator is treated as a super user in this system. He can have all the privileges to do anything in this system. He is the person who received the Profile of a Doctor and accept/reject the registration. He is the person who receives the Complaints from the Patient and redirects to respective Doctor for response. He should have a facility to communicate using chat, email facility with other stakeholders. He should take care of Backup of Patient, Doctor details and maintain history. He should able to add Rooms availability and Ambulance details into the site for each Hospital. Another tasks done by the administrator is he can generates reports, log files, backup, recovery of data any time. Doctors He should able to see a Patients appointment details on a particular date. Also if the Patient is already visited, able to see the previous Prescription given the Patient, Disease History, Visiting details, etc. They should be able to see the Feedback given by the Patient. They should be able to see the Complaints given by the Patient and must provide the Response for that. He should have a facility to communicate using chat, email facility with other stakeholders. Patients They should have a facility to register to the site with their Personal data along with Health details Height, Weight, Family inherited Diseases, Blood Group, etc. Being a Patient (after registration) should able to take an Appointment of a Doctor visit. They should have a facility to give Complaints about Kiosk Manager or Doctor service. They should able to Search for a Doctor and can see the Doctors Profile for an appointment. They should able to book Rooms or make request for an Ambulance to Kiosk Manager Managers He should be able to provide an Appointment of a Doctor to a Patient on request (based on Doctors available timings). They should be able to see the Complaints given by the Patient and must provide the Response for that. He should have a facility to communicate using chat, email facility with other stakeholders. They should have a Search facility to find a Patient or Doctor and can check their Profile or History details. He should to receive the Rooms Booking or request for an Ambulance of a particular Hospital and make arrangement/approve the same for a Patient. General Public General Public (i.e. Guest visitors) should able to access the site Home page, Registration Page, etc. common pages of the site. This user should able to see the Doctors Schedules, Contact details, Specialization details, etc. They should able to Search for a Doctor. They should able to see the Rooms available, Ambulance availability of a particular Hospital. Web Registration The system has a process of registration. Every User need to submit his complete details in the form of registration. Whenever a User registration completed automatically he/she can get a user id and password. By using that user id and password he/she can log into the system. Search: This system provides search facility to the patients. Patient can search for Doctors and their available timings for take appointments Reports Different kind of reports is generated by the system. Patients History and prescriptions Doctors list Lab reports Daily Monthly Reports, Appointment list of Patients for Kiosk Managers Authentication: Authentication is nothing but providing security to the system. Here every must enter into the system throw login page. The login page will restrict the UN authorized users. A user must provide his credential like user Id and password for log into the system. For that the system maintains data for all users. Whenever a user enters his user id and password, it checks in the database for user existence. If the user is exists he can be treated as a valid user. Otherwise the request will throw back. 2.4 System Requirement Specifications Hardware Requirements: PIV 2.8 GHz Processor and Above RAM 512MB and Above HDD 40 GB Hard Disk Space and Above Software Requirements: WINDOWS OS (XP / 2000 / 200 Server / 2003 Server) Visual Studio .Net 2008 Enterprise Edition Internet Information Server 5.0 (IIS) Visual Studio .Net Framework (Minimal for Deployment) version 3.5 SQL Server 2005 Enterprise Edition 2.5 PROPOSED SYSTEM To debug the existing system, remove procedures those cause data redundancy, make navigational sequence proper. To provide information about users on different level and also to reflect the current work status depending on organization. To build strong password mechanism. NEED FOR COMPUTERIZATION We all know the importance of computerization. The world is moving ahead at lightning speed and everyone is running short of time. One always wants to get the information and perform a task he/she/they desire(s) within a short period of time and too with amount of efficiency and accuracy. The application areas for the computerization have been selected on the basis of following factors: Minimizing the manual records kept at different locations. There will be more data integrity. Facilitating desired information display, very quickly, by retrieving information from users. Facilitating various statistical information which helps in decision-making? To reduce manual efforts in activities that involved repetitive work. Updating and deletion of such a huge amount of data will become easier. FUNCTIONAL FEATURES OF THE MODEL As far as the project is developed the functionality is simple, the objective of the proposal is to strengthen the functioning of Audit Status Monitoring and make them effective and better. The entire scope has been classified into five streams knows as Coordinator Level, management Level, Auditor Level, User Level and State Web Coordinator Level. The proposed software will cover the information needs with respect to each request of the user group viz. accepting the request, providing vulnerability document report and the current status of the audit. 2.6 INPUT AND OUTPUT The major inputs and outputs and major functions of the system are follows: Inputs: Admin enter his user id and password for login Admin accept the Doctor registration. User enters his user id and password for login. Patient registers for the Appointment. New user gives his completed personnel, address and phone details for registration. Administrator giving information to generate various kinds of reports. Outputs: Admin can have his own home page. Admin get all Doctors details. Admin can view all Patients details. Users enter their own home page. Admin will get the login information of a particular user. The new users data will be stored in the centralized database. Admin get the search details of different criteria. Different kind of reports is generated by administrator. 2.7 PROCESS MODEL USED WITH JUSTIFICATION ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICAION The following commands specify access control identifiers and they are typically used to authorize and authenticate the user (command codes are shown in parentheses) USER NAME (USER) The user identification is that which is required by the server for access to its file system. This command will normally be the first command transmitted by the user after the control connections are made (some servers may require this). PASSWORD (PASS) This command must be immediately preceded by the user name command, and, for some sites, completes the users identification for access control. Since password information is quite sensitive, it is desirable in general to mask it or suppress type out. Feasibility Report Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation: Technical Feasibility Operational Feasibility Economical Feasibility 3.1. TECHNICAL FEASIBILITY The technical issue usually raised during the feasibility stage of the investigation includes the following: Does the necessary technology exist to do what is suggested? Do the proposed equipments have the technical capacity to hold the data required to use the new system? Will the proposed system provide adequate response to inquiries, regardless of the number or location of users? Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of access and data security? Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System. The current system developed is technically feasible. It is a web based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The databases purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system. 3.2. OPERATIONAL FEASIBILITY Proposed projects are beneficial only if they can be turned out into information system. That will meet the organizations operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: Is there sufficient support for the management from the users? Will the system be used and work properly if it is being developed and implemented? Will there be any resistance from the user that will undermine the possible application benefits? This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits. The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status. 3.3. ECONOMICAL FEASIBILITY A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at NIC, There is nominal expenditure and economical feasibility for certain. SOFTWARE REQUIREMENT SPECIFICATION The software, Site Explorer is designed for management of web sites from a remote location. INTRODUCTION Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system. Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process. DEVELOPERS RESPONSIBILITIES OVERVIEW: The developer is responsible for: Developing the system, which meets the SRS and solving all the requirements of the system? Demonstrating the system and installing the system at clients location after the acceptance testing is successful. Submitting the required user manual describing the system interfaces to work on it and also the documents of the system. Conducting any user training that might be needed for using the system. Maintaining the system for a period of one year after installation. 4.1. FUNCTIONAL REQUIREMENTS OUTPUT DESIGN Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provides a permanent copy of the results for later consultation. The various types of outputs in general are: External Outputs, whose destination is outside the organization. Internal Outputs whose destination is within organization and they are the Users main interface with the computer. Operational outputs whose use is purely within the computer department. Interface outputs, which involve the user in communicating directly. 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 hot 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. INPUT DESIGN 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 departments 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. ERROR AVOIDANCE At this stage care is to be taken to ensure that input data remains accurate form the stage at which it is recorded up to the stage in which the data is accepted by the system. This can be achieved only by means of careful control each time the data is handled. ERROR DETECTION Even though every effort is make to avoid the occurrence of errors, still a small proportion of errors is always likely to occur, these types of errors can be discovered by using validations to check the input data. DATA VALIDATION Procedures are designed to detect errors in data at a lower level of Primary Healthcare Web Technology Application Primary Healthcare Web Technology Application Primary health care ABSTRACT Primary Health Care is committed to helping patients take control of their health. This system is virtual, but our physicians and their dedication is real. Using secure, web-based technologies provided by Medical Web, our health-care providers offer advice and treatment for a variety of conditions. Patients can communicate securely and confidentially with our physicians throughout the treatment process using our messaging system. As a physician-owned company, we are committed to helping our patients receive the utmost care and medical attention. Primary Health Care delivers quality healthcare through innovative services. Using secure, web-based technologies provided by Medical Web, our physicians provide advice and treatment for a variety of healthcare conditions. Our services include: Treatment of Non-emergent Conditions Mental Health Naturopathic Advice Remedies Physician Advice Laboratory Interpretations All of our services are provided through the Internet in a secure and confidential manner. A secure communication portal is established between the patient and a Primary health care provider to allow one-on-one interaction. Physicians can discuss treatment options with patients and patients can respond. By building a trusting relationship, Primary health care can effectively provide a direct benefit to each and every patient. 1.1 INTRODUCTION TO PROJECT Primary health care delivers quality healthcare through innovative services. Using secure, web-based technologies provided by Medical Web, our physicians provide advice and treatment for a variety of healthcare conditions. Our services include: Treatment of Non-emergent Conditions Mental Health Naturopathic Advice Remedies Physician Advice Laboratory Interpretations All of our services are provided through the Internet in a secure and confidential manner. A secure communication portal is established between the patient and a Primary health care provider to allow one-on-one interaction. Physicians can discuss treatment options with patients and patients can respond. By building a trusting relationship, Primary health care can effectively provide a direct benefit to each and every patient. ORGANIZATION PROFILE Software Solutions is an IT solution provider for a dynamic environment where business and technology strategies converge. Their approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organizations current IT assets. Their work with large global corporations and new products or services and to implement prudent business and technology strategies in todays environment. Xxxxxxxs RANGE OF EXPERTISE INCLUDES: Software Development Services Engineering Services Systems Integration Customer Relationship Management Product Development Electronic Commerce Consulting IT Outsourcing We apply technology with innovation and responsibility to achieve two broad objectives: Effectively address the business issues our customers face today. Generate new opportunities that will help them stay ahead in the future. THIS APPROACH RESTS ON: A strategy where we architect, integrate and manage technology services and solutions we call it AIM for success. A robust offshore development methodology and reduced demand on customer resources. A focus on the use of reusable frameworks to provide cost and times benefits. They combine the best people, processes and technology to achieve excellent results consistency. We offer customers the advantages of: SPEED: They understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low risk path to achieve results. Our track record is testimony to complex projects delivered within and evens before schedule. EXPERTISE: Our teams combine cutting edge technology skills with rich domain expertise. Whats equally important they share a strong customer orientation that means they actually start by listening to the customer. Theyre focused on coming up with solutions that serve customer requirements today and anticipate future needs. A FULL SERVICE PORTFOLIO: They offer customers the advantage of being able to Architect, integrate and manage technology services. This means that they can rely on one, fully accountable source instead of trying to integrate disparate multi vendor solutions. SERVICES: Xxx is providing its services to companies which are in the field of production, quality control etc with their rich expertise and experience and information technology they are in best position to provide software solutions to distinct business requirements. 1.2 PURPOSE OF THE PROJECT The project is fully integrated with Customer Relationship Management (CRM) solution and developed in a manner that is easily manageable, time saving and relieving one form semi automated. Primary health care delivers quality healthcare through innovative services. Using secure, web-based technologies provided by Medical Web, our physicians provide advice and treatment for a variety of healthcare conditions. Our services include: Treatment of Non-emergent Conditions Mental Health Naturopathic Advice Remedies Physician Advice Laboratory Interpretations All of our services are provided through the Internet in a secure and confidential manner. A secure communication portal is established between the patient and a Primary health care provider to allow one-on-one interaction. Physicians can discuss treatment options with patients and patients can respond. By building a trusting relationship, Primary health care can effectively provide a direct benefit to each and every patient. 1.3 PROBLEM IN EXISTING SYSTEM The existing system is a manual system. Here the User of the system needs to save his information in the form of excel sheets or Disk Drives. There is no sharing is possible if the data is in the form of paper or Disk drives. There is no online appointment facility. The manual system gives us very less security for saving data; some data may be lost due to mismanagement. There is no rich user interface. Its a limited system and fewer users friendly. There is no email facility. Searching of particular information is very critical it takes lot of time. The users cannot able to restrict the information. There is no report generation. SOLUTION OF THESE PROBLEMS The development of the new system objective is to address the solutions for the drawbacks of existing problem domain. Using this new system the patient can register for making online appointment with doctor. For interaction between patient and doctor chatting has provided. By this facility patient would chat with doctor. The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach. User Friendliness is provided in the application with various controls provided by system Rich User Interface. This system provides online appointment facility. The system makes the overall project management much easier and flexible. It can be accessed over the Intranet. It provides email facility. The user information files can be stored in centralized database which can be maintained by the system. his can give the good security for user information because data is not in client machine. Authentication is provided for this application only registered users can access. It provides search facility. There is no risk of data management at any level while the project development is under process. Report generation features is provided to generate different kind of data reports. SYSTEM ANALYSIS 2.1 INTRODUCTION After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution. 2.2 ANALYSIS MODEL SDLC METHDOLOGIES This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process. SPIRAL MODEL was defined by Barry Boehm in his 1988 article, â€Å"A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models. As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project. The steps for Spiral Model can be generalized as follows: The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system. A preliminary design is created for the new system. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product. A second prototype is evolved by a fourfold procedure: Evaluating the first prototype in terms of its strengths, weakness, and risks. Defining the requirements of the second prototype. Planning an designing the second prototype. Constructing and testing the second prototype. At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customers judgment, result in a less-than-satisfactory final product. The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above. The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired. The final system is constructed, based on the refined prototype. The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time. The following diagram shows how a spiral model acts like: 2.3 STUDY OF THE SYSTEM In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browser interface. The GUIS at the top level have been categorized as Administrative user interface 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. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion and Data updating along with the extensive data search capabilities. The operational or generic user interface helps the users upon 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 helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities NUMBER OF MODULES The system after careful analysis has been identified to be presented with the following modules: Administrator Managers Doctors Patients General Public Web Registration Search Reports Authentication Administrator Administrator is treated as a super user in this system. He can have all the privileges to do anything in this system. He is the person who received the Profile of a Doctor and accept/reject the registration. He is the person who receives the Complaints from the Patient and redirects to respective Doctor for response. He should have a facility to communicate using chat, email facility with other stakeholders. He should take care of Backup of Patient, Doctor details and maintain history. He should able to add Rooms availability and Ambulance details into the site for each Hospital. Another tasks done by the administrator is he can generates reports, log files, backup, recovery of data any time. Doctors He should able to see a Patients appointment details on a particular date. Also if the Patient is already visited, able to see the previous Prescription given the Patient, Disease History, Visiting details, etc. They should be able to see the Feedback given by the Patient. They should be able to see the Complaints given by the Patient and must provide the Response for that. He should have a facility to communicate using chat, email facility with other stakeholders. Patients They should have a facility to register to the site with their Personal data along with Health details Height, Weight, Family inherited Diseases, Blood Group, etc. Being a Patient (after registration) should able to take an Appointment of a Doctor visit. They should have a facility to give Complaints about Kiosk Manager or Doctor service. They should able to Search for a Doctor and can see the Doctors Profile for an appointment. They should able to book Rooms or make request for an Ambulance to Kiosk Manager Managers He should be able to provide an Appointment of a Doctor to a Patient on request (based on Doctors available timings). They should be able to see the Complaints given by the Patient and must provide the Response for that. He should have a facility to communicate using chat, email facility with other stakeholders. They should have a Search facility to find a Patient or Doctor and can check their Profile or History details. He should to receive the Rooms Booking or request for an Ambulance of a particular Hospital and make arrangement/approve the same for a Patient. General Public General Public (i.e. Guest visitors) should able to access the site Home page, Registration Page, etc. common pages of the site. This user should able to see the Doctors Schedules, Contact details, Specialization details, etc. They should able to Search for a Doctor. They should able to see the Rooms available, Ambulance availability of a particular Hospital. Web Registration The system has a process of registration. Every User need to submit his complete details in the form of registration. Whenever a User registration completed automatically he/she can get a user id and password. By using that user id and password he/she can log into the system. Search: This system provides search facility to the patients. Patient can search for Doctors and their available timings for take appointments Reports Different kind of reports is generated by the system. Patients History and prescriptions Doctors list Lab reports Daily Monthly Reports, Appointment list of Patients for Kiosk Managers Authentication: Authentication is nothing but providing security to the system. Here every must enter into the system throw login page. The login page will restrict the UN authorized users. A user must provide his credential like user Id and password for log into the system. For that the system maintains data for all users. Whenever a user enters his user id and password, it checks in the database for user existence. If the user is exists he can be treated as a valid user. Otherwise the request will throw back. 2.4 System Requirement Specifications Hardware Requirements: PIV 2.8 GHz Processor and Above RAM 512MB and Above HDD 40 GB Hard Disk Space and Above Software Requirements: WINDOWS OS (XP / 2000 / 200 Server / 2003 Server) Visual Studio .Net 2008 Enterprise Edition Internet Information Server 5.0 (IIS) Visual Studio .Net Framework (Minimal for Deployment) version 3.5 SQL Server 2005 Enterprise Edition 2.5 PROPOSED SYSTEM To debug the existing system, remove procedures those cause data redundancy, make navigational sequence proper. To provide information about users on different level and also to reflect the current work status depending on organization. To build strong password mechanism. NEED FOR COMPUTERIZATION We all know the importance of computerization. The world is moving ahead at lightning speed and everyone is running short of time. One always wants to get the information and perform a task he/she/they desire(s) within a short period of time and too with amount of efficiency and accuracy. The application areas for the computerization have been selected on the basis of following factors: Minimizing the manual records kept at different locations. There will be more data integrity. Facilitating desired information display, very quickly, by retrieving information from users. Facilitating various statistical information which helps in decision-making? To reduce manual efforts in activities that involved repetitive work. Updating and deletion of such a huge amount of data will become easier. FUNCTIONAL FEATURES OF THE MODEL As far as the project is developed the functionality is simple, the objective of the proposal is to strengthen the functioning of Audit Status Monitoring and make them effective and better. The entire scope has been classified into five streams knows as Coordinator Level, management Level, Auditor Level, User Level and State Web Coordinator Level. The proposed software will cover the information needs with respect to each request of the user group viz. accepting the request, providing vulnerability document report and the current status of the audit. 2.6 INPUT AND OUTPUT The major inputs and outputs and major functions of the system are follows: Inputs: Admin enter his user id and password for login Admin accept the Doctor registration. User enters his user id and password for login. Patient registers for the Appointment. New user gives his completed personnel, address and phone details for registration. Administrator giving information to generate various kinds of reports. Outputs: Admin can have his own home page. Admin get all Doctors details. Admin can view all Patients details. Users enter their own home page. Admin will get the login information of a particular user. The new users data will be stored in the centralized database. Admin get the search details of different criteria. Different kind of reports is generated by administrator. 2.7 PROCESS MODEL USED WITH JUSTIFICATION ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICAION The following commands specify access control identifiers and they are typically used to authorize and authenticate the user (command codes are shown in parentheses) USER NAME (USER) The user identification is that which is required by the server for access to its file system. This command will normally be the first command transmitted by the user after the control connections are made (some servers may require this). PASSWORD (PASS) This command must be immediately preceded by the user name command, and, for some sites, completes the users identification for access control. Since password information is quite sensitive, it is desirable in general to mask it or suppress type out. Feasibility Report Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation: Technical Feasibility Operational Feasibility Economical Feasibility 3.1. TECHNICAL FEASIBILITY The technical issue usually raised during the feasibility stage of the investigation includes the following: Does the necessary technology exist to do what is suggested? Do the proposed equipments have the technical capacity to hold the data required to use the new system? Will the proposed system provide adequate response to inquiries, regardless of the number or location of users? Can the system be upgraded if developed? Are there technical guarantees of accuracy, reliability, ease of access and data security? Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System. The current system developed is technically feasible. It is a web based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The databases purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at NIC or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system. 3.2. OPERATIONAL FEASIBILITY Proposed projects are beneficial only if they can be turned out into information system. That will meet the organizations operating requirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: Is there sufficient support for the management from the users? Will the system be used and work properly if it is being developed and implemented? Will there be any resistance from the user that will undermine the possible application benefits? This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits. The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status. 3.3. ECONOMICAL FEASIBILITY A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs. The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at NIC, There is nominal expenditure and economical feasibility for certain. SOFTWARE REQUIREMENT SPECIFICATION The software, Site Explorer is designed for management of web sites from a remote location. INTRODUCTION Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system. Scope: This Document plays a vital role in the development life cycle (SDLC) and it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process. DEVELOPERS RESPONSIBILITIES OVERVIEW: The developer is responsible for: Developing the system, which meets the SRS and solving all the requirements of the system? Demonstrating the system and installing the system at clients location after the acceptance testing is successful. Submitting the required user manual describing the system interfaces to work on it and also the documents of the system. Conducting any user training that might be needed for using the system. Maintaining the system for a period of one year after installation. 4.1. FUNCTIONAL REQUIREMENTS OUTPUT DESIGN Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provides a permanent copy of the results for later consultation. The various types of outputs in general are: External Outputs, whose destination is outside the organization. Internal Outputs whose destination is within organization and they are the Users main interface with the computer. Operational outputs whose use is purely within the computer department. Interface outputs, which involve the user in communicating directly. 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 hot 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. INPUT DESIGN 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 departments 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. ERROR AVOIDANCE At this stage care is to be taken to ensure that input data remains accurate form the stage at which it is recorded up to the stage in which the data is accepted by the system. This can be achieved only by means of careful control each time the data is handled. ERROR DETECTION Even though every effort is make to avoid the occurrence of errors, still a small proportion of errors is always likely to occur, these types of errors can be discovered by using validations to check the input data. DATA VALIDATION Procedures are designed to detect errors in data at a lower level of