Introduction

The healthcare industry has undergone a significant transformation in recent years, driven by
advancements in technology and the increasing demand for efficient and patient-centric
services. One of the key components enabling this transformation is the adoption of Hospital
Management Systems (HMS). These comprehensive software solutions aim to streamline
and automate various processes within healthcare facilities, ultimately improving patient
care, enhancing operational efficiency, and reducing administrative burdens.

1.1. Project Overview

The Hospital Management System Website project is an ambitious endeavor that aims to
develop a robust and user-friendly web-based platform to facilitate the efficient management
of hospital operations. This system will serve as a centralized hub, integrating various
modules and functionalities essential for the smooth functioning of a healthcare facility.

The HMS Website will encompass a wide range of features, including patient management,
medical records management, appointment scheduling, billing and finance, inventory
management, human resources management, and reporting and analytics. By consolidating
these critical components into a single platform, the system will enable healthcare
professionals, administrative staff, and patients to access relevant information and perform
necessary tasks seamlessly.

One of the key objectives of the HMS Website is to provide a seamless and intuitive user
experience, ensuring that all stakeholders can navigate and interact with the system
effortlessly. The website will feature a responsive and modern design, optimized for various
devices, including desktops, laptops, tablets, and smartphones, ensuring accessibility from
anywhere, at any time.

The system's backend will be built on a robust and scalable architecture, leveraging cutting-
edge technologies and adhering to industry best practices for security, performance, and
maintainability. The data storage and management components will be designed to handle
large volumes of sensitive healthcare information while ensuring compliance with relevant
regulations and privacy standards.

1.2. Objectives

The primary objectives of the Hospital Management System Website project are as follows:

1. Enhance Operational Efficiency: Streamline and automate various hospital processes,

reducing administrative overhead, and improving overall operational efficiency.

2. Improve Patient Care: Facilitate better coordination among healthcare providers, ensure
accurate and timely documentation, and promote data-driven decision-making, ultimately
contributing to improved patient outcomes.

1
3. Centralized Information Management: Provide a centralized platform for storing,
accessing, and managing patient medical records, appointment schedules, billing
information, inventory levels, and staff records.

4. Enhance Data Security and Privacy: Implement robust security measures, including
role-based access control, data encryption, and audit trails, to ensure the confidentiality and
integrity of sensitive healthcare data.

5. Facilitate Reporting and Analytics: Generate comprehensive reports and dashboards,

providing valuable insights into various aspects of hospital operations, enabling data-driven
decision-making and performance monitoring.

6. Promote Interoperability: Enable seamless integration with other healthcare systems,

such as laboratory information systems (LIS), picture archiving and communication systems
(PACS), and electronic health records (EHR), facilitating data exchange and collaboration
among different healthcare entities.

7. User-friendly Interface: Develop an intuitive and user-friendly interface that ensures

ease of use for healthcare professionals, administrative staff, and patients, reducing the
learning curve and increasing adoption rates.

1.3. Scope and Limitations

The scope of the Hospital Management System Website project encompasses the
development of a comprehensive web-based platform that addresses the core requirements of
hospital operations. The system will include the following modules:

1. Patient Management: This module will handle patient registration, maintain electronic
medical records (EMR), facilitate appointment scheduling, and track patient history and
treatments.

2. Medical Records Management: The system will securely store and manage patient
medical records, including diagnoses, laboratory test results, prescriptions, and treatment
plans, ensuring easy retrieval and sharing of information among authorized healthcare
providers.

3. Appointment Scheduling: Patients will be able to schedule appointments online, view

available time slots, and receive appointment reminders, while healthcare providers can
manage their schedules efficiently.

4. Billing and Finance: This module will handle billing processes, including generating
invoices, tracking payments, managing insurance claims, and maintaining financial records.

5. Inventory Management: The system will facilitate the management of medical supplies,
pharmaceuticals, and equipment, tracking stock levels, generating purchase orders, and
monitoring expiration dates.

2
6. Human Resources Management: This module will handle staff recruitment, personnel
records, payroll management, scheduling, and performance evaluation.

7. Reporting and Analytics: The system will generate comprehensive reports and
dashboards, providing valuable insights into various aspects of hospital operations, such as
patient census, resource utilization, revenue generation, and performance metrics.

While the Hospital Management System Website aims to provide a comprehensive solution,
there are certain limitations and considerations to be aware of:

1. Integration Scope: Initially, the system will focus on core functionalities and may have
limited integration capabilities with external systems. However, future enhancements will
address interoperability and integration requirements.

2. Legacy System Migration: The project does not include the migration of data from
existing legacy systems, as this will be addressed in a separate phase or initiative.

3. Regulatory Compliance: While the system will adhere to relevant healthcare regulations
and standards, such as HIPAA (Health Insurance Portability and Accountability Act), it may
require additional customizations or enhancements to address specific regional or
institutional requirements.

4. User Training: The project scope does not include extensive user training or change
management activities, which will be handled separately by the hospital's internal teams or
dedicated resources.

3
 System Analysis
2.1. Current System Analysis

The current system for managing hospital operations at [Hospital Name] primarily relies on a
combination of manual processes and disparate software applications, leading to
inefficiencies, data silos, and potential errors. This analysis aims to identify the limitations
and challenges of the existing system, which will inform the requirements for the new
Hospital Management System (HMS) Website.

Manual Processes:
- Patient registration and data entry are performed manually, often leading to errors,
duplications, and delays in accessing patient information.
- Appointment scheduling is done through paper-based systems or spreadsheets, making it
challenging to coordinate schedules and track availability.
- Medical records, including diagnoses, test results, and treatment plans, are maintained in
physical files, increasing the risk of misplacement or damage.
- Billing and invoicing processes are handled manually, resulting in potential errors and
delays in revenue collection.
- Inventory management for medical supplies and equipment is conducted using manual
stock tracking, which can lead to stock-outs or overstocking.
- Human resources processes, such as employee records, payroll, and scheduling, are
managed through various disconnected systems and manual data entry.

Disparate Software Applications:

- Multiple software applications are used across different departments, leading to data silos
and hindering efficient information sharing and collaboration.
- Lack of integration between these applications results in redundant data entry and potential
inconsistencies.
- Reporting and analytics capabilities are limited due to the fragmented nature of data
sources, making it challenging to gain comprehensive insights and make data-driven
decisions.

Challenges and Limitations:

- Inefficient processes and manual data entry increase the risk of errors and reduce
productivity.
- Difficulty in accessing up-to-date and accurate patient information, which can impact the
quality of care.
- Limited visibility into inventory levels and resource utilization, hindering effective
planning and resource allocation.
- Lack of centralized patient records and medical histories, making it challenging to provide
coordinated care across different departments or healthcare providers.
- Inability to generate comprehensive reports and analytics, hampering data-driven decision-
making and performance monitoring.
- Potential compliance risks due to challenges in maintaining data security, privacy, and
audit trails across multiple systems and manual processes.
4
2.2. Problem Statement

The current system for managing hospital operations at [Hospital Name] is plagued by
inefficiencies, data fragmentation, and manual processes that hinder the delivery of high-
quality patient care and impede operational effectiveness. The lack of a centralized and
integrated system for managing patient records, appointments, billing, inventory, and human
resources leads to suboptimal resource utilization, potential errors, and limited visibility into
performance metrics.

The primary problems encountered with the existing system include:

1. Fragmented Data and Processes: The use of disparate software applications and manual
processes across various departments results in data silos, redundant data entry, and potential
inconsistencies. This fragmentation hinders efficient information sharing, collaboration, and
decision-making.

2. Inefficient Patient Management: The manual processes involved in patient registration,

appointment scheduling, and medical record keeping are time-consuming and prone to
errors. Accessing up-to-date and accurate patient information is challenging, potentially
impacting the quality of care provided.

3. Limited Visibility and Reporting: The lack of centralized data and reporting capabilities
makes it difficult to gain comprehensive insights into hospital operations, resource
utilization, revenue generation, and performance metrics. Data-driven decision-making is
hindered due to the fragmented nature of data sources.

4. Inventory and Resource Management Challenges: Manual inventory management

practices and limited visibility into stock levels and resource utilization can lead to stock-
outs, overstocking, and inefficient resource allocation.

5. Billing and Revenue Cycle Inefficiencies: Manual billing processes, lack of integration
with insurance claims management, and potential errors in invoicing can result in delays in
revenue collection and financial leakages.

6. Human Resources Management Complexities: Disparate systems and manual processes

for managing employee records, payroll, scheduling, and performance evaluations increase
administrative overhead and reduce efficiency.

7. Compliance and Security Risks: The current system lacks robust security measures,
audit trails, and mechanisms to ensure compliance with relevant healthcare regulations and
data privacy standards, exposing the hospital to potential risks.

To address these problems and achieve operational excellence, improve patient care, and
enhance overall efficiency, the development of a comprehensive and integrated Hospital
Management System (HMS) Website is crucial.

5
2.3. Requirements Gathering and Analysis

To develop a comprehensive and effective Hospital Management System (HMS) Website, a

thorough requirements gathering and analysis process was undertaken. This process involved
stakeholder consultations, workflow analysis, and a detailed study of the current system's
limitations and challenges. The identified requirements were then classified into functional
and non-functional categories.

2.3.1. Functional Requirements

Functional requirements define the specific features and functionalities that the HMS
Website must possess to fulfill its intended purpose. The following functional requirements
have been identified:

1. Patient Management:
- Patient registration and demographic information capture
- Maintain electronic medical records (EMR) with patient history, diagnoses, and treatment
plans
- Appointment scheduling and reminders
- Integration with insurance providers for eligibility verification and claims processing

2. Medical Records Management:

- Secure storage and management of patient medical records
- Upload and access diagnostic reports, lab results, and imaging studies
- Ability to share medical records with authorized healthcare providers
- Compliance with relevant healthcare data standards and regulations (e.g., HL7, HIPAA)

3. Appointment Scheduling:
- Online appointment booking for patients
- Display of available time slots and healthcare provider schedules
- Appointment reminders and notifications
- Integration with provider calendars and resource scheduling

4. Billing and Finance:

- Generate invoices and medical bills
- Track payments and outstanding balances
- Manage insurance claims and pre-authorizations
- Integrate with payment gateways and financial systems
- Generate financial reports and statements

5. Inventory Management:
- Track and manage inventory levels of medical supplies, pharmaceuticals, and equipment
- Generate purchase orders and manage vendor relationships
- Monitor expiration dates and reorder levels
- Integrate with supply chain and logistics systems
6
6. Human Resources Management:
- Maintain employee records and personnel information
- Manage payroll and benefits administration
- Staff scheduling and shift management
- Performance evaluation and training tracking

7. Reporting and Analytics:

- Generate customizable reports and dashboards
- Analyze patient census, resource utilization, revenue generation, and operational metrics
- Identify trends and patterns for data-driven decision-making
- Export data in various formats (e.g., CSV, PDF, Excel)

8. Integration and Interoperability:

- Ability to integrate with external systems and healthcare providers
- Support for industry-standard data exchange protocols (e.g., HL7, FHIR)
- Enable data sharing and collaboration between different departments and entities

9. User Management and Access Control:

- Role-based access control and permissions management
- User authentication and authorization mechanisms
- Audit trails and activity logging

2.3.2. Non-functional Requirements

Non-functional requirements define the qualitative characteristics and constraints that the
HMS Website must adhere to, ensuring its overall quality, performance, and maintainability.
The following non-functional requirements have been identified:

1. Usability and User Experience:

- Intuitive and user-friendly interface for healthcare professionals, administrative staff, and
patients
- Responsive design for optimal viewing on various devices (desktops, laptops, tablets,
smartphones)
- Adherence to accessibility standards and guidelines

2. Performance and Scalability:

- Ability to handle high volumes of concurrent users and transactions
- Efficient data processing and retrieval mechanisms
- Scalable architecture to accommodate future growth and demand

3. Security and Privacy:

- Robust data encryption and secure communication protocols (e.g., HTTPS, SSL/TLS)
- Compliance with relevant security standards (e.g., HIPAA, GDPR)
- Mechanisms for data integrity, confidentiality, and availability

4. Availability and Reliability:

7
 - High system uptime and fault tolerance
- Backup and disaster recovery mechanisms
- Load balancing and failover capabilities

5. Maintainability and Extensibility:

- Modular and extensible codebase for future enhancements and customizations
- Adherence to coding standards and best practices
- Comprehensive documentation and version control

6. Compatibility and Interoperability:

- Support for various web browsers and versions
- Compatibility with different operating systems and devices
- Integration with third-party systems and APIs (e.g., electronic health records, laboratory
information systems)

7. Localization and Internationalization:

- Support for multiple languages and locales
- Adherence to cultural and regional preferences
- Ability to handle different date, time, and number formats

8. Compliance and Regulatory Requirements:

- Adherence to relevant healthcare regulations and standards (e.g., HIPAA, HL7, ICD)
- Auditing and logging mechanisms for compliance monitoring
- Ability to adapt to changing regulatory requirements

9. Data Migration and Conversion:

- Mechanisms for importing and converting data from legacy systems
- Data validation and integrity checks during migration
- Mapping and transformation of data to align with the new system's data structures

10. Training and Documentation:

- Comprehensive user manuals and training materials
- Online help and support resources
- Training programs for healthcare professionals and administrative staff

11. Deployment and Environment Requirements:

- Specifications for server infrastructure, operating systems, and database management
systems
- Requirements for development, testing, staging, and production environments
- Deployment scripts and automation tools

12. Monitoring and Logging:

- Mechanisms for system monitoring and performance tracking
- Logging and auditing of user activities and system events
- Integration with monitoring and logging tools

8
 System Design
3.1. System Architecture

The Hospital Management System (HMS) Website will adopt a modern and scalable
architecture to ensure efficient performance, maintainability, and extensibility. The proposed
architecture follows a multi-tier approach, separating the application into distinct layers for
better modularity and separation of concerns.

1. Presentation Layer:
- This layer will consist of the user interface components, developed using responsive web
technologies such as HTML, CSS, and JavaScript frameworks (e.g., React, Angular, or
Vue.js).
- The user interface will be designed to provide an intuitive and user-friendly experience
for healthcare professionals, administrative staff, and patients.
- Responsive design principles will be employed to ensure optimal viewing and
functionality across various devices, including desktops, laptops, tablets, and smartphones.

2. Application Layer:
- This layer will contain the business logic and application programming interfaces (APIs)
that handle the core functionalities of the HMS Website.
- The application layer will be built using a server-side programming language and
framework, such as Node.js with Express or Java with Spring Boot.
- APIs will be designed following RESTful principles, enabling seamless integration with
other systems and facilitating future extensibility.
- This layer will also handle authentication, authorization, and access control mechanisms.

3. Data Access Layer:

- This layer will manage the interaction between the application layer and the database,
abstracting the complexities of data storage and retrieval.
- Object-Relational Mapping (ORM) tools, such as Sequelize (for Node.js) or Hibernate
(for Java), will be utilized to simplify database operations and promote code reusability.
- Caching mechanisms may be implemented to improve performance and reduce database
load for frequently accessed data.

