COVID 19 With Hospital

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 41

COVID-19

Abstract:
Effective screening of SARS-CoV-2 enables quick and efficient diagnosis of COVID-19 and can
mitigate the burden on healthcare systems. Prediction models that combine several features to
estimate the risk of infection have been developed. These aim to assist medical staff worldwide
in triaging patients, especially in the context of limited healthcare resources. We established a
machine-learning approach that trained on records from 51,831 tested individuals (of whom
4769 were confirmed to have COVID-19). The test set contained data from the subsequent week
(47,401 tested individuals of whom 3624 were confirmed to have COVID-19). Our model
predicted COVID-19 test results with high accuracy using only eight binary features: sex, age
≥60 years, known contact with an infected individual, and the appearance of five initial clinical
symptoms. Overall, based on the nationwide data publicly reported by the Israeli Ministry of
Health, we developed a model that detects COVID-19 cases by simple features accessed by
asking basic questions. Our framework can be used, among other considerations, to prioritize
testing for COVID-19 when testing resources are limited.

This pandemic continues to challenge medical systems worldwide in many aspects, including
sharp increases in demands for hospital beds and critical shortages in medical equipment, while
many healthcare workers have themselves been infected. Thus, the capacity for immediate
clinical decisions and effective usage of healthcare resources is crucial. The most validated
diagnosis test for COVID-19, using reverse transcriptase polymerase chain reaction (RT-PCR),
has long been in shortage in developing countries. This contributes to increased infection rates
and delays critical preventive measures.

In this paper, we propose a machine-learning model that predicts a positive SARS-CoV-2


infection in a RT-PCR test by asking eight basic questions. The model was trained on data of all
individuals in Israel tested for SARS-CoV-2 during the first months of the COVID-19 pandemic.
Thus, our model can be implemented globally for effective screening and prioritization of testing
for the virus in the general population.

Existing System:
From the past decade, the fast growth of digital methodologies is playing a vital role in resolving
different problems of the health sector as well as disease prevention. The existing global health
emergency is also tracking the support of digital equipment to deal with COVID-19 proficiently.
The prophecy of the patient’s outcome is still a tough concern in the field of health care. Due to
the huge growth of ML techniques, predicting and diagnosing diseases made it easy in current
days. ML can learn through machines and makes a proper prediction by self-learning. ML has
extensively forecasted many diseases like hepatitis [10], Human immunodeficiency virus (HIV)
[11], Ebola virus [12], etc. Similarly, huge ranged data of COVID-19 patients have also been
combined and studied with ML. Several techniques of ML were utilized to identify the affected
individuals with personalized characteristics. The performance of ML is reliant on choosing data
illustration. To stabilize these challenges, feature engineering advanced by taking the advantage
of human creativity. Yet, these drawbacks have been elaborated by some health ideologies that
are consumed in the generalization of information. There can be a situation where some medical
works need to be implied in unusual ways.
This problem can be resolved by illustrating the health composition in the adhoc technique. Still,
the latest prototypes cannot be predicted by supervised models. Nevertheless, representation
learning can be effortless to extract essential data while creating predictors [13]. Among the
diverse methods of representation learning, DL methods are easy and created by the composition
of numerous nonlinear variations.

Proposed System:
In spite the success of machine learning approaches, their performance is highly affected by the
quality of the hand-engineered features. The hand-engineered features are not optimal and also a
time-consuming task [12]. This is the main drawback of machine learning approach, despite the
success, these techniques suffer from serious degradation in performance. The alternative
approach, which has become hot research topic in recent era, is to extract automatic optimal
features from the input data. These techniques have not only removed the barrier of manual
feature extraction but also improved the classification accuracy.

Several techniques based on deep learning (DL) have been put forward to achieve the above
goals: automatic feature extraction and improving classification accuracy. With improvements in
computer hardware, it has become feasible to train more and more complex models. DL
approaches, especially CNNs have shown their efficiency for various computer vision tasks such
as object detection, natural language processing, image segmentation and classification.
Motivated from the computer vision community, the medical community has also adopted the
model to solve many medical image analysis tasks. 

SOFTWARE REQUIREMENT

Operating System : Window 10


Front -End : Visual Studio 2008
Back –End : SQL Server 2008
Language - .Net, Java Script
HARDWARE REQUIREMENT
Processor : Intel Pentium IV,2.4 GHz
RAM : 512 MB
Hard Disk Drive : 40 GB
Video : 800*600, 1024*768 256 colors

Modules:

 Patient registration
 Covid prediction
 Take action
 View report

Modules Description:

Registration: This module helps in registering information about patients and handling both IPD
and OPD patient’s query. A unique ID is generated for each patient after registration. This helps
in implementing customer relationship management and also maintains medical history of the
patient.

Covid prediction:To assess workforce capacity during COVID-19 and non-COVID-19


functions during the course of the outbreak, including task distribution, health workforce
infections and availability of personal protective equipment

Take action:To assess the structural capacities of facilities to allow safe COVID-19 case
management, maintain the delivery of essential services and enable surge capacity planning

View Report:Lab Test System carry complete details of the test services that are available in the
hospital such as blood test and different other test services. It also manages the history of test
details according to the registered patient name.

FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put forth
with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the Medical Shop. For feasibility analysis, some understanding of the
major requirements for the system is essential.
Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY
 TECHNICAL FEASIBILITY
 SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY:

This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the Medical Shop can pour into the research and development of
the system is limited. The expenditures must be justified. Thus the developed system as well within the
budget and this was achieved because most of the technologies used are freely available. Only the
customized medicines had to be purchased.

TECHNICAL FEASIBILITY:

