Project JustificationProject Definition
Problem Statement from the client point of view
A hospital requires security of all its databases to avoid hacking and crash of the information software. Hospital requires the use of secure IS system for online data accessibility and exchange of information to avoid hacking and crash of their software by hackers. To design and implement such secure medical database secure IS for exchange of information and secure medical database information system.
Medical database security is very vital for the overall security of medical information systems and networks. This is mandatory because of its widespread use and the nature of this technology today. Database security not only an essential prerequisite for effective medical care but involves fundamental ethical principles. Our research problem is to implement methodologies for the development of suitable secure medical database design for hospitals, clinics, medical professionals and patients, which is necessary prerequisite for the successful development of such systems. The required framework and requirements for medical database security are discussed, implementation plan, schedule of development, cost and parameters of the secure medical database design are presented. To overcome some of the problems currently encountered a secure medical database development methodology is presented.
List the educational objectives of the project
To get good understanding of security in implementation medical IS system.
A system is a group of works that implement plans collectively, striving for a common goal. An information system is a system that grants information to the organization at various stages, especially during decision-making. Health Information System (HIS) In a health service set up, the information system is when data collection, processing, and reporting are executed simultaneously, to provide maximum success in health service provision. Management is at its optimum throughout the various levels of service provision.
Expected Input
Expected Outcome
A trustworthy and dependable HIS system which can fabricate information that relates to health care facilities of the Ministry of Health and Population, as well as outside this institution.
Improvement of database structures so that they can be expanded with no breaks in the middle all data requirements to be amalgamated into one unified system for access.
Specific Requirements
Specify the requirements,
Functional requirements
Functional Requirements
Registration
SRS001Add patientsAllow staff to add new patients to the system.
SRS002 Assign IDAllows staff to assign each patient an ID and enter it to the patients record. The patient will use this ID throughout hisher stay in hospital.
Consultation
SRS003 Assign Ward Assign an appropriate ward to the patient by consulting nurse.
SRS004 Assign to Waiting ListIf no bed is available, assign Patient to awaiting list.
Medical matter management
SRS005Assign DoctorAssigns a doctor to a given patient.
SRS006 Assign NurseAssign a nurse to a given patient.
SRS007 Inform DoctorsUpdate doctors of new patients.
SRS008 Inform NursesUpdate nurses of new patients.
SRS009 Emergency CaseIn an emergency case, assign an emergency room, doctors and nurses to the patient right away.
SRS010 Surgery caseIn a surgery case, to assign asurgery room, surgeon and nurses to the patient.
SRS011 Generate Report (normal)Produce the patients situation record every two hours for normal patients.
SRS012Generate Report (Severe)Produce patients situation record every half hour for severe patients.
SRS013 Record procedureThe entire treatment procedure for the patientwill be recordedby the system.
SRS014 Inform patientInform the patients of available beds as soon as they become available, those who are on the bed waiting list.
Check Out
SRS015 Delete Patient IDDelete the ID of the patient from the system when the patient checks out.
SRS016 Add to beds-available listAdd the beds just evacuated in beds-available list.
Database
SRS020 Patient Mandatory Informationpatients first name, last name, phone number, personal health number, address, postal code, city, country, patient identification number.
SRS021Update Patient Informationupdate any of the patients information as described in SRS020
SRS022 Search for Patientsearch for patients information by last name or PHN or patient ID.
SRS023Staff Mandatory Informationstaffs identification number, first name, last name, phone number, address, postal code, city, country, employee type, duty schedule.
SRS024 Update Staff Informationupdate any of the staffs information.
SRS025Employee Informationfor employee information by last name, or ID number.
SRS026Ward Typesfour types Maternity, Surgical, Cancer and Cardiac.
SRS027 Ward Informationward name, ward number, list of rooms in ward.
SRS028 Room Informationroom number, list of beds in room, fullnot full.
SRS029 Bed Informationbed number, occupiedunoccupied, patient PHN.
SRS030 Ward Searchsearch the ward, room, and by ward number, room number and bed number respectively, or by hierarchal hyperlinks from ward to bed.
Design Constraints
SRS031 Databaseuse theMySQLDatabase,
SRS032 Operating SystemThe Development will be onWindows Vista
SRS033 Web-BasedWeb-based application.
Non-Functional Requirements
Security
SRS034 Patient Identification
SRS035 Logon ID
SRS036 ModificationAny modification (insert, delete,update) for the Database must be synchronized
SRS037Compliancecomply with the Health Authority Regulations
Performance Requirements
SRS042Response Time response time in 1 second.
SRS043 Capacity support 1000 patients information.
SRS044 User-interface The user-interface respond within 5 seconds.
SRS045 Conformity conform to the Microsoft Accessibility guidelines
Maintainability
SRS046 Back Up
SRS047 Errors
Reliability
SRS048 Availability
The HIS implementation is divided into 9 databases linked together. Following tables will be assigned to different databases as follows
Common codes (country, governorate, district, facility, drug, vaccine, etc.)
Infrastructure
Curative health care
Preventive health care
Tropical disease
Location
Performance requirements
The system is split up into control tables these help in filing the system, and give access to essential information to the software. The documentation is present in English and Arabic languages. If the software contains complex forms of data entry, they are broken down into two or more tables. All the code tables are sent to the governorate health directorates when possible, for checking. Some codes that are still not defined also exist. The FoxPro HIS is a well thought out program, although it contains areas where there is plenty of room for improvement. These include
More complete support for data entry.
Increase in flexibility and plan execution through a more normal database.
Switching of text data to Unicode coding systems.
The aim of these improvements should be to convert the system into a relational database server like Microsoft SQL Server. The best FoxPro features should be left behind during this conversion, like the styles for naming tables, the selected coding systems both national and international, and other control files in documentation.
Interface requirements (if applicable)
Security
The Software Development Life Cycle (SDLC) has four basic phases. The identification phase, development of alternatives, selection phase, and evaluation phase. Security is a critical issue at the design and coding phase of the Software Development Life Cycle (Lee, 1999). Following security methods can be employed
Threat modeling
Attack trees
Attack patterns
UMLSec
SecureUML
Security Patterns
There are multiple security risks associated with designing and coding phases of software development life cycle. Threat modeling is a security method for finding out security holes and how they might be exploited. UMLSec and SecureUML are extensions of Unified Modeling Language to identify and protect security of applications. Attack patterns, attack trees and security patterns are tools which are also used to identify and mitigate risks to computer applications.
Human factor requirements (if applicable)
Development of the proposed HIS software
Implementation Plan
Develop a system development plan,
Design system architecture
Schedule estimation
Time will be estimated according to the activities required and project phases. This HIS system development can take 3-5 months. Design architecture will take 1 week, coding will take 15-25 days, testing code for errors will take 7-14 days, final implementation can take 10-20 days, then documentation and other things 10-15 days.
Cost and resources for the project and
In HIS system development, cost is associated with different resources and time consumed in the project development and design of each phase. Cost can be reduced or increased with time and with employment of more engineers. The aim is to achieve a balance between cost and time, an optimal cost is lowest possible cost in associated time.
Cost of HIS system development will be USD 15000.
Other metrics useful in system management
Conclusion
Implementation Planschedule estimationsize estimationmilestone review scheduleaudits and walkthrough schedulefinal product deliver scheduleFinal Product
Problem Statement from the client point of view
A hospital requires security of all its databases to avoid hacking and crash of the information software. Hospital requires the use of secure IS system for online data accessibility and exchange of information to avoid hacking and crash of their software by hackers. To design and implement such secure medical database secure IS for exchange of information and secure medical database information system.
Medical database security is very vital for the overall security of medical information systems and networks. This is mandatory because of its widespread use and the nature of this technology today. Database security not only an essential prerequisite for effective medical care but involves fundamental ethical principles. Our research problem is to implement methodologies for the development of suitable secure medical database design for hospitals, clinics, medical professionals and patients, which is necessary prerequisite for the successful development of such systems. The required framework and requirements for medical database security are discussed, implementation plan, schedule of development, cost and parameters of the secure medical database design are presented. To overcome some of the problems currently encountered a secure medical database development methodology is presented.
List the educational objectives of the project
To get good understanding of security in implementation medical IS system.
A system is a group of works that implement plans collectively, striving for a common goal. An information system is a system that grants information to the organization at various stages, especially during decision-making. Health Information System (HIS) In a health service set up, the information system is when data collection, processing, and reporting are executed simultaneously, to provide maximum success in health service provision. Management is at its optimum throughout the various levels of service provision.
Expected Input
Expected Outcome
A trustworthy and dependable HIS system which can fabricate information that relates to health care facilities of the Ministry of Health and Population, as well as outside this institution.
Improvement of database structures so that they can be expanded with no breaks in the middle all data requirements to be amalgamated into one unified system for access.
Specific Requirements
Specify the requirements,
Functional requirements
Functional Requirements
Registration
SRS001Add patientsAllow staff to add new patients to the system.
SRS002 Assign IDAllows staff to assign each patient an ID and enter it to the patients record. The patient will use this ID throughout hisher stay in hospital.
Consultation
SRS003 Assign Ward Assign an appropriate ward to the patient by consulting nurse.
SRS004 Assign to Waiting ListIf no bed is available, assign Patient to awaiting list.
Medical matter management
SRS005Assign DoctorAssigns a doctor to a given patient.
SRS006 Assign NurseAssign a nurse to a given patient.
SRS007 Inform DoctorsUpdate doctors of new patients.
SRS008 Inform NursesUpdate nurses of new patients.
SRS009 Emergency CaseIn an emergency case, assign an emergency room, doctors and nurses to the patient right away.
SRS010 Surgery caseIn a surgery case, to assign asurgery room, surgeon and nurses to the patient.
SRS011 Generate Report (normal)Produce the patients situation record every two hours for normal patients.
SRS012Generate Report (Severe)Produce patients situation record every half hour for severe patients.
SRS013 Record procedureThe entire treatment procedure for the patientwill be recordedby the system.
SRS014 Inform patientInform the patients of available beds as soon as they become available, those who are on the bed waiting list.
Check Out
SRS015 Delete Patient IDDelete the ID of the patient from the system when the patient checks out.
SRS016 Add to beds-available listAdd the beds just evacuated in beds-available list.
Database
SRS020 Patient Mandatory Informationpatients first name, last name, phone number, personal health number, address, postal code, city, country, patient identification number.
SRS021Update Patient Informationupdate any of the patients information as described in SRS020
SRS022 Search for Patientsearch for patients information by last name or PHN or patient ID.
SRS023Staff Mandatory Informationstaffs identification number, first name, last name, phone number, address, postal code, city, country, employee type, duty schedule.
SRS024 Update Staff Informationupdate any of the staffs information.
SRS025Employee Informationfor employee information by last name, or ID number.
SRS026Ward Typesfour types Maternity, Surgical, Cancer and Cardiac.
SRS027 Ward Informationward name, ward number, list of rooms in ward.
SRS028 Room Informationroom number, list of beds in room, fullnot full.
SRS029 Bed Informationbed number, occupiedunoccupied, patient PHN.
SRS030 Ward Searchsearch the ward, room, and by ward number, room number and bed number respectively, or by hierarchal hyperlinks from ward to bed.
Design Constraints
SRS031 Databaseuse theMySQLDatabase,
SRS032 Operating SystemThe Development will be onWindows Vista
SRS033 Web-BasedWeb-based application.
Non-Functional Requirements
Security
SRS034 Patient Identification
SRS035 Logon ID
SRS036 ModificationAny modification (insert, delete,update) for the Database must be synchronized
SRS037Compliancecomply with the Health Authority Regulations
Performance Requirements
SRS042Response Time response time in 1 second.
SRS043 Capacity support 1000 patients information.
SRS044 User-interface The user-interface respond within 5 seconds.
SRS045 Conformity conform to the Microsoft Accessibility guidelines
Maintainability
SRS046 Back Up
SRS047 Errors
Reliability
SRS048 Availability
The HIS implementation is divided into 9 databases linked together. Following tables will be assigned to different databases as follows
Common codes (country, governorate, district, facility, drug, vaccine, etc.)
Infrastructure
Curative health care
Preventive health care
Tropical disease
Location
Performance requirements
The system is split up into control tables these help in filing the system, and give access to essential information to the software. The documentation is present in English and Arabic languages. If the software contains complex forms of data entry, they are broken down into two or more tables. All the code tables are sent to the governorate health directorates when possible, for checking. Some codes that are still not defined also exist. The FoxPro HIS is a well thought out program, although it contains areas where there is plenty of room for improvement. These include
More complete support for data entry.
Increase in flexibility and plan execution through a more normal database.
Switching of text data to Unicode coding systems.
The aim of these improvements should be to convert the system into a relational database server like Microsoft SQL Server. The best FoxPro features should be left behind during this conversion, like the styles for naming tables, the selected coding systems both national and international, and other control files in documentation.
Interface requirements (if applicable)
Security
The Software Development Life Cycle (SDLC) has four basic phases. The identification phase, development of alternatives, selection phase, and evaluation phase. Security is a critical issue at the design and coding phase of the Software Development Life Cycle (Lee, 1999). Following security methods can be employed
Threat modeling
Attack trees
Attack patterns
UMLSec
SecureUML
Security Patterns
There are multiple security risks associated with designing and coding phases of software development life cycle. Threat modeling is a security method for finding out security holes and how they might be exploited. UMLSec and SecureUML are extensions of Unified Modeling Language to identify and protect security of applications. Attack patterns, attack trees and security patterns are tools which are also used to identify and mitigate risks to computer applications.
Human factor requirements (if applicable)
Development of the proposed HIS software
Implementation Plan
Develop a system development plan,
Design system architecture
Schedule estimation
Time will be estimated according to the activities required and project phases. This HIS system development can take 3-5 months. Design architecture will take 1 week, coding will take 15-25 days, testing code for errors will take 7-14 days, final implementation can take 10-20 days, then documentation and other things 10-15 days.
Cost and resources for the project and
In HIS system development, cost is associated with different resources and time consumed in the project development and design of each phase. Cost can be reduced or increased with time and with employment of more engineers. The aim is to achieve a balance between cost and time, an optimal cost is lowest possible cost in associated time.
Cost of HIS system development will be USD 15000.
Other metrics useful in system management
Conclusion
Implementation Planschedule estimationsize estimationmilestone review scheduleaudits and walkthrough schedulefinal product deliver scheduleFinal Product
No comments:
Post a Comment