Hospital Information System

Full Report

Introduction

Hospital Information Systems (HIS) are becoming a fresh need for medical organizations to thrive in
inter-organizational battles that are highly competitive. In addition, evolving technology has allowed
medical organizations to demonstrate commitment with enhanced facilities to better healthcare
solutions. However, in the realization of such initiatives, there are many problems. Capital shortages and
the absence of a prevalent dictionary of information is a common issue. Furthermore, hand-written and
guided records from physicians without prevalent pattern design and variance between distinct clinics
create each application distinct from others. In addition, problems such as plan execution, enormous
project volume, people's perception of IT and such execution, etc., render the job long and monotonous.

The purpose of any Hospital Information System (HIS) is to use a computer network to gather, store and
retrieve customer service and administrative data from different agencies for all hospital operations and
meeting the demands of all concerned bodies. It also helps to develop extensive health care strategies
with cost effectiveness and efficiency as a decision support system for hospital officials.

Business Processes

A business process can be referred to as a consecutive series of single operations to attain general goals.
Such goals are generally geared towards the requirements of the client and the present business
condition. Only if all engaged individuals and machinery objects have been earlier aligned can the value
chain operate unhindered. Perceived as one organization, the executed procedures can be defined as a
feature, transforming a specified entry into a measurable result. Activities in this situation result in
increased importance; a main component of business processes.

Relevant variables must be regarded in attempt to implement the concept of system governance in the
hospital industry. Unlike an agricultural, or manufacturing system, where products are situated in the
core, people are the most significant cases of healthcare service delivery. Thus, it is necessary to respect
different requirements of people and other patient sensitivities.

An information system facilitating the activities of a hospital weighs into account:

1. The features of a health care facility

2. The capacity of information technology

The information management system complements the other elements of a very complicated
organizational structure and hospital operations. It functions as an integrator of all these parts by
allowing data to be collected, stored and shared. The Hospital Information System (HIS)'s range, material
and composition perform many distinct tasks. It includes a number of sub-systems and apps (often
referred to as modules) that optimally use ICT and computerization to promote the provision of hospital
facilities.
In particular, a healthcare facility's information systems promote two primary groups of operations,
features and facilities, i.e.:

1. The key function of offering healthcare to its customers

2. Managing the hospital as a business entity, a supplier of medical facilities, and a physical
institution

The Hospital Information System (HIS) focuses mainly on hospital operations management. However, it
is possible to collect, analyze and use the information accessible from the scheme for strategic
management, including studies. The HIS is considered to consist of two wide schemes, i.e.

I. Patient Care Information System

II. Managerial Information System

It is conceptual to divide into these two wide classifications. The information system that promotes the
governance of administrative, intellectual (human) resources, facilities and leisure operations is
arbitrarily put under the Managerial Information System. For the scope of this paper, we will deal with
Information Systems for Patient Care, i.e. the central business function of a hospital.

Activity Diagram

In the attached Visio Drawing, pages 1 and 2 feature Activity Diagrams. These display not only the
processes of patient care, such as obtaining consultancy from doctor then undergoing operation, but
also administrative processes such as checking
into the hospital and paying bills/fees.

UML modeling vocabulary included that for

both developers and stakeholders, these
diagrams are usually readily comprehensible.

In UML for the IT Business Analyst, "The

exercise diagram is the most helpful for the IT
BA to depict job stream [because] it is easy to
understand — for both BAs and end-users."
Since they are among the most user-friendly
diagrams accessible, they are usually
considered to be an important instrument in
the collection of an analyst. In addition, as
mentioned above, activity diagrams enable an
investigator to show various circumstances and
performers through the use of swimlanes within
a workflow. However, swimlanes are
mandatory as a single disease or actor is usually
shown without them.

We see several activities take place, connected

by arrows which show the sequence of events.
Diamonds represent decisions which must be taken and connect to the course of action which is taken
upon making a decision. Fork Nodes represent where parallel decisions must be taken i.e. when two
courses of action occur simultaneously and lead to one activity. Activity diagrams very helpfully indicate
when processes are ending and beginning, hence they are extremely simple to interpret.
Case Diagram

When using Unified Modeling Language (UML), a situation diagram for use enables you know how a
person could communicate with your framework. And ultimately, it should assist your group identify
demands and arrange them. But use case diagrams, with a few modifications, can also be used outside
of software engineering to portray any scheme in which performers work to achieve an objective.

You're going to want to maintain your information minimal like many diagrams and layouts. UML case
diagrams are not intended to provide an in-depth look at each of your system elements. Rather, they
constitute a high-level summary of how instances of use, performers, and the relationship between your
model.

Pages 3 and 4 show visuals of the case diagrams for our two business processes; Patient admission and
Logging of all details into the official database. The human characters represent individuals and their
functions. For e.g. When patients are being admitted into the hospital, it is the job of the Receptionist to
admit the patient and to schedule an appointment with a doctor or consultant and to handle all billing.
Likewise, a doctor must not only treat the patient, but must also fulfill database completion obligations,
such as logging in and filing patient prescriptions.