This study is carried out to check the technical feasibility, that is, the technical requirements
of the system. Any system developed must not have a high demand on the available technical resources.
This will lead to high demands on the available technical resources. This will lead to high demands being
placed on the client. The developed system must have a modest requirement, as only minimal or null
changes are required for implementing this system.

SOCIAL FEASIBILITY:

The aspect of study is to check the level of acceptance of the system by the user. This includes
the process of training the user to use the system efficiently. The user must not feel threatened by the
system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the
methods that are employed to educate the user about the system and to make him familiar with it. His
level of confidence must be raised so that he is also able to make some constructive criticism, which is
welcomed, as he is the final user of the system.
LANGAUGE SPECIFICATION

4.1 features of ASP. net

WHAT IS “.NET”?

Microsoft .NET is a set of Microsoft software technologies for rapidly building and
integrating XML Web services, Microsoft Windows-based applications, and Web solutions. The .NET
Framework is a language-neutral platform for writing programs that can easily and securely
interoperate. There’s no language barrier with .NET: there are numerous languages available to the
developer including Managed C++, C#, Visual Basic and Java Script. The .NET framework provides the
foundation for components to interact seamlessly, whether locally or remotely on different platforms. It
standardizes common data types and communications protocols so that components created in
different languages can easily interoperate.

“.NET” is also the collective name given to various software components built upon
the .NET platform. These will be both mediciness (Visual Studio.NET and Windows.NET Server, for
instance) and services (like Passport, .NET My Services, and so on).

THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).

2. A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the environment within which
programs run. The most important features are:

 Conversion from a low-level assembler-style language, called Intermediate Language (IL), into
code native to the platform being executed on.
 Memory management, notably including garbage collection.
 Checking and enforcing security restrictions on the running code.
 Loading and executing programs, with version control and other such features.
The following features of the .NET framework are also worth description:

Managed Code - is code that targets .NET, and which contains certain extra information - “metadata” -
to describe itself. Whilst both managed and unmanaged code can run in the runtime, only managed
code contains the information that allows the CLR to guarantee, for instance, safe execution and
interoperability.

Managed Data - With Managed Code comes Managed Data. CLR provides memory allocation and Deal
location facilities, and garbage collection. Some .NET languages use Managed Data by default, such as
C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do not. Targeting CLR can, depending
on the language you’re using, impose certain constraints on the features available. As with managed and
unmanaged code, one can have both managed and unmanaged data in .NET applications - data that
doesn’t get garbage collected but instead is looked after by unmanaged code.

Common Type System - The CLR uses something called the Common Type System (CTS) to strictly
enforce type-safety. This ensures that all classes are compatible with each other, by describing types in a
common way. CTS define how types work within the runtime, which enables types in one language to
interoperate with types in another language, including cross-language exception handling. As well as
ensuring that types are only used in appropriate ways, the runtime also ensures that code doesn’t
attempt to access memory that hasn’t been allocated to it.

Common Language Specification - The CLR provides built-in support for language interoperability. To
ensure that you can develop managed code that can be fully used by developers using any programming
language, a set of language features and rules for using them called the Common Language Specification
(CLS) has been defined. Components that follow these rules and expose only CLS features are
considered CLS-compliant.

THE CLASS LIBRARY

.NET provides a single-rooted hierarchy of classes, containing over 7000 types. The root
of the namespace is called System; this contains basic types like Byte, Double, Boolean, and String, as
well as Object. All objects derive from System. Object. As well as objects, there are value types. Value
types can be allocated on the stack, which can provide useful flexibility. There are also efficient means of
converting value types to object types if and when necessary.
The set of classes is pretty comprehensive, providing collections, file, screen, and
network I/O, threading, and so on, as well as XML and database connectivity.

The class library is subdivided into a number of sets (or namespaces), each providing
distinct areas of functionality, with dependencies between the namespaces kept to a minimum.

LANGUAGES SUPPORTED BY .NET

The multi-language capability of the .NET Framework and Visual Studio .NET enables
developers to use their existing programming skills to build all types of applications and XML Web
services. The .NET framework supports new versions of Microsoft’s old favorites Visual Basic and C++ (as
ASP.NETand Managed C++), but there are also a number of new additions to the family:

Visual Basic .NET has been updated to include many new and improved language
features that make it a powerful object-oriented programming language. These features include
inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured
exception handling, custom attributes and also supports multi-threading.

Visual Basic .NET is also CLS compliant, which means that any CLS-compliant language
can use the classes, objects, and components you create in Visual Basic .NET.

Managed Extensions for C++ and attributed programming are just some of the
enhancements made to the C++ language. Managed Extensions simplify the task of migrating existing C+
+ applications to the new .NET Framework.

C# is Microsoft’s new language. It’s a C-style language that is essentially “C++ for Rapid
Application Development”. Unlike other languages, its specification is just the grammar of the language.
It has no standard library of its own, and instead has been designed with the intention of using the .NET
libraries as its own.

Microsoft Visual J# .NET provides the easiest transition for Java-language developers
into the world of XML Web Services and dramatically improves the interoperability of Java-language
programs with existing software written in a variety of other programming languages.
Active State has created Visual Perl and Visual Python, which enable .NET-aware
applications to be built in either Perl or Python. Both mediciness can be integrated into the Visual Studio
.NET environment. Visual Perl includes support for ActiveState’s Perl Dev Kit.

Other languages for which .NET compilers are available include:

 FORTRAN
 COBOL
 Eiffel

Fig1 .Net Framework

ASP.NET Windows Forms

XML WEB SERVICES

Base Class Libraries

Common Language Runtime

Operating System

INTRODUCTION TO ASP.NET