4. Database Layer:
- A relational database management system (RDBMS), such as MySQL, PostgreSQL, or
Oracle, will be employed to store and manage the hospital's data securely.
- The database will be designed following normalization principles to ensure data integrity
and minimize redundancy.
- Appropriate indexing and partitioning strategies will be implemented to optimize query
performance and handle large volumes of data efficiently.

5. Security Layer:
- This layer will encompass various security measures to protect the system and ensure
compliance with relevant regulations, such as HIPAA.
9
 - Encryption techniques (e.g., SSL/TLS) will be implemented for secure data transmission
over the network.
- Role-based access control (RBAC) and authentication mechanisms (e.g., OAuth, JWT)
will be employed to restrict unauthorized access to sensitive information.
- Audit trails and logging mechanisms will be implemented to track and monitor user
activities and system events.

6. Integration Layer:
- This layer will facilitate the integration of the HMS Website with other healthcare
systems, such as electronic health records (EHR), laboratory information systems (LIS), and
picture archiving and communication systems (PACS).
- Industry-standard protocols and data exchange formats, such as HL7 and FHIR, will be
supported to enable interoperability and data sharing with external systems.
- APIs and message queues may be utilized to enable asynchronous communication and
decouple the integration components from the core application.

The proposed architecture leverages modern technologies and follows best practices for
scalability, maintainability, and security. It promotes modular design, allowing for easier
upgrades, enhancements, and integration with future systems or technologies. Additionally,
the separation of concerns and layered approach facilitate better code organization, testing,
and deployment processes.

3.2. Database Design

The database design for the Hospital Management System (HMS) Website plays a crucial
role in ensuring data integrity, efficient data storage and retrieval, and supporting the various
functional requirements of the system. The database will be implemented using a relational
database management system (RDBMS) and will follow normalization principles to
minimize redundancy and ensure data consistency.

The proposed database schema will consist of several tables organized into logical entities,
such as patients, medical records, appointments, billing, inventory, employees, and users.
Each table will have a primary key to uniquely identify records, and foreign keys will be
used to establish relationships between tables.

1. Patient Management:
- `Patients` table: Stores patient demographic information, contact details, and unique
identifiers.
- `MedicalRecords` table: Stores patient medical histories, diagnoses, treatments, allergies,
and other relevant clinical data.
- `Appointments` table: Stores appointment details, including date, time, healthcare
provider, and patient information.

2. Billing and Finance:

10
 - `Invoices` table: Stores invoice details, including patient, services rendered, charges, and
payment status.
- `Payments` table: Stores payment records, including payment methods, amounts, and
dates.
- `InsuranceClaims` table: Stores insurance claim information, such as claim status,
provider details, and reimbursement amounts.

3. Inventory Management:
- `Inventory` table: Stores information about medical supplies, pharmaceuticals, and
equipment, including item details, stock levels, and reorder thresholds.
- `Vendors` table: Stores vendor information for procurement and supply chain
management.
- `PurchaseOrders` table: Stores purchase order details, including items ordered, quantities,
vendor information, and delivery dates.

4. Human Resources Management:

- `Employees` table: Stores employee information, including personal details, job titles,
departments, and contact information.
- `Payroll` table: Stores payroll records, including salary information, deductions, and
benefits.
- `EmployeeSchedules` table: Stores employee schedules, shift timings, and attendance
records.

5. User Management:
- `Users` table: Stores user credentials, roles, and access permissions for the HMS Website.
- `Roles` table: Stores information about different user roles and their associated
permissions.

6. Audit and Logging:

- `AuditLog` table: Stores a record of user activities, system events, and changes made to
critical data for auditing and compliance purposes.

Appropriate indexing strategies will be implemented to optimize query performance and

improve data retrieval times. Database views and stored procedures may be utilized to
simplify complex queries and enforce data integrity constraints.

The database design will also consider scalability and performance requirements,
incorporating techniques such as partitioning and sharding, if necessary, to handle large
volumes of data efficiently. Additionally, data backup and recovery strategies will be
implemented to ensure data protection and business continuity.

3.3. User Interface Design

The user interface (UI) design of the Hospital Management System (HMS) Website is a
critical aspect that directly impacts the usability and user experience for healthcare
professionals, administrative staff, and patients. The UI design will follow modern design

11
principles and best practices to ensure an intuitive, accessible, and user-friendly experience
across various devices and platforms.

1. Responsive Design:
- The HMS Website will adopt a responsive design approach, ensuring optimal viewing
and functionality across different screen sizes and devices, including desktops, laptops,
tablets, and smartphones.
- The UI will dynamically adjust and adapt to the user's device, providing a consistent and
seamless experience regardless of the viewport size.

2. User-Centered Design:
- The UI design will prioritize the needs and workflows of the target users, including
healthcare providers, administrative staff, and patients.
- Extensive user research, usability testing, and iterative design processes will be employed
to gather feedback and refine the UI based on user preferences and requirements.

3. Intuitive Navigation:
- The website's navigation structure will be designed to be intuitive and easy to navigate,
enabling users to quickly access the desired information or functionalities.
- Clear and descriptive labels, icons, and visual cues will be used to guide users through the
various sections and features of the application.

4. Accessibility:
- The UI design will adhere to accessibility standards and guidelines, such as the Web
Content Accessibility Guidelines (WCAG), to ensure that the website is usable by
individuals with disabilities.
- Considerations will be made for color contrast, font sizes, alternative text for images, and
keyboard navigation support.

5. Consistent and Clean Layout:

- The UI will follow a consistent layout and design patterns throughout the website,
promoting familiarity and reducing the cognitive load on users.
- A clean and minimalistic approach will be adopted, with appropriate use of white space,
typography, and visual hierarchy to enhance readability and focus.

6. Clear Information Hierarchy:

- Information will be organized and presented in a logical and hierarchical manner,
allowing users to quickly grasp the most important information and navigate to specific
details as needed.
- Visual cues, such as typography, color coding, and iconography, will be used to establish
a clear hierarchy and aid in information scanning and comprehension.

7. Intuitive Forms and Input Fields:

- Forms and input fields will be designed with clear labels, instructions, and validation
rules to ensure accurate data entry and minimize user errors.

12
 - Appropriate input controls, such as dropdowns, date pickers, and auto-complete fields,
will be utilized to enhance the user experience and improve data quality.

8. Feedback and Notifications:

- The UI will provide clear and timely feedback to users, including success or error
messages, progress indicators, and confirmations for critical actions.
- Notifications will be implemented to keep users informed about important events,
updates, or actions required within the system.

9. Branding and Customization:

- The UI design will incorporate the hospital's branding elements, such as logos, color
schemes, and typography, to create a cohesive and professional appearance.
- Provisions for customization options will be made to accommodate specific branding or
design requirements of different healthcare facilities.

10. Compliance and Accessibility Testing:

- Rigorous testing and evaluation processes will be conducted to ensure the UI design
complies with relevant accessibility standards, usability guidelines, and industry best
practices.
- User testing and feedback sessions will be conducted to identify and address any
usability issues or areas for improvement.

The user interface design of the HMS Website will prioritize simplicity, efficiency, and
accessibility, enabling healthcare professionals, administrative staff, and patients to interact
with the system seamlessly and effectively. Regular iterations and refinements based on user
feedback and evolving requirements will be incorporated to ensure the UI remains user-
friendly and meets the changing needs of the healthcare industry.

3.4. Security Considerations

Ensuring the security and privacy of sensitive healthcare data is of paramount importance in
the design and implementation of the Hospital Management System (HMS) Website. Robust
security measures and best practices will be incorporated throughout the system to protect
against potential threats, maintain data integrity, and comply with relevant regulations and
standards, such as HIPAA (Health Insurance Portability and Accountability Act).

1. Authentication and Authorization:

- Strong authentication mechanisms, such as multi-factor authentication (MFA) or
biometric authentication, will be implemented to ensure only authorized users can access the
system.
- Role-based access control (RBAC) will be employed to restrict access to sensitive
information and functionalities based on user roles and permissions.
- Session management techniques, such as secure session handling and session timeouts,
will be implemented to mitigate the risk of session hijacking or unauthorized access.

13
2. Data Encryption:
- All sensitive data, including patient medical records, financial information, and user
credentials, will be encrypted at rest and in transit using industry-standard encryption
algorithms (e.g., AES-256) and secure protocols (e.g., SSL/TLS).
- Encryption keys will be securely managed and rotated regularly to enhance data
protection.

3. Secure Communication:
- All communication between the client (web browser) and the server will be encrypted
using secure protocols, such as HTTPS, to prevent eavesdropping and man-in-the-middle
attacks.
- Secure communication channels will also be established for integrations with external
systems and third-party APIs.

4. Input Validation and Sanitization:

- Robust input validation and sanitization techniques will be implemented to prevent
various types of attacks, such as SQL injection, cross-site scripting (XSS), and other code
injection vulnerabilities.
- Input data will be validated and sanitized on both the client-side (using JavaScript) and
server-side (using server-side programming languages) to enhance security.

5. Audit Trails and Logging:

- Comprehensive audit trails and logging mechanisms will be implemented to track and
monitor user activities, system events, and changes made to critical data.
- Log files will be securely stored and regularly reviewed for potential security incidents or
unauthorized access attempts.

6. Secure Software Development Practices:

- Industry-standard secure coding practices, such as the OWASP (Open Web Application
Security Project) guidelines, will be followed during the development process.
- Regular security testing, including penetration testing and vulnerability assessments, will
be conducted to identify and address potential security weaknesses.

7. Secure Infrastructure and Hosting:

- The HMS Website will be hosted on secure and hardened servers, with regular patching
and updates to address security vulnerabilities.
- Firewalls, intrusion detection/prevention systems (IDS/IPS), and other security
appliances will be implemented to protect the infrastructure from external threats.

8. Security Awareness and Training:

- Comprehensive security awareness and training programs will be developed and
implemented for all users, including healthcare professionals, administrative staff, and
system administrators.
- Regular updates and reinforcement of security best practices will be provided to maintain
a strong security culture within the organization.

14
 Implementation
4.1. Development Environment

Establishing a robust and efficient development environment is crucial for the successful
implementation of the Hospital Management System (HMS) Website. The development
environment will include a set of tools, frameworks, and technologies that facilitate
collaboration, version control, and streamlined development processes.

1. Integrated Development Environment (IDE):

- The development team will utilize modern IDEs, such as Visual Studio Code, IntelliJ
IDEA, or WebStorm, which provide powerful code editing capabilities, debugging tools, and
integrated version control support.

2. Version Control System:

- The project will leverage a distributed version control system (DVCS) like Git to manage
the codebase, track changes, facilitate collaboration among developers, and enable easy code
merging and branching.
- A code repository hosting service, such as GitHub, GitLab, or Bitbucket, will be used to
store the project's codebase and facilitate code reviews, issue tracking, and project
management.

3. Continuous Integration and Continuous Deployment (CI/CD):

- A CI/CD pipeline will be established using tools like Jenkins, Travis CI, or CircleCI to
automate the build, testing, and deployment processes.
- This pipeline will ensure that code changes are regularly built, tested, and deployed to
different environments (e.g., development, staging, production), streamlining the release
cycle and reducing manual effort.

4. Development Environments:
- Separate development, testing, and staging environments will be set up to mimic the
production environment as closely as possible, enabling thorough testing and validation
before deploying changes to the live system.
- Containerization technologies, such as Docker and Kubernetes, may be utilized to ensure
consistent and reproducible environments across different stages of the development
lifecycle.

5. Issue Tracking and Project Management:

- Issue tracking and project management tools, such as Jira, Trello, or GitHub Issues, will
be employed to organize and prioritize tasks, track bugs and feature requests, and manage
project workflows and timelines.

15
4.2. Front-end Development

The front-end development of the HMS Website will focus on creating a responsive, user-
friendly, and accessible web interface for healthcare professionals, administrative staff, and
patients. The following technologies and frameworks will be utilized:

1. HTML, CSS, and JavaScript:

- The front-end will be built using modern web standards, including HTML5 for
structuring content, CSS3 for styling and layout, and JavaScript for adding interactivity and
dynamic behavior.

2. Responsive Web Design:

- Responsive web design principles will be employed to ensure optimal viewing and
functionality across various devices, including desktops, laptops, tablets, and smartphones.
- CSS frameworks like Bootstrap or Bulma, combined with media queries and fluid grid
layouts, will be utilized to achieve a responsive and adaptive user interface.

3. Front-end Framework:
- A modern front-end framework, such as React, Angular, or Vue.js, will be adopted to
facilitate the development of reusable and modular user interface components.
- These frameworks provide features like component-based architecture, state
management, and efficient rendering, enabling the creation of highly interactive and
performant web applications.

4. UI Component Library:
- A popular UI component library, such as Material-UI (for React), Angular Material, or
Vue Material, will be integrated to provide pre-built and stylized UI components, ensuring a
consistent and visually appealing user experience throughout the application.

5. Form Handling and Validation:

- Libraries and frameworks like React Hook Form, Formik, or Angular Reactive Forms
will be utilized to simplify form handling, validation, and submission processes, ensuring
data integrity and providing a seamless user experience.

6. State Management:
- Efficient state management solutions, such as Redux (for React), NgRx (for Angular), or
Vuex (for Vue.js), will be implemented to manage the application's state, enabling better
control over data flow and facilitating communication between components.

7. Routing and Navigation:

- Client-side routing libraries, like React Router, Angular Router, or Vue Router, will be
employed to enable seamless navigation within the application, providing a smooth and
efficient user experience.

16
8. Accessibility:
- Accessibility best practices and guidelines, such as WCAG (Web Content Accessibility
Guidelines), will be followed during front-end development to ensure the application is
usable by individuals with disabilities.

9. Performance Optimization:
- Techniques like code splitting, lazy loading, and optimizing asset delivery will be
implemented to enhance the application's performance, reducing load times and improving
the overall user experience.

10. Testing and Quality Assurance:

- Unit tests and end-to-end (E2E) tests will be written using frameworks like Jest, Enzyme
(for React), Karma and Jasmine (for Angular), or Vue Test Utils (for Vue.js) to ensure the
quality and reliability of the front-end codebase.

The front-end development process will prioritize user experience, responsiveness,

accessibility, and performance, ensuring that the HMS Website provides a seamless and
intuitive interface for all users.

4.3. Back-end Development

The back-end development of the HMS Website will focus on building a robust and scalable
server-side application to handle core functionalities, data processing, and integration with
other systems. The following technologies and frameworks will be utilized:

1. Server-side Programming Language and Framework:

- A modern server-side programming language, such as Node.js (with Express.js) or Java
(with Spring Boot), will be chosen to develop the back-end application.
- These frameworks provide features like routing, middleware, and dependency injection,
facilitating the development of RESTful APIs and handling server-side logic efficiently.

2. API Development:
- RESTful APIs will be designed and implemented following industry best practices and
guidelines, such as the Richardson Maturity Model or the Microsoft REST API Guidelines.
- APIs will be documented using tools like Swagger or API Blueprint, ensuring clear
communication and ease of integration with other systems.

3. Authentication and Authorization:

- Secure authentication and authorization mechanisms, such as JSON Web Tokens (JWT)
or OAuth 2.0, will be implemented to protect sensitive data and ensure appropriate access
control.
- Role-based access control (RBAC) will be employed to manage user permissions and
restrict access to specific functionalities based on user roles.

