System Design Project for Family First Medical Center Analysis

This project outlines the development of a medical information system for Family First Medical Center, addressing the need to replace manual procedures with an efficient digital system. It begins with an executive summary and a system request, followed by an analysis of business requirements, values, and constraints. A detailed work plan is provided, including task durations and dependencies. The feasibility analysis covers technical, organizational, and economic aspects, with a cost-benefit analysis demonstrating the project's economic viability. The project defines both functional and non-functional requirements, along with use cases. Process models, including context diagrams, level 0, level 1, and level 2 data flow diagrams, are created to illustrate system processes. A comprehensive data model, including a data dictionary and an ER diagram, is also included. The project concludes with a bibliography of relevant sources.

Running head: SYSTEM DESIGN
System Design
Name of the Student:
Name of the University:
Author Note

1
SYSTEM DESIGN
Executive Summary
This report has been prepared here for the description of the case for the Family First Medical
Centre. The organization was started by Dr. Robert Slate. However, the current manual
procedures and the paper works have been hampering the business of the organization for a long
time and hence the organization would be helped greatly if a medical information system is
developed for them. The description of the system is also included in this report aided by models
and illustrations.

2
SYSTEM DESIGN
Table of Contents
System Request................................................................................................................................4
Business Requirements................................................................................................................4
Business Values...........................................................................................................................4
Constraints...................................................................................................................................4
Work Plan........................................................................................................................................4
Feasibility Analysis.........................................................................................................................6
Technical......................................................................................................................................6
Organizational..............................................................................................................................6
Economic.....................................................................................................................................7
Requirements Definition..................................................................................................................8
Functional Requirements.............................................................................................................8
Non-functional Requirements......................................................................................................8
Use Cases.........................................................................................................................................9
Process Model................................................................................................................................10
Context Diagram........................................................................................................................10
Level 0 Data Flow Diagram......................................................................................................11
Level 2 Data Flow Diagram......................................................................................................12
Data Model....................................................................................................................................13
Data Dictionary..........................................................................................................................13

3
SYSTEM DESIGN
ER Diagram...............................................................................................................................17
Bibliography..................................................................................................................................18

4
SYSTEM DESIGN
System Request
A medical information system is to be developed for the organization as the current
business procedure have been manual and this very unconvincing for Dr. Slate. Hence, the need
for an information system has come up that would be managing all the information and
procedures of the system.
Business Requirements
The business requirements of the organization are provided below:
 The patients’ details are to store in the system.
 The treatment and the prescription associated with it should be handled properly.
 The prescription is required to be filed.
 Finally, the patient should receive the receipt for the prescriptions.
Business Values
The organization is looking to improve the medical facilities for their customers so that
the cost of treatment is reduced and process is accelerated to a great extent.
Constraints
The company policy does not allow the refills of the Family First prescriptions.
Work Plan
The work plan for the development of the medical information system of the Family First
Medical Center is provided below:
Task Name Duratio Start Finish Predecessors

5
SYSTEM DESIGN
n
Medical Information System Development 80 days Mon 9/2/19 Fri 12/20/19
Project initiation 7 days Mon 9/2/19 Tue 9/10/19
Client Meeting 3 days Mon 9/2/19 Wed 9/4/19
Requirements Gathering 2 days Thu 9/5/19 Fri 9/6/19 2
Budget allocation 2 days Mon 9/9/19 Tue 9/10/19 3
Project design 15 days Wed 9/11/19 Tue 10/1/19
Project team allocation 4 days Wed 9/11/19 Mon 9/16/19 4
functional Requirements 2 days Tue 9/17/19 Wed 9/18/19 6
Non-Functional Requirements 1 day Thu 9/19/19 Thu 9/19/19 7
Hardware Requirements 2 days Fri 9/20/19 Mon 9/23/19 8
System Design 3 days Tue 9/24/19 Thu 9/26/19 9
System Modelling 3 days Fri 9/27/19 Tue 10/1/19 10
Project Implementation 43 days Wed 10/2/19 Fri 11/29/19
Procurement of Hardware 2 days Wed 10/2/19 Thu 10/3/19 11
Software Installation 4 days Fri 10/4/19 Wed 10/9/19 13
Front End Development 11 days Thu 10/10/19 Thu 10/24/19 14
Data base development 14 days Fri 10/25/19 Wed 11/13/19 15