ASP.NET is the .NET framework layer that handles Web requests for specific types of
files, namely those with (.aspx or .ascx) extensions. The ASP.NET engine provides a robust object model
for creating dynamic content and is loosely integrated into the .NET framework.

WHAT IS ASP.NET?
ASP.NET is part of the .NET framework. ASP.NET programs are centralized applications
hosted on one or more Web servers that respond dynamically to client requests. The responses are
dynamic because ASP.NET intercepts requests for pages with a specific extension (.aspx or .ascx) and
hands off the responsibility for answering those requests to just-in-time (JIT) compiled code files that
can build a response “on-the-fly.”

ASP.NET deals specifically with configuration (web.config and machine.config) files, Web
Services (ASMX) files, and Web Forms (ASPX) files. The server doesn’t “serve” any of these file types—it
returns the appropriate content type to the client. The configuration file types contain initialization and
settings for a specific application or portion of an application. Another configuration file, called
machine.web, contains machine-level initialization and settings. The server ignores requests for web
files, because serving them might constitute a security breach.

Client requests for these file types cause the server to load, parse, and execute code to
return a dynamic response. For Web Forms, the response usually consists of HTML or WML. Web Forms
maintain state by round-tripping user interface and other persistent values between the client and the
server automatically for each request.

A request for a Web Form can use ViewState, SessionState, or ApplicationState to


maintain values between requests. Both Web Forms and Web Services requests can take advantage of
ASP. Net’s integrated security and data access through ADO.NET, and can run code that uses system
services to construct the response. So the major difference between a static request and a dynamic
request is that a typical Web request references a static file. The server reads the file and responds with
the contents of the requested file.

ASP.NET uses .NET languages. ASP.NET code exists in multithreaded JIT compiled DLL
assemblies, which can be loaded on demand. Once loaded, the ASP.NET DLLs can service multiple
requests from a single in-memory copy.

ASP.NET supports all the .NET languages (currently C#, C++, VB.NET, and JScript, but
there are well over 20 different languages in development for .NET), so you will eventually be able to
write Web applications in your choice of almost any modern programming language.
In addition to huge increases in speed and power, ASP.NET provides substantial
development improvements, like seamless server-to-client debugging, automatic validation of form
data.

Fig2. Interoperability

ASP.NET EVENTS

.NET events and why they are cool

Every time an ASP.NET page is viewed, many tasks are being performed behind the
scenes. Tasks are performed at key points ("events") of the page's execution lifecycle.

The most common events are:

On Init
The first event in our list to be raised is OnInit. When this event is raised, all of the
page's server controls are initialized with their property values. Post Back values are not applied to the
controls at this time.

On Load

The next event to be raised is On Load, which is the most important event of them all as
all the page’s server controls will have their Post Back values now.

Post Back Events

Next all the Post Back events are raised. These events are only raised when the page
view is the result of a Post Back. The order that these events are raised can't be defined or relied upon;
the only consistency with the order that Post Back events are raised is that they are all raised between
the Unload and OnPreRender events.

OnPreRender

This event is raised just prior to the page or server control's html output being written
into the response stream that's sent to the client web browser. This is last chance you have to make any
modifications. By this point, all the server controls on the page have the final data applied.

On Unload

This is the last event in our list to be raised and you should destroy any un-managed
objects and close any currently open database connection at this point. It is not possible to modify any
controls on the page at this point as the response stream has already been sent to the client web
browser.

As each event of the page is raised it also automatically tells all its child controls to raise
their own implementation of the same event. In turn each of those controls will tell its own child
controls to do the same and so on down the control tree till all controls have done so. Then execution
flow is passed back to the main page class to continue onto the next event and the process is repeated
for that event.
MAIN FEATURES OF ASP.NET

Successor of Active Server Pages (ASP), but completely different architecture

• Object-oriented

• Event-based

• Rich library of Web Controls