17
4. Data Access Layer:
- An Object-Relational Mapping (ORM) tool, such as Sequelize (for Node.js) or Hibernate
(for Java), will be utilized to abstract the database interactions and simplify data access
operations.
- Repository patterns or data access objects (DAOs) will be implemented to encapsulate
data access logic and promote code reusability.

5. Caching:
- Caching mechanisms, such as Redis or Memcached, will be employed to improve
performance and reduce database load for frequently accessed data.

6. Logging and Monitoring:

- Robust logging and monitoring solutions, like Winston (for Node.js) or Logback (for
Java), will be implemented to track application events, errors, and performance metrics,
enabling effective troubleshooting and maintenance.

7. Background Jobs and Messaging:

- Asynchronous processing and messaging queues, like Bull (for Node.js) or RabbitMQ
(for Java), will be utilized to handle long-running tasks, such as report generation or batch
processing, ensuring responsiveness and scalability.

8. Integration and Interoperability:

- Support for industry-standard protocols and data exchange formats, such as HL7 and
FHIR, will be implemented to enable integration with external healthcare systems, like
electronic health records (EHR) or laboratory information systems (LIS).

9. Security:
- Security best practices, including input validation, sanitization, and encryption of
sensitive data, will be implemented to protect the application from potential threats and
vulnerabilities.
- Regular security audits and penetration testing will be conducted to identify and mitigate
security risks.

10. Testing and Quality Assurance:

- Unit tests, integration tests, and end-to-end (E2E) tests will be written using frameworks
like Jest, Mocha, or JUnit, ensuring the quality and reliability of the back-end codebase.
- Continuous Integration (CI) pipelines will be set up to automatically run tests and code
quality checks with every code change, catching issues early in the development cycle.

The back-end development process will prioritize scalability, security, and adherence to
industry standards and best practices, ensuring that the HMS Website's server-side
application is robust, efficient, and capable of seamlessly integrating with other healthcare
systems.

4.4. Database Implementation

18
The database implementation is a critical component of the HMS Website, as it serves as the
central repository for storing and managing various types of data, including patient records,
appointments, billing information, inventory data, and user authentication details. The
following steps will be taken to ensure a secure and efficient database implementation:

1. Database Management System (DBMS) Selection:

- A robust and scalable relational database management system (RDBMS), such as
MySQL, PostgreSQL, or Oracle, will be selected based on the project's requirements,
performance needs, and compatibility with the chosen back-end technologies.

2. Database Schema Design:

- The database schema will be designed following normalization principles to ensure data
integrity, minimize redundancy, and optimize query performance.
- The schema will consist of multiple tables organized into logical entities, such as patients,
medical records, appointments, billing, inventory, employees, and user authentication.
- Appropriate data types, constraints, and indexes will be defined to enforce data
consistency and improve query performance.

3. Data Modeling and Relationships:

- Entity-relationship diagrams (ERDs) will be created to visualize the relationships
between different entities and tables, facilitating a better understanding of the data model.
- Appropriate relationships, such as one-to-one, one-to-many, or many-to-many, will be
established between tables using primary and foreign key constraints.

4. Database Optimization:
- Database optimization techniques, such as indexing, partitioning, and query tuning, will
be employed to ensure efficient data retrieval and storage operations, especially for large
data volumes.
- Database performance monitoring tools will be utilized to identify and address potential
bottlenecks or inefficiencies.

5. Data Security and Encryption:

- Sensitive data, such as patient medical records and financial information, will be
encrypted at rest using industry-standard encryption algorithms (e.g., AES-256) to protect
against unauthorized access or data breaches.
- Role-based access control (RBAC) mechanisms will be implemented to restrict database
access based on user roles and permissions.

6. Data Backup and Recovery:

- Robust data backup and recovery strategies will be implemented to ensure data protection
and business continuity in case of system failures, disasters, or security incidents.
- Backup schedules and procedures will be established, and regular testing of recovery
processes will be conducted to validate their effectiveness.

7. Database Migrations and Version Control:

19
 - Database migration scripts and version control mechanisms will be employed to manage
schema changes and facilitate easy deployment of database updates across different
environments (e.g., development, staging, production).
- Tools like Liquibase, Flyway, or Alembic will be utilized for database migration
management and version control.

8. Integration with Back-end Application:

- The database implementation will be seamlessly integrated with the back-end application
through the use of an Object-Relational Mapping (ORM) tool or a data access layer,
abstracting the complexities of database interactions and promoting code reusability.

9. Database Monitoring and Logging:

- Comprehensive database monitoring and logging mechanisms will be implemented to
track database performance, query execution times, and potential issues or errors, enabling
proactive maintenance and troubleshooting.

10. Compliance and Regulatory Requirements:

- The database implementation will adhere to relevant healthcare regulations and
standards, such as HIPAA (Health Insurance Portability and Accountability Act), ensuring
the protection of sensitive patient data and compliance with data privacy and security
requirements.

By following these steps, the database implementation will be secure, efficient, and scalable,
providing a reliable foundation for storing and managing critical healthcare data within the
HMS Website.

4.5. Integration and Testing

Integrating various components and ensuring the overall quality and reliability of the HMS
Website are crucial aspects of the implementation process. The following steps will be taken
to facilitate integration and thorough testing:

1. Integration Testing:
- Integration testing will be conducted to verify the correct interaction and data flow
between different modules and components of the HMS Website, such as the front-end,
back-end, and database.
- Test cases will be designed to validate scenarios involving multiple components, ensuring
they work together as expected and handle edge cases correctly.

2. API Testing:
- Comprehensive testing of the RESTful APIs will be performed to ensure their
functionality, reliability, and adherence to specified requirements.
- Tools like Postman, Insomnia, or Swagger will be utilized to test API endpoints, validate
responses, and verify authentication and authorization mechanisms.

3. End-to-End (E2E) Testing:

20
 - E2E tests will be written to simulate real-world user scenarios and validate the
application's behavior from start to finish, ensuring a seamless and consistent experience.
- Testing frameworks like Selenium, Cypress, or Puppeteer will be employed to automate
E2E tests across different browsers and environments.

4. Performance Testing:
- Performance testing will be conducted to assess the HMS Website's ability to handle
varying loads and identify potential bottlenecks or performance issues.
- Tools like JMeter, Gatling, or LoadRunner will be utilized to simulate concurrent user
traffic and measure response times, throughput, and resource utilization.

5. Security Testing:
- Security testing, including penetration testing and vulnerability assessments, will be
performed to identify and mitigate potential security risks and vulnerabilities.

6. Usability Testing:
- Usability testing will be conducted with representative users (e.g., healthcare
professionals, administrative staff, patients) to gather feedback on the user interface,
navigation, and overall user experience.
- Insights from usability testing will be incorporated to refine the application and enhance
its usability and accessibility.

7. Compliance Testing:
- Compliance testing will be performed to ensure that the HMS Website adheres to relevant
healthcare regulations and standards, such as HIPAA, HL7, and data privacy guidelines.
- Automated testing tools and manual audits will be employed to validate compliance
requirements and identify any potential violations or non-conformities.

8. Test Automation and Continuous Integration:

- Automated testing frameworks and Continuous Integration (CI) pipelines will be
established to enable frequent and reliable testing throughout the development lifecycle.

9. Test Data Management:

- Appropriate test data management strategies will be implemented to ensure the
availability of realistic and representative test data for various testing scenarios.
- Test data generation tools or anonymized production data may be utilized, ensuring
compliance with data privacy regulations and protecting sensitive patient information.

10. Defect Tracking and Resolution:

- A defect tracking system, such as Jira or Bugzilla, will be employed to log, prioritize,
and manage the resolution of identified defects or issues during the testing process.

System Modules
5.1. Patient Management
21
The Patient Management module is a crucial component of the HMS Website, serving as the
foundation for managing patient information and interactions within the healthcare facility.
This module streamlines the processes related to patient registration, profile management,
appointment handling, and communication, ensuring efficient and coordinated patient care.

Patient Registration
The patient registration process is the first step in establishing a comprehensive patient
record within the HMS. Healthcare professionals can easily register new patients by
capturing essential demographic and contact information, such as name, date of birth,
address, phone number, and emergency contacts. The system automatically assigns a unique
patient identifier to each new record, facilitating easy identification and retrieval of patient
data throughout the healthcare facility.

Patient Profile
The HMS Website maintains a comprehensive patient profile for each registered individual.
This profile serves as a centralized repository for storing and managing a wide range of
patient-related information, including:

1. Personal Details: In addition to demographic and contact information, the patient profile
may include details such as gender, marital status, and preferred language, ensuring
personalized care and effective communication.

2. Medical History: A detailed medical history is captured and maintained within the patient
profile, including information about past and current medical conditions, allergies, surgeries,
hospitalizations, and any relevant family medical history.

3. Insurance Information: Details about the patient's insurance coverage, including

insurance provider, policy numbers, and coverage details, are stored within the patient
profile. This information is crucial for streamlining billing and claims processes.

4. Emergency Contacts: The patient profile allows healthcare professionals to record

emergency contact information, such as the names, relationships, and contact details of
individuals authorized to make decisions or be notified in case of an emergency.

5. Documents and Attachments: The patient profile provides a secure repository for storing
and accessing patient-related documents, such as consent forms, identification documents,
insurance cards, or medical reports. This feature ensures that critical information is readily
available when needed.

Search and Filtering

The Patient Management module incorporates powerful search and filtering capabilities,
enabling healthcare professionals to quickly locate and retrieve patient records based on
various criteria. Users can search for patients by name, patient ID, date of birth, or any other
relevant information, streamlining the process of accessing patient data.

22
Additionally, advanced filtering options allow users to narrow down search results based on
specific criteria, such as medical conditions, allergies, or insurance providers. This feature is
particularly useful in identifying patient groups for targeted outreach, follow-up care, or
clinical studies.

Appointment Management
The Patient Management module seamlessly integrates with the Appointment Scheduling
module, providing healthcare professionals with a comprehensive view of each patient's
upcoming appointments. Within the patient profile, users can access a calendar view or a list
of scheduled appointments, including details such as date, time, provider, and appointment
type.

This integration enables healthcare professionals to efficiently manage patient appointments,

reschedule or cancel appointments as needed, and ensure that patient records are readily
available during each visit, improving the overall quality of care and patient experience.

Document Management
The HMS Website offers a robust document management system within the Patient
Management module, enabling healthcare professionals to securely store and manage
patient-related documents. This feature allows users to upload various file formats, including
PDFs, images, and scanned documents, and associate them with the corresponding patient
record.

Document management capabilities include version control, access controls, and audit trails,
ensuring that only authorized personnel can access and modify patient documents.
Additionally, the system may provide functionalities for annotating, redacting, or digitally
signing documents, further enhancing the security and integrity of patient information.

Communication
Effective communication with patients is essential for providing high-quality care and
ensuring patient satisfaction. The Patient Management module includes tools for sending
appointment reminders, follow-up messages, and notifications to patients via various
communication channels, such as email, SMS, or secure messaging platforms.

Healthcare professionals can customize the content and timing of these communications,
ensuring that patients receive timely and relevant information. This feature helps reduce no-
show rates, improves appointment adherence, and keeps patients informed about their
healthcare journey.

5.2. Medical Records Management

The Medical Records Management module is a critical component of the HMS Website,
responsible for securely storing, managing, and accessing patient medical records. This
module ensures accurate and comprehensive documentation of healthcare services, enables
seamless information sharing among healthcare providers, and promotes data-driven
decision-making for improved patient outcomes.

23
Electronic Medical Records (EMR)
At the heart of the Medical Records Management module lies the Electronic Medical Record
(EMR) system. EMRs serve as comprehensive digital repositories for storing and managing
patient medical histories, diagnoses, treatments, medications, allergies, and test results.

The EMR system within the HMS Website is designed to capture and organize patient
medical information in a structured and easily accessible format. Healthcare professionals
can create, update, and review EMRs for each patient, ensuring that accurate and up-to-date
information is available at all times.

Key components of the EMR system include:

1. Patient Summary: A high-level overview of the patient's medical history, current

conditions, medications, and allergies, providing a quick reference for healthcare providers.

2. Clinical Notes: Detailed documentation of patient encounters, including subjective and

objective findings, assessments, and treatment plans, recorded using standardized formats
such as SOAP (Subjective, Objective, Assessment, Plan) notes.

3. Medication List: A comprehensive list of prescribed medications, including dosages,

frequencies, and instructions, ensuring accurate medication management and reducing the
risk of adverse drug interactions.

4. Allergy and Intolerance Records: Detailed records of patient allergies and intolerances,
including the type of reaction and severity, to inform treatment decisions and prevent
potential adverse reactions.

5. Immunization Records: Documentation of administered vaccinations, including dates,

vaccine types, and lot numbers, ensuring accurate tracking and compliance with
immunization schedules.

6. Lab and Diagnostic Results: Integration with laboratory information systems and
diagnostic imaging systems, enabling secure storage and retrieval of test results, such as
blood work, microbiology reports, and radiology images.

SOAP Notes
The Medical Records Management module provides a dedicated feature for creating and
maintaining SOAP (Subjective, Objective, Assessment, Plan) notes. SOAP notes are a
standardized format used by healthcare professionals to document patient encounters,
ensuring consistent and comprehensive documentation of medical information.

Within the HMS Website, healthcare providers can easily create SOAP notes by entering
relevant information in each section:

1. Subjective: Details about the patient's chief complaint, symptoms, and medical history, as
reported by the patient.

24
2. Objective: Objective findings from physical examinations, vital signs, and diagnostic test
results.

3. Assessment: The healthcare provider's evaluation and diagnosis based on the subjective
and objective information.

4. Plan: The proposed treatment plan, including medications, procedures, follow-up

appointments, and patient education.

Medication Management
The Medical Records Management module includes a robust medication management
feature, enabling healthcare professionals to accurately track and manage prescribed
medications for each patient. This feature ensures medication safety, reduces the risk of
adverse drug interactions, and promotes medication adherence.

Key capabilities of the medication management feature include:

1. Prescription Management: Healthcare providers can electronically prescribe

medications, including dosages, frequencies, and instructions, directly within the patient's
EMR.

2. Medication List: A comprehensive list of prescribed medications is maintained within the

patient's EMR, providing a clear overview of current and past medications.

3. Medication Reconciliation: During patient encounters, healthcare providers can review

and reconcile the patient's medication list, ensuring accuracy and identifying potential
discrepancies or contraindications.

4. Refill Reminders: Automated reminders can be sent to patients when medication refills
are due, promoting medication adherence and improving treatment outcomes.

5. Drug Interaction Checks: The system can perform automated checks for potential drug
interactions, allergies, or contraindications based on the patient's medical history and current
medication list, alerting healthcare providers to potential risks.

6. E-Prescribing: Integration with e-prescribing systems and pharmacies, enabling

electronic transmission of prescriptions and streamlining the medication fulfillment process.

Laboratory and Diagnostic Results

The Medical Records Management module seamlessly integrates with laboratory
information systems (LIS) and picture archiving and communication systems (PACS) to
enable secure storage, retrieval, and visualization of laboratory test results and diagnostic
imaging studies.

Healthcare professionals can access and review test results, such as blood work,
microbiology reports, and radiology images, directly within the patient's EMR. This
25
integration eliminates the need for manual data entry, reduces the risk of transcription errors,
and ensures that healthcare providers have access to the most up-to-date and accurate
diagnostic information.

