Project Report On Healthcare M

COVENANT UNIVERSITY INSTITUTE BUEA-
CAMEROON
(Knowledge and Wisdom with the Fear of God)
SCHOOL OF ENGINEERING
ELAD BENDRICE EKANGWO
MAT No: 22CU005CE
SUPERVISED BY:
Dr. NYANGA BERNARD Y. (Ph.d)
i
CERTIFICATION
This is to certify that the “Internship report” submitted by ELAD BENDRICE EKANGWO (MAT.
No: 22CU005CE) is work done by him and submitted during 2023 – 2024 academic year, in
partial fulfillment.
ii
DEDICATION
To Almighty GOD who in his infinite mercy, provided me with strength and inspiration in writing
this Internship report and also Dedicating it to the ELAD’s Family for being there to guide me
both spiritually and financially.
iii
ACKNOWLEDGEMENTS
It has been a gratify experience carrying out this internship project and being part of the
COVENANT UNIVERSITY INSTITUTE OF CAMEROON (CUINS). Worth team of dedicated academic
professionals who were committed in making sure the project have new ideas and its being
carried out with present standards. I am grateful to Dr. Nyanga Bernard Y. for guiding me on
project completion and also for the time spent. Professor Nyanga judith Lum N. for rectifying
errors and making sure that the project is of standards. Thanking Yunga Nji Prosper for the
support and making sure obstacles and technical issues are solved. To all the staffs and my
Colleagues who made sure a constant work and new suggestion was put in place.
iv
TABLE OF CONTENTS
CERTIFICATION.............................................................................................................................................ii
DEDICATION................................................................................................................................................iii
ACKNOWLEDGEMENTS................................................................................................................................iv
CHAPTER 1....................................................................................................................................................1
Introduction.................................................................................................................................................1
1.1 PURPOSE................................................................................................................................................2
1.2 PROJECT SCOPE......................................................................................................................................2
1.3 PRODUCT PERSPECTIVE..........................................................................................................................3
CHAPTER 2....................................................................................................................................................4
LITERATURE REVIEW....................................................................................................................................4
2.1 (11 E-healthcare: an analysis of key themes in research........................................................................4
2.2 Role Based Access Control Models for E-Healthcare Systems................................................................5
CHAPTER 3....................................................................................................................................................7
SYSTEM ANALYSIS........................................................................................................................................7
3.1 EXISTING SYSTEM...................................................................................................................................7
3.2 PROPOSED SYSTEM................................................................................................................................7
CHAPTER 4....................................................................................................................................................9
SOFTWARE REQUIREMENT SPECIFICATION:................................................................................................9
4.1 OPERATING ENVIRONMENT...................................................................................................................9
4.1.2 SOFTWARE ENVIRONMENT:................................................................................................................9
4.2 DESIGN AND IMPLEMENTATION CONSTRAINTS...................................................................................11
4.2.1 CONSTRAINTS IN ANALYSIS...............................................................................................................11
4.3 ASSUMPTIONS AND DEPENDENCIES....................................................................................................12
4.4 SYSTEM FEATURES................................................................................................................................12
4.5. EXTERNAL INTERFACE REQUIREMENTS...............................................................................................13
v
4.6 SOFTWARE INTERFACES.......................................................................................................................13
4.8 OTHER NON FUNCTIONAL REQUIREMENTS.........................................................................................14
4.9 PROCESS DESCRIPTION.........................................................................................................................16
CHAPTER 5..................................................................................................................................................19
SYSTEM DESIGN SPECIFICATION.................................................................................................................19
5.1 SYSTEM ARCHITECTURE.......................................................................................................................19
5.2 Use Case model....................................................................................................................................20
5.3 Class Diagram.......................................................................................................................................20
APPENDICES/DIAGRAMS............................................................................................................................21
vi
CHAPTER 1
Introduction
Healthcare is a field in which accurate record keeping and communication are critical and yet in
which the use of computing and networking technology lags behind other fields. Healthcare
professionals and patients are often uncomfortable with computers, and feel that computers
are not central to their healthcare mission, even though they agree that accurate record
keeping and communication are essential to good healthcare. In current healthcare, information
is conveyed from one healthcare professional to another through paper notes or personal
communication. For example, in the United States, electronic communication between
physicians and pharmacists is not typically employed but, rather, the physician writes a
prescription on paper and gives it to the patient. The patient carries the prescription to the
pharmacy, waits in line to give it to a pharmacist, and waits for the pharmacist to fill the
prescription. To improve this process, the prescriptions could be communicated electronically
from the physician to the pharmacist, and the human computer interfaces for the physicians,
nurses, pharmacists and other healthcare professionals could be voice enabled.
According to Carmen Catizone of the National Association of Boards of Pharmacy, there are as
many as 7,000 deaths from incorrect prescriptions in the United States each year. A Washington
Post article indicates that as many as 5% of the 3 billion prescriptions filled each year are
1
incorrect. These numbers indicate that there is an urgent need to reduce the errors in
healthcare.
1.1 PURPOSE
This paper describes a distributed e-healthcare system that uses the Service- Oriented
Architecture as a means of designing, implementing, and managing healthcare services .
1.2 PROJECT SCOPE
Effective and timely communication between patients, physicians, nurses, pharmacists, and
other healthcare professionals is vital to good healthcare. Current communication mechanisms,
based largely on paper records and prescriptions, are old-fashioned, inefficient, and unreliable.
When multiple healthcare professionals and facilities are involved in providing healthcare for a
patient, the healthcare services provided aren’t often coordinated. Typically, a physician writes
a prescription on paper and gives it to the patient. The patient carries the prescription to the
pharmacy, waits in line to hand the prescription to the pharmacist, and waits for the pharmacist
to fill the prescription. The pharmacist might be unable to read the physician’s handwriting; the
patient could modify or forge the prescription; or the physician might be unaware of
medications prescribed by other physicians. These and other problems indicate the need to
improve the quality of healthcare.
A distributed electronic healthcare system based on the service- oriented architecture (SOA) can
address some of these issues and problems. We developed a distributed e-healthcare system
for use by physicians, nurses, pharmacists, and other professionals, as well as by patients and
2
medical devices used to monitor patients. Multimedia input and output— with text, images, and
speech—make the system less computer- like and more attractive to users who aren’t
computer-oriented.
1.3 PRODUCT PERSPECTIVE
Our prototype distributed e-healthcare system uses SOA to enforce basic software architecture
principles and provide interoperability between different computing platforms and applications
that communicate with each other. Although our distributed e-healthcare system provides user-
friendly interfaces for busy healthcare professionals and patients, security and privacy are
particularly important in this area, so we designed the prototype with security and privacy in
mind. The system authenticates users and logs session information and attaches resources to
the resource creator, so that only privileged users can view or modify the data
3
CHAPTER 2
LITERATURE REVIEW
2.1 (11 E-healthcare: an analysis of key themes in research
Avinandan Mukherjee, John McGinnis -International Journal of Pharmaceutical
and Healthcare Marketing 2007.
Purpose - Healthcare is among the fastest-growing sectors in both developed and emerging
economies. E-healthcare is contributing to the explosive growth within this industry by utilizing
the internet and all its capabilities to support its stakeholders with information searches and
communication processes. The purpose of this paper is to present the state-of-the-art and to
identify key themes in research on e-healthcare.
Design/methodology/approach - A review of the literature in the marketing and management of
e-healthcare was conducted to determine the major themes pertinent to e-healthcare research
as well as the commonalities and differences within these themes.
Findings - Based on the literature review, the five major themes of e-healthcare research
identified are: cost savings; virtual networking; electronic medical records; source credibility and
privacy concerns; and physician-patient relationships.
Originality/value - Based on these major themes, managerial implications for e-healthcare are
formulated. Suggestions are offered to facilitate healthcare service organizations' attempts to
4
further implement and properly utilize e-healthcare in their facilities. These propositions will
also help these stakeholders develop and streamline their e-healthcare processes already in use.
E-healthcare systems enable firms to
improve efficiency, to reduce costs, and to facilitate the coordination of care across multiple
facilities.
2.2 Role Based Access Control Models for E-Healthcare Systems
Covenant University Institute -Department of Computer and Information
Sciences
E-healthcare is the use of web-based systems to share and deliver information across the
internet. With this ability, privacy and security must be maintained according to the Health
Insurance Portability and Accountability Act (HIPAA) standards. The reasonable approach to
developing a system that can meet these requirements is a system that utilizes role-based
models. Role-based access control (RBAC) is important because personnel could change but the
position and access to the safe information keeps stable. With a role-based model it becomes
easier to maintain access control, assign privileges, and personnel to the appropriate role .
Implementation is based off the security policy, which is a critical component of any system
because it defines which roles or people have access to what information. An extensible markup
5
language (XML) is used to enforce this policy because it is a web-based technology that is good
for data transportation and security. Within this research project, we are able to give an
overview for the state-of-art of secure e-healthcare system, and better understand a way of
implementing a secure e-healthcare system that meets HIPAA standards and can share
information to patients and healthcare facilities via the web service.
A Distributed e-Healthcare System Based on the Service Oriented Architecture
Kart, F. Gengxin Miao Moser, L.E. Melliar-Smith, P.M. Dept. of Electr. & Comput.
Eng., Univ. of California, Santa Barbara, CA;
Large-scale distributed systems, such as e-healthcare systems, are difficult to develop due to
their complex and decentralized nature. The service oriented architecture facilitates the
development of such systems by supporting modular design, application integration and
interoperation, and software reuse. With open standards, such as XML, SOAP, WSDL and UDDI,
the service oriented architecture supports interoperability between services operating on
different platforms and between applications implemented in different programming languages.
In this paper we describe a distributed e-healthcare system that uses the service oriented
architecture as a basis for designing, implementing, deploying, invoking and managing
healthcare services. The e-healthcare system that we have developed provides support for
physicians, nurses, pharmacists and other healthcare professionals, as well as for patients and
medical devices used to monitor patients. Multi-media input and output, with text, images and
speech, make the system more user friendly than existing e-healthcare systems.
6
CHAPTER 3
SYSTEM ANALYSIS AND DESIGN
3.1 EXISTING SYSTEM
• In existing e-Healthcare systems has focused on record keeping and databases.
• It has also focused on access and security for recording and communicating healthcare
information
• Human errors are more by exploiting electronic communication and record keeping.
3.2 PROPOSED SYSTEM
• This system aims to reduce human errors by exploiting electronic communication and record
keeping, and by providing user-friendly input and output capabilities.
• Modern technology is use to expose the functionality of our e-healthcare system as Web
Services based on the Service Oriented Architecture, so that both humans and applications can
use the services provided.
7
• It provides services that involve patients, physicians, nurses and pharmacists as well as
medical monitoring devices, whereas their framework focuses specifically on the use of medical
monitoring devices.
8
SYSTEM DESIGN SPECIFICATION
3.3 SYSTEM ARCHITECTURE
Clinic WS Patient WS
Application Server
Clinicians Database
3. Patients
Web Clinic WS Patient WS
Service
Web Service Patient Web service Pharmacist Web Service
Database
Pharmacist
Application Patient Web Pharmacist Web server

Server server
9
3.4 Use Case model
The use case model is model that describes the requirement of the system in diagrammatic
form based on UML language. It describes the relationship between the actors of the system
and use case of the system. UML stands for Unified Modeling Language. Figure 1.1: below
shows the use case model of the system.
3.5 Class Diagram
The class diagram is a model that describes the functions of the system both public and private
operate base on UML language. That is, the Actor functions linked to other activities such as
their roles and how the communication flows in the system. Figure 1.2 below shows the class
diagram mode of the system.
10
APPENDICES/DIAGRAMS
Fig.1.1 USE CASE MODEL OF HEALTHCARE MANAGEMENT SYSTEM
11
Fig.1.2 CLASS DIAGRAM MODEL OF HEALTHCARE MANAGEMENT
SYSTEM
12
CHAPTER 4
SOFTWARE REQUIREMENT SPECIFICATION:
4.1 OPERATING ENVIRONMENT
4.1.1 HARDWARE ENVIRONMENT:
• Hard Disk: 10GB and Above
• RAM: 512MB and Above
• Processor: Pentium III and Above
4.1.2 SOFTWARE ENVIRONMENT:
• Windows Operating System 10 and Above
• Web Browser - Internet Explorer
• Apache Tomcat 5.5 Server
 XAMPP
• XML
13
This tutorial introduces Derby's basic features and walks you through using both frameworks;
first the embedded framework using the Derby Embedded JDBC driver, then the Network Server
framework using the Derby Network Client JDBC driver.
APACHE TOMCAT:
Apache Tomcat is an implementation of the Java Servlet and Java Server Pages technologies.
The Java Servlet and JavaServer Pages specifications are developed under the Java Community
Process Apache Tomcat is developed in an open and participatory environment and released
under the Apache Software Liscense. Apache Tomcat is intended to be a collaboration of the
best-of-breed developers from around the world.
XML:
Java Platform, Micro Edition (Java ME) provides a robust, flexible environment for applications
running on mobile and other embedded devices
—mobile phones, personal digital assistants (PDAs), TV set-top boxes, and printers. Java ME
includes flexible user interfaces, robust security, built-in network protocols, and support for
14
networked and offline applications that can be downloaded dynamically. Applications based on
Java ME are portable across many devices, yet leverage each device's native capabilities.
4.2 DESIGN AND IMPLEMENTATION CONSTRAINTS
4.2.1 CONSTRAINTS IN ANALYSIS
• Constraints as Informal Text
• Constraints as Operational Restrictions
• Constraints Integrated in Existing Model Concepts
• Constraints as a Separate Concept
• Constraints Implied by the Model Structure
4.2.2 CONSTRAINTS IN DESIGN
• Determination of the Involved Classes
• Determination of the Involved Objects
• Determination of the Require Clauses
• Global actions and Constraint Realization
15
4.3 ASSUMPTIONS AND DEPENDENCIES
A hierarchical structuring of relations may result in more classes and a more complicated
structure to implement. Therefore it is advisable to transform the hierarchical relation
structure to a simpler structure such as a classical flat one. It is rather straightforward to
transform the developed hierarchical model into a bipartite, flat model, consisting of
classes on the one hand and flat relations on the other. Flat relations are preferred at the
design level for reasons of simplicity and implementation ease. There is no identity or
functionality associated with a flat relation.
4.4 SYSTEM FEATURES
A distributed e-healthcare system can help solve this conundrum.
Medical monitoring devices worn by the patient, and frequent electronic
communication between the patient and a nurse, can ensure that the prescribed
treatment is being followed and that the patient is making good progress.
16
4.5. EXTERNAL INTERFACE REQUIREMENTS
4.5.1User Interfaces
The User Interface is Web Browsers like Internet Explorer, Mozilla Firefox, opera, etc.
4.5.2 SERVER SIDE
The web application will be hosted on one of the department's Linux servers and
connecting to one of the school Oracle Database server. The web server is listening on
the web standard port, port 80.
4.5.3 CLIENT SIDE
The system is a web based application; clients are requiring using a modern web browser
such as Mozilla Firebox 1.5, Internet Explorer 6 and Enable Cookies. The computer must
have an Internet connection in order to be able to access the system.
4.6 SOFTWARE INTERFACES
4.6.1 SERVER SIDE
17
The system already has the required software to host a Java web application. An Apache
Web server will accept all requests from the client and forward specific requests to
Tomcat 5.5 Servlet Container with JEE 5.0
4.6.2 CLIENT SIDE
An OS is capable of running a modern web browser which supports HTML version 3.2 or
higher.
4.7 COMMUNICATION INTERFACES
The HTTP protocol will be used to facilitate communications between the client and
server.
4.8 OTHER NON FUNCTIONAL REQUIREMENTS
4.8.1 PERFORMANCE REQUIREMENTS
We expect that most pages be returned in 1 second or less to users for whom
bandwidth isn't an issue. We will attempt to keep pages to a reasonable size, however, in
order to ensure that users with slow connections (e.g. 56K) do not experience a delay of
more than 3 seconds for most pages.
One way to do this is to limit queries so they do not return more than 20 events per
page. For larger pages, or pages that return search results from the database, we expect
page returns of 3 seconds for users with fast connections and 5 seconds for users with
slower connections to be reasonable.
18
4.8.2 SAFETY REQUIREMENTS
The software may be safety-critical. If so, there are issues associated with its integrity
level. The software may not be safety-critical although it forms part of a safety-critical
system. For example, software may simply log transactions. If a system must be of a high
integrity level and if the software is shown to be of that integrity level, then the
hardware must be at least of the same integrity level. There is little point in producing
'perfect' code in some language if hardware and system software (in widest sense) are
not reliable. If a computer system is to run software of a high integrity level then that
system should not at the same time accommodate software of a lower integrity level.
Systems with different requirements for safety levels must be separated. Otherwise, the
highest level of integrity required must be applied to all systems in the same
environment.
4.8.3 SECURITY REQUIREMENTS
Do not block the some available ports through the windows firewall
Two machines should be connected with LAN setting.
4.8.4 SOFTWARE QUALITY ATTRIBUTES
Functionality: are the required functions available, including interoperability and
security.
Reliability: maturity, fault tolerance and recoverability.
Usability: how easy it is to understand, learn and operate the software system.
19
Efficiency: performance and resource behavior.
Maintainability: how easy is it to modify the software.
Portability: can the software easily be transferred to another environment, including
install ability.
4.9 PROCESS DESCRIPTION
Clinical Module:
Input:
• Physician Login Page.
• Enter the username and password.
Process:
• Clinical staff services.
• Add patient data / notes
• Forwards the prescription to the patient and pharmacy.
20
• Make referrals to other physician
• Patient services:
• Make appointments
• Deliver notification
Output:
• Select the menu bar.
• Patient Diagnosis data.
• Patient appointment
Healthcare module:
Input:
Healthcare Login page.
Process:
Pharmacy Services:
21
Receive / view / fill prescriptions
Patient Services
• Enable renewals of prescriptions
• Provide notification
Output:
Menu bar (delivery date, today delivery, medicine details). Select any one from menu
bar.
22
CHAPTER 5
CONCLUSION AND RECOMMENDATION
5.1 CONCLUSION
At this point, thou the internship report project was a though one there by, coming to termination was a
challenge.
Some issues face are;
 ISSUES GETTING RESPECTIVE SOFTWARES: It was not an easy task downloading the
recommended software for the system as some updates required paid version.
 POOR INTERNET CONNECTION: getting dependences and other upgraded packages on the
internet was a problem of a kind, because at some period internet was very slow.
 POWER FAILURE: Due to our current time that at some area like mine has electrical blackout
sometimes thereby, making this project to be slower than expected.
5.2 RECOMMENDATIONS
 Getting respective software should be solved by keeping a download for the application needed
for that processor.
 Poor internet connection can be solved by getting better WiFI Routers and a choice of alternative
for which Network is best at the moment.
 For unforeseen circumstances, a stand by Generator should be installed in case of power outage.
23
Below are System codes and screenshots
LOGIN PAGE
LOGIN CODES
<x-guest-layout>
<x-authentication-card>
<x-slot name="logo">
<x-authentication-card-logo />
</x-slot>
<x-validation-errors class="mb-4" />
@session('status')
<div class="mb-4 font-medium text-sm text-green-600">
{{ $value }}
</div>
24
@endsession
<form method="POST" action="{{ route('login') }}">
@csrf
<div>
<x-label for="email" value="{{ __('Email') }}" />
<x-input id="email" class="block mt-1 w-full" type="email" name="email" :value="old('email')"

required autofocus autocomplete="username" />
</div>
<div class="mt-4">
<x-label for="password" value="{{ __('Password') }}" />
<x-input id="password" class="block mt-1 w-full" type="password" name="password" required

autocomplete="current-password" />
</div>
<div class="block mt-4">
<label for="remember_me" class="flex items-center">
<x-checkbox id="remember_me" name="remember" />
<span class="ms-2 text-sm text-gray-600">{{ __('Remember me') }}</span>
</label>
</div>
<div class="flex items-center justify-end mt-4">
@if (Route::has('password.request'))
25
<a class="underline text-sm text-gray-600 hover:text-gray-900 rounded-md focus:outline-
none focus:ring-2 focus:ring-offset-2 focus:ring-indigo-500" href="{{ route('password.request') }}">
{{ __('Forgot your password?') }}
</a>
@endif
<x-button class="ms-4">
{{ __('Log in') }}
</x-button>
</div>
</form>
</x-authentication-card>
</x-guest-layout>
26
REGISTRATION PAGE
REGISTRATION PAGE CODES
<x-guest-layout>
<x-authentication-card>
<x-slot name="logo">
<x-authentication-card-logo />
</x-slot>
<x-validation-errors class="mb-4" />
<form method="POST" action="{{ route('register') }}">
@csrf
<div>
<x-label for="name" value="{{ __('Name') }}" />
27
<x-input id="name" class="block mt-1 w-full" type="text" name="name" :value="old('name')"
required autofocus autocomplete="name" />
</div>
<div class="mt-4">
<x-label for="email" value="{{ __('Email') }}" />
<x-input id="email" class="block mt-1 w-full" type="email" name="email" :value="old('email')"

required autocomplete="username" />
</div>
<div>
<x-label for="phone" value="{{ __('phone') }}" />
<x-input id="phone" class="block mt-1 w-full" type="text" name="phone" :value="old('')"

required autofocus autocomplete="phone" />
</div>
<div>
<x-label for="address" value="{{ __('address') }}" />
<x-input id="address" class="block mt-1 w-full" type="text"

name="address" :value="old('address')" required autofocus autocomplete="address" />
</div>
<div class="mt-4">
<x-label for="password" value="{{ __('Password') }}" />
<x-input id="password" class="block mt-1 w-full" type="password" name="password" required

autocomplete="new-password" />
</div>
<div class="mt-4">
<x-label for="password_confirmation" value="{{ __('Confirm Password') }}" />

28
<x-input id="password_confirmation" class="block mt-1 w-full" type="password"
name="password_confirmation" required autocomplete="new-password" />
</div>
@if (Laravel\Jetstream\Jetstream::hasTermsAndPrivacyPolicyFeature())
<div class="mt-4">
<x-label for="terms">
<div class="flex items-center">
<x-checkbox name="terms" id="terms" required />
<div class="ms-2">
{!! __('I agree to the :terms_of_service and :privacy_policy', [
'terms_of_service' => '<a target="_blank" href="'.route('terms.show').'"

class="underline text-sm text-gray-600 hover:text-gray-900 rounded-md focus:outline-none focus:ring-2
focus:ring-offset-2 focus:ring-indigo-500">'.__('Terms of Service').'</a>',
'privacy_policy' => '<a target="_blank" href="'.route('policy.show').'"

class="underline text-sm text-gray-600 hover:text-gray-900 rounded-md focus:outline-none focus:ring-2
focus:ring-offset-2 focus:ring-indigo-500">'.__('Privacy Policy').'</a>',
]) !!}
</div>
</div>
</x-label>
</div>
@endif
<div class="flex items-center justify-end mt-4">
<a class="underline text-sm text-gray-600 hover:text-gray-900 rounded-md focus:outline-none

focus:ring-2 focus:ring-offset-2 focus:ring-indigo-500" href="{{ route('login') }}">
29
{{ __('Already registered?') }}
</a>
<x-button class="ms-4">
{{ __('Register') }}
</x-button>
</div>
</form>
</x-authentication-card>
</x-guest-layout>
30
DASHBOARD FOR ADMIN
DASHBOARD CODES
<!DOCTYPE html>
<html lang="en">
<head>

<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<title>Hospital</title>

<link rel="stylesheet" href="assets/vendors/mdi/css/materialdesignicons.min.css">
<link rel="stylesheet" href="assets/vendors/css/vendor.bundle.base.css">


<link rel="stylesheet" href="assets/vendors/jvectormap/jquery-jvectormap.css">
31
<link rel="stylesheet" href="assets/vendors/flag-icon-css/css/flag-icon.min.css">
<link rel="stylesheet" href="assets/vendors/owl-carousel-2/owl.carousel.min.css">
<link rel="stylesheet" href="assets/vendors/owl-carousel-2/owl.theme.default.min.css">




<link rel="stylesheet" href="assets/css/style.css">

<link rel="shortcut icon" href="assets/images/favicon.png" />
</head>
<body>
<div class="container-scroller">
<div class="row p-0 m-0 proBanner" id="proBanner">
<div class="col-md-12 p-0 m-0">
<div class="card-body card-body-padding d-flex align-items-center justify-content-between">
<div class="ps-lg-1">
<div class="d-flex align-items-center justify-content-between">
<p class="mb-0 font-weight-medium me-3 buy-now-text">Free 24/7 customer support,

updates, and more with this template!</p>
<a href="https://www.bootstrapdash.com/product/corona-free/?
utm_source=organic&utm_medium=banner&utm_campaign=buynow_demo" target="_blank"
class="btn me-2 buy-now-btn border-0">Get Pro</a>
</div>
</div>
<div class="d-flex align-items-center justify-content-between">
32
<a href="https://www.bootstrapdash.com/product/corona-free/"><i class="mdi mdi-home me-3
text-white"></i></a>
<button id="bannerClose" class="btn border-0 p-0">
<i class="mdi mdi-close text-white me-0"></i>
</button>
</div>
</div>
</div>
</div>

<nav class="sidebar sidebar-offcanvas" id="sidebar">
<div class="sidebar-brand-wrapper d-none d-lg-flex align-items-center justify-content-center fixed-

top">
<a class="sidebar-brand brand-logo" href="index.html"><img src="assets/images/logo.svg"

alt="logo" /></a>
<a class="sidebar-brand brand-logo-mini" href="index.html"><img src="assets/images/logo-

mini.svg" alt="logo" /></a>
</div>
<ul class="nav">
<li class="nav-item profile">
<div class="profile-desc">
<div class="profile-pic">
<div class="count-indicator">
<img class="img-xs rounded-circle " src="assets/images/faces/face15.jpg" alt="">
<span class="count bg-success"></span>
</div>
<div class="profile-name">
33
<h5 class="mb-0 font-weight-normal">Henry Klein</h5>
<span>Gold Member</span>
</div>
</div>
<a href="#" id="profile-dropdown" data-bs-toggle="dropdown"><i class="mdi mdi-dots-

vertical"></i></a>
<div class="dropdown-menu dropdown-menu-right sidebar-dropdown preview-list" aria-

labelledby="profile-dropdown">
<a href="#" class="dropdown-item preview-item">
<div class="preview-thumbnail">
<div class="preview-icon bg-dark rounded-circle">
<i class="mdi mdi-settings text-primary"></i>
</div>
</div>
<div class="preview-item-content">
<p class="preview-subject ellipsis mb-1 text-small">Account settings</p>
</div>
</a>
<div class="dropdown-divider"></div>
<i class="mdi mdi-onepassword text-info"></i>
</div>
</div>
34
<p class="preview-subject ellipsis mb-1 text-small">Change Password</p>
</div>
</a>
<i class="mdi mdi-calendar-today text-success"></i>
</div>
</div>
<p class="preview-subject ellipsis mb-1 text-small">To-do list</p>
</div>
</a>
</div>
</div>
</li>
<li class="nav-item nav-category">
<span class="nav-link">Navigation</span>
</li>
<li class="nav-item menu-items">
<a class="nav-link" href="index.html">
<span class="menu-icon">
<i class="mdi mdi-speedometer"></i>
</span>
<span class="menu-title">Dashboard</span>
35
</a>
</li>
<a class="nav-link" data-bs-toggle="collapse" href="#ui-basic" aria-expanded="false" aria-

controls="ui-basic">
<i class="mdi mdi-laptop"></i>
</span>
<span class="menu-title">Basic UI Elements</span>
<i class="menu-arrow"></i>
</a>
<div class="collapse" id="ui-basic">
<ul class="nav flex-column sub-menu">
<li class="nav-item"> <a class="nav-link"

href="pages/ui-features/buttons.html">Buttons</a></li>

href="pages/ui-features/dropdowns.html">Dropdowns</a></li>

href="pages/ui-features/typography.html">Typography</a></li>
</ul>
</div>
</li>
<a class="nav-link" href="pages/forms/basic_elements.html">
<i class="mdi mdi-playlist-play"></i>
</span>
36
<span class="menu-title">Form Elements</span>
</a>
</li>
<a class="nav-link" href="pages/tables/basic-table.html">
<i class="mdi mdi-table-large"></i>
</span>
<span class="menu-title">Tables</span>
</a>
</li>
<a class="nav-link" href="pages/charts/chartjs.html">
<i class="mdi mdi-chart-bar"></i>
</span>
<span class="menu-title">Charts</span>
</a>
</li>
<a class="nav-link" href="pages/icons/mdi.html">
<i class="mdi mdi-contacts"></i>
</span>
<span class="menu-title">Icons</span>
</a>
37
</li>
<a class="nav-link" data-bs-toggle="collapse" href="#auth" aria-expanded="false" aria-

controls="auth">
<i class="mdi mdi-security"></i>
</span>
<span class="menu-title">User Pages</span>
<i class="menu-arrow"></i>
</a>
<div class="collapse" id="auth">
<ul class="nav flex-column sub-menu">
<li class="nav-item"> <a class="nav-link" href="pages/samples/blank-page.html"> Blank Page

</a></li>
<li class="nav-item"> <a class="nav-link" href="pages/samples/error-404.html"> 404 </a></li>
<li class="nav-item"> <a class="nav-link" href="pages/samples/error-500.html"> 500 </a></li>
<li class="nav-item"> <a class="nav-link" href="pages/samples/login.html"> Login </a></li>
<li class="nav-item"> <a class="nav-link" href="pages/samples/register.html"> Register

</a></li>
</ul>
</div>
</li>
<a class="nav-link"
href="http://www.bootstrapdash.com/demo/corona-free/jquery/documentation/documentation.html">
<i class="mdi mdi-file-document-box"></i>
38
</span>
<span class="menu-title">Documentation</span>
</a>
</li>
</ul>
</nav>

<div class="container-fluid page-body-wrapper">

<nav class="navbar p-0 fixed-top d-flex flex-row">
<div class="navbar-brand-wrapper d-flex d-lg-none align-items-center justify-content-center">
<a class="navbar-brand brand-logo-mini" href="index.html"><img src="assets/images/logo-

mini.svg" alt="logo" /></a>
</div>
<div class="navbar-menu-wrapper flex-grow d-flex align-items-stretch">
<button class="navbar-toggler navbar-toggler align-self-center" type="button" data-

toggle="minimize">
<span class="mdi mdi-menu"></span>
</button>
<ul class="navbar-nav w-100">
<li class="nav-item w-100">
<form class="nav-link mt-2 mt-md-0 d-none d-lg-flex search">
<input type="text" class="form-control" placeholder="Search products">
</form>
</li>
</ul>
39
<ul class="navbar-nav navbar-nav-right">
<li class="nav-item dropdown d-none d-lg-block">
<a class="nav-link btn btn-success create-new-button" id="createbuttonDropdown" data-bs-

toggle="dropdown" aria-expanded="false" href="#">+ Create New Project</a>
<div class="dropdown-menu dropdown-menu-right navbar-dropdown preview-list" aria-

labelledby="createbuttonDropdown">
<h6 class="p-3 mb-0">Projects</h6>
<a class="dropdown-item preview-item">
<i class="mdi mdi-file-outline text-primary"></i>
</div>
</div>
<p class="preview-subject ellipsis mb-1">Software Development</p>
</div>
</a>
<i class="mdi mdi-web text-info"></i>
</div>
</div>
40
<p class="preview-subject ellipsis mb-1">UI Development</p>
</div>
</a>
<i class="mdi mdi-layers text-danger"></i>
</div>
</div>
<p class="preview-subject ellipsis mb-1">Software Testing</p>
</div>
</a>
<p class="p-3 mb-0 text-center">See all projects</p>
</div>
</li>
<li class="nav-item nav-settings d-none d-lg-block">
<a class="nav-link" href="#">
<i class="mdi mdi-view-grid"></i>
</a>
</li>
<li class="nav-item dropdown border-left">
<a class="nav-link count-indicator dropdown-toggle" id="messageDropdown" href="#" data-bs-

toggle="dropdown" aria-expanded="false">
41
<i class="mdi mdi-email"></i>
<span class="count bg-success"></span>
</a>

labelledby="messageDropdown">
<h6 class="p-3 mb-0">Messages</h6>
<img src="assets/images/faces/face4.jpg" alt="image" class="rounded-circle profile-pic">
</div>
<p class="preview-subject ellipsis mb-1">Mark send you a message</p>
<p class="text-muted mb-0"> 1 Minutes ago </p>
</div>
</a>
</div>
<p class="preview-subject ellipsis mb-1">Cregh send you a message</p>
</div>
</a>
42
</div>
<p class="preview-subject ellipsis mb-1">Profile picture updated</p>
</div>
</a>
<p class="p-3 mb-0 text-center">4 new messages</p>
</div>
</li>
<li class="nav-item dropdown border-left">
<a class="nav-link count-indicator dropdown-toggle" id="notificationDropdown" href="#" data-

bs-toggle="dropdown">
<i class="mdi mdi-bell"></i>
<span class="count bg-danger"></span>
</a>

labelledby="notificationDropdown">
<h6 class="p-3 mb-0">Notifications</h6>
43
<i class="mdi mdi-calendar text-success"></i>
</div>
</div>
<p class="preview-subject mb-1">Event today</p>
<p class="text-muted ellipsis mb-0"> Just a reminder that you have an event today </p>
</div>
</a>
<i class="mdi mdi-settings text-danger"></i>
</div>
</div>
<p class="preview-subject mb-1">Settings</p>
<p class="text-muted ellipsis mb-0"> Update dashboard </p>
</div>
</a>
<i class="mdi mdi-link-variant text-warning"></i>
44
</div>
</div>
<p class="preview-subject mb-1">Launch Admin</p>
<p class="text-muted ellipsis mb-0"> New admin wow! </p>
</div>
</a>
<p class="p-3 mb-0 text-center">See all notifications</p>
</div>
</li>
<li class="nav-item dropdown">
<a class="nav-link" id="profileDropdown" href="#" data-bs-toggle="dropdown">
<div class="navbar-profile">
<img class="img-xs rounded-circle" src="assets/images/faces/face15.jpg" alt="">
<p class="mb-0 d-none d-sm-block navbar-profile-name">Henry Klein</p>
<i class="mdi mdi-menu-down d-none d-sm-block"></i>
</div>
</a>

labelledby="profileDropdown">
<h6 class="p-3 mb-0">Profile</h6>
45
<i class="mdi mdi-settings text-success"></i>
</div>
</div>
<p class="preview-subject mb-1">Settings</p>
</div>
</a>
<i class="mdi mdi-logout text-danger"></i>
</div>
</div>
<p class="preview-subject mb-1">Log out</p>
</div>
</a>
<p class="p-3 mb-0 text-center">Advanced settings</p>
</div>
</li>
</ul>
<button class="navbar-toggler navbar-toggler-right d-lg-none align-self-center" type="button"

data-toggle="offcanvas">
<span class="mdi mdi-format-line-spacing"></span>
46
</button>
</div>
</nav>



<footer class="footer">
<div class="d-sm-flex justify-content-center justify-content-sm-between">
<span class="text-muted d-block text-center text-sm-left d-sm-inline-block">Copyright ©

bootstrapdash.com 2021</span>
<span class="float-none float-sm-right d-block mt-1 mt-sm-0 text-center"> Free <a

href="https://www.bootstrapdash.com/bootstrap-admin-template/" target="_blank">Bootstrap admin
template</a> from Bootstrapdash.com</span>
</div>
</footer>

</div>

</div>

</div>


<script src="assets/vendors/js/vendor.bundle.base.js"></script>


47
<script src="assets/vendors/chart.js/Chart.min.js"></script>
<script src="assets/vendors/progressbar.js/progressbar.min.js"></script>
<script src="assets/vendors/jvectormap/jquery-jvectormap.min.js"></script>
<script src="assets/vendors/jvectormap/jquery-jvectormap-world-mill-en.js"></script>
<script src="assets/vendors/owl-carousel-2/owl.carousel.min.js"></script>
<script src="assets/js/jquery.cookie.js" type="text/javascript"></script>


<script src="assets/js/off-canvas.js"></script>
<script src="assets/js/hoverable-collapse.js"></script>
<script src="assets/js/misc.js"></script>
<script src="assets/js/settings.js"></script>
<script src="assets/js/todolist.js"></script>


<script src="assets/js/dashboard.js"></script>

</body>
</html>
48

Project Report On Healthcare M

Uploaded by

Copyright:

Available Formats

Project Report On Healthcare M

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Report On Healthcare M

Uploaded by

Copyright:

Available Formats

COVENANT UNIVERSITY INSTITUTE BUEA-

ELAD BENDRICE EKANGWO

MAT No: 22CU005CE

communication. For example, in the United States, electronic communication between

prescription. To improve this process, the prescriptions could be communicated electronically

nurses, pharmacists and other healthcare professionals could be voice enabled.

Architecture as a means of designing, implementing, and managing healthcare services .

1.2 PROJECT SCOPE

other healthcare professionals is vital to good healthcare. Current communication mechanisms,

improve the quality of healthcare.

1.3 PRODUCT PERSPECTIVE

2.1 (11 E-healthcare: an analysis of key themes in research

Avinandan Mukherjee, John McGinnis -International Journal of Pharmaceutical

and Healthcare Marketing 2007.

identify key themes in research on e-healthcare.

Design/methodology/approach - A review of the literature in the marketing and management of

as well as the commonalities and differences within these themes.

privacy concerns; and physician-patient relationships.

formulated. Suggestions are offered to facilitate healthcare service organizations' attempts to

E-healthcare systems enable firms to

2.2 Role Based Access Control Models for E-Healthcare Systems

Covenant University Institute -Department of Computer and Information

information to patients and healthcare facilities via the web service.

A Distributed e-Healthcare System Based on the Service Oriented Architecture

Eng., Univ. of California, Santa Barbara, CA;

development of such systems by supporting modular design, application integration and

the service oriented architecture supports interoperability between services operating on

different platforms and between applications implemented in different programming languages.

architecture as a basis for designing, implementing, deploying, invoking and managing

SYSTEM ANALYSIS AND DESIGN

3.1 EXISTING SYSTEM

• In existing e-Healthcare systems has focused on record keeping and databases.

3.2 PROPOSED SYSTEM

keeping, and by providing user-friendly input and output capabilities.

use the services provided.

3.3 SYSTEM ARCHITECTURE

Web Clinic WS Patient WS

Web Service Patient Web service Pharmacist Web Service

Application Patient Web Pharmacist Web server

shows the use case model of the system.

3.5 Class Diagram

diagram mode of the system.

Fig.1.1 USE CASE MODEL OF HEALTHCARE MANAGEMENT SYSTEM

SOFTWARE REQUIREMENT SPECIFICATION:

4.1 OPERATING ENVIRONMENT

4.1.1 HARDWARE ENVIRONMENT:

• Hard Disk: 10GB and Above

• RAM: 512MB and Above

• Processor: Pentium III and Above

4.1.2 SOFTWARE ENVIRONMENT:

• Windows Operating System 10 and Above

• Web Browser - Internet Explorer

• Apache Tomcat 5.5 Server

framework using the Derby Network Client JDBC driver.

best-of-breed developers from around the world.

running on mobile and other embedded devices

4.2 DESIGN AND IMPLEMENTATION CONSTRAINTS

4.2.1 CONSTRAINTS IN ANALYSIS