Ellipses indicate activities occurring whereas arrows show association with individuals who must conduct
said activities. Multiple people can carry out multiple activities and often these are interconnected.
Class Diagrams

Several category diagrams represent the domain model for the Hospital Management System. The
diagram's aim is to illustrate and clarify hospital design, employees, nurse interactions, and terminology
of nurse therapy.
A person may be connected with various hospitals on the diagram in Visio, and a hospital may hire or
service various people. The title and home address of the patient category has obtained characteristics.
Name reflects the complete word and could be coupled by name, title, middle name, and household (or
last) name. Patient category has obtained assign status that can be calculated on the basis of their place
of conception and present date or form of entry to hospital.

This class diagram on pages 5 and 6 shows a set of classes and the relationship between them. Class
includes class name, such as “Doctor”; class attributes such as “Name: string”, and class operations such
as “Prescribe Meds”. Classes are connected based on relationships between them, such as relationship
between patient who pays a bill.

This class diagram shows how one class can have multiple associations and associations. The best
example is the doctor, who is connected to bills, appointments, pharmacy and user credentials. These
connections lead the doctor to be connected to patients and nurses as well, ultimately.

Sequence Diagram

A sequence diagram shows interactions. From the name it is clear that the diagram deals with some
sequences, which are the sequence of messages flowing from one object to another. Interaction
between the components of a system is very important from the point of view of implementation and
execution.

A sequence diagram demonstrates the communication of objects within a given timeframe. Parallel
lifelines display simultaneous tasks while diagonal lines display mutual posts in the sequence in which
they happen. In a graphical way, this means full runtime situations.

In a hospital system we see that the patient takes an appointment from a doctor by interacting with a
receptionist who interacts with the doctor to ascertain whether he is available. If the appointment is
taken that means the doctor was available and vice versa.

The relationship then excludes the receptionist once treatment begins, however, another component,
the nurse is added. Activities are all provided a suitable time-frame. The end of all processes is signified
by the end of the lifeline or, in some cases, by an “X”. This is helpful as it allows even those who are not
proficient in UML to identify processes and their initiation and ending.
State Machine Diagram

An entity's conduct is not only an immediate result of its outputs, but it also relies on its previous state.
The past history of an entity can best be modeled by a finite state machine diagram or traditionally
called automata. UML state machine diagrams (or sometimes referred to as state diagrams, state
machines or state diagrams) indicate an entity's various conditions. State machine diagrams can also
demonstrate how, by shifting from one state to another, an organization reacts to different occurrences.
State machine diagram is a UML diagram for modeling a system's vibrant essence.
Typically, state machine diagram is used to define an object's state-
dependent conduct. An entity reacts to the same case separately based on
the state in which it is. State machine diagrams are generally implemented
to items but can be implemented to any component that has conduct to
other organizations such as: performers, usage instances, techniques,
subsystem structures and so on and are typically used in combination with
diagrams of communication (generally sequence diagrams).

As shown in the Visio drawing, in a hospital management system, a state

machine diagram can be used to express the protocol of a system,
showing which activities must take place and under what circumstances
can we move on to the next one. No process can be carried forward unless
the preceding step is completed such as paying bills. If bills are not paid
then patient must go to reception and settle his dues before consultation
and eventually treatment can begin.

State machine diagram also shows the database kept in hospital records,
where the records of patients can be added, changed or deleted. This
system is especially important in the digital age where everything is
uploaded on the cloud. Years’ worth of data is accessible within minutes
due to this database and can be edited or removed without any
obstruction.
Conclusion

Hospital management scheme helps to record patient data and handle patient request. After
registration, a unique ID will be produced for each individual. This enables manage client relationships
and also retains patient medical background. This scheme also tracks doctor meetings when the person
gets the moment and amount of the meeting from the receptionist and visits the doctor appropriately.
This system also deals with testing appointments as the patient receives the appointment time and
number and submits the test accordingly when and when ID is produced.

It also deals with bed allotments by checking their ID for different clients. By diagnosing the clients, it
also performs multiple procedures. The scheme defines whether the individual is a doctor or employees
and manages multiple operations such as wage drawing and salaries, as well as adding data from
doctor / staff to the database. This scheme is accountable for managing multiple other operations in the
database, such as deleting, publishing doctor / staff data. As the person is diagnosed by the doctor, he
provides therapy and provides people with suggestions and prescribes laboratory exams and
medications.

This scheme also requires charge of medical equipment, doctor's tour, vitality monitoring, patient
condition drawing, diet planning, blood collection, transmission of data and release data, ward
retention, inter-and intra-patient payments, as well as the patient's release overview, which involves
hygiene at the moment of release, medical history, multiple diagnoses and prescriptions for medicines.
Patients can afford the fee by credit card, money or cheque, whose data this scheme maintains.

Resources

(ICMR, 2004)

(VLabs, 2016)

(Blogger, 2011)

(C., 2011)

(U., 2006)