can i get a eer diagram like using lucid $?$

StayFit is a health club chain in Melbourne that has multiple branches around the city. They have

been operating for the last $2$ years and they are launching new programs for customers to expand

their business. Considering the expansion, they would like to develop a scalable database that can

support their website and the software their staff use for business operations. You have been tasked

with the modelling responsibility of the database. Their requirements around what information need

to be accommodated in the new database are outlined in the description below.

For each branch of the chain, StayFit keeps the branch name, branch address, contact phone

number, and contact email address on record. Each branch has several employees who take care of

the daily operations and provide training support to gym members. Each employee is assigned a

unique ID$.$ Their name, address, phone, email, tax file number $($TFN$),$ and

certifications$/$qualifications are also kept on record. An employee can have multiple qualifications,

for example, Cert III in Fitness, Cert IV in Personal Training, etc.

Members of the gym can sign up with a branch using their online registration process. The

information that are recorded for each member during the sign$-$up process include their name,

address, phone, email, and an emergency contact. StayFit also maintains information on some

known medical conditions that might be triggered in a gym environment for the safety of their

members. For each medical condition, they keep the name of the condition $($e$.$g$.,$ Asthma, Diabetes

Type $1,$ Diabetes Type $2,$ Cardiomyopathy, etc.$)$ and a short description of the problem. While

signing up$,$ a new member is asked to disclose any conditions they may have from this list of known

conditions. Each member can have multiple conditions, and one condition can be associated with

many members. The recorded medical condition$($s$)$ of a member help the staff determine the best

course of action in case of an emergency.

StayFit strives to provide exceptional workout experience for the members. Each branch has a wide

range of equipment for members to use. Each equipment within a branch has a unique ID and a

name. The company also maintains a record of how many of each equipment is currently

operational in a branch. All equipment requires periodic maintenance to ensure they are always

safe to use for the members. Therefore, for each of the equipment the last service date and the next

service date are recorded. The company also records the relevant information of each

maintenance$/$service work carried out for the upkeep of the equipment. The information may

include a unique maintenance number, the date and time of maintenance, the equipment that was

worked on and a short description of the work.

As part of the expansion of business, each branch has started offering fitness programs to the

members. Only the members of a branch can sign$-$up for a program and one member can sign$-$up

for multiple programs at a time. Programs can be classified into two types, i$.$e$.,$ strength training

programs and high$-$intensity interval training $($HIIT$)$ programs. For each fitness program the

database needs to store a program ID$,$ a program title, duration in weeks, start date and end date. In

addition, the recommended amount of minimum daily calory intake is recorded for strength training

programs, and the recommended amount of maximum daily calory intake is recorded for the HIIT

programs.

Each fitness program gets assigned one lead trainer, who is a staff in the branch offering the

program. The lead trainer has the responsibility of the wellbeing of the members in the program.

In addition to the lead trainer, multiple other trainers may get assigned to a program depending on

the demand. The session timetable within a program is not required to be stored in the new database.

It is managed separately by the lead trainer via social media platforms.

You are required to develop an EER model for the above problem description. The EER

should contain all necessary information such as entities, attributes, primary keys,

relationships $($including specialization$/$union if any$),$ cardinalities, and participation

$($including $($min$,$ max$)).$ Any assumptions should also be stated clearly. If assumptions are

made, it is important to make sure that the assumptions reflect possible real practice for a

similar business and do not contradict with the problem description above.