Documente Academic
Documente Profesional
Documente Cultură
Submitted by
Gaurav Chaplot
om th
May,2010
HEALTH RISK ASSESSMENT
CONTENTS
1. Preface
2. Project Profile:-
11 Company Profile
11 Project Definition
3. Software Tools:
1. About ASP.Net.
2. About JavaScript.
3. About HTML
4. Hardware Platform
5. System Analysis
1. Introduction.
2. Feasibility Study.
3. Problem analysis.
4. Need of a new system.
8. E R Diagram
12. Conclusion
13. Bibliography
PREFACE
Health Risk assessment is a scientific process of evaluating the adverse effects caused
by a substance, activity, lifestyle, or natural phenomenon.
Whereas the practices of 20th century health care were based largely on paper, there
is now a broad consensus that realizing an improved 21st century vision of health care
will require intensive use of information technology to acquire, manage, analyze, and
disseminate health care information and knowledge. Accordingly, the Administration
and Congress have been moving to encourage the adoption, connectivity, and
interoperability of health care information technology.
Formar President George W. Bush called for nationwide use of electronic medical
records by 2014 and the Department of Health and Human Services (HHS) is
involved in various aspects of achieving this goal.
COMPANY PROFILE
Fusion Outsourcing Pvt. Ltd. is leading solution provider based in Udaipur, India.
With the company’s inception in the year 2004 FUSION has set milestones in its
areas of operation. It started up with the idea of providing an offshore support to its
foreign clients in the area of process outsourcing.
Today FUSION has diversified its areas of operation in various fields which
includes:
Software development
Application Management
FUSION has a proven track record of establishing and running dedicated test labs for
their Global 1000 clients. The teams at FUSION use disciplined, mature SEI CMM
certified quality processes that have been honed
Over 1 Million person hours of project work in the field of onsite/offshore testing,
with a clear focus on areas critical to the success of such efforts. FUSION has
developed methodologies for end-to-end testing of complex systems, and has
adequate exposure to testing of systems using a client’s in-house methods. FUSION
provides robust review, testing and change control processes, ensuring cost-effective,
fast and quality deliverables through a global delivery model consisting of onsite,
near-shore and onsite / offshore execution.
Product Engeneering
Today, saving money is the primary motivation for Independent Software Vendors
(ISVs) seeking offshore outsourcing vendor relationships. Some companies, not
satisfied with potential savings of 20% to 40%, seek greater savings by opening their
own offshore product development and maintenance centers. This practice is
particularly prevalent in the high-tech sector, where companies may already have
offshore R&D centers, and in the financial services sector, where companies are
looking to reduce costs and/or better secure their internal systems. Unfortunately, the
management investment and overhead costs associated with opening a high-quality
offshore product development center that is intended to support an enterprise IT
organization rarely justifies the payoff.
Technology Consulting
Our clients are global corporations who are empowered through our value-based,
customized, and implementation-oriented approach.
When we serve our clients on IT issues, we combine our knowledge and experience in
IT with our strengths in strategy, organization, and operations. With a rich pool of
resources across the world, deep industry and business process expertise, broad global
resources and a proven track record, FUSION can mobilize the right people, skills,
and technologies to help clients improve their performance.
Web Services
Website design & development
Graphic design/Multimedia
FUSION's offers a wide range of professional graphic design services including logo
design, corporate identity development, multimedia and flash presentations.
We lay solid foundation in web design development. Keeping track of the latest
technological innovations we make good use of the most advanced web design tools,
thus ensuring the top-notch quality of the end-product and complete satisfaction of
our customers. Our step-by-step process guarantees that nothing is overlooked in the
final product.
Web applications and websites require maintenance and support as your needs change
and grow. FUSION's provides maintenance and support services freeing you from
maintaining expensive in-house support staff. We partner with our clients to help their
on line business running smoothly and error-free.
KPO Service
Financial Research & Analysis
Web applications and websites require maintenance and support as your needs change
and grow. FUSION's provides maintenance and support services freeing you from
maintaining expensive in-house support staff. We partner with our clients to help their
on line business running smoothly and error-free.
BPO Services
Call Center Services
Healthcare Services
Many companies provide complete healthcare services that cater to the healthcare
industry as a whole, these companies offers high-quality medical services at cost-
effective price but FUSION outsourcing Pvt. Ltd. offers a range of Healthcare
services that can help you achieve a faultless process giving competitive advantage.
FUSION outsourcing offers the following Healthcare services :-
Medical Coding
Medical Billing
Account Receivable
Data Management
FUSION understands that timely access to business document ensures the smooth
functioning of an organization. Today's fast pace dynamic business environment
demands that organizations adopt a document management system that keeps pace
with its growth,in the absence of which, administrators and network consultants feel
handicapped . FUSION offshore services provides you with the best in industry data
management solutions.
Data Cleansing
Data Mining
INTRODUCTION OF HRA
Health Risk Assessment (HRA) is an evolving concept defined as a systematic
collection of electronic health information about individual patients or populations. It
is a record in digital format that is capable of being shared across different health care
settings, by being embedded in network-connected enterprise-wide information
systems. Such records may include a whole range of data in comprehensive or
summary form, including demographics, medical history, medication and allergies,
immunization status, laboratory test results, radiology images, and billing
information.
Doctors and nurses spend hours every day chasing down patient charts and missing
information. Hospitals bear enormous costs associated with record filing and
overhead, as well as paper copying and printing. As difficult as the challenges of
paper-based medicine can be, the prospect of an overnight conversion to fully
electronic records can be even more unnerving.
The Health Risk Assessment (HRA) Records Management tracks activity and status
for a hospital’s paper medical records files, while additionally permitting a hospital to
integrate paper-based information with digital records quickly and easily. By uniting
paper and electronic records, hospitals gain the benefits of integrated, shared patient
information and automated workflow that are inherent with digital data.
• Cost savings. Hospitals can see substantial reductions in the costs associated with
record filing and overhead, time lost while hunting down files, and paper copying
and printing.
1. They need to surf login pages, so option of user name and password is to
display.
2. Data Manager can set Grid Page Size in pages of others roles.
3. Data Manager has Permission to set Screen setting by set that which tabs will
be appeared in pages for others role.
4. Data Manager can add new records in the Lookups section like new role,
family member, physician, medicine etc. and can set that which and how many
roles, medicines, family members etc. will be appeared in pages for others
role.
5. Data Manager can add new roles with their user name and password.
1. They need to surf login pages, so option of user name and password is to
display.
2. Employee can add new patient with patient information like patient name, date
of service, location etc. Employee can search for a particular patient by his
/her first name or last name.
3. After add new patient, Employee can update Demographic, Insurance, PCP
Consultants related information of patient.
Service to Physician:-
1. They need to surf login pages, so option of user name and password is
to display.
2. Physician can perform all actions similar to Employee.
ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors and
other programming tools, including Microsoft Visual Studio .NET. Not only does this
make Web development easier, but it also provides all the benefits that these tools
have to offer, including a GUI that developers can use to drop server controls onto a
Web page and fully integrated debugging support.
Developers can use Web Forms or XML Web services when creating an ASP.NET
application, or combine these in any way they see fit. Each is supported by the same
infrastructure that allows you to use authentication schemes, cache frequently used
data, or customize your application's configuration, to name only a few possibilities.
• Web Forms allow you to build powerful forms-based Web pages. When
building these pages, you can use ASP.NET server controls to create common
UI elements, and program them for common tasks. These controls allow you
to rapidly build a Web Form out of reusable built-in or custom components,
simplifying the code of a page. For more information, see Web Forms Pages.
For information on how to develop ASP.NET server controls, see Developing
ASP.NET Server Controls.
Each of these models can take full advantage of all ASP.NET features, as well as the
power of the .NET Framework and .NET Framework common language runtime.
These features and how you can use them are outlined as follows:
• If you have ASP development skills, the new ASP.NET programming model
will seem very familiar to you. However, the ASP.NET object model has
changed significantly from ASP, making it more structured and object-
oriented. Unfortunately this means that ASP.NET is not fully backward
compatible; almost all existing ASP pages will have to be modified to some
extent in order to run under ASP.NET. In addition, major changes to Visual
Basic .NET mean that existing ASP pages written with Visual Basic Scripting
Edition typically will not port directly to ASP.NET. In most cases, though, the
necessary changes will involve only a few lines of code. For more
information, see Migrating from ASP to ASP.NET.
• ASP.NET provides a simple model that enables Web developers to write logic
that runs at the application level. Developers can write this code in the
Global.asax text file or in a compiled class deployed as an assembly. This
logic can include application-level events, but developers can easily extend
this model to suit the needs of their Web application. For more information,
see ASP.NET Applications.
• For advanced developers who want to use APIs as powerful as the ISAPI
programming interfaces that were included with previous versions of ASP,
ASP.NET offers the IHttpHandler and IHttpModule interfaces. Implementing
the IHttpHandler interface gives you a means of interacting with the low-
level request and response services of the IIS Web server and provides
functionality much like ISAPI extensions, but with a simpler programming
model. Implementing the IHttpModule interface allows you to include
custom events that participate in every request made to your application. For
more information, see HTTP Runtime Support.
• Writing custom debug statements to your Web page can help immensely in
troubleshooting your application's code. However, they can cause
embarrassment if they are not removed. The problem is that removing the
debug statements from your pages when your application is ready to be ported
to a production server can require significant effort. ASP.NET offers the Trace
Context class, which allows you to write custom debug statements to your
pages as you develop them. They appear only when you have enabled tracing
for a page or entire application. Enabling tracing also appends details about a
request to the page, or, if you so specify, to a custom trace viewer that is
stored in the root directory of your application. For more information, see
ASP.NET Trace.
• Applications are said to be running side by side when they are installed on the
same computer but use different versions of the .NET Framework. To learn
how to use different versions of ASP.NET for separate applications on your
server, see Side-by-Side Support in ASP.NET.
• IIS 6.0 uses a new process model called worker process isolation mode, which
is different from the process model used in previous versions of IIS. ASP.NET
uses this process model by default when running on Windows Server 2003.
For information about how to migrate ASP.NET process model settings to
worker process isolation mode, see IIS 6.0 Application Isolation Modes.
The Components of .NET Framework
The .NET Framework is divided into two main components: the .NET Framework
Class Library and the Conman language Runtime.
The Common Type System defines how types are declared, used, and
managed in the runtime, and is also an important part of the runtime's support
for cross-language integration. The common type system performs the
following functions:
• Establishes a framework that helps enable cross-language integration, type
safety, and high performance code execution.
• Defines rules that languages must follow, which helps ensure that objects
written in different languages can interact with each other
The .NET Framework includes classes, interfaces, and value types that
expedite and optimize the development process and provide access to system
functionality. To facilitate interoperability between languages, the .NET
Framework types are CLS-compliant and can therefore be used from any
programming language whose compiler conforms to the common language
specification (CLS).
The .NET Framework types are the foundation on which .NET applications,
components, and controls are built. The .NET Framework includes types that
perform the following functions:
• Perform I/O.
The runtime provides a complex yet very elegant mechanism for routing requests
through this pipeline. There are a number of interrelated objects, most of which are
extensible either via sub classing or through event interfaces at almost every level of
the process, so the framework is highly extensible. Through this mechanism it’s
possible to hook into very low level interfaces such as the caching, authentication and
authorization. You can even filter content by pre or post processing requests or simply
route incoming requests that match a specific signature directly to your code or
another URL. There are a lot of different ways to accomplish the same thing, but all
of the approaches are straightforward to implement, yet provide flexibility in finding
the best match for performance and ease of development.
About ADO.NET
Most applications need data access at one point of time making it a crucial component
when working with applications. Data access is making the application interact with a
database, where all the data is stored. Different applications have different
requirements for database access. VB .NET uses ADO .NET (Active X Data Object)
as it's data access and manipulation protocol which also enables us to work with data
on the Internet. Let's take a look why ADO .NET came into picture replacing ADO.
DataSet
The dataset is a disconnected, in-memory representation of data. It can be considered
as a local copy of the relevant portions of the database. The DataSet is persisted in
memory and the data in it can be manipulated and updated independent of the
database. When the use of this DataSet is finished, changes can be made back to the
central database for updating. The data in DataSet can be loaded from any valid data
source like Microsoft SQL server database, an Oracle database or from a Microsoft
Access database.
Data Provider
The Data Provider is responsible for providing and maintaining the connection to the
database. A DataProvider is a set of related components that work together to provide
data in an efficient and performance driven manner. The .NET Framework currently
comes with two DataProviders: the SQL Data Provider which is designed only to
work with Microsoft's SQL Server 7.0 or later and the OleDb DataProvider which
allows us to connect to other types of databases like Access and Oracle. Each
DataProvider consists of the following component classes:
The DataAdapter object which populates a disconnected DataSet with data and
performs update
Has the capability to show the data. Also, gives you the UI for operations like
insert, edit, delete and look up etc. However, although this part lets you issue the
commands for CRUD, this part renders the actual duty to a lower layer called
Business Layer.
2. Business Layer
This layer is responsible for applying all business rules on the data. For an example,
this layer may reject an insert operation if the age of the voter is less than 18. So, the
rules that we want to enforce from a users point of view are confirmed in this layer.
3. Data Layer
This layer is supposed to be just a copy of your persistent storage. So, you want this
layer to be reusable across different business layers. And also, this layer is supposed
to act as an adapter between your Object Oriented world and the SQL world for the
Business Layer. This layer may have methods that actually perform CRUD
operations and provides OO interface to the Business Layer.
ABOUT JAVA SCRIPT
JavaScript is a programming language that is used to make web pages
interactive. It runs on your visitor's computer and so does not require constant
downloads from your web site.
• Hypertext is the method by which you move around on the web — by clicking
on special text called hyperlinks which bring you to the next page. The fact
that it is hyper just means it is not linear — i.e. you can go to any place on the
Internet whenever you want by clicking on links — there is no set order to do
things in.
• Markup is what HTML tags do to the text inside them. They mark it as a
certain type of text (italicized text, for example).
SQL-SERVER 2005
SQL Server 2005 Express Edition is the next version of MSDE and is a free, easy-to-
use, lightweight, and embeddable version of SQL Server 2005. Continue reading to
learn more about the benefits of SQL Server Express Edition and to download SQL
Server Management Studio.
Microsoft makes SQL Server available in multiple editions, with different feature sets
and targeting different users.
The compact edition is an embedded database engine. Unlike the other editions of
SQL Server, the SQL CE engine is based on SQL Mobile (initially designed for use
with hand-held devices) and does not share the same binaries. Due to its small size
(1MB DLL footprint), it has a markedly reduced feature set compared to the other
editions. For example, it supports a subset of the standard data types, does not support
stored procedures or Views or multiple-statement batches (among other limitations).
It is limited to 4GB maximum database size and cannot be run as a Windows service,
Compact Edition must be hosted by the application using it. The 3.5 version includes
considerable work that supports ADO.NET Synchronization Services.
SQL Server Developer Edition includes the same features as SQL Server Enterprise
Edition, but is limited by the license to be only used as a development and test system,
and not as production server. This edition is available to download by students free of
charge as a part of Microsoft's DreamSpark program.
SQL Server Enterprise Edition is the full-featured edition of SQL Server, including
both the core database engine and add-on services, while including a range of tools
for creating and managing a SQL Server cluster.
SQL Server Evaluation Edition, also known as the Trial Edition, has all the features
of the Enterprise Edition, but is limited to 180 days, after which the tools will
continue to run, but the server services will stop.
SQL Server Express Edition is a scaled down, free edition of SQL Server, which
includes the core database engine. While there are no limitations on the number of
databases or users supported, it is limited to using one processor, 1 GB memory and 4
GB database files. The entire database is stored in a single .mdf file, and thus
making it suitable for XCOPY deployment. It is intended as a replacement for MSDE.
Two additional editions provide a superset of features not in the original Express
Edition. The first is SQL Server Express with Tools, which includes SQL Server
Management Studio Basic. SQL Server Express with Advanced Services adds full-
text search capability and reporting services.
2. 1 GB RAM
3. 80 GB Hard Disk
SYSTEM ANALYSIS
1. Existing System: -
The existing system does not use any computer based system. All the jobs are done
manually. The job such as maintaining the information about the various department’s
meeting when the following meeting is organized and where it held and when, who
are the attendances and what is the final decision of the meeting. Informing all the
department member manually which is very time consuming process. Information
about the various meeting held in past is to be searched manually that takes time and
consume many resources.
At present, all the operations are carried out manually. Sometimes, information is
duplicated, filled incorrectly or missed. A new computerized system is needed to
handle all these data integrity and consistency problems that arise when system is
handled manually.
(e) The project would help in effective and systematic record keeping that
is storing and retrieving of useful data.
(f) Project will produce various reports so that management can make
decisions on the basis of these reports
3. Proposed System: -
The proposed system objectives are drawn to avoid the drawbacks of the Meeting
scheduler .The proposed system replaces inefficient process and time-consuming task
of the current system to be a simple, accurate and effective proposed system. The
objective of this project is to create a website of meeting management system and
provide services to provide every detail about the meeting that held and to be held in
the various departments. This site records all the information about the past meetings
for future use.
The system deals right from entering the records in the database to generation of the
reports. The major advantage is the increase in the speed and efficiency of the work.
Much of the tedious jobs in the old system are reduced.
4. Feasibility Study:-
Technical Feasibility: -
Hardware Requirements:-
512 MB RAM
80 GB HDD
Monitor
Keyboard
Mouse
LAN card
Modem
Internet Connection
SOFTWARE REQUIREMENTS
For Development Purpose:
ASP.NET with C#
IIS
Email Accounts
Windows XP
Internet Explorer.
Internet Connection
Mail Server
Introduction to SRS
The Software Requirements Specifications presents the overall information about the
interface, flow of data and constraints for the products.
An SRS is a document that completely describes what the proposed software should
do without describing how the software will do it. Therefore it describes the complete
external behavior of proposed software. An SRS is used to define needs and
expectations of the users. It serves as a contract document between customer and
developer. It is produced at the culmination of analysis task.
• General description
• Information description
This document, that is, software requirements specifications describes the overall
requirement that will be satisfied by the final product development. It serves as the
foundation for subsequent software engineering activities. It describes the function of
computer-based system and the constraints that will govern the development
SYSTEM DESIGN
&
DEVELOPMENT
SYSTEM DESIGN & DEVELOPMENT
Software Engineering Paradigm Applied: -
Project Planning
The key to a successful project is in the planning. Creating a project plan is the first
thing you should do when undertaking any kind of project.
Often project planning is ignored in favor of getting on with the work. However,
many people fail to realize the value of a project plan in saving time, money and
many problems.
• Ensure project includes all the work required, and only the work required,
to complete the project successfully.
• Ensure that the project will satisfy the needs for which it was undertaken.
• Ensure the most effective use of the people involved with the project.
• Quality delivery
• Customer satisfaction
• Structured
Description:-
This page is default login page of the site from here all employees, physicians and
data manager will login and proceed.
On this page the login of the HRA and logo section is arrange according to the need
of client.
This is a home page specifying the Grid View setting for the pages of others
role.
Screen Permission
This page is used by Data Manager to set that which and how many tabs will
be appeared on the pages of others role.
Look Ups
Look Ups is used to add, delete and edit items in all sections like family
member, medications and consults etc which are selected by physicians or
employees.
Add Users
This page is used to add new role with user name and password.
Change Password
Log Out
This is Data Entry home page. From here an employee can search any patient by
his/her first name or last name and can add new patient with patient information. An
employee can update any patient information by select patient from patient bar at the
left side of page alphabetically.
Insurance
PCP/Consults
Family History
Advanced Directive
Allergies
Immunization
Surgical History
Hospitalization/SNF Visits
Medications
Chief Complaint
HPI
Review of Systems
Exam/Vitals
Labs
Diagnostics
Functional Assessment
Problem List
Recommendation
Data Entry Home page Menu Descriptions
Add Users
General Description-
Add New is an interface from where an Employee can add new patient
with click on Save button after fill up the form.
Technical Description
Validations:
Mandatory Fields:
1. Last Name
2. First Name
3. Location
4. Date of Service
5. DOB
6. Reside At
7. Gender
Size Validation:
1. LastName : 50 Characters
2. FirstName : 50 Characters
4. MRN : 15 Characters
Other Validations:
Code Description:
Functionality:
On Save Button we validate where the Specific Patient already exist in our system or
not.
If Exist
Update the information and make a new admission for him
Otherwise
Insert that patient to Patient table and also make a new admission for him.
1. btn_save_Click():-
2. fun_demo_insert():-
Database Operations:
Affected Class:
csDemoGraphics.cs
Affected Function
btn_save_Click()
fun_demo_insert()
Used SP’s :
DE_Demographic_Insert()
Fields Description:
Patient Table
MRN SSN
FirstName LastName
MiddleName GenderId
DOB MaritalStatusId
Address1 Address2
City StateId
Zip Phone
Fax Cell
CreatedDate CreatedBy
CountryId CountyId
RaceId EthnicityId
SSN FirstName ,
LastName MiddleName,
GenderId DOB
MaritalStatusId Address1
Address2 City
StateId Zip
Phone Fax
Cell CreatedDate
CreatedBy CountryId
CountyId RaceId
EthnicityId ResideAtID
Demographic
General Description-
Demographic is an interface from where an Employee can update patient's
Demographic related information with click on update button.
Technical Description
All Fields Values:
Validations:
Mandatory Fields:
1. Last Name
2. First Name
3. Location
4. Date of Service
5. DOB
6. Reside At
7. Gender
Size Validation:
1. LastName : 50 Characters
2. FirstName : 50 Characters
4. MRN : 15 Characters
Other Validations:
Code Description
Functions we used to get this thing done:
1. onPadeLoad():-
Database Operations
Affected Class:
csDemoGraphics.cs
Affected Function
onPageLoad()
fun_demo_update()
Used SP’s :
DE_Dempgraphic_Update()
Fields Description:
Patient Table
MRN SSN
FirstName LastName
MiddleName GenderId
DOB MaritalStatusId
Address1 Address2
City StateId
Zip Phone
Fax Cell
CreatedDate CreatedBy
CountryId CountyId
RaceId EthnicityId
LastName MiddleName
GenderId DOB
MaritalStatusId Address1
Address2 City
StateId Zip
Phone Fax
Cell CreatedDate
CreatedBy CountryId
CountyId RaceId
EthnicityId ResideAtID
Family History
General Description-
Family History is an interface from where an Employee can add new and update patient's
Family History related information with click on update button.
Technical Description
All Fields Values:
Sr.No Field Name Field Control Field Type In DB
Code Description
Functionality:
1. btn_save_Click():
2. csfamilyinfo.FamilyInfo_Update():-
Database Operations
Affected Class:
csFamilyInfo.cs
Affected Function
btn_save_Click()
csfamilyinfo.FamilyInfo_Update()
Used SP’s :
DE_FamilyInfo_Update()
Fields Description:
PatientFamilyInfo Table
FamilyMember PatientID
AssessmentId AgeOfDath
CODEID1 CODEID2
CODEID3 CODEID4
ModifiedDate ModifiedBy
Labs
General Description-
Labs is an interface from where an Employee can add and update patient's
different Labs related information.
Validations:
Mandatory Fields:
1. Order Date
2. Order By
Code Description
Functions we used to get this thing done:
btn_save_Click():-
cslabs.LabInfo_Update()
Database Operations
Affected Class:
csLabs.cs
Affected Function
btn_save_Click()
cslabs.LabInfo_Update()
Used SP’s :
DE_Lab_CMP_Insert_Update_Delete()
Fields Description:
PatientLabCMP Table
ALTGPT ALKPHOS
ASTGOT ModifiedBy
TBI CA
GLUCOSE NA
K CL
CO2 BUN
CREATININE BUNORCREATRATIO
ALBUMIN TOTALPROTEIN
GLOBULIN AORGRATIO
PatientId OrderBy
OrderOn ModifiedDate
E Signature
General Description-
E Signature is an interface from where a physician can perform E Signature for
a patient report.
Technical Description
All Fields Values:
Mandatory Fields:
1. Signature
Code Description
Functionality:
1. btn_save_Click():
2. tblCBC_Return():-
3. Physician_Approval_insert():-
Database Operations
Affected Function
btn_save_Click()
tblCBC_Return()
Physician_Approval_insert()
Used SP’s :
PH_Approve_SignatureReturnOnPhysician()
PH_Approve_Insert()
Fields Description:
Users Table
UserId RoleId
UserName Password
RoleIdentityId SIGNATURE
PhysicianId InsuranceCompanyId
ActiveUser CreatedDate
CreatedBy Modifieddate
ModifiedBy DeletedDate
PatientPhysicianApproval Table
ApprovalId PatientId
AssessmentId UserId
ApprovalDate CreatedDate
CreatedBy ModifiedDate
Modifiedby DeletedDate
PatientPhysicianApprovalHistory Table
ApprovalHistoryId ApprovalId
PatientId AssessmentId
UserId ApprovalDate
CreatedDate CretedBy
ModifiedDate ModifiedBy
DeletedDate DeletedBy
E R DIAGRAM
E R DIAGRAM
In software engineering, an entity-relationship model (ERM) is an abstract
and conceptual representation of data. Entity-relationship modeling is a
database modeling method, used to produce a type of conceptual schema or
Testing
1) Introduction:
As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the
software system itself integrated with any applicable hardware system(s). The
purpose of integration testing is to detect any inconsistencies between the
software units that are integrated together (called assemblages) or between any
of the assemblages and the hardware. System testing is a more limiting type of
testing; it seeks to detect defects both within the "inter-assemblages" and also
within the system as a whole.
2) Testing Objective:-
A good test case is the one that has a high probability of finding an as-yet-
undiscovered error.
3) Types of Testing: -
Black box testing - Internal system design is not considered in this type of
testing. Tests are based on requirements and functionality.
White box testing - This testing is based on knowledge of the internal logic of
an application’s code. Also known as Glass box Testing. Internal software and
code working should be known for this type of testing. Tests are based on
coverage of code statements, branches, paths, conditions.
Functional testing - This type of testing ignores the internal parts and focus
on the output is as per requirement or not. Black-box type testing geared to
functional requirements of an application.
Load testing - Its a performance testing to check system behavior under load.
Testing an application under heavy loads, such as testing of a web site under a
range of loads to determine at what point the system’s response time degrades
or fails.
Stress testing - System is stressed beyond its specifications to check how and
when it fails. Performed under heavy load like putting large number beyond
storage capacity, complex database queries, continuous input to system or
database load.
Security testing - Can system be penetrated by any hacking way. Testing how
well the system protects against unauthorized internal or external access.
Checked if system, database is safe from external attacks.
Alpha testing - In house virtual user environment can be created for this type
of testing. Testing is done at the end of development. Still minor design
changes may be made as a result of such testing.
• Test Analysis,
• Test Design,
• Testing Cycles,
• Post Implementation.
Software testing has its own life cycle that intersects with every stage of the
SDLC. The basic requirements in software testing life cycle is to control/deal with
software testing – Manual, Automated and Performance.
Test Planning
This is the phase where Project Manager has to decide what things need to be
tested, do I have the appropriate budget etc. Naturally proper planning at this stage
would greatly reduce the risk of low quality software. This planning will be an
ongoing process with no end point.
Activities at this stage would include preparation of high level test plan-(according
to IEEE test plan template The Software Test Plan (STP) is designed to prescribe
the scope, approach, resources, and schedule of all testing activities. The plan must
identify the items to be tested, the features to be tested, the types of testing to be
performed, the personnel responsible for testing, the resources and schedule
required to complete testing, and the risks associated with the plan.). Almost all of
the activities done during this stage are included in this software test plan and
revolve around a test plan.
Test Analysis
Once test plan is made and decided upon, next step is to delve little more into the
project and decide what types of testing should be carried out at different stages of
SDLC, do we need or plan to automate, if yes then when the appropriate time to
automate is, what type of specific documentation I need for testing.
Proper and regular meetings should be held between testing teams, project
managers, development teams, Business Analysts to check the progress of things
which will give a fair idea of the movement of the project and ensure the
completeness of the test plan created in the planning phase, which will further help
in enhancing the right testing strategy created earlier. We will start creating test
case formats and test cases itself. In this stage we need to develop Functional
validation matrix based on Business Requirements to ensure that all system
requirements are covered by one or more test cases, identify which test cases to
automate, begin review of documentation, i.e. Functional Design, Business
Requirements, Product Specifications, Product Externals etc. We also have to
define areas for Stress and Performance testing.
Test Design
Test plans and cases which were developed in the analysis phase are revised.
Functional validation matrix is also revised and finalized. In this stage risk
assessment criteria is developed. If you have thought of automation then you have
to select which test cases to automate and begin writing scripts for them. Test data
is prepared. Standards for unit testing and pass / fail criteria are defined here.
Schedule for testing is revised (if necessary) & finalized and test environment is
prepared.
In this phase we have to complete all the test plans, test cases, complete the
scripting of the automated test cases, Stress and Performance testing plans needs to
be completed. We have to support the development team in their unit testing phase.
And obviously bug reporting would be done as when the bugs are found.
Integration tests are performed and errors (if any) are reported.
Testing Cycles
In this phase we have to complete testing cycles until test cases are executed
without errors or a predefined condition is reached. Run test cases --> Report Bugs
--> revise test cases (if needed) --> add new test cases (if needed) --> bug fixing -->
retesting (test cycle 2, test cycle 3….).
Final Testing and Implementation
Post Implementation
In this phase, the testing process is evaluated and lessons learnt from that testing
process are documented. Line of attack to prevent similar problems in future
projects is identified. Create plans to improve the processes. The recording of new
errors and enhancements is an ongoing process. Cleaning up of test environment is
done and test machines are restored to base lines in this stage.
To improve quality:
As computers and software are used in critical applications, the outcome of a bug can
be severe. Bugs can cause huge losses. Bugs in critical systems have caused airplane
crashes, allowed space shuttle missions to go awry, halted trading on the stock
market, and worse. Bugs can kill. Bugs can cause disasters. The so-called year 2000
(Y2K) bug has given birth to a cottage industry of consultants and programming tools
dedicated to making sure the modern world doesn't come to a screeching halt on the
first day of the next century. In a computerized embedded world, the quality and
reliability of software is a matter of life and death.
Quality means the conformance to the specified design requirement. Being correct,
the minimum requirement of quality, means performing as required under specified
circumstances. Debugging, a narrow view of software testing, is performed heavily to
find out design defects by the programmer. The imperfection of human nature makes
it almost impossible to make a moderately complex program correct the first time.
Finding the problems and get them fixed, is the purpose of debugging in
programming phase.
We can not test quality directly, but we can test related factors to make quality visible.
Quality has three sets of factors -- functionality, engineering, and adaptability. These
three sets of factors can be thought of as dimensions in the software quality space.
Each dimension may be broken down into its component factors and considerations at
successively lower levels of detail. Table 1 illustrates some of the most frequently
cited quality considerations.
Integrity Structure
Good testing provides measures for all relevant factors. The importance of any
particular factor varies from application to application. Any system where human
lives are at stake must place extreme emphasis on reliability and integrity. In the
typical business system usability and maintainability are the key factors, while for a
one-time scientific program neither may be significant. Our testing, to be fully
effective, must be geared to measuring each relevant factor and thus forcing quality to
become tangible and visible.
Tests with the purpose of validating the product works are named clean tests, or
positive tests. The drawbacks are that it can only validate that the software works for
the specified test cases. A finite number of tests can not validate that the software
works for all situations. On the contrary, only one failed test is sufficient enough to
show that the software does not work. Dirty tests, or negative tests, refer to the tests
aiming at breaking the software, or showing that it does not work. A piece of software
must have sufficient exception handling capabilities to survive a significant level of
dirty tests.
A testable design is a design that can be easily validated, falsified and maintained.
Because testing is a rigorous effort and requires significant time and cost, design for
testability is also an important design rule for software development.
Software reliability has important relations with many aspects of software, including
the structure, and the amount of testing it has been subjected to. Based on an
operational profile (an estimate of the relative frequency of use of various inputs to
the program ), testing can serve as a statistical sampling method to gain failure data
for reliability estimation.
Software testing is not mature. It still remains an art, because we still cannot make it a
science. We are still using the same testing techniques invented 20-30 years ago,
some of which are crafted methods or heuristics rather than good engineering
methods. Software testing can be costly, but not testing software is even more
expensive, especially in places that human lives are at stake. Solving the software-
testing problem is no easier than solving the Turing halting problem. We can never be
sure that a piece of software is correct. We can never be sure that the specifications
are correct. No verification system can verify every correct program. We can never be
certain that a verification system is correct either.
FEATURES OF THE PROJECT
There are 6 key features for this project. They are:-
More interoperability.
CONCLUSION
CONCLUSION
Handwritten paper medical records can be associated with poor legibility, which can
contribute to medical errors. Pre-printed forms, the standardization of abbreviations,
and standards for penmanship were encouraged to improve reliability of paper
medical records. Electronic records help with the standardization of forms,
terminology and abbreviations, and data input. Digitization of forms facilitates the
collection of data for epidemiology and clinical studies.
BIBLIOGRAPHY
Books:
System Analysis And Design :James A.Senn
Websites:
www.msdn.microsoft.com/asp.net
www.quickstarts.asp.net
www.sitepoint.com/article/sql-injection-attacks-safe