The document summarizes a hospital management system that uses a database to track patient and nurse leader information. The database contains tables for patients and nurse leaders. The patient table stores a patient's personal details, diagnosis, and lab reports. The nurse leader table contains their personal information and work schedule. A one-to-many relationship exists between nurse leaders and patients, where each patient is assigned one nurse leader but a nurse leader can manage multiple patients. The nurse leader ID acts as a foreign key in the patient table to link each patient to their assigned nurse leader.

1. Answers: In the given system, a database is used to
Answers:
In the given system, a database is used to keep track of a patient’s details such as their
diagnosis details, laboratory report, along with their personal details. In the hospital
system, every patient must be under the supervision of a nurse leader, this nurse leader is
responsible for managing the treatment of the patient. The details of the nurse leader in the
system must contain their personal information, their shift timings, and the details of
medication such as any errors in administering doses to the patient. Hence, in this system
the relevant entities are the nurse leader and the patient. The chosen attributes for a patient
include their personal information such as their name, phone number, address, the ward
number in which they are admitted, the details of the diagnosis provided to the patient, and
details of their laboratory report. The chosen attributes of the nurse leader entity also
include their personal details such as their name, phone number, address, joining date (to
figure out their experience in the system), their working hours (or shift timing), and details
of any errors in medication. These attributes were chosen to provide full functionality in the
system and maintain the details of each patient along with the diagnosis provided to them.
The primary attribute for nurse leader and patient is their id, as through these id’s a patient
or a nurse leader can be uniquely identified. Every patient in the system must be overlooked
by a nurse leader, however, a nurse leader may be responsible for multiple patients. The
cardinality of this relation is one-to-many.
The Created Database Model Consists Of These Two Entities With The Aforementioned
Relationship Between Them Where a Nurse Leader Is Responsible For Managing each
patient in the system. The cardinality of this relationship is one nurse leader to many
patients where every patient must have a nurse leader. In the patient table in the database,
the nurse leader id is used as a foreign key and must not contain any null values, this
integrity check ensures that every patient must have a nurse leader managing them.
Bibliography
Sahatqija, K., Ajdari, J., Zenuni, X., Raufi, B., & Ismaili, F. (2018, May). Comparison between
relational and NOSQL databases. In 2018 41st international convention on information and
communication technology, electronics and microelectronics (MIPRO) (pp. 0216-0221).

2. IEEE. 10.23919/MIPRO.2018.8400041
Puja, I., Poscic, P., & Jaksic, D. (2019, May). Overview and Comparison of Several elational
Database Modelling Metodologies and Notations. In 2019 42nd International Convention on
Information and Communication Technology, Electronics and Microelectronics
(MIPRO) (pp. 1641-1646). IEEE. 10.23919/MIPRO.2019.8756667