• Separation of layout (HTML) and logic (e.g. C#)

• Compiled languages instead of interpreted languages

• GUI can be composed interactively with Visual Studio .NET

• Better state management

NAMESPACES

ASP.NET uses a concept called namespaces. Namespaces are hierarchical object models
that support various properties and methods. For example, HTML server controls reside in
"System.web.UI.HtmlControls" namespace, web server controls reside in “System.web.UI. Web
Controls" namespace and ADO+ resides in "System. Data" namespace.

LANGUAGE INDEPENDENT

An ASP.NET page can be created in any language supported by .NET framework.


Currently .NET framework supports VB, C#, JScript and Managed C++.

ASP.NET SERVER CONTROLS

Using ASP.NET Server Controls, browser variation is handled because these controls
output the HTML themselves based on the browser requesting the page.

TYPES OF CONTROLS

ASP.NET has two basic types of controls: HTML server controls and Web server
controls.HTML Server Controls are generated around specific HTML elements and the ASP.NET engine
changes the attributes of the elements based on server-side code that you provide. Web server controls
revolve more around the functional you need on the page. The ASP.NET engine takes the extra steps to
decide based upon the container of the requester, what HTML to output.

Fig 3. Web Controls

ADO.NET

ADO.NET provides a set of classes which a script can use to interact with databases.
Scripts can create instances of ADO.NET data classes and access their properties and methods. A set of
classes which work with a specific type of database is known as a .NET Data Provider. ADO.NET comes
with two Data Providers, the SQL Server.NET Data Provider (which provides optimized access for
Microsoft SQL Server databases) and the OLEDB.NET Data Provider, which works with a range of
databases. The main ADO.NET OLEDB data access classes are OLEDBConnection, OLEDBCommand,
OLEDBDataReader and OLEDBDataAdapter.

FEATURES OF SQL SERVER 2000


The OLAP Services feature available in SQL Server version 7.0 is now called Sql server
2005Analysis Services. The term OLAP Services has been replaced with the term Analysis
Services. Analysis Services also includes a new data mining component. The Repository
component available in SQL Server version 7.0 is now called Microsoft Sql server 2005Meta
Data Services. References to the component now use the term Meta Data Services. The term
repository is used only in reference to the repository engine within Meta Data Services
SQL-SERVER database consist of six type of objects,
They are,
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO

TABLE:
A database is a collection of data about a specific topic.
VIEWS OF TABLE:
We can work with a table in two types,
1. Design View
2. Datasheet View
Design View
To build or modify the structure of a table we work in the table design view. We
can specify what kind of data will be hold.
Datasheet View
To add, edit or analyses the data itself we work in tables datasheet view mode.
QUERY:
A query is a question that has to be asked the data. Access gathers data that answers the
question from one or more table. The data that make up the answer is either dynaset (if you edit
it) or a snapshot (it cannot be edited). Each time we run query, we get latest information in the
dynaset. Access either displays the dynaset or snapshot for us to view or perform an action on it,
such as deleting or updating.
FORMS:
A form is used to view and edit information in the database record by record. A form
displays only the information we want to see in the way we want to see it. Forms use the familiar
controls such as textboxes and checkboxes. This makes viewing and entering data easy.

views of Form:
We can work with forms in several primarily there are two views,
They are,
1. Design View
2. Form View

Design View
To build or modify the structure of a form, we work in forms design view. We can add
control to the form that are bound to fields in a table or query, includes textboxes, option buttons,
graphs and pictures.
Form View
The form view which display the whole design of the form.
]
REPORT:
A report is used to vies and print information from the database. The report can
ground records into many levels and compute totals and average by checking values from many
records at once. Also the report is attractive and distinctive because we have control over the size
and appearance of it.

MACRO:
A macro is a set of actions. Each action in macros does something. Such as opening a
form or printing a report. We write macros to automate the common tasks the work easy and
save the time.

SYSTEM DESIGN

INPUT DESIGN

Input design is the process of converting user-originated inputs to a computer-based format.


Input design is one of the most expensive phases of the operation of computerized system and is often
the major problem of a system.In the project, the input design is made in various web forms with
various methods.

For example, in the Admin form, the empty username and password is not allowed. The
username if exists in the database, the input is considered to be invalid and is not accepted.Likewise,
during the “Purchase” process, we purchase more than one medicines.

OUTPUT DESIGN

Output design generally refers to the results and information that are generated by the system
for many end-users; output is the main reason for developing the system and the basis on which they
evaluate the usefulness of the application.

In the project, the output is to view the medicines, purchase items, updated by the current
medicines rate.
DATABASE DESIGN:

The database design is a must for any application developed especially more for the data store projects.
Since the chatting method involves storing the message in the table and produced to the sender and
receiver, proper handling of the table is a must.

In the project, login table is designed to be unique in accepting the username and the length of the
username and password should be greater than zero.

In this database design the admin details and the user details are stored in the database. The different
users view the data in different format according to the privileges given.

The complete listing of the tables and their fields are provided in the annexure under the title ‘Table
Structure’.

SYSTEM TESTING AND MAINTENANCE

Testing is vital to the success of the system. System testing makes a logical assumption that
if all parts of the system are correct, the goal will be successfully achieved. In the testing
process we test the actual system in an organization and gather errors from the new system
operates in full efficiency as stated. System testing is the stage of implementation, which is
aimed to ensuring that the system works accurately and efficiently.

In the testing process we test the actual system in an organization and gather errors from the
new system and take initiatives to correct the same. All the front-end and back-end
connectivity are tested to be sure that the new system operates in full efficiency as stated.
System testing is the stage of implementation, which is aimed at ensuring that the system
works accurately and efficiently.

The main objective of testing is to uncover errors from the system. For the uncovering
process we have to give proper input data to the system. So we should have more conscious
to give input data. It is important to give correct inputs to efficient testing.
Testing is done for each module. After testing all the modules, the modules are integrated
and testing of the final system is done with the test data, specially designed to show that the
system will operate successfully in all its aspects conditions. Thus the system testing is a
confirmation that all is correct and an opportunity to show the user that the system works.
Inadequate testing or non-testing leads to errors that may appear few months later.

This will create two problems time delay between the cause and appearance of the
problem. The effect of the system errors on files and records within the system. The purpose
of the system testing is to consider all the likely variations to which it will be suggested and
push the system to its limits

The testing process focuses on logical intervals of the software ensuring that all the
statements have been tested and on the function intervals (i.e.,) conducting tests to uncover
errors and ensure that defined inputs will produce actual results that agree with the required
results. Testing has to be done using the two common steps Unit testing and Integration
testing. In the project system testing is made as follows:

The procedure level testing is made first. By giving improper inputs, the errors occurred
are noted and eliminated. This is the final step in system life cycle. Here we implement the
tested error-free system into real-life environment and make necessary changes, which runs
in a fashion.

Here system maintenance is done every months or year based on Medical Shop policies,
and is checked for errors like runtime errors, long run errors and other maintenances like
table verification and reports.
UNIT TESTING

Unit testing verification efforts on the smallest unit of software design, module. This is
known as “Module Testing”. The modules are tested separately. This testing is carried out
during programming stage itself. In these testing steps, each module is found to be working
satisfactorily as regard to the expected output from the module.
INTEGRATION TESTING
Integration testing is a systematic technique for constructing tests to uncover error
associated within the interface. In the project, all the modules are combined and then the
entire programmer is tested as a whole. In the integration-testing step, all the error uncovered
is corrected for the next testing steps.