The system also supports advanced visualization and manipulation tools for diagnostic
imaging studies, allowing healthcare professionals to zoom, pan, and annotate images as
needed, facilitating accurate interpretation and diagnosis.

Access Controls and Audit Trails

Ensuring the security and integrity of medical records is of paramount importance in the
Medical Records Management module. Robust access controls and auditing mechanisms are
implemented to safeguard sensitive patient information while maintaining regulatory
compliance.

Role-based access controls (RBAC) are employed, allowing healthcare facilities to define
user roles and permissions based on their responsibilities and the level of access required.
This approach ensures that only authorized personnel can access, modify, or delete medical
records, enhancing data security and privacy.

Furthermore, comprehensive audit trails are maintained, recording all actions performed
within the Medical Records Management module. These audit trails provide detailed
information about the user, date, time, and the specific actions taken, such as creating,
modifying, or accessing patient records. This level of auditing not only supports data
integrity but also facilititated regulatory compliance and enables investigations in case of
potential data breaches or unauthorized access attempts.

5.3. Appointment Scheduling

The Appointment Scheduling module is a vital component of the HMS Website,
streamlining the process of scheduling and managing appointments for patients. This module
ensures efficient resource allocation, improves patient flow, and enhances the overall
experience for both patients and healthcare providers.

Online Appointment Booking

The HMS Website provides a user-friendly interface for patients to conveniently book
appointments online. Patients can access the online appointment booking system through the
website or a dedicated patient portal, where they can view available time slots based on their
preferred healthcare provider, location, or service.

The online booking process is designed to be intuitive and straightforward, guiding patients
through the steps of selecting the appropriate service, providing necessary information (such
as reason for the visit or insurance details), and confirming the appointment details.

Provider Scheduling and Resource Allocation

The Appointment Scheduling module offers a comprehensive solution for managing
healthcare provider schedules and allocating resources effectively. Healthcare providers can
26
access a centralized calendar view, allowing them to monitor their upcoming appointments,
block time for various activities, and manage their availability.

Furthermore, the module integrates with the facility's resource management system, ensuring
efficient allocation of examination rooms, diagnostic equipment, and other resources based
on the scheduled appointments. This integration optimizes resource utilization, minimizing
redundancy and improving patient flow within the healthcare facility.

Appointment Management
The Appointment Scheduling module provides a robust platform for healthcare professionals
to efficiently manage and coordinate appointments. Key features include:

1. Appointment Reminders: Automated reminders can be sent to patients via email, SMS,
or voice messages, reducing the likelihood of missed appointments and improving
appointment adherence.

2. Waitlist Management: The system maintains a waitlist for patients who cannot secure
their preferred appointment times, allowing healthcare providers to fill cancellations or no-
shows promptly.

3. Appointment Rescheduling: Patients or healthcare providers can reschedule

appointments with ease, ensuring minimal disruption to schedules and maximizing resource
utilization.

4. Appointment Analytics: Comprehensive reports and analytics are available, providing

insights into appointment volumes, patient flows, and resource utilization, enabling data-
driven decision-making and process optimization.

5.4. Billing and Finance

The Billing and Finance module streamlines financial processes within the healthcare
facility, ensuring accurate invoicing, efficient payment processing, and effective claims
management. This module plays a crucial role in revenue capture, minimizing leakages, and
promoting financial transparency.

Patient Invoicing and Payment Processing

The Billing and Finance module provides a comprehensive platform for generating accurate
patient invoices, reflecting the services rendered, procedures performed, and associated
charges. Healthcare professionals can seamlessly create invoices directly within the system,
leveraging the integration with the Medical Records Management module to capture relevant
patient information and treatment details.

The invoicing process is streamlined through the use of templates, which can be customized
to align with the healthcare facility's branding and formatting preferences. These templates
ensure consistency in invoice presentation and improve the overall professional appearance.

To enhance the patient experience, the HMS Website offers a secure online patient portal,
where patients can access their invoices, view itemized charges, and make convenient online
27
payments. The online payment functionality is designed to be user-friendly, accepting
various payment methods, including credit/debit cards, mobile wallets, and bank transfers.

The Billing and Finance module integrates with robust payment processing capabilities,
ensuring secure and efficient handling of financial transactions. This integration involves the
implementation of industry-standard payment security measures, such as tokenization and
encryption, to protect sensitive financial data and comply with relevant regulations, such as
the Payment Card Industry Data Security Standard (PCI-DSS).

Insurance Claims Management

The Billing and Finance module seamlessly integrates with insurance providers through the
Insurance Claims Management feature. This feature enables healthcare professionals to
streamline the process of submitting insurance claims, facilitating efficient reimbursement
and minimizing delays or denials.

The Insurance Claims Management feature allows healthcare providers to capture and
transmit all necessary information to insurance providers, ensuring accurate and timely
claims processing. This information may include patient demographics, insurance policy
details, diagnoses codes, procedure codes, and medical records documentation.

By integrating with insurance providers' systems, the module can track claim statuses,
monitor reimbursements, and identify potential issues or denials. This integration facilitates
prompt resolution of any discrepancies, minimizing financial leakages and ensuring proper
reimbursement for services rendered.

Revenue Cycle Management

The Billing and Finance module incorporates robust revenue cycle management capabilities,
enabling healthcare facilities to streamline financial processes from patient registration to
final payment. Effective revenue cycle management is crucial for maximizing revenue
capture, minimizing leakages, and ensuring financial sustainability.

The revenue cycle management features within the HMS Website include:

1. Patient Registration and Eligibility Verification: Streamlining the patient registration

process by capturing all necessary demographic and insurance information, enabling
eligibility verification with insurance providers.

2. Medical Coding and Charge Capture: Leveraging advanced medical coding capabilities
to accurately capture charges based on the services rendered, diagnoses, and procedures
performed.

3. Claims Management and Follow-up: Comprehensive tools for managing insurance

claims, including follow-up processes to address denials or underpayments and maximize
reimbursement.

4. Denial Management and Appeals: Mechanisms to track and manage denied claims,
initiate appeals processes, and resolve discrepancies to optimize revenue capture.
28
5. Reporting and Analytics: Detailed financial reporting and analytics capabilities,
providing insights into revenue generation, accounts receivable, aging reports, and other key
performance indicators for data-driven decision-making.

Compliance and Regulatory Standards

The HMS Website is designed to adhere to relevant compliance and regulatory standards,
ensuring the highest level of data security, privacy, and patient confidentiality. Key
compliance features include:

- Access Controls and Audit Trails: Robust access controls and audit trails are
implemented to ensure appropriate user access to patient records and maintain detailed logs
of all actions performed within the system.

- Data Encryption and Security: Industry-standard encryption protocols are employed to

secure patient data at rest and in transit, safeguarding sensitive information from
unauthorized access.

- Regulatory Compliance Reporting: Comprehensive reporting capabilities are available to

demonstrate compliance with regulations such as the Health Insurance Portability and
Accountability Act (HIPAA), enabling healthcare facilities to meet auditing and reporting
requirements.

- Disaster Recovery and Business Continuity: The HMS Website incorporates robust
disaster recovery and business continuity measures, ensuring the availability of critical
patient data and minimizing downtime in the event of system failures or disruptions.

By prioritizing compliance and adhering to stringent regulatory standards, the HMS Website
provides healthcare facilities with the assurance of secure and reliable operations while
maintaining the highest level of patient confidentiality and data integrity.

Use Case Diagram

29
UML Diagrams

30
1. Hospital organization

2. Hospital wards and teams

31
3. Hospital Treatment

32
DFD of Hospital System Website
33
Data flow diagram Hospital Management System is used to create an overview of Hospital
management without going in too much detail. The overall Hospital Management System is
represented and described using input, processing and output in DFD. The DFD diagram for
Hospital Management System provides information about the inputs and outputs of each
process and entity of hospital such as patient, staff, doctor, room and medical treatment.

Following are hospital management system DFD level 0, 1, 2. You can have these levels at
the end of this discussion. Let us explain each one by one.

Context Level (Zero Level) DFD

The Zero Level DFD for hospital management system depicts the overview of whole
hospital management system. It is supposed to be an abstract view of overall system. This is
also called as context diagram for hospital management system in which entire system is
represented as single process with its relationship with external entities such as admin, staff,
doctor etc.

Level 1 DFD

The first level DFD (1st Level) of Hospital management system shows more details of
processing. Level 1 DFD list all the major sub processes that makes the entire system. It also
identifies data store of hospital master data that contains all records of patient, doctor, staff,
room, treatment etc. that will be used to during different other process like patient
registration and patient discharge.

34
The important process to be carried out are:
1. User & login
2. Hospital master
3. Patient registration
4. Doctor module
5. Add patient service
6. Discharge billing
The level 1 DFD for hospital management system provides a broad overview but go into
greater depth than context level diagram.

Level 2 DFD

The Second level (2nd level) DFD of hospital management system represents how the
system is divided into sub systems and the second level provides more details about: patient
registration, medical treatment, patient service record and billing process.

35
Following are some functionality of hospital management system

1. Admin can add, edit and delete hospital master records such as ward, room, medicine etc.
2. Admin can add, edit and delete doctor record
3. Admin can add, edit and delete staff record
4. Admin can add, edit and delete various treatment details
5. Patient details can be added, edit and delete
6. Room allocation can be done
7. Prepare discharge bill

After viewing this level now you will be more clear about where data input goes and from
where output data comes. This Level 2 Data Flow Diagram shows you a detailed process of
hospital management system and also give you a clear view about data that flows into the
system.

36
 ER Diagram for Hospital System Website
Entity:-
Entity is the thing which we want to store information. It is an elementary basic building
block of storing information about business process. An entity represents an objects defined
within the information system about which you want to store information.

Relationship:-
A relationships named connection or association between entities used to relate two or more
entities with some common attributes of meaningful interaction between the object.

Attributes:-
Attributes are the properties of the entities and relationship. Descriptor of the entity.
Attributes are elementary pieces of and information attached to an entity.

37
38
System Design of Database

39
 Code for Website
Home Page
<!DOCTYPE html>
<html>

<head>
<title>Mico</title>
<!-- bootstrap core css -->
<link rel="stylesheet" type="text/css" href="css/bootstrap.css" />

<!-- fonts style -->

<link href="https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700;900&display=swap" rel="stylesheet">
<!-- nice select -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/jquery-nice-select/1.1.0/css/nice-select.min.css"integrity="sha256-
mLBIhmBvigTFWPSCtvdu6a76T+3Xyt+K571hupeFLg4=" crossorigin="anonymous" />
<!-- Custom styles for this template -->
<link href="css/style.css" rel="stylesheet" />
</head>

<body>

<div class="hero_area">
<!-- header section strats -->
<header class="header_section">
<div class="header_top">
<div class="container">
<div class="contact_nav">
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call : +01 123455678990
</span>
</a>
<a href="">
<i class="fa fa-envelope" aria-hidden="true"></i>
<span>
Email : [email protected]
</span>
</a>
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
</div>
</div>
</div>
<div class="header_bottom">
<div class="container-fluid">
<nav class="navbar navbar-expand-lg custom_nav-container ">
<a class="navbar-brand" href="index.html">
<img src="images/logo.png" alt="">
</a>

<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-

controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class=""> </span>
</button>

<div class="collapse navbar-collapse" id="navbarSupportedContent">

<div class="d-flex mr-auto flex-column flex-lg-row align-items-center">
<ul class="navbar-nav ">
<li class="nav-item active">
<a class="nav-link" href="index.html">Home <span class="sr-only">(current)</span></a>
</li>
<li class="nav-item">
<a class="nav-link" href="about.html"> About</a>
40
 </li>
<li class="nav-item">
<a class="nav-link" href="treatment.html">Treatment</a>
</li>
<li class="nav-item">
<a class="nav-link" href="doctor.html">Doctors</a>
</li>
<li class="nav-item">
<a class="nav-link" href="testimonial.html">Testimonial</a>
</li>
<li class="nav-item">
<a class="nav-link" href="contact.html">Contact Us</a>
</li>
</ul>
</div>
<div class="quote_btn-container">
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Login
</span>
</a>
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Sign Up
</span>
</a>
<form class="form-inline">
<button class="btn my-2 my-sm-0 nav_search-btn" type="submit">
<i class="fa fa-search" aria-hidden="true"></i>
</button>
</form>
</div>
</div>
</nav>
</div>
</div>
</header>
<!-- end header section -->
<!-- slider section -->
<section class="slider_section ">
<div class="dot_design">
<img src="images/dots.png" alt="">
</div>
<div id="customCarousel1" class="carousel slide" data-ride="carousel">
<div class="carousel-inner">
<div class="carousel-item active">
<div class="container ">
<div class="row">
<div class="col-md-6">
<div class="detail-box">
<div class="play_btn">
<button>
<i class="fa fa-play" aria-hidden="true"></i>
</button>
</div>
<h1>
Mico <br>
<span>
Hospital
</span>
</h1>
<p>
when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to
</p>
<a href="">
Contact Us
</a>
</div>
</div>
<div class="col-md-6">
<div class="img-box">
41
 <img src="images/slider-img.jpg" alt="">
</div>
</div>
</div>
</div>
</div>
<div class="carousel-item">
<div class="container ">
<div class="row">
<div class="col-md-6">
<div class="detail-box">
<div class="play_btn">
<button>
<i class="fa fa-play" aria-hidden="true"></i>
</button>
</div>
<h1>
Mico <br>
<span>
Hospital
</span>
</h1>
<p>
when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to
</p>
<a href="">
Contact Us
</a>
</div>
</div>
<div class="col-md-6">
<div class="img-box">
<img src="images/slider-img.jpg" alt="">
</div>
</div>
</div>
</div>
</div>
<div class="carousel-item">
<div class="container ">
<div class="row">
<div class="col-md-6">
<div class="detail-box">
<div class="play_btn">
<button>
<i class="fa fa-play" aria-hidden="true"></i>
</button>
</div>
<h1>
Mico <br>
<span>
Hospital
</span>
</h1>
<p>
when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to
</p>
<a href="">
Contact Us
</a>
</div>
</div>
<div class="col-md-6">
<div class="img-box">
<img src="images/slider-img.jpg" alt="">
</div>
</div>
</div>
</div>
</div>
</div>
<div class="carousel_btn-box">
<a class="carousel-control-prev" href="#customCarousel1" role="button" data-slide="prev">
42
 <img src="images/prev.png" alt="">
<span class="sr-only">Previous</span>
</a>
<a class="carousel-control-next" href="#customCarousel1" role="button" data-slide="next">
<img src="images/next.png" alt="">
<span class="sr-only">Next</span>
</a>
</div>
</div>

</section>
<!-- end slider section -->
</div>

<!-- book section -->

<section class="book_section layout_padding">

