Emergency situations happen whether we want it or not. During such emergencies requiring immediate medical attention, one would come upon assistance from the emergency line (999) for ambulance assistance. But current ambulance services in Malaysia are not efficient enough as the current emergency line resolution may take up to 20-30 minutes before the emergency call reaches the respective hospital. Additional time will be taken by the hospital to diagnose the problem through the phone in which precious time is wasted.
The Ambulance-Hospital Tracking system is envisioned with efficiency and speed of execution in mind. It is a comprehensive system which consists of the following:
An online website with a centralized database linking hospitals around Malaysia. This data will also contain data on the particular specialization of each hospital in order to better cater for specific ailments of the patient (eg: cardiology, neurosurgeon etc)
A mobile application (encapsulated in a mobile web application) used by the ambulance system with a direct link to the online website mentioned earlier via 3G / GPRS. The ambulance personnel who will access this system will have an interface to diagnose the patient on-site via a triage system. Information recorded by the ambulance personnel will be directly updated into the website, where it will then recommend the nearest hospital (with the particular specialization) to bring the patient to. Furthermore, when the ambulance is in route to the hospital, information stored in the website will allow the medical practitioner as well as the support staff at the hospital to be prepared in advance to take care of the patient upon arrival to the hospital.
The benefits of this system may be looked at as follows:
Allows the ambulance to have an advanced triage system to better diagnose the patient and to recommend on the next course of action.
Allows the hospital in which the ambulance will send the patient to, to have pre-emptive information regarding the state and condition of the patient.
Brief description of project objectives.
(i.e. scope of proposal and deliverables)
Project deliverables and Scope
Basically to solve the problems that have been mentioned above in section B it will necessitate some serious considerations and efforts to be able to execute the solution. The system that will be developed will have core functions i.e. main function, enhanced functions that will be used to wrap up the core functions and if I have the time to develop special functions that will be developed to add more reliability to the system.
Categorizing patients emergency
Locating the best possible option which is finding the closest available hospital with
Getting directions to the hospital according to UAP which directs the closes rout via the staleties and traffic reports from traffic police.
AHT system can be enhances in futures as below:
Smart pick up can be added to the system via future advance GPS options
Brief description of the resources needed by the proposal.
(i.e. hardware, software, access to information / expertise, user involvement etc.)
Hardware resources needed by the proposal:
A web server running on these current operating systems / server technologies:
Windows operating system (Linux may be considered)
Apache web server
A personal computer / notebook to access the website
A mobile device capable of the following:
Internal web browser with browsing capability
3G or GPRS connectivity (3G preferred)
Recommended to have a mobile device with touchscreen / integrated keyboard for speed of data entry (preferably a Windows Mobile / Blackberry device)
Web server applications:
Windows / Linux (for web server)
Windows Mobile / Blackberry OS (for mobile devices)
Microsoft Internet Explorer / Google Chrome / Mozilla Firefox (web browser)
Mobile web browser for mobile device (usually embedded in the mobile device)
Adobe Dreamweaver (for building the application)
Adobe Photoshop (for graphical editing)
Access to information:
Triage management and execution workflow
Database of hospitals with specialization and location data
PHP programming language
MySQL / SQL relational database management system concepts
Academic research being carried out and other information, techniques being learnt.
(i.e. what are the names of books you are going to read / data sets you are going to use)
In developing this system, there are a lot of websites, articles, and books I have to go through them in order to develop such a system. Also many researchesââ‚¬â„¢ are needed to be done. Firstly questionnaires will be prepared to the users in order to gather their ideas.
Academic research is certainly needed to pursue the success and completion of the system. Therefore, a lot of researches on many different areas have to be done. The research areas of the system might include several areas:
Since web applications are written in different web programming languages and I have selected PHP, I will need in depth knowledge on PHP programming language. Adobe dream viewer is the tool that I will be using so I need to have strong skills on PHP programming. seeking of programming language knowledge and skills, a lot of learning needs to be done by referring to many books, journals, websites and guidance from colleagues as well as my supervisor.
I might refer to several books that guide and help me in learning and developing the system such as:
The Complete Reference Java 2, Fifth Edition by Herbert Schildt.
Android Essential, FristPress by Chris Haseman.
Unlocking Android, A Developerââ‚¬â„¢s Guide By W. Frank Ableson, Charlie Collins, Robi Sen.
Java 2: The Complete Reference, Fifth Edition by Herbert Schildt.
And I might refer to some websites as well such as:
Real world methods and practice:
Search similar existing system. I have not yet found the system which is similar to my proposal.
Research on similar existing system will be carried out to determine better functions, better usability and user friendly and may be new requirements.
Questionnaires and interviews will be done to gather information and feedback to try to make the system as perfect as possible.
It is important to put in considerations that at this point in time the research is still at its beginning stage, therefore journals and white papers have still not yet been acquired. Any changes or materials that are used in guiding to the completion the project will be documented and any changes will be accordingly noted in the final documentation.
Brief description of the development plan for the proposed project.
(i.e. which software methodology and why, the major areas of functions to be developed and the order in which developed)
In order to develop this system, currently I am doing a research on the Rational Unified Process (RUP) and compare it with the other methodologies. I have yet to come up with a final solution on what methodology to be used, however the finalized methodology will be chosen either RUP which I mentioned or else will be applied to this project with applicable reasons that support the selecting of the methodology. Then, all the stages mentioned below will be following the progress of the finalized methodology. The duration of time given to each task might have some changes in the future.
Initiation stage: ( 3 weeks)
During this stage, I will identify the area that the project will be focused on. The proposal of the project will be done during this stage which describes the type of the system, reasons for why it is required and the users whom we are going to develop the system for.
Planning Stage: ( 5-6 weeks )
In this stage, I will establish a high level view of the proposed project and its goals. The Project Specification Form will be done during this stage which shows the scope, deliverables and resources of the project. Moreover, initiation planning will be shown. Then, a methodology will be selected and the initiation plan will be applied and used in the selected methodology.
Requirement Analysis Stage: ( 4 weeks )
At this stage, I will define the various project goals into functions such as a method. The requirements will be gathered from the end-user by doing questionnaire. These requirements are analyzed for their validity and the possibility of making a system that meet the users need.
Design Stage: ( 5 weeks )
Before starting the actual coding, it is extremely essential to understand what we are going to create and what it should look like. During this stage, I will lay down detailed design and process including sample screen layouts, process diagrams or pseudo code if it is required. System Design helps in specifying the overall system architecture.
Development Stage: ( 8-10 weeks )
By this stage, I will start developing the system using the language that Iââ‚¬â„¢ve appropriately chosen. The functions will be implemented with taking in consideration that the system must deliver all the functions that are specified in the Project Specification Form.
Integration and Test Stage: ( 3 weeks)
During this stage, debugging the system will be done to check for any deviation from the original system plan and design.
Installation and User Acceptance Stage: ( 2 weeks )
The system will be installed and tested by random users to identify acceptance and satisfaction of the users. The testing will be done by users who are hospital staff and emergency unit staff and I will be interviewing for my primary research. The changes will be done to ensure a successfully developed . After that, the system will be ready to use.
Brief description of the evaluation and test plan for the proposed project.
(i.e. what is the success criteria and how will be evaluated & implementation will be tested, indicate the estimated size of the demonstration/test database)
To certify that the project is a success, testing is crucial to be carried out along the development of the system. To ensure that the project is a success it has to seamlessly integrate all the different technologies together to come up with a solution. The main criteria are identified:
User acceptance and Requirement Testing
Variety of users will be allocated to test the system. They will check the entire links of the whole system. Those users will be kindly asked to give a feedback of the testing. Moreover, the feedback will have an impact on the improvement the system. This is necessary because it shows the level of acceptance of the users towards the system by looking at their feedbacks and satisfaction.
Functionality and Module Testing
Module testing is concerned with the testing of the smallest piece of software for which a separate specification exists. So, each module in the system will be tested to ensure that all the modules are running successfully and able to perform well. Making the system works perfectly as mentioned in the proposal and if it meets the user requirements will make the system success.