VALIDATION TESTING

To uncover functional errors, that is, to check whether functional characteristics


confirm to specification or not.

MAINTENANCE:

The objectives of this maintenance work are to make sure that the system gets into work all time
without any bug. Provision must be for environmental changes which may affect the computer or
software system. This is called the maintenance of the system. Nowadays there is the rapid change in
the software world. Due to this rapid change, the system should be capable of adapting these changes.
In our project the process can be added without affecting other parts of the system.

Maintenance plays a vital role. The system liable to accept any modification after its
implementation. This system has been designed to favor all new changes. Doing this will not affect the
system’s performance or its accuracy.

SYSTEM IMPLEMENTATION

Implementation is the stage of the project when the theoretical design is turned out into a
working system. Thus it can be considered to be the most critical stage in achieving a successful
new system and in giving the user, confidence that the new system will work and be effective.
The implementation stage involves careful planning, investigation of the existing system and
its constraints on implementation, designing of methods to achieve changeover and evaluation of
changeover methods.
Implementation is the process of converting a new system design into operation. It is the
phase that focuses on user training, site preparation and file conversion for installing a Customer
and supplier system. The important factor that should be considered here is that the conversion
should not disrupt the functioning of the organization.

E-R Diagrams:
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way
to unify the network and relational database views. Simply stated the ER model is a conceptual
data model that views the real world as entities and relationships. A basic component of the
model is the Entity-Relationship diagram which is used to visually represents data objects. Since
Chen wrote his paper the model has been extended and today it is commonly used for database
design For the database designer, the utility of the ER model is:
 it maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
 it is simple and easy to understand with a minimum of training. Therefore, the model can be
used by the database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to implement a
data model in a specific database management software.

Connectivity and Cardinality:


The basic types of connectivity for relations are: one-to-one, one-to-many, and many-to-many.
A one-to-one (1:1) relationship is when at most one instance of a entity A is associated with one
instance of entity B. For example, "employees in the company are each assigned their own
office. For each employee there exists a unique office and for each office there exists a unique
employee.
A one-to-many (1:N) relationships is when for one instance of entity A, there are zero, one, or
many instances of entity B, but for one instance of entity B, there is only one instance of entity
A.An example of a 1:N relationships is
a department has many employees
each employee is assigned to one department
A many-to-many (M:N) relationship, sometimes called non-specific, is when for one instance of
entity A, there are zero, one, or many instances of entity B and for one instance of entity B there
Hospital Management System 22 are zero, one, or many instances of entity A. The connectivity
of a relationship describes the mapping of associated

ER Notation:
There is no standard for representing data objects in ER diagrams. Each modeling methodology
uses its own notation. The original notation used by Chen is widely used in academics texts and
journals but rarely seen in either CASE tools or publications by nonacademics. Today, there are
a number of notations used, among the more common are Bachman, crow's foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The
notation used in this document is from Martin. The symbols used for the basic ER constructs are:
Entities are represented by labeled rectangles. The label is the name of the entity. Entity names
should be singular nouns.
Relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs
Attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.
Cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.
Existence is represented by placing a circle or a perpendicular bar on the line. Mandatory
existence is shown by the bar (looks like a 1) next to the entity for an instance is required.
Optional existence is shown by placing a circle next to the entity that is optional.

ER Diagram:
Covid 19

Patient
Covid prediction Take action View report
registration

Address
Negative

Age Exposure Risk Level Test report


P ID Positive
Gender
Name
P detail
PH No

High risk
Low risk

DFD DIAGRAM:

DFDs show the flow of data from external entities into the system, showed how the data
moved from one process to another, as well as its logical storage. There are only four symbols:

 Squares representing external entities, which are sources or destinations of data.


 Rounded rectangles representing processes, which take data as input, do something to it,
and output it.
 Arrows representing the data flows, which can either, be electronic data or physical
items.
 Open-ended rectangles representing data stores, including electronic stores such as
databases or XML files and physical stores such as or filing cabinets or stacks of paper.

There are several common modeling rules for creating DFDs:

 All processes must have at least one data flow in and one data flow out.
 All processes should modify the incoming data, producing new forms of outgoing data.
 Each data store must be involved with at least one data flow.
 Each external entity must be involved with at least one data flow.
 A data flow must be attached to at least one process.

DFDs are nothing more than a network of related system functions and indicate from
where information is received and to where it is sent. It is the starting point in the system that
decomposes the requirement specifications down to the lowest level detail.

The four symbols in DFD, each of which has its meaning. They are given below:

 External entities are outside to system but they either supply input data in the system or
use the system output. These are represented by square of rectangle. External entities that
supply data into a system are sometimes called Sources. External entities that use system
data are sometimes called sinks.
 Dataflow models that passages of data in the system and are represented by line by
joining system components. An arrow indicates the direction of the flow and the line is
labeled by the name of the dataflow.
 Process show that the systems do. Each process has one or more data inputs and one or
data outputs. Circles in DFD represent them. Each high level process may be consisting
of more than one lower level processes. Process will be expanded in sequent level DFD.
A circle or a bubble represents a process that transforms incoming data flow into
outgoing dataflow.
Data Flow Diagram:
0-Level DFD:

Covid 19 Covid prediction


Patient registration

CONTEXT DTAGRAM

Level 1:
Registration
Enter
Process Patient Details
Patient data Register
2.0
status

View Profile
Profile Update
Edit data
User 2.1
Updates

Level 2:

Patient  Register

Covid prediction

Take action

View Report

Conclusions and Future Work:


