Answer To: Kent Institute Australia Pty. Ltd. Assessment Brief XXXXXXXXXXABN XXXXXXXXXXCRICOS Code: 00161E RTO...
Aniket answered on Sep 17 2021
TITLE PAGE
HEALTH SYSTEM FOR SMALL MEDICAL PARTITIONING CENTER
EXECUTIVE SUMMARY
This is a health system developed for a small medical partitioning center which will later be adopted by a public hospital. It is developed on OOP system with data structures and algorithms.
INTRODUCTION
A health system consists of various entities, theirs records and operations. In our system we have designed them according to the most suitable data structure and used various algorithms which will fit right according to the operations need. Later we have modified some of our design so that it can become compatible with the public hospital data and can work in the similar and smoother way as it is working for a small medical partitioning center.
BACKGROUND
At the initial stage, we distinguished the use cases of the system and then we created the entities of the system which will be used throughout the system. Now after creating them, we designed the structure of how our class for the desired use case and entity will be made. What will be the data members and what will the member functions for those classes. After that we looked into the data structures part. That which data structure will be the best choice for our system. Then we designed our operations which can be performed in our health system. Now after designing those operations we looked into the algorithms which can help in performing those operations. And finally after building the system for our small medical partitioning center we moved forward towards optimizing it, so that it can work on larger scale data sets and records.
CASE STUDY AND DESIGN
5.1 VARIABLES, RANGES AND KEYS
In this system we will be using linked list as a data structure. We are using linked list here because linked list is a linear collection of data in the form of nodes. According to the project we need to store the data of different doctors, patients and nursing staff so linked list would be the best choice. The implementation of linked list requires class which supports OOPs functionality and its structure can be made according to our own needs and thus would help us to make a replica of the entity of various use cases in our system into the data structure we want via class.
Now for Doctor Node, we will create a class with name Doctor Info which will contain Doctor Id, name, age, mobile no, experience, and specialty. All the nodes of Doctor Info will be contained in a linked list named Doctors. The key here will be Doctor Id. Since it will be a linked list so we need not worry about the range.
Similarly for Nursing Staff Node, we will create a class with name Nursing Staff Info which will contain Staff Id, Name, Age, Mobile no, Experience, and category. All the nodes of Nursing Staff Info will be contained in a linked list named Nursing Staffs. The key here will be Staff Id. Since it will also be a linked list so we need not worry about the range.
And in the same way for Patient Node, we will create a class with name Patient Info which will contain Patient Id, Name, Age, Mobile no, Disease, and Doctor Id. All the nodes of Patient Info will be contained in a linked list named Patients. The key here will be Patient Id. Since it will also be a linked list so we need not worry about the range.
5.2 OPERATIONS AND THEIR JUSTIFICATION
The operations which will be used in this OOP system are given as:-
1. Add Doctor Data
2. Edit Doctor Data
3. Delete Doctor Data
4. Search Doctor Data
5. Search Doctor Data by Specialty
6....