<div class="container">
<div class="row">
<div class="col">
<form>
<h4>
BOOK <span>APPOINTMENT</span>
</h4>
<div class="form-row ">
<div class="form-group col-lg-4">
<label for="inputPatientName">Patient Name </label>
<input type="text" class="form-control" id="inputPatientName" placeholder="">
</div>
<div class="form-group col-lg-4">
<label for="inputDoctorName">Doctor's Name</label>
<select name="" class="form-control wide" id="inputDoctorName">
<option value="Normal distribution ">Normal distribution </option>
<option value="Normal distribution ">Normal distribution </option>
<option value="Normal distribution ">Normal distribution </option>
</select>
</div>
<div class="form-group col-lg-4">
<label for="inputDepartmentName">Department's Name</label>
<select name="" class="form-control wide" id="inputDepartmentName">
<option value="Normal distribution ">Normal distribution </option>
<option value="Normal distribution ">Normal distribution </option>
<option value="Normal distribution ">Normal distribution </option>
</select>
</div>
</div>
<div class="form-row ">
<div class="form-group col-lg-4">
<label for="inputPhone">Phone Number</label>
<input type="number" class="form-control" id="inputPhone" placeholder="XXXXXXXXXX">
</div>
<div class="form-group col-lg-4">
<label for="inputSymptoms">Symptoms</label>
<input type="text" class="form-control" id="inputSymptoms" placeholder="">
</div>
<div class="form-group col-lg-4">
<label for="inputDate">Choose Date </label>
<div class="input-group date" id="inputDate" data-date-format="mm-dd-yyyy">
<input type="text" class="form-control" readonly>
<span class="input-group-addon date_icon">
<i class="fa fa-calendar" aria-hidden="true"></i>
</span>
</div>
</div>
</div>
<div class="btn-box">
<button type="submit" class="btn ">Submit Now</button>
</div>
</form>
</div>
</div>
</div>
43
 </section>

<!-- end book section -->

<!-- about section -->

<section class="about_section">
<div class="container ">
<div class="row">
<div class="col-md-6 ">
<div class="img-box">
<img src="images/about-img.jpg" alt="">
</div>
</div>
<div class="col-md-6">
<div class="detail-box">
<div class="heading_container">
<h2>
About <span>Hospital</span>
</h2>
</div>
<p>
has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English.
Many desktop publishing packages and web page editors has a more-or-less normal distribution of letters, as opposed to using 'Content here,
content here', making it look like readable English. Many desktop publishing packages and web page editors
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
</div>
</section>

<!-- end about section -->

<!-- treatment section -->

<section class="treatment_section layout_padding">

<div class="side_img">
<img src="images/treatment-side-img.jpg" alt="">
</div>
<div class="container">
<div class="heading_container heading_center">
<h2>
Hospital <span>Treatment</span>
</h2>
</div>
<div class="row">
<div class="col-md-6 col-lg-3">
<div class="box ">
<div class="img-box">
<img src="images/t1.png" alt="">
</div>
<div class="detail-box">
<h4>
Nephrologist Care
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="box ">
44
 <div class="img-box">
<img src="images/t2.png" alt="">
</div>
<div class="detail-box">
<h4>
Eye Care
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="box ">
<div class="img-box">
<img src="images/t3.png" alt="">
</div>
<div class="detail-box">
<h4>
Pediatrician Clinic
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="box ">
<div class="img-box">
<img src="images/t4.png" alt="">
</div>
<div class="detail-box">
<h4>
Parental Care
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
</div>
</div>
</section>

<!-- end treatment section -->

<!-- team section -->

<section class="team_section layout_padding">

<div class="container">
<div class="heading_container heading_center">
<h2>
Our <span>Doctors</span>
</h2>
</div>
<div class="carousel-wrap ">
<div class="owl-carousel team_carousel">
<div class="item">
<div class="box">
<div class="img-box">
<img src="images/team1.jpg" alt="" />
45
 </div>
<div class="detail-box">
<h5>
Hennry
</h5>
<h6>
MBBS
</h6>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
</div>
</div>
<div class="item">
<div class="box">
<div class="img-box">
<img src="images/team2.jpg" alt="" />
</div>
<div class="detail-box">
<h5>
Jenni
</h5>
<h6>
MBBS
</h6>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
</div>
</div>
<div class="item">
<div class="box">
<div class="img-box">
<img src="images/team3.jpg" alt="" />
</div>
<div class="detail-box">
<h5>
Morco
</h5>
<h6>
MBBS
</h6>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
46
 <a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>

<!-- end team section -->

<!-- client section -->

<section class="client_section layout_padding">
<div class="container">
<div class="heading_container">
<h2>
<span>Testimonial</span>
</h2>
</div>
</div>
<div class="container px-0">
<div id="customCarousel2" class="carousel carousel-fade" data-ride="carousel">
<div class="carousel-inner">
<div class="carousel-item active">
<div class="box">
<div class="client_info">
<div class="client_name">
<h5>
Morijorch
</h5>
<h6>
Default model text
</h6>
</div>
<i class="fa fa-quote-left" aria-hidden="true"></i>
</div>
<p>
editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their
infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still
in their infancy. Various
</p>
</div>
</div>
<div class="carousel-item">
<div class="box">
<div class="client_info">
<div class="client_name">
<h5>
Rochak
</h5>
<h6>
Default model text
</h6>
</div>
<i class="fa fa-quote-left" aria-hidden="true"></i>
</div>
<p>
Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still
in their infancy. editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy.
</p>
</div>
</div>
<div class="carousel-item">
47
 <div class="box">
<div class="client_info">
<div class="client_name">
<h5>
Brad Johns
</h5>
<h6>
Default model text
</h6>
</div>
<i class="fa fa-quote-left" aria-hidden="true"></i>
</div>
<p>
Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy, editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their
infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy. Various
</p>
</div>
</div>
</div>
<div class="carousel_btn-box">
<a class="carousel-control-prev" href="#customCarousel2" role="button" data-slide="prev">
<i class="fa fa-angle-left" aria-hidden="true"></i>
<span class="sr-only">Previous</span>
</a>
<a class="carousel-control-next" href="#customCarousel2" role="button" data-slide="next">
<i class="fa fa-angle-right" aria-hidden="true"></i>
<span class="sr-only">Next</span>
</a>
</div>
</div>
</div>
</section>
<!-- end client section -->

<!-- contact section -->

<section class="contact_section layout_padding-bottom">
<div class="container">
<div class="heading_container">
<h2>
Get In Touch
</h2>
</div>
<div class="row">
<div class="col-md-7">
<div class="form_container">
<form action="">
<div>
<input type="text" placeholder="Full Name" />
</div>
<div>
<input type="email" placeholder="Email" />
</div>
<div>
<input type="text" placeholder="Phone Number" />
</div>
<div>
<input type="text" class="message-box" placeholder="Message" />
</div>
<div class="btn_box">
<button>
SEND
</button>
</div>
</form>
</div>
</div>
<div class="col-md-5">
<div class="img-box">
<img src="images/contact-img.jpg" alt="">
</div>
</div>
48
 </div>
</div>
</section>
<!-- end contact section -->

<!-- info section -->

<section class="info_section ">
<div class="container">
<div class="info_top">
<div class="info_logo">
<a href="">
<img src="images/logo.png" alt="">
</a>
</div>
<div class="info_form">
<form action="">
<input type="email" placeholder="Your email">
<button>
Subscribe
</button>
</form>
</div>
</div>
<div class="info_bottom layout_padding2">
<div class="row info_main_row">
<div class="col-md-6 col-lg-3">
<h5>
Address
</h5>
<div class="info_contact">
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call +01 1234567890
</span>
</a>
<a href="">
<i class="fa fa-envelope"></i>
<span>
[email protected]
</span>
</a>
</div>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_links">
<h5>
Useful link
</h5>
<div class="info_links_menu">
<a class="active" href="index.html">
Home
</a>
49
 <a href="about.html">
About
</a>
<a href="treatment.html">
Treatment
</a>
<a href="doctor.html">
Doctors
</a>
<a href="testimonial.html">
Testimonial
</a>
<a href="contact.html">
Contact us
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
LATEST POSTS
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post1.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post2.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
News
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post3.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post4.png" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- end info_section -->
50
 <!-- custom js -->
<script src="js/custom.js"></script>

</body>
</html>

Doctor Page
<!DOCTYPE html>
<html>

<head>
<!-- Basic -->
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<!-- Mobile Metas -->
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
<!-- Site Metas -->
<meta name="keywords" content="" />
<meta name="description" content="" />
<meta name="author" content="" />

<title>Mico</title>

<!-- bootstrap core css -->

<link rel="stylesheet" type="text/css" href="css/bootstrap.css" />

<!-- fonts style -->

<link href="https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700;900&display=swap" rel="stylesheet">

<!--owl slider stylesheet -->

<link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/assets/owl.carousel.min.css" />

<!-- font awesome style -->

<link href="css/font-awesome.min.css" rel="stylesheet" />
<!-- nice select -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/jquery-nice-select/1.1.0/css/nice-select.min.css" integrity="sha256-
mLBIhmBvigTFWPSCtvdu6a76T+3Xyt+K571hupeFLg4=" crossorigin="anonymous" />
<!-- datepicker -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/bootstrap-datepicker/1.3.0/css/datepicker.css">
<!-- Custom styles for this template -->
<link href="css/style.css" rel="stylesheet" />
<!-- responsive style -->
<link href="css/responsive.css" rel="stylesheet" />

</head>

<body class="sub_page">

<div class="hero_area">
<!-- header section strats -->
<header class="header_section">
<div class="header_top">
<div class="container">
<div class="contact_nav">
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call : +01 123455678990
</span>
</a>
<a href="">
<i class="fa fa-envelope" aria-hidden="true"></i>
<span>
Email : [email protected]
</span>

51
 </a>
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
</div>
</div>
</div>
<div class="header_bottom">
<div class="container-fluid">
<nav class="navbar navbar-expand-lg custom_nav-container ">
<a class="navbar-brand" href="index.html">
<img src="images/logo.png" alt="">
</a>
</a>

<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-

controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class=""> </span>
</button>

<div class="collapse navbar-collapse" id="navbarSupportedContent">

<div class="d-flex mr-auto flex-column flex-lg-row align-items-center">
<ul class="navbar-nav ">
<li class="nav-item ">
<a class="nav-link" href="index.html">Home <span class="sr-only">(current)</span></a>
</li>
<li class="nav-item">
<a class="nav-link" href="about.html"> About</a>
</li>
<li class="nav-item">
<a class="nav-link" href="treatment.html">Treatment</a>
</li>
<li class="nav-item active">
<a class="nav-link" href="doctor.html">Doctors</a>
</li>
<li class="nav-item">
<a class="nav-link" href="testimonial.html">Testimonial</a>
</li>
<li class="nav-item">
<a class="nav-link" href="contact.html">Contact Us</a>
</li>
</ul>
</div>
<div class="quote_btn-container">
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Login
</span>
</a>
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Sign Up
</span>
</a>
<form class="form-inline">
<button class="btn my-2 my-sm-0 nav_search-btn" type="submit">
<i class="fa fa-search" aria-hidden="true"></i>
</button>
</form>
</div>
</div>
</nav>
</div>
</div>
</header>
<!-- end header section -->
</div>

52
<!-- team section -->

<section class="team_section layout_padding">

<div class="container">
<div class="heading_container heading_center">
<h2>
Our <span>Doctors</span>
</h2>
</div>
<div class="carousel-wrap ">
<div class="owl-carousel team_carousel">
<div class="item">
<div class="box">
<div class="img-box">
<img src="images/team1.jpg" alt="" />
</div>
<div class="detail-box">
<h5>
Hennry
</h5>
<h6>
MBBS
</h6>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
</div>
</div>
<div class="item">
<div class="box">
<div class="img-box">
<img src="images/team2.jpg" alt="" />
</div>
<div class="detail-box">
<h5>
Jenni
</h5>
<h6>
MBBS
</h6>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
</div>
</div>
<div class="item">
<div class="box">
<div class="img-box">
<img src="images/team3.jpg" alt="" />
53
 </div>
<div class="detail-box">
<h5>
Morco
</h5>
<h6>
MBBS
</h6>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>

<!-- end team section -->

<!-- info section -->

<section class="info_section ">
<div class="container">
<div class="info_top">
<div class="info_logo">
<a href="">
<img src="images/logo.png" alt="">
</a>
</div>
<div class="info_form">
<form action="">
<input type="email" placeholder="Your email">
<button>
Subscribe
</button>
</form>
</div>
</div>
<div class="info_bottom layout_padding2">
<div class="row info_main_row">
<div class="col-md-6 col-lg-3">
<h5>
Address
</h5>
<div class="info_contact">
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call +01 1234567890
</span>
</a>
<a href="">
<i class="fa fa-envelope"></i>
<span>
54
 [email protected]
</span>
</a>
</div>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_links">
<h5>
Useful link
</h5>
<div class="info_links_menu">
<a href="index.html">
Home
</a>
<a href="about.html">
About
</a>
<a href="treatment.html">
Treatment
</a>
<a href="doctor.html" class="active">
Doctors
</a>
<a href="testimonial.html">
Testimonial
</a>
<a href="contact.html">
Contact us
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
LATEST POSTS
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post1.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post2.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
55
 <h5>
News
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post3.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post4.png" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- end info_section -->

<script src="js/custom.js"></script>

</body>
</html>

CSS
body {
font-family: 'Roboto', sans-serif;
color: #0c0c0c;
background-color: #ffffff;
overflow-x: hidden;
}

.layout_padding {
padding: 90px 0;
}

.layout_padding2 {
padding: 75px 0;
}

.layout_padding2-top {
padding-top: 75px;
}

.layout_padding2-bottom {
padding-bottom: 75px;
}

.layout_padding-top {
padding-top: 90px;
}

.layout_padding-bottom {
padding-bottom: 90px;
}

.heading_container {
display: -webkit-box;
display: -ms-flexbox;
display: flex;
56
 -webkit-box-orient: vertical;
-webkit-box-direction: normal;
-ms-flex-direction: column;
flex-direction: column;
-webkit-box-align: start;
-ms-flex-align: start;
align-items: flex-start;
}

.heading_container h2 {
position: relative;
font-weight: bold;
}

.heading_container h2 span {
color: #00c6a9;
}

.heading_container.heading_center {
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
text-align: center;
}

a,
a:hover,
a:focus {
text-decoration: none;
}

a:hover,
a:focus {
color: initial;
}

.btn,
.btn:focus {
outline: none !important;
-webkit-box-shadow: none;
box-shadow: none;
}

/*header section*/
.hero_area {
position: relative;
}

.sub_page .hero_area {
height: auto;
}

.sub_page .header_section {
margin-top: 0;
}

.header_section .header_top {
padding: 15px 0;
}

.header_section .header_top .contact_nav {

display: -webkit-box;
display: -ms-flexbox;
display: flex;
}

.header_section .header_top .contact_nav a {

margin-right: 25px;
color: #555555;
}

.header_section .header_top .contact_nav a i {

color: #00c6a9;
57
}

.header_section .header_bottom {
background-color: #00c6a9;
}

.header_section .header_bottom .container-fluid {

padding-right: 25px;
padding-left: 25px;
}

.navbar-brand {
background-color: #ffffff;
padding: 15px 35px;
}

.navbar-brand img {
width: 55px;
}

.custom_nav-container {
padding: 0;
}

.custom_nav-container .navbar-nav .nav-item .nav-link {

padding: 3px 15px;
margin: 10px 15px;
color: #ffffff;
text-align: center;
text-transform: uppercase;
}