The rapid spread of COVID-19 across the world and the increasing number of deaths require
urgent actions from all sectors. Future prediction of potential infections will enable authorities to
tackle the consequences effectively. Furthermore, it is necessary to keep up with the number of
infected people by performing regular check-ups, and it is often vital to quarantine infected
people and adopt medical measures. Additionally, attention should be given to several other
factors to curb the spread of COVID-19, such as the environmental effects and the similarities
among the most affected areas, and careful measures should be adopted. In this paper, AI-based
techniques were proposed for the prediction and diagnosis of COVID-19:

Prediction models such as the PA, ARIMA, and LSTM algorithms were used to predict the
number of COVID-19 confirmations, recoveries, and deaths over the next 7 days. PA delivered
the best performance. It predicted the number of COVID-19 confirmations, recoveries, and
deaths in Australia and obtained prediction accuracies of 99.94%, 90.29%, and 94.18%,
respectively. It also predicted the number of COVID19 confirmations, recoveries, and deaths in
Jordan and obtained prediction accuracies of 99.08%, 79.39%, and 86.82%, respectively.
Meanwhile, investigation into more sophisticated forecasting and prediction methods is a subject
of a future work.

References:
[1] World Health Organization, "Laboratory testing for coronavirus disease 2019 (COVID-19)
in suspected human cases: interim guidance, 2 March 2020," World Health Organization, World
Health Organization2020.

[2] Worldometers. (2020, April. 6). Coronavirus Cases. Available:


https://www.worldometers.info/coronavirus/

[3] A. Chen. ( 2020) China’s coronavirus app could have unintended consequences. MIT
Technology Review. Available:

https://www.technologyreview.com/2020/02/13/844 805/coronavirus-china-app-close-
contactsurveillance-covid-19-technology/

[4] F. Jiang, L. Deng, L. Zhang, Y. Cai, C. W. Cheung, and Z. Xia, "Review of the clinical
characteristics of coronavirus disease 2019 (COVID-19)," Journal of General Internal Medicine,
pp. 1-5, 2020.

[5] Z. Wu and J. M. McGoogan, "Characteristics of and important lessons from the coronavirus
disease 2019 (COVID-19) outbreak in China: summary of a report of 72 314 cases from the
Chinese Center for Disease Control and Prevention," Jama, 2020.

SCREEN SHOTS
CODING

LOGIN PAGE
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;

namespace covid
{
public partial class login : Form
{
static int attempt = 3;
public login()
{
InitializeComponent();
}

private void button1_Click(object sender, EventArgs e)


{
string username = textBox1.Text;
string password = textBox2.Text;

if ((this.textBox1.Text == "admin") && (this.textBox2.Text ==


"admin"))
{
attempt = 0;
MessageBox.Show("you are granted with access");
this.Hide();
homepage h =new homepage();
h.ShowDialog();
}
else if ((attempt == 3) && (attempt > 0))
{

label4.Text = ("You Have Only " + Convert.ToString(attempt) +


" Attempt Left To Try");
--attempt;
}
else
{

MessageBox.Show("you are not granted with access");


}
}
}
}

PATIENT REGISTRATION
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data.SqlClient;

