Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

HHInvoice copayAmtDue copay Paid Insurancelnvoice nsuredAmtDue insured Paid Hous

ID: 3827667 • Letter: H

Question

HHInvoice copayAmtDue copay Paid Insurancelnvoice nsuredAmtDue insured Paid Household HHID InsuranceCo headName address telephone (key 1. company Name visitCopay address contactName lastPaymentDate contactTelephone balance Patient Office Visit patientID (key) visitID name date birthdate Copay Amt gender copay Paid firstVisitDate copay Code lastVisitDate Invoice invoicelD dateSent total Payment o 1 1 amtPreviouslyPaid datePaid am Refused PaymentID date amount 1.2 Procedure procedureDescription totalAmt CopayAmt insurance Paid insuranceDenied descriptionOfTeeth 1.2 MedicalStaff staff ID name address telephone title-position

Explanation / Answer

Hi,

The above diagram clearly depicts the Hospital Management System, in other words its ER-Diagram for Hospital Management.

        SYSTEM DESIGN

1. Introduction

     The purpose of design phase is to plan a solution for problem specified by the requirements. System design aims to identify the modules that should be in the system, the specification of those modules and how they interact with each other to produce the result. The goal of the design process is to produce a model or representation of a system can be used later to build that system. The produced model is called design of the system.

2. Applicable Document

      As the project is user friendly, it can be applied to large database with more information. This software can be used by hospital management to make the work simple. They can get information quickly as possible. It can handle large volume of data and present the report whenever required. In this project, we use SRS as the applicable document.

3. Functional Decomposition

      Functional decomposition refers broadly to the process of resolving a functional relationship into its constituent. Parts in such a way that the original function can be reconstructed from those parts by function composition. In general, this process of decomposition is undertaken either for the purpose of gaining insight into the identity of constituent components (which may reflect individual physical processes of interest, for example) or for

the purpose of obtaining a compressed representation of the global function, a task which is feasible only when the constituent processes possess a certain level of modularity.

4. Functional Component and Assumptions

     4.1. Administration module:-

               Administrator can view all the details of the hospital record.

4.2. Inpatient module:-

          This module is used to store details of patients who are admitted.

4.3. Outpatient module:-

   The outpatient module contains details of the patient who are came for check_ups.

4.4. Lab module:-

           Lab module is used to generate laboratory reports.

4.5. Billing module:-

           Billing module is used to calculate the bill of the patient.

5. Description of the Program

   5.1. Context Flow Diagram:-

              A context flow diagram is a 0th level DFD.It only contains one process node that generalizes the functions of the entire system in relationship to external entities.

Administrator/user

                           Authentication

                          

                                   Lab reports, bill

                                   Statement

                         

                                                                        Hospital Database                                            

5.2. Data Flow Diagram

         A Data flow diagram is a graph showing the flow of data values from their sources in objects through processes that transform them to their destination in other objects.

           A DFD also known as “bubble chart”, has the purpose of clarifying the system requirements and identifying major transformation that will become programs in system design.So, it is the starting point of the design phase that functionally decomposes the requirements specifications down to the lowest level of detail.A DFD consists of a series of bubbles joined by lines.

       

DFD use a number of symbols to represent systems. Most Data flow modeling method use 4 kinds of symbols to represent four kinds of system components:-

Symbols

Description

Process

A process shows a transformation or manipulation of data flows within the system.

External entity

External entities are outside the system, but they either supply input data into the system or use system output.

Data flows

A data flow shows flow of information from source to destination. A data flow is represented by a line, with arrowhead showing the direction of flow.

Data base

Database is a huge collection of data. It is used for storage purpose.

1st level DFD

Receptionist

                          Login                                                   

                          Password

                                          Valid user

                                                                                                                              Database

                                                                                                                       

                                                                   

                                                                               Check up

                                         Patient info       Database

                                                                    Lab

                                                                    Reports                               

                                                         Patient &lab report

Patient

                                          Report                                           Bill/charge   Database

                                          And

                                                               Bill

                                                                      Database                                   

                                      

Level 2 DFD (1.4)

            Admitted patient                                                    Database

                                                                     Lab report &patient report

               Lab report

                                                                                                          Lab report

                                                                        Lab report &patient report

      Patient came for checkup

                                                      Database

Level 2 DFD (1.5)

Charges for inpatient                                   Database

                                                                 Health card amount

                                                                                                            

      Lab charge

Charges for outpatient                                          Health card amount

                                                                              Database

       Lab charge

                                       Database              

5.3. Description of Component

       5.3.1. Administration module:-

                    Input: - User Name, Password

                    Process Definition: - Login to the system

                    Output:-If login is successful then administrator can view and update the records.

5.3.2. Inpatient module:-

            Input: - Inpatient detail

           Process Definition: - Information about the treatment given to the patients who are admitted.

            Output: - Information about the patient.

         Interface with other module: - The inpatient details are necessary for lab reports and billing.

5.3.3. Outpatient module:-

             Input: - Outpatient detail

             Process Definition: - This module has the information about the treatment given to the patient who are came to check up.

           

Output: - Information about the patient.

    Interface with other module: - The outpatient details are necessary for lab reports and billing.

5.3.4. Lab module:-

             Input: - Patient ID, Category

             Process Definition:-Laboratory reports of the patient.

             Output: - Lab report and charge.

             Interface with other module: - This module requires information from inpatient and outpatient modules.

5.3.5. Billing module:-

             Input: - Patient ID

             Process Definition:-Calculates bill and deduct amount if any card facility is available.

             Output: - Bill.

             Interface with other module: - Billing module requires information from inpatient and outpatient modules.

Administrator/user