.custom_nav-container .navbar-nav .nav-item:hover .nav-link {

color: #252525;
}

.custom_nav-container .nav_search-btn {
width: 35px;
height: 35px;
padding: 0;
border: none;
color: #ffffff;
}

.custom_nav-container .nav_search-btn:hover {
color: #252525;
}

.custom_nav-container .navbar-toggler {
outline: none;
}

.custom_nav-container .navbar-toggler {
padding: 0;
width: 37px;
height: 42px;
-webkit-transition: all .3s;
transition: all .3s;
}

.custom_nav-container .navbar-toggler span {

display: block;
width: 35px;
height: 4px;
background-color: #ffffff;
margin: 7px 0;
-webkit-transition: all 0.3s;
transition: all 0.3s;
position: relative;
border-radius: 5px;
-webkit-transition: all .3s;
transition: all .3s;
}
58
.custom_nav-container .navbar-toggler span::before, .custom_nav-container .navbar-toggler span::after {
content: "";
position: absolute;
left: 0;
height: 100%;
width: 100%;
background-color: #ffffff;
top: -10px;
border-radius: 5px;
-webkit-transition: all .3s;
transition: all .3s;
}

.custom_nav-container .navbar-toggler span::after {

top: 10px;
}

.custom_nav-container .navbar-toggler[aria-expanded="true"] {
-webkit-transform: rotate(360deg);
transform: rotate(360deg);
}

.custom_nav-container .navbar-toggler[aria-expanded="true"] span {

-webkit-transform: rotate(45deg);
transform: rotate(45deg);
}

.custom_nav-container .navbar-toggler[aria-expanded="true"] span::before, .custom_nav-container .navbar-toggler[aria-expanded="true"]

span::after {
-webkit-transform: rotate(90deg);
transform: rotate(90deg);
top: 0;
}

.custom_nav-container .navbar-toggler[aria-expanded="true"] .s-1 {

-webkit-transform: rotate(45deg);
transform: rotate(45deg);
margin: 0;
margin-bottom: -4px;
}

.custom_nav-container .navbar-toggler[aria-expanded="true"] .s-2 {

display: none;
}

.custom_nav-container .navbar-toggler[aria-expanded="true"] .s-3 {

-webkit-transform: rotate(-45deg);
transform: rotate(-45deg);
margin: 0;
margin-top: -4px;
}

.custom_nav-container .navbar-toggler[aria-expanded="false"] .s-1,

.custom_nav-container .navbar-toggler[aria-expanded="false"] .s-2,
.custom_nav-container .navbar-toggler[aria-expanded="false"] .s-3 {
-webkit-transform: none;
transform: none;
}

.quote_btn-container {
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
}

.quote_btn-container a {
color: #ffffff;
margin-right: 25px;
text-transform: uppercase;
59
}

.quote_btn-container a span {
margin-left: 5px;
}

.quote_btn-container a:hover {
color: #252525;
}

/*end header section*/

/* slider section */
.slider_section {
-webkit-box-flex: 1;
-ms-flex: 1;
flex: 1;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
-webkit-box-shadow: 0 5px 15px 0 rgba(0, 0, 0, 0.1);
box-shadow: 0 5px 15px 0 rgba(0, 0, 0, 0.1);
padding-top: 45px;
padding-bottom: 75px;
}

.slider_section .dot_design {
position: absolute;
width: 450px;
right: 0;
bottom: 0;
-webkit-transform: translateY(50%);
transform: translateY(50%);
z-index: 1;
}

.slider_section .dot_design img {

width: 100%;
}

.slider_section .row {
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
}

.slider_section #customCarousel1 {
width: 100%;
position: unset;
}

.slider_section .play_btn {
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
border-radius: 100%;
width: 65px;
height: 65px;
position: relative;
z-index: 3;
margin-top: 15px;
margin-bottom: 45px;
}

.slider_section .play_btn button {

60
 background-color: #00c6a9;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
border-radius: 100%;
width: 100%;
height: 100%;
border: none;
position: relative;
z-index: 5;
color: #ffffff;
outline: none;
}

.slider_section .play_btn::before {
content: "";
width: 100%;
height: 100%;
position: absolute;
top: 50%;
left: 50%;
background-color: #00c6a9;
opacity: 1;
border-radius: 100%;
-webkit-transform: translate(-50%, -50%);
transform: translate(-50%, -50%);
}

.slider_section .play_btn::before {
z-index: 2;
-webkit-animation: before-animation 1500ms infinite;
animation: before-animation 1500ms infinite;
}

@-webkit-keyframes before-animation {
0% {
-webkit-transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1);
transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1);
opacity: 1;
}
100% {
-webkit-transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1.4);
transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1.4);
opacity: 0;
}
}

@keyframes before-animation {
0% {
-webkit-transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1);
transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1);
opacity: 1;
}
100% {
-webkit-transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1.4);
transform: translateX(-50%) translateY(-50%) translateZ(0) scale(1.4);
opacity: 0;
}
}

.slider_section .detail-box {
color: #252525;
}

.slider_section .detail-box h1 {
font-size: 3rem;
font-weight: bold;
61
 text-transform: uppercase;
margin-bottom: 25px;
}

.slider_section .detail-box h1 span {

color: #00c6a9;
}

.slider_section .detail-box p {
color: #6d6d6d;
}

.slider_section .detail-box a {
display: inline-block;
padding: 10px 45px;
background-color: #252525;
color: #ffffff;
border-radius: 5px;
margin-top: 15px;
}

.slider_section .detail-box a:hover {

background-color: #0c0c0c;
}

.slider_section .img-box img {

width: 100%;
}

.slider_section .carousel_btn-box {
position: absolute;
bottom: 0;
right: 10%;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: justify;
-ms-flex-pack: justify;
justify-content: space-between;
width: 110px;
height: 50px;
-webkit-transform: translateY(50%);
transform: translateY(50%);
z-index: 3;
}

.slider_section .carousel_btn-box .carousel-control-prev,

.slider_section .carousel_btn-box .carousel-control-next {
position: unset;
width: 50px;
height: 50px;
background-color: #00c6a9;
opacity: 1;
}

.slider_section .carousel_btn-box .carousel-control-prev img,

.slider_section .carousel_btn-box .carousel-control-next img {
width: 10px;
}

.slider_section .carousel_btn-box .carousel-control-prev:hover,

.slider_section .carousel_btn-box .carousel-control-next:hover {
background-color: #252525;
}

.book_section h4 {
position: relative;
padding-bottom: 5px;
margin-bottom: 35px;
}

.book_section h4 span {
color: #00c6a9;
62
}

.book_section h4::before {
content: "";
position: absolute;
left: 0;
bottom: 0;
width: 75px;
height: 2px;
background-color: #00c6a9;
}

.book_section form {
padding: 35px 45px;
-webkit-box-shadow: 0 0 15px 10px rgba(0, 0, 0, 0.07);
box-shadow: 0 0 15px 10px rgba(0, 0, 0, 0.07);
}

.book_section form label {

color: #000000;
}

.book_section form .form-control {

width: 100%;
background-color: transparent;
border: 1px solid #00c6a9;
height: 45px;
outline: none;
-webkit-box-shadow: none;
box-shadow: none;
border-radius: 5px;
padding: 0 15px;
}

.book_section form .form-control::-webkit-input-placeholder {

color: #00c6a9;
}

.book_section form .form-control:-ms-input-placeholder {

color: #00c6a9;
}

.book_section form .form-control::-ms-input-placeholder {

color: #00c6a9;
}

.book_section form .form-control::placeholder {

color: #00c6a9;
}

.book_section form #inputDate {

color: #00c6a9;
}

.book_section form #inputDate input {

color: #00c6a9;
}

.book_section form button.btn {

background-color: #252525;
color: #ffffff;
padding: 10px 45px;
border-radius: 5px;
margin-top: 10px;
text-transform: uppercase;
}

.book_section .date_icon {
right: 10px;
height: 100%;
position: absolute;
background-color: transparent;
border: none;
63
 display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
color: #00c6a9;
}

.book_section .nice-select:after {
content: "\f107";
font-family: FontAwesome;
border: none;
width: auto;
height: auto;
-webkit-transform: none;
transform: none;
top: 7px;
font-size: 20px;
font-weight: bold;
-webkit-transition: all .3s;
transition: all .3s;
}

.book_section .nice-select.open:after {
content: "\f106";
}

.about_section .row {
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
}

.about_section .img-box img {

max-width: 100%;
}

.about_section .detail-box p {
color: #999;
margin-top: 15px;
}

.about_section .detail-box a {
display: inline-block;
padding: 10px 45px;
background-color: #252525;
color: #ffffff;
border-radius: 5px;
margin-top: 15px;
}

.about_section .detail-box a:hover {

background-color: #0c0c0c;
}

.treatment_section {
position: relative;
}

.treatment_section .side_img {
position: absolute;
right: 15px;
width: 175px;
height: auto;
bottom: 125px;
}

.treatment_section .side_img img {

width: 100%;
64
}

.treatment_section .heading_container h2 {
text-transform: none;
}

.treatment_section .box {
margin-top: 45px;
}

.treatment_section .box .img-box {

width: 65px;
}

.treatment_section .box .img-box img {

width: 100%;
}

.treatment_section .box .detail-box {

margin-top: 15px;
}

.treatment_section .box .detail-box h4 {

font-weight: bold;
}

.treatment_section .box .detail-box a {

text-transform: uppercase;
color: #00c6a9;
}

.treatment_section .box .detail-box a:hover {

color: #252525;
}

.team_section {
background-color: #00c6a9;
}

.team_section .heading_container {
margin-bottom: 45px;
}

.team_section .heading_container h2 {
color: #000000;
text-transform: uppercase;
margin: 0;
}

.team_section .heading_container h2 span {

color: #ffffff;
}

.team_section .box {
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: vertical;
-webkit-box-direction: normal;
-ms-flex-direction: column;
flex-direction: column;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
text-align: center;
-webkit-transition: all 0.3s;
transition: all 0.3s;
padding: 0 10px;
background: -webkit-gradient(linear, left top, left bottom, color-stop(10%, transparent), color-stop(10%, #ffffff));
background: linear-gradient(to bottom, transparent 10%, #ffffff 10%);
}

.team_section .box .img-box img {

65
 width: 100%;
}

.team_section .box .detail-box {

padding: 15px;
border-radius: 10px;
-webkit-transition: all 0.3s;
transition: all 0.3s;
}

.team_section .box .detail-box h5 {

font-weight: bold;
}

.team_section .box .detail-box h6 {

color: #00c6a9;
}

.team_section .box .detail-box .social_box {

display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
}

.team_section .box .detail-box .social_box a {

width: 30px;
height: 30px;
border-radius: 100%;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
font-size: 18px;
margin: 0 2.5px;
color: #000000;
}

.team_section .team_carousel {
margin-top: 45px;
padding: 0 45px;
}

.team_section .team_carousel .owl-nav {

display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
margin-top: 20px;
}

.team_section .team_carousel .owl-nav button {

position: absolute;
top: 50%;
width: 50px;
height: 50px;
background-color: #ffffff;
outline: none;
color: #000000;
-webkit-transform: translateY(-50%);
transform: translateY(-50%);
font-size: 28px;
font-weight: bold;
}
66
.team_section .team_carousel .owl-nav button:hover {
background-color: #252525;
color: #ffffff;
}

.team_section .team_carousel .owl-nav button.owl-prev {

left: -25px;
}

.team_section .team_carousel .owl-nav button.owl-next {

right: -25px;
}

.client_section .heading_container {
margin-bottom: 35px;
}

.client_section .heading_container h2 {
text-transform: uppercase;
margin: 0;
}

.client_section .box {
margin: 15px 45px;
-webkit-box-shadow: 0 0 5px 0 rgba(0, 0, 0, 0.25);
box-shadow: 0 0 5px 0 rgba(0, 0, 0, 0.25);
padding: 25px;
}

.client_section .box .client_info {

display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: justify;
-ms-flex-pack: justify;
justify-content: space-between;
}

.client_section .box .client_info .client_name h5 {

font-weight: 600;
color: #00c6a9;
}

.client_section .box .client_info .client_name h6 {

margin-bottom: 0;
color: #bfc0c0;
font-weight: normal;
font-size: 15px;
}

.client_section .box .client_info i {

font-size: 24px;
}

.client_section .box p {
margin-top: 15px;
}

.client_section .carousel-control-prev,
.client_section .carousel-control-next {
width: 45px;
height: 125px;
background-color: #00c6a9;
opacity: 1;
font-size: 28px;
font-weight: bold;
top: 50%;
-webkit-transform: translateY(-50%);
transform: translateY(-50%);
}

.client_section .carousel-control-prev {
67
 left: 0;
}

.client_section .carousel-control-next {
right: 0;
}

.contact_section {
position: relative;
}

.contact_section .heading_container {
margin-bottom: 25px;
}

.contact_section .heading_container h2 {
text-transform: uppercase;
}

.contact_section .form_container {
margin-right: 45px;
}

.contact_section .form_container input {

width: 100%;
border: 1px solid #00c6a9;
height: 50px;
margin-bottom: 25px;
padding-left: 15px;
background-color: transparent;
outline: none;
color: #101010;
}

.contact_section .form_container input::-webkit-input-placeholder {

color: #00c6a9;
}

.contact_section .form_container input:-ms-input-placeholder {

color: #00c6a9;
}

.contact_section .form_container input::-ms-input-placeholder {

color: #00c6a9;
}

.contact_section .form_container input::placeholder {

color: #00c6a9;
}

.contact_section .form_container input.message-box {

height: 120px;
}

.contact_section .form_container button {

border: none;
text-transform: uppercase;
display: inline-block;
padding: 15px 65px;
background-color: #00c6a9;
color: #ffffff;
border-radius: 0;
font-weight: bold;
}

.contact_section .form_container button:hover {

background-color: #00937d;
}

.contact_section .img-box img {

width: 100%;
}

68
.info_section {
background-color: #252525;
color: #ffffff;
}

.info_section .info_top {
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
}

.info_section .info_top .info_logo {

margin-right: 45px;
}

.info_section .info_top .info_logo a {

display: block;
background-color: #ffffff;
padding: 20px 35px;
}

.info_section .info_top .info_logo a img {

width: 55px;
}

.info_section .info_form {
-webkit-box-flex: 1;
-ms-flex: 1;
flex: 1;
margin-top: 15px;
}

.info_section .info_form form {

display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: end;
-ms-flex-align: end;
align-items: flex-end;
}

.info_section .info_form form input {

background-color: transparent;
padding: 5px 0;
outline: none;
width: 100%;
min-width: 100%;
color: #ffffff;
border: none;
border-bottom: 1px solid #ffffff;
}

.info_section .info_form form input::-webkit-input-placeholder {

color: #9c9c9c;
}

.info_section .info_form form input:-ms-input-placeholder {

color: #9c9c9c;
}

.info_section .info_form form input::-ms-input-placeholder {

color: #9c9c9c;
}

.info_section .info_form form input::placeholder {

color: #9c9c9c;
}

.info_section .info_form form button {

background-color: transparent;
69
 color: #00c6a9;
margin-top: 15px;
text-transform: uppercase;
font-size: 15px;
outline: none;
border: none;
-webkit-transform: translateX(-100%);
transform: translateX(-100%);
}

.info_section h5 {
text-transform: uppercase;
position: relative;
padding-left: 20px;
margin-bottom: 25px;
}

.info_section h5:before {
content: "";
position: absolute;
top: 50%;
left: 0;
width: 15px;
height: 15px;
background-color: #00c6a9;
-webkit-transform: translateY(-50%);
transform: translateY(-50%);
}

.info_section .info_links .info_links_menu {

display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-orient: vertical;
-webkit-box-direction: normal;
-ms-flex-direction: column;
flex-direction: column;
}

.info_section .info_links .info_links_menu a {

color: #ffffff;
}

.info_section .info_links .info_links_menu a:not(:nth-last-child(1)) {

margin-bottom: 10px;
}

.info_section .info_links .info_links_menu a:hover, .info_section .info_links .info_links_menu a.active {

color: #00c6a9;
}

.info_section .info_post .post_box {

display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
}

.info_section .info_post .post_box .img-box {

width: 65px;
min-width: 65px;
height: 65px;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
70
 background-color: #ffffff;
margin-right: 10px;
}

.info_section .info_post .post_box .img-box img {

width: 55px;
}

.info_section .info_post .post_box p {

margin: 0;
}

.info_section .info_post .post_box:not(:nth-last-child(1)) {

margin-bottom: 15px;
}

.info_section .info_contact a {
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
color: #ffffff;
margin-bottom: 10px;
}

.info_section .info_contact a i {
margin-right: 5px;
width: 25px;
}

.info_section .info_contact a:hover p {

color: #ffffff;
}

.info_section .social_box {
width: 100%;
display: -webkit-box;
display: -ms-flexbox;
display: flex;
margin-top: 25px;
}

.info_section .social_box a {
display: -webkit-box;
display: -ms-flexbox;
display: flex;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
color: #00c6a9;
font-size: 24px;
margin-right: 10px;
}

/* footer section*/
.footer_section {
position: relative;
background-color: #252525;
text-align: center;
}

.footer_section p {
color: #ffffff;
padding: 25px 0;
margin: 0;
}

.footer_section p a {
71
 color: inherit;
}

Testimonial Page
<!DOCTYPE html>
<html>

<head>
<title>Mico</title>
<link href="css/style.css" rel="stylesheet" />

</head>

<body class="sub_page">

<div class="hero_area">
<!-- header section strats -->
<header class="header_section">
<div class="header_top">
<div class="container">
<div class="contact_nav">
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call : +01 123455678990
</span>
</a>
<a href="">
<i class="fa fa-envelope" aria-hidden="true"></i>
<span>
Email : [email protected]
</span>
</a>
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
</div>
</div>
</div>
<div class="header_bottom">
<div class="container-fluid">
<nav class="navbar navbar-expand-lg custom_nav-container ">
<a class="navbar-brand" href="index.html">
<img src="images/logo.png" alt="">
</a>
</a>

<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-

controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class=""> </span>
</button>

<div class="collapse navbar-collapse" id="navbarSupportedContent">

<div class="d-flex mr-auto flex-column flex-lg-row align-items-center">
<ul class="navbar-nav ">
<li class="nav-item ">
<a class="nav-link" href="index.html">Home <span class="sr-only">(current)</span></a>
</li>
<li class="nav-item">
<a class="nav-link" href="about.html"> About</a>
</li>
<li class="nav-item">
<a class="nav-link" href="treatment.html">Treatment</a>
</li>
<li class="nav-item">
<a class="nav-link" href="doctor.html">Doctors</a>
</li>

72
 <li class="nav-item active">
<a class="nav-link" href="testimonial.html">Testimonial</a>
</li>
<li class="nav-item">
<a class="nav-link" href="contact.html">Contact Us</a>
</li>
</ul>
</div>
<div class="quote_btn-container">
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Login
</span>
</a>
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Sign Up
</span>
</a>
<form class="form-inline">
<button class="btn my-2 my-sm-0 nav_search-btn" type="submit">
<i class="fa fa-search" aria-hidden="true"></i>
</button>
</form>
</div>
</div>
</nav>
</div>
</div>
</header>
<!-- end header section -->
</div>

<!-- client section -->

<section class="client_section layout_padding">
<div class="container">
<div class="heading_container">
<h2>
<span>Testimonial</span>
</h2>
</div>
</div>
<div class="container px-0">
<div id="customCarousel2" class="carousel carousel-fade" data-ride="carousel">
<div class="carousel-inner">
<div class="carousel-item active">
<div class="box">
<div class="client_info">
<div class="client_name">
<h5>
Morijorch
</h5>
<h6>
Default model text
</h6>
</div>
<i class="fa fa-quote-left" aria-hidden="true"></i>
</div>
<p>
editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their
infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still
in their infancy. Various
</p>
</div>
</div>
<div class="carousel-item">
<div class="box">
<div class="client_info">
73
 <div class="client_name">
<h5>
Rochak
</h5>
<h6>
Default model text
</h6>
</div>
<i class="fa fa-quote-left" aria-hidden="true"></i>
</div>
<p>
Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still
in their infancy. editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy.
</p>
</div>
</div>
<div class="carousel-item">
<div class="box">
<div class="client_info">
<div class="client_name">
<h5>
Brad Johns
</h5>
<h6>
Default model text
</h6>
</div>
<i class="fa fa-quote-left" aria-hidden="true"></i>
</div>
<p>
Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy, editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their
infancy. Variouseditors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in
their infancy. Various
</p>
</div>
</div>
</div>
<div class="carousel_btn-box">
<a class="carousel-control-prev" href="#customCarousel2" role="button" data-slide="prev">
<i class="fa fa-angle-left" aria-hidden="true"></i>
<span class="sr-only">Previous</span>
</a>
<a class="carousel-control-next" href="#customCarousel2" role="button" data-slide="next">
<i class="fa fa-angle-right" aria-hidden="true"></i>
<span class="sr-only">Next</span>
</a>
</div>
</div>
</div>
</section>
<!-- end client section -->

<!-- info section -->

<section class="info_section ">
<div class="container">
<div class="info_top">
<div class="info_logo">
<a href="">
<img src="images/logo.png" alt="">
</a>
</div>
<div class="info_form">
<form action="">
<input type="email" placeholder="Your email">
<button>
Subscribe
</button>
</form>
</div>
74
</div>
<div class="info_bottom layout_padding2">
<div class="row info_main_row">
<div class="col-md-6 col-lg-3">
<h5>
Address
</h5>
<div class="info_contact">
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call +01 1234567890
</span>
</a>
<a href="">
<i class="fa fa-envelope"></i>
<span>
[email protected]
</span>
</a>
</div>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_links">
<h5>
Useful link
</h5>
<div class="info_links_menu">
<a href="index.html">
Home
</a>
<a href="about.html">
About
</a>
<a href="treatment.html">
Treatment
</a>
<a href="doctor.html">
Doctors
</a>
<a class="active" href="testimonial.html">
Testimonial
</a>
<a href="contact.html">
Contact us
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
LATEST POSTS
75
 </h5>
<div class="post_box">
<div class="img-box">
<img src="images/post1.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post2.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
News
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post3.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post4.png" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- end info_section -->

<!-- footer section -->

<footer class="footer_section">
<div class="container">
<p>
&copy; <span id="displayYear"></span> All Rights Reserved By
<a href="https://html.design/">Free Html Templates</a>
</p>
</div>
</footer>
<!-- footer section -->
<script src="js/custom.js"></script>

</body>
</html>

Treatment Page
<!DOCTYPE html>
<html>

76
<head>
<title>Mico</title>
<!-- fonts style -->
<link href="https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700;900&display=swap" rel="stylesheet">
<!-- datepicker -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/bootstrap-datepicker/1.3.0/css/datepicker.css">
<!-- Custom styles for this template -->
<link href="css/style.css" rel="stylesheet" />
</head>
<body class="sub_page">

<div class="hero_area">
<!-- header section strats -->
<header class="header_section">
<div class="header_top">
<div class="container">
<div class="contact_nav">
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call : +01 123455678990
</span>
</a>
<a href="">
<i class="fa fa-envelope" aria-hidden="true"></i>
<span>
Email : [email protected]
</span>
</a>
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
</div>
</div>
</div>
<div class="header_bottom">
<div class="container-fluid">
<nav class="navbar navbar-expand-lg custom_nav-container ">
<a class="navbar-brand" href="index.html">
<img src="images/logo.png" alt="">
</a>
</a>

<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-

controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class=""> </span>
</button>

<div class="collapse navbar-collapse" id="navbarSupportedContent">

<div class="d-flex mr-auto flex-column flex-lg-row align-items-center">
<ul class="navbar-nav ">
<li class="nav-item ">
<a class="nav-link" href="index.html">Home <span class="sr-only">(current)</span></a>
</li>
<li class="nav-item">
<a class="nav-link" href="about.html"> About</a>
</li>
<li class="nav-item active">
<a class="nav-link" href="treatment.html">Treatment</a>
</li>
<li class="nav-item">
<a class="nav-link" href="doctor.html">Doctors</a>
</li>
<li class="nav-item">
<a class="nav-link" href="testimonial.html">Testimonial</a>
</li>
<li class="nav-item">
<a class="nav-link" href="contact.html">Contact Us</a>
</li>
</ul>
77
 </div>
<div class="quote_btn-container">
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Login
</span>
</a>
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Sign Up
</span>
</a>
<form class="form-inline">
<button class="btn my-2 my-sm-0 nav_search-btn" type="submit">
<i class="fa fa-search" aria-hidden="true"></i>
</button>
</form>
</div>
</div>
</nav>
</div>
</div>
</header>
<!-- end header section -->
</div>

<!-- treatment section -->

<section class="treatment_section layout_padding">

<div class="side_img">
<img src="images/treatment-side-img.jpg" alt="">
</div>
<div class="container">
<div class="heading_container heading_center">
<h2>
Hospital <span>Treatment</span>
</h2>
</div>
<div class="row">
<div class="col-md-6 col-lg-3">
<div class="box ">
<div class="img-box">
<img src="images/t1.png" alt="">
</div>
<div class="detail-box">
<h4>
Nephrologist Care
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="box ">
<div class="img-box">
<img src="images/t2.png" alt="">
</div>
<div class="detail-box">
<h4>
Eye Care
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
78
 </a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="box ">
<div class="img-box">
<img src="images/t3.png" alt="">
</div>
<div class="detail-box">
<h4>
Pediatrician Clinic
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="box ">
<div class="img-box">
<img src="images/t4.png" alt="">
</div>
<div class="detail-box">
<h4>
Parental Care
</h4>
<p>
alteration in some form, by injected humour, or randomised words which don't look even slightly e sure there isn't anything
</p>
<a href="">
Read More
</a>
</div>
</div>
</div>
</div>
</div>
</section>

<!-- end treatment section -->

<!-- info section -->

<section class="info_section ">
<div class="container">
<div class="info_top">
<div class="info_logo">
<a href="">
<img src="images/logo.png" alt="">
</a>
</div>
<div class="info_form">
<form action="">
<input type="email" placeholder="Your email">
<button>
Subscribe
</button>
</form>
</div>
</div>
<div class="info_bottom layout_padding2">
<div class="row info_main_row">
<div class="col-md-6 col-lg-3">
<h5>
Address
</h5>
<div class="info_contact">
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
79
 <span>
Location
</span>
</a>
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call +01 1234567890
</span>
</a>
<a href="">
<i class="fa fa-envelope"></i>
<span>
[email protected]
</span>
</a>
</div>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_links">
<h5>
Useful link
</h5>
<div class="info_links_menu">
<a href="index.html">
Home
</a>
<a href="about.html">
About
</a>
<a href="treatment.html" class="active">
Treatment
</a>
<a href="doctor.html">
Doctors
</a>
<a href="testimonial.html">
Testimonial
</a>
<a href="contact.html">
Contact us
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
LATEST POSTS
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post1.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
80
 <div class="post_box">
<div class="img-box">
<img src="images/post2.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
News
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post3.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post4.png" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<script src="js/custom.js"></script>
</body>
</html>

Contact US Page
<!DOCTYPE html>
<html>

<head>
<title>Mico</title>
<!-- bootstrap core css -->
<link rel="stylesheet" type="text/css" href="css/bootstrap.css" />

<!-- fonts style -->

<link href="https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700;900&display=swap" rel="stylesheet">

<!--owl slider stylesheet -->

<link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/assets/owl.carousel.min.css" />

<!-- font awesome style -->

<link href="css/font-awesome.min.css" rel="stylesheet" />
<!-- nice select -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/jquery-nice-select/1.1.0/css/nice-select.min.css" integrity="sha256-
mLBIhmBvigTFWPSCtvdu6a76T+3Xyt+K571hupeFLg4=" crossorigin="anonymous" />
<!-- datepicker -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/bootstrap-datepicker/1.3.0/css/datepicker.css">
<!-- Custom styles for this template -->
<link href="css/style.css" rel="stylesheet" />
<!-- responsive style -->

81
 <link href="css/responsive.css" rel="stylesheet" />

</head>

<body class="sub_page">

<div class="hero_area">
<!-- header section strats -->
<header class="header_section">
<div class="header_top">
<div class="container">
<div class="contact_nav">
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call : +01 123455678990
</span>
</a>
<a href="">
<i class="fa fa-envelope" aria-hidden="true"></i>
<span>
Email : [email protected]
</span>
</a>
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
</div>
</div>
</div>
<div class="header_bottom">
<div class="container-fluid">
<nav class="navbar navbar-expand-lg custom_nav-container ">
<a class="navbar-brand" href="index.html">
<img src="images/logo.png" alt="">
</a>
</a>

<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-

controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class=""> </span>
</button>

<div class="collapse navbar-collapse" id="navbarSupportedContent">

<div class="d-flex mr-auto flex-column flex-lg-row align-items-center">
<ul class="navbar-nav ">
<li class="nav-item ">
<a class="nav-link" href="index.html">Home <span class="sr-only">(current)</span></a>
</li>
<li class="nav-item">
<a class="nav-link" href="about.html"> About</a>
</li>
<li class="nav-item">
<a class="nav-link" href="treatment.html">Treatment</a>
</li>
<li class="nav-item">
<a class="nav-link" href="doctor.html">Doctors</a>
</li>
<li class="nav-item">
<a class="nav-link" href="testimonial.html">Testimonial</a>
</li>
<li class="nav-item active">
<a class="nav-link" href="contact.html">Contact Us</a>
</li>
</ul>
</div>
<div class="quote_btn-container">
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
82
 Login
</span>
</a>
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Sign Up
</span>
</a>
<form class="form-inline">
<button class="btn my-2 my-sm-0 nav_search-btn" type="submit">
<i class="fa fa-search" aria-hidden="true"></i>
</button>
</form>
</div>
</div>
</nav>
</div>
</div>
</header>
<!-- end header section -->
</div>

<!-- contact section -->

<section class="contact_section layout_padding-bottom">
<div class="container">
<div class="heading_container">
<h2>
Get In Touch
</h2>
</div>
<div class="row">
<div class="col-md-7">
<div class="form_container">
<form action="">
<div>
<input type="text" placeholder="Full Name" />
</div>
<div>
<input type="email" placeholder="Email" />
</div>
<div>
<input type="text" placeholder="Phone Number" />
</div>
<div>
<input type="text" class="message-box" placeholder="Message" />
</div>
<div class="btn_box">
<button>
SEND
</button>
</div>
</form>
</div>
</div>
<div class="col-md-5">
<div class="img-box">
<img src="images/contact-img.jpg" alt="">
</div>
</div>
</div>
</div>
</section>
<!-- end contact section -->

<!-- info section -->

<section class="info_section ">
<div class="container">
<div class="info_top">
<div class="info_logo">
<a href="">
<img src="images/logo.png" alt="">
83
 </a>
</div>
<div class="info_form">
<form action="">
<input type="email" placeholder="Your email">
<button>
Subscribe
</button>
</form>
</div>
</div>
<div class="info_bottom layout_padding2">
<div class="row info_main_row">
<div class="col-md-6 col-lg-3">
<h5>
Address
</h5>
<div class="info_contact">
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call +01 1234567890
</span>
</a>
<a href="">
<i class="fa fa-envelope"></i>
<span>
[email protected]
</span>
</a>
</div>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_links">
<h5>
Useful link
</h5>
<div class="info_links_menu">
<a href="index.html">
Home
</a>
<a href="about.html">
About
</a>
<a href="treatment.html">
Treatment
</a>
<a href="doctor.html">
Doctors
</a>
<a href="testimonial.html">
Testimonial
</a>
84
 <a class="active" href="contact.html">
Contact us
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
LATEST POSTS
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post1.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post2.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
News
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post3.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post4.png" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- end info_section -->

<script src="js/custom.js"></script>

</body>
</html>

About US Page

85
<!DOCTYPE html>
<html>

<head>
<title>Mico</title>
<!-- bootstrap core css -->
<link rel="stylesheet" type="text/css" href="css/bootstrap.css" />

<!-- fonts style -->

<link href="https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700;900&display=swap" rel="stylesheet">

<!--owl slider stylesheet -->

<link rel="stylesheet" type="text/css" href="https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/assets/owl.carousel.min.css" />

<!-- font awesome style -->

<link href="css/font-awesome.min.css" rel="stylesheet" />
<!-- nice select -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/jquery-nice-select/1.1.0/css/nice-select.min.css" integrity="sha256-
mLBIhmBvigTFWPSCtvdu6a76T+3Xyt+K571hupeFLg4=" crossorigin="anonymous" />
<!-- datepicker -->
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/bootstrap-datepicker/1.3.0/css/datepicker.css">
<!-- Custom styles for this template -->
<link href="css/style.css" rel="stylesheet" />
<!-- responsive style -->
<link href="css/responsive.css" rel="stylesheet" />

</head>

<body class="sub_page">

<div class="hero_area">
<!-- header section strats -->
<header class="header_section">
<div class="header_top">
<div class="container">
<div class="contact_nav">
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call : +01 123455678990
</span>
</a>
<a href="">
<i class="fa fa-envelope" aria-hidden="true"></i>
<span>
Email : [email protected]
</span>
</a>
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
</div>
</div>
</div>
<div class="header_bottom">
<div class="container-fluid">
<nav class="navbar navbar-expand-lg custom_nav-container ">
<a class="navbar-brand" href="index.html">
<img src="images/logo.png" alt="">
</a>
</a>

<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-

controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
<span class=""> </span>
</button>

<div class="collapse navbar-collapse" id="navbarSupportedContent">

<div class="d-flex mr-auto flex-column flex-lg-row align-items-center">
<ul class="navbar-nav ">
86
 <li class="nav-item ">
<a class="nav-link" href="index.html">Home <span class="sr-only">(current)</span></a>
</li>
<li class="nav-item active">
<a class="nav-link" href="about.html"> About</a>
</li>
<li class="nav-item">
<a class="nav-link" href="treatment.html">Treatment</a>
</li>
<li class="nav-item">
<a class="nav-link" href="doctor.html">Doctors</a>
</li>
<li class="nav-item">
<a class="nav-link" href="testimonial.html">Testimonial</a>
</li>
<li class="nav-item">
<a class="nav-link" href="contact.html">Contact Us</a>
</li>
</ul>
</div>
<div class="quote_btn-container">
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Login
</span>
</a>
<a href="">
<i class="fa fa-user" aria-hidden="true"></i>
<span>
Sign Up
</span>
</a>
<form class="form-inline">
<button class="btn my-2 my-sm-0 nav_search-btn" type="submit">
<i class="fa fa-search" aria-hidden="true"></i>
</button>
</form>
</div>
</div>
</nav>
</div>
</div>
</header>
<!-- end header section -->
</div>

<!-- about section -->

<section class="about_section layout_padding">

<div class="container ">
<div class="row">
<div class="col-md-6 ">
<div class="img-box">
<img src="images/about-img.jpg" alt="">
</div>
</div>
<div class="col-md-6">
<div class="detail-box">
<div class="heading_container">
<h2>
About <span>Hospital</span>
</h2>
</div>
<p>
has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English.
Many desktop publishing packages and web page editors has a more-or-less normal distribution of letters, as opposed to using 'Content here,
content here', making it look like readable English. Many desktop publishing packages and web page editors
</p>
<a href="">
Read More
</a>
87
 </div>
</div>
</div>
</div>
</section>

<!-- end about section -->

<!-- info section -->

<section class="info_section ">
<div class="container">
<div class="info_top">
<div class="info_logo">
<a href="">
<img src="images/logo.png" alt="">
</a>
</div>
<div class="info_form">
<form action="">
<input type="email" placeholder="Your email">
<button>
Subscribe
</button>
</form>
</div>
</div>
<div class="info_bottom layout_padding2">
<div class="row info_main_row">
<div class="col-md-6 col-lg-3">
<h5>
Address
</h5>
<div class="info_contact">
<a href="">
<i class="fa fa-map-marker" aria-hidden="true"></i>
<span>
Location
</span>
</a>
<a href="">
<i class="fa fa-phone" aria-hidden="true"></i>
<span>
Call +01 1234567890
</span>
</a>
<a href="">
<i class="fa fa-envelope"></i>
<span>
[email protected]
</span>
</a>
</div>
<div class="social_box">
<a href="">
<i class="fa fa-facebook" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-twitter" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-linkedin" aria-hidden="true"></i>
</a>
<a href="">
<i class="fa fa-instagram" aria-hidden="true"></i>
</a>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_links">
<h5>
Useful link
</h5>
88
 <div class="info_links_menu">
<a href="index.html">
Home
</a>
<a class="active" href="about.html">
About
</a>
<a href="treatment.html">
Treatment
</a>
<a href="doctor.html">
Doctors
</a>
<a href="testimonial.html">
Testimonial
</a>
<a href="contact.html">
Contact us
</a>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
LATEST POSTS
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post1.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post2.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
<div class="col-md-6 col-lg-3">
<div class="info_post">
<h5>
News
</h5>
<div class="post_box">
<div class="img-box">
<img src="images/post3.jpg" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
<div class="post_box">
<div class="img-box">
<img src="images/post4.png" alt="">
</div>
<p>
Normal
distribution
</p>
</div>
</div>
</div>
</div>
89
 </div>
</div>
</section>
<!-- end info_section -->
<script src="js/custom.js"></script>

</body>
</html>

Screenshot

Home Page:
90
91
Doctors Page:

92
Treatment Page

93
Testimonial Page
94
Contact Page

95
About Us Page

96
Testing
97
7.1. Unit Testing:
- Test individual components or modules of the HMS, such as patient registration,
appointment scheduling, medical record management, billing, and inventory management.
- Write unit tests for each function or method within these components to ensure they work
correctly under various scenarios (e.g., valid and invalid inputs, boundary conditions, error
handling).
- Unit tests can be written and executed by developers during the coding phase.

7.2. Integration Testing:

- Test the integration between different components or modules of the HMS (e.g., patient
registration and appointment scheduling, medical records and billing, inventory management
and procurement).
- Verify that data and information flow correctly between integrated components and that
interfaces (APIs, databases, etc.) work as expected.
- Test scenarios where multiple components interact, such as scheduling an appointment,
updating medical records, and generating bills.

7.3. System Testing:

- Perform end-to-end testing of the entire HMS, including all components, interfaces, and
external systems (e.g., laboratory information systems, radiology systems, electronic health
records).
- Test the system under various loads, stress conditions, and different configurations to
ensure it meets performance, scalability, and reliability requirements.
- Validate that the HMS adheres to healthcare standards, regulations, and security protocols
(e.g., HIPAA compliance, data privacy, and access controls).

7.4. User Acceptance Testing (UAT):

- Involve healthcare professionals (doctors, nurses, administrators, etc.) and simulate real-
world scenarios to test the HMS from the user's perspective.
- Test the usability, workflow, and user interface of the HMS to ensure it meets the needs
and expectations of the end-users.
- Validate that the HMS supports typical healthcare processes, such as patient registration,
diagnosis, treatment planning, and discharge processes.
- Test the accuracy and completeness of data entry, retrieval, and reporting functionalities.

Future enhancements
98
8.1. Potential Improvements:
- Continuously gather feedback from end-users (healthcare professionals, administrators,
patients) to identify areas for improvement and new features that can enhance the usability,
efficiency, and functionality of the HMS.
- Implement advanced analytics and reporting capabilities to provide insights into patient
data, treatment outcomes, resource utilization, and operational performance.
- Enhance the user interface and user experience (UX) to ensure intuitive navigation,
accessibility, and compliance with the latest design standards and best practices.
- Improve data security and privacy measures by implementing advanced encryption, access
controls, and auditing mechanisms to comply with evolving healthcare regulations and
standards.

8.2. Integration with Other Healthcare Systems:

- Develop interfaces and APIs to enable seamless integration with other healthcare systems,
such as Electronic Health Records (EHR), Laboratory Information Systems (LIS), Radiology
Information Systems (RIS), and Picture Archiving and Communication Systems (PACS).
- Implement interoperability standards (e.g., HL7, FHIR) to facilitate data exchange and
communication between the HMS and other healthcare systems, ensuring accurate and
consistent patient information across different platforms.
- Explore the integration of telemedicine capabilities, enabling remote patient monitoring,
virtual consultations, and secure sharing of medical data between healthcare providers and
patients.

8.3. Scalability and Performance Optimization:

- Assess the current architecture and infrastructure of the HMS to identify potential
bottlenecks and areas for improvement in terms of scalability, reliability, and performance.
- Implement load balancing and caching mechanisms to handle increased traffic and user
loads, ensuring consistent and responsive performance.
- Explore the use of cloud computing technologies (e.g., cloud-based storage, computing
resources) to facilitate scalability, redundancy, and disaster recovery capabilities.
- Optimize database performance by implementing indexing, partitioning, and other database
optimization techniques to improve query execution times and overall system
responsiveness.
- Continuously monitor and analyze system performance metrics, identifying and addressing
any performance issues or bottlenecks proactively.

It's important to note that future enhancements should be driven by the evolving needs of the
healthcare industry, changing regulations, technological advancements, and user feedback. A
well-planned and executed enhancement strategy can ensure that the HMS remains relevant,
efficient, and capable of meeting the ever-changing demands of healthcare providers and
patients.

99
 Conclusion
9.1. Summary:
The Hospital Management System (HMS) project aimed to develop a comprehensive
software solution to streamline and automate various administrative, clinical, and operational
processes within a healthcare facility. The system encompassed modules for patient
registration, appointment scheduling, electronic medical records, billing and invoicing,
inventory management, and reporting.

Throughout the project lifecycle, various phases were undertaken, including requirements
gathering, system analysis and design, implementation, testing, and deployment. The system
was developed using modern technologies and programming languages, adhering to industry
standards and best practices.

9.2. Lessons Learned:

During the course of the project, several valuable lessons were learned:

1. Importance of stakeholder involvement: Actively involving healthcare professionals,

administrators, and end-users throughout the project ensured that the system met their
specific needs and requirements, leading to higher user acceptance and adoption.

2. Change management: The healthcare industry is subject to frequent regulatory changes

and evolving standards. Effective change management processes were crucial to adapt the
system accordingly and maintain compliance.

3. Data security and privacy: Handling sensitive patient data required robust security
measures, such as encryption, access controls, and auditing mechanisms, to ensure data
privacy and comply with healthcare regulations (e.g., HIPAA).

4. Integration challenges: Integrating the HMS with other healthcare systems (EHRs, LIS,
RIS) posed technical challenges due to varying data formats and communication protocols.
Adopting industry standards (HL7, FHIR) and creating well-defined interfaces were
essential.

5. Performance and scalability: As the system handled large volumes of data and
concurrent users, performance optimization and scalability measures (load balancing,
caching, database optimization) were crucial to maintain responsiveness and handle
increasing demands.

9.3. Future Scope:

The HMS project has laid a solid foundation for further enhancements and expansions:

1. Continuous improvement: Gathering user feedback and incorporating new features and
improvements based on evolving needs and technological advancements.

100
2.Integration with emerging technologies: Exploring integration with emerging
technologies, such as telemedicine, wearable devices, and artificial intelligence, to enhance
patient care and operational efficiency.

3. Interoperability and data exchange: Expanding interoperability capabilities to

seamlessly exchange data with a wider range of healthcare systems, promoting better
coordination and continuity of care.

4. Analytics and reporting: Enhancing analytical and reporting capabilities to provide

deeper insights into patient data, treatment outcomes, resource utilization, and operational
performance, enabling data-driven decision-making.

5. Cloud adoption: Evaluating the potential benefits of migrating the HMS to a cloud-based
architecture, leveraging scalability, redundancy, and cost-efficiency advantages offered by
cloud computing platforms.

The successful implementation of the HMS has laid the groundwork for continued
innovation and improvement in healthcare delivery, ultimately benefiting patients, healthcare
providers, and the overall healthcare ecosystem.

‘
101
 References
Bibliography

Here's a sample bibliography that could be included in the documentation for the Hospital
Management System (HMS) project:

1. "HIPAA for Professionals." U.S. Department of Health & Human Services,

www.hhs.gov/hipaa/for-professionals/index.html. Accessed 15 May 2023.

2. Bhuvan, V., et al. "Hospital Management Information System (HMIS)." International

Journal of Scientific and Research Publications, vol. 5, no. 6, June 2015, pp. 1-6,
www.ijsrp.org/research-paper-0615/ijsrp-p4196.pdf.

3. "Health Level Seven International (HL7)." HL7 International, www.hl7.org. Accessed 20

May 2023.

4. "FHIR Overview." HL7 International, www.hl7.org/fhir/overview.html. Accessed 20 May

2023.

Websites

  www.slideshare.net
  www.youtube.com
  www.tutorialspoint.com
  www.w3schools.com
  www.stackoverflow.com

Appendices

If there are any additional materials, such as source code snippets, database schemas, or
supplementary information relevant to the HMS project, they can be included as appendices
in the documentation. Appendices provide a structured way to present supporting materials
without interrupting the main flow of the documentation.

For example, an appendix could include:

- Appendix A: Database Schema Diagram

- Appendix B: Sample SQL Scripts
- Appendix C: API Documentation
- Appendix D: User Interface Wireframes and Mockups
- Appendix E: Deployment and Configuration Guidelines

102