namespace covid
{
public partial class patientregistration : Form
{
SqlConnection con = new SqlConnection("Data Source=.\\
SQLEXPRESS;Initial Catalog=covid;Integrated Security=True");
SqlCommand cmd;
SqlDataAdapter adapt;
int id = 0;
public patientregistration()
{
InitializeComponent();
DisplayData();
}

private void button1_Click(object sender, EventArgs e)


{
SqlCommand cmd = new SqlCommand("insert into patientregistration"
+
"(id,name,address,aadharno,mobile,email,visitor,treatment)values(@id,@name,@ad
dress,@aadharno,@mobile,@email,@visitor,@treatment)", con);
con.Open();
cmd.Parameters.AddWithValue("@id", textBox1.Text);
cmd.Parameters.AddWithValue("@name", textBox2.Text);
cmd.Parameters.AddWithValue("@address", textBox3.Text);
cmd.Parameters.AddWithValue("@aadharno", textBox4.Text);
cmd.Parameters.AddWithValue("@mobile", textBox5.Text);
cmd.Parameters.AddWithValue("@email", textBox6.Text);
cmd.Parameters.AddWithValue("@visitor", textBox7.Text);
cmd.Parameters.AddWithValue("@treatment", textBox8.Text);
cmd.ExecuteNonQuery();
MessageBox.Show("record Has Been Saved Successfully");
textBox1.Text = "";
textBox3.Text = "";
textBox4.Text = "";
textBox5.Text = "";
textBox6.Text = "";
textBox7.Text = "";
textBox8.Text = "";
con.Close();
DisplayData();
ClearData();

}
private void DisplayData()
{
con.Open();
DataTable dt = new DataTable();
adapt = new SqlDataAdapter("select * from patientregistration",
con);
adapt.Fill(dt);
dataGridView1.DataSource = dt;
con.Close();
}
private void ClearData()
{

textBox2.Text = "";
textBox3.Text = "";
textBox4.Text = "";
textBox5.Text = "";
textBox6.Text = "";
textBox7.Text = "";
textBox8.Text = "";
id = 0;

}
private void button2_Click(object sender, EventArgs e)
{
con.Open();
cmd = new SqlCommand("update patientregistration set
id=@id,name=@name,address=@address,aadharno=@aadharno,mobile=@mobile,email=@em
ail,visitor=@visitor,treatment=@treatment where id=@id", con);
cmd.Parameters.AddWithValue("@id", id);
cmd.Parameters.AddWithValue("@name", textBox2.Text);
cmd.Parameters.AddWithValue("@address", textBox3.Text);
cmd.Parameters.AddWithValue("@aadharno", textBox4.Text);
cmd.Parameters.AddWithValue("@mobile", textBox5.Text);
cmd.Parameters.AddWithValue("@email", textBox6.Text);
cmd.Parameters.AddWithValue("@visitor", textBox7.Text);
cmd.Parameters.AddWithValue("@treatment", textBox8.Text);
cmd.ExecuteNonQuery();
MessageBox.Show("Record Updated Successfully");
con.Close();
DisplayData();
ClearData();
}

private void button3_Click(object sender, EventArgs e)


{
if (id != 0)
{
cmd = new SqlCommand("delete patientregistration where
id=@id", con);
con.Open();
cmd.Parameters.AddWithValue("@id", id);
cmd.ExecuteNonQuery();
con.Close();
MessageBox.Show("Record Deleted Successfully!");
DisplayData();
ClearData();
}
else
{
MessageBox.Show("Please Select Record to Delete");
}
}

private void dataGridView1_RowHeaderMouseClick(object sender,


DataGridViewCellMouseEventArgs e)
{
id =
Convert.ToInt32(dataGridView1.Rows[e.RowIndex].Cells[0].Value.ToString());
textBox1.Text =
dataGridView1.Rows[e.RowIndex].Cells[0].Value.ToString();
textBox2.Text =
dataGridView1.Rows[e.RowIndex].Cells[1].Value.ToString();
textBox3.Text =
dataGridView1.Rows[e.RowIndex].Cells[2].Value.ToString();
textBox4.Text =
dataGridView1.Rows[e.RowIndex].Cells[3].Value.ToString();
textBox5.Text =
dataGridView1.Rows[e.RowIndex].Cells[4].Value.ToString();
textBox6.Text =
dataGridView1.Rows[e.RowIndex].Cells[5].Value.ToString();
textBox7.Text =
dataGridView1.Rows[e.RowIndex].Cells[6].Value.ToString();
textBox8.Text =
dataGridView1.Rows[e.RowIndex].Cells[7].Value.ToString();
}

private void patientregistration_Load(object sender, EventArgs e)


{
using (SqlConnection con = new SqlConnection("Data Source=.\\
SQLEXPRESS;Initial Catalog=covid;Integrated Security=True"))
{
using (cmd = new SqlCommand("Select isnull(max(ID),0) from
patientregistration", con))
{
con.Open();
object result = cmd.ExecuteScalar();
con.Close();
textBox1.Text = (int.Parse(result.ToString()) +
1).ToString();
}
}
}

private void button5_Click(object sender, EventArgs e)


{
textBox1.Text = "";
textBox2.Text = "";
textBox3.Text = "";
textBox4.Text = "";
textBox5.Text = "";
textBox6.Text = "";
textBox7.Text = "";
textBox8.Text = "";
generate();

}
private void generate()
{
using (SqlConnection con = new SqlConnection("Data Source=.\\
SQLEXPRESS;Initial Catalog=covid;Integrated Security=True"))
{
using (cmd = new SqlCommand("Select isnull(max(ID),0) from
patientregistration", con))
{
con.Open();
object result = cmd.ExecuteScalar();
con.Close();
textBox1.Text = (int.Parse(result.ToString()) +
1).ToString();
}
}
}

private void button4_Click(object sender, EventArgs e)


{
this.Hide();
symptoms h = new symptoms();
h.ShowDialog();
}
}

SYMPTOMS
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
using System.Data;
using System.Data.SqlClient;

namespace covid
{
public partial class symptoms : Form
{
SqlConnection con = new SqlConnection("Data Source=.\\
SQLEXPRESS;Initial Catalog=covid;Integrated Security=True");
SqlCommand cmd;
SqlDataAdapter adapt;
int id = 0;
public symptoms()
{
InitializeComponent();
DisplayData();
}

private void symptoms_Load(object sender, EventArgs e)


{
string mainconn = ("Data Source=.\\SQLEXPRESS;Initial
Catalog=covid;Integrated Security=True");
SqlConnection sqlconn = new SqlConnection(mainconn);
string sqlquery = "select * from patientregistration ";
sqlconn.Open();
SqlCommand sqlcomm = new SqlCommand(sqlquery, sqlconn);
SqlDataAdapter sda = new SqlDataAdapter(sqlcomm);
DataTable dt = new DataTable();
sda.Fill(dt);
comboBox1.ValueMember = "id";
comboBox1.DisplayMember = "id";
comboBox1.DataSource = dt;

sqlcomm.ExecuteNonQuery();
sqlconn.Close();
}

private void comboBox1_SelectedIndexChanged(object sender, EventArgs


e)
{
string mainconn = ("Data Source=.\\SQLEXPRESS;Initial
Catalog=covid;Integrated Security=True");
SqlConnection sqlconn = new SqlConnection(mainconn);
string sqlquery = "select * from patientregistration where id = '"
+ comboBox1.Text + "'";
SqlCommand sqlcomm = new SqlCommand(sqlquery, sqlconn);
sqlconn.Open();
SqlDataReader sdr = sqlcomm.ExecuteReader();
while (sdr.Read())
{
textBox2.Text = sdr[1].ToString();
textBox3.Text = sdr[2].ToString();
textBox4.Text = sdr[3].ToString();
textBox5.Text = sdr[4].ToString();
textBox6.Text = sdr[5].ToString();
textBox7.Text = sdr[6].ToString();
textBox8.Text = sdr[7].ToString();

}
}

private void button1_Click(object sender, EventArgs e)


{

double total = 0;
double sym1 = 25;
double sym2 = 25;
double sym3 = 25;
double sym4 = 25;

if (checkBox1.Checked == true)
{
total = total + sym1;
}

if (checkBox2.Checked == true)
{
total = total + sym2;
}

if (checkBox3.Checked == true)
{
total = total + sym3;
}

if (checkBox4.Checked == true)
{
total = total + sym4;
}
textBox1.Text = total.ToString();

private void button2_Click(object sender, EventArgs e)


{
SqlCommand cmd = new SqlCommand("insert into symptom" +
"(id,name,address,aadharno,mobile,email,visitor,treatment,level,result)values(
@id,@name,@address,@aadharno,@mobile,@email,@visitor,@treatment,@level,@result
)", con);
con.Open();
cmd.Parameters.AddWithValue("@id", comboBox1.Text);
cmd.Parameters.AddWithValue("@name", textBox2.Text);
cmd.Parameters.AddWithValue("@address", textBox3.Text);
cmd.Parameters.AddWithValue("@aadharno", textBox4.Text);
cmd.Parameters.AddWithValue("@mobile", textBox5.Text);
cmd.Parameters.AddWithValue("@email", textBox6.Text);
cmd.Parameters.AddWithValue("@visitor", textBox7.Text);
cmd.Parameters.AddWithValue("@treatment", textBox8.Text);
cmd.Parameters.AddWithValue("@level", textBox1.Text);
cmd.Parameters.AddWithValue("@result", comboBox2.Text);
cmd.ExecuteNonQuery();
MessageBox.Show("record Has Been Saved Successfully");
textBox1.Text = "";
textBox3.Text = "";
textBox4.Text = "";
textBox5.Text = "";
textBox6.Text = "";
textBox7.Text = "";
textBox8.Text = "";
comboBox1.Text = "";
comboBox2.Text = "";
con.Close();
DisplayData();
ClearData();
}
private void DisplayData()
{
con.Open();
DataTable dt = new DataTable();
adapt = new SqlDataAdapter("select * from symptom", con);
adapt.Fill(dt);
dataGridView1.DataSource = dt;
con.Close();
}
private void ClearData()
{

textBox2.Text = "";
textBox3.Text = "";
textBox4.Text = "";
textBox5.Text = "";
textBox6.Text = "";
textBox7.Text = "";
textBox8.Text = "";
id = 0;

private void button3_Click(object sender, EventArgs e)


{
con.Open();
cmd = new SqlCommand("update symptom set
id=@id,name=@name,address=@address,aadharno=@aadharno,mobile=@mobile,email=@em
ail,visitor=@visitor,treatment=@treatment,level=@level,result=@result where
id=@id", con);
cmd.Parameters.AddWithValue("@id", id);
cmd.Parameters.AddWithValue("@name", textBox2.Text);
cmd.Parameters.AddWithValue("@address", textBox3.Text);
cmd.Parameters.AddWithValue("@aadharno", textBox4.Text);
cmd.Parameters.AddWithValue("@mobile", textBox5.Text);
cmd.Parameters.AddWithValue("@email", textBox6.Text);
cmd.Parameters.AddWithValue("@visitor", textBox7.Text);
cmd.Parameters.AddWithValue("@treatment", textBox8.Text);
cmd.Parameters.AddWithValue("@level", textBox1.Text);
cmd.Parameters.AddWithValue("@result", comboBox2.Text);
cmd.ExecuteNonQuery();
MessageBox.Show("Record Updated Successfully");
con.Close();
DisplayData();
ClearData();
}

private void dataGridView1_RowHeaderMouseClick(object sender,


DataGridViewCellMouseEventArgs e)
{
id =
Convert.ToInt32(dataGridView1.Rows[e.RowIndex].Cells[0].Value.ToString());
comboBox1.Text =
dataGridView1.Rows[e.RowIndex].Cells[0].Value.ToString();
textBox2.Text =
dataGridView1.Rows[e.RowIndex].Cells[1].Value.ToString();
textBox3.Text =
dataGridView1.Rows[e.RowIndex].Cells[2].Value.ToString();
textBox4.Text =
dataGridView1.Rows[e.RowIndex].Cells[3].Value.ToString();
textBox5.Text =
dataGridView1.Rows[e.RowIndex].Cells[4].Value.ToString();
textBox6.Text =
dataGridView1.Rows[e.RowIndex].Cells[5].Value.ToString();
textBox7.Text =
dataGridView1.Rows[e.RowIndex].Cells[6].Value.ToString();
textBox8.Text =
dataGridView1.Rows[e.RowIndex].Cells[7].Value.ToString();
textBox1.Text =
dataGridView1.Rows[e.RowIndex].Cells[8].Value.ToString();
comboBox2.Text =
dataGridView1.Rows[e.RowIndex].Cells[9].Value.ToString();
}

private void button4_Click(object sender, EventArgs e)


{
if (id != 0)
{
cmd = new SqlCommand("delete symptom where id=@id", con);
con.Open();
cmd.Parameters.AddWithValue("@id", id);
cmd.ExecuteNonQuery();
con.Close();
MessageBox.Show("Record Deleted Successfully!");
DisplayData();
ClearData();
}
else
{
MessageBox.Show("Please Select Record to Delete");
}
}
private void button5_Click(object sender, EventArgs e)
{
textBox1.Text = "";
textBox2.Text = "";
textBox3.Text = "";
textBox4.Text = "";
textBox5.Text = "";
textBox6.Text = "";
textBox7.Text = "";
textBox8.Text = "";
}

private void button6_Click(object sender, EventArgs e)


{

report h = new report();


h.ShowDialog();
}

}
}

TABLES
Allocated rooms

Hospital Details
Patient Registration

ROOMS

Symptom

You might also like