6
SYSTEM DESIGN
Backend integration 12 days Thu 11/14/19 Fri 11/29/19 16
System Testing 13 days Mon 12/2/19 Wed 12/18/19
Error Detection 5 days Mon 12/2/19 Fri 12/6/19 17
Updating current project 6 days Mon 12/9/19 Mon 12/16/19 19
System Documentation 2 days Tue 12/17/19 Wed 12/18/19 20
Project Closure 2 days Thu 12/19/19 Fri 12/20/19
Handing over Documentation 1 day Thu 12/19/19 Thu 12/19/19 21
Project Team Sign Off 1 day Fri 12/20/19 Fri 12/20/19 23
Feasibility Analysis
Technical
The currently manual procedures of the organization would be developed and improved
to a great extent. The procedures would be accelerated and the overall cost of treatment would be
reduced and the hence, the project would be technically feasible.
Organizational
The organizational feasibility depends on business efficiency of the system. The
development of the system would increase the overall efficiency of the business by reducing the

7
SYSTEM DESIGN
response time and increasing the profit. Hence, the system would be feasible for the
organization.
Economic
It is very important that the economic aspect of the project is also considered for the
feasibility of the project. The cost benefit analysis provided below is used here for the feasibility
study.
Analysis Variables:
Discount Rate Used 6.00%
Annual Benefits
$
35,000.00
Annual Operational
Costs
$
8,700.00
One-Time
Development Cost
$
38,000.00
Year of
Project
0 1 2 3 4 5 TOTALS
Economic Benefit $0.00
$
35,000.00
$
35,000.00
$
35,000.00
$
35,000.00
$
35,000.00
Discount Rate 1.0000 0.9434 0.8900 0.8396 0.7921 0.7473
PV of Benefits $0.00
$33,018.8
7 $31,149.88 $29,386.67
$27,723.2
8 $26,154.04
NPV of all
BENEFITS $0.00
$
33,018.87
$
64,168.74
$
93,555.42
$
121,278.7
0
$
147,432.73
$
147,432.73
One-Time COSTS
$(38,000
.00)
Recurring Costs $0.00
$
(8,700.00)
$
(8,700.00)
$
(8,700.00)
$
(8,700.00)
$
(8,700.00)
Discount Rate 1.0000 0.9434 0.8900 0.8396 0.7921 0.7473
PV of Recurring
Costs $0.00
$
(8,207.55)
$
(7,742.97)
$
(7,304.69)
$
(6,891.21)
$
(6,501.15)

8
SYSTEM DESIGN
NPV of all COSTS
$(38,000
.00)
$
(46,207.55
)
$
(53,950.52
)
$
(61,255.20)
$
(68,146.42
)
$
(74,647.56)
$
(74,647.56)
Overall NPV
$
72,785.17
Overall ROI
0.9751
Break-even Analysis
Yearly NPV Cash
FLOW
$(38,000
.00)
$
24,811.32
$
23,406.91
$
22,081.99
$
20,832.06
$
19,652.89
Overall NPV Cash
FLOW
$(38,000
.00)
$
(13,188.68
)
$
10,218.23
$
32,300.21
$
53,132.28
$
72,785.17
From the analysis made above it can be easily seen that both the ROI and NPV obtained
on the analysis variables are positive. Hence, it can be derived that the system development
would be economically feasible for the organization.
Requirements Definition
Functional Requirements
The main functional requirements of the system are:
 Patient name verification
 Patient Diagnosis process
 Storing drug log
 Generation of the receipt of the prescription for the patients
Non-functional Requirements
The non-functional requirements of the system are:

9
SYSTEM DESIGN
 The system should be available 24x7 as the patients might need emergency attention at
any time.
 The data for the system should be secure as the system would be containing a large
amount of data about the health of the patients.
 The system should be scalable as in longer run the system would be required to store an
extensive amount of data.
Use Cases
The main use cases of the system developed for the Family First organization are:
 Registration
 Appointment
 Record details
 Treatment
 Prescription
 Generate Receipt
 Make Payment
 Drug Log

10
SYSTEM DESIGN
Process Model
Context Diagram

11
SYSTEM DESIGN
Level 0 Data Flow Diagram
Level 1 Data Flow Diagram
The treatment and prescription process has been described in this Level 1 Data Flow
